The document presents a vehicle management system that includes project objectives, requirements, and testing procedures. It outlines functionality for both admin and user modules, such as managing vehicle and driver details, and booking car trips. Additionally, it describes the project's budget, task identification, and provides visual tools like PERT and Gantt charts for project management.

1. • Welcome To Our
Presentation
1
Topic:
VEHICLE MANAGEMENT SYSTEM
Contact us: +91 9873725832

2. Overview:
Dhaka vehicle system4/17/2017
2
• Project Requirements
• Use case diagram
• Project Objective
• Project Scope
• Task identify
• PERT chart-Critical path analysis-Gantt chart
• Project Budget

3. Requirements:
• Introduction
A Software requirements specification (SRS) is a comprehensive description of
the intended purpose and environment for software under development.
SRS defines how an application will interact with system hardware,
other programs & human user in a wide variety of real world situations.
i. Functional Requirement
ii. Non-Functional requirement
3

4. Functional & Non-Functional
Requirements: 4
Functional Requirement:
Programming Languages : Java (jdk1.5).•
•
•
•
WebTechnologies
Database
Server
: Html, JavaScript.
: My_sql
: Tomcat Apache5.0
Non-functional Requirement:
Processor : duel core•
•
•
Hard Disk : 512 MB
Ram : 256 MB

5. Using Tools: 5
The software used in this project
is:
 OS
 Data Base
IDE
Browser
Windows
MS-SQL Server
NetBeans
Google Chrome

6. Features: 6
ADMIN:
• View/Edit/Delete Vehicle Details
• View/Edit/Delete Driver Details
• Booking Status Detail
USER MODULE
• Login/Registration of User
• Take a Car trip (Google Map Integration)
• View Car Details
• Car Booking

7. Use case Table: (Vehicle System) 7
Level 0 Level 1 Level 2 Actor
Account Sign in
Sign out
User
Admin
Vehicle System Search Vehicle name
Route name
Bus stop
User
Admin
Report About System, route
Request for Addvehicle
User
Update Add vehicle
Add route
Add Bus stop
Change Location
Admin

8. Scope & Objective For Project:
To register and keep the information about all vehicles.
 To build up a system that provides and generates the summary
Report from the database records in order to get the whole view
about the vehicles amounts.
Summarize the accidental records and responds for the
further improvements.
A web based tool where user can search for additional information
of the vehicle.
8

9. Task Identity & procedure: 9
• Requirement analysis :
As we are doing this by ourselves not for a organization or for a company. So we collect
requirement by ourselves by brainstorming and questioning other people. Later we discus
among us and fixed our requirement.

10. Task Identity & procedure:
10
• Database Design:

11. Task Identity & procedure: 11
• User Interface:

12. Task Identity & procedure:
User Interface:
4/17/2017 Dhaka vehicle system
12

13. Task Identity & procedure: 13
• Quality Assurance:
• Unit Testing:
Unit testing focuses verification effort on the smallest unit of software design that is the module.
Using procedural design description as a guide, important control paths are tested to uncover
errors within the boundaries of the module. The unit test is normally white box testing oriented
and the step can be conducted in parallel for multiple modules.
• Integration Testing:
Integration testing is a systematic technique for constructing the program structure, while
conducting test to uncover errors associated with the interface. The objective is to take unit
tested methods and build a program structure that has been dictated by design.

14. Task Identity & procedure: 14
• System Testing:
System testing is actually a series of different tests whose primary purpose is to fully exercise
the computer-based system. Although each test has a different purpose, all work to verify that
all system elements have been properly integrated to perform allocated functions.
• Security Testing:
Attempts to verify the protection mechanisms built into the system.
• Performance Testing:
This method is designed to test runtime performance of software within the context of an
integrated system.

15. FPA
4/17/2017
15
• Matrix Used for EI
• Matrix Used for EI

16. FPA
• Matrix Used for EO and EQ
16

17. Pert chart
19
1
4
5
2
3
6 7
B[5,8]
3[14,17]
6[8,14]
D[8,14]
G[21,26]
5[21,26]
Activity Dependen
cy
Time Human
Requirme
nt gather
A
_ 5 3
Desgin
B
A 3 2
Database
C
_ 8 4
Coding
D
A,C 6 3
Testing
E
B,C 4 3
Recovery
F
D 7 4
Release G E,F 5 2

18. Critical path analysis 18
TASK Time ES EF LS LF SLACK
A 5 0 5 9 14 9
B 3 5 8 14 17 9
C 8 0 8 0 8 0
D 6 8 14 8 14 0
E 4 8 12 17 21 9
F 7 14 21 14 21 0
G 5 21 26 21 26 0

19. Gantt chart
Dhaka vehicle system4/17/2017
19

20. Budget 20
Task Cost Total
Buy new equipment 25000 25000
Developer cost 3*25000 75000
Testing cost 2*15000 30000
Hired skilled designer 2*10000 20000
Other cost 10000 10000
Total cost 160000 TK

21. Thank you everybody 21
Visit our Website- http://www.wethecoders.com