The Unified Modeling Language
The Unified Modeling Language
Diagrams Methodology
1
MotivationWhy a unified notation? Expressiveness Completeness Consistency
2
The Unified Modeling Language
The Value of the UMLIt is an open standard It supports the entire software development lifecycle It supports diverse application areas It is based on experience and needs of the user community It is supported by many tools
3
Creating UMLUML 2.0
UML 1.4industrialization
UML 1.3revision OMG Acceptance, Nov 1997Final submission to OMG, Sep‘97 First submission to OMG, Jan´97
UML 1.1standardization
UML partners
UML 1.0 UML 0.9Unified Method 0.8
Web - June´96 OOPSLA´95
Other methods
Booch OOAD
OMT
OOSE
4
The Unified Modeling Language
Contributions to UMLMeyer Before and after conditions Booch OOA&D Rumbaugh OMT Jacobson OOSE Shlaer - Mellor Object lifecycles Odell Classification5
Harel Statecharts
Gamma, et al Frameworks and patterns, HP Fusion Operation descriptions and message numbering Embley Singleton classes and high-level view Wirfs-Brock Responsibilities
Motivation (cont.)Why a multi-diagrammatic notation? Focus Multiple aspects of a complex system Complexity Need for detailed analysis and design
6
The Unified Modeling Language
UML Models, Views and DiagramsA diagram is a view into a model Presented from the aspect of a particular stakeholder Provides a partial representation of the system Is semantically consistent with other views
7
Architectural viewAn architectural view is a simplified description (an abstraction) of a system From a particular perspective Covering particular concerns, and Omitting entities that are not relevant to this perspective
8
The Unified Modeling Language
The Architect’s VisionLogical ViewEnd-user Functionality
…… 此处隐藏3373字 ……
Example: registration for an examD1:ExameDate Jan: Examprint print
date subject studentsList 1: Studentprint
day month year time
Name N-1:Student Surname N Student Name Code Name Surname Surname Code Code
SoftEng: Lesson name code
25