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
Part 1: Use Case Realisation for the ‘Record New Tour’ Use Case...........................................2
1.1 Analysis Class Diagram:..................................................................................................2
1.2 Communication Diagram:................................................................................................3
Part 2: Sequence Diagram..........................................................................................................4
Part 3: Evaluation.......................................................................................................................6
Bibliography:..............................................................................................................................9

2SYSTEM ANALYSIS AND DESIGN
Part 1: Use Case Realisation for the ‘Record New Tour’ Use Case
1.1 Analysis Class Diagram:
The UML class diagram is the graphical representation of the classes and its attributes
and operations. These classes are representation of structural model of the TMS application.
Each of the classes has a constructor that provide details of each objects of classes
(Fernandez-Saez et al. 2015). Each of the classes are associated with others through a
relationship. This relationship can be association, inheritance, aggregation and more.
The biggest advantage of the class diagram is providing the most basic design element
of an application and that is classes and its characteristics (Dennis, Wixom and Tegarden
2015). However, the class diagram cannot capture all the characteristics of a class but it can
provide enough details to get a gripping idea of the structural pattern of an application.
Figure 1: Class Diagram of Proposed System
(Source: Created by Author)

3SYSTEM ANALYSIS AND DESIGN
The above class diagram shows that the record ne tournament requirement is
established based on three classes. These three classes are tour, driver and clericalAssistant.
Each of these classes has different operations that can be used for different purposes. The
classes are connected to each other using the association relationship. The attributes are
private so that no other package can access the attributes. To make use of the attributes, the
operations are declared as public. Each object of the class will access the attributes through
the operations. This will increase the security of the application directly. One clerical
assistant can record many tours and each tour can have several rivers. There is a limit to enter
the number of drivers but in this case this is not in the concern.
1.2 Communication Diagram:
The communication diagram can be considered as the extension of the class diagram
that only showcase the real communication among the objects of the classes. The
communication diagram uses objects of the classes rather than the class itself and illustrates
how the messages are transferred among the objects (Marrella et al. 2015). It shows the
message flow in a sequence.
The communication diagram is the most scalable diagram of all the UML. The
designer can easily integrate new objects and messages in the communication diagram (Idani
and Ledru 2015). The most popular project methodology, agile development, is suitable for
communication diagram.