ICT103 - System Analysis and Design: QuickCabs Report

This report provides a comprehensive system analysis and design for QuickCabs, an online cab booking company. The analysis includes requirement modeling, focusing on functional and non-functional requirements, and the selection of an adaptive methodology from the SDLC approach. The report details methodologies, advantages, and disadvantages of both predictive and adaptive models. It outlines requirement-gathering techniques like interviews and questionnaires. The functional requirements encompass customer input, trip and transaction recording, and account number verification. Non-functional requirements emphasize system robustness and availability. The report concludes with an activity diagram illustrating the cab payment use case, along with a bibliography of referenced sources.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of Student-
Name of University-
Author’s Note-

1SYSTEM ANALYSIS AND DESIGN
Introduction
For conducting the requirement modelling for this assessment, the case study that is
considered for this is an online cab booking company known as QuickCabs. This cab booking
company provides customer service to book cabs and pay for the fares online. The customer
associated with the online cab booking company makes online payment for the service they take
from the company.
As a system analyst, proper business plan is to be made for developing the requirement
modelling of the system. This modelling will be used for developing the online site of
QuickCabs. The project is to be developed with the project management technologies and
methodologies that would help to complete the project successfully.
Methodologies
The SDLC approach of project development includes a process that is basically used by
software industries. This approach is used for designing the product, developing as well as
testing the software that are f high quality. The main process that SDLC provides is produce a
software of high quality that helps to meet the expectation of the customer or exceeds the
expectation of the customers (Abrahamsson et al. 2017). This approach also helps to complete
the project in time and within the estimated cost of the project. There are two types of models in
SDLC, predictive model and adaptive model. Both the models with their advantages and
disadvantages are explained in the section below:
Predictive model: This is the traditional model and is known as sequential model. This
model includes linear flow of development for the software application. This process includes a
set of finite stages that is to be completed fully before moving on the next step or process. The

2SYSTEM ANALYSIS AND DESIGN
approaches that are included in waterfall model includes requirements, design, execution, testing
as well as release of the project.
Advantages: This model is a structured model and this is very easy to follow. The
activities in this model are properly defined and includes careful planning of all the projects.
There are specific deliverables at all the stages included in the process.
Disadvantages: This approach does not all the developer to go back to the previous stages
once it has been completed. This project provides flexibility for adjusting the scope of the
project. This predictive model is more expensive compared to all other methodologies included.
Predictive model: This model is iterative model that have evolved through collaboration
between all the teams. This predictive model is a dynamic model as well as iterative model that
works in sprints and included defined duration for completing the project. This model provides
lightweight deliverables that reduces time for the software that is released (Lewis 2017). This
model also includes adaptive planning, early delivery of the project, continuous development of
the project, flexible responsiveness for the changes that are required.
Advantages: Provides software of high quality that includes many iterations for the
project. This model helps to deliver the project in least possible amount of time. This project
includes deep involvement of client and provides flexibility for completing the project. This
methodology includes high collaboration degree between the teams and between all the parties
involved in the project.
Disadvantages: This model mainly requires specialized developers to complete the
project. This project is to be maintained by experts and includes many set of skills for

3SYSTEM ANALYSIS AND DESIGN
completing the project. This model is challenging when comes to scaling projects and includes
constant refactoring for the changes.
Chosen Methodology
The methodology that can be used for developing the system of QuickCabs is adaptive
methodology of project development. This project can develop the priority requirement first for
completing the project. This project includes initial delivery of the project faster compared to any
other methodologies. The customers with this methodology includes functionality early. This
includes lower delivery cost and helps to release the increment of the project. Customers in this
model can provide feedback for product development and helps to avoid changes at the end of
the project.
Requirement Gathering
Interviews: This is a tool that can be used at beginning of the process so that the
background information related to the business problems can be solved. This includes
understanding the world from perspective of system that is being developed. Interviews can be
carried out with the stakeholders to achieve a particular function.
Questionnaires: Questionnaires helps the researchers to provide latent requirement as
well as features for the system (Giachetti 2016). This can be chosen carefully and includes
probing questions. Specific drill down can be recorded for completing the project successfully.
Use Case and Scenarios: For the high level functions include din the requirement of the
system, use case helps to complete the project successfully. This helps to gather data from all the
developers in the project.

4SYSTEM ANALYSIS AND DESIGN
Requirements
The functional requirements that are included in the system are:
1. The system will be capable of taking input from the customers. The details of the customer
will be captured in the database of the system.
2. The system will record all the details of the trips in the database.
3. The system will be capable of storing the transaction details in the system.
4. The system will ask the users to provide their account numbers.
5. The system will provide their user and
The non-functional requirement that are included in the QuickCabs system includes:
1. The system is expected to be robust.
2. The system will be available to the users all the time.
3. The system will accept all the data that are provided by the user.

5SYSTEM ANALYSIS AND DESIGN
Requirement Modelling
Figure 1: Activity Diagram of cab payment use case
(Source: Created by author on Visio)
Conclusion
It can be concluded from the above discussion that the designing of the new system for
the QuickCabs can be done with proper implementation of project management technologies as
well as project management methodologies for completing the project. The above project shows
the methodologies that could be applied for completing the project successfully. There are two
types of methodologies that are included in life cycle of the project. This project could have been
completed with implementing the methodologies that are included in the project development
life cycle. For designing a project, there is need to gather the requirements of the project. Many
data gathering requirements are available that states different processes to gather the data for the

6SYSTEM ANALYSIS AND DESIGN
project. All those data gathering document can be used for gathering the data related to the
online system included in the system. This report also defines the functional as well as non-
functional requirement for the system that is being developed for the QuickCabs.

7SYSTEM ANALYSIS AND DESIGN
Bibliography
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Lewis, W.E., 2017. Software testing and continuous quality improvement. Auerbach
publications.
Stark, J., 2015. Product lifecycle management. In Product lifecycle management (Volume 1) (pp.
1-29). Springer, Cham.
Giachetti, R., 2016. Design of enterprise systems: Theory, architecture, and methods. CRC
Press.
Mac Ginty, R. and Williams, A., 2016. Conflict and development. Routledge.
Iqbal, U. and Bajwa, I.S., 2016, August. Generating UML activity diagram from SBVR rules.
In 2016 Sixth International Conference on Innovative Computing Technology (INTECH) (pp.
216-219). IEEE.
Chaudhuri, A., 2016. Randomized response and indirect questioning techniques in surveys.
Chapman and Hall/CRC.
Mihas, P., 2019. Qualitative data analysis. In Oxford Research Encyclopedia of Education.