Beruflich Dokumente
Kultur Dokumente
CHAPTER 1 : INTRODUCTION
2
CHAPTER 1: INTRODUCTION
In the existing system Colleges have to manually maintain information regarding College
busses and routes. Information relating to student passengers and bus passes have to be
maintained separately.
3
During the period of finalizing the idea of the system, the primary goal was to design the
system i.e those who don’t know how to handle the software. As designing work began and
things started taking shape, the system got developed to a stage where it would be used by entry
level
Hardware:
RAM 64 MB.
Processor Pentium 4.
Hard Disk Capacity 1GB.
Monitor 15”
Software:
4
CHAPTER 2: PROPOSED SYSTEM
2.1 Proposed System
The Bus Management System is a desktop system aimed at students, college administration to
maintain bus facility. The system takes student information as input source and attempts to
maintain the bus services. It allows flexibility during these processes.
The system generates exhaustive reports related to the Bus Management i.e. Fees paid,
dues, rout no. & bus stop. The reports highlight various bus services and features of the bus,
which can be subjected to improvements especially for the college administration to improve bus
transport system.
The system requires comparatively small amount of resources such as memory,
input/output devices and disk space.
The system overall keeps approach in highlighting key features of the bus services.
5
Develop software such that everybody working in colleges bus management can handle
easily. Trainer can store & retrieve data easily. And hence, keeping these major target segments
in focus, the system was developed.
The economic factors were also worked out keeping the target segments into focus. The
objective of developing a tool for technical as well as non-technical user hence got achieved.
2.4 Feasibility
Once the scope of the system is defined, we have to specify exactly how the system will
look like which, leads to an estimate of the computer storage requirements that form the basis for
the file design that is to be undertaken in the design phase of the project life cycle. Feasibility
study is the test of system proposal according to its workability, impact on the organization,
ability to meet user needs, effective use of resources.
There are three aspects involved in the feasibility study.
7
Class Diagram
8
3.1.2 Use Case Diagram
A use-case instance is a sequence of actions a system performs that yields an observable result
of value to a particular actor. The sequence referred to in the definition is really a specific flow
of events through the system, or an instance. A use case defines a set of use-case instances. An
actor communicates with a use-case instance of the system. The functionality of a system is
defined by different use cases, each of which represents a specific flow of events. The
description of a use case defines what happens in the system when the use case is performed.
Enter Username
User
Enter Password
9
DataEntry Enter Data
User
Data Retrieval Enter ReceiptNo
Use case diagram for Data Entry, Data Retrieval, Bus Scheduling
10
Exit
User
11
Sequence Diagram
12
Login BussPa Receipt
ss
4:
8: 1:
6: 3:
9: 2:
DataRetr Options DataEntr
ival y
7: 5:
11:
12: 10:
Bus
Scheduling
Collaboration Diagram
13
Enter the password and
username
select Option
view
click on button view bus information
click on add button
schedule
Bus Pass Bus Receipt
click on exit
Activity Diagram
14
USERNNAME PASSWORD
LOGIN
Enter into
Database
Schedule
Bus Time
RouteNo Bus Stop
15
Login Screen
Options
Data Entry
Bus Pass
Receipt
Data Retrieval
Bus Scheduling
17
5.4 Bus Receipt Form
18
5.6 Data Retrieval Form
19
20
5.6 Bus Scheduling Form
21
22
23
CHAPTER 7 : IMPLEMENTATION AND TESTING
College Bus
Management
DataEntr Schedule
y1.mdb .mdb
Software: JDK 1.5.0, Edit Plus, Microsoft Office 2003, Rational Rose
24
7.2.2 Frame details
This project is being developed comprising of several frames. The names of the frames
under the scope of this project are revealed as under:
Login Screen
Options
Data Entry
Bus Pass
Receipt
Data Retrieval
Bus Scheduling
We have used two tables as databases that have been established in Microsoft Access.
We have accessed this database from JAVA using JDBC connections and thus have arranged to
make changes to the database without directly opening the file, through the front end, i.e. JAVA
frames.
This addresses to the GUI design issues associated with the project. The project involves
building an interface with good GUI and which is user friendly. The interface basically
incorporates the menu including the functionalities viz open, save, print, close.
On the click event of optimize the system provides the user with the optimized code as
output on the screen.
The exit option the system enables to exit from the application.
25
7.3 Test Plan
1. Introduction
This Test Plan provides the strategy for testing the project “College Bus
Management System”. This section of the Test Plan document describes the following.
Purpose
Objectives
a. Document Purpose
This Test Plan reviews:
b. Objectives
This document provides the platform for testing the project “College
Bus Management System”. The objective of testing is to see if the project meets the
Software Requirement Specifications. This document will provide - (1) the
guidelines for the testing team to test the functionalities embedded in the project
and (2) help for evaluating the Software Quality of the project.
2. Project Scope
This section of the Test Plan document describes the (1) Scope of the project
“College Bus Management System” and (2) Out of Scope of the project “College Bus
Management System”.
26
Data Entry
Bus Scheduling
Data Retrieval
3. Project Resources
Table below describes the Roles, Responsibilities and Resource Name for the
testing of the Project “College Bus Management System”.
27
Table 1 - Project Roles and Responsibilities
4. Test Strategies/Techniques
This section of the document describes – (1) Test design and (2) Test Data for the
project “College Bus Management System”.
a. Test Design
Considering the scope of the project and the time limitations, we will be
performing following tests.
a) Unit Test –
This test verifies the program logic and is based on the knowledge
of the program structure.
b) Integration Test –
This test verifies the entire system’s functionality according to the
design specification.
c) Business Requirements –
This test verifies whether specific requirements of the
customer are met.
d) Acceptance Testing –
This test verifies whether the system needs to meet the
initial objectives and customer’s expectations.
For performing the above mentioned tests, we will create test cases as shown in
table below.
28
Table below describes the description of each test case mentioned in table 2 and the
results expected from a corresponding test case.
ID
UC-1 TC-1 User enters a valid User is granted the access to the
username and password system
UC-1 TC-2 User enters correct User denied access and “Incorrect
username with wrong Username or Password”displayed
password
UC-1 TC-3 User enters incorrect User denied access and “Incorrect
username Username or Password”displayed
UC-3 TC-2 Check Stop validity in Set Display correct stop names for
bus schedule selected bus route
29
schedule selected bus route
UC-3 TC-4 Bus Scheduling: Check if New route should be saved in the
new Bus Schedule is database with the correct
saved correctly to the parameters like Stops and Timings
Database under the
correct Route Number
UC-4 TC-2 Retrieve correct details Display Receipt Details for the
according to receipt no. input Receipt No.
entered
b. Database
A Head maintains Database that contains the login names and passwords of all the
users.
30
5. Project Tasks/Schedule
Table 4 describes the schedule for the Test Plan of the project “College Bus
Management System
Project Schedule
6. Defect Responsibility/Resolution
31
7. Exit Criteria
Testing can proceed to the next stage of the process when a sufficient proportion
of the current stage has been completed All exit criteria should be satisfied by the end of
the project.
Goals and deliverables of the test plan of the “College Bus Management System” are as
follows –
a) Goals:
b) Deliverables:
Test Planning Stage
Test Execution and Defect Tracking Stage
Evaluation and Improvement – this include
Test Cycle Evaluation
Project Summary / Evaluation
32
7.4 Test Case for Bus Scheduling
Test Case
Use Test Step Description Expected Actual Result Successf Environm Log
Case Result ul/Faile ent No. (if Number
Cas (if different from
No. d failed) (if
e expected)
failed)
UC- TC-4 Bus Scheduling: New route Routes are correctly Successf - -
3 Check if new Bus should be saved saved in the ul
Schedule is saved in the database Database and are
correctly to the with the correct available in the Data
Database under the parameters like Entry Form.
correct Route Stops and
Number Timings
33
8. Limitations and Future Enhancement
8.1 Limitations
Testing on platforms like Linux and Mac has not been performed
Standalone system with no internet support.
34