Escolar Documentos
Profissional Documentos
Cultura Documentos
System
Software Engineering
Project Report
(CSHP - 410)
Submitted by:
2013
Keshav Mahavidyalaya
University of Delhi
Table of Contents
Problem Statement................................................................................................ 3
1
INTRODUCTION................................................................................................ 4
1.1
Purpose..................................................................................................... 4
1.2
Scope........................................................................................................ 4
1.3
Definitions................................................................................................. 4
1.4
Overview................................................................................................... 4
2.1.1
2.1.2
2.1.3
Data Dictionary................................................................................... 7
Project Management........................................................................................ 9
3.1
Cost Estimations....................................................................................... 9
3.1.1
3.1.2
Efforts............................................................................................... 10
3.2
Schedule................................................................................................. 11
3.3
Risk Table................................................................................................ 11
Design Engineering....................................................................................... 12
4.1
Architectural Design................................................................................12
4.2
Testing........................................................................................................... 14
Problem Statement
Problem Analysis:1.We dont have system which could inform Passenger about their Bus Timing, Shedule
etc.
2.We only do have record of bus Timings on which bus should start on a route which is
also sometimes not followed by drivers.
3. There is no information provided to passenger about buses.
Method of Solution:-
1.The problem of bus timing and other problem could be solved by Schedule Monitoring
of Buses.
2. Real time Information should be provided to user about their bus this could be done by
using GPS in buses.
1 INTRODUCTION
1.1 Purpose
The GPS Based Bus Management System (GBMS) is used to keep Track of Buses by
Company. Also this facility can be used to give information to Passenger by web and a
Display on Bus Stop.
1.2 Scope
Many cities have found that using GPS tracking systems not only improve the efficiency of
city bus operations, but also encourage more commuters to take advantage of their city bus
systems.
Many city bus systems have discovered that GPS tracking systems which allow passengers to
monitor the location and estimated arrival time of their bus actually increases the number of
people using city buses for routine commuting. For example, if a rushed commuter can
1.3 Definitions
Our System also provides information about Buses to Passenger. Consider the possibility of
implementing GPS tracking systems which allow customers to monitor bus locations via
website, or cell phones. This will likely increase the satisfaction of customers. Also a display
is fixed on every Stop so passenger will know where their bus is and when will it arrive.
1.4 Overview
The purpose of this section is to obtain agreement regarding the objectives the system must
meet. Ultimately this segment defines the boundaries of the effort. The GPS Based Bus
Management System helps administrator honor their professional commitments by
following a tailored version of the organizations standard process. This project aims to
provide helpful information about Bus in a given geographic area. Also it store Tracking
Information in Database. It also keep track of Buss speed if it is crossed the authority will get
the information.verify his or her bus is running on time via their cell phone or a website, they
are much more likely to ride the bus rather than take a cab or drive themselves.
DFD Level 0
2.1.2
DFD Level 1
2.1.3
Data Dictionary
Type
Bus_ID
Long Integer
Route_no
Integer
Emp_no
Long Integer
Driver_name
Character[20]
Description
Primary Key
Table 2: Route
Field Name
Type
Route_no
Integer
Route_Name
Character[20]
Start
Character[20]
Destination
Character[20]
Path
Integer
Description
Primary Key
Multi valued
Table 3: Stops
Field Name
Type
Stop_id
Integer
Stop_name
Character[20]
Degree_lat
Float
Min_lat
Float
Sec_lat
Float
Degree_log
Float
Min_log
Float
Sec_log
Float
Description
Primary Key
Table 4: Main
Field Name
Type
Bus_ID
Long Integer
Route_no
Integer
Route_Name
Character[20
]
Time
Time Stamp
Loc_lat
Loc_log
Degree
Float
Min
Float
Sec
Float
Degree
Float
Min
Float
Sec
Float
Next_stop
Integer
Last_stop
Integer
Description
3 Project Management
3.1 Cost Estimations
3.1.1
Opt.
Est. Count
Weight
FP Count
External Inputs
23
External
Outputs
23
External
Inquires
10
Internal Logical
Files
10
35
External
Interface Files
11
Count Total
102
Factor
Values
Data communication
Distributed processing
Performance Critical
10
11
12
Conversion/installation in design
13
Multiple installation
14
Total
38
(Fi)] = 38
Value adjustment factor= [0.65+0.01* 38]
=0.65 + 0.38
= 1.03
FP (EST.) = 102 * 1.03
= 105.06
3.1.2
Efforts
3.2 Schedule
S.No.
Process/Phase
Start Date
Finish Date
1.
Requirement gathering
20/01/13
15/02/13
2.
Requirement analysis
16/02/13
27/02/13
3.
DFD preparation
28/02/13
10/03/13
4.
11/03/13
20/03/13
5.
21/03/13
30/03/13
6.
ERD preparation
31/03/13
10/04/13
7.
FPA calculation
11/04/13
16/04/13
RISK
CATEGORY
Technical risk
PROBABILIT
Y
30%
IMPACT
Delivery deadline
tightened
Project risk
30%
Project risk
20%
Team dissension/lack of
cohesion
Project risk
10%
RMMM PLAN
4 Design Engineering
4.1 Architectural Design
5 Testing
Administrator module :