Transportation Management System

Admas University
_____________________

Hargeisa, Somaliland

__________________

Submitted for the partial fulfillment of the requirements for the award of the Degree in

ICT
_______________

By:

Mohamed Abdullahi Ahmed

&

Faisal Ali Mohamed

August, 2022

CERTFICATE

pg. 1
This is to certify that the project titled “Online car rental system” is a bona-fide work done by

Mohamed Abdullahi Ahmed

Faisal Ali Mohamed

In partial fulfillment of the requirements for the award of BSc. (ICT)

During the period 2019-2022

(Moktar Abdi Sheik “Mash”) Mr. Yosef Meleke

Advisor Head of the Department

DECLARATION

pg. 2
We, Mohamed Abdullahi Ahmed and Faisal Ali Mohamed hereby declare that we have
carried out an independent research work on “Transportation management system” in
fractional fulfillment of the requirement a Bachelor of Science Degree in Information and
Communication Technology with the guidance and support of the research advisor.

Mohamed Abdullahi Ahmed Faisal Ali Mohamed

Signature _________ Signature: _______

Date: _________ Date: _________

pg. 3
 APPROVAL

I, Moktar Abdi Sheik “Mash”, approve that this research under the title
“Transportation management system” is done by Faisal Ali Mohamed and Mohamed
Abdullahi Ahmed under my supervision.

Moktar Abdi Sheik “Mash"

Signature ____________ Date ______________

pg. 4
 ACKNOWLEDGEMENT
First of all, purely and simply, all praise is due to Allah who is almighty for providing us the heath
and the intellectual’s ability necessary to complete this thesis.
It is from him we draw support in life. We must acknowledge our vast thanks to Allah, the ever
magnificent the ever thankful, for his helps and bless.
We are totally sure that this work would not have ever become truth, without his guidance Also
we like to thank our families for their generous support us and encourage us through our life and
we will pay, Allah reward them with all the happiness and success that life can bring to them.

Press our thanks especially for especial person who support as and hardly work with us in every
step we do in this research paper and help us a lot.

We are grateful to some people who worked with us and contributed to present in this thesis.
We deeply like to express our gratitude to our supervisor who worked hard with us on the all period
from banning at last time achievement of the present research particularly our supervisor Mr.
Moktar Abdi Sheik “Mash”, who has been always generous, during all phases of preparing
research continues advice and encouragement us throughout the path of the thesis.
We would like to express our very sincere gratitude to our dean Yosef Meleke for his effort and
encourages, motivated us all the time and be sides us in every obstacle faced us also for our lecture
for their time and efforts expended by Ahmed Nassir Hajji for support and encouraged whenever
we was in needed in research and our lecture Moktar Abdi Sheik “Mash” who support us any
situation of this research and motivates us as lecture also many thanks to brothers and sisters in
our class for their motivations.

pg. 5
Contents
CERTFICATE ................................................................................................................................................... 1
CHAPTER 1 .................................................................................................................................................... 9
1.0 Introduction: ..................................................................................................................................... 9
1.1 Background of the project ................................................................................................................ 9
1.3 Problem of the Statement ............................................................................................................... 10
1.3 Project objectives ............................................................................................................................ 11
General objectives ............................................................................................................................. 11
Specific Objectives ............................................................................................................................ 11
1.4 The scope of the project .................................................................................................................. 11
1.5 Significance of the study ................................................................................................................. 12
1.6 Data Collection Methodology......................................................................................................... 12
1.1 Observation ................................................................................................................................. 12
1.2 Interviews..................................................................................................................................... 12
1.3 Questionnaires ............................................................................................................................. 12
1.7 System development method .......................................................................................................... 13
We use waterfall model it’s very simple to understand a use in water full model each phase must be
complete fully before next phase can begin. ....................................................................................... 13
1.8 Project Management ....................................................................................................................... 13
1.9 WBS and Gant Chart ..................................................................................................................... 14
CHAPTER TWO ........................................................................................................................................ 15
2.0 Introduction ..................................................................................................................................... 15
2.1 Development Software .................................................................................................................... 16
Tripper Bus........................................................................................................................................ 16
VamoosBus ........................................................................................................................................ 17
2.2 Comparison of the existing systems ............................................................................................... 20
2.3 Summary.......................................................................................................................................... 20
Chapter three ............................................................................................................................................... 21
2.4 Research methodology .................................................................................................................... 21
2.5 Data collection methodology ...................................................................................................... 21
2.6 Existing System ............................................................................................................................... 21
2.7 Weakness and the strength of the existing system ....................................................................... 21

pg. 6
 2.8 User Requirements.......................................................................................................................... 22
2.9 Business Rules ................................................................................................................................. 22
Software Requirements .................................................................................................................... 22
Software Requirements also have two types: - ............................................................................... 22
Here are some functional requirements of the system: - ............................................................... 22
Non-Functional requirements .......................................................................................................... 22
The non-functional requirements of the system are described as follows: - ................................ 23
3.0 Feasibility Study .............................................................................................................................. 23
Here the feasibility study can be performed in four ways such as: - ............................................ 23
3.1 System Development Life Cycle (SDLC) ...................................................................................... 24
Identify the Current Problems............................................................................................................. 25
❖ Plan ............................................................................................................................................. 25
❖ Design ......................................................................................................................................... 25
❖ Build ........................................................................................................................................... 26
❖ Code Test ................................................................................................................................... 26
❖ Software Deployment................................................................................................................ 26
CHAPTER FOUR ....................................................................................................................................... 27
3.2 introduction ...................................................................................................................................... 27
3,3 UML diagrams .............................................................................................................................. 27
3.4 Use case diagram ............................................................................................................................. 27
Authentication Sequence Diagrams ................................................................................................ 29
Bus Sequence Diagrams.................................................................................................................... 30
Customer Sequence Diagrams ......................................................................................................... 31
Booking Sequence Diagrams ............................................................................................................ 32
3.6 Class diagram .................................................................................................................................. 33
3.7 User Interface prototyping ............................................................................................................. 34
CHAPTER FIVE ........................................................................................................................................ 35
System Design ........................................................................................................................................ 35
3.8 Introduction ..................................................................................................................................... 35
4.0 Normalization in database.............................................................................................................. 35
First normal form ............................................................................................................................. 36
Second normal form ......................................................................................................................... 36

pg. 7
 4.1 Database dictionary ........................................................................................................................ 36
1.Booking ........................................................................................................................................... 36
2.Buses ................................................................................................................................................ 37
3.Customer......................................................................................................................................... 37
4.Routes .............................................................................................................................................. 37
5.Driver .............................................................................................................................................. 38
6.Seats................................................................................................................................................. 38
7.Users ................................................................................................................................................ 38
4.2 ER Diagram ..................................................................................................................................... 39
Tables of the database .......................................................................................................................... 39
4.3 Interface design ............................................................................................................................... 40
Dashboard.......................................................................................................................................... 40
Customer Form Design..................................................................................................................... 41
Booking Form Design ....................................................................................................................... 41
Buses Report .......................................................................................................................................... 42
chapter six ................................................................................................................................................... 43
Introduction ........................................................................................................................................... 43
Implementation ..................................................................................................................................... 43
Code of the Login form..................................................................................................................... 43
Code of the booking .......................................................................................................................... 44
Code of the Customer ....................................................................................................................... 45
Testing Login form ........................................................................................................................... 46
Testing customer form ...................................................................................................................... 47
Testing Booking form ....................................................................................................................... 48
CHAPTER SEVEN .................................................................................................................................... 49
Bibliography .......................................................................................................................................... 49
References ................................................................................................................................................... 49

pg. 8
 CHAPTER 1

1.0 Introduction:
This introductory chapter sets the frame for the research.
It begins with an Introduction to the study and looks at the background of the project.
It goes further to Identify the research problem, the research objectives and questions,
scope of the system and project organization.
A transportation management system (TMS) is specialized software for planning,
executing and optimizing the shipment of goods. Users perform three main tasks in a
TMS: Find and Compare the rates (prices) and services of carriers available to ship
a customer's order, book the shipment and then track its movement to delivery. A
TMS is a necessity for any company with direct responsibility for transporting a
significant Volume of goods or hiring service providers to do the job. The
complexities of today's supply Chains, transport modes and regulations make the task
nearly impossible without Computerization.

1.1 Background of the project

The Transportation and Logistics Management System (T&LMS) is an automated
system that is used to manage passenger information and its administration. It is
meant to provide the Administration and Staff, with information in real-time to make
their work more interesting and less stressing. This project will automate the daily
operations of Safar Same Transportation Hargeisa Branch. The project keeps safety
of the passenger and employee details. Safar-Same Transportation and Logistics.
Is a new unique and exceptional company initiated by group of professionals in 2012
the company management team has substantial relevant proven and practical
expertise. Some of this team has over ten years of experience about this particular
business sector. Our objectives are to provide high quality, safe, comfortable, reliable
and affordable of variety of transportation services in Somaliland.
Nowadays, system of the transportation uses the manual system where needs to fill
all records in a file from the system users to the technical writers. This work is handled
by staff to fill all the transport reservation form with handwriting This will give
difficult to find file when the same customer come to book transport again.
Transport Management System (TMS) is a system to effectively manage
information about customer profile and make reservation easily. It also
manages the transportation system for other communities Customer also can
see types of transport that can be booked with faster and make the choice of
the transport. Customer does not need to register many times because the

pg. 9
 profile customer has been saved into database. This system focus as a reservation
form and latest information about the transport availability.
The information management system provides to implement process of Transport
Management System (TMS) reservation form that user request. The data that must
be sent include pick-up date, drop-off date, transport types, how long to rent, method
of payment, and etc. This data must be sent to supplier rental companies. Then,
information management system also controls the user request that must be completed
by customer. Customer’s profile can be updated any time. When user completes it,
the data must be submitted to the rental companies system.

1.3 Problem of the Statement

Transport Management System (TMS) has design to manage the booking and
maintenance of growing transport. Problem occurs when transports have mechanical
problems are rented, vehicles that have been double booked and there have been cases
when the wrong vehicle has been rented when it has been returned and not serviced.
The current system has redundancy, where data cause by the manual system which
uses paper to fill the information. Data is also not being kept in the secure location.
Information lost is common by using manual system. The efficient planning and
management of an organization's transport system is the key to providing a proficient
transport network. Transport systems should ensure accessibility at an acceptable
level of safety and comfort, in an environment-friendly manner for the movement of
people. Additionally, it encourages patterns of growth and economic. The major
challenge faced Safar Same using manual system they are:

➢ Currently the type of system being used at the counter is an internal system
which
➢ Is manually used in selling the bus tickets. The problems facing the company
are
➢ that customers have to go to the counter to buy bus ticket or ask for bus
schedule customers will also have to queue up for a long time in order to
secure a bus ticket
➢ And will also need to pay cash when they buy the bus ticket update
➢ No online buses schedule

pg. 10
1.3 Project objectives
➢ To develop a transportation and Logistics management system is very
important role in any formal organization, because computer works faster and
accurate than human.
➢ To change Manual Data into Automatic Data customer
➢ To register new customer, employee.
➢ We will create search passengers
➢ The purpose of developing the transportation and logistics system of any
organization is that to make easy to management to store a large number of
data and reports into the computer.
➢ The purpose of developing the transportation and logistics system of any
organization is that to make easy search to management to store a large
number of data and reports into the computer.

General objectives
Travel management systems and applications are used for capturing and research
information such as customer travel, shipping Goods. A business that has clean,
correctly formatted and accurate data will be able to provide a good level of service
as well as saving time and money
Develop Transport Management System (TMS) to adapt Safar-same Modern to book
transport and save data easily.
To assist Safar-Same transport managers to efficiently plan and manage their
organizations.
To save user data and information efficiently in real-time data retrieval

Specific Objectives
We hope This Project to be Acceptable and Successfully.
All supply and demand quantities are given in whole numbers.
This system help them the average number of passengers.
Tickets is safer, faster, more dependable, and less expensive. Furthermore, this
concept can be applied by other bus companies to make it easier for their customers.
Customers value it since it allows them so verify the availability of bus tickets.

1.4 The scope of the project

This Bus Transportation system is generic web portal application that aids customers
to reserve a seat in a certain bus, anytime and anywhere and variety of buses that
satisfy the customer’s requirements are provided.
This system replaces manual bookings which has no transparent bookings.

➢ It is also help company to get route's information’s that passing cities.

➢ Finally, it records
➢ Bookings

pg. 11
 ➢ Customers
➢ Driver's info
➢ Routes

1.5 Significance of the study

This study will provide better understanding about the projects and Safar-Same of the
Safar-Same Management System. It is important to the sense that is explores the
major problems encountered by the Traffic Officials, Motorists and the Public.

1.6 Data Collection Methodology

So as to collect data from Modern coast bus ticket booking system as well as its client
appropriate methods of collecting data were needed. These techniques included the
following:
1.1 Observation
This involved the researcher going to the field of study, making direct watch on the
way the organization under study operates, identifying the possible drawbacks of the
operating system analyzing the problems and developing a solution based on the
observations made. This technique was employed since it provides a first-hand
information which is quite reliable and accurate since the method provided a quick
overview of the system. It is the most effective technique.
1.2 Interviews
This is a direct face to face conversation between the system analyst (interviewer)
and the users of the system. This was used where the respondents were few in order
clarifying and verifying gathered facts. This technique was important to use since
some data could not be collected by direct observation unless interviewed, hence it
helped in enriching the data for quality processing.
1.3 Questionnaires
A questionnaire refers to a set of questions prepared by the person collecting data in
a paper which is issued to specific people who in turn respond to the questions
privately without the presence of the interviewer. Once the respondent is through,
he/she will issue the answers back to the person collecting the data. This technique
was also important because some interviewees
we’re not confident enough to respond to the question at the interview panel during the
interview and therefore a questionnaire best suited such people

pg. 12
1.7 System development method
We use waterfall model it’s very simple to understand a use in water full model each phase
must be complete fully before next phase can begin.

Expected outcome
1. The developed system will improve the work performance

2. The customer information will be more secure

3. This the system will increase the number of the customers

4. This system will reduce errors

5. It’s easy to use this system

1.8 Project Management

Chapter One: discuss on introduction of this project. This chapter includes
Introduction,
Background, Problem statements, purpose of the study, Objectives of study, Research
Questions, Scope of the study, Significance of the study developing methodology and
project organization

pg. 13
1.9 WBS and Gant Chart
first Allah is grateful to us for enabling us to start a project that we today date 4 April
started and it took us to finish at a time of 4 days thanks to God for us to finish that
time with the task we were doing ability to catch up during that time and finish this
chapter today we have completed and date 8 April

GANT CHART:

pg. 14
 CHAPTER TWO
Literature Review

2.0 Introduction
It is a process of collecting and interpreting facts, identifying the problems, and
decomposition of a system into its components or Data analysis is defined as a process
of cleaning, transforming, and modeling data to discover useful information for
business decision-making. The purpose of Data Analysis is to extract useful
information from data and taking the decision based upon the data analysis. System
analysis is conducted for the purpose of studying a system or its parts in order to
identify its objectives. It is a problem-solving technique that improves the system and
ensures that all the components of the system work efficiently to accomplish their
purpose. You are beginning a journey that will enable you to build on every aspect of
your education and experience. Becoming a systems analyst is not a goal; it is a path
to a rich and diverse career that will allow you to exercise and continue to develop a
wide range of talents Today, the internet has become an important information
resource

pg. 15
 2.1 Development Software

Tripper Bus
Tripper Bus offers travelers reliable luxury transportation between New York City
and the Washington, DC Suburbs of Arlington, Virginia and Bethesda, Maryland.
Our fleet is fully equipped with the latest in comfort and convenience to include wi-
fi, electrical outlets and complimentary entertainment in the form of movies and tv
series viewable on your personal device while traveling.

pg. 16
VamoosBus

Our Family formed Vamoose Bus in February 2004 to fill a hole in the market that you, our
customer, identified. You wanted a convenient, quiet, clean ride on a comfortable bus. You sought
personal service and a live person to talk to, not a recording machine. In a nutshell, you wanted to
be treated like family, and we listened.
We currently offer daily service between New York City and the following 3 cities in the
Washington, DC Metropolitan area: Bethesda, MD; Arlington (Rosslyn), VA & Lorton, VA.
Carrying an average of more than 6,500 passengers a week, Vamoose Bus has developed a solid
reputation among travelers in the NYC and DC metro area, who recognize the company’s devotion
to customer service, and many of whom ride the service on a weekly basis.
Our motor coach providers are proud of their safety records, receiving high safety ratings from the
U.S. Department of Transportation. All coaches are fully licensed, insured, and routinely inspected
and our drivers all have superior driving records.
In addition to our main NYC-MD/VA bus route, Vamoose Bus also features the luxury Vamoose
Gold Bus service, a niche in the bus industry; Vamoose Bus Rewards, a rewards program for
frequent-travelers; luggage-storage service at our NYC bus stop; and sprinter-van limo
transportation in NYC.

pg. 17
 .

CheckMyBus

CheckMyBus is a search engine for intercity bus trips all over the world, and we help
you find the best offers, cheapest tickets, and most convenient journeys. Our team
reflects this, bringing expertise from across the globe to provide optimal service,
while catering to the specific needs of regional markets. As the company expands, we
will continue our commitment to a diverse and global workplace to best serve users
all over the world.

pg. 18
pg. 19
2.2 Comparison of the existing systems

Chechmybus VAMOOSE CHECKMYBUS

System Only users can access

Access Users can access the the system
system from all the Accesses by all type
Specific time
world of users.

Scalability Can be accessed with any The access can be Difficult to access if
condition of internet speed controlled and no too many users access
or quantity of users. problem with the at the same time.
quantity of the users.

2.3 Summary
As has been detailed above, there is no general agreement on the appropriate way
of storing and maintaining the customers’ information records around the world but
every organization develops its own system based on their needs and necessity. Every
organization or company has its own strategy which they use to shape the exchange
relationship between themselves and their customers.
All these systems are willing to solve the problem of keeping records on physical
processes but they are different in the way of solving that problem.
Safar Same also has a lot of the same features with these existing systems described
above but at the same time we would apply some new changes to fit the requirements
of the company.

pg. 20
 Chapter three
2.4 Research methodology
Research methodology is the path through which researchers need to conduct their
research. It shows the path through which these researchers formulate their problem
and objective and present their result from the data obtained during the study period.
The research methodology is the general research strategy that outlines the way in
which research is to be undertaken and among other things, identifies the methods to
be used in it.
2.5 Data collection methodology
Data collection is the process of gathering and measuring information on targeted
variables in an established systematic fashion, which then enables one to answer
relevant questions and evaluate outcomes. Data collection techniques like this: -
➢ Questionnaires and Surveys
➢ Focus Groups
➢ Interview
➢ Observations
➢ Documents and Records We choose Interview technique as one of our data
collection methods.

2.6 Existing System

Safar-Same Modern Bus previous system was kind of hard to Calculate also to
manage and control the daily activity during work as it was Handling by hand and
written papers, so this nowadays the officers would not Like to work that hard they
need smart controlling to continue smoothly Their Work. Therefore, there were many
problems and efforts that faced this company to handle it so easier than before because
this ex-system can consume time and We can see many errors that can occur during
work so far this system the Company is about to leave to begin the smart system.

2.7 Weakness and the strength of the existing system

➢ Weakness of the existing system
➢ Not user-friendly.
➢ Vulnerable errors.
➢ Time consuming.
➢ Poor processing.

pg. 21
 ➢ Strength of the existing system
➢ Intangible asset.
2.8 User Requirements
✓ User must have knowledge of computer skills
✓ User must have knowledge in its field
✓ User must also have basic knowledge of English too
✓ Comfortable of working with computer
✓ Experience in the usage of computer and office software packages and knowledge
of database package, experience of web base management systems.
2.9 Business Rules
The system must be capable of registering any customer who wants to give feedback.
The system must not register a customer with the same information i.e. Ali any
Duplicates.
Software Requirements
❖ WIN XP / 10 / or above of the operating system.
❖ Apache server as an example.
Front-end and back-end selection We are selected in programming language
that supports in online applications and they are Front-end
o HTML and CSS Back-end
o PHP and MYSQLI
Software Requirements also have two types: -
Functional requirements A Functional Requirement (FR) is a description of the
service that the software must offer. It describes a software system or its component.
A function is nothing but inputs to the software system, its behavior, and outputs. It
can be a calculation, data manipulation, business process, user interaction, or any
other specific functionality which defines what function a system is likely to perform.
Functional Requirements are also called Functional
Here are some functional requirements of the system: -
➢ The system should maintain a quantity record.
➢ The system must keep the record of feedback type.
➢ The system must have the ability to delete and update the record.
➢ The system also must have security to prevent data.
➢ The system must search the area.
Non-Functional requirements
Non-Functional Requirement (NFR) specifies the quality attribute of a software
system. They judge the software system based on Responsiveness, Usability,
Security, Portability and other non-functional standards that are critical to the success
of the software system. Example of nonfunctional requirement, “how fast does the

pg. 22
 website load?” Failing to meet non-functional requirements can result in systems that
fail to satisfy user needs,
The non-functional requirements of the system are described as follows: -
1) Security: One of the most important non-functional requirements is security.
Security requirements can come in many different forms:
a. Privacy: Requirements can dictate protection for sensitive information.
Some types of privacy requirements include: data encryption for database
tables, policies regarding the transmission of data to 3rd parties (e.g.,
scrambling user account numbers), etc... Sources for privacy requirements
could be legislative or corporate.
b. Physical: These requirements relate to the physical protection of the
system. Other types of physical requirements include items such as
elevated floors (for server cooling), fire prevention systems, etc.…
c. Access: Access requirements define account types / groups and their
access rights. An example of an access requirement could be to limit each
account to one login at a time or to restrict where an application can be
deployed or used
2) Reliability: The system must be reliable and meet user needs requirements.
Increasing the performance of the software will improve the reliability of the
software and storing backup data can increase reliability of the software.
3) Performance: The system must be in good performance and measuring all
operations must take a few seconds
4) Maintainability: The system must be maintainable if some errors occur.
5) Scalability: The system should accept future expansion.
6) Usability: The system must be user-friendly and easy to use.

3.0 Feasibility Study

A feasibility study is a preliminary study undertaken before the real work of a project
starts to ascertain the likelihood of the project's success. It is an analysis of possible
solutions to a problem and a recommendation on the best solution to use. A feasibility
study is defined as an evaluation or analysis of the potential impact of a proposed
project or program. A feasibility study is conducted to assist decision-makers in
determining whether or not to implement a particular project or program
Here the feasibility study can be performed in four ways such as: -
➢ Economic feasibility study.
➢ Operational feasibility study.
➢ Technical feasibility study.
➢ Schedule feasibility study.

pg. 23
Economic feasibility
This is a very important aspect to be considered while you are developing a project.
We decided the technology based on the minimum possible cost factor.
• All hardware and software have to be borne by the Customer
• Overall, we have estimated that the benefits the is going to receive from the
proposed system will overcome the initial costs and the later on running cost for the
system.
Operational feasibility
The proposed system is GUI based and that is very user-friendly and all inputs to be
taken self-explanatory even to the layman. Besides, proper training has to be
conducted to let the users know the essence of the system to the users so that they feel
comfortable with the new system.
Technical feasibility
This included the study of a function, performance and constraints that may affect
the ability to achieve an acceptable system. For this feasibility study, we studied
complete functionality to be provided in the system.
We use: -

Front end: pip.

Back end: MySQL.

Schedule feasibility
Schedule Feasibility is defined as the probability of a project to be completed within
its scheduled time limits, by a planned due date. If a project has a high probability to
be completed on-time, then its schedule feasibility is appraised as high. In many cases
a project will be unsuccessful if it takes longer than it was estimated: some external
environmental conditions may change, hence a project can lose its benefits,
expediency and profitability. If a work to be accomplished at a project does not fit the
timeframes demanded by its customers, then a schedule is unfeasible (amount of work
should be reduced or other schedule compression methods applied). If the project
managers want to see their projects completed before they can lose their utility, they
(project managers) need to give proper attention to controlling their schedule
feasibility: to calculate and continually reexamine whether it is possible to complete
all amount and scope of work lying ahead, utilizing the given number of resources,
within required period of time. Schedule feasibility study.
3.1 System Development Life Cycle (SDLC)
SDLC or the Software Development Life Cycle is a process that produces software
with the highest quality and lowest cost in the shortest time possible. SDLC provides
a well-structured flow of phases that help an organization to quickly produce high-
quality software which is well-tested and ready for production use.

pg. 24
 ✓ Stages and Best Practices of SDLC Following the best practices and/or stages of
SDLC ensures the process works in a smooth, efficient, and productive way.

Identify the Current Problems

❖ Plan
“What do we want?” In this stage of the SDLC, the team determines the cost and
resources required for implementing the analyzed requirements. It also details the
risks involved and provides sub-plans for softening those risks.
❖ Design
“How will we get what we want?” This phase of the SDLC starts by turning the
software specifications into a design plan called the Design Specification. All
stakeholders then review this plan and offer feedback and suggestions. It’s crucial to
have a plan for collecting and incorporating stakeholder input into this document.
Failure at this stage will almost certainly result in cost overruns at best and the total
collapse of the project at worst.
.

pg. 25
❖ Build
“Let’s create what we want.” At this stage, the actual development starts. Every
developer must stick to the agreed blueprint. Also, make sure you have proper
guidelines in place about the code style and practices. For example, define a
nomenclature for files or define a variable naming style such as camel Case. This will
help your team to produce organized and consistent code that is easier to understand
but also to test during the next phase.

❖ Code Test
“Did we get what we want?” In this stage, we test for defects and deficiencies. We
fix those issues until the product meets the original specifications. In short, we want
to verify if the code meets the defined requirements.

❖ Software Deployment
“Let’s start using what we got.” At this stage, the goal is to deploy the software to
the production environment so users can start using the product. However, many
organizations choose to move the product through different deployment environments
such as a testing or staging environment. This allows any stakeholders to safely play
with the product before releasing it to the market. Besides, this allows any final
mistakes to be caught before releasing the product.

pg. 26
 CHAPTER FOUR

3.2 introduction
This chapter focuses on the system analysis of the proposed system (TMS), the
system requirements are determined in the system analysis phase.
The system design provides an overview of both system and architectural design for
the proposed system to help users to understand the system.
The transport system will be used by (Object oriented methodology).
Object Oriented Methodology (OOM) is a system development approach
encouraging and facilitating re-use of software components. With this methodology,
a computer system can be developed on a component basis which enables the
effective re-use of existing components and facilitates the sharing of its components
by other systems
The Unified Modeling Language (UML) is a general-purpose, developmental,
modeling language in the field of software engineering that is intended to provide a
standard way to visualize the design of a system

3,3 UML diagrams

Use case diagram
Sequence diagram
Class responsibility collaborator (CRC) diagram.

3.4 Use case diagram

A use case diagram at its simplest is a representation of a user's interaction with the
system that shows the relationship between the user and the different use cases in
which the user is involved.
A use case diagram can identify the different types of users of a system and the
different use cases and will often be accompanied by other types of diagrams as well.
The use cases are represented by either circles or ellipses.

pg. 27
pg. 28
Authentication Sequence Diagrams

pg. 29
Bus Sequence Diagrams

pg. 30
Customer Sequence Diagrams

pg. 31
Booking Sequence Diagrams

pg. 32
3.6 Class diagram

pg. 33
3.7 User Interface prototyping
User interface prototypes are an essential part of designing user flaws and interfaces
they allow
designer to show their design an interactive and engaging product
Directory examples of usage are part of the design of the flow users and internet sites
allow
Designing the system and presenting the ideas on which they are based and claiming
to present the
design through them Good product design for anyone involved in experimenting with
different
designs using real users in the design process Can also be used to engage and
coordinate project
sponsorship and practical support.

pg. 34
 CHAPTER FIVE
System Design
3.8 Introduction
This chapter will cover the different types of system designs. Software design is a
process to transform user requirements into some suitable form, which helps the
programmer in software
coding and implementation.
To get the best design we will cover these two design stages.

3.9 Database Design

A properly designed database provides you with access to up-to-date, accurate

information. Because a correct design is essential to achieve your goals in working
with a database, investing the time required to learn the principles of good design
makes sense. In the end, you are much more likely to end up with a database that
meets your needs and can easily accommodate change.

4.0 Normalization in database

Normalization is the process of organizing data in a database. This includes creating
tables and establishing relationships between those tables according to rules designed
both to protect the data and to make the database more flexible by eliminating
redundancy and inconsistent dependency. Redundant data wastes disk space and
creates maintenance problems. If data that exists in more than one place must be
changed, the data must be changed in exactly the same way in all locations.

pg. 35
First normal form
In order to make the first normal form of my database, horizontal redundancies are
removed. Similarly,
I practice the primary key to make each row unique. There are no two columns
holding the same information in my relational database. Also, there is no single
column holding more than one item. For example in the advisor table there is no
redundant data as every column holds specific information about the advisor. Note: I
did not use multiple fields in a single table to store similar data.
Second normal form
Each and every attribute in a table is fully functionally dependent on the primary key.
For example, in the thesis table all the attributes of the table cannot functionally
operate if the thesis id (PK) is missing. Note: Records should not depend on anything
other than a table's primary key.

4.1 Database dictionary

1.Booking
column type null comments
Booking_id Int(11) no

Customer_id Int(11) no

Rout_id Int(11) no

Customer_route Varchar (250) no

Booked_amount Int (100) no

Booked_seat Varchar (100 no

pg. 36
2.Buses
column type null comments

bus_no int(11) no

bus_assigned tinyint(1) no

bus_created datetime no

3.Customer
column type null comments
customer_id varchar(11) no

customer_name varchar(50) no

customer_phone varchar(50) no

Customer_created datetime no

4.Routes
column type null comments
rout_id int(11) no

Bus_no varchar(155) no

route_cities to cities varchar(255) no

Route_dep_date Date no

Route_dep_time Time no

Route_step_cost Int(100) no

pg. 37
5.Driver
column type null comments
Diver_id Int(11) no

Diver_name Varchar(50) no

Diver_phone Varchar(50) no

Diver_address Varchar(50) no

Bus_no Int(11) no

6.Seats
column type null comments
bus_no varchar(155) no

Seat_booked varchar(255) yes null

7.Users
column type null comments
user_id int(11) no

user_name varchar(20) no

user_password varchar(20) no

pg. 38
4.2 ER Diagram

Tables of the database

pg. 39
4.3 Interface design
User interface (UI) design is the process designers use to build interfaces in software or computerized
devices, focusing on looks or style. Designers aim to create interfaces which users find easy to use and
pleasurable.

Dashboard

pg. 40
Customer Form Design

Booking Form Design

pg. 41
Buses Report

pg. 42
 chapter six
Introduction
In this chapter, we are presenting the most important part of the development of the
proposed fuel
station which is converting the whole tasks done in the previous phases into real time
working system, it
represents the different standards carried out in the coding of the system and the
system testing functionalities
Implementation
Implementation System implementation is the process by which system design is
turned into a working system. Implementation must be planned carefully to the
proposed system to avoid any unanticipated problems. This system needs to plug in
the organization's network, so the system’s visitors can access it anywhere after the
visitors logged into the system. In the thesis record management system we classify
the applications into these modules.

Code of the Login form

pg. 43
Code of the booking

pg. 44
Code of the Customer

pg. 45
Testing Login form
St_no Action input Expected Actual autput status
output

1 Eccess the Safar-same Bookings The website The webiste pass

website

2 User click the Login model form The login The login pass
administrtor page page
login button

3 User click the Button=login Please fill this dashboard Fail

login button out field
without enter
any data

4 User enter Username=admin Dashboard dashboard pass

username and
passoword of Passowd=password@123
the system

pg. 46
Testing customer form

St_no Action input Expected Actual autput status

output

1 Eccess the Safar-same The website The webiste pass

webite Bookings

2 Admin customers The customer The customer form pass

customer form
button in the
dashboard

3 Admin click Button Please fill this Cutomer Fail

submit in the :submit in out field added
customer customer
form without
enter any
data

4 Admin enter Button: add customers customers pass

customer customer
detial in order
to register
new
customer

pg. 47
Testing Booking form

St_no Action input Expected Actual autput status

output

1 Eccess the Safar-same The website The webiste pass

webite Bookings

2 Admin register Button-booking The booking The booking pass

new booking form form

3 Admin click Button :submit Please fill this Booked added Fail
submit button in booking out field
in booking
without enter
any valid data

4 Admin enter Button: add booking booking pass

valid booking booking
details

pg. 48
 CHAPTER SEVEN
Bibliography

References
altexsoft.com/blog/transportation-management-system. (2022, 8 7).
www.altexsoft.com/blog/transportation-management-system. Retrieved from
www.altexsoft.com/blog/transportation-management-system:
https://www.altexsoft.com/blog/transportation-management-system

creately. (2022, 8 7). creately.com/. Retrieved from http//:creately.com/: http//:creately.com/

https://www.sap.com/insights/transport management system . (2022, 8 8).

https://www.sap.com/insights/transport management system . Retrieved from
https://www.sap.com/insights/transport management system :
https://www.sap.com/insights/transport management system

visual-paradigm.com. (2022, 8 7). https://www.visual-paradigm.com/. Retrieved from

https://www.visual-paradigm.com/: https://www.visual-paradigm.com/

w3schools. (2022, 7 4). Retrieved from https://www.w3schools.com: https://www.w3schools.com

w3schools. (2022, 8 7). https://www.w3schools.com/. Retrieved from www.w3schools.com/:

https://www.w3schools.com/

pg. 49
References
. Database Analysis. 2013. Database Analysis. [ONLINE] Available at:
HTTP://db.grussell.org/section004.html [Accessed 17 October 2013]. . (2022, 8 4). . Database
Analysis. 2013. Database Analysis. [ONLINE] Available at:
HTTP://db.grussell.org/section004.html [Accessed 17 October 2013]. . Retrieved from . Database
Analysis. 2013. Database Analysis. [ONLINE] Available at:
HTTP://db.grussell.org/section004.html [Accessed 17 October 2013]. : . Database Analysis. 2013.
Database Analysis. [ONLINE] Available at: HTTP://db.grussell.org/section004.html [Accessed 17
October 2013].

. https://blog.intekfreight-logistics.com/best-transportation-management-software-tms. (2022, 7 7). .

https://blog.intekfreight-logistics.com/best-transportation-management-software-tms.
Retrieved from . https://blog.intekfreight-logistics.com/best-transportation-management-
software-tms: . https://blog.intekfreight-logistics.com/best-transportation-management-
software-tms

. https://blog.intekfreight-logistics.com/best-transportation-management-software-tms. (2022, 7 7). .

https://blog.intekfreight-logistics.com/best-transportation-management-software-tms.
Retrieved from . https://blog.intekfreight-logistics.com/best-transportation-management-
software-tms: . https://blog.intekfreight-logistics.com/best-transportation-management-
software-tms

pg. 50