Showing papers by "Grady Booch published in 2005"

The Unified Modeling Language Reference Manual, Second Edition

Abstract: Like all dynamic languages, the Unified Modeling Language (UML) is growing more complex over time. While it is true that for most developers, this means that you will regularly use a smaller percentage of the language, the actual percentage will vary from person to person and from day to day. Therefore, no abridged UML manual could possibly be adequate. Written by the three creators of the UML, this manual is clearly definitive and one that all developers should have at extended arms reach. Designed to cover the changes in the recently released UML 2.0, which were significant, a CD with the full text in Adobe PDF form with hotlinks to the definitions of the key terms is also included. The opening chapter is an overview of the UML and most people can skip it. Chapter two is an overview of models, and this one is worth reading. Short, it introduces some of the fundamental terminology and approaches. A walkthrough of UML is done in chapter three, which introduces the various formal views of a project. They are: static, design, use case, state machine, activity, interaction, deployment, and model management. Each of these views is then explained in a short chapter. These chapters should be required reading for users of the book, as they establish much of the notational and definitional background used in the reference section. The real value of the book is in the five hundred plus pages of detailed definitions of the key terms and phrases in the UML. Listed in alphabetical order, each entry has the following form:

On creating a handbook of software architecture

Abstract: It is a sign of maturity for any given engineering discipline when we can name, study, and apply the patterns relevant to that domain. In civil engineering, chemical engineering, mechanical engineering, electrical engineering, and now even genomic engineering, there exist libraries of common patterns that have proven themselves useful in practice. Unfortunately, no such architectural reference yet exists for software-intensive systems. Although the patterns community has pioneered the vocabulary of design patterns through the work of the Hillside Group and the Gang of Four, our industry has no parallel to the architecture handbooks found in more mature design disciplines.Following the work of Bruce Anderson, who over a decade ago conducted a series of workshops at OOPSLA, I've begun an effort to fill this void in software engineering by codifying a the architecture of a large collection of interesting software-intensive systems, presenting them in a manner that exposes their essential patterns and that permits comparison across domains and architectural styles.In this presentation, we'll examine the nature of architectural patterns and the process of conducting architectural digs to harvest them, and then examine a few of the systems studied thus far.

Echoes?: structured design and modern software practices

Abstract: Structured Design has been described as a "traditional approach" and an "alternative technology" by the SEI's (Software Engineering Institute) software technology roadmap on their website [July 2005]. While website visitors are cautioned that structured design does not lend itself to object orientation the method has clearly influenced the evolution of object-oriented design practices. This panel brings together software design visionaries to discuss and debate "echoes" in software design "practice".