London Metropolitan University, Faculty of Computing

CS6003ES Advanced Software Engineering

Coursework Assignment, Semester 2 (part 2), 2023/24
Module Leader: Mrs. Yamuna Nawarathne

Part 2 weighting: 30% in total

STUDENT ID NUMBERS: _______ 23042026___________________________

NAMES_________Thenura Rehan Bandara Wijekoon________

_____________________________________________

Submission deadline:

To submit at the module Weblearn with all documents to your

tutor

The electronic version of your individual report must indicate ID number, Surname and First name in
the first page or at the beginning of program file (as comments).

If you think there is a good reason for late submission, such as illness, and you have supporting documentary
evidence then you should follow the “mitigating circumstance” procedures outlined in the Red Book, otherwise
assignments will NOT be accepted by the module Organizer after the due date.

PLAGIARISM

You are reminded that there exist regulations concerning plagiarism. Extracts from these regulations
are printed overleaf. Please sign below to say that you have read and understand these extracts:

(Signature:)__________________________Thenura___________________________________
Acknowledgement

We sincerely thank each and every team member for their commitment and diligence in helping
the City Taxi software project succeed. Their dedication and knowledge have been crucial in
helping us provide our client with a high-caliber solution. We would especially want to thank
Mrs. Yamuna for her guidance and encouragement during the project, which have been crucial to
our success.

Table of Contents
Introduction...............................................................................................................................................4
Chapter 01..................................................................................................................................................4
1.1 Generic plan information................................................................................................................4
1.1.1 Document standard..................................................................................................................4
1.1.2 Acronyms...................................................................................................................................5
Chapter 02..................................................................................................................................................7
2.1 System overview...............................................................................................................................7
2.2 Purpose.............................................................................................................................................7
2.3 Scope.................................................................................................................................................8
2.4 Objective...........................................................................................................................................8
2.5 Assumptions and constraints..........................................................................................................9
2.5.1 Assumptions of the project.......................................................................................................9
2.5.1 Constraints of the project.........................................................................................................9
2.6 Project deliverables.......................................................................................................................10
2.6.1 Project deliverables to the client............................................................................................10
2.6.2 Project deliverables on phases...............................................................................................10
2.7 Project Schedule............................................................................................................................12
2.8 Budget summary............................................................................................................................13
Chapter 03................................................................................................................................................13
3.1 Organizational structure...............................................................................................................13
3.1.1 selected organization structure..............................................................................................13
 3.2 Project team...................................................................................................................................14
3.2.1 Team structure description....................................................................................................14
3.2.2 Team responsibility.................................................................................................................15
Chapter 04................................................................................................................................................16
4.1 Work Breakdown structure..........................................................................................................16
4.2 WBS for system..............................................................................................................................17
4.3 Rationale for WBS.........................................................................................................................17
4.4 Gantt Chart....................................................................................................................................18
4.5 Gantt chart for system...................................................................................................................19
4.6 Rationale for Gantt chart..............................................................................................................21
4.7 Project Milestone...........................................................................................................................21
4.8 Rationale Milestone.......................................................................................................................22
4.9 Activity Network diagram...........................................................................................................24
4.10 Activity Network diagram for System........................................................................................27
4.11 Critical Path of Project................................................................................................................27
Chapter 05................................................................................................................................................27
5.1 Project Maintenance......................................................................................................................27
Conclusion................................................................................................................................................28

List of tables

Table 1 acronyms........................................................................................................................................6
Table 2schedule.........................................................................................................................................12
Table 3budget summary............................................................................................................................13
Table 4team structure...............................................................................................................................15
Table 5team responsibility........................................................................................................................15

List of Figures
Figure 1wbs...............................................................................................................................................17
Figure 2gantt chart....................................................................................................................................20
Figure 3network diagram..........................................................................................................................27
Introduction
In their capacity as Project Manager for the creation of City Taxi (PVT) Ltd.’s innovative online
cab reservation system, they are responsible for spearheading a significant change aimed at
increasing operational effectiveness and improving consumer happiness in the urban
transportation industry. This program demonstrates City Taxi's steadfast commitment to
providing quality, convenience, and dependability through innovation in technology. The goal is
to create an intuitive booking system that benefits both devoted drivers and esteemed passengers.
This project aligns with City Taxi's long-standing goal of enhancing the passenger experience
from booking to drop-off, solidifying its position as a leader in offering cutting-edge, customer-
focused transportation options in Sri Lanka.

In their effort to modernize urban mobility in Sri Lanka, City Taxi (PVT) Ltd. has achieved a
major milestone with the establishment of a web-based taxi reservation system. This initiative
intends to streamline the booking process through the integration of cutting-edge technical
solutions, thereby promoting a smooth communication channel between drivers and passengers.
This calculated action aims to strengthen City Taxi's position as a pioneer in implementing
cutting-edge, customer-focused transportation technologies while increasing operational
effectiveness. The aspiration is to set a new standard for urban transportation and maintain City
Taxi's forefront position in technical advancement in the sector.

Chapter 01
1.1 Generic plan information
1.1.1 Document standard
• Date of Issue & Status: 10/04/2024, Draft/Final
• Issuing Organization: Maze Technologies
Document conventions

• The entire document is to be justified.

• Text line spacing is set to 1.5.
• References are formatted according to the Harvard citation style.
• Main Titles:
- Font: Times New Roman
- Style: Bold
- Size: 40

• Subtitles:
- Font: Times New Roman
- Style: Bold
- Size: 20

• Body Text:
- Font: Times New Roman
- Size: 12

1.1.2 Acronyms
A brief list of acronyms that are used in the project documentation so that all stakeholders may
comprehend it clearly and easily.

Acronym Definition
PM Project Management/Manager
WBS Work Breakdown Structure
SRS System Requirement Specification
 Acronym Definition
SDLC Software Development Life Cycle
Table 1 acronyms

Glossary

• Agile Methodology: A project management and software development approach

emphasizing incremental delivery, team collaboration, continual planning, and learning.
• CI/CD (Continuous Integration/Continuous Deployment): Automates app delivery stages
for frequent releases.
• SDLC (Software Development Life Cycle): Process for planning, creating, testing, and
deploying software systems.
• SRS (System Requirements Specification): Describes software or system functions,
features, and limitations.
• Backend: Manages database transactions, authentication, and application logic on the
server-side of a web application.
• Frontend: Collects user input, processes it, and presents results on the client-side of a web
application.
• MVC (Model-View-Controller): Separates applications into model, view, and controller
components.
• CRUD (Create, Read, Update, Delete): Basic functions of persistent storage like
databases.
• API (Application Programming Interface): Specifies how software components should
interact.
• SaaS (Software as a Service): Distributes software hosted by a third-party over the
Internet.
• Stakeholder: Individual, team, or organization interested in project success.
• UI (User Interface): Human-computer interaction point, like the screen, keyboard, and
mouse.
• UX (User Experience): Overall experience of using a product, focusing on ease and
pleasure.
 • WBS (Work Breakdown Structure): Hierarchical decomposition of project scope into
deliverables.

Chapter 02
2.1 System overview
Since City Taxi (PVT) Ltd, a Sri Lankan company committed to providing high-quality,
reasonably priced transportation options to middle-class consumers, the City Taxi Management
System is a revolutionary step. In order to improve client happiness, increase operational
efficiency, and maintain the company's competitive advantage in the rapidly changing
transportation industry, this web-based reservation system was created. The system has a number
of cutting-edge features, such as automatic fare calculation, online booking, real-time driver
tracking, and user-friendly interfaces for administrators, drivers, and passengers.

The project was created to address and correct the inefficiencies of the current manual
reservation system, with the dual goals of expediting the reservation process and demonstrating
leadership in customer-centric transportation solutions. The initiative intends to use cutting-edge
technology to make bookings easier and more efficient, promote better communication, and
guarantee a smooth and excellent experience for passengers from booking to drop-off. Utilizing
cutting-edge technologies like MongoDB, React, Node.js, and Express.js, the system is designed
to satisfy customers' needs while abiding by rules and industry norms. Features like real-time
location monitoring, a dynamic list of available drivers, safe online payment processing, and
extensive reporting and analytics for ongoing service improvement are all supported.

With an eye toward the future, the system is ready for more improvements that should improve
the services it offers. These include of the addition of ride-sharing features, real-time emergency
support, predictive analytics for peak demand hours, loyalty programs, support for several
languages, interaction with public transit, and the application of augmented reality to enhance
customer experience.
2.2 Purpose
The goal of the City Taxi Management System is to bring the Sri Lankan transportation company
City Taxi (PVT) Ltd.’s reservation procedure up to date. By providing features including online
booking, real-time driver tracking, automated payment computation, and user-friendly interfaces
for passengers, drivers, and administrators, the system seeks to increase customer happiness,
improve service efficiency, and preserve a competitive edge. By utilizing cutting-edge
technologies like MongoDB, React, Node.js, and Express.js, it aims to satisfy the ever-changing
demands of the urban transportation sector while maintaining industry norms and laws and
offering a smooth user experience.

2.3 Scope
The aim of the project for City Taxi (PVT) Ltd is to set up a sophisticated, user-friendly online
reservation system. Through this program, booking cabs will be made easier, passenger-driver
interactions will be improved, driver scheduling will be efficiently managed, and a feedback
system will be implemented. Additionally, it will make use of geolocation technology,
streamline the invoicing procedure, and enable integration with reservations made over the
phone. The system will also include advanced reporting and analytical capabilities, real-time taxi
tracking, and features that can expand with the business. It will also enhance overall customer
support skills. The goal is to provide a comprehensive solution that streamlines the taxi booking
process for drivers and riders alike, with an emphasis on efficiency and quality while providing
excellent transportation services.

2.4 Objective
The objectives of the web-based reservation system project for City Taxi (PVT) Ltd are as
follows:

• Taxi reservation processes for registered and telephone-operator-assisted bookings.

• Improve communication with real-time updates, including SMS notifications.
• Ensure a secure and straightforward user registration process.
• Implement a passenger rating system for continuous service improvement.
 • Utilize geolocation services to display available drivers closest to the passenger's
location.
• Develop an automated payment calculation system for convenient transactions.
• Seamlessly integrate the telephone operator reservation option with system records.
• Automate driver location tracking for real-time updates.
• Implement a reporting system for performance analysis and optimization.
• Calculate the estimations of distances and duration
• Generate comprehensive reports and charts
• Provide filtered key information on respective dashboards.

2.5 Assumptions and constraints

2.5.1 Assumptions of the project
A few assumptions of the web-based reservation system project for City Taxi (PVT) Ltd are given
below.

• User Adaptability: Assumes users will quickly adapt to and embrace the new technology-
based reservation system.
• Technological Infrastructure: Presumes the existence of a robust technological setup for
features like geolocation and real-time tracking.
• Demand for Convenience: Infers a significant user demand for improved booking
efficiency and convenience.
• Privacy and Security: Assumes compliance with stringent data security and privacy
standards to protect user information.
• System Scalability: Suggests the system is designed to accommodate future growth in
user numbers and transaction volume efficiently.
• Continuous Improvement: Assumes a commitment to leveraging user feedback and data
analytics for ongoing service enhancement.

2.5.1 Constraints of the project

A few constraints of the web-based reservation system project for City Taxi (PVT) Ltd are given
below.
 • Internet Dependence: The system's functionality hinges on continuous, reliable internet
access for both passengers and drivers.
• Technological Literacy: Assumes a baseline level of technological literacy among users,
potentially excluding non-tech-savvy individuals.
• Hardware Requirements: Users must have access to smartphones or computers, which
could limit access for those without such devices.
• Geolocation Accuracy: The effectiveness of real-time tracking and driver location
features depends on the accuracy of geolocation services.
• Payment Processing: Relies on third-party payment gateways, which may introduce risks
related to transaction security and reliability.
• System Maintenance: Requires ongoing technical support and updates, presenting
potential downtime or disruptions during maintenance periods.

2.6 Project deliverables

2.6.1 Project deliverables to the client
The deliverables related to the client of the web-based reservation system project for City Taxi
(PVT) Ltd are as follows:

• Software Model (Use Cases)

• Requirements Analysis Report (Functional and Non-functional)
• Technical Documentation Analysis
• System Design (Diagrams, Components, Classes, Database Model)
• System Prototype
• Test Case Documentation
• User Manual
• Completed Software Product
• Evaluation Report

2.6.2 Project deliverables on phases

Planning Phase:

• Project Plan
 • Requirements Specification

Design Phase:

• System Design Overview

• Design Blueprints
• Database Model
• UI Prototypes

Development Phase:

• Software Prototype
• Pilot Release

Testing Phase:

• System Testing (System testing, Integration testing, etc.)

• User Acceptance Testing Results

Deployment Phase:

• Final System Release

• Deployment Plan

Post-Deployment Phase:

• User Training Materials

• Maintenance and Support Plan
 2.7 Project Schedule

Table 2schedule

Week Date Phase Activities

(No.)
1 Dec 1 - Dec Project Initiation Stakeholder meetings and project charter signing
5
2 Dec 6 - Dec Requirements Requirements gathering and analysis
12 Phase
3 Dec 13 - Dec Design Phase System architecture and database design
19
4 Dec 20 - Dec Design Phase UI/UX design and prototype development
26
5 Dec 27 - Jan Development Backend development (APIs, server logic)
2 Phase
6 Jan 3 - Jan 9 Development Frontend development (React components, UI
Phase integration)
7 Jan 10 - Jan Development Integration of frontend with backend and testing
16 Phase
8 Jan 17 - Jan Testing Phase Continued integration testing and performance
 23 testing
9 Jan 24 - Jan Testing Phase Completion of testing and system refinements
30
10 Jan 31 - Feb Deployment Phase Deployment preparations and User Acceptance
6 Testing (UAT)
11 Feb 7 - Feb Deployment Phase Final system deployment and user training
13
12 Feb 14 - Feb Post-Deployment Post-deployment reviews, documentation
20 finalization

2.8 Budget summary

Team Member Role Hourly Rate (£) Hours Total Cost (£)
Project manager Project management 24 270 6,750
Full-time Member 1 Senior Developer 50 540 27,000
Full-time Member 2 UI/UX Designer 50 540 27,000
Full-time Member 3 QA Engineer 35 540 18,900
Part-time Member 1 Software Architect 35 270 9,450
Part-time Member 2 Support Engineer 35 270 9,450
Total 98,550
Table 3budget summary

Chapter 03
3.1 Organizational structure
3.1.1 selected organization structure

Project Manager
3.2 Project team
3.2.1 Team structure description
The City Taxi Management System project uses a more streamlined organizational structure to
improve communication and collaboration. The project sponsor is in charge and sets the strategic
direction for the endeavor. The project manager carefully plans all the operational details. The
project's core group consists of a QA Engineer, a UI/UX Designer, and a Senior Developer who
work closely together. To provide tailored assistance, there are also positions for specialized
support. It is essential that stakeholders actively participate in order to ensure that the system is
customized to meet their needs.

In order to meet project objectives on schedule, the organizational structure of the City Taxi
Management System project skillfully combines technical know-how with strategic control. The
initiative is led by a part-time Project Manager who maintains a distance from the development
operations in order to concentrate on thorough coordination. The three full-time professionals
working on software development, UI/UX design, and quality assurance are the project's
lifeblood; they guarantee consistent progress and adherence to strict guidelines. Two part-time
professionals that provide technical support and architectural insights to meet the project's
evolving needs further enhance the dynamism within the team. This configuration creates a
collaborative, fruitful atmosphere that combines various skills with the project's objectives,
enabling its successful completion.
 Role Name Contribution Qualification
Project Manager Thenura Wijekoon Oversee all the project Project manager with 3 experience
progress and manage the in software development, possessing
all the project phases. a PMP certification and specializing
in Agile methodologies.

Senior Developer Sahiru Bodehewa The senior developer Has been a full stack developer for
contributes by providing over 6 years in various companies in
technical leadership and the industry.
providing solutions to
problems.
UI/UX Designer Thimeth Bolabotuwa Designing the user Has 3 years of experience in UI/UX
interface, prototypes, designing for local business projects
wireframes
QA engineer Ramesh Dhanapala Plan and conduct test Has 4 years’ experience in QA
activities, identify defects engineering in the industry.
and ensure product quality.
Software Architect Bhanuka Rathnayake Guided the team on system Has 2 years of experience in the
architecture, guarantee the industry. Has been involved in
system robustness. several major projects during that
period.
Support Engineer Jason Nawarathna Provide technical support Has 1 and half of years of
and perform ongoing experience in the industry as a
system maintenance and backend developer.
updates.
Table 4team structure

3.2.2 Team responsibility

Role Duties
Project Manage all project phases from inception to completion, facilitate communication among team members
Manager and stakeholders, and oversee scheduling and resource allocation.
Senior Spearhead the development process, crafting both client-side and server-side architecture, and validate the
 Role Duties
Developer technical feasibility of UI/UX concepts.
UI/UX Conceptualize and design the user interface and experience, develop prototypes and wireframes, and work
Designer closely with developers for design implementation.
Plan and conduct testing activities, pinpoint and document software defects, ensure product quality
QA Engineer standards are met, and handle user acceptance testing.
Software Offer guidance on system architecture, guarantee system robustness and efficiency, and provide direction
Architect on technical approaches.
Support Provide technical support following deployment, address technical queries, and perform ongoing system
Engineer maintenance and updates.
Table 5team responsibility

Chapter 04
4.1 Work Breakdown structure

A software project's entire scope is arranged into a comprehensive framework of phases, tasks,
and assignments using a Work Breakdown Structure (WBS) that complies with ISO 12207-2008.
Through adherence to this standard, the project's goals, salient features, and work packages are
closely connected to the designated procedures for overseeing the software lifetime, including
creation, use, upkeep, and disposal. By providing a clear path to achieve the established
requirements, the WBS supports precise project planning, execution, supervision, and
completion.
4.2 WBS for system

Figure 1wbs

4.3 Rationale for WBS

The City Taxi Management System Project’s Work Breakdown Structure (WBS) is a detailed
project plan that complies with ISO 12207-2008's strict guidelines. It ensures that every stage of
the software lifecycle is well-planned and documented. The project is broken down into specific
tasks by this WBS, which makes it possible to clearly assign roles, allocate resources
appropriately, and create accountable schedules for each team member. This paradigm, created
to demystify complicated procedures, maximizes work flow and increases team cooperation.
The WBS also includes the supervision of non-technical components, such as risk assessments
and stakeholder interactions, ensuring that any roadblocks are identified and addressed in
advance. With its comprehensive scope, the WBS serves as a communication tool as well as a
project tracking tool, making the progress and outcomes of the project evident to all stakeholders
involved.
In this framework, duties are methodically laid out to cover a wide range of activities –
beginning with the basic architectural planning, progressing through the complex stages of
UI/UX design, and ending with the crucial stages of development and integration.
Comprehensive testing procedures are the next step in this painstaking attention to detail, and
they are crucial to guaranteeing quality and producing a finished product that can be relied upon.

Through careful task alignment with the project's overall objectives and ISO standards, the work
breakdown structure (WBS) creates an environment that is favorable to successful project
completion. This alignment guarantees that the City Taxi Management System project will be
finished within the allotted budget, on schedule, and in compliance with its specified scope.
Consequently, it establishes a strong foundation for the provision of a software solution that not
only fulfills but also precisely tailors to the requirements of its end customers. Furthermore, the
implementation of a structured approach to project management highlights the significance of
strategic planning and compliance with international standards, so augmenting the likelihood of
project success and guaranteeing the ultimate product's dependability and efficiency in fulfilling
user requirements.

4.4 Gantt Chart

The Gantt chart that has been presented effectively illustrates the project timetable from
December 4, 2023, to February 27, 2024, adhering to ISO 12207-2008 standards. Planning,
design, testing, and deployment are all well-defined, guaranteeing an organized, quality-focused
approach to software development. Every activity, including system design and stakeholder
management, reflects the standard's focus on methodical, disciplined processes. The delivery of a
high-quality software product is facilitated by this visual planning tool, which helps with
progress tracking, quality standard alignment, and effective resource management for the project.

4.5 Gantt chart for system

Figure 2gantt chart
4.6 Rationale for Gantt chart

In order to manage software development projects in accordance with ISO 12207-2008

standards, a Gantt chart is necessary. By providing a visual representation of the project timeline
from start to finish, it helps stakeholders better comprehend and agree on the project's scope and
timing. This clarity is essential for tracking task progress against scheduled completion dates and
making sure the project stays on schedule. Another important advantage is efficient resource
management, which is made possible by the chart's depiction of work distribution and possible
bottlenecks, which promotes efficient resource use. By describing task dependencies, it also
makes project coordination easier. Task dependencies are essential for avoiding delays and
guaranteeing that activities are executed in the correct order.

The Gantt chart promotes a transparent and cohesive project environment by clearly showing
timetables and progress, which greatly improves communication and collaboration. This is
especially crucial for following ISO 12207-2008's organized, quality-focused approach, which
places a strong emphasis on software development's planning, execution, and monitoring.
Furthermore, via early detection of possible problems, the chart helps to mitigate risk and allows
for prompt response. In general, the Gantt chart is a fundamental tool for project management
that ensures software development projects are completed successfully and in accordance with
international standards by promoting efficiency, clarity, and quality.

4.7 Project Milestone

The project milestones of the web-based reservation system project for City Taxi (PVT) Ltd are
as follows:

1. Project Charter Approval: Secured by December 12, 2023, marking the official
kickoff.
2. Stakeholder Plan Finalized: All stakeholder agreements in place by December 8, 2023.
3. Team and Resources Assembled: Key personnel and resources locked in by December
14, 2023.
4. Requirements Sign-Off Completed: Project requirements fully endorsed by December
26, 2023.
 5. System Design Lockdown: Design phase concluded with consensus by January 5, 2024.
6. Development Phase Initiation: Code development starts in earnest on January 6, 2024.
7. Deployment Concludes: deployment phase concluding by February 9, 2024.
8. Testing Phase Begins: Systematic testing underway by February 12, 2024.
9. Testing Phase Wrapped Up: All testing finalized by February 23, 2024.
10. Deployment Readiness Achieved: System prepped and ready for live use by February
20, 2024.
11. Project Goes Live: Official system launch celebrated on February 29, 2024.
12. Documentation Finalized: Comprehensive documentation wrapped up by February 26,
2024.
13. Project Officially Closed: The project formally concludes on March 1, 2024.

4.8 Rationale Milestone

1. Project Charter Approval (December 12, 2023): This milestone serves as the official start
of the project, formally endorsing its scope, goals, and limits. It is essential because it
gives the project team the power to assign resources, outlines the main goals of the
project, and creates the structure that all other activities will take place in.

2. Stakeholder Plan Finalized (December 8, 2023): Having the stakeholder plan finalized
prior to project charter approval guarantees that everyone has understood their respective
roles, responsibilities, and expectations. In order to ensure the project is carried out
smoothly, it is imperative that this step be taken to gain the support and buy-in of
important stakeholders, such as potential system users, taxi businesses, and city officials.

3. Team and Resources Assembled (December 14, 2023): Assuring that the project team is
prepared to proceed with planning and execution as soon as possible once the project
commences involves securing essential individuals and resources. This milestone is
essential for building a strong project foundation and making sure that the resources,
technologies, and expertise needed to complete the project are available.
4. Requirements Sign-Off Completed (December 26, 2023): With the completion of this
milestone, a crucial stage where all project requirements were established, examined, and
authorized by stakeholders is completed. It is crucial to make sure that the project's goals
meet the expectations of all stakeholders and that its scope is precisely defined in order to
avoid scope creep and enable a seamless transition to the system design phase.

5. System Design Lockdown (January 5, 2024): Reaching a consensus at the end of the
design phase guarantees that the features, system architecture, and user interface are all
offered to fulfill stakeholder expectations and project needs. This milestone creates a
defined path for the development team to follow, which is essential for moving from
planning to execution.

6. Development Phase Initiation (January 6, 2024): Initiating code development as soon as

the system design is finalized reduces downtime and keeps the project moving forward.
This benchmark denotes the point at which the project's plans are turned into actual
results, from planning to active development.

7. Deployment Concludes (February 9, 2024): By finishing the deployment phase by this

date, there will be enough time to thoroughly evaluate the system in a real-world setting.
It guarantees that the system is correctly installed, configured, and ready for testing and
real-world use.
8. Testing Phase Begins (February 12, 2024): It is possible to find and fix any problems
before the system goes live by starting systematic testing soon after deployment.
Reaching this milestone is essential to guaranteeing the cab management system's
dependability, security, and effectiveness.

9. Testing Phase Wrapped Up (February 23, 2024): By completing all testing by this date,
you can be sure that the system has been properly examined and that any problems found
 have been fixed. In order to guarantee that the system is prepared for deployment and use
in a live environment, this milestone is essential.

10. Deployment Readiness Achieved (February 20, 2024): Making sure the system is
prepared and operational prior to the end of the last testing phase enables any last-minute
modifications based on input from testing. The system is now prepared for formal launch
and operational use, as indicated by this milestone.

11. Project Goes Live (February 29, 2024): The taxi management system becomes an
operational service upon its official introduction, moving it from a project. This
milestone, which denotes the system's readiness to efficiently run city taxi services, is an
important accomplishment.
12. Documentation Finalized (February 26, 2024): Completing thorough documentation
before to the project's launch guarantees that administrators, support staff, and system
users will have access to the data required for system upkeep, use, and troubleshooting.

13. Project Officially Closed (March 1, 2024): Formally concluding the project after going
live allows the project team to evaluate its success, document lessons learned, and
transition to maintenance or support roles. This milestone is critical for closing out the
project in an organized manner, ensuring that all project objectives have been met and
that the system is fully operational and supported.

4.9 Activity Network diagram

ID Task Description Dependencie Duration Start End Date
s (Workdays) Date
A1 Initiate Document Creation None 2 2023-12- 2023-12-
04 05
A2 Project Charter Development None 7 2023-12- 2023-12-
04 12
A3 Stakeholder Identification and A1 4 2023-12- 2023-12-
 Management Plan 05 08
A4 Risk Assessment A1 4 2023-12- 2023-12-
07 12
A5 Resource Allocation and Create Team A2, A4 3 2023-12- 2023-12-
12 14
A6 Kick-off Meeting A3, A5 1 2023-12- 2023-12-
15 15
A7 Requirement Gathering A6 8 2023-12- 2023-12-
15 26
A8 Create Functional and Non-Functional A7 2 2023-12- 2023-12-
Requirements 21 22
A9 Requirement Validation and A8 4 2023-12- 2023-12-
Verification 21 26
A1 Create and Finalize SRS A9 8 2023-12- 2023-12-
0 15 26
A1 Architectural Design A10 4 2023-12- 2023-12-
1 26 29
A1 UI/UX Design A11 6 2023-12- 2024-01-
2 29 05
A1 System Security Design A11 6 2023-12- 2024-01-
3 29 05
A1 Data Migration Strategy Development A13 3 2024-01- 2024-01-
4 01 03
A1 Frontend Development A12 13 2024-01- 2024-01-
5 05 23
A1 Backend Development A14 22 2024-01- 2024-02-
6 09 07
A1 Integration A15, A16 5 2024-02- 2024-02-
7 05 09
A1 Develop Detailed Test Plan A10 7 2023-12- 2024-01-
8 26 31
A1 Execute Comprehensive Testing A17, A18 5 2024-02- 2024-02-
9 01 07
A2 Implement Security Vulnerability A19 4 2024-02- 2024-02-
0 Assessments 02 07
A2 Facilitate User Acceptance Testing A19 6 2024-02- 2024-02-
1 (UAT) 07 14
A2 Configure Production Environment A21 5 2024-02- 2024-02-
2 14 20
A2 Launch System in Production A22 4 2024-02- 2024-02-
3 Environment 19 22
A2 Create and Deliver Final A19, A21 9 2024-02- 2024-02-
4 Documentation 14 26
A2 Host Official Project Closure with A23, A24 1 2024-02- 2024-02-
5 Stakeholders 27 27
Table 6 network diagram
4.10 Activity Network diagram for System

Figure 3network diagram

4.11 Critical Path of Project

The Critical path = A2, A5, A6, A7, A8, A9, A10, A11, A13, A14, A16, A17, A19, A21, A22, A23, A25= 94

∴ The minimum time needed to complete this project is 94 days

Chapter 05
5.1 Project Maintenance
To maintain the system's security, scalability, and dependability, regular maintenance is
essential. Upholding operational excellence and user happiness through software maintenance
involves several crucial factors that are covered by maintenance activities. Patch management
and bug fixes are essential maintenance duties. To maintain system integrity and security, bug
fixes and vulnerabilities in software must be implemented quickly. Effective mitigation of
possible hazards to data security and user experience is achieved through proactive identification
and resolution.

In addition, performance optimization is a constant endeavor during the maintenance stage.

Ensuring that system performance is consistently monitored allows for the detection of
inefficiencies and bottlenecks. The system's speed and efficiency are improved to match
changing user expectations by implementing the appropriate tweaks and optimizations, such as
resource allocation or code reworking. One further crucial component of maintenance is reacting
to consumer input and market expectations. The software is kept competitive and in line with
changing user needs through feature enhancements that are based on market trends and user
input. The software's value proposition is regularly enhanced by adding new features and
functionalities, which raises user happiness and increases market relevance. additionally, By
preventing obsolescence and guaranteeing user pleasure in the face of technological changes,
compatibility updates make sure that the program stays usable and available across a range of
platforms and devices.

Maintaining current and correct information for users is ensured by updating user manuals,
system documentation, and knowledge base articles. Detailed and understandable documentation
promotes self-service and user comprehension, which lowers reliance on support services and
increases user empowerment. In addition, 24/7 technical support guarantees consistent service
availability and user support. Quick handling of customer questions and technical problems
increases user pleasure and software solution trust.

Conclusion
The City Taxi software project concluded successfully within the planned three-month
timeframe. Led by an experienced project manager, our dedicated team delivered a
comprehensive web-based solution for taxi operations. With expertise in software development,
QA, UI/UX design, and technical support, the £100,000 budget was efficiently allocated. The
client's agreement to the timeframe demonstrates satisfaction with the outcomes, solidifying our
relationship and opening doors for future collaborations.