Chapter Four: System Analysis and Requirement Modeling

1. Introduction

1.1 Purpose

This chapter aims to delve into the analysis of the current vehicle management system, utilizing various
modeling tools to provide a comprehensive understanding of its functionalities, strengths, weaknesses,
and requirements for improvement.

1.2 Scope

The analysis covers the vehicle management system's core modules, including booking, user
management, admin functionalities, driver assignments, and vehicle tracking.

1.3 Objectives

- Describe the operational flow of the current system.

- Identify stakeholders and their roles within the system.

- Analyze the system using modeling tools such as flow charts, DFDs, use cases, and UML diagrams.

- Outline functional and non-functional requirements for system enhancement.

2. Description of the Current System

2.1 Overview
The current vehicle management system facilitates vehicle booking, user registration, admin
management, driver assignments, and vehicle tracking. Users can access the system through web or
mobile interfaces to book vehicles for various purposes.

2.2 System Components

- User Interface: Allows users to interact with the system for booking vehicles.

- Database: Stores information about users, vehicles, bookings, and drivers.

- Booking Module: Handles vehicle booking requests, availability checks, and confirmation.

- Admin Module: Provides administrative functions for managing users, vehicles, and drivers.

- Driver Module: Assigns drivers to bookings and manages their schedules.

2.3 System Flow using System Analysis Modeling Tools

2.3.1 Flow Charts

[Insert flowchart depicting the booking process from user request to confirmation]

2.3.2 Data Flow Diagrams (DFDs)

[Insert level 0 DFD showing high-level system components]

[Insert level 1 DFDs depicting detailed processes within each module]

2.3.3 Use Cases

[Insert use case diagram illustrating actor interactions and system functionalities]
2.3.4 Unified Modeling Language (UML) Diagrams

[Insert class diagram depicting system entities and their relationships]

[Insert sequence diagram showing interactions between user, admin, and system components during a
booking process]

[Insert activity diagram illustrating the workflow of booking management]

3. System Analysis

3.1 Stakeholder Analysis

[Provide detailed stakeholder analysis highlighting their roles, interests, and expectations]

3.2 Functional Requirements

[Outline functional requirements based on use cases and system analysis]

3.3 Non-Functional Requirements

[Identify non-functional requirements related to system performance, security measures, user

experience, etc.]

4. Requirement Modeling

4.1 Use Case Diagram

[Provide a use case diagram]

4.2 Use Case Descriptions

[Present use case descriptions for key system functionalities]

4.3 Activity Diagrams

[Include activity diagrams for important system processes]

4.4 Class Diagrams

[Provide class diagrams depicting system entities and their attributes]

4.5 Sequence Diagrams

[Present sequence diagrams for critical system interactions]

5. Conclusion

This chapter has provided a thorough analysis of the current vehicle management system, outlining its
functionalities, stakeholders, and requirements for enhancement. The requirement modeling section
lays the groundwork for system refinement and future development phases.
Chapter six

Chapter Six: System Implementation

1. Introduction

In this chapter, we will discuss the implementation details of the vehicle management system, including
the coding and testing tools used, the system test plan, testing procedures, and proposed change-over
techniques.

2. Tools Used for Coding and Testing

2.1 Programming Languages and Frameworks

For the implementation of the vehicle management system, we will use PHP for server-side scripting,
HTML and CSS for front-end design, JavaScript for client-side interactions, and SQL for database
management.

2.2 Integrated Development Environment (IDE)

Popular IDEs such as Visual Studio Code, Sublime Text, or PhpStorm can be used for writing and
debugging code efficiently.

2.3 Version Control System (VCS)

Git will be used as the version control system to manage the source code repository, enabling
collaboration among developers and tracking changes effectively.

2.4 Testing Tools

For testing, we will utilize PHPUnit for PHP unit testing, Selenium WebDriver for automated browser
testing, and Postman for API testing.

3. System Test Plan

3.1 Objectives of Testing

The primary objectives of testing are to verify the functionality of the system modules (booking, user
management, admin functionalities, driver assignments, and vehicle tracking), ensure compliance with
requirements, and identify and rectify any defects.

3.2 Testing Environment

Testing will be conducted in a controlled environment resembling the production setup, with
configurations matching hardware, software, and network specifications.

3.3 Test Cases

Comprehensive test cases will be developed covering various scenarios, edge cases, and user
interactions for each system module. These test cases will be based on functional and non-functional
requirements.

3.4 Testing Procedures

Testing procedures will involve executing the predefined test cases, recording results, and identifying
any failures or discrepancies. Testing will include unit testing, integration testing, system testing, and
user acceptance testing.

3.5 Acceptance Criteria

Acceptance criteria will be defined based on system requirements and user feedback, determining
whether the system meets stakeholders' expectations and is ready for deployment.

4. Testing

4.1 Data Used for Testing

Testing will involve using synthetic and real-world data sets to simulate different scenarios and validate
system functionality under various conditions.

4.2 Testing Approach

A combination of manual and automated testing approaches will be employed to ensure comprehensive
test coverage and efficient execution of test cases.

4.3 Types of Testing Conducted

Various types of testing, including unit testing, integration testing, system testing, and user acceptance
testing, will be conducted to validate the system's functionality, performance, and reliability.

4.4 Results and Findings

Testing results will be documented, including defects or issues identified during the testing process.
Findings will be analyzed, and necessary adjustments or corrections will be made to improve system
quality and reliability.

5. Proposed Change-over Techniques

Change-over techniques such as parallel adoption or phased implementation will be proposed based on
project requirements, risks, and constraints. The chosen technique will aim to minimize disruption to
operations and ensure a smooth transition to the new system.

6. Conclusion

The implementation of the vehicle management system involves utilizing PHP, CSS, SQL, and JavaScript
to develop a robust and efficient system. By employing appropriate coding and testing tools, developing
a comprehensive test plan, conducting thorough testing, and proposing suitable change-over
techniques, the system can be successfully implemented to meet stakeholders' requirements and
expectations.

Chapter seven

Chapter Seven: Limitations, Conclusions, and Recommendations

1. Limitations

During the development of the vehicle management system, several limitations were encountered:

- Time Constraints: Limited time for research, development, and testing impacted the thoroughness of
the analysis and the depth of system features.
- Financial Constraints: Budget limitations restricted access to resources and tools that could have
enhanced system functionality and performance.

- Data Availability: Limited access to comprehensive and accurate data hindered thorough testing and
evaluation of the system's capabilities.

- Anti-Cooperative Responses: Some stakeholders' reluctance to provide necessary information or

feedback impeded the project's progress.

2. Conclusion

The vehicle management system successfully addresses identified needs and requirements outlined in
the theoretical background and literature review. Leveraging technologies such as PHP, CSS, SQL, and
JavaScript, the system offers practical solutions for transportation management challenges.

The system's user-friendly interfaces, automated processes, and comprehensive features enhance
operational efficiency and user experience. Its potential significance for application in transportation,
logistics, and fleet management industries is evident.

3. Recommendations

Moving forward, the following recommendations are proposed for system enhancement:

- Continuous Improvement: Establish a system for continuous improvement to address identified

shortcomings and ensure alignment with evolving user needs.

- Enhanced Testing Procedures: Invest in robust testing procedures, including user acceptance and
performance testing, to validate system functionalities under various conditions.

- Stakeholder Engagement: Foster stronger collaboration with stakeholders to gather feedback and
address concerns, ensuring system enhancements reflect user needs.

- Integration of Advanced Features: Explore integrating advanced features such as GPS tracking and
predictive maintenance to optimize vehicle management processes.
- Training and Support: Provide comprehensive training and ongoing support to users, admins, and
drivers to maximize system utilization and efficiency.

By implementing these recommendations, the vehicle management system can continue evolving to
meet changing demands, driving improvements in transportation management and efficiency.