OOAD (part 2)diagrams

CSCI577a TAs: Alexey

Outline

• UML diagrams:– Use case diagrams– Robustness diagrams– Sequence diagrams– Artifacts diagrams

• ER diagram

UML diagram relationships(in structural models: use case, robustness class diagrams)

Relationship types / link types:– Association – one object

uses/associates with another object – Composition– one object

uses/associates with another object and controls its life cycle.

– Generalization – inheritance: e.g. class - super class.

Examples: WinBook Use Case diagram (all use cases)

Examples: WinBook Use Case diagram (all use cases)

• Common mistakes:– To many details – Functionality expressed in an implementation

specific way– Functions of the system are not viewed from the

perspective of the actors.

Examples: Robustness diagram: Add win-condition

• Common mistakes:– Control flow is not marked– Covers multiple use cases in one diagram – good

practice is to draw different diagrams.– Rainy day scenarios are not covered• What can go wrong on the previous diagram?

Examples: Robustness diagram: Add win-condition

Examples: Sequence diagram: Add win-condition

Examples: Sequence diagram: Add win-condition (full)

• Artifact diagram:– is the specification of a physical piece of

information that is used or produced by a software components

• Deployment diagram– represent the assignment of software artifacts to

deployment targets (e.g. servers, distributions, DBs)

Artifact diagram

Examples: Artifact diagram & Deployment diagram

• Entity–Relationship model is a data model for describing the data of a business domain in an abstract way that can be implemented in a relational database.– Entities– Relationships

ER-diagram

Refferences

• https://en.wikipedia.org/wiki/Artifact_%28UML%29