College Bus Final Report

7/24/2019 College Bus Final Report

1/37

COLLEGE BUSMANAGEMENT SYSTEM

Submitted By-Rahul Bansode (Roll No.-126)

Francis Araujo (Roll No.-)

!uided By-

"r. Amrish Ni#am

"rs. Netra $atil

"rs. An%ha &aidya


2/37

Every work that completes successfully sta!s o the costat ecoura"emet#

"oo!w$ll a! support of the people% Throu"h th$s# we woul! l$ke to e&press our

"rat$tu!e to all those who have cotr$'ute! to accompl$sh our pro(ect successfully%

)t $s a pleasure to ackowle!"e our !e't to all the people $volve!# !$rectly or

$!$rectly# $ the !evelopmet of th$s pro(ect# u!ertake at eartment o/

"aster / comuter Alication*S)BA+, Th$s e&per$ece w$ll !e-$tely help us $

our future e!eavors of work%

.e woul! l$ke to take the opportu$ty to thak "r.Amresh Ni#am(Assistant

$ro/essor)0"rs.An%ha &aidya (Associate $ro/essor) "rs. Netra $atil

(Associate $ro/essor) at /epartmet of Master of Computer Appl$cat$o# *S)BA+,

for the$r costat "u$!ace throu"hout th$s pro(ect%

.e woul! also l$ke to thak r. Arita !oal (irector "'A-SBAR)a! all other

facult$es of our !epartmet for 'e$" a costat source of $sp$rat$o r$"ht from

seek$" pro(ect to the successful complet$o of pro(ect a! also "u$!$" us

throu"hout our pro(ect%

0$ally we e&press our !eep "rat$tu!e to /epartmet L$'rary for prov$!$" us var$ous

'ooks a! $format$o o may top$cs that were ecessary for our pro(ect%

Our o'l$"at$o rema$s to all those people a! fr$e!s who have !$rectly or $!$rectlyhelpe! us $ successful complet$o of our pro(ect% No amout of wor!s wr$tte here

w$ll su1ce for our sese of "rat$tu!e towar!s all of them%

2


3/37

S$h"a! Tech$cal E!ucat$o Soc$ety3s

SN3!A NS4454, F B5SN,SSA"NS4RA4N R,S,AR'3

Approve! 'y A)CTE4 A1l$ate! to U$vers$ty of 5ue

',R4F'A4,

Th$s $s to cert$fy that the pro(ect et$tle!

'olle%e Bus "ana%ement System

has 'ee complete! successfully 'y

Rahul Bansode (Roll No 126)

Towar!s the part$al ful-llmet of the Masters of Computer Appl$cat$o fromthe U$vers$ty of 5ue for the aca!em$c year 2677 8 2672

9ea! of /epartmet 5ro(ect $ char"e

:


4/37

S$h"a! Tech$cal E!ucat$o Soc$ety3s

SN3!A NS4454, F B5SN,SSA"NS4RA4N R,S,AR'3

Approve! 'y A)CTE4 A1l$ate! to U$vers$ty of 5ue

',R4F'A4,

Th$s $s to cert$fy that the pro(ect et$tle!

'olle%e Bus "ana%ement System

has 'ee complete! successfully 'y

Francis Araujo (Roll No )

Towar!s the part$al ful-llmet of the Masters of Computer Appl$cat$o fromthe U$vers$ty of 5ue for the aca!em$c year 2677 8 2672%

9ea! of /epartmet 5ro(ect $ char"e

4able / 'ontents

CHAPTER 1 : INTRODUCTION

1.1 Existing System and Need for System

1. S!o"e of #or$

;


5/37

1.% O"erating En&ironment ' Hard(are and Soft(are

CHAPTER : PROPOSED S)STE*

.1 Pro"osed System

. O+,e!ti&es of System

.% User Re-irements

./ 0easi+iity Stdy

CHAPTER % : ANA2)SIS 3 DESI4N

%.1 Anaysis P5ase

%.1. Cass Diagram

%.1.% Use Case Diagrams%. Design P5ase

%..1 Se-en!e Diagram

%.. Coa+oration Diagram

%..% A!ti&ity Diagram

%.% *ode S"e!ifi!ations

CHAPTER 6 : 0RONT END SPECI0ICATION

6.1 *en Tree

6. *en S!reens

6.% In"t S!reens

CHAPTER 7 : I*P2E*ENTATION AND TESTIN4

7.1 Com"onent Diagram

7. De"oyment Diagram7.% Test Pan

7./ Test Cases

CHAPTER 8 : 2I*ITATIONS AND 0UTURE ENHANCE*ENTS


6/37

8.1 2imitations of t5e system

8. Pro"osed En5an!ements

8.% Con!sion 3 0tre S!o"e.

CHAPTER 1: INTRODUCTION

=


7/37

1.1 Existing System:

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.

Need for System

Provide a simpler method to store and access information related to buses and students.

Provide a simple interface which will be easily used without much training.

Reduce paperwork and make all related information accessible easily.

1. S!o"e of #or$

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. "s designing work began and

things started taking shape the system got developed to a stage where it would be used by entry

level

#he $us %anagement &ystem is being developed to provide a tool for the different

colleges to easily maintain the college bus information. #he system will give an effective output

for the 'ava ( %icrosoft excel given as input to the system. #he compiled )ava program given as

input to the system after scanning the program will generate different reports.

"t the start of the pro)ect setup %icrosoft "ccess provides an interactive part to store

information about buses* different routs of buses student information and bus pass etc.

.

>


8/37

1.% O"erating En&ironment

Hard(are:

R"% +, %$.

Processor Pentium ,.

-ard Disk Capacity /$.

%onitor 01

Soft(are:

2indows 34.xp and more versions

'ava.

%& "ccess

CHAPTER : PROPOSED S)STE*

.1 Pro"osed System

?


9/37

#he $us %anagement &ystem is a desktop system aimed at students college administration to

maintain bus facility. #he system takes student information as input source and attempts to

maintain the bus services. It allows flexibility during these processes.

#he system generates exhaustive reports related to the $us %anagement i.e. 5ees paid

dues rout no. ( bus stop. #he reports highlight various bus services and features of the bus

which can be sub)ected to improvements especially for the college administration to improve bus

transport system.

#he system re6uires comparatively small amount of resources such as memory

input7output devices and disk space.

#he system overall keeps approach in highlighting key features of the bus services.

. O+,e!ti&es of System:

Develop software such that everybody working in colleges bus management can handle

easily. #rainer can store ( retrieve data easily. "nd hence keeping these ma)or target segments

in focus the system was developed.

#he economic factors were also worked out keeping the target segments into focus. #he

ob)ective of developing a tool for technical as well as non8technical user hence got achieved.

.% User Re-irement:

9eeds to have basic computer knowledge.

9eeds a little orientation to be able to use the software efficiently.

@


10/37

./ 0easi+iity

:nce 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 re6uirements that form the basis for

the file design that is to be undertaken in the design phase of the pro)ect life cycle. 5easibility

study is the test of system proposal according to its workability impact on the organization

ability to meet user needs effective use of resources.

#here are three aspects involved in the feasibility study.

./.1 Te!5ni!a feasi+iity

#he technical feasibility study highlighted various differences in approaches and

implementations of the 'ava programming language environment. #otal flexibility in bus

management makes easy to handle the information about student ( bus.

./. E!onomi!a feasi+iity

#he economical feasibility of the system was given due attention as well considering the

emerging global market .#he system primarily aimed at academic and entry level personnel

works out to be a good prospective system if positioned properly into the I# market. #he system

has been kept very compact initially in the college only and depending on the targeted market

segment response additional /;I features could be added. #he system hence at present is

economically feasible.

:perational feasibility means whether the new system performs its work efficiently and

asks for the user needs. 2hat are the facilities provided< 2hat is the impact on the user operationally feasible and very

easy to operate. "lso on8demand reports will give the users* the exact information that itself

proves that the system is working perfectly.

C5a"ter %: ANA2)SIS 3 DESI4N

76


11/37

%.1Anaysis P5ase

%.1.1 Cass Diagram.

DataEntry

Name

YearDepartment

Semester

ReceiptNoFeesPaid

Dues

RouteNo

BusStop

Time

Main()

actionPerformed()

windowClosin()

Receipt

Name

Year

Department

Semester

ReceiptNoFeesPaid

Dues

RouteNo

BusStop

Time

BusPass

Year

Department

Semester

ReceiptNo

FeesPaid

Dues

RouteNo

BusStop

TimeName

!oin

"sername

Password

Main()

actionPerformed()

windowClosin()

Sc#edule

RouteNo

BusStopTime

Main()

actionPerformed()

windowClosin()

DataRetri$al

ReceiptNo

Name

Year

Department

Semester

FeesPaid

DuesRouteNo

BusStop

Time

Main()

actionPerformed()

windowClosin()

Master Form

DataEntry()

DataRetri$al()

BusSc#edulin()

Class /$a"ram

77


12/37

%.1. Use Case Diagram

A use-case instance$s a seuece of act$os a system performs that y$el!s

a o'serva'le result of value to a part$cular actor% The seuece referre! to

$ the !e-$t$o $s really a spec$-c ow of evets throu"h the system# or a

$stace% A use case !e-es a set of usecase $staces% A actor

commu$cates w$th a usecase $stace of the system% The fuct$oal$ty of a

system $s !e-e! 'y !$Deret use cases# each of wh$ch represets a spec$-c

ow of evets% The !escr$pt$o of a use case !e-es what happes $ the

system whe the use case $s performe!%

Enter "sername

"ser

Enter Password

Use case !$a"ram for Lo"$

72


13/37

Enter Data

Enter ReceiptNo

Enter RouteNo

DataEntry

Data Retrie$al"ser

Bus sc#edule

Use case !$a"ram for /ata Etry# /ata +etr$eval# Bus Sche!ul$"

7:


14/37

"ser

E&it

Use case !$a"ram for e&$t 'utto

%. Design "5ase:

%..1 Se-en!e Diagram

7;


15/37

7


16/37

Seuence ia%ram

%.. Coa+oration Diagram

!oin ReceiptBussPa

ss

DataRetri$al

Bus

Sc#edulin

'ptions DataEntr

y

()

**)

+)

,)

-)

*)

.)/)

0)

*1)*+)

2)

'ollaboration ia%ram

7=


17/37

%..% A!ti&ity Diagram

$alid pasword 3usernamein$alid passwords3username

E&it t#e Fuction

select 'ption

Enter t#e Data

Bus sc#edule

Bus Receipt

4iew for end

select Ma5or

function

Prompt for

Reentry

Enter t#e password and

username

$iew 6us

sc#edule

$iew

information

Searc#

information

Bus Pass

if option is data entry if option is Data Retri$al

if option is sc#edule

clic7 on 6utton clic7 on add 6utton

clic7 on e&it

Acti7ity ia%ram

7>


18/37

Schedule

Bus StoRouteNo

%../ Entity Reations5i" Diagram

7?

USE+NNAME 5ASS.O+/

LOG)N

Eter $to

/ata'ase

Bus 4ime


19/37

%.% *ode S"e!ifi!ation?

@ogin &creen

:ptions

Data Antry

$us Pass

Receipt

Data Retrieval

$us &cheduling

7@


20/37

CHAPTER 6: 0RONT END SPECI0ICATION

6.1 2ogin S!reen

6. O"tion 0orm

26


21/37

6.% Data Entry 0orm

6./ 9s Re!ei"t 0orm

27


22/37

6.6 9s Pass 0orm

6. Data Retrie&a 0orm

22


23/37

2:


24/37

6. 9s S!5eding 0orm

2;


25/37

2


26/37

2=


27/37

CHAPTER 7 : I*P2E*ENTATION AND TESTIN4

7.1 Com"onent Diagram

Collee Bus

Manaement

DataEntr

y*8md6

Sc#edule

8md6

7. Im"ementation Detais

7..1 Te!5noogi!a Im"ementation detais

Platform? 2I9 BP.

&oftware? 'D .0.= Adit Plus %icrosoft :ffice ==E Rational Rose

-ardware? Pentium IF processor 0 %$ R"% 4= /$ -DD

2>


28/37

7.. 0rame detais

#his pro)ect is being developed comprising of several frames. #he names of the frames

under the scope of this pro)ect are revealed as under?

@ogin &creen

:ptions

Data Antry

$us Pass

Receipt

Data Retrieval

$us &cheduling

7..% Data+ase detais

2e have used two tables as databases that have been established in %icrosoft "ccess. 2e

have accessed this database from '"F" using 'D$C connections and thus have arranged to make

changes to the database without directly opening the file through the front end i.e. '"F" frames.

7../ Interfa!e detais

#his addresses to the /;I design issues associated with the pro)ect. #he pro)ect involves

building an interface with good /;I and which is user friendly. #he interface basically

incorporates the menu including the functionalities viz open save print close.

:n the click event of optimize the system provides the user with the optimized code as

output on the screen.

#he exit option the system enables to exit from the application.

7.% Test Pan

2?


29/37

. Introduction

This Test Plan provides the strategy for testing the project College Bus

Management System. This section of the Test Plan document describes the folloing.

Purpose

!bjectives

a. "ocument Purpose

#his #est Plan reviews?

i. Axisting pro)ect information

ii. $usiness re6uirements and critical transactions to be tested

iii. #esting types and strategies to be implemented and

iv. " proposed testing schedule

b. !bjectives

#his document provides the platform for testing the pro)ect GCollege

$us %anagement &ystem1. #he ob)ective of testing is to see if the pro)ect meets the

&oftware Re6uirement &pecifications. #his document will provide 8 H the

guidelines for the testing team to test the functionalities embedded in the pro)ectand H help for evaluating the &oftware Juality of the pro)ect.

. Pro)ect &cope

This section of the Test Plan document describes the #$% Scope of the project

College Bus Management System and #&% !ut of Scope of the project College Bus

Management System.

a. Scope of the Project

GCollege $us %angement &ystem1 will be tested for its functionality on

the following parameters H ;nit testing H Integration testing HE &ystem testing

and H, Customer "cceptance #esting HC"#. Aach test is scheduled to take one

week with the Customer "cceptance test on E=8=E8=.

The testing includes testing for several functions li'e

(ogin feature

2@


30/37

"ata )ntry

Bus Scheduling

"ata *etrieval

b. !ut of Scope of the Project

Performance of the project College Bus Management System for

operation on a number of computers is out of scope of this project at this point of

time.

E. Pro)ect Resources

#able below describes the Roles Responsibilities and Resource 9ame for the

testing of the Pro)ect GCollege $us %anagement &ystem1.

Role Responsibilities Resource 9ameHs

#esters Plan testing activities

Axecute #est Cases

5ind report and track defects

%easure test effort

"nalyze results

5rancis and Rahul

Developers Deliver complete builds of the application

Provide #esters with feedback regarding

changes new functionality

Provide expertise and knowledge of the

application8under8test

Aliminate agreed upon defects

Rahul and 5rancis

$usiness "nalysts Interview ;sers

Create $usiness Re6uirements

Create #est &cenarios #est Cases

5rancis and Rahul

;sers Describe and review $usiness Re6uirements

Describe and review user profiles

Perform Customer "cceptance #esting HC"#

5rancis and Rahul

Desktop

"dministrators

Installation of software

#roubleshooting of hardware7software

Information regarding standard desktop

Rahul and 5rancis

:6


31/37

#able 8 Pro)ect Roles and Responsibilities

,. #est &trategies7#echni6ues

#his section of the document describes K H #est design and H #est Data for the

pro)ect GCollege $us %anagement &ystem1.

a. Test "esign

Considering the scope of the pro)ect and the time limitations we will be

performing following tests.

a% +nit Test ,

This test verifies the program logic and is based on the 'noledge

of the program structure.

b% -ntegration Test ,

This test verifies the entire systems functionality according to thedesign specification.

c% Business *e/uirements ,

This test verifies hether specific re/uirements of the

customer are met.

d% 0cceptance Testing ,

This test verifies hether the system needs to meet the

initial objectives and customers e1pectations.

2or performing the above mentioned tests3 e ill create test cases as shon in

table belo.

;se Case ID Description #est Case

;C8 ;se Case @ogin #C8

;C8 ;se Case Data Antry #C8

;C8E ;se Case $us &cheduling #C8E

;C8, ;se Case Data Retrieval #C8,

;se cases and #est Cases

:7


32/37

#able below describes the description of each test case mentioned in table and the

results expected from a corresponding test case.

;se

Case

ID

#est

Case ID

Description Axpected Result

;C8 #C8 ;ser enters a valid

username and password

;ser is granted the access to the

system

;C8 #C8 ;ser enters correct

username with wrong

password

;ser denied access and GIncorrect

;sername or Password1displayed

;C8 #C8E ;ser enters incorrectusername

;ser denied access and GIncorrect;sername or Password1displayed

;C8 #C8 If 9ame entered contains

special characters

Display error message

;C8 #C8 If fees paid is negative

alphabet or special

character

Display error message GIncorrect

Data1

;C8 #C8E If dues is negative

alphabet or special

character


Data1

;C8 #C8, Check if new record

stored successfully if no

errors in from.

&tore new record successfully

;C8E #C8 Input route no If bus no is negativealphabet or

special character display error

GI9C:RRAC# R:;#A 9:1

;C8E #C8 Check &top validity in &et

bus schedule

Display correct stop names for

selected bus route

:2


33/37

;C8E #C8E $us &cheduling?Check

#ime validity in &et bus

schedule

Display correct time slots for

selected bus route

;C8E #C8, $us &cheduling? Check if

new $us &chedule issaved correctly to the

Database under the

correct Route 9umber

9ew route should be saved in the

database with the correctparameters like &tops and #imings

;C8, #C8 If Receipt 9o. entered is

alphabet special character

or negative


Receipt 9o.1

;C8, #C8 Retrieve correct details

according to receipt no.

entered

Display Receipt Details for the

input Receipt 9o.

#able E K Description and the Axpected Results of each #est Case

b. "atabase

" -ead maintains Database that contains the login names and passwords of all the

users.

.

::


34/37

0. Pro)ect #asks7&chedule

#able , describes the schedule for the #est Plan of the pro)ect GCollege $us

%anagement &ystem

#ask "rtifacts Pro)ected Completion

#est Plan Completed #est Plan Fersion .= 088=

#est Anvironment

Prepared

-ardware and software 088=

#est Cases Recorded

and Axecuted

College $us #est Plan

Document version .= #est

Results Document

488=

Defects submitted

and tracked

;nit #est Results Document 8E8=

Integration test #est Plan Document Fersion

.=

8=E8=

Customer

"cceptance #est

#est Plan Document Fersion

.=

E8E8=

Pro)ect &chedule

+. Defect Responsibility7Resolution

Possible defects identified through manual testing will be discussed with

development team members to verify that the observed behavior constitutes a defect.

Defects found will be tried to be resolved. If not possible they will be delivered with the

deliverables as G4non Bugs1. Defect register will be maintained to keep a track of all

the defects found in the software.

L. Axit Criteria

:;


35/37

#esting can proceed to the next stage of the process when a sufficient proportion

of the current stage has been completed "ll exit criteria should be satisfied by the end of

the pro)ect.

4 /oals and Deliverables

5oals and deliverables of the test plan of the College Bus Management System are as

follos ,

a /oals?

#o accomplish all tasks described in this test plan.

#o install a measurable improvable repeatable and manageable test

process.

#o verify the functionality and content of the current version of the

application.

#o reduce the fre6uency of error associated with manual testing.

#o find and successfully track ==> of defects present along the user

path defined in this plan.

b Deliverables?

#est Planning &tage

#est Axecution and Defect #racking &tage

Avaluation and Improvement K this include

#est Cycle Avaluation

Pro)ect &ummary 7 Avaluation

7./ Test Case for 9s S!5eding

:


36/37

Test Case

Use

Cas

e

Test

Case

No.

Ste" Des!ri"tion Ex"e!ted

Rest

A!ta Rest

Hif different from

expected

S!!essf

;0aie

d

En&ironm

ent No.


37/37

#esting on platforms like @inux and %ac has not been performed

&tandalone system with no internet support.

8. 0tre En5an!ement

In 0tre (e try to de&eo" t5e foo(ing:

#he system can be made to allow access from multiple systems with a central system as

the &erver for databases.

.

College Bus Final Report

Documents

Transcript of College Bus Final Report