UML - Unified Modeling Language The Unified Modeling...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Unified Modeling Language The Unified Modeling Language is a third-generation method for specifying, visualizing, and documenting the artifacts of an object-oriented system under development. The Unified Modeling Language represents the unification of the Booch, Objectory, and OMT methods and their direct and upwardly compatible successor. It also incorporates ideas from a number of other methodologists, including Peter Coad, Derek Coleman, Ward Cunningham, David Embley, Eric Gamma, David Harel, Richard Helm, Ralph Johnson, Stephen Mellor, Bertrand Meyer, Jim Odell, Kenny Rubin, Sally Shlaer, John Vlissides, Paul Ward, Rebecca Wirfs-Brock, and Ed Yourdon. We continue to solicit feedback from these and other methodologists and from the industry at large as we continue their work. Our goal is to make the Unified Modeling Language the basis for a common, stable, and expressive object-oriented development method. Why did we create the unified modeling Language? Identifiable object-oriented methods first appeared in the late 1980s. In the years following--characteristic of almost every emerging discipline--there was an explosion of object-oriented methods as various methodologists experimented with different approaches to object-oriented analysis and design. Experience with a number of these methods grew, accompanied by a growing maturation of the field as a whole as more and more projects applied these ideas to the development of production-quality, mission- critical systems. By the mid-1990s, a few second-generation methods began to appear, most notably Booch '94, the continued evolution of OMT, and Fusion. Given that the Booch and OMT methods were already independently growing together
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
and were collectively recognized as the dominant object-oriented methods worldwide, Booch and Rumbaugh joined forces in October 1994 to forge a complete unification of their work. Both Booch and OMT had begun to adopt Ivar Jacobson's use cases, and thus it was natural that in the fall of 1995, Jacobson formally joined this unification effort. As we began our unification, we established four goals to bound our efforts: A To model systems (and not just software) using object-oriented concepts T To establish an explicit coupling to conceptual as well as executable artifacts T To address the issues of scale inherent in complex, mission-critical systems T To create a method usable by both humans and machines Devising a notation for use in object-oriented analysis and design is not unlike designing a programming language. First, the author must bound the problem: Should the notation encompass requirements specification? Should the notation extend to the level of a visual programming language? Second, the author must strike a balance between expressiveness and simplicity: Too simple a notation will limit the breadth of problems that can be solved; too complex a notation will overwhelm the mortal developer. In the case of unifying existing methods, the author must also be sensitive to the installed base: Make
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

Page1 / 29

UML - Unified Modeling Language The Unified Modeling...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online