Online Bus Reservation System Group B

Project: Online Bus Reservation System

ONLINE BUS RESERVATION SYSTEM

SOUMITH CHUNCHU

SUBJECT : SOF501_7DFC

DATE : 12/17/2015

1


Content

S.NO Topic Page No1 Abstract 22 Project Integration Management 33 Project Scope Management 44 Work Breakdown Structure(WBS) 55 Project Cost Management 5 6 Project Time Management 8 7 Gantt Chart 88 Network Diagram 8 9 Project Quality management 1010 HR Management 1011 Procurement Management 1212 Stakeholder management 1313 Communication Management 20 14 Risk Management 2115 Use cases and Use Case Diagram 22 16 Test case design and Description 5117 Conclusion 60

18 References 61

2


Abstract

Now-a-days substantial numbers of people prefer bus transportation. Because of the

increasing

traffic and pollution in every country. Especially in India travelling through bus is a rapidly

growing business. Because India is the country with second highest population in the world.

In

India manual bus reservation system is in existence. It consumes lots of time to the

passengers.

Due to this reason a productive system is to be proposed in this paper to solve the issue of bus

reservation. The system is a web based online system and allows the passengers to check the

availability of buses, booking tickets online, availability of seats, timings of buses,

cancellation

of tickets. By using this system people can book tickets from any part of the country though

internet. This provides people an easy and faster way of reserving tickets for bus

transportation.

The online bus ticket reservation system (ORBS) can be used in many countries throughout the

world where there is manual reservation system. In this system validation of user is done in a

secure and efficient way. ORBS provides a group of works with interface environments. Also

there will be a database which will keep all the records that done by user while visiting the

page.

ORBS is connected with a company server database, thus no more connection with other

systems

is needed. In this paper the proposed reservation system for booking tickets online is built by

using java script, PHP, html, SQL and cascading style sheet.

Keywords: bus reservation, passengers, transportation, India

3


Project Integration Management: Project integration management includes initiation,

planning, execution, monitoring, and closing of the project.

Initiation: The Initiating Process Group is an essential step in completing your process. This

is the phase where you define your project and obtain authorization to complete your goals.

Planning: Project Planning Phase is to identify and document scope, business requirements,

tasks, schedules, costs, risk, quality, and staffing needs.

Execution: It is the execution of plans, processes, and procedures summarized and referenced

in the Project Plan. Particular attention is paid to the production and quality of the project.

Monitoring: The Monitoring and Controlling process oversees all the tasks and metrics

necessary to ensure that the approved and authorized project is within scope, on time, and on

budget so that the project proceeds with minimal risk.

Closing: The Closing phase includes all the activities necessary for the project are completed

and closing of the project.

4


Project Scope Management:

Our System will manage records of all users. Provides facilities for customers to reserve seats.

All details of the customers are collected. Design of a system that will benefit to operators and

passengers of all categories in traveling bus. Develop a cost effective, efficient and user

friendly graphic interface for bus reservation system. Provides timely and accurate report of

bus operational delay and other road mishaps. To perform the task of bus seat reservation

efficiently and effectively. Administrator will to generate and update the various types of

information and perform the reservation.

1. Analyzing the existing system

2. Manage record of all our users.

3. Provides facilities for customers to reserve seats.

4. All details of the customers are collected.

5. Design of a system that will benefit to operators and passengers of all categories in

5


traveling bus.

6. Develop a cost effective, efficient and user friendly graphic interface for bus reservation

system.

7. Provides timely and accurate report of bus operational delay and other road mishaps.

8. To perform the task of bus seat reservation efficiently and effectively.

9. To generate and update the various types of information and perform the reservation.

WORK BREAKDOWN STRUCTURE (WBS):-

Project Cost Management:

Managing the product cost is a major task in the project undertaking process. Because the

project must be completed within the given budget. Cost estimation is made at the initiation of

the project. An efficient product should be produced within the given budget. Project cost

estimation is done through COCOMO.

6


Project Cost Estimation by using COCOMO’81 (Constructive Cost Model)

Basic COCOMO

Type Effort Schedule

Semi PM= 2.4 (KLOC)1.05 TD= 2.5(PM)0.38

PM= person-month (effort)

KLOC= lines of code, in thousands

TD= number of months estimated for software development (duration)

Effort Estimation:

Assuming that the project is consist of 5,000 source lines of code

Effort = 2.4* (5)1.05 = 13 Person-Months

COCOMO estimates that 13 Person-Months of effort is required to complete it.

Project /product Costing:-

Type of component Complexity of

Components

Lo Avera

g

e

Hig Tot

External inputs 5 1 0 6

External outputs 2 1 0 3

External inquiries 2 2 0 4

Internal logical file 3 2 5

External interface

files

3 2 0 5

7


Total no of un adjusted Function points 23

Function point Analysis:-

Calculate Fi's Value

Data communications 2

Distributed data

processing

3

Performance 4

Heavily used

configuration

3

On-Line data entry 3

End-user efficiency 5

On-Line update 5

Complex processing 3

Reusability 4

Operational ease 5

Multiple sites 0

Facilitate change 3

Total 40

To compute function points (FP), the following relationship is used:

FP est. = Count Total * [0.65+ 0.01 *(Fi)]

= 23 * [0.65 + 0.01 * 40]

= 24.15

Project Time management:

8


Time for the project is based on the requirement of the customer. A clear schedule is prepared

between the projects initiations to termination to deliver the project to the costumer within the

given time. In some case to increase the deliverability some changes are made to the planned

schedule of the project. Duration of the project is estimated by using:-

Duration Estimation:

The duration of a project is based on the effort predicted by the effort equation:

TD = 2.5 * (Effort) 0.38

TD=2.5 * (13)0.38 =7 Months

Gantt chart:

NETWORK DIAGRAM:

Critical Path Identification Table:

9


Determining the following six parameters for each activity which can identify the critical

path:

ES: earliest start time

ES (K) = max [EF (J) J is an immediate predecessor of K]

EF: earliest finish time

EF (K) = ES (K) + Duration (K)

LF: latest finish time

LF (K) = min [LS (J): J is a successor of K]

LS: latest start time

LS (K) = LF (K) – Duration (K)

TS: Total Slacks

TS (K) = LS (K) – ES (K)

FS: Free Slack

FS (K) = min [ES (J): J is successor of K] – EF (K)

Activity Duration ES EF LS LF TS FS

A 5 0 5 0 5 0 0

B 3 0 3 3 6 3 0

C 8 5 13 5 13 0 0

D 7 5 12 6 13 1 2

E 7 0 7 6 13 6 0

F 4 13 17 13 17 0 6

G 5 17 22 17 22 0 0

The parameters and slacks are calculated as follows:

The critical path is: A, C, F, and G

Project Quality Management:

10


Maintaining the quality of the product that is delivered is one of the main function. The

product should satisfy the requirements of the customer including the standard of quality

required for the costumer. Quality of the product is tested by employing:-

ISO 15504 (Software Process Improvement and Capability Determination or SPICE)

ISO 9000

HR Management:

Human resource management follows the recruitment of candidates required for the

completion of the project. Human resource manager should review the resumes of the

candidates and select the candidates required for the project. HR manager recruit the

candidates basing on skills, experience, and requirement of the project.

Allocation of People to Activities:

11


Days

Members

Name

Rahul

Nitesh

Soumith

Muqeet

Shahab

OBS:

12


Activity Bar Chart

+

Procurement Management:

13


It is a process of acquiring the required equipment and tools that are required for the project

undertaken. Following processes are included in the procurement management:-

Identify the goods and services to procure.

Complete Purchase Orders and issue to suppliers.

Agree on delivery timeframes and methods.

Receive goods and services from suppliers.

Review and accept the items procured.

Approving the supplier payments.

Hardware and Software Specification:

RAM 64 MB

Processor 1 GHz

Operating System Windows

Type 32bits, 64bits.

Tools and technologies Used

Language: PHP, HTML, CSS, JavaScript, AJAX , J Query.

Tools :- Notepad++, Dreamweaver, XAMPP.

Stakeholder management:

Stakeholders are the people involved in the project directly or indirectly. In our project

stakeholders directly involved are the customers (DAEWO COUSTMERS). Stakeholders

involved in the project indirectly are the people who use the OBRS. Managing the

Stakeholder is an important task because it provides the up-to-date requirements of the

project. Necessary changes should be made to the project at some stages by considering the

requirements of the stakeholder. Steps followed in stakeholder management is as following:-

Identify Stakeholders

14


Sample Stakeholder Analysis

Classify Stakeholder Positions

Determine Stakeholder Management Approach

Designing the requested deliverables

Stakeholder Initial Requirements:

Para Initial Requirements

1.0 Administration login.

1.0 Administration logout.

1.0 A customer “shall” visit himself to the system for buses and ticket information

1.0 A client shall requests for a ticket he needed

1.0 Feedback from users

1.0 System shall update the client Request.

1.0 A unique seat number shall be issued for every individual passenger.

1.0 A system will view the passenger information.

2.0 A system will search the seats.

2.0 A system will accept or reject the client request.

2.0 A system will generate confirmation message

2.0 The System “shall” generate an action event for a corresponding administrator when a

request is placed for updating of passenger details etc

2.0 Corresponding administrator “shall ” view his Action List containing different

actions, and correspondingly process these pending actions

Allocate requirements

Para Initial Requirements Use Case Name

15


1.0 Administration login. UC_ login

1.0 Administration logout. UC_ logout

1.0 A customer “shall” visit himself

to the system for buses

and ticket information

UC_Information_Request

1.0 Feedback from users UC_ feedback

1.0 A client shall requests for a

ticket he needed.

UC_Place_Order_Request

1.0 System shall update the client

Request

UC_update_request

1.0 A unique seat number shall be

issued for every

individual passenger.

UC_Number_seats_Request

1.0 A system will view the

passenger information

UC_View_Request

2.0 A system will search the seats. UC_search_request

2.0 A system will accept or reject

the client.

UC_accept_Request

UC_reject_Request

2.0 A system will generate

confirmation message

UC_Number_conformtion_messae_Request

2.0 The System “shall” generate an

action event for a

corresponding

administrator when a

request is placed for

updating of passenger

details etc

UC_create_action

16


2.0 Corresponding administrator

“shall ” view his Action

List containing different

actions, and

correspondingly process

these pending actions

UC_view_action

Prioritize requirements

Par Rank Initial

Requir

ements

Use

C

a

s

e

I

D

Use Case Name

1.0 Highest Administration

login.

UC_1 UC_ login

1.0 Highest Administration

logout.

UC_2 UC_ logout

1.0 Highest A customer

“shall”

visit

himself

to the

system

for

UC_3 UC_Information_Request

17


buses

and

ticket

informa

tion

1.0 Highest A client shall

request

s for a

ticket

he

needed.

UC_4 UC_Place_Order_Request

1.0 Highest System shall

update

the

client

Reques

t

UC_5 UC_update_request

1.0 Highest A unique seat

number

shall be

issued

for

every

individ

ual

passeng

er.

UC_6 UC_Number_seats_Request

1.0 Mediu

m

Feedback from

users

UC_7 UC_ feedback

1.0 Mediu

m

A system will

view

UC_8 UC_Update_Request

18


the

passeng

er

informa

tion

2.0 Mediu

m

A system will

search

the

seats.

UC_9 UC_search_request

2.0 Mediu

m

A system will

accept

or

reject

the

client.

UC_10 UC_accept_Request

UC_reject_Request

2.0 Mediu

m

A system will

generat

e

confirm

ation

receipt

UC_11 UC_Number_conformaion__Requ

est

2.0 Low The System

“shall”

generat

e an

action

event

for a

corresp

onding

UC_12 UC_create_action

19


adminis

trator

when a

request

is

placed

for

updatin

g of

passeng

er

details

etc

2.0 Low Corresponding

adminis

trator

“shall ”

view

his

Action

List

contain

ing

differen

t

actions,

and

corresp

ondingl

y

process

UC_13s

s

UC_view_action

20


these

pendin

g

actions

Requirements Traceability Matrix:

Sr# Para System Specification

Text

Build Use Case Name Category

1 1.0 A customer “shall” visit

himself to the

system for buses

and ticket

information

B1 UC_Information_Request Business

2 1.0 A client shall requests for

a ticket he

needed.

B1 UC_Place_Order_Request Business

3 1.0 System shall update the

client Request

B1 UC_update_request

Business

4 1.0 A unique seat number

shall be issued for

every individual

passenger.

B1 UC_Number_seats_Request

Business

5 1.0 A system will view the

passenger

information

B1 UC_Update_Request Business

6 2.0 A system will search the

seats.

B1 UC_search_request Business

7 2.0 A system will accept or B1 UC_accept_Request Business

21


reject the client

request.

UC_reject_Request

8 2.0 A system will generate

confirmation

message.

B1 UC_Number_recipient_Request Business

9 2.0 The System “shall”

generate an action

event for a

corresponding

administrator

when a request is

placed for

updating of

passenger details

etc

B1 UC_create_action Business

10 2.0 Corresponding

administrator

“shall ” view his

Action List

containing

different actions,

and

correspondingly

process these

pending actions

B1 UC_view_action Business

Communication Management:

Communication among the employees of the project should be effective. Communication

management involves the following:-

22


communication skills

organizational skills

leadership Skills

Team building skills

technology skills

Risk management:

It is a process of identification, analysis and either acceptance or mitigation of uncertainty in

investment decision-making. Risks can be avoided by following the plans that are employed

at the process of initiation of the project. Risks like cost overflow can be avoid by monitoring

the cost throughout the execution process and by preparing a proper estimation cost of the

project.

23

IT Project

Business

Competitors

Suppliers

Cash flow

Technical

Hardware

Software

Network

Organizational

Executivesupport

User support

Team support

ProjectManagement

Estimates

Communication

Resources


SCOPE

Primary Actor

Online Bus Reservation System

Administrator, User

Stakeholder & Interest Actor wants accurate processing of login page.

So, that no one else accesses the website actor

panel.

Description The Actor get login into actor panel of website.

Precondition The server is in running state.

Success Guarantee (Post Condition): The actor logged in successfully.

Main Success Scenario: *. The Actor enters user name and password.

*. The username and password is validated from

the database.

*. Create session and bring administrator to actor

panel if the username and password is correct.

Extension: At any time system fails to connect database.

*. System displays an error message.

*. Ask actor to re-enter username and password.

Special Requirement: The process will work well with good internet

speed.

24


Use Case UC1: Administrator Login

25


26

Use Case UC2: Administrator Logout

SCOPE Online Bus Reservation System

Primary Actor Administrator, System

Stakeholder & Interest Admin logout.

Description The system interacts with queries.


Success Guarantee (Post Condition): The system interacts with request successfully.

Main Success Scenario: *. Admin logout successfully.




speed.



Primary Actor Administrator, System, User

Stakeholder & Interest Admin login.

Description The system interacts with queries and then show seats.


Success Guarantee (Post Condition): The system interacts with request successfully.

Main Success Scenario: *. Admin login successfully.



Special Requirement: The process will work well with good internet speed.

Use Case UC3: View seats

27


Use Case UC4: Update seats


Primary Actor Administrator or System.

Stakeholder & Interest The administrator wants the successful

updated seats record in the database.

Description The system updated record in the database.

Precondition The administrator is logged into admin panel.

Success Guarantee (Post Condition): *. The record is updated in the database.

*. Give message that records updated

successfully.

Main Success Scenario: *. The admin enters admin panel by login.

*. Update the record in record section.

*. The records are saved in the database.



*. Ask actor to re-enter username and

password.


speed.

28



Primary Actor Administrator

Stakeholder & Interest The administrator wants the successful edited

record in the database.

Description The administrator edited seats record in the

database.

Precondition The administrator is logged into admin panel.

Success Guarantee (Post Condition): *. The record is edited in the database.

*. Give message that records edited

successfully.

Main Success Scenario: *. The admin enters admin panel by login.

*. Edit the record in record section.

*. The records are saved in the database.




password.


speed.

Use Case UC5: Edit seats

29



Primary Actor User

Stakeholder & Interest The user wants to successfully search the

information from website.

Description The user searches the required information.

Precondition Records/ Information is added in the database.

Success Guarantee (Post Condition): Information is searched successfully and

showed to user.

Main Success Scenario: *. The user enters the keyword of information

in search text box.

*. Press/ Click the search button.

*. Relevant record is fetched from database

and showed to the user.




password.


speed.

Use Case UC6: Search Information

30



Primary Actor Administrator

Stakeholder & Interest The Administrator wants to successfully delete

the information from website.

Description The Administrator deletes the required

information.

Precondition Records/ Information is deleted from the

database.

Success Guarantee (Post Condition): Information is searched successfully and

showed to administrator.

Main Success Scenario: *. The administrator enters the keyword of

information in search text box.



and showed to the administrator.




password.


speed.

Use Case UC7: Delete Seats

31



Primary Actor User, Administrator

Stakeholder & Interest Actor wants to view the seats records

available.

Description The actor get login into admin panel of

website.

Precondition The actor successfully logged in.

Success Guarantee (Post Condition): The actor logged in successfully and views the

required seat records.

Main Success Scenario: *. The actor enters the keyword of information

in search text box.



and showed to the actor.




password.


speed.

Use Case UC8: View Seats Records

32



Primary Actor User, Administrator

Stakeholder & Interest Actor wants to view the routs information

available.

Description The actor get login into admin panel of

website.

Precondition The actor successfully logged in.

Success Guarantee (Post Condition) The actor logged in successfully and views the

required rout information.

Main Success Scenario *. The actor enters the keyword of information

in search text box.


*. Relevant record is fetched from database and

showed to the actor.

Extension At any time system fails to connect database.



password.

Special Requirement The process will work well with good internet

speed.

Use Case UC9: Routs Information

33


Use cases & Use case Diagrams

34


35


36


37


Admin login

In admin panel,firstly admin will give his/her name and password then he/she will get access

to this site.After login he/she will be able to perform some importand function like he/she will

add schedule,view users,view feedback.All these activites will automatically be stored in

database.

38


Add Schedule

After login admin will be able to add/delete/edit schedule, like he/she will add/set

sources,destination,depart time,arival time,cost of travels.

39


View User

Admin will be able to see users details like user’s name, conic, cell no, source, destination,

depart time, no of seats that user booked. Admin will also be able to cancel booking of users.

40


View comment

Admin will be able to see user’s comments (feedback), after reading comments he/she will be

able to delete comments.

41


Home page:

This is home page of our website. Different terminals of different cities are shown here.

Facilities in Daewoo are shortly describe for example punctuality, audio/visual entertainment,

luxury buses and luggage etc. Also overview of Daewoo Express is describe.

42


Schedule:

At this page schedule of buses are shown. Select source and destination from option and click

on submit button. Then new page open which tells about depart time, arrival time, travel time

and fare.

Services:

Services which are mention on home page, at this page briefly describe. Punctuality,

audio/visual entertainment, luggage and luxury buses.

43


Terminals

In this page of our website, we tell about some popular terminals of Daewoo, and also given

brief contact information and address of these terminals one by one.

44


Booking

In this module user will do booking of seats by filling this form, like he/she have to select

source, destination, timing, must have to fill no of seats which he/she want to reserve from

available seats, name, mobile no, conic no.

45


Feedback

In this module user will be able to give us feedback if he/she want to do, its up to their own

choice either they want to or not.

46


About Us

In this user will be able to know our company.

47


Document Information

Category Information

Customer All users

Project <Online bus reservation system >

Document Test Plan

Document Version 1.0

Identifier PGBH01-2003-TP

Status Draft

Author(s) <BSSE-F10-008,BSSE-F10-017 >

Approver(s) PM

Issue Date May 01, 2014

Document Location

Distribution

1. Advisor

2. PM

3. Project Office

Definition of Terms, Acronyms and Abbreviations

This section should provide the definitions of all terms, acronyms, and abbreviations required

to interpret the terms used in the document properly.

Term DescriptionOBRS Online bus reservation system

48


Purpose of Document

This chapter is intended to deliver a high level overview of “Online Bus Reservation System”.

Software developers, System Engineers and Testers (with a basic knowledge of software;

what is it? how it is generally tested) will benefit from this chapter.

Project Overview

We are developing an Online Bus Reservation System through which people can reserve

seats. Reservation System is an Internet based application that can be access throughout the

Internet and can be access by anyone who has a net connection. OBRS will automate the

reservation of tickets and enquires about availability of the tickets. OBRS includes email

information for the tickets. OBRS provides a group of works with interface environments.

Also there will be a database which will keep all the records that done by user while visiting

the page. OBRS is connected with a company server database, thus no more connection with

other systems is needed.

Scope of Testing

The scope of our test plan is to find and report as many bugs as possible to improve the

integrity of our program. Although exhaustive testing is not possible, we will exercise a broad

range of tests to achieve our goal. We will be testing Online Bus Reservation System that

includes the data entry and data related work. Our user interface to utilize these functions is

designed to be user-friendly and provide easy manipulation of the data.

Test Plan Strategy

These test plans should be able to show all the Online Bus Reservation System functionality

and features defined in the requirements document. For each level of testing, a separate test

plan is prepared with the following set of deliverables:

Test Case Number

Features to be tested

49


Items to be tested

Pass / Fail criteria

Input

Output Results

Unit Testing

Definition:

Unit testing means testing in which each function independently verify correct processing in a

standalone environment. Unit Test consists of testing individual programs or subroutines as

they are written instead of testing the entire system after it has been written. The testing of the

smaller building blocks is done first and then these blocks are combined and tested. Unit

testing will be conducted to verify the implementation of each necessary requirement changes.

The requirements will be tested and verified by members only. After any new requirement is

added, unit testing will be done for these features.

Participants:

Developers, Test Team & some other project personnel are involved in unit testing

Methodology:

Initial Unit Test will be conducted by the developers.

As the completed modules are received from the development department, the test team will

start the Unit Test on these modules

Integration Testing

Definition:

Integration testing is to ensure that all interacting subsystems in a system interface correctly

with one another to produce the desired results. Furthermore, in trying to attain this goal,

50


integration tests will ensure that the introduction of one or more subsystems into the system

does not have an adverse effect on existing functionality.

Participants

This phase is performed by an independent test team.

Methodology:

Integration tests will be run according to the Integration Test Plans by the Test Team Leader

or Test Team Member.

If any of the actual results do not agree with expected results, the person performing the test

will complete a Problem Report (PR).

After the necessary action has been taken to resolve the problem, the test run will be

performed again from the beginning of the test step .The Test Plan may need to be updated,

depending on the results of the test.

System Testing

Definition:

The goal of System Testing is to ensure that the system performs as per the functional

requirements specified by client. A system test covers the testing of functions within the

system. System testing is performed once integration testing has been completed.

Participants:

System Tests shall be run by the System Testing Team.

Methodology:

a. Verify that the System Test Environment has been created and that it is functional.

b. Execute the system test plan scenarios as assigned to each test team member

c. Create a problem report for deviations from the expected results documented in the

system test plan scenario. Interact with support team to help resolve problem reports.

d. Update the tracking report to reflect test step execution and completion.

Test Environment

The goal is to create a testing environment as close to the development environment as

51


possible and to provide an automated black box test suite that can be run when changes are

made to the software. The test environment is the same windows environment used for

software

development. Below are the hardware and software requirements for the test environment.

Hardware

The hardware and network requirements for testing activities are:

Ref Hardware Purpose

1. Any PC where we can

connect to database

To be able to run the prototype of

OBRS

Software

The software requirements for testing activities are:

Ref Software Purpose

1. Windows 2007,2008 etc. The system shall operate in

Windows operating systems

2. SQL Server 2005 For the database server as all the

development will be done in SQL

2005

3. Microsoft VS For designing and developing the

application

52


Schedule

Testing Activities Begin End

__________________________________________________________________________

Designing Test Cases 05-10-2015 07-12-2015

Executing Test Cases 08-10-2015 13-12-2015

Unit Testing 07-10-2015 12-12-2015

Integration Testing 14-10-2015 15-12-2015

System Testing 13-10-2015 14-12-2015

Control Activities

Reviews

The project team will perform reviews for each Phase. (i.e. Requirements Review, Design

Review, Code Review, Test Plan Review, Test Case Review and Final Test Summary

Review). A meeting notice, with related documents, will be emailed to each participant.

Bug Review meetings

Regular weekly meeting will be held to discuss reported defects. The development department

will provide status/updates on all defects reported and the test department will provide

addition defect information if needed. All member of the project team will participate. Test

preparation and testing progress will be formally reported during a weekly Status Meeting.

Change Request

Once testing begins, changes to the system are discouraged. If functional changes are

required, these proposed changes will be discussed with the Change Control Board. The

Change Control Board will determine the impact of the change and if/when it should be

implemented.

Defect Reporting

53


When defects are found, the testers will complete a defect report on the defect tracking

system. The defect tracking Systems is accessible by testers, developers & all members of the

project team. When a defect has been fixed or more information is needed, the developer will

change the status of the defect to indicate the current state. Once a defect is verified, as

FIXED by the testers, the testers will close the defect report.

This section also indicates when and how the review meetings will be conducted and who

would participate in these activities.

A status report will be prepared by the Test Controller to facilitate this meeting. This report

will contain the following information:-

1. Current Status v. Plan (Ahead/Behind/On Schedule)

2. Progress of tasks planned for previous week

3. Tasks planned for next week including tasks carried from previous week

4. Issues/Risks

Functions to be tested

List of all functions needed to be test. The following scheme is recommended for listing and

description of requirements to be tested.

1.1 Login Functionality

1.2 View Functionality

1.3 Search information Functionality

1.4 Edit Functionality

1.5 Reserve seats functionality

1.6 Feedback functionality

Functions not to be tested

This is a listing of what is 'not' to be tested from the user's viewpoint of what the system does.

This is not a technical description of the software, but a user's view of the functions. Identify

why the feature is not to be tested, there can be any number of reasons. They may include

functions i.e.

54


Not to be included in this release of the Software.

Low risks, has been used before and was considered stable.

Will be released but not tested or documented as a functional part of the release of this

version of the software.

According to above mention points, neither there are such functions present in OBRS that

can’t be test, nor function that don’t require testing.

Test Case Design and Description

Summarize the common attributes of test cases.

Test Case ID: 1

Test Case ID: Id # 1 QA Test Engineer

Test case Version: Version # 1 Reviewed By

Test Date: 10-11-2015 Use Case Reference(s)

Revision History No

Objective Whether admin is successfully login or not.

Product/Ver/Module Login of OBRS.

Environment: RAM 64 MB,Processor 1 GHz,Operating System Window ,Type 32bits, 64bits, Window 7

and above

Assumptions: Power failure, testers team are not available, time shorten

Pre-Requisite: Database should be properly connected and in working form

Step No.

Execution description

Procedure result

1

2

3

4

Open OBRS homepage

'Enter Designation, User ID and password and press LOGIN

Button

i.e. Designation= Admin

i.e. User ID= Iqra

Enter Password and press LOGIN Button

i.e. 'Password= 12345

Enter user ID and Password and press LOGIN Button i.e.

'USER ID= XYX & Password = XYZ

Display Warning Message Box "Please

Enter Password"


Enter User ID "


Enter Correct User ID and

Password”

55


5 For User there is no need to login, he/she can use the site

without login.

……

Comments; In above Test case correct User ID” 123#@!” and password is “ABC”

Passed Failed Not Executed

Test Case ID: 2

Test Case ID: 2 QA Test Engineer


Test Date: 10-11-2015 Use Case Reference(s) Relation to use case #1

Revision History

No

Objective Whether admin can view users or not.

Product/Ver/Module Registration module Of OBRS


and above


Pre-Requisite: Database should be properly connected and manager must be login

Step No.


Procedure result

1

2

3

Admin can see users and can take actions.

Admin selects the “View User” option

Enter the action

System displays a view seats page

System display the form

System and admin verifies the form if

it is correct then the

information Is stored. Updated

in the database.

Comments


56


Test Case ID: 3



Test Date: 15-11-2015 Use Case Reference(s) Relation to use case # 1,2

Revision History No

Objective Test whether Edit functionality working is valid or invalid

Product/Ver/Module Edit module Of OBRS

Environment: RAM 64 MB,Processor 1 GHz,Operating System Windows

Type 32bits, 64bits,Window 7 and above


Pre-Requisite: Database & internet should be properly connected.

Step No.


Procedure result

1

2

3

Administrator must login

Admin: Select add schedule/view user /view comment

which you want to Edit

Enter Ok button

There form open

System displays a form

Enter new details

Comments:


Test Case ID: 4


57




Revision History No

Objective Test whether the user can easily search schedule and seat information

Product/Ver/Module Search module Of OBRS


and above



Step No.


Procedure result

1

2

User can see services and terminal information

User : Search pages from menu

Select “Search” option from the menu

Relevant pages will be open

Site display pages

Comments:


Test Case ID: 5




Revision History No

Objective Test reservation seat functionality work properly or not

Product/Ver/Module Reserve seat module of OBRS


and above


58



Step No.


Procedure result

1

2

User will see schedule

User will do booking according to schedule

There form open

System displays a form

Comments:


Test Case ID: 6




Revision History No

Objective Test whether Feedback functionality working is valid or invalid

Product/Ver/Module Feedback module Of OBRS


and above



Step No.


Procedure result

1

2

3

User will give feedback

Enter Name

Enter Suggestion

Click on Submit button

There form open

Success message shows

59


Comments:


Traceability Matrix

<Test case name/Id>

Sr.

no.

Requirement ID Use Case ID GUI ID Test case ID Status Date

Completed1

2

3

4

5

6

Requirement #1

Requirement #2

Requirement #3

Requirement #4

Requirement #5

Requirement #6

use case #1

use case #2

use case #3

use case #4

use case #5

use case #6

GUI ref# 1

GUI ref#2

GUI ref#3

GUI ref#4

GUI ref#5

GUI ref#6

Test case ID#1

Test case ID#2

Test case ID#3

Test case ID#4

Test case ID#5

Test case ID#6

Complete

Complete

Complete

Complete

Complete

Complete

10-05-2014

10-05-2014

10-05-2014

15-05-2014

17-05-2014

17-05-2014

Major Deliverables

This section lists what will be delivered at the end of the test phase, such as:

Test plan

Test cases

Test summary report

Risks and Assumptions

60


Below are the issues that may affect the development and operation of the test plan, e.g.

communications, security, training.

Ref Issue Action

1. Testing Group needs to be

trained.

Requirements will be explained to

the testing group.

2. Testing Group needs to be

trained on security

processes check.

Security is an important component

of this prototype. Testing group

needs to be training on security

processes and Web services.

Assumptions

All assumptions regarding the test plan are below.

Ref Assumption Impact

1. Database SQL Server

2005 is running and

system tables are

installed.

To be able to access OBRS

system tables and process

requests.

2. All testers have database

connectivity.

To be able to test some of the test

cases.

3 Testers have username

and passwords setup for

by administrators.

Login pages will be required for

tester. To be able to test some test

cases.

Dependencies

The main dependencies of our system regarding the plan are:

61


Ref Dependency Action

1. Database availability. Required tables and process will be

setup from the database server for

tester to be able to access.

Exit Criteria

The Exit Criteria detailed below must be achieved before the software can be recommended

for promotion to Acceptance status. Furthermore, it is recommend that there be a minimum 2

days effort for Final Integration testing AFTER the final fix/change has been retested.

All High Priority errors from System Test must be fixed and tested.

All functions identified in the requirement document are present and working.

No more than three medium priority problems open.

If any medium or low-priority errors are outstanding - the implementation risk

must be signed off as acceptable by Business Analyst and Business Expert

Project Integration Test must be signed off by Test Controller and Business

Analyst.

Business Acceptance Test must be signed off by Business Expert.

62


Conclusion

Daewoo is Online Bus reservation System which provides online reservation of bus.

This system is user friendly and accurate.

This system is available 24 hours and efficient in reservation.

It has no hidden costs in fares.

63


References

Frame, J. Davidson, Managing Projects in Organizations: How to Make the Best Use of Time,

Techniques, and People, 3rd edition, Jossey-Bass, 2003

Kerzner, Harold, Project Management: Project Management: A Systems Approach to

Planning, Scheduling, and Controlling, 10th edition, Wiley, 2009

Larson, Elizabeth and Richard, Requirements Management, Part 1: Requirements Planning,

Watermark Learning, Inc., 2009

Lewis, James, The Project Manager's Desk Reference, 3rd edition, McGraw-Hill, 2006

Martin, Paula, Tate, Karen, the Project Management Memory Jogger: A Pocket Guide for

Project Teams, GOAL/QPC, 1997

Meredith, R. Jack and Mantel, Jr., Samuel J., Project Management: A Managerial Approach,

7th edition, Wiley, 2008

64

Date post:	11-Apr-2017
Category:	Documents
Upload:	soumith-chunchu
View:	185 times
Download:	8 times

Online Bus Reservation System Group B

Documents