IMAT5205 - System Analysis and Design: Modeling a Tour System

Verified

Added on  2023/04/23

|12
|2277
|201
Report
AI Summary
This report presents a system analysis and design for a tour information system, utilizing UML diagrams to model the system's functionality. It includes a class diagram illustrating the structure with classes like clerical assistants, passengers, and tour leaders, detailing their attributes and operations. A communication diagram demonstrates the interactions between these actors, showcasing the flow of information for tasks such as recording new tours, updating details, and processing payments. Furthermore, a sequence diagram outlines the sequential order of interactions, particularly between clerical assistants and passengers, for actions like logging in, updating tour details, and viewing updated information. The report also evaluates the use of CASE tools in enhancing developer productivity and system quality, discussing their benefits and drawbacks, and highlights the role of UML in automating software production and improving system design. The analysis emphasizes the importance of modeling techniques in understanding and implementing complex systems.
Document Page
Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of Student-
Name of University-
Author’s Note-
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
1SYSTEM ANALYSIS AND DESIGN
Part 1. Use Case Realisation for the ‘Record New Tour’ Use Case
Class Diagram
a) Class Diagram is commonly known as static diagrams that represents static view in an
application. For an information system, class diagram is used for visualizing, documenting
various aspects, describing the system, as well as constructing some executable code for the
application that is to be implemented. The attributes and the operations of a particular class are
explained in a class diagram. Main use of class diagram in a system analysis is designing a static
view of the application. It is also used for describing the responsibilities of a system and is
considered as the base of the component as well as deployment of the diagrams.
Document Page
2SYSTEM ANALYSIS AND DESIGN
b) Class Diagram
Figure 1: Class Diagram of the Record New Tour
(Source: Created by author on Enterprise Architect)
c) The above class diagram shows three class for the Record New Tour Use case. The
classes shown in the above diagram is clerical assistants, passenger, and tour leader. Clerical
assistants has attributes and operations defined in the class diagram. There are four attributes that
are included in the clerical assistant class along with six operations. The passenger class has four
attributes and three operations, which defines the passenger class. The Tour Leader class has four
attributes and three operations that are to be included in the class. The operations that the users
will perform are shown clearly in the class diagram. The classes are associated with each other.
Document Page
3SYSTEM ANALYSIS AND DESIGN
The passenger class is associated with clerical assistant class and Tour Leader class. The clerical
assistant maintains all the tour records, drivers, hotels, customer enquiries, payments, invoices,
as well as provides catering establishments. The tour leaders are responsible for planning the
aspects of the tours. There are private variable as well as public variable attributes that are
present in the classes.
Communication Diagram
a) Communication diagram is used for showing the interaction between the users in a
system. It is an interaction diagram that shows about interaction of the objects. Communication
diagram is extension of the object diagram, which shows all objects with messages that travels
from one place to another. The purpose of using communication diagram drawing model
message that passes between the objects or the roles for delivering functionalities of the use
cases and the operations involved. Communication diagram is also used as model mechanism as
the architectural design within the system and also shows the capturing interactions showing the
passes of the messages in between the objects and the roles in the scenario.
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
4SYSTEM ANALYSIS AND DESIGN
b)
Figure 2: Communication Diagram for the new information system of Record New Tour
(Source: Created by author on Enterprise Architect)
c) The communication diagram above shows the communicating process of the system of
Record New Tour System. The above diagram shows about how the communication takes place
within the system. There are three actors who are involved in this system analysis. The actors are
clerical assistants, tour leader, and passenger. Three of them communicate among themselves in
the system to carry out the process. Clerical assistants needs to login their system, edit the tour
details, add new tour, selects the driver as well as looks at the payment that is made by the
passengers. The passengers can view the details of the tour and can select their specific tour. The
passengers can make payment according to the tour selected by them. The tour leader can update
the cost of the tour. The tour leader cannot update the tour details or assign driver for the tour.
Document Page
5SYSTEM ANALYSIS AND DESIGN
The above communication diagram shows the communication process that can be taken place in
the new system of tour.
Part 2. Sequence Diagram for the ‘Record New Tour’ Use Case
a) Sequence diagram is manly used for showing the interactions in between objects in
sequential order by which the interaction occur. A sequence diagram is useful for showing how
communication takes place in a business with all the objects interaction in business. Sequence
diagram is mostly used in a business to know the requirement of the business and also the
communication requirement for implementation of the future system. In the requirement phase,
the analyst can improve the use case of the system. A sequence diagram mainly describes how
the system works and the order of the objects in the system function.
Document Page
6SYSTEM ANALYSIS AND DESIGN
b)
Figure 3: Sequence Diagram for the new information system of Record New Tour
(Source: Created by author on Enterprise Architect)
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
7SYSTEM ANALYSIS AND DESIGN
c) The above sequence diagram shows the sequence of communication that is to be
carried out in the new system of the tour company. As the main function of the sequence diagram
is helping the businesspersons and the software developers for documenting as well as
understanding the requirements of the system that is new or already exists. The above sequence
diagram shows two actors of the new system. The clerical assistants is one of the actor of the
system and the other actor is the passenger. For logging in to the system, the clerical assistant
needs to provide the log in credentials and update the tour details. The tour details are updated by
the database administrator and a feedback message is sent to the actor that the details of the tour
is updated successfully. The passenger also needs to login to the system to view the updated tour
details and make payment according to the updated tour details.
Part 3: Evaluation
CASE tools can also be used for enhancing the productivity of the developers as well as
satisfaction of the developers. The CASE tools involves making the development task of the
system more enjoyable. Using the CASE tool are mainly used to formalize gathering stage of the
requirement, forcing the developers for considering what the developers needs to build. CASE
tools mainly enables system developing that helps to maintain the system easily as well as helps
in easy testing of the system. The quality of the system mainly is improved through the CASE
tool.
The CASE tool inherent many benefits in the CASE tool. Firstly, they allows all the
system engineers in focusing the architecture instead of worrying about the coding. The
requirements of the system can be given by the designers and can also generate code for the
system. CASE tools also supports reverse engineering where the code of the legacy system can
be changed to design some specifications that can be used in restructuring the code, meeting all
Document Page
8SYSTEM ANALYSIS AND DESIGN
the business needs. One of the big advantage of CASE tool is using of CASE tool mainly enables
the organization for implementing design philosophy for the projects, people as well as for the
systems. There are always some standard of development methodology and that is to be followed
by the analyst of the CASE tool. Developers working in different teams helps to utilize the
procedures as well as methods to develop the aspects of project, share the information with all
the development teams. CASE tools mainly have ability for synchronizing model design as well
as implementation. This results in better designing as well as analyzing and there can be more
accurate coding because of procedures such as automatic debugging and automatic testing.
There are many features of CASE tool that are used in engineering system development.
There are number of features that are supported by CASE tools by including feature of
Automated Diagram Support. The features that are supported by CASE tools are checking
syntactic correctness as well as supports data dictionary. CASE tool also checks the consistency
as well as completeness of the system and helps in navigation to the linked diagrams. CASE
tools supports layering of system along with the requirement traceability. The requirement can be
changed along with designing of the system. The CASE tool also helps to generate automatic
report and system simulation. There can also be performance analysis with the help of CASE
tool while developing a system.
There are many analyst as well as researchers hesitant in using the methodologies of pen
and paper. Using of CASE tool mainly helps to fear in control loss in the design phase. The
usability problems that are associated with the CASE tools discourages the initial use and the
continued use. Most of the tools have some substantial curve of learning which takes many
valuable time from the project. With the CASE tool, the cost of the developing the system also
increases.
Document Page
9SYSTEM ANALYSIS AND DESIGN
UML (Unified Modelling Language) mainly looks for a technique that automates the
software production as well as improves the quality as well as reduces the cost as well as time in
the market. The UML technique mainly includes component technology, frameworks, patterns as
well as visual programming. The businesses helps in seeking techniques for managing
complexity of the systems for increasing the scope as well as scale of the software. The UML
mainly provides the users with ready to use model with visual modeling for developing as well
as exchanging the models. The UML also provides extensibility as well as specialization
mechanisms for extending core concepts and is independent for some specific programming
languages as well as development processes. The UML also provides some formal basis that
understands modeling language as well as encourage growth of object oriented tool in the
market. This also supports higher level of development including frameworks, components,
collaborations as well as patterns that is considered as the best practice for system development.
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
10SYSTEM ANALYSIS AND DESIGN
Bibliography
Del Turco, R.R., Di Pietro, C. and Martignano, C., 2018. Designing a multi-layered User
Interface for EVT 2: a development report. AIUCD 2018, p.105.
Frank, U., Atkinson, C., Grossmann, G. and Clark, T., 2016. Designing Models and Systems to
Support IT Management: A Case for Multilevel Modeling. In MULTI@ MoDELS (pp. 3-24).
Hare, E. and Kaplan, A., 2017. Designing Modular Software: A Case Study in Introductory
Statistics. Journal of Computational and Graphical Statistics, 26(3), pp.493-500.
Katayama, T., Urata, S., Ogata, Y., Kita, Y., Yamaba, H., Aburada, K. and Okazaki, N., 2015.
Prototype of a Supporting Tool to Generate Testing Communication Diagram. Journal of
Robotics, Networking and Artificial Life, 2(1), pp.9-12.
Kaur, T. and Sehra, S.K., 2015. Designing and development of database testing
tool. International Journal of Computer Applications, 120(19).
Kounev, S., Huber, N., Brosig, F. and Zhu, X., 2016. A model-based approach to designing self-
aware IT systems and infrastructures. Computer, 49(7), pp.53-61.
Mayan, J.A., Menezes, R.J. and George, M.B., 2016. Designing a Customized Testing Tool for
Windows Phones Utilizing Background Agents. In Proceedings of the International Conference
on Soft Computing Systems (pp. 33-46). Springer, New Delhi.
Pedreira, O., García, F., Brisaboa, N. and Piattini, M., 2015. Gamification in software
engineering–A systematic mapping. Information and software technology, 57, pp.157-168.
Document Page
11SYSTEM ANALYSIS AND DESIGN
Ptak, P., 2018, May. APPLICATION OF THE SOFTWARE PACKAGE LTSPICE FOR
DESIGNING AND ANALYSING THE OPERATION OF ELECTRONIC SYSTEMS.
In Proceedings of the International Scientific Conference. Volume V (Vol. 402, p. 408).
Rumpe, B., 2016. Sequence Diagrams. In Modeling with UML(pp. 191-208). Springer, Cham.
Sahaf, Z., Garousi, V., Pfahl, D., Irving, R. and Amannejad, Y., 2014, May. When to automate
software testing? decision support based on system dynamics: an industrial case study.
In Proceedings of the 2014 International Conference on Software and System Process (pp. 149-
158). ACM.
Vu, T.D., Hung, P.N. and Nguyen, V.H., 2015, December. A method for automated test data
generation from sequence diagrams and object constraint language. In Proceedings of the Sixth
International Symposium on Information and Communication Technology (pp. 335-341). ACM.
chevron_up_icon
1 out of 12
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]