- Shopping Bag ( 0 items )
Modeling languages have been used by system developers for decades to specify, visualize, construct, and document systems; rough sketches using stick figures and arrows and scribbled routing conditions go back still further. But the Unified Modeling Language (UML), for the first time in the history of systems engineering, gives practitioners a common language that applies to a multitude of different systems, domains, and methods or processes. It does not guarantee project success, but enables you to communicate ...
Ships from: Murphy, TX
Usually ships in 1-2 business days
Ships from: fallbrook, CA
Usually ships in 1-2 business days
Modeling languages have been used by system developers for decades to specify, visualize, construct, and document systems; rough sketches using stick figures and arrows and scribbled routing conditions go back still further. But the Unified Modeling Language (UML), for the first time in the history of systems engineering, gives practitioners a common language that applies to a multitude of different systems, domains, and methods or processes. It does not guarantee project success, but enables you to communicate solutions in a consistent, standardized, and tool-supported language.All indications suggest that the industry is rushing to the UML. Created by leading software engineering experts Grady Booch, James Rumbaugh, and Ivar Jacobson (now of Rational Software Corporation), and accepted as a standard by the Object Management Group (OMG) in 1997, the language has already achieved more success than any previous contenders. With a firm conceptual and pragmatic basis, it is well suited to supporting projects in modern languages like C++ and Java. And standardization lays the groundwork for tools as well as standard methods or processes.This book presents the UML, including its extension mechanisms and the Object Constraint Language (OCL), in a clear reference format. For those new to the language, a tutorial quickly brings you to the point where you can use the UML. The book is concise and precise, breaking down the information along clean lines and explaining each element of the language. Introductory chapters also convey the purpose of the UML and show its value to projects and as a means for communication.Topics include:
This quick reference guide to Unified Modeling Language (UML) version 1.1 is geared toward managers, engineers and professionals. It details both UML syntax and semantics, and it explores the role of UML in problem solving. For best comprehension, users should be familiar with UML.
What Constitutes the Unified Modeling Language?
The UML Definition
...The UML is defined by a set of documents (Figure 1-2) from Rational Software Corporation and the Object Management Group. The UML definition
The UML semantics document constitutes the single, common, definitive, formal, comprehensive, and precise specification of the UML (called the inside view). The UML semantics document
The UML Notation Guide constitutes the notational or visual representation of the UML and provides examples (called the outside view). The UML Notation Guide
The UML extension documents provide user-defined extensions (using extension mechanisms). These documents
A UML variant is a semantically well-defined language (expressed as a metamodel) based on (and built on top of) the UML metamodel. It specializes the UML but does not change the UML terms or redefine their meanings.
The Object Constraint Language
The Object Constraint Language (OCL) is a formal, easily readable and writable, nonprogramming, implementation-independent language. The OCL
Posted April 12, 2002
This book alleges to be for anyone interested in UML, including engineers, but that's simply not the case. The book does contain a fair amount of detailed technical information, but it tends to be presented in a style more consistent with management-speak than engineering jargon. For example, the introductory chapter contains one of the most buzzword-compliant sentences I've ever been pained to read: '[UML] enables the capturing, communicating, and leveraging of strategic, tactical, and operational knowledge to facilitate increasing value by increasing quality, reducing costs, and reducing time-to-market while managing risks and being proactive in regard to ever-increasing change and complexity.' I don't believe that makes the book useless or bad, but more technical types will be left scratching their heads in puzzlement as they put down the book in favor of 'UML Distilled'. If you want a book to convince your boss that UML is something you should use at work, then this may very well be your best bet. If you need a tech manual to work through some of the finer points, then look elsewhere.Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.