Systems Analysis and Design Report: QuickCabs Online System

This report presents a Systems Analysis and Design for QuickCabs, an online organization. It begins with an introduction to system analysis and the case study, detailing the need for a new system that allows users to book and pay for services, while also allowing administrators to manage information. The report then explores various methodologies, including the System Development Life Cycle (SDLC), predictive and adaptive approaches, and focuses on the Spiral Model as the chosen methodology. It covers requirement gathering, functional and non-functional requirements, and requirement modeling using activity diagrams. The report concludes by summarizing the key aspects of system analysis and design, highlighting the processes and methodologies used for developing the QuickCabs online system. References from various books and journals are included for further reading.

Systems Analysis
And
Design

Table of Contents
INTRODUCTION...........................................................................................................................1
Methodologies..................................................................................................................................1
SDLC (System Development Life Cycle)...................................................................................1
Predictive approaches..................................................................................................................2
Adaptive approaches...................................................................................................................3
Chosen Methodology.......................................................................................................................3
Spiral Model................................................................................................................................3
Requirement gathering................................................................................................................3
Requirements...............................................................................................................................3
Requirement Modelling..............................................................................................................4
Conclusion.......................................................................................................................................5
References........................................................................................................................................6

INTRODUCTION
System analysis refers to process of scrutinising business or processes for identification
of their goals along with their purpose for creation of procedures and systems for attaining them
within effectual manner (Dennis, Wixom and Roth, 2018). It is associated with analysis of
requirements for assisting decision makers for identification better actions that have been carried
out.
The case study is based on QuickCabs which is a online organisation and renders their
employees to book as well as pay for services. Individual can look forward for taxis within
website and when bookings are made the details of customer will be checked to identify whether
they are existent or new. Unique ID along with password will be provided to new customers for
carrying out their transactions. Being a system analyst the system must be designed in such a
way that new customers can be added and transactions related with same must be carried out. In
addition to this, there needs to be an option with an administrator for adding, deleting or
modifying information related with taxis and driver.
Methodologies
SDLC (System Development Life Cycle)
A conceptual model that comprises of procedures as well as policies for development of
altering systems within their life cycles is referred to as SDLC (Dennis, Wixom and Tegarden,
2015). Basically, it renders framework for technical as well as non-technical activities for
delivering quality systems for meeting or exceeding expectations for managing decision making.
QuickCabs can utilise its phases for breaking down their system or formulate new as per the
information. These stages are illustrated below: Planning or feasibility study: In this the problem will be defined for an instance with
respect to QuickCabs, administrator needs to alter details associated with taxis or driver.
This denotes there is scope for improvisation in their existing systems. The objectives of
defined system must be clarified so that there must be an overview of all the aspects
which have to be performed. Security aspects must also be taken into consideration by
system analyst and at the end feasibility report must be created (System Development
Life Cycle, 2019).
1

 Analysis and specification: In this case, system analyst is supposed to gather details from
their customer on the basis of their requirements and also the needs of firm must be taken
into account. Then that information must be validated so that wants can be prioritised. As
per this, system goals must be enhanced and software requirement specification
document must be build up which contains all the needs related with hardware, software,
network and functional requirements at the end of this specified stage. System Design: It comprises of network, system, design of applications, database & user
interface. In this system analyst of QuickCabs is liable for transforming SRS document
within logical structure as it comprises of complete as well as detailed set of
specifications by the usage of programming languages (Giurgiutiu and Lyshevski, 2016).
The proposed design must be reviewed and ensured that all the requirements specified
within SRS document of system analyst have been addressed. Implementation: The system analyst within QuickCabs is responsible for designing by
the usage of coding. Like an online system will be formulated by which customers can
carry out their bookings as well as alterations can be carried out by administrator as per
requirements. All the modules will be integrated for detecting bugs. By the test plan, test
report will be prepared that will be containing errors.
 Support/Maintenance: It comprises of activities like physical on-site or phone call
support for users when they are installing it on their devices (Jiang and et. al, 2015).
Implementation of alterations within software which it undergoes within specified period
of time along with this residual errors will be handled.
Predictive approaches
The approach which makes assumption with respect to development of project that can
be organised as well as planned in an advance and can be developed accordingly is referred to as
predictive approach. The advantage of this is that system analyst can develop them within
predetermined plan as well as in this deviations are not allowed. In addition to this, developers
need to identify requirements in advance (System Development Life Cycle (SDLC), 2015). Their
disadvantages are that design needs to completely specified before they are being programmed,
it is not easy to design a system entirely without any kind of programming. In this case, system
analyst of QuickCabs can make use of waterfall model and parallel method.
2

Adaptive approaches
The approach that is more flexible and assumes that project is not planned entirely in
advance so that relevant modifications can be carried out while it is in progress is referred to as
adaptive approach. But still some of the requirements must be identified by system analyst of
QuickCabs after preliminary development has been carried out (System Development Life Cycle
(SDLC), 2015). The advantage of such kind of approach is that it enables developer along with
client to acknowledge requirements. For risk reduction mechanism prototyping is being used.
The disadvantages of using this is that it involves lots of time for development of system.
Chosen Methodology
Spiral Model
The accumulation of both prototype and sequential model which comprises of continuous
enhancements refers to spiral model. There are specified activities that are being carried out
within one spiral and same is carried out until it is completely build up (Martinez, Correia and
Viegas, 2015). The system analysts of QuickCabs have opted to make use of Spiral Model.
Reason behind this is that, by this development can be carried out quickly as well as it is handled
within a strategic manner. In addition to this risk is evaluated in an appropriate and systematic
manner. It will also provide system analyst of QuickCabs to have feedback from customers and
make changes accordingly.
Requirement gathering
It is crucial for a system analyst to analyse needs of their customers so that system can be
developed in accordance to that. For this, it is necessary that required information must be
gathered, it can be done by making use of interview. For an instance of 10 individuals so that
information can be acquired from different perspectives. It will assist system analyst of
QuickCabs to formulate system according to their needs.
Requirements
Functional requirements of online cab includes that system will validate automatically
the registered users, only top level authorities of QuickCabs have access to transactions that are
being made as well as it must be merged with banking API. Non-functional requirements,
customers must change the password after it has been used initially and unsuccessful attempts
3

must be recorded in along with this,there needs to be capability of system for handling large
request (Giurgiutiu and Lyshevski, 2016).
Requirement Modelling
Activity diagram describes the way in which activities are being carried out at diverse
levels of abstraction.
4
Illustration 1: Activity Diagram

For an instance the activity diagram for QuickCabs have been provided above in which
user has different options as per their requirements and book cab along with this make payment
accordingly.
Conclusion
From above it can be concluded that, system analysis refers to scrutiny of condition for
development of system solution. The SDLC comprises of different phases which can be utilised
while development of system and depending upon requirements models are used. In addition to
this, there exists different methods for gathering of information from different sources either
through interview or questionnaires. Activity diagram depicts the entire flow of information and
ways in which data is transferred.
5

References
Books & Journals
Dennis, A., Wixom, B. H. and Roth, R. M., 2018. Systems analysis and design. John wiley &
sons.
Dennis, A., Wixom, B. H. and Tegarden, D., 2015. Systems analysis and design: An object-
oriented approach with UML. John wiley & sons.
Giurgiutiu, V. and Lyshevski, S. E., 2016. Micromechatronics: modeling, analysis, and design
with MATLAB. CRC Press.
Jiang, X. and et. al, 2015. Large-scale taxi o/d visual analytics for understanding metropolitan
human movement patterns. Journal of Visualization. 18(2). pp.185-200.
Martinez, L. M., Correia, G. H. and Viegas, J. M., 2015. An agent‐based simulation model to
assess the impacts of introducing a shared‐taxi system: an application to Lisbon
(Portugal). Journal of Advanced Transportation. 49(3). pp.475-495.
Online
System Development Life Cycle. 2019. [Online]. Available through:
<https://www.tutorialspoint.com/system_analysis_and_design/system_analysis_and_des
ign_development_life_cycle.htm>.
System Development Life Cycle (SDLC). 2015. [Online]. Available through:
<https://techblogmu.blogspot.com/2017/04/system-development-life-cycle-sdlc.html>.
6