Metrobus Project Plan

Software Development Plan for Metro Bus Tracking Application
Software Development Plan for METRO BUS

TRACKING APPLICATION
Version: 1
Approval date: January 25th,2023
Form FM-SE-15 Software Development Plan Template. Effective 6/14/2018

DOCUMENT CONTROL PANEL

metrobus_Project_Plan.pdf
File Name:
File Location:
Version Number: 1.0
Name Date
Muhammad Anas Khan (SE-21079)
Created By: Taha Hassan (SE-20301)
Suhaib Khan (SE-21078) 25/1/2023
Reviewed By: Taha Hassan (SE-20301)
Suhaib Khan (SE-21078)
Modified By:

Approved By: Taha Hassan (SE-20301) 25/1/2023
Suhaib Khan (SE-21078)
Form FM-SE-15 Software Development Plan Template. Effective 6/14/2018

Table of Contents
1 Overview 1
1.1 Scope 1
1.2 Identification 1
1.3 System Overview 1
1.3.1 Operational Concept 1
1.3.2 Computer Software Configuration Items 1
1.4 Relationship to Other Plans 1
2 Reference Documents 1
3 Overview of Software Development Planning 2
3.1 Requirements and Development 2
3.2 System Life Cycle 3
3.3 Schedules and Resources 3
3.4 Training Requirements 3
4 General Software Development Activities 3
4.1 Development Process 3
4.2 Development Methods 3
4.3 Product Standards 3
4.4 Reusable Products 3
4.4.1 Incorporating Reusable Products 3
4.4.2 Developing Reusable Products 4
4.5 Critical Requirements 4
4.6 Computer Hardware Resource Utilization 4
5 Detailed Software Development Activities 4
5.1 Project Planning and Oversight 4
5.2 Establishing a Software Development Environment 5
5.3 System Requirements Analysis 7
5.4 System Design 7
5.5 Software Requirements Analysis 8
5.6 Software Design 10
5.7 Software Implementation and Test/Code and Unit Test 10
5.8 Software Integration and Testing 12
5.9 System Integration and Testing 13
5.10 System Acceptance Test 14
5.11 Preparing for Software Use 15
5.11.1 Preparing for Software Transition 16
5.12 Software Configuration Management 17
5.13 Software Product Evaluation 17
5.14 Software Quality Assurance 18
5.15 Corrective Action 19
5.16 Technical and Management Reviews 20
5.17 Other Software Development Activities 21
6 Project Gantt Chart 22
7 User Definitions 23
List of Acronyms and Abbreviations
DB DataBase
DDB Distributed DataBase
DBMS Database Management System
SEMP System Engineering Management Plan
HDD Hard Disk Drive
CNIC Computerized National Identity Card
GPS Global Positioning System

1 Overview
This is a Software Development Plan (SDP) for the Metro Bus Tracking Application. The
purpose of this application is to provide real-time tracking of the Green Line Metro Bus, which
was recently launched in Karachi, and also calculates the fares of the bus from one station to the
other.
1.1 Scope
The scope of the project includes the development of a web-based or mobile application that
allows users to track the location of the Green Line Metro Bus in real-time. The application will
also calculate the fares of the bus from one station to another based on the distance traveled.
1.2 Identification
The Metro Bus Tracking Application is being developed us for the Green Line Metro Bus in
Karachi, Pakistan.
1.3 System Overview

The Metro Bus Tracking Application will use GPS technology to track the location of the Green
Line Metro Bus in real-time. The application will also calculate the fares of the bus from one
station to another based on the distance traveled.
1.3.1 Operational Concept

The application will allow users to track the location of the Green Line Metro Bus in real-time
and calculate the fares of the bus from one station to another. The application will be accessible
via web-based or mobile platforms.
1.3.2 Computer Software Configuration Items

The application will be developed using modern web technologies such as HTML, CSS,
JavaScript, and a JavaScript framework such as React or Angular. The application will also
utilize a database for storing and retrieving data.
1.4 Relationship to Other Plans
2 Reference Documents
• https://www.irjet.net/archives/V6/i3/IRJET-V6I3772.pdf
1
• https://www.researchgate.net/publication/
339678623_A_Technical_Paper_Review_on_Vehicle_Tracking_System
3 Overview of Software Development Planning

Requirements:
• This system contains information about the new metro buses, the number of seats
available and prices.
• This system has a high priority since current buses in Pakistan are overpopulated and
there is a lack of information available to citizens about their routes.
• The system will prompt users to sign-up then store this data into the database. Once
stored user can now login to use the application.
• Once logged in user will be shown a menu which gives them the option for “Show
Routes”, “Give Feedback”, “Search Station”, “Metro Wallet” and “Quit”
• The system will show routes of all the metro buses on google maps. Each bus's location
will be shown in
• real-time with their estimated arrival time.
• Each bus will be given a different colour on its shown route, for example, bus number F-
20 will have a red route while bus number D-12 will have a yellow route.
• System will allow users to give developers feedback. This feedback can also receive a
reply from
• developers that will be visible to the user that gave the feedback.
• System will allow users to select two stations and will calculate the total fares for
travelling those stations through the metro bus.
Training:
• Engineers will be required to learn how to use Google Maps API key.
• They will require to learn about all the metro buses that are active on the road so that
their information can be added into the system.
• They will be trained on using Atlas MongoDB to make use of DDB.
Constraints:
• The main constraint on the documentation is that is cannot be finalized until the Pakistan
Government approves of it.
• The documentation has to take into account road laws of Pakistan.
3.1 Requirements and Development

The project will begin with a requirements gathering phase to identify the specific needs of the
end-users and stakeholders. The development team will then use this information to design and
develop the application.
2
3.2 Project Documentation

The project will include documentation such as user manuals, technical documentation, and
system documentation to ensure proper maintenance and support of the application.
3.3 System Life Cycle

The project will follow a standard software development life cycle model, such as Agile or
Waterfall, to ensure a structured and efficient development process.
3.4 Schedules and Resources

The project schedule and resource requirements will be determined during the planning phase
and will be regularly reviewed and updated throughout the project
3.5 Training Requirements

• Google Maps API key will be required for training Engineers
• An Atlas MongoDB subscription will be required
4 General Software Development Activities

4.1 Development Process
The project will follow a structured development process, such as Agile or Waterfall, to ensure a
efficient and effective development process.
4.2 Development Methods

The project will utilize modern web development technologies and methodologies such as
HTML, CSS, JavaScript, and a JavaScript framework such as React or Angular.
.
4.3 Reusable Products

The project will adhere to industry-standard software development practices and guidelines to
ensure a high-quality final product.
4.3.1 Incorporating Reusable Products

The project team will strive to identify and incorporate existing reusable software products into
the Metro Bus Tracking Application to reduce development time and costs. A thorough search
for such products will be conducted, with the scope of the search including industry-standard
3
libraries, open-source solutions, and commercially available products. The criteria used for
evaluating reusable products will include compatibility with the overall architecture of the
application, ease of integration, and the ability to meet the project's specific requirements.
4.3.2 Developing Reusable Products

As the project progresses, the development team will continually evaluate opportunities for
developing reusable software products. These opportunities will be reported to the project
manager and evaluated for inclusion in the project's scope. If feasible, development of reusable
products will be prioritized to provide long-term benefits for future projects.
4.4 Critical Requirements

The Metro Bus Tracking Application will handle critical requirements such as safety assurance,
security assurance, and privacy assurance. These requirements will be identified during the
requirements gathering phase and will be given priority during development. The project team
will follow industry-standard best practices to ensure that the application meets these critical
requirements.
4.5 Computer Hardware Resource Utilization

The project team will use appropriate computer hardware resources for the development, testing
and deployment of the Metro Bus Tracking Application. The hardware resources will be
allocated based on the project's requirements and will be monitored throughout the project to
ensure efficient utilization. The project team will also consider the scalability and future growth
of the application when allocating hardware resources.
5 Detailed Software Development Activities

This section provides the plans for performing detailed software development activities,
including the approach (i.e., methods, procedures, and tools).
5.1 Project Planning and Oversight

This section describes the approach to be followed for project planning and oversight.
● Software development planning:

The project team will use a structured software development method such as Agile or
Waterfall to plan and execute the development of the Metro Bus Tracking Application.
● Computer software configuration item test planning:
4
The project team will plan and execute tests on the individual software components
(configuration items) to ensure they meet the project's requirements.
● System test planning:
The project team will plan and execute tests on the complete system, including the
integration of all software components, to ensure the application meets the project's
requirements.
● Software installation planning:
The project team will plan and execute the installation of the application on the target
hardware and software platform.
● Software transition planning:
The project team will plan and execute the transition of the application from development
to production, including training of end-users and stakeholders.
● Following and updating plans:
● The project team will regularly review and update the project plans, including the
intervals for management review to ensure the project stays on track and meets its goals.
5.2 Establishing a Software Development Environment

The approach for establishing, controlling, and maintaining a software development environment
will include the following steps:
● Software engineering environment:
The project team will establish a software engineering environment that includes the
necessary tools and resources for developing, testing, and deploying the Metro Bus
Tracking Application.
● Software test environment:
The project team will establish a software test environment that includes the necessary
tools and resources for testing the application.
● Software development library:
The project team will establish a software development library that includes reusable
code, libraries, and other resources that can be reused across projects.
● Software development files
The project team will establish and maintain a system for storing and managing software
development files, including source code, documentation, and other project-related files.
5
This will ensure that the project team has a controlled and consistent environment for
developing, testing and deploying the application, which will help to increase the quality of the
software development process., and other project-related files.
6
5.3 System Requirements Analysis

Analysis of user input:
 Users of the Metro Bus tracking and fare calculation system will primarily be individuals
who use the Metro Bus service.
 The system will gather input from users regarding their desired destination and starting
point, as well as any preferences for bus routes or stations.
Operational concept:
 The system will provide real-time tracking of Metro Buses in each city.
 The system will calculate fares for bus trips from one station to another.
 The system will provide users with estimated arrival times for buses at specific stations.
System requirements:
 The system will need to be able to access real-time data on the locations of all active
Metro Buses in the city.
 The system will need to be able to calculate bus fares based on the distance or time
traveled.
 The system will need to be able to provide users with estimated arrival times for buses at
specific stations, taking into account traffic, route changes, and other factors.
 The system will need to be accessible through a user-friendly interface, such as a website
or mobile app.
 The system will need to be able to handle a large number of simultaneous users.
 The system will need to be able to integrate with any existing systems used by the Metro
Bus service.
 The system will need to be maintained and updated on a regular basis to ensure continued
accurate and reliable performance.
5.4 System Design

System wide design decisions:
 The system will be designed as a web-based or mobile application, to be easily accessible

to users.
7
 The system will make use of real-time GPS data to track the location and movement of
all active Metro Buses in the city.
 The system will use this data to calculate fares based on distance or time traveled and
provide estimated arrival times for buses at specific stations.
 The system will be designed to be user-friendly and easy to navigate.
 The system will be designed to handle a large number of simultaneous users.
System architectural design:
 The system will consist of a front-end interface for users to interact with, which will be
built using technologies such as HTML, CSS, and JavaScript.
 The back-end of the system will include a database to store and retrieve information on
bus locations, routes, fares, and estimated arrival times.
 The system will use APIs to gather real-time GPS data on bus locations and integrate
with any existing systems used by the Metro Bus service.
 The system will be hosted on a web server and will be accessible through a web browser
or mobile app.
 The system will be designed to be scalable and able to handle an increasing number of
users over time.
 The system will include a secure login feature for the administrator to manage and update
the system.
5.5 Software Requirements Analysis

5.5.1 Approach
The software requirements analysis for the Metro Bus system will involve a thorough
examination of the needs and expectations of the users, as well as an analysis of the current
system's capabilities and limitations. This will be done through a combination of stakeholder
interviews, user surveys, and other forms of research.
5.5.2 Entrance Criteria
The project scope and objectives have been clearly defined and agreed upon by all stakeholders.
A detailed user requirement document has been prepared and reviewed by all stakeholders.
The proposed solution has been validated through initial feasibility analysis.
5.5.3 Exit Criteria
8
A comprehensive software requirements specification document has been prepared and reviewed
by all stakeholders.
All identified requirements have been prioritized and grouped into functional and non-functional
requirements.
All requirements have been validated through user acceptance testing.
The software development team has been provided with all necessary information to begin the
development process
9
5.6 Software Design

5.6.1 Approach: The software design for the Metro Bus system will be based on a modular
and scalable architecture, allowing for easy maintenance and future updates. The design
will be developed through a iterative process, with regular review and feedback from
stakeholders and users.
The software requirements specification document has been approved and accepted by all
stakeholders.
A high-level design has been prepared and reviewed by the development team.
5.6.3 Exit Criteria
A detailed software design document has been prepared, including architecture diagrams and
class diagrams.
The design has been reviewed and approved by all stakeholders.
The design has been validated through technical feasibility analysis.
The design is aligned with the project objectives and requirements.
5.6.4 Software architecture/preliminary design:
The preliminary design for the Metro Bus system will be based on a client-server architecture,
with a web-based front-end for users and a back-end server for data processing and storage. The
system will make use of real-time tracking technology and a fare calculation algorithm to
provide accurate and up-to-date information to users.
5.6.5 Software detailed design:
The detailed design for the Metro Bus system will include specific class diagrams and
flowcharts outlining the functionality of each module. This will include the real-time tracking
module, fare calculation module, and user interface module. The detailed design will also include
database schema and API design for integrating the system with other relevant systems.
5.7 Software Implementation and Test/Code and Unit Test

5.7.1 Approach: The software code and unit testing for the Metro Bus system will follow a test-
driven development approach, with a focus on ensuring the quality and stability of the code. The
unit testing process will be performed in parallel with the software development process to
ensure that all requirements are met and any bugs are identified and fixed in a timely manner.
10
5.7.2 Entrance Criteria:
The software design document has been approved and accepted by all stakeholders.
The development team has been provided with all necessary resources and tools to begin the
software development process.
5.7.3 Exit Criteria:
The software code has been fully implemented and meets all requirements and design
specifications.
All code has been reviewed and approved by the development team.
All unit tests have been successfully passed and all bugs have been identified and fixed.
The software is ready for user acceptance testing.
5.7.4 Software code:
The software code for the Metro Bus system will be developed using industry standard
programming languages and frameworks, such as Java for back-end, ReactJS for front-end and
MySQL for database. The code will be organized and structured following best practices for
maintainability and scalability.
5.7.5 Unit testing preparations:
Unit testing preparations will involve the creation of test cases and test data, as well as the
development of test scripts and test harnesses. This will be done in collaboration with the
development team and stakeholders to ensure that all relevant requirements are covered.
5.7.6 Performing unit testing:
Unit testing will be performed by the development team to ensure that all code meets the
requirements and functions as intended. This will involve running the test cases and scripts
against the software code, and recording and analyzing the results.
5.7.7 Revision and retesting:
If any bugs or issues are identified during unit testing, the development team will revise the code
and re-test it to ensure that all issues have been resolved.
5.7.8 Analyzing and recording unit test results:
11
The results of the unit testing will be analyzed and recorded to ensure that all requirements have
been met and all bugs have been identified and fixed. The test results will be reviewed and
approved by the development team and stakeholders before the software is moved on to the next
stage of testing
5.8 Software Integration and Testing

5.8.1 Approach:
The software integration and testing for the Metro Bus system will involve integrating all the
various software components and modules developed during the previous stages, such as real-
time tracking, fare calculation and user interface, into a cohesive and functional system. This will
be done through a series of integration and testing activities, to ensure that all components work
together as intended and meet the system requirements.
All software components have been successfully developed and unit tested.
The development team has been provided with all necessary resources and tools to begin the
integration and testing process.
5.8.3 Exit Criteria
All software components have been successfully integrated into a functional system.
The system has been successfully tested and meets all requirements.
All bugs have been identified and fixed.
The system is ready for acceptance testing.
5.8.4 Preparing for integration and testing:
The integration and testing process will begin by preparing the necessary test environments, test
data, and test cases. This will be done in collaboration with the development team and
stakeholders to ensure that all relevant requirements are covered.
5.8.5 Performing integration and testing:
The system will be tested by running a series of integration and system-level tests, such as
functional testing, performance testing, and usability testing. These tests will be performed by
the development team and will be used to identify any issues or bugs in the system.
5.8.6 Revision and retesting:
12
If any bugs or issues are identified during integration and testing, the development team will
revise the system and re-test it to ensure that all issues have been resolved.
5.8.7 Analyzing and recording integration and test results:
The results of the integration and testing will be analyzed and recorded to ensure that all
requirements have been met and all bugs have been identified and fixed. The test results will be
reviewed and approved by the development team and stakeholders before the system is moved
on to the next stage of testing.
5.9 System Integration and Testing

This section describes the approach to be followed for participating in system integration and
testing (SIT) for the real-time tracking and fare calculation system for Metro Buses. The system
aims to provide ease and a better experience for users by providing real-time tracking of the
Metro Bus in each city and calculating the fares from one station to another.
● Independence in SIT: The software engineer(s) will be responsible for supporting the testing
activities, ensuring the independence and objectivity of the testing process.
● Testing on the target computer system: The system will be tested on the target computer
system to ensure proper functionality and compatibility.
● Preparing for SIT: The software engineer(s) will prepare for SIT by creating test cases and
scripts, and configuring the test environment.
● Performing SIT dry runs: The software engineer(s) will perform dry runs of SIT to identify and
address any issues before actual testing begins.
● Performing SIT: The software engineer(s) will conduct SIT according to the project SEMP,
testing the system's functionality, performance, and security.
13
● Revision and retesting: Any issues identified during SIT will be corrected and the system will
be retested to ensure proper functionality.
● Analyzing and recording SIT results: The software engineer(s) will analyze and record the
results of SIT, documenting any issues and their resolution. This will be used to improve the
system and its maintenance.
5.10 System Acceptance Test

This section describes the approach to be followed for participating in system acceptance testing
for the real-time tracking and fare calculation system for Metro Buses. The system aims to
provide ease and a better experience for users by providing real-time tracking of the Metro Bus
in each city and calculating the fares from one station to another, and also tells the user about the
estimated time to reach any station.
● Independence in system acceptance testing: The software engineer(s) will be responsible for
supporting the testing activities, ensuring the independence and objectivity of the testing process.
● Testing on the target computer system: The system will be tested on the target computer
system to ensure proper functionality and compatibility.
● System acceptance test preparation: The software engineer(s) will prepare for system
acceptance testing by creating test cases and scripts, and configuring the test environment.
● Performing system acceptance test dry runs: The software engineer(s) will perform dry runs of
system acceptance testing to identify and address any issues before actual testing begins.
● Performing system acceptance testing: The software engineer(s) will conduct system
acceptance testing according to the project SEMP, testing the system's functionality,
performance, and security.
14
● Revision and retesting: Any issues identified during system acceptance testing will be
corrected and the system will be retested to ensure proper functionality.
● Analyzing and recording system acceptance test results: The software engineer(s) will analyze
and record the results of system acceptance testing, documenting any issues and their resolution.
This will be used to improve the system and its maintenance
5.11 Preparing for Software Use

This section describes the approach to be followed for preparing for software use.
● Preparing the executable software
● Preparing version descriptions for user sites
● Preparing user manuals
● Installing at user sites
15
5.11.1 Preparing for Software Transition

This section describes the approach to be followed for preparing for software transition for the
real-time tracking and fare calculation system for Metro Buses. The system aims to provide ease
and a better experience for users by providing real-time tracking of the Metro Bus in each city
and calculating the fares from one station to another and also tells the user about the estimated
time to reach any station.
● Preparing the executable software: The software engineer(s) will prepare the final version of
the software for delivery, including any necessary updates and bug fixes, and verify its
functionality.
● Preparing source files: All source files will be identified, verified, and recompiled, as
necessary, to ensure their accuracy and completeness.
● Preparing version descriptions for the support site: The software engineer(s) will prepare
version descriptions for the support site to assist in identifying the current version of the
software.
● Preparing the “as-built” CSCI design and other software support information: The software
engineer(s) will prepare the "as-built" CSCI design and other software support information,
including documentation and user manuals, to assist in the support and maintenance of the
system.
● Updating the system design description: The software engineer(s) will update the system
design description to reflect any changes made during the development and testing phase.
● Preparing support manuals: The software engineer(s) will prepare support manuals for the
system to assist users in understanding and using the system.
16
● Transitioning to the designated support site: The software will be transitioned to the designated
support site for distribution and maintenance.
5.12 Software Configuration Management

This section describes the approach to be followed for software configuration management (CM)
for the real-time tracking and fare calculation system for Metro Buses. The system aims to
provide ease and a better experience for users by providing real-time tracking of the Metro Bus
in each city and calculating the fares from one station to another and also tells the user about the
estimated time to reach any station.
● Configuration identification: The software engineer(s) will identify and document all software
components and versions, including source code, executables, and documentation.
● Configuration control: The software engineer(s) will implement and maintain procedures for
controlling changes to the software, including change requests, approval, and implementation.
● Configuration status accounting: The software engineer(s) will implement and maintain
procedures for tracking and reporting the status of software components, including version,
release, and distribution information.
● Configuration audits: The software engineer(s) will conduct regular audits of the software
components to ensure their accuracy and completeness.
● Packaging, storage, handling, and delivery: The software engineer(s) will package, store,
handle, and deliver the software in accordance with established procedures and standards. This
includes ensuring software security, preservation, and accessibility.
5.13 Software Product Evaluation

This section describes the approach to be followed for software product evaluation for the real-
time tracking and fare calculation system for Metro Buses. The system aims to provide ease and
a better experience for users by providing real-time tracking of the Metro Bus in each city and
calculating the fares from one station to another and also tells the user about the estimated time
to reach any station.
17
● In-process and final software product evaluations: The software engineer(s) will conduct in-
process and final evaluations of the software to ensure compliance with project requirements,
design, and standards.
● Software product evaluation records, including items to be recorded: The software engineer(s)
will maintain records of all software product evaluations, including the results and any issues
identified.
● Independence in software product evaluation: The software product evaluation will be

conducted independently to ensure objectivity and impartiality in the evaluation process.
● Evaluation criteria: Evaluation criteria will be established to assess the software product
against the requirements and standards established for the project.
● Evaluation schedule: Evaluation will be conducted according to the program schedules

established for the project.
5.14 Software Quality Assurance

This section describes the approach to be followed for software quality assurance (QA) for the
real-time tracking and fare calculation system for Metro Buses. The system aims to provide ease
and a better experience for users by providing real-time tracking of the Metro Bus in each city
and calculating the fares from one station to another, and also tells the user about the estimated
time to reach any station.
● Software QA process and product evaluations: The software engineer(s) will implement and
maintain a QA process to ensure compliance with project requirements, design, and standards.
This will include in-process and final evaluations of the software.
● Software QA records, including items to be recorded: The software engineer(s) will maintain
records of all software QA activities, including evaluations, test results, and any issues identified.
18
● Independence in software QA: The software QA process will be conducted independently to

ensure objectivity and impartiality in the evaluation process.
● QA plan: A comprehensive QA plan will be established to outline the approach and procedures
for software QA.
● QA schedule: The QA activities will be conducted according to the program schedules

established for the project
5.15 Corrective Action

The software engineer(s) will be responsible for implementing and maintaining the corrective
action process throughout the development and maintenance of the system. Subtopics to be
addressed include:
● Establishing a process for tracking and reporting problems
● Identifying and assessing the impact of problems
● Implementing corrective actions
● Verifying the effectiveness of corrective actions
● Maintaining records of corrective actions
● Providing for continuous improvement of the corrective action process
● Problem/change report: A process will be established to track and report problems and changes
to the software system. This includes a problem/change report form, and a process for
submitting, reviewing, and approving problem/change reports.
19
● Identifying and assessing impact: A process will be established to identify and assess the
impact of problems on the software system. This includes determining the severity and priority
of the problem and its impact on system functionality and performance.
● Implementing corrective actions: The software engineer(s) will implement corrective actions
to address problems and changes identified during development, testing, and maintenance.
● Verifying the effectiveness of corrective actions: The software engineer(s) will verify the
effectiveness of corrective actions by conducting retests or re-evaluations as necessary.
● Maintaining records of corrective actions: The software engineer(s) will maintain records of all
corrective actions, including problem/change reports, problem assessments, corrective action
plans, and verification results.
● Providing for continuous improvement: The software engineer(s) will continuously monitor
and improve the corrective action process to ensure its effectiveness and efficiency.
5.16 Technical and Management Reviews

Technical Review:
 The system will utilize GPS technology to track the location of the Metro buses in real-time.
 A fare calculation algorithm will be implemented to determine the cost of a trip from one
station to another.
 Data will be collected and analyzed to estimate arrival times at each station.
 The system will be developed using appropriate programming languages and frameworks to
ensure stability, scalability, and security.
 Regular testing and quality assurance will be conducted to ensure the system's functionality
and accuracy.
Management Review:
20
 The system's performance will be monitored and evaluated regularly to ensure it meets the
needs of the users and the organization.
 The project team will maintain clear and effective communication with stakeholders to
ensure their needs and requirements are being met.
 The project timeline and budget will be closely monitored to ensure the project stays on track
and within budget.
 Any issues or risks will be identified and addressed in a timely manner.
 Regular status updates will be provided to stakeholders to ensure they are informed of the
project's progress.
5.17 Other Software Development Activities

• Risk management: Potential risks will be identified and evaluated, and corresponding
strategies will be put in place to mitigate or avoid them. These may include technical
risks, such as system failures or security breaches, as well as project risks, such as delays
or budget overruns.
• Software management indicators: Metrics will be used to measure the performance and
quality of the system, including user satisfaction, system uptime, and error rates. These
indicators will be used to identify areas for improvement and to track progress over time.
• Security and privacy: The system will be designed with security and privacy in mind,
including measures to protect sensitive data, such as user information and payment
details. Regular security audits will be conducted to identify and address any
vulnerabilities.
• Subcontractor management: If subcontractors are used, they will be managed according

to the project's requirements, timelines, and budget. Regular communication and
coordination will be maintained to ensure the smooth delivery of their work.
• Interface with software independent verification and validation agents: Independent

agents will be used to verify and validate the system's functionality and performance.
This will include testing and quality assurance, as well as reviews of the system's design
and architecture.
• Coordination with associate developers: The development team will work closely with
other teams and stakeholders, including designers, project managers, and business
analysts, to ensure that the system meets the needs of the organization and its users.
21
• Improvement of project processes: The project team will regularly review and improve
their development process to ensure that the system is delivered on time and within
budget. This will include identifying areas for improvement and implementing best
practices to streamline the development process.
6 Project Gantt Chart

The below gantt chart shows how the different project software life cycle phases will be
distributed:
22
7 User Definitions
Database: It is an organized collection of structured information, or data, typically stored
electronically in a computer system.
Database Management System: It is essentially nothing more than a computerized data-keeping

system. Users of the system are given facilities to perform several kinds of operations on such a
system for either manipulation of the data in the database or the management of the database
structure itself.
23
DOCUMENT REVISION HISTORY

Version Approved Created/
Description of Change(s)
Number Date Modified By
Taha Hassan (SE-
20301)
Sohaib Khan (SE-
1 25/1/2023 First Draft
21078)
Anas Khan (SE-
21079)
24

Metrobus Project Plan

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Metrobus Project Plan

Uploaded by

Copyright:

Available Formats

Software Development Plan for Metro Bus Tracking Application

Software Development Plan for METRO BUS

Approval date: January 25th,2023

Form FM-SE-15 Software Development Plan Template. Effective 6/14/2018

DOCUMENT CONTROL PANEL

Muhammad Anas Khan (SE-21079)

Form FM-SE-15 Software Development Plan Template. Effective 6/14/2018

DDB Distributed DataBase

DBMS Database Management System

SEMP System Engineering Management Plan

HDD Hard Disk Drive

CNIC Computerized National Identity Card

GPS Global Positioning System

1.3 System Overview

1.3.1 Operational Concept

1.3.2 Computer Software Configuration Items

1.4 Relationship to Other Plans

3 Overview of Software Development Planning

3.1 Requirements and Development

3.2 Project Documentation

3.3 System Life Cycle

3.4 Schedules and Resources

3.5 Training Requirements

4 General Software Development Activities

4.2 Development Methods

4.3 Reusable Products

4.3.1 Incorporating Reusable Products

4.3.2 Developing Reusable Products

4.4 Critical Requirements

4.5 Computer Hardware Resource Utilization

5 Detailed Software Development Activities

5.1 Project Planning and Oversight

● Software development planning:

5.2 Establishing a Software Development Environment

5.3 System Requirements Analysis

5.4 System Design

 The system will be designed as a web-based or mobile application, to be easily accessible

 The system will be designed to be user-friendly and easy to navigate.

 The system will be designed to handle a large number of simultaneous users.

System architectural design:

5.5 Software Requirements Analysis

5.5.2 Entrance Criteria

5.5.3 Exit Criteria

5.6 Software Design

5.6.2 Entrance Criteria

5.6.3 Exit Criteria

The design has been reviewed and approved by all stakeholders.

The design has been validated through technical feasibility analysis.

The design is aligned with the project objectives and requirements.

5.6.4 Software architecture/preliminary design:

5.6.5 Software detailed design:

5.7 Software Implementation and Test/Code and Unit Test

5.7.2 Entrance Criteria:

5.7.3 Exit Criteria:

The software is ready for user acceptance testing.

5.7.4 Software code:

5.7.5 Unit testing preparations:

5.7.6 Performing unit testing:

5.7.7 Revision and retesting:

5.7.8 Analyzing and recording unit test results:

5.8 Software Integration and Testing

5.8.2 Entrance Criteria

5.8.3 Exit Criteria