King's Own Institute ICT 103 System Analysis and Design T219 Report

This report presents a comprehensive system analysis and design for the QuickCabs online booking system, employing various UML diagrams to illustrate the system's functionality. The report begins with an introduction outlining the project's objectives, followed by detailed use case descriptions that define the interactions between actors (customers, system administrators, and managers) and the system. Each use case, such as updating personal details, checking taxi availability, modifying taxi information, and updating driver details, is thoroughly described with scenarios, triggers, preconditions, postconditions, and flow of activities. The report then proceeds with visual representations, including a use case diagram, activity diagrams, sequence diagrams, a domain model class diagram, a state machine diagram, and user interface designs for registration, login, checking availability, and booking confirmation. These diagrams provide a clear understanding of the system's architecture and user interactions. The conclusion summarizes the benefits of the new booking system for the company and its customers, emphasizing the ease of use and improved customer experience. The report concludes with a bibliography of cited sources.

Running head: ICT 103 SYSTEM ANALYSIS AND DESIGN T219
ICT 103 SYSTEM ANALYSIS AND DESIGN T219
Name of student
Name of university
Author’s note:

1
ICT 103 SYSTEM ANALYSIS AND DESIGN T219
Table of Contents
Introduction................................................................................................................................3
Use case descriptions.................................................................................................................3
Use case description 1............................................................................................................3
Use case description 2............................................................................................................4
Use case description 3............................................................................................................5
Use case description 4............................................................................................................7
Use case diagram........................................................................................................................9
Activity diagram.......................................................................................................................10
Activity diagram 1................................................................................................................10
Activity diagram 2................................................................................................................11
Activity diagram 3................................................................................................................12
Activity diagram 4................................................................................................................13
Sequence diagram....................................................................................................................14
Sequence diagram 1.............................................................................................................14
Sequence diagram 2.............................................................................................................15
Sequence diagram 3.............................................................................................................16
Sequence diagram 4.............................................................................................................17
Domain model class diagram...................................................................................................18
State machine diagram.............................................................................................................19
User interface...........................................................................................................................20
Conclusion................................................................................................................................23
Bibliography.............................................................................................................................24

2
ICT 103 SYSTEM ANALYSIS AND DESIGN T219
Introduction
QuickCabs is the new online company who intends to offer the facility for booking
and then paying for the taxis online. This report intends to analyse the online booking system
in QuickCabs case study using UML diagrams. The new system would provide the users to
check the availability of taxis online and then make taxi bookings according to their choice.
Use case descriptions
Use case description 1
Use Case name Update personal details
Scenario The existing customers should be able to update their personal details in their
account
Brief description When the customer log in into their account, a functionality is required to be
provided to the customers to update their personal information and save the
details
Actor Customer
Related use case Login, register
Trigger The customer provides their login details in the website of QuickCabs
Primary Scenario 1. The customer login into the website using their credentials
2. Customers click on update personal details in their account
3. Customer provide their new details in the website
Stakeholders Customer, system administrator

3
ICT 103 SYSTEM ANALYSIS AND DESIGN T219
Pre-Conditions Existing customers login into the system
Post-Conditions Personal information has been updated
Exception conditions None
Flow of activities Actor System
1. Customer provide their login
details in the website
2. Customer checks their
personal details in their account
3. Customer provide the new
information in their account
1. System verifies the credentials
of the customer
2. System provide the details of
the customer account
3. System approves the new
details that are provided by the
customer
Use case description 2
Use Case name Check for availability of taxis
Scenario The customer check the availability of taxis in their locality
Brief description The customer (new or existing) check the availability of taxis in their locality
and book taxis from website according to their preferred time
Actor Customer
Related use case Login, register, check availability
Trigger The customer login into the system and then enter their preferred timings for

4
ICT 103 SYSTEM ANALYSIS AND DESIGN T219
booking.
Primary Scenario 1. Customers are successfully signed in into the website
2. Customers enter the booking timing in the form
3. Views the available taxis in the area
Stakeholders Customer, system administrator, manager
Pre-Conditions Customers sign in into the website
Post-Conditions View the details of the available taxis in the locality
Exception conditions None
Flow of activities Actor System
1. Customer provide their login
details in the website
2. Customer enter their preferred
booking timing in the website
3. Views the available taxis in
the area
1. System verifies the credentials of
the customer
2. System provides the list of booking
timings available
3. System displays the list and details
of taxis that are available in that
preferred time slot
Use case description 3
Use Case name Modify information of taxis
Scenario The system administrator updates the details of the available taxis and add

5
ICT 103 SYSTEM ANALYSIS AND DESIGN T219
the details of any new taxi
Brief description When the company has added any new taxis to their inventory, then the
system administrator adds the details of that taxi in the system. The system
administrator could update the details of any existing taxi in their inventory
Actor System administrator
Related use case Login of system administrator, update details of taxis
Trigger The system administrator provide the login details in the system
Primary Scenario 1. The system administrator check the details of the existing taxis in the
inventory of the organisation
2. The system administrator update the details of the taxis available in the
company
Stakeholders
Pre-Conditions System gains a query of the client regarding any product
Post-Conditions Query of the customer has been posted
Exception conditions None
Flow of activities Actor System
1. System administrator login into the system
2. System administrator checks the list of
available taxis in the inventory
3. System administrator adds the details
1. System verifies the credentials
of the admin
2. System displays the list of taxis
available in the inventory of the
company

6
ICT 103 SYSTEM ANALYSIS AND DESIGN T219
of new taxi in the inventory
4. Updates the details of the existing taxi
from inventory
3. Details of taxi are successfully
added
4. Details of taxi are successfully
updated
Use case description 4
Use Case name Update information of drivers
Scenario System administrator updates the details of drivers of the company
Brief description The system administrator login into the system for updating the details of the
drivers of company
Actor System administrator
Related use case Login, check driver details
Trigger The system administrator login into the system and then click of drivers list
Primary Scenario 1. The system administrator checks the details of the appointed drivers of
the company
2. The system administrator updates the details of the appointed drivers of
the company
3. System administrator adds the details of any new driver appointed by the
company
Stakeholders Manager, system administrator, drivers
Pre-Conditions System administrator login into the system

7
ICT 103 SYSTEM ANALYSIS AND DESIGN T219
Post-Conditions Driver details are updated in the system
Exception conditions None
Flow of activities Actor System
1. System administrator login into
the system
2. System administrator checks the
list of available drivers in the
inventory
3. System administrator adds the
details of new driver in the
database
4. Updates the details of the existing
taxi from inventory
1. System authenticates the login
credentials
2. System performs the verification of
the account of user
3. System verifies the details of the
driver and then add to the database

8
ICT 103 SYSTEM ANALYSIS AND DESIGN T219
Use case diagram
Figure 1: Use case diagram
Source: (Created by author)
This image provides the details of all the use cases of the online booking system of
QuickCabs. The main actors of the system are the employee, admin, manager and the
customer. The customer could register in the system, login in the website and then check for
available taxis in the area. The manager could login into the system, check the previous
transactions of the customer, manage the taxis, and manage the driver details. The admin of
the system could login and then modify the taxi details as well as the taxi details of the
organisation. The transactions could be also managed by the admin for making a report of all
the transactions done by the customers of the organisation.

9
ICT 103 SYSTEM ANALYSIS AND DESIGN T219
Activity diagram
Activity diagram 1
Figure 2: Activity diagram of updating personal details
Source: (Created by author)
in this diagram activity of updating the personal details has been provided where the
activities starts when the user provides their login credentials in the system. The system
verifies the login credentials and if the details are correct then access is provided to the
website of the organisation or else the login fails. When the credentials have been verified,

10
ICT 103 SYSTEM ANALYSIS AND DESIGN T219
the user could view the homepage of the company. In this page the account details are
provided in the top section where the customers could enter for updating the personal details.
Activity diagram 2
Figure 3: Activity diagram of checking availability
Source: (Created by author)
In this diagram, the activity checking the availability of the taxis are provided for the
customer. The customer login into the system using the login credentials and the check the
availability of the taxi according to their specifications.

11
ICT 103 SYSTEM ANALYSIS AND DESIGN T219
Activity diagram 3
Figure 4: Activity diagram of modifying the taxi details
Source: (Created by author)
In this image, the activity diagram of modifying the taxi details have been provided.
The system admin could login into the system for checking the taxi details and the updating
the details if it is required. Any new taxi details could be added in the system and if any
changes are required in the existing details of the taxis, the system admin could make the
required changes.