System Analysis and Design

This document provides an overview of system analysis and design, focusing on the use case realisation for the 'Record New Tour' use case. It includes analysis class diagram, communication diagram, and sequence diagram. The document also discusses the evaluation of Computer Aided Software Engineering (CASE) tools and the importance of UML diagrams in software development.

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:
In unified modelling language various static diagrams are present. The diagram that
describes the static structure of the application is called class diagram. The class diagram has
four main components such as classes, attributes, methods and relationships. Most of the
class diagram represents the attributes as private and methods as public entities.
The biggest advantage of the class diagram that it can provide the base for generating
other UML diagrams. Another benefit of the class diagram is that it can illustrate the accurate
static structure of the application. The class diagrams are easy to develop and understand.
Figure 1: Wide World Tour Management System Class Diagram
(Source: Created by Author)

3SYSTEM ANALYSIS AND DESIGN
The proposed class diagram in the figure 1 illustrates that the record new tour use case
required four classes. Each of the classes has its own set of attributes and methods. Each
methods are declared in way that it can use the attributes of its own class and generate new
information. As it can be seen, the attributes of all the classes are private access modifier.
This is done to prevent any other class to access the attributes of other class. The class
diagram illustrates that normal classes will be implemented for the record new tour use case.
All the methods will be declared as static so that other classes can access it. The class
diagram also entails that this part of the application will not have any polymorphism.
1.2 Communication Diagram:
Like the static structure of application, the Unified Modelling Language describes the
interactions among the entities of the application. This kind of diagrams are known as the
interaction diagram. The communication diagram is a part of interaction diagram that shows
interaction among the objects. The communication diagram is also considered as the
extended version of object diagram.
The communication diagram can model the flow of messages among the objects and
it is the biggest advantage of communication diagram. Communication diagram is capable of
modelling the system’s architectural design mechanism. The communication diagram also
represents the interactions, which shows the roles within the collaboration scenario.

4SYSTEM ANALYSIS AND DESIGN
Figure 2: Communication Diagram of Wide World Tour Management System
(Source: Created by Author)
The figure 2 represents the communication diagram for record new tour use case. The
rectangles has been used for representing the objects of the classes, described in the class
diagram. The clerical_staff_object shows that it will access two methods. The login is used
by the clerical assistant to access the system. The add_new_tour() method is called by the
clerical object to access the tour class object. The diagram shows the flow of messages in
order through the numbering. The Class_Tour() is a constructor that assigns data to the
attributes of the class. Each object can have different values. The constructor calls the
Add_Leader() and Add_Driver methods to assign leaders and drivers to the tour.
Part 2: Sequence Diagram
Another interaction diagram of Unified Modelling Language is the sequence diagram.
The sequence diagram is responsible for visualizing the process of executing the record new

5SYSTEM ANALYSIS AND DESIGN
tour operation. The sequence diagram illustrates the interaction among the objects of the
application in terms of collaboration. This diagram is focused on the time of the execution of
operations. The diagram also represent the order in which the functions of the application is
executed.
The sequence diagram is capable of visualizing the high-level interaction among the
objects of the system. The sequence diagrams are highly scalable. It can show either a single
operation or a set of operations based on the requirements.
Figure 3: Sequence Diagram of Wide World Tour Management System
(Source: Created by Author)
The sequence diagram represented in the figure 3 shows that clerical staff is assumed
to be an actor and other references to the classes are considered as objects. The diagram does
not concentrate on showing the login, class leader and class driver methods. The sequence

6SYSTEM ANALYSIS AND DESIGN
diagram captures only the scenario that shows the operation of recording a new tour. It shows
that actor clerical_staff_object calls the add_new_tour() method to start the operation. After
that, object of the tour class, object_tour(), calls the constructor to generate a new tour. This
constructor will assign values to the attributes defined in the tour class. Then the constructor
calls the Add_Leader() method first to assign a new leader to the tour and then calls the
Add_Driver() method to assign a driver. In case of driver, the clerical assistant will be asked
to add more drivers. Based on the reply of the assistant, the application will add new driver or
just end the method.
Part 3: Evaluation
The CASE or Computer Aided Software Engineering tool is the collection of software
applications. These applications are referred to as the computer-assisted methods and tools in
the domain of software development for ensuring error free and high quality application. The
enterprise architect is a case tool developed by Sparx System. The tool has integrated
modelling platform that supports information technology systems, embedded development
and more. The CASE tool provides an approach that is consisted with check-points and
disciplines so that analysts and designers can easily develop the system. This feature is also
included in the enterprise architect so that project milestones can be checked during
development. The first thing that enterprise architect offers is high performance modules. The
case tool can easily load the files and processing of the models can also be done very quickly.
Another thing that case tool offers to the designers and analysts is global collaboration. The
enterprise architecture is tightly integrated with the deployable cloud servers so that different
persons from around the world can work on the same project. This makes the communication
of the project very efficient and effective. Another thing that enterprise architect case tool
offers is simulation of the models. However, it is not connected to the prepared class,
sequence and communication diagram but it is extremely important for big projects. The

7SYSTEM ANALYSIS AND DESIGN
system analysts can bring their models to life to check the integrity of the diagrams along
with the effectiveness of the proposed logic.
As a system analyst, the first role was to find out the requirements of the application.
In this case, the concentration is only on the record new tour use case of the world tour
management system. The use case included the information of how the users can access the
system and how system will reply to user’s query. The enterprise case tool has been mainly
used for creating the UML diagrams. These diagrams are class diagram, communication
diagram and sequence diagram. The case tool provided the option of creating modules for
each different diagrams. Managing the elements of the diagram was extremely easy and
accurate. It is because, enterprise architect saves the elements declared in the diagram in
documents. The diagram can be changed by altering the data mentioned in this documents.
Handling the task was very easy as every diagrams were created and maintained separately.
To create the classes drag and drop option was followed. After creating the class, operations
and attributes were created through features option. Same way the objects were declared in
the communication and sequence diagram. Creating relationships were also very easy as in
every diagram the relationships were declared the same way. After choosing the relationship
type, from one class or object to other the pointer was dragged. The name of the classes and
relationships could be declared through the window in middle right potion.
The UML diagrams are most used tool in the object oriented system projects. That is
why there are lots of information available in various journals and tutorials sites about how to
use the UML properly. The UML is considered as a standard notation between the software
developers. The UML provide flexibility that is extremely required in the software
development domain. Modelling the diagrams and interaction among the elements can be
declared particularly for the requirement of the proposed system. The UML diagrams can be
used to accurately follow the architecture of the software. The UML is considered to be a rich

8SYSTEM ANALYSIS AND DESIGN
modelling language that can capture the high-level requirements easily. The UML diagrams
allows the system analysts and designers to capture both the static and dynamic nature of the
system. Along with the structural and behavioral structures can also be captured using the
UML models. That is why the analysts and designers can use the UML notations not only for
object oriented applications but for business process enhancements also. The UML assists in
finding the security, tracking, performance and other system related non-functional
requirements. The analysts use the UML as a visual language that can share the details of the
system to all the stakeholders.

9SYSTEM ANALYSIS AND DESIGN
Bibliography:
Bashir, R.S., Lee, S.P., Khan, S.U.R., Chang, V. and Farid, S., 2016. UML models
consistency management: Guidelines for software quality manager. International Journal of
Information Management, 36(6), pp.883-899.
Bhutto, A. and Hussain, D.M.A., 2018. Validate UML Model and OCL Expressions Using
USE Tool. Pertanika Journal of Science and Technology (jst), 26(3), pp.1465-1480.
Burgueno, L., Gogolla, M. and Vallecillo, A., 2017. Teaching model views with UML and
OCL.
Burgueno, L., Vallecillo, A. and Gogolla, M., 2018. Teaching UML and OCL models and
their validation to software engineering students: an experience report. Computer Science
Education, pp.1-19.
El Ahmar, Y., Le Pallec, X. and Gerard, S., 2016. Empirical Activity: Assessing the
Perceptual Properties of the Size Visual Variation in UML Sequence Diagram. In HuFaMo
workshop.
Fernandez-Saez, A.M., Genero, M., Chaudron, M.R., Caivano, D. and Ramos, I., 2015. Are
Forward Designed or Reverse-Engineered UML diagrams more helpful for code
maintenance?: A family of experiments. Information and Software Technology, 57, pp.644-
663.
Gogolla, M., Hamann, L., Hilken, F. and Sedlmeier, M., 2015. Modeling behavior with
interaction diagrams in a UML and OCL tool. In Behavior Modeling--Foundations and
Applications(pp. 31-58). Springer, Cham.

10SYSTEM ANALYSIS AND DESIGN
Gogolla, M., Hamann, L., Hilken, F. and Sedlmeier, M., 2015. Modeling behavior with
interaction diagrams in a UML and OCL tool. In Behavior Modeling--Foundations and
Applications(pp. 31-58). Springer, Cham.
Gomaa, H., 2015. Designing Real-Time applications with the COMET/UML method. URL:
http://citeseerx. ist. psu. edu/viewdoc/download.
Mani, P. and Prasanna, M., 2017. Test case generation for embedded system software using
UML interaction diagram. J Eng Sci Technol, 12(4), pp.860-874.
Soares, J.A.C., 2017. Automatic Model Transformation from UML Sequence Diagrams to
Coloured Petri Nets.
Storrle, H., 2018. On the impact of size to the understanding of UML diagrams. Software &
Systems Modeling, 17(1), pp.115-134.
Torre, D., Labiche, Y., Genero, M. and Elaasar, M., 2018. A systematic identification of
consistency rules for UML diagrams. Journal of Systems and Software.