System Analysis and Design for Wide World Tour Management System

This document provides a detailed analysis of the Wide World Tour Management System using UML diagrams like class, communication and sequence diagrams. It also evaluates the use of enterprise architect as a case tool for the analysis and design process.

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:................................................................................................4
Part 2: Sequence Diagram..........................................................................................................5
Part 3: Evaluation.......................................................................................................................7
Bibliography:............................................................................................................................10

2SYSTEM ANALYSIS AND DESIGN
Part 1: Use Case Realisation for the ‘Record New Tour’ Use Case
1.1 Analysis Class Diagram:
The UML class diagrams are consisted of classes, attributes, methods and
relationships. The class diagram is used for modelling the static structure of an application.
The relationships in class diagram can be of many types such as association, composition,
aggregation, inheritance and many more. The class diagrams also visualizes the access
modifiers of operations and attributes.
The class diagram gives the fundamental building squares to the object oriented
strategies and it very well may be viewed as the most valuable element of class diagram. The
most ideal approach to catch the basic example of an object oriented application is through
the class diagram.

3SYSTEM ANALYSIS AND DESIGN
Figure 1: Wide World Tour Management System Class Diagram
(Source: Created by Author)
Only three classes were enough for representing the static structure of the record new
tour use case. As per the description of use case, the assistant class will represent clerical
assistant, tour class will represent tour and driver class will represent driver. The class
diagram demonstrates that the clerical_class and tour class are associated through an
association relationship. It is not referenced in the class diagram how the administrative
partner techniques will be approved or how the right hand can get to the system. The class
diagram just focused on speaking to the auxiliary example of record new visit use case. In

4SYSTEM ANALYSIS AND DESIGN
light of the characteristics and tasks pronounced in the figure 1, other bound together
demonstrating dialect diagrams will be made. The tour class has an attribute named driver
which holds the information of which driver is assigned to the tour. As the tour class is
composed with driver class, it is safe to say they have composition relationship among them.
1.2 Communication Diagram:
The UML diagram has a purpose of showing the communication between various
entities of the system. The UML communication diagrams represents the flow of messages
among the objects of the object oriented application. The objects are presented through
rectangles and messages are shown through lifeline. The communication diagram is kind of a
interaction diagram that mainly concentrates on visualizing the interaction among objects.
Like each other dynamic UML model, the correspondence diagram demonstrates how
the system will reaction to solicitations of clients. The correspondence diagram fills the hole
of class diagram by demonstrating the request of the messages.
Figure 2: Communication Diagram of Wide World Tour Management System
(Source: Created by Author)

5SYSTEM ANALYSIS AND DESIGN
The diagram shows that the create_tour() message is called two times. As the
communication diagram does not show the lifeline of the messages it cannot be understood
when the first call ends and when the second starts. The diagram outlines that the application
can have a solitary administrative class object. All things considered, this implies one
administrative agent can be working in association. The Tour class can have numerous
objects. Be that as it may, in this correspondence diagram just two correspondence diagrams
has been appeared. The visit class does not allude to sparing the administrative colleague who
made the visit. Same way the driver_class can be different objects. The proposed
communication diagram shows that driver object can be included into the operation more
than one time by calling the allocate_driver() message. The communication diagram also
could not identify for which create_tour() message, the allocate_driver() message was called.
Part 2: Sequence Diagram
The UML diagram that describes the interaction between the classes in the context of
a transmission of messages over time. The sequence diagrams are also called as event
diagrams. Among all the UML diagrams, the sequence diagram validates and visualizes the
runtime scenarios perfectly.
So as to catch the dynamic idea of the application or a piece of the application, the
sequence diagram has the greatest part among the various UML diagrams. The class diagram
and communication diagram can't indicate different conditions that are initiated in the login.
The sequence diagram can without much of a stretch speak to this conditions through circle
and other if else boxes.

6SYSTEM ANALYSIS AND DESIGN
Figure 3: Sequence Diagram of Wide World Tour Management System
(Source: Created by Author)
The objects created in the sequence diagram is the reference of classes and every class
only access the attributes defined within it. The imitation of the record new tour operation is
done through calling the create_tour() message. As seen in the diagram, the message is live
until the tour is either saved or operation terminates. The messages are called after the first
create_tour() message help is finished. This delineates two create_tour() messages will work
autonomously. The sequence diagram, notwithstanding, does not demonstrate the limit if visit

7SYSTEM ANALYSIS AND DESIGN
and relegating drivers to visit. Presently the constructor Tour class() will be called by the
tour1 and tour2 objects to dole out qualities to the traits. The allocate_driver() technique is
called through this constructor to appoint a driver to the visit.
Part 3: Evaluation
The Case Tool chose for this task is enterprise architect. The enterprise architect
underpins full life cycle models for the product designing, implanted and continuous system
improvement and data innovation system. The enterprise architect accompanies in-assembled
prerequisite taking care of highlights that permits examination and plan of abnormal state
necessities of TMS. The enterprise architect bolsters multi-user with the goal that colleagues
can all the while deal with the structuring assignments. The execution of enterprise architect
is very high and it can process the solicitations in insignificant time. The case tool can
without much of a stretch suit gigantic groups which has a similar perspective of the business.
The enterprise architect give full detectability with respect to the system prerequisites,
necessity examination and plans. The planning of the diagrams were simple. The case tool
gives finish bolster while making the plans dependent on the examination done on the
enterprise. The effect of the case tool in the examination is prompt. Every one of the
prerequisite can be approved and checked utilizing the case tool. The class, communication
and sequence diagrams are made with right data consequently every one of those plans
outlines precise portrayal of the application. Changing the diagrams are likewise simple. The
enterprise architect stores the structure of the diagram component in a different segment
regardless of whether it is erased from the graphical diagram.
The Case Tool, enterprise architect, allowed to efficiently collect the accurate system
requirements. The diagrams created using the enterprise architect was completely based on
the record new tour use case of TMS or World Tour Management System. The use case

8SYSTEM ANALYSIS AND DESIGN
incorporated the data of how the users can get to the system and how system will answer to
user's inquiry. The enterprise case device has been for the most part used for making the
UML diagrams. These diagrams are class diagram, communication diagram and sequence
diagram. The case device gave the choice of making modules for each extraordinary
diagrams. The enterprise architect is equipped with such a user interface that allows easy
navigation through various diagrams and support drag and drop. The case tool also
documents the diagrams in separate section. For this reason, quality of the analysis and
design becomes extremely high. Taking care of the activities was simple as each diagram
were made and kept up independently. To make the classes simplified alternative was
pursued. In the wake of making the class, activities and characteristics were made through
highlights choice. Same way the objects were announced in the communication and sequence
diagram. Making connections were additionally simple as in each diagram the connections
were pronounced a similar way. In order to implement the relationship into the diagrams, the
relationship types are selected and object to object is dragged.
The system designers and system analysts use the UML diagrams like class, sequence,
communication and more for graphically visualizing both the static and dynamic elements of
the system. The UML diagrams has a section called class diagram that enables the designers
to catch the static structure of the applications. The class diagram likewise demonstrates the
relationship among the classes that enables the analysts to speak to how the classes will speak
with one another amid run time. Regardless of who has built up the diagrams, any system
analyst or designer can get a thought of what is intended to be spoken to through the UML
diagrams. It is because, the UML diagrams are straightforward. The diagrams are additionally
simple to make. This enables the designer to change over the prerequisites of the system to
visual diagrams effortlessly. The system analyst collect the requirements of the system and
analyse those findings to generate information for supporting designs. The enterprise

9SYSTEM ANALYSIS AND DESIGN
architect properly supported the process of analysing the requirement along with converting
those requirements into diagrams. In this manner, the UML diagrams enables the designers to
make a precise login for the application. Each UML diagram is comprised of connections.
These connections enables the designers to catch and speak to the inner communication of the
system elements. As the UML diagram is the present standard for object oriented
programming, the accessibility of data is significantly more than other modelling language.
Through this way the complex diagrams can be created very easily, all the supports can be
taken from various websites. Various diagrams can be created by following the UML
notations. The UML can support both the dynamic and static nature of the application.

10SYSTEM ANALYSIS AND DESIGN
Bibliography:
Afanasyev, A.N., Voit, N.N., Voevodin, E.Y. and Gainullin, R.F., 2015, October. Control of
UML diagrams in designing automated systems software. In Application of Information and
Communication Technologies (AICT), 2015 9th International Conference on (pp. 285-288).
IEEE.
Cunha, A., Garis, A. and Riesco, D., 2015. Translating between Alloy specifications and
UML class diagrams annotated with OCL. Software & Systems Modeling, 14(1), pp.5-25.
Dennis, A., Wixom, B.H. and Tegarden, D., 2015. Systems analysis and design: An object-
oriented approach with UML. John wiley & sons.
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., Hilken, F., Niemann, P. and Wille, R., 2017, July. Formulating model
verification tasks prover-independently as UML diagrams. In European Conference on
Modelling Foundations and Applications (pp. 232-247). Springer, Cham.
Idani, A. and Ledru, Y., 2015. B for modeling secure information systems. In International
Conference on Formal Engineering Methods (pp. 312-318). Springer, Cham.
Ilieva-Obretenovaa, M., 2016. Information System Functions for SmartGrid
Management. Sociology, 6(2), pp.96-103.
Marosin, D., Van Zee, M. and Ghanavati, S., 2016. Formalizing and modeling enterprise
architecture (EA) principles with goal-oriented requirements language (GRL).

11SYSTEM ANALYSIS AND DESIGN
In International Conference on Advanced Information Systems Engineering (pp. 205-220).
Springer, Cham.
Marrella, A., Mecella, M., Russo, A., Steinau, S., Andrews, K. and Reichert, M., 2015. Data
in Business Process Models, A Preliminary Empirical Study (Short Paper). In Service-
Oriented Computing and Applications (SOCA), 2015 IEEE 8th International Conference
on (pp. 116-122). IEEE.