System Analysis and Design

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student
Name of the University
Author’s note:

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
1. Use Case Diagram:......................................................................................................................2
2. Conceptual Class Diagram:.........................................................................................................6
3. Interaction Diagrams:..................................................................................................................8
3.1 Sequence Diagram:................................................................................................................8
3.1 Collaboration Diagram:.........................................................................................................9
3.1 Activity Diagram:................................................................................................................10
Bibliography:.................................................................................................................................13

2SYSTEM ANALYSIS AND DESIGN
1. Use Case Diagram:
In UML (Unified Modelling Language), a use case diagram is required for adding current
system user (actors). Apart from this, it also highlights their interaction with the system (Soares
2017). Use case diagrams are required for discussion with system or applicants with which user
can interact with the system. The main focus on the system application is to provide help to the
entities. UML is a well-known toolkit which is required for building diagrams. Use case
diagrams provides oval shape where stick figures represent the actors (Cunha, Garis and Riesco
2015). The actors aim to take part in the system for creating a line between actor and use case.
The major components of Use diagram are
Actors: User tends to interact with the given system. An actor in Use case can be
anything like person, organization or outside system that can interact with the application or
system. There can be any external objects which produces or consumes data.
System: The consequence of interaction and action tend to lie between the given actor
and system (Osman and Chaudron 2018). In many cases, system may be also referred to a
scenario.
Goals: It is the end result in most of use case. A successful diagram aims to describe
various kind of activities and variants which is required for reaching a particular goal.
The overall notation of Use case is very much straightforward and does not require any
kinds of symbol like other UML diagram.
Use Cases: The horizontal shaped oval represents different uses which a user may have.
Actors: Stick figures aims to represent the people who employ the use case.

3SYSTEM ANALYSIS AND DESIGN
Association: It is the line or connection between actors of the use case diagram (Septian,
Alianto and Gaol 2017). In some of the complex diagram, it is very much important to
understand the actors that are associated within a Use case.
System boundary boxes: A box is nothing but a proper system which tends to scope up
with all the use case. All the required use cases are considered to just outside the box which is
outside the scope of the system.
Packages: A UML shape helps the user to put various elements on a single group.
Figure 1: Use Case Diagram of ICIMS
(Source: Created by Author)