Architecture and the UML
Tham khảo tài liệu 'architecture and the uml', công nghệ thông tin, quản trị mạng phục vụ nhu cầu học tập, nghiên cứu và làm việc hiệu quả
Architecture and the UML
Models, Views, and Diagrams
A model is a complete
description of a system
from a particular
State
perspective State
Diagrams
Class
Diagrams
Use Case Diagrams
Use Case
Diagrams State
Use Case Use Case
Diagrams State
Diagrams
Use Case Diagrams Object
Diagrams
Diagrams
Sequence Diagrams
Diagrams
Diagrams
Scenario State
Scenario
Diagrams State
Diagrams
Collaboration
Diagrams Models Component
Diagrams
Diagrams Diagrams
Scenario Component
Scenario
Diagrams
Component
Diagrams
Deployment
Statechart
Diagrams Diagrams
Diagrams Diagrams
Activity
Diagrams
Use Case Model
Use Case
Diagrams
Use Case
Use Case
Views
Views Class Object
Diagrams Diagrams
Analysis
Analysis
Views
Views Component
Diagrams
Design
Design Deployment
Views
Views Diagrams
Sequence
Depl.
Depl. Diagrams
Views
Views
Collaboration
Impl.
Impl. Diagrams
Views
Views
Statechart
Diagrams
Test
Test
Views
Views
Activity
Diagrams
Analysis & Design Model
Use Case
Diagrams
Use Case
Use Case
Model
Views Class Object
Diagrams Diagrams
Analysis
Analysis
Model
Views Component
Diagrams Incl. subsystems
and packages
Design
Design Deployment
Model
Views Diagrams
Sequence
Depl.
Depl. Diagrams
Model
Views
Collaboration
Impl.
Impl. Diagrams
Model
Views
Statechart
Diagrams
Test
Test
Model
Views
Activity
Diagrams
Deployment and Implementation
Model Use Case
Diagrams
Use Case
Use Case
Model
Views Class Object
Diagrams Diagrams
Analysis
Analysis
Model
Views Component
Diagrams
Design
Design Deployment
Model
Views Diagrams
Incl. active classes
Sequence and components
Depl.
Depl. Diagrams
Model
Views
Collaboration
Impl.
Impl. Diagrams
Model
Views
Statechart
Diagrams
Test
Test
Model
Views
Activity
Diagrams
Test Model
Use Case
Diagrams
Use Case
Use Case
Model
Views Class Object
Diagrams Diagrams
Analysis
Analysis
Model
Views Component
Diagrams
Design
Design Deployment
Model
Views Diagrams
Test model refers to
all other models and Sequence
Depl.
Depl. Diagrams
Model
Views uses corresponding
diagrams
Collaboration
Impl.
Impl. Diagrams
Model
Views
Statechart
Diagrams
Test
Test
Model
Views
Activity
Diagrams
Use case - functions of a system from the user's point of view
Sequence diagrams -illustrates object interactions arranged in a time sequence.
Class diagrams -static structure in terms of classes and relationships
Activity diagrams -behavior of an operation as a set of actions
State chart diagrams -behavior of a class in terms of states
Collaboration diagrams -spatial representation of objects, links, and interactions
Object diagrams -objects and their relationships and correspond to (simplified
collaboration diagrams that do not represent message broadcasts)
Component diagrams -physical components of an application
Deployment diagrams -deployment of components on particular pieces of hardware
Actors
An actor is someone or some thing that
must interact with the system under
development
Buyerr
seller
Tranc coord
Security system
Use Cases
A use case is a pattern of behavior the system exhibits
- Each use case is a sequence of related transactions
performed by an actor and the system in a dialogue
Actors are examined to determine their needs
- Buyer – post an rfq
- seller – respond to rfq Principal actors
Secondary actors
- Data validator – validate External hardware
- Dep manager -- deploy Other systems
post an rfq Validate deploy
Use Cases
A flow of events document is created for
each use cases
- Written from an actor point of view
Details what the system must provide to
the actor when the use cases is executed
Typical contents
- How the use case starts and ends
- Normal flow of events
- Alternate flow of events
- Exceptional flow of events
Uses and Extends Use Case
Relationships
As the use cases are documented, other
use case relationships may be discovered
- A uses relationship shows behavior that is
common to one or more use cases
- An extends relationship shows optional
behavior
- Communicates shows specific functions
Post an rfq
Logon validation
validate
Use Case Realizations
The use case diagram presents an outside
view of the system
Interaction diagrams describe how use
cases are realized as interactions among
societies of objects
Two types of interaction diagrams
- Sequence diagrams
- Collaboration diagrams
Sequence Diagram
A sequence diagram displays object
interactions arranged in a time sequence
: Buyer registration registration profile
form manager section 1
1: fill in info
2: submit
3: add user
4: add interests
5: save information
6: add info
7: add
Class Diagrams
A class diagram shows the existence of
classes and their relationships in the logical
view of a system
UML modeling elements in class diagrams
- Classes and their structure and behavior
- Association, aggregation, dependency, and
inheritance relationships
- Multiplicity and navigation indicators
- Role names
Classes
A class is a collection of objects with common
structure, common behavior, common
relationships and common semantics
Classes are found by examining the objects in
sequence and collaboration diagram
A class is drawn as a rectangle with three
compartments
Classes should be named using the vocabulary of
the domain
- Naming standards should be created
- e.g., all classes are singular nouns starting with a
capital letter
Classes
1. Attributes and Operations
2. Stereotype
3. Visibility of Attributes
and Operations
«signal» transaction within a state machine.
«interface» description of visible operations.
«metaclass»The class of a class
«utility»A class reduced to the concept of module
Extensibility Mechanisms
Stereotype
Tagged value
Constraint
Common Elements
Common Mechanisms
Data Types
Packages
