Professional Documents
Culture Documents
Bus Pass System
Bus Pass System
Bus Pass System
titled “ Bus Pass System” as per syllabus laid down by the University of Pune
during academic year 2013-14. They are sincere honest and completes the work
• Acknowledgment
• Problem Definition
• Existing System & Need Of New System
• Scope of System
• Feasibility Study
• Requirement Analysis
• Entity Relation Diagram(ERD)
• Data Dictionary
• Data Flow Diagram
• UML Diagram
▪ Class Diagram
▪ Use case Diagram
▪ Collaboration Diagram
▪ State Chart
▪ Component Diagram
▪ Deployment Diagram
▪ Sequence Diagram
▪ Activity Diagram
• Input / Output Screens
• Report Layout
• System Testing
• User Manual System
• Limitation
• Bibliography
ACKNOWLEDGEMENT
Existing System:-
This system is based on passenger pass in which passenger
can travel with concession along with from his/her village or city.
This system is also based on student & passenger pass. There
are two types of passes like student pass & passengers pass.
Pass
A) Student Pass :
This is based on student pass in which student travels from
his / her village / city. The student pass is only of type one month
pass. In this student pays the money for ten days &get 20 days
money concession means Student pays amount with 66.66%
concession. The system is working manually & includes lots of
paper work.
The student pass procedure is as follows:-
B) Passenger Pass:-
This is based on Passenger pass in which Passenger
travels from his / her village / city. In this, Passenger pass is
valid for all passengers such as Employees, Teachers, Private
class Students or any person. The system is working manually
& includes lots of paper work.
There are two types of Passenger Pass are as follows:
1) One Month Pass.
2) Three Month Pass.
1) One Month Pass :
Need of Computerization:
There is a need of computerisation of existing system
because of following reasons:
• The existing system is totally manual.
• It is time consuming & tedious.
• All the student and passenger information is recorded
into manually register.
• There is the lost of documents, chance of document
messing.
• Searching of the previous records of the student is also
time consuming & tedious. They have not found in all
the registers.
• Because of this the system is physically hard. So we try
to solve this problem by computerising the system.
Proposed System:-
• Consistency in department.
1. Technical Feasibility:
The project is technically feasible. No additional software
or hardware is required for the implementation, as the system is
platform independent.
2. Economical Feasibility:
3. Operational Feasibility:
B) Hardware Requirements:
1) Hard Disk Drive: 100 GB Onwards.
2) RAM: 128 MB Onwards.
3) Processor: 1.0 GHz Onwards
4) Printer.
REQUIREMENT
ANALYSIS
• Interview
• Record Review
• Questionnaire
• Observation
1. Questionnaire:-
A questionnaire is sequence of questions to collect
information from the user. The questions are clear and simple and
to the point. The success of collecting data through a
questionnaire mainly depends on how skillful and imaginatively
the questionnaire has been designed, we ask them how the
system actually works, how you collect the information or which
type of peoples uses which type of scheme etc.
The questionnaire is as follows:-
1. What is the process to pass system?
2. What is the type of passes?
3. How much concision of passes?
2. Record Review:-
Information related with the system may be present through
journals, forms, documents, circulars, notices which are previous
official documents.
The kind of record review provides very valuable information
to the analyst about the system, organization and various
procedures and rules.
3. Observation:-
Observation allows us to gain information. In this method we
have observed various documents, the flow of documents; way of
process is carried out etc.
ER-DIAGRAM
Sname
Name of c/s
reg.no.
M
Student/Passenger has
M
Address
Passtype
1
Pass
route
M
validity
approach
1
1
Clerk issue
address
cid cname
DATA DICTIONARY
Login Table:-
Student / Clerk
Passenger
Form & Amount Form
Bus
Form Issue
Pass
Form System
Pass ID
Pass ID 0.0
Reports Amount
Management Account
Bus
First Level DFD
Clerk
Student
Master
Maintenance
Passenger
1.0
Report
Generation
2.0
Management
UML DIAGRAMS
Class Diagram:-
+addStudent() +addStudent()
+addPassenger() +addPassenger()
+deleteStudent() +deleteStudent()
+deletePassenger() +deletePassenger()
+takePass() +takePass()
1..* 1*
1 1
Administrator
#id : Number
#name : String
#address : Number
+addMember()
+deleteMember()
+addClerk()
+deleteClerk()
Use case Diagram:-
Clerk
Student/Passenger
Account
Management
Sequence Diagram:-
Student/Passenger Clerk System
Ask Information
Insert Data
Pass & ID
Pass & ID
Activity Diagram:-
Start
Valid invalid
Student Passenger
Fill Form Take Details Fill Form Take Details Fill Form Take Details
End
Component Diagram:-
Student /Passenger
Clerk
System
Deployment Diagram:-
Database
Student / Clerk
Passenger
System
Collaboration Diagram:-
Clerk
State Chart Diagram:-
Start
Ask Information
End
INPUT-OUTPUT
SCREEN
s
REPORT LAYOUT
Types of Testing:-
1. Black-Box Testing :-
In this, the structure of the program is not considered.
The software is considered as a black box to which defined
inputs are given. From this the defined outputs are obtained. In
this the tester only knows what the software is supposed to do
but he cannot look in the box to see how it operates.
We have given all possible Inputs checked all correct outputs:
▪ Enter Username & Password- valid- Login
successfully.
▪ Enter student & passenger details - Add records
into database successfully.
▪ Enter register no. & other details- records are
inserted successfully.
2. White Box Testing :-
BOOKS:
Following is the list of books and the tutorial software’s that
helped us to create our project.
Software Engineering
…….By- Roger Pressmen
Object Oriented Software Engineering
…….By- Mrs.Sharada Patil & Mr.Alok Pawar
WEBSITE:-
http://www.Google.com
http:// www.w3school.com
Thank You...