• First, we would like to thank Almighty

GOD. Secondly, we would like to

express our gratitude to our teacher
Mr. Wakjira Bekele for his help,
willingness, and commitment in giving
his precious time to help us.
FMS (Fleet management system )
 Fleet management is one of the core functions of any
logistics company
In Ambo University, employers use transportation or
get service from university itself.
Currently the university use manual system like
scheduling to give service
During they use this manual system they couldn’t and
consumed
02/13/24
 By observing those problems this project is going to
solve the above problems
 We will design and implement a working automated
model of the system in the problem

02/13/24
 Difficulty in searching and updating data
 Data Redundancy under different titles about
the same object
 The process of generating report about
individual item has become a challenge in the
existing system
 Manual data handling

02/13/24
 Is to Develop:
User friendly
Easily accessible
Centralized Web based Fleet management for
Ambo University

02/13/24
02/13/24
02/13/24
02/13/24
02/13/24
9
10
11
02/13/24
 Changing the manual system in to web-based system
without affecting the structure of the organization.
 Developing easily accessible information/documents
that is clear to employees when accessing data in 24/7
model.
 To avoid redundancy of records in the working
system as the proposed system provides mechanisms
to sort files in database system.
 To avoid wastage of paper work on records in the
system
02/13/24
02/13/24
02/13/24
02/13/24
02/13/24
02/13/24
02/13/24
02/13/24
 CONT’D

02/13/24 23
 Login Validation Account Main page
Actor <<UI>> <<controller>> <<DB>> <<UI>>

Click

enter check validty

username &
password invalid
(username&
password)
valid

Display

Figure 3 Sequence diagram for Login form

02/13/24
 Enter user name &
password

Incorrect
Error message

Correct
Display vehicle
schedule page

Search vehicle information

Fill required data

about the vehicle

Incorrect
Incorrect input

Correct

Assign vehicle

02/13/24
02/13/24
Figure 18 State chart diagram for login
 Design Goals
The proposed has the following goals:-
Performance: The system should be able to give response
(error message) when the user enters incorrect input.
Availability: The system should be available for twenty four
(24) .
End user: The system should provide user friendly
Usability:-the extent to which a product can be used by
specified users to achieve specified goals.
Modifiability:-The system should be modifiable for further
modification and enhancement of the application.

02/13/24 27
25
 Proposed software architecture
 The proposed system is expected to replace the existing
system by an automated system.
 The architecture used for the system is a three (3) tier.
 The three tier architectures consist of three components
distributed in 3 layers: client (requester of services) the
business logic (data handler) and server (provider of
services).

02/13/24
2628
 Proposed Architecture

02/13/24 27
29
 Subsystem Decomposition
 The fleet management system is decomposed into the following
subsystems.
 Administrator subsystem: Control User information Updating
, Adding, Etc.
 General Service manager subsystem: Controlling The overall
Fleet system
 Scheduler subsystem: Scheduling, Fill fuel cost
 Property Worker: giving Coupon Number
 Driver: Fuel request, Exit request, View schedule.

02/13/24 30
28
 Implementation and Testing
 Final phase of implementation is testing.
 Testing is a process to show the correctness of the program.
 Unit Testing
 Unit testing is every module of the System is separately tested.
 Every Steps of the system is tested.
 System Testing
 It is the final step of testing.
 Members tests the entire system as a whole with all forms, code,
modules.
 This form of testing is popularly known as Black Box testing or
System tests.
02/13/24 29
31
 Cont’d
 Integration testing
 The process of testing the interaction between different modules or
components of a software application.
 Functional Testing
 Functional testing focuses on validating the software application's
features, functions, and capabilities, ensuring that they work as
specified in the requirements.
 Performance testing
 The software performance, such as its responsiveness, speed, and
stability, under various load conditions.
 The performance and reliability requirements when subjected to
different levels of user traffic and system load.

02/13/24 32
30
Recommendation and conclusion

02/13/24
Recommendation and conclusion

02/13/24
02/13/24
02/13/24
34