Professional Documents
Culture Documents
UNIVERSITY
July 2021
Adama
i
Contents
1. Introduction..............................................................................................................................1
2. Objectives.................................................................................................................................2
2.1 General Objectives............................................................................................................2
2.2 Specific Objectives...........................................................................................................2
3. Project Scope............................................................................................................................2
4. Overall Description..................................................................................................................3
4.1. Product Perspective...........................................................................................................3
4.2. Main Components of the TMS..........................................................................................3
5. TMS Features...........................................................................................................................6
6. Functional Requirements..........................................................................................................6
7. Design.......................................................................................................................................7
7.1 Use case diagrams.............................................................................................................7
7.2 Class Diagram.................................................................................................................10
7.3 ER Diagram.....................................................................................................................11
ii
1. Introduction
Transport Management System refers to the process of managing activities, which
is related to vehicle that means vehicle distribution to different employee transport
requests, maintenance requests and maintaining vehicles and permanent recording
of every events that happens around ASTU vehicles. In ASTU, the Transport
Management is handles by the transport team and the transport maintenance team,
which are found under the general service directorate.
The duties currently performed by the General Service Directorate include
managing employee transport request, managing vehicle maintenance and
managing vehicle transport distribution and provide daily-based services including
emergency service with the help of different paper-based formats. In addition to
this, the office is responsible to outsource vehicle maintenance and depending on
the shortage of vehicle transport delivery can be outsourced. The current system is
largely paper-based and the General Service Directorate Office does not have a
database management system. The absence of a database management system
affects performance, proper resource utilization and effectiveness because of
operational and productivity constraints associated with the current manual system.
The current system suffers from inadequate security, limited file sharing, and lack
of data integrity. The absence of a database management system also affects the
collection, analysis, and generation of reports from aggregated data. In addition,
there is no auditable electronic record of what was requested, what the
maintenance history of a given vehicle was and what spare part is available in a
store at a given time. In order to improve operational efficiency and effectiveness,
as well as resolve the issues identified above, General Service Directorate Office
has decided to have a well-organized web-based system with its central database
management system.
1
2. Objectives
2.1 General Objectives
To develop a transport management system that changes the manual system into
automated system for ASTU.
3. Project Scope
The Transport Management System will enable us ease of transport request and
maintenance request for employees, to establish vehicle maintenance history and
requests and assign vehicles for the requests.
The scope of Transport Management System is listed below
o Registration of Vehicle
o Registration of items
o Vehicle Maintenance Request
o Vehicle maintenance request approvals
o Assign mechanics for vehicle maintenance
2
o Order Item for Maintenance
o Item Request for maintenance purpose
o Deliver Item for Maintenance
o Vehicle request
o Request approvals
o Assign Vehicles
o Assign Driver to Vehicle
o Assign Vehicle to Work unit
o Generate different types of Report
4. Overall Description
4.1. Product Perspective
3
Maintenance Request
Maintenance request
Approvals
Assign mechanics
Order items for maintenance
Item request for maintenance
Deliver items for maintenance
Maintenance Request
Approvals
4
Vehicle Transport Request
Vehicle Requests
Approve Vehicle Requests
Assign Vehicle / Provide transport
Vehicle Requests
Approvals
User Management
Users
Roles
Permissions
Menus
Sub Menus
5
Vehicle Management
Work Unit Vehicles
Transport Vehicles
5. TMS Features
The proposed TMS shall include the following features.
- Registration of Vehicle
- Register different types of item
- Vehicle Maintenance
- Deliver item
- Requests
- Assign Vehicle to request
- Assign Driver to Vehicle
- Assign Vehicle to Work unit
- Generate different kind of Report
- Register an item
6. Functional Requirements
- To employee request item
- Generate different kind of Report
- Update number of item/balance
- Add a new property
- Request item/property for utilization
- Approvals for requests
6
7. Design
We started designing the system by analyzing the requirements, using UML diagrams we
represented the functionality and how the data flows in the system. And an ER diagram to
represent the database of the system. Following are the diagrams.
A use case diagram is usually simple. It does not show the detail of the use cases:
It only summarizes some of the relationships between use cases, actors, and
systems
add items/vehicles
Work Unit
view item/vehicle info
7
request
approve
assign
order
deliver
maintaine
8
request
approve
Work Unit
assign
Employee
9
7.2 Class Diagram
-id
-employee_id
--- Items
- -id
--- -name
-item_type_id
---
Employee -register()
-deliver()
-id ---
-personal_name
-father_name
-grand_father_name Mechanics
...
-memberName
-request()
-id
...
-employee_id
---
-maintain()
---
10
7.3 ER Diagram
1 has 1
Work Units * request n Vehicles Driver request Maintenance
wu_id
start date start date
Types
name n maintened by
id
assign is
an
start date
duration
1 Mechanics emp_id
1
n
n
Employee 1
duration
is
has an order
name
wu_id start date
deliver n Items
id name
11
12