1
Week 1-2 : Model use case diagrams for the specified projects
A use case diagram is a diagram that shows a set of use cases and actors and their
relationships
Use case diagrams commonly contain
Use cases
Actors
Dependency, generalization, and association relationships
Packages, instances of use cases
Notes and constraints
Apply use case diagrams to model the static use case view of a system by modeling
The context of a system
The requirements of a system
To model the context of a system,
Identify the actors that surround the system by considering which groups
require help from the system to perform their tasks; which groups are needed to
execute the system’s functions; which groups interact with external hardware
or other software systems; and which groups perform secondary functions for
administration and maintenance
Organize actors that are similar to one another in a generalization /
specialization hierarchy
Where it aids understandability, provide a stereotype for each such actor
Populate a use case diagram with these actors and specify the paths of
communication from each actor to the system’s use cases
To model the requirements of a system
Establish the context of the system by identifying the actors that surround it.
For each actor, consider the behavior that each expects or requires the system to
provide.
Name these common behaviors as use cases.
2
Factor common behavior into new use cases that are used by others; factor variant
behavior into new use cases that extend more main line flows.
Model these use cases, actors, and their relationships in a use case diagram.
Adorn these use cases with notes that assert nonfunctional requirements; we may have
to attach some of these to the whole system
Use case diagram for ATM system
AIM : To analyze, design and model use case diagram for ATM system
3
SCENARIO : The customer carries out following operations through ATM system
Step1: Identify the actors of a system
1.
2.
3.
Step 2: Identify Use Cases
1.
Use Case Diagram
Use case diagram for Railway reservation system
AIM : To analyze, design and model use case diagram for Railway reservation system
4
SCENARIO : The passenger carries out following operations through the system
Step1: Identify the actors of a system
1.
2.
3.
Step 2: Identify Use Cases
1.
Use Case Diagram
Use case diagram for Library Management System
AIM : To analyze, design and model use case diagram for Library Management system
SCENARIO : The student and librarian carries out following operations
5
Step 1: Identify the actors of a system
1. Librarian
2. Student
Step 2: Identify Each Other’s Functionalities (Use Cases)
Librarian :
1. Add Publication
2. Add books
3. Add Branch
4. Add Student
5. Issue Book
6. Add student issue book
7. Apply Penalty
8. Change Password
9. View Reports
Student
1. Search Book
2. Return Book
3. Pay Penalty
USE DIAGRAM:
Week 3-4 : Model class diagrams for the above specified projects
Class diagrams are used to model the static design view of a system. Graphically, a class diagram is a
collection of vertices and arcs. A class diagram shows a set of
6
Classes
Interfaces
Collaborations
Relationships.
May contain notes and constraints.
May also contain packages or subsystems
Uses:
1. To model the vocabulary of a system
2. To model simple collaborations
3. To model a logical database schema
Modeling Techniques
To model simple collaboration
Identify the mechanism required.
Identify the classes, interfaces, and other collaborations
Use scenarios to walk through these things
Populate these elements with their contents.
To model a schema
Identify the classes in the model
Create a class diagram that contains these classes and mark them as persistent
Expand the structural details of these classes
Watch for common patterns
Consider the behavior of these classes by expanding operations
Use tools to help transform the logical design into a physical design.
Class diagram for ATM system
AIM : To analyze, design and model class diagram for ATM system
Step1: Identify the classes of a system
7
1.
2.
3.
Step 2: Identify relationships
1.
Step 3 : Identify multiplicity
1.
Class Diagram
Class diagram for Railway reservation system
AIM : To analyze, design and model class diagram for railway reservation system
Step1: Identify the classes of a system
8
1.
2.
3.
Step 2: Identify relationships
1.
Step 3 : Identify multiplicity
1.
Class Diagram
Class diagram for Library management system
AIM : To analyze, design and model class diagram for library management system
Step1: Identify the classes of a system
9
1.
2.
3.
Step 2: Identify relationships
1.
Step 3 : Identify multiplicity
1.
Class Diagram
Week 5-6 : Model sequence diagrams for the specified projects
Interaction Diagrams
An interaction diagram shows an interaction, consisting of a set of objects and their
relationships, including the messages that may be dispatched among them
Interaction diagrams are used to model the dynamic aspects of a system.
10
An interaction diagram is basically a projection of the elements found in an interaction.
Interaction diagrams commonly contain Objects, Links, Messages.
It may contain notes and constraints.
Sequence Diagrams
A sequence diagram is an interaction diagram that emphasizes the time ordering of messages
Graphically it is a table that shows objects arranged along the X axis and messages
ordered in increasing time along the Y axis
Place the objects that participate in the interaction at the top of your diagram, across
the X axis, object that initiates the interaction at the left, and increasingly more
subordinate objects to the right
Place the messages that these objects send and receive along the Y axis, in order of
increasing time from top to bottom
