System Requirements Modelling Report for QuickCabs Booking System

This report delves into the process of modelling system requirements, specifically focusing on the development of a booking system for QuickCabs, an online taxi service. It begins by introducing the context and need for a new booking system design to improve management of bookings, customer information, and transactions. The report then explores System Development Life Cycle (SDLC) methodologies, comparing predictive and adaptive approaches, and discussing the waterfall and agile models. The agile model is chosen as the most suitable methodology for this project. The report outlines the process of gathering requirements through surveys, questionnaires, and interviews. It further details both functional requirements, such as software requirement specifications, prototype models, and testing specifications, and non-functional requirements, including reliability, security, usability, performance, and availability. Finally, the report includes a model of the login/register process for the QuickCabs website.

Running head: MODELLING SYSTEM REQUIREMENTS
Modelling System Requirements
Name of the Student
Name of the University
Author note

1MODELLING SYSTEM REQUIREMENTS
Table of Contents
1. Introduction..................................................................................................................................2
2. Methodologies.............................................................................................................................2
2.1 Types of Approach in SDLC.................................................................................................3
2.2 SDLC Methodologies............................................................................................................4
2.3 Waterfall and Agile Model....................................................................................................4
3. Chosen Methodology...................................................................................................................5
4. Gathering Requirements..............................................................................................................5
5. Requirements...............................................................................................................................6
5.1 Functional Requirements.......................................................................................................6
5.2 Non-Functional Requirements...............................................................................................6
6. Modelling Requirements.............................................................................................................8
References........................................................................................................................................9

2MODELLING SYSTEM REQUIREMENTS
1. Introduction
The report discusses concepts in relation with QuickCabs. The online based company
provides user with facilities based on booking and paying for taxi service over the online
platform. Any user registered within the system would be able to search for the taxis that are
available and can be visible within the website (Permana 2015). Users would need to register
themselves within the website where they would be provided with a unique ID and password.
The login information could be used for users to process the further mode of transactions.
In the present context of needs within the business, there is a major need to include a new
form of design for a booking system. With the help of the new design, the system of
management of bookings, handling customer information and dealing with various kind of
transactions would become easy to maintain (Stare 2014). The report would thus discuss about
the use of different form of methodologies while discussing the most suitable methodology that
would help in the development of the system.
2. Methodologies
The defining of the new system would need to be done in a systematic manner. Hence,
the use of System Development Life Cycle (SDLC) would majorly help in developing a proper
system, which would exactly meet with the requirements (Chang, Lee and Chen 2014). The
SDLC comprises of certain activities, which are: planning, designing, implementation of
software coding, testing, documentation, deployment and future maintenance over the code.

3MODELLING SYSTEM REQUIREMENTS
(Figure 1: The SDLC Model)
(Source: Velmourougan et al. 2014)
2.1 Types of Approach in SDLC
There are two forms of SDLC models and approaches that includes:
Predictive SDLC Model – In this model of approach, the planning phase for the entire
project would be made before the development phase over the project. The different kind of
processes that would be involved in the predictive approach includes initiation, planning for the
project, deep analysis over the design approaches, implementation and further deployment.
The usefulness of the predictive approach to SDLC for the designing of the booking
system for QuickCabs is that it would lead to high level of planning approaches (Basri et al.
2016). The predictive approach could be used for developing such applications in which the
product would be understood in an appropriate manner. Thus, the involvement of the customer
would only be made during the changing of scope and at the start of the project.

4MODELLING SYSTEM REQUIREMENTS
However, the limitations of predictive approach that could be determined towards the
development procedure includes the fact that the process is time-consuming. This approach is
also traditional as the processes cannot be processed in a backward direction.
Adaptive SDLC Model – The approach follows a different process as compared to
predictive approach. The approach is highly adaptable in nature in which the environment mainly
evolves with little planning and learning. This approach is dynamic in nature, which further helps
in systematic and proper development of the software as per the needs of the environment.
The usefulness for the approach is that the adaptive nature helps in the addition of new
kind of functionalities that could be included at any step of the process and at any point of time
(Velmourougan et al. 2014). The approach primarily focuses over the implementation procedure
rather than focusing over the functionality.
However, the limitations of this approach is that the customized nature restricts the
feature of re-usability of code. Each of the applications within the software would need to
implemented in a different manner. Based on the lengthy process of development, the exceeding
of budget for the project would be certain.
2.2 SDLC Methodologies
The different kind of methodologies defined within the SDLC are lean, waterfall, agile,
iterative, spiral and DevOps. Based on the requirements for the development of the system, there
are two form of approaches that could be made use of during the phase of development.
2.3 Waterfall and Agile Model
The description of both of the models are discussed below:

5MODELLING SYSTEM REQUIREMENTS
Waterfall Model – This is defined as a traditional model. It can also be defined as a
linear-sequential model in which each of the phases would be completed before the start of the
next phase. This would thus ensure that no overlapping of any tasks would occur over another.
Agile Model – The agile model focuses over the fact that each of the project would be
handled in a different manner. The iterative approach is mainly followed within the development
of software related projects. No kind of detailed planning is mentioned on the future tasks. The
projects defined by the agile model is based on adapting to the requirements of the user and the
system. The product to be developed in tested on a frequent basis with the help of several kind of
iterations.
3. Chosen Methodology
Based on developing the booking system, the agile model could be implemented. This
approach could be used for large scale projects in which many kind of revisions could help in
gaining effective outcomes. During the phase of developing the system, the agile model could
help in including different functionalities that might be implemented at any phase whenever
needed (Stoica et al. 2016). Changes made within the development phase that would be made
with agile approach would rather help in understanding the technical faults that might arise and
thus could be mitigated accordingly.
4. Gathering Requirements
Requirements would need to be gathered would be entirely based on various kind of
methods such as surveys, questionnaires and interviews. The view of various users and other
related taxi drivers would be collected (Davey and Parker 2015). Based on understanding the

6MODELLING SYSTEM REQUIREMENTS
needs of the users, the new specifications based on the business requirements would be discussed
and further implemented.
5. Requirements
5.1 Functional Requirements
The functional requirements defines the different kind of functions performed by the
system or their sub-systems. These might comprise of high-level statements or the type of
function that might be performed within the system. The services of the system are also
described in detail within the requirements.
The functional requirements associated with the development of the new booking system
for QuickCabs includes:
1. Documentation for Software Requirement Specification (SRS)
2. Documentation for the prototype model for the future development process
3. Defining use case models and activity diagrams based on defining the kind of
interaction between the users and system (Raturi et al. 2014).
4. Testing specifications, which includes Integration testing, end-to-end testing and API
testing.
5. Working capability of the system
5.2 Non-Functional Requirements
The non-functional requirements helps in defining certain criteria based on judging the
operations performed within a system rather than focusing over specific behaviours of the

7MODELLING SYSTEM REQUIREMENTS
system. They are thus put in contrast with the functional requirements based on defining specific
functions or behaviours.
The non-functional requirements of the booking system includes:
1. Reliability factors would need to be determined. Any kind of bugs within the code
should be determined during the testing phase.
2. Security requirements based on the type of encryption used within the system would be
discussed. These should be determined as different kind of transactions would be handled by the
system.
3. The usability factors would be considered based on understanding the efficiency,
intuitiveness and workload of the system.
4. The performance factor would also be considered as an important factor based on
understanding the responsiveness and amount of user interactions.
5. The availability of the website to the user at all times for maintaining each of the
necessary operations is another necessary requirement.

8MODELLING SYSTEM REQUIREMENTS
6. Modelling Requirements
(Figure 2: The Modelling of Login/Register for QuickCabs Website)
(Source: Created by author)

9MODELLING SYSTEM REQUIREMENTS
References
Basri, S., Kama, N., Haneem, F. and Ismail, S.A., 2016, December. Predicting effort for
requirement changes during software development. In Proceedings of the Seventh Symposium on
Information and Communication Technology(pp. 380-387). ACM.
Chang, D., Lee, C.K.M. and Chen, C.H., 2014. Review of life cycle assessment towards
sustainable product development. Journal of Cleaner Production, 83, pp.48-60.
Davey, B. and Parker, K., 2015. Requirements elicitation problems: a literature analysis. Issues
in Informing Science and Information Technology, 12, pp.71-82.
Permana, P.A.G., 2015. Scrum method implementation in a software development project
management. International Journal of Advanced Computer Science and Applications, 6(9),
pp.198-204.
Raturi, A., Penzenstadler, B., Tomlinson, B. and Richardson, D., 2014, June. Developing a
sustainability non-functional requirements framework. In Proceedings of the 3rd International
Workshop on Green and Sustainable Software(pp. 1-8). ACM.
Stare, A., 2014. Agile project management in product development projects. Procedia-Social
and Behavioral Sciences, 119, pp.295-304.
Stoica, M., Ghilic-Micu, B., Mircea, M. and Uscatu, C., 2016. Analyzing Agile Development-
from Waterfall Style to Scrumban. Informatica Economica, 20(4).
Velmourougan, S., Dhavachelvan, P., Baskaran, R. and Ravikumar, B., 2014, September.
Software development Life cycle model to build software applications with usability. In 2014

10MODELLING SYSTEM REQUIREMENTS
International Conference on Advances in Computing, Communications and Informatics
(ICACCI) (pp. 271-276). IEEE.