Scribd
Upload
179 views4 pages

Use Case Diagram

A use case diagram models the interactions between actors and the system. It includes actors like passengers and databases, and use cases like login, checking availability, making reservations, and issuing tickets. A class diagram shows the classes, attributes, operations, and relationships within a system using notations like rectangles for classes. An activity diagram models workflows and processes through activities, transitions, swimlanes, and end states. It is commonly used to model scenarios like a payment dispatch workflow.

Uploaded by

yashi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
179 views4 pages

Use Case Diagram

A use case diagram models the interactions between actors and the system. It includes actors like passengers and databases, and use cases like login, checking availability, making reservations, and issuing tickets. A class diagram shows the classes, attributes, operations, and relationships within a system using notations like rectangles for classes. An activity diagram models workflows and processes through activities, transitions, swimlanes, and end states. It is commonly used to model scenarios like a payment dispatch workflow.

Uploaded by

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

USE CASE DIAGRAM:

Definition: A behavioral diagram that shows a set of use cases and actors and
their relationships is called a use case diagram. It address the static use case
view of a system and important in modeling the behavior of a system.
The major concepts involved in use case model are:
 Actor: an actor represents anything that interacts with the system.
 Use case: a use case is a sequence of action a system perform that yields a
result to the actor.
 Relation: it defines the relationship between actor and a user.
The actors involved in the use case diagram are:
 Passenger
 Train details DB(database)
 Reservation DB
The use cases involved are:
 Login
 Check availability  Date  Train name  Reservation type
 Fill and Submit form
 Make reservation
 Make cancellation
 Issue ticket

6.2 CLASS DIAGRAM:


Definition: Class diagram is also known as static structure diagram. It is a
collection of static modelling elements such as classes and their relationships.
Class diagrams also show the attributes and operations of the various classes
and the constraints that apply to the way objects are connected.
The various terminologies used in the class diagram are as follows:
Aggregate Relationship: The aggregate relationship shows a whole and part
of relationship between two classes. The classes at the client end of the
aggregate relationship are sometimes called the aggregate class.
Association Relationship: An association provides a pathway for
communication. The types of association are:
• Uni-directional
• Bi-directional
Dependency: A dependency is a relationship between two model elements in
which a change to one model element will affect the other model element.
Generalization: A generalized relationship between classes shows that the
subclass shares the structure or behavior defined in one or more super class.
Class Notation: The UML notation for class is a rectangle divided into 3 parts
 Class Name
 Attributes
 Operations
Interface: An interface is a variation of a class. An interface shares the same
features as a class. In other words, it contains attributes and methods. The only
difference is that the methods are only declared in the interface and will be
implemented by the class implementing the interface.

6.3 ACTIVITY DIAGRAM:


Definition: An activity diagram is typically used for modeling the sequence of
activities in a process. It provides a way to model the workflow of a business
process. An activity diagram is basically a special case of a state machine where
most states are activities.
Using Activity Diagrams: Activity diagram can model many different types of
workflows. For example, a company could use activity diagrams to model the
flow for an payment dispatch.
Understanding Workflows: Each activity represents the performance of a
group of actions in a workflow. Once the activity is complete, the flow of
control moves to the next activity or state through a transition. If an outgoing
transition is not clearly triggered by an event, then it is triggered by the
completion of the contained actions inside the activity. A unique activity
diagram feature is a swimlane that defines who or what is responsible for
carrying out the activity or state. It is also possible to place objects on activity
diagrams. The workflow stops when a transition reaches an end state.
Activity diagrams cannot reside within the component view it is mostly attached
in use case or logical view.

You might also like