Scribd
Upload
126 views

UML Quick Reference Guide 001

Use case diagrams are used to Model the behaviour of a system. Life cycle diagrams show the life cycle of an application. Lifecycle diagrams show how an application is used and used again.

Uploaded by

cfc01
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
126 views

UML Quick Reference Guide 001

Use case diagrams are used to Model the behaviour of a system. Life cycle diagrams show the life cycle of an application. Lifecycle diagrams show how an application is used and used again.

Uploaded by

cfc01
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Rules for Modeling the Diagrams

A
A Use Case Modeling
Step one. With all of the information available, identify the actors. Identify the roles (nouns) that are external
to the system but uses the system
B C Step two. Identify the functions internal to the system (verbs and nouns)
Step three. Model the relationships between actors and use cases – associations (the only relationship that
may exist between an actor and a use case)
* *
Step four. Model relationships between use cases:
D Extend – conditional execution of extending use case
Include – compulsory execution of included use case
Generalization – (specialized use case) Type of (generalized use case). Generalized use case contains
Where do I Model the common behaviour inherited by the specialized use cases
Diagrams?
Class Modeling
B
Use Case View Finding classes: If the use case diagrams are defined, the classes may be derived from the existing use
A Who does what? cases:
Package diagrams
Use case diagrams
The noun from the use case – class
The verb from the use case – operation
Logical View
B With what? The rules of relationships:
Package diagrams Rule 1: If it is part of, have parts and the parts will still exist if the parent is destroyed - Aggregation
Class diagrams Rule 1a: If the parts cannot exist independently after the parent is destroyed – Composition
Object diagrams
Rule 2: If it is a type of another class, or a subtype of another class - Generalization
Composite structure diagrams
Rule 3: If not rule 1 or 2 then there is a 98% probability that it is an association
Dynamic View
C How? B
Object modeling
Package diagrams Definition: An object is an instance of a class. A class must exist first, before an object can be instanced
Analysis diagrams from that class
Activity diagrams
Sequence diagrams
Communication diagrams C
Activity Modeling
Interaction overview diagrams End to end process modeling: Activity = Execution of function. This implies: Activity name = Use case
State machine diagrams name
Timing diagrams Scenario modeling: 1 activity diagram to explain all scenarios

D
Deployment View Sequence modeling
Implemented by what software C
components?
End to end system process modeling: Interaction overview diagram
Package diagrams Scenario modeling: 1 sequence diagram per scenario
Component diagrams
Deployment diagrams C Life Cycle Modeling
A life cycle is attached to a class and describes all of the states that class may be in, in its life

© 2005 Xpdian (Pty) Limited

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy