SER 2009

Software Engineering 2.0 and Research 2.0

 
Socialization of Software PDF print email
GradyBooch

We have a cognitive surplus that is the source of incredible visions for the promise of software-intensive systems; turning those visions into raw, running, naked code is, of course, the challenge. While there are some fundamental things that limit us - the fact that we can't transmit messages faster than the speed of light, for one - and some very human ones - the contemporary ethics of a community may discourage us from delivering systems that are otherwise technically feasible - what trips up most organizations is the dance between the technical and the human: how we architect our systems, and how we architect the organizations that develop, deploy, operate, and evolve them. In short, software development is a human activity, subject to all the human drama therein. In this presentation, we'll examine that dance between the technical and the human, and examine some best practices in architecture and social organization.

Short Bio: Grady is recognized internationally for his innovative work in software architecture, software engineering, and collaborative development environments. He has devoted his life's work to improving the art and the science of software development. Grady served as Chief Scientist of Rational Software Corporation since its founding in 1981 and through its acquisition by IBM in 2003. He now is part of the IBM Thomas J. Watson Research Center serving as Chief Scientist for Software Engineering, where he continues his work on the Handbook of Software Architecture and also leads several projects in software engineering that are beyond the constraints of immediate product horizons. Grady is one of the original authors of the Unified Modeling Language (UML). He is the author of six best-selling books and as published several hundred articles on software engineering, including papers published in the early '80s that originated the term and practice of object-oriented design (OOD), plus papers published in the early 2000's that originated the term and practice of collaborative development environments.
SER2009-SocializationOfSoftware_Page_01

Download the presentation  

Trackback(0)

TrackBack URI for this entry

Comments (1)


Show/hide comments
...
Ian Sommerville
An interesting presentation that I sort of agree with, certainly when we are talking about individual systems and maybe even systems of systems, where there are only a small number of systems involved. I wonder what architecture means when we talk about really large systems. Linda Northrop has drawn the analogy of a collection of systems as a city where bits are being constantly repaired, replaced, changed, taken down and made available. But most cities don't have a coherent architecture but are a mix of architectures and architectural styles. In some cities (like Paris) there is a coherence about the architecture in some areas but a radical change in others, e.g. La Defense.

So - the question is - do our current notions of architecture scale? Does architecture imply control? If we move to a situation where we interact with digital ecosystems, how do our current notions of architecture have to change?
Ian Sommerville , 05 November 2009

Write comment

feedShow/hide comment form
smaller | bigger
security image
Write the displayed characters

busy
Last Updated on Thursday, 05 November 2009 08:43