Scribd
Upload
22 views10 pages

UML Diagram

Uploaded by

Endale Aragu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
22 views10 pages

UML Diagram

Uploaded by

Endale Aragu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 10

UML Diagram

Usecase and Class Diagram

1
Use case diagram
• Derived from use-case study scenarios. It is an overview of use cases,
actors, and their communication relationships to demonstrate how
the system reacts to requests from external users. It is used to
capture system requirements

2
Usecase Relationship

3
Cont..
Example optional use cases:
UC5: InspectAccessHistory
»
tend
«ex

ManageAccount
«ex
tend
»
UC6: SetDevicePrefs

Key differences between «include» and «extend» relationships


Included use case Extending use case
Is this use case optional? No Yes
Is the base use case complete
without this use case? No Yes

Is the execution of this use case conditional? No Yes


Does this use case change the
behavior of the base use case? No Yes

[ Source: Robert Maksimchuk & Eric Naiburg: UML for Mere Mortals, Addison-Wesley, 2005. ] 4
Login Use Case?

BAD: GOOD:

Login
«inc
lude
AddUser »
AddUser
Login
Landlord
SetDevicePrefs Landlord SetDevicePrefs lu de»
«inc

5
Class Diagram
• Class diagrams can be derived from use-case diagrams or from
text analysis of the given problem domain.
• A class diagram is generated by system analysts and designers and
will be iteratively refined in the subsequent phases during the
software development life cycle.

6
Relationships between classes

 Generalization: an inheritance relationship


 inheritance between classes

 interface implementation

 Association: a usage relationship


Dependency

 aggregation

 composition

7
Association: a usage relationship
• aggregation: “is part of”
– symbolized by a clear white diamond

• composition: “is entirely made of”


– stronger version of aggregation
– the parts live and die with the whole
– symbolized by a black diamond

8
Cont..
• dependency: “uses temporarily”
– symbolized by dotted line
– often is an implementation detail, not an
• intrinsic part of that object's state

9
Realization
• In a realization relationship, one entity (normally an interface) defines
a set of functionalities as a contract and the other entity (normally a
class) “realizes” the contract by implementing the functionality
defined in the contract.

10

You might also like