System Analysis and Design

This document provides an overview of system analysis and design, focusing on use case realisation, analysis class diagram, communication diagram, sequence diagram, and evaluation. It explains the concepts and benefits of each diagram and how they contribute to the development of a system. The document also discusses the use of a CASE tool for analysis and design, and the advantages of using UML models. It concludes with a bibliography of relevant sources.

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..........................................................................................................5
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:
As per the software engineering concept, the class diagram is a type of UML or
unified modelling language. The class diagrams represents a static structural diagram which
visualizes the framework of a system through visualizing the classes of the operations,
attributes and system along with the relationship.
The class diagram can assist in system analysis and design through the following
ways.
i. It can visualize the static classifier structure within the proposed system
ii. The class diagram can offer fundamental notation regarding similar structural
UML diagrams
iii. It can facilitate the work of the developers and other project team staff

3SYSTEM ANALYSIS AND DESIGN
Figure 1: Class Diagram of Wide World Tour Management System
(Source: Created by Author)
For creating the class diagram, it is assumed that tour will be of two types. This will
be shown through the attribute named city. The tour leader and drivers have been shown
through two different classes. The staff type attribute will be used to show staff is self-
employed or not. The customer details are stored in the customer class. The scheduling of the
coaches and drivers are through the start and end data of the tour.
1.2 Communication Diagram:
The Unified Modelling Language or UML communication diagrams are similar to
sequence diagram. It is a type of interaction diagram. This diagram visualizes the interaction

4SYSTEM ANALYSIS AND DESIGN
between the objects of the systems. This is an extended part of the object diagram which
visualizes the system objects along with the system messages which is transferred among the
objects.
The advantage of the communication diagram are as following.
i. It can properly show the functionalities of the use case and processes of record
new tour
ii. The designers can easily catch the interactions among the objects.
Understanding the communication between the objects will be very easy
Figure 2: Communication Diagram of Wide World Tour Management System
(Source: Created by Author)

5SYSTEM ANALYSIS AND DESIGN
All the classes in the class diagram is visualized as the objects in the proposed
communication diagram. The clerical assistance takes the first step to add a tour. Therefore,
the clerical assistance is considered as the first object in the diagram. The tour details are
stored in the tour object. Therefore, the second object is the tour. Then driver object is used to
show driver addition process.
Part 2: Sequence Diagram
UML sequence diagram is used for visualizing the details of the processes that are
carried out. This is a part of UML interaction diagrams. Like communication diagram, it
shows the interaction among the objects within the perspective of collaboration. The focus of
the sequence diagram remains upon the time of message transmission to show the interaction
order.
The advantages of the sequence diagrams are as following.
i. The sequence diagram will assist in identifying the interface, architectural and
logical issues early in the design phase
ii. It can be used as a collaboration tool.
iii. It is effective in documenting the dynamic view of the system design for
several levels

6SYSTEM ANALYSIS AND DESIGN
Figure 3: Sequence Diagram of Wide World Tour Management System
(Source: Created by Author)
To create the sequence diagram each objects are converted into lifelines. Each lifeline
can communicate with each other. A database is also considered as a lifeline to show the
storing of the data into the database. It is assumed that no loop is used in the sequence
diagram. It is because, the clerical assistance selects only a single driver.
Part 3: Evaluation
The CASE or Computer Aided Software Engineering refers to the collection of
various tools that assist in developing and maintaining the software projects. The CASE tools
are a set of applications that can allow designing the system along with making the SDLC
tasks automatic. For analysing the case study of the Wide World Tour Management System,
the CASE tool was a very significant piece of application. The case tool used for analysis,
Enterprise Architect, has many features like structural UML model, behavioural UML model
and many more. It was possible to design every possible diagram for the proposed system
through the Enterprise Architect only. Through the development of the class diagram, the

7SYSTEM ANALYSIS AND DESIGN
attributes of the classes and the operations they will perform has been identified. The case
tool provide very easy interaction module which allowed to concentrate more the case study
rather than usage of the tool itself.
The tool allowed in changing the diagrams even after saving the diagrams. It was not
possible to identify all the aspects of the classes at first. After continuously changing the
initial diagram, the final class diagram was developed. The based on the finding of the class
diagram, the objects of the classes are identified. The enterprise architect allowed to align the
business needs with the technical aspects. The case tool was very assisting in evaluating the
UML models. The case tool has been used extensively to show the message passing among
the objects. The message passing is critical factor system analysis and design as it allow
better system understanding and its object communication.
The first benefit that case tool provided in system analysis is that it allowed focusing
on the architecture of the system without worrying about the coding. The integration of the
requirements of adding a new tour was very easy through the use of the Enterprise Architect.
It is more significant to concentrate on the system operations rather than how to use the tool
itself. The easy to use interface and great interaction modules has made it possible. The use
case diagram provided in the case study allowed understanding of the system behaviour.
However, understanding the elements of the system was a difficult task. If the case tool was
not supportive then it was not possible to generate the classes and the objects of Wide World
Tour Management System. The case tool provided a customized approach toward system
analysis. It was possible to capture the needs of the data processing so that internal
communication among the objects could be identified. Through the case tool, the insight of
the business could be recorded into models which resulted in developing the more model.

8SYSTEM ANALYSIS AND DESIGN
The UML models have been used for developing both the structural and behavioural
models. Perhaps, the biggest advantage of UML model is that it allows the designer to model
both the structural and behavioural model of a system. This means that through the UML
models only, the designers can analyse and design the internal structure, messages passing
through system elements, communication, interface requirements, interaction basics and
more. The UML modelling convention has so many models that it can cover almost all the
aspects of a large information system. The UML is capable of catching both the static and
dynamic aspects of a system. It is very important to create a UML diagram to capture the
basic designs of a system through which the other complex models can be created.

9SYSTEM ANALYSIS AND DESIGN
Bibliography:
Baumann, P., Hahn, T. and Hubbuch, J., 2015. High‐throughput micro‐scale cultivations and
chromatography modeling: Powerful tools for integrated process development.
Biotechnology and bioengineering, 112(10), pp.2123-2133.
Bryman, A. and Bell, E., 2015. Business research methods. Oxford University Press, USA.
Cengarle, M.V., Grönninger, H. and Rumpe, B., 2014. System model semantics of class
diagrams. arXiv preprint arXiv:1409.6635.
Clark, W.C., Tomich, T.P., Van Noordwijk, M., Guston, D., Catacutan, D., Dickson, N.M.
and McNie, E., 2016. Boundary work for sustainable development: Natural resource
management at the Consultative Group on International Agricultural Research (CGIAR).
Proceedings of the National Academy of Sciences, 113(17), pp.4615-4622.
Da Silva, A.R., 2015. Model-driven engineering: A survey supported by the unified
conceptual model. Computer Languages, Systems & Structures, 43, pp.139-155.
Dabbagh, M. and Lee, S.P., 2014. An approach for integrating the prioritization of functional
and nonfunctional requirements. The Scientific World Journal, 2014.
Deeba, F., Kun, S., Shaikh, M., Dharejo, F.A., Hayat, S. and Suwansrikham, P., 2018, April.
Data transformation of UML diagram by using model driven architecture. In 2018 IEEE 3rd
International Conference on Cloud Computing and Big Data Analysis (ICCCBDA) (pp. 300-
303). IEEE.
Dumais, S., Cutrell, E., Cadiz, J.J., Jancke, G., Sarin, R. and Robbins, D.C., 2016, January.
Stuff I've seen: a system for personal information retrieval and re-use. In ACM SIGIR Forum
(Vol. 49, No. 2, pp. 28-35). ACM.

10SYSTEM ANALYSIS AND DESIGN
Eckhardt, J., Vogelsang, A. and Fernández, D.M., 2016. Are" Non-functional" Requirements
really Non-functional? An Investigation of Non-functional Requirements in Practice. In
Software Engineering (ICSE), 2016 IEEE/ACM 38th International Conference on (pp. 832-
842). IEEE.
Ilieva-Obretenovaa, M., 2016. Information System Functions for SmartGrid Management.
Sociology, 6(2), pp.96-103.
Khan, S., Babar, M., Khan, F., Arif, F. and Tahir, M., 2016. Collaboration Methodology for
Integrating Non-Functional Requirements in Architecture. the Journal of Applied
Environmental and Biological Sciences (JAEBS), 6, pp.63-67.
Koller, M., Vadlja, D., Braunegg, G., Atlić, A. and Horvat, P., 2017. Formal-and high-
structured kinetic process modelling and footprint area analysis of binary imaged cells: Tools
to understand and optimize multistage-continuous PHA biosynthesis. The EuroBiotech
Journal, 1(3), pp.203-211.
Lazar, J., Feng, J.H. and Hochheiser, H., 2017. Research methods in human-computer
interaction. Morgan Kaufmann.
Rahman, M. and Ripon, S., 2014. Elicitation and modeling non-functional requirements-a
POS case study. arXiv preprint arXiv:1403.1936.
Ricci, F., Rokach, L. and Shapira, B., 2015. Recommender systems: introduction and
challenges. In Recommender systems handbook (pp. 1-34). Springer, Boston, MA.
Stanton, N.A., Salmon, P.M., Rafferty, L.A., Walker, G.H., Baber, C. and Jenkins, D.P.,
2017. Human factors methods: a practical guide for engineering and design. CRC Press.

11SYSTEM ANALYSIS AND DESIGN
Thum, T., Kastner, C., Benduhn, F., Meinicke, J., Saake, G. and Leich, T., 2014. FeatureIDE:
An extensible framework for feature-oriented software development. Science of Computer
Programming, 79, pp.70-85.
Wichmann, A., Jäger, S., Jungebloud, T., Maschotta, R. and Zimmermann, A., 2016, April.
Specification and execution of system optimization processes with UML activity diagrams.
In Systems Conference (SysCon), 2016 Annual IEEE (pp. 1-7). IEEE.