Component Design and
Implementation Diagrams

Design Diagrams
1. Use Case Diagram can model the whole system but usually it models subsystem/component
2. (relate actors to major functions)
3. Activity Diagram is usually used to model the whole system or subsystem/component (it shows the sequence of major functions)
4. Use case Detail is used to model a single function or service/component interface
5. Class Diagram (discovered by analyzing the Usecase
Detail and main business document) is used to model a subsystem / component static view
6. Sequence/ Collaboration Diagram (is used to show the sequence of action between classes to perform a single function/ component interface
7. State Diagram (usually done for the most critical object/ component )

Implementation Diagrams
• Component Diagrams:
– The component diagram is one of the easier-tounderstand diagrams,
– set of components and their relationships
– Illustrate static implementation view
– Component maps to one or more classes,
• Package Diagram:
• Organizing element to group
• Can group components
• Deployment Diagrams:
– Set of nodes and their relationships
– Illustrate static deployment view of architecture
– Node typically encloses one or more components

Review of Analysis and Design
Methodologies
1.
2.

Structural Approach (Context Diagram, DFD,
Structural Chart, Structural English)
Object Oriented Approach ( Use Case Diagram, Use
Case detail, Activity diagram, Class diagram,
Sequence diagram, Collaboration Diagram, Package diagram Use-Case Diagrams
• Interaction of Users with System Components
• Actors
– External Entity that Interacts with Software
– Promote Simulation of Events
– Can be People, Software Tools, etc.
• Use-Case Diagram
– Graph of Actors and Set of Use Cases Enclosed by
System (High-Level) or Class Boundary
– Black Box View of System Components
– Derived via User Interviews

Use-Case Diagrams
Supermarket Example
HTSS: System View

HTSS
Scan Items
Ring Order

Cashier

Buy Items

Customer
Catalog
Check Status
Place Order

Customer

Catalog: Class View

Sales Person

Fill Order
Estb. Credit

Supervisor

Use-Case Diagrams Clinic

Activity Diagram
-Granularity Level of Use-Cases is Variable

© Makoto Nakayama, Ph.D.

8

Use Case Detail for the FindProduct Interface within a Store component (usually done for components that have User
Interface, eg. OCX

•

Main Flow
1. The customer selects the “find Product”
2. The customer selects the search criteria
3. The Component returns a list of matching product •

Alternative flow
4-a if there is no product, the component will return no match string
* customer can cancel at any time

•

Ways to identify and classes and class attributes and methods
1. Use cases detail
•

The Nouns in the Use Case Help

Determine Class

attributes
•

The Verbs in the Use Case Help

Methods

2. Major Business documents
3. Major Business process

Determine Class

Getting classes form business document
Order ( what is the most important Document

What entities are related to this document

Getting classes from Business process

Sequence Diagram for Supermarket component’s ordering interface

Collaboration Diagram
• Convey Same Info as Sequence
Diagrams but Focus on Object Roles instead of messages
• Object Roles are Rectangles
• E.g., aHotel, aChain, etc.

Your Turn
For eye glass store
– Create a use case diagram and a set of detail usecase descriptions for the process of buying glasses from the viewpoint of the patient, but do not bother to identify the flow of events within each use case.
The first step is to see an eye doctor who will give you a prescription. Once you have a prescription, you go to a optical dispensary, where you select your frames and place the order for your glasses.
Once the