The Unified Modeling Language (UML)

122 downloads 292 Views 65KB Size Report
UML. Semi-formal semantic specification. Includes: abstract syntax, well- formedness rules, dynamic semantics. UML can capture the structure of object- oriented.
The Unified Modeling Language (UML)

UML Semi-formal semantic specification Includes: abstract syntax, well-formedness rules, dynamic semantics UML can capture the structure of object-oriented systems at a higher level than code Diagram Types: The class diagram, the sequence diagram

UML

A good design notation should show overall system structure in a graphic form but leave detailed semantic definitions(?) to text.

7 Design Goals of UML

1. Provide users a read-to-use, expressive visual modeling language so they can develop and exchange meaningful models.

7 Design Goals of UML 2. Provide extensibility and specialization mechanisms to extend the core concepts. –

Users need to be able to: • Build models using core concepts without using extension mechanisms for most normal applications • Add new concepts and notations for issues not covered by the core. • Choose among variant interpretations of existing concepts, when there is no clear consensus • Specialize the concepts, notations and constraints for particular application domains

7 Design Goals of UML

3. Be independent of particular programming languages and development processes.

7 Design Goals of UML

4. Provide a formal basis for understanding the modeling language. • Need to be precise and approachable

7 Design Goals of UML

5. Encourage the growth of the OO tools market.

7 Design Goals of UML

6. Support higher-level development concepts such as collaborations, frameworks, patterns, and components.

7 Design Goals of UML

7. Integrate best practices.

Additional Goals

1. Inclusion of a simpler UML within a general, comprehensive UML

Additional Goals 2. Usefulness in several modeling perspectives Modeling perspectives (Designing Object Oriented Systems, Cook & Daniels) – Essential perspective: concepts – Specification perspective: characteristics – Implementation perspective: construction

Additional Goals

3. Correspondence to code, close enough to permit re-engineering

Additional Goals

4. Computer-aided, as well as manual, usage

Suggest Documents