Description
This is a document explains implementation of software and MIS for managing road traffic and transport.
Transport Management
Management Information system (MIS)
Introduction
1.1. Purpose
The purpose of this document is to describe the functional and technical implementation details of the Transport management system being developed in the context of the statement of work.
1.2.
Scope And Objective
The Objective of this application software is to manage the transportation of an Educational Institution so as to achieve a better and effective control of vehicles available at the lowest possible cost. The Phase 1 implementation of the Transport Management System will address the following through the SRS document: • • • • • Identification of Routes in the city Mapping of Routes Administrative services Bus Maintenance Passenger Information System
The Phase 2 implementation will have the following features as a addon to the above mentioned functionalities • •
•
Mapping of Buses only to Profit making routes Feedback System Complaint re-addressable mechanism
1.3.
Product Overview
The Application software is intended to help the transport department to help manage and run the transport system of the educational institute in a way that results in efficiency and profit for both the travellers and the transport department. The software will allow students who have registered themselves with the transport department to login and see the bus routes, change their Bus preferences, give their feedback, register complaints online. The software will help the Transport department people to effectively plan and manage the transport services, and help the passengers in their daily transportation.
2. General Description
2.1. Functions
The main function that this Transport management system has to perform is the management of the transportation system of the Educational Institution in way that reduces chaos, is effective, efficiently manages the available resources and is beneficial to the students who use it. This software also is supposed to help the transport department plan and manage the services, keep a detailed record of its passengers, drivers and conductors, plan and schedule the maintenance and various legal details regarding the buses like road tax, permits, insurance etc. 2.2. User Characteristics
The system will be used by two different users having proper authentication (userid and password). The first set of users would be the passengers who have registered themselves with the transport department to use the transport services. The second set of users would be the employees of the transportation department who would manage the servies and the administrative issues. 2.3. General Constraints
The main constraints of this system is network resources (internet availability), proper functioning of the hardware and the server.
3. Specific Requirements
3.1. Functional requirements: The main functional requirements of
this application software are: • • • • • • • • • • Information of the current route or the route taken by a vehicle during a period Details about number of students/ employees on each point and a route per vehicle Listing of students boarding from a point, on a route or on a vehicle Expenses incurred( head wise) on each vehicle during a period. Average Kms/ litre of petrol/diesel A comparisons of performance of vehicles A comparison of performance of drivers on a single vehicle A list of drivers vehicle wise Details of arrival/departure time of the vehicle at a particular point and distance The record of vehicle maintenance incurred and the schedule of maintenance Details related to contract, permit, road tax and insurance of vehicle
3.2. Performance requirements
Many factors affect the performance of a software application, including available computing resources, network connectivity, and performance of integrated systems. The numbers of records processed per sec should be at least 50 no matter their complexity and the network response time on a 256Kbps line should not exceed 30ms. 3.3. Non functional requirements Reusability
3.3.1.
The code should be so developed so that the phase 1 code can be used for further development of the system and new stand alone features could be integrated into the existing code.
3.3.2.
Reliability
The code should be reliable as in the quality defects and the performance issues should never be major. The system should not breakdown under heavy traffic and during peak performance time. 3.3.3. Documentation
The system, its build, the requirements, the overall system architecture, database requirements, performance standards all should be well documented so as to aid in the future development and maintenance of the system.
Use Case
TRANSPORT MANAGEMENT
COMPARISON OF VEHICLE PERFORMANCE «uses» «uses»
DRIVER
COMPARISON OF DRIVER PERFORMANCE
«uses»
ADMIN
«uses»
UPDATION OF MANDATORY OPERATIONS
«uses» «uses» SCHEDULING OF ROUTE ,TIME AND NUMBER OF STUDENTS BOARDING «uses» «uses»
«uses» «uses» CROSSCHECKING STUDENT LIST FROM PREDEFINED LIST
«uses»
«uses» MAINTAINANCE
CONDUCTOR
STUDENT
EXPENSE CALCULATION PER HEAD
Class Diagram
CONDUCTOR -Name -ID -Vehicle Alloted
STUDENT -Name -Student Id -Boarding Point +Boarding()
DRIVER -Name -Driver Id -Vehicle Alotted +driving() +Mandatory()
Bus -Bus No. -Bus Id +Avg. per KM()
Admin -Name -Employee ID +Vehicle Comparasion () +Driver Comparison () +Vehicle Scheduling () +Expenses per head () +Driver List() +Conductor List () +Student Allotment()
Maintenance -Bus ID +servicing() +Cleaning () +Air Check()
Deployment Diagram
Web Server
TCP/I Oracle Database
deploy deploy
deploy
deploy
deploy
LOGIN.exe
Bus Route.exe
Maintenance. exe
Passenger DB Scheme s
Bus DB scheme
Passenge r
Transport Employees
Bus Contract
Passenger Detail Table T
Mainte nnance Bus Staff Table
Permit
Boarding Points
Tax & Insurance
In this deployment diagram the front end would consist of a login screen to be used by the two type of the users of the system, passengers and the employees. After adding their credentials that will be validated against the record present in their respective database tables, they would be moved to their respective pages. There would also be a maintenance page that will b used by the transport department employees. The database table consists of two schemas passenger schema and the bus schema, both containing the details of the passengers and the buses.
Select Select routes on routes time basis with of student Identificatio above populace n of paramete important rs and
Allocate Add buses to buses to new routes randomly and remove ply on Mapping buses from different buses to routes that routes time are not
TRANSPORT MANAGEMENT track of database passengers the of most the to grow SYSTEMexisting insurance, frequent Maintenanc
permit, e of various contractor buses Passenger passenger transport s snetwork
Keep
Keep new Add a
Setup Review feedback the and existing complaint Feedback system mechanis and m and complaint streamlin
WORK BREAKDOWN STRUCTURE (WBS) Activity Diagram
i f ao t n bu o c re tr u u n ot r e
d t il osu ete p ye n e s f t d n m oe o a / l ec p i to r u p rvh le ah o r o t e e i n e c
l si g f i tn o su et t dn s
epne i c r d y ah xe s s nu b ec e vh l ( a u t d y d in eic c lc la b a m ) e e
cm r i n f o p is o a o pro ac ovh l e r ne f e i e f m c
c m r i n fpro a c o o p iso o e r ne f a f m d es n sn l vh le r r o a i g ei iv e c
l toc n ut r ad is f o d c s n o d es e i l w e r r vh e i iv c s
d t il od p ru e s f ea r a t e ad ri at e n a vl im r
r c r / c eu o eo s hd le f d m t n ne a e ac in
d t isr l t do o t atpr i , o d x e l e e t c n c e tr a t a a r , m a a d s r ne fa eic n inu c o vh le a
Activity diagram here depicts the various activities that are performed. It starts with providing information about the routes that various buses follow to the passengers, the allowing the passengers to select the bus they wish to board. This enrols them to the database as passenger and adds their personal details to the records of the transport department. Then the transport department calculates the expenses that each route incurs so as to increase the services on the profitable routes and stop from the loss making routes. It aslso keeps the record of all the bus details like the driver/conductor details, the maintenance details etc.
Sequence Diagram
Admin performance comparison()
driver conductor
student
vehicle
info
vehicle performance()
mandatory operations()
scheduling details()
crosschecking student list()
maintenance
expenses per head()
References and Bibliography
1. Frank Tsui, “Managing Software Projects”, Viva Books. 2. Kethy Schwalbe, “Information Technology Project management”, Thomson
Learning.
3. Roger S. Pressman, “Software Engineering – A Practioner’s Approach,
McGaw Hill.
doc_806420233.doc
This is a document explains implementation of software and MIS for managing road traffic and transport.
Transport Management
Management Information system (MIS)
Introduction
1.1. Purpose
The purpose of this document is to describe the functional and technical implementation details of the Transport management system being developed in the context of the statement of work.
1.2.
Scope And Objective
The Objective of this application software is to manage the transportation of an Educational Institution so as to achieve a better and effective control of vehicles available at the lowest possible cost. The Phase 1 implementation of the Transport Management System will address the following through the SRS document: • • • • • Identification of Routes in the city Mapping of Routes Administrative services Bus Maintenance Passenger Information System
The Phase 2 implementation will have the following features as a addon to the above mentioned functionalities • •
•
Mapping of Buses only to Profit making routes Feedback System Complaint re-addressable mechanism
1.3.
Product Overview
The Application software is intended to help the transport department to help manage and run the transport system of the educational institute in a way that results in efficiency and profit for both the travellers and the transport department. The software will allow students who have registered themselves with the transport department to login and see the bus routes, change their Bus preferences, give their feedback, register complaints online. The software will help the Transport department people to effectively plan and manage the transport services, and help the passengers in their daily transportation.
2. General Description
2.1. Functions
The main function that this Transport management system has to perform is the management of the transportation system of the Educational Institution in way that reduces chaos, is effective, efficiently manages the available resources and is beneficial to the students who use it. This software also is supposed to help the transport department plan and manage the services, keep a detailed record of its passengers, drivers and conductors, plan and schedule the maintenance and various legal details regarding the buses like road tax, permits, insurance etc. 2.2. User Characteristics
The system will be used by two different users having proper authentication (userid and password). The first set of users would be the passengers who have registered themselves with the transport department to use the transport services. The second set of users would be the employees of the transportation department who would manage the servies and the administrative issues. 2.3. General Constraints
The main constraints of this system is network resources (internet availability), proper functioning of the hardware and the server.
3. Specific Requirements
3.1. Functional requirements: The main functional requirements of
this application software are: • • • • • • • • • • Information of the current route or the route taken by a vehicle during a period Details about number of students/ employees on each point and a route per vehicle Listing of students boarding from a point, on a route or on a vehicle Expenses incurred( head wise) on each vehicle during a period. Average Kms/ litre of petrol/diesel A comparisons of performance of vehicles A comparison of performance of drivers on a single vehicle A list of drivers vehicle wise Details of arrival/departure time of the vehicle at a particular point and distance The record of vehicle maintenance incurred and the schedule of maintenance Details related to contract, permit, road tax and insurance of vehicle
3.2. Performance requirements
Many factors affect the performance of a software application, including available computing resources, network connectivity, and performance of integrated systems. The numbers of records processed per sec should be at least 50 no matter their complexity and the network response time on a 256Kbps line should not exceed 30ms. 3.3. Non functional requirements Reusability
3.3.1.
The code should be so developed so that the phase 1 code can be used for further development of the system and new stand alone features could be integrated into the existing code.
3.3.2.
Reliability
The code should be reliable as in the quality defects and the performance issues should never be major. The system should not breakdown under heavy traffic and during peak performance time. 3.3.3. Documentation
The system, its build, the requirements, the overall system architecture, database requirements, performance standards all should be well documented so as to aid in the future development and maintenance of the system.
Use Case
TRANSPORT MANAGEMENT
COMPARISON OF VEHICLE PERFORMANCE «uses» «uses»
DRIVER
COMPARISON OF DRIVER PERFORMANCE
«uses»
ADMIN
«uses»
UPDATION OF MANDATORY OPERATIONS
«uses» «uses» SCHEDULING OF ROUTE ,TIME AND NUMBER OF STUDENTS BOARDING «uses» «uses»
«uses» «uses» CROSSCHECKING STUDENT LIST FROM PREDEFINED LIST
«uses»
«uses» MAINTAINANCE
CONDUCTOR
STUDENT
EXPENSE CALCULATION PER HEAD
Class Diagram
CONDUCTOR -Name -ID -Vehicle Alloted
STUDENT -Name -Student Id -Boarding Point +Boarding()
DRIVER -Name -Driver Id -Vehicle Alotted +driving() +Mandatory()
Bus -Bus No. -Bus Id +Avg. per KM()
Admin -Name -Employee ID +Vehicle Comparasion () +Driver Comparison () +Vehicle Scheduling () +Expenses per head () +Driver List() +Conductor List () +Student Allotment()
Maintenance -Bus ID +servicing() +Cleaning () +Air Check()
Deployment Diagram
Web Server
TCP/I Oracle Database
deploy deploy
deploy
deploy
deploy
LOGIN.exe
Bus Route.exe
Maintenance. exe
Passenger DB Scheme s
Bus DB scheme
Passenge r
Transport Employees
Bus Contract
Passenger Detail Table T
Mainte nnance Bus Staff Table
Permit
Boarding Points
Tax & Insurance
In this deployment diagram the front end would consist of a login screen to be used by the two type of the users of the system, passengers and the employees. After adding their credentials that will be validated against the record present in their respective database tables, they would be moved to their respective pages. There would also be a maintenance page that will b used by the transport department employees. The database table consists of two schemas passenger schema and the bus schema, both containing the details of the passengers and the buses.
Select Select routes on routes time basis with of student Identificatio above populace n of paramete important rs and
Allocate Add buses to buses to new routes randomly and remove ply on Mapping buses from different buses to routes that routes time are not
TRANSPORT MANAGEMENT track of database passengers the of most the to grow SYSTEMexisting insurance, frequent Maintenanc
permit, e of various contractor buses Passenger passenger transport s snetwork
Keep
Keep new Add a
Setup Review feedback the and existing complaint Feedback system mechanis and m and complaint streamlin
WORK BREAKDOWN STRUCTURE (WBS) Activity Diagram
i f ao t n bu o c re tr u u n ot r e
d t il osu ete p ye n e s f t d n m oe o a / l ec p i to r u p rvh le ah o r o t e e i n e c
l si g f i tn o su et t dn s
epne i c r d y ah xe s s nu b ec e vh l ( a u t d y d in eic c lc la b a m ) e e
cm r i n f o p is o a o pro ac ovh l e r ne f e i e f m c
c m r i n fpro a c o o p iso o e r ne f a f m d es n sn l vh le r r o a i g ei iv e c
l toc n ut r ad is f o d c s n o d es e i l w e r r vh e i iv c s
d t il od p ru e s f ea r a t e ad ri at e n a vl im r
r c r / c eu o eo s hd le f d m t n ne a e ac in
d t isr l t do o t atpr i , o d x e l e e t c n c e tr a t a a r , m a a d s r ne fa eic n inu c o vh le a
Activity diagram here depicts the various activities that are performed. It starts with providing information about the routes that various buses follow to the passengers, the allowing the passengers to select the bus they wish to board. This enrols them to the database as passenger and adds their personal details to the records of the transport department. Then the transport department calculates the expenses that each route incurs so as to increase the services on the profitable routes and stop from the loss making routes. It aslso keeps the record of all the bus details like the driver/conductor details, the maintenance details etc.
Sequence Diagram
Admin performance comparison()
driver conductor
student
vehicle
info
vehicle performance()
mandatory operations()
scheduling details()
crosschecking student list()
maintenance
expenses per head()
References and Bibliography
1. Frank Tsui, “Managing Software Projects”, Viva Books. 2. Kethy Schwalbe, “Information Technology Project management”, Thomson
Learning.
3. Roger S. Pressman, “Software Engineering – A Practioner’s Approach,
McGaw Hill.
doc_806420233.doc