bus route system

8/3/2019 Bus Route System

1/50

ACKNOWLEDGEMENT

A project like this takes quite a lot of time to do properly. As is often the case, this project

owes its existence and certainly its quality to a number of people, whose name does not

appear on the cover. Among them is one of the most extra ordinary programmers it has

been my pleasure to work with Mr.Jhaber mal who did more than just check the facts by

offering thoughtful logic where needed to improve the project as a whole.

We also thank to Mrs. Saroj Hirnwal (H.O.D. -IT Deptt. SBCET, Jaipur) who

deserves credit for helping me done the project and taking care of all the details that most

programmers really dont think about. Errors and confusions are my responsibility, butthe quality of the project is to their credit and we can only thank them.

We are highly thankful and feel obliged to Milan Travels staff members for nice Co-

Operation and valuable suggestions in my project work.

We owe my obligation to my friends and other colleagues in the computer field for their

co-operation and support.

We thank God for being on my side.


2/50

CONTENTS

Chapter 1 Introduction

Chapter 2 Development model

Chapter 3 System Study

Chapter 4 Project Monitoring System

Chapter 5 System Analysis

Chapter 6 Operating Environment

Chapter 7 System Design

Chapter 8 Screen Shoots

Chapter 9 System Testing

Chapter 10 System Implementation

Chapter 11 Conclusion

Chapter 12 Scope of the Project


3/50

Chapter-1

Introuction

In bus route system there has been a collection of buses, agent who are booking tickets

for customers journey which give bus number and departure time of the bus. According

to its name it manages the details of all agent, tickets, rental details, and timing details

and so on. It also manages the updating of the objects.

In the tour detail there is information about bus, who has been taking customers at their

destination, it also contain the detailed information about the customer, who has been

taken from which bus and at what are the number of members he or she is taking his/her

journey.

This section also contain the details of booking time of the seat(s) or collecting time of

the tickets, this section also contain the booking date and the name of agent which is

optional, by which the customer can reserve the seats for his journey

In Bus no category it contains the details of buses which are old/new. New buses are

added with the details with bus no, from city to the city, type of the bus, rent of a single

seat, if the bus has sleeper than the cost of sleeper, if the cabin has the facility for sitting

than the cost of cabin seats, tour timings of the new bus has also been stored. How many

buses are currently given and available in office?

In seats specification, it gives the list of given issued and currently available seats and

contain the information about seats like sleeper, cabin etc.

The main objective of this project is to provide the better work efficiency, security,

accuracy, reliability, feasibility. The error occurred could be reduced to nil and working

conditions can be improved.


4/50

Chapter-2

Development model

Software Process Model

Our project life cycle uses the waterfall model, also known as classic life cycle model or

linear sequential model.

The Waterfall Model

The waterfall model encompasses the following activities:

System/information Engineering and Modeling

System Engineering and Analysis encompass requirements gathering at the system level

with a small amount of Top-level design and analysis. Information Engineering

encompasses requirements gathering at the strategic business level and at the business

area level.

Software requirements analysis

Software requirements analysis involves requirements for both the system and the

software to be document and reviewed with the customer.

System/InformationEngineeringAnalysis Design Code Test


5/50

Design

Software design is actually a multi-step process that focuses on for distinct attributes of a

program: data structure, software architecture, interfaces representation and procedural

detail. The design process translates requirements into a representation of the software

that can be accessed for quality before coding begins.

Code Generation

Code-Generation phase translates the design into a machine-readable form.

Testing

Once code has been generated, program testing begins. The testing focuses on the logical

internals of the software, ensuring that all statement have been tested, and on the

functional externals; that is, conducting test to uncover errors and ensure that define input

will produce actual results that agree with required results.

Support

Software will undoubtedly undergo change after it is delivered to the customer. Change

will occur because errors have been encountered, because the software must be adapted to

accommodate changes in its external environment or because the customer requires

functional or performance enhancements.


6/50

Chapter-3

System Study

Before the project can begin, it becomes necessary to estimate the work to be done, the

resource that will be required, and the time that will elapse from start to finish. During

making such a plan we visited site many more times.

3.1 Project planning objectives

The objective of software project planning is to provide a framework that enables the

management to make reasonable estimates of resources, cost, and schedule. These

estimates are made within limited time frame at the beginning of a software project and

should be updated regularly as the project progresses. In addition, estimates should

attempt to define best case and worst case scenarios so that project outcomes can be

bounded.

3.2 Software Scope

The first activity in software project planning is the determination of software scope.

Software scope describes the data and control to be processed, function, performance,

constraints, interfaces, and reliability.

3.2.1 Gathering Information Necessary for Scope

The most commonly used technique to bridge communication gap between customer and

the software developer to get the communication process started is to conduct a

preliminary meeting or interview. When I visited the site we have been introduced to the

Manager of the center, there were two other persons out of one was the technical adviser

and another one was the cost accountant. Neither of us knows what to ask or say; we were

very much worried that what we say will be misinterpreted.

We started to asking context-free questions; that is, a set of questions that will lead to a

basic understanding of the problem. The first set of context-free questions was like this:

What do you want to be done?


7/50

Who will use this solution?

What is wrong with your existing working systems?

Is there another source for the solution?

Can you show us (or describe) the environment in which the solution will

be used?

After first round of above asked questions. We revisited the site and asked many more

questions considering to final set of questions.

Are our questions relevant to the problem that you need to be solved?

Are we asking too many questions?

Should we be asking you anything else?

3.2.2 Feasibility

Not everything imaginable is feasible, not even in software. Software feasibility has four

dimensions:

Technologyis a project technically feasible? Is it within the state of the art?

Finance Is it financially feasible?

Timewill the project be completed within specified time?

Resourcesdoes the organization have the resources needed to succeed?

After taking into consideration of above said dimensions, we found it could be feasible for us

to develop this project.

3.3 Software Project Estimation

Software cost and effort estimation will never be an exact science. Too may variables

human, technical, environmental, politicalcan affect the ultimate cost of software and effort

applied to develop it. However, software project estimation can be transformed a black art to

a series of systematic steps that provide estimates with acceptable risk.

To achieve reliable cost and effort estimates, a number of options arise:

Delay estimation until late in the project (since, we can achieve 100% accurate estimates after

the project is complete!)


8/50

Base estimates on similar projects that have already been completed.

Use relatively simple decomposition techniques to generate project cost and effort estimates.

Use one or more empirical models for software cost and effort estimation.

Unfortunately, the first option, however attractive, is not practical. Cost estimates must be

provided Up front. However, we should recognize that the longer we wait, the more we

know, and the more we know, the less likely we are to make serious errors in our estimates.

The second option can work reasonably well, if the current project is quite similar to past

efforts and other project influences (e.g., the customer, business conditions, the SEE,

deadlines) are equivalent. Unfortunately past experience has not always been a good indicator

of future results.

The remaining options are viable approaches the software project estimation. Ideally, the

techniques noted for each option be applied in tandem; each used as cross check for the other.

Decomposition techniques take a divide and conquer approach to software project

estimation. By decomposing a project into major functions and related software engineering

activities, cost and effort estimation can be performed in the stepwise fashion.

Empirical estimation models can be used to complement decomposition techniques and

offer a potentially valuable estimation approach in their own right. A model based onexperience (historical data) and takes the form

D = f (vi)

Where d is one of a number of estimated values (e.g., effort, cost, project duration and we are

selected independent parameters (e.g., estimated LOC (line of code)).

Each of the viable software cost estimationoptions is only as good as the historical data used

to seed the estimate. If no historical data exist, costing rests on a very shaky foundation.


9/50

Chapter-4

Project Monitoring System

4.1 PERT Chart

Program evaluation and review technique (PERT) and critical path method (CPM) are

two project scheduling methods that can be applied to software development. These

techniques are driven by following information:

Estimates of Effort

A decomposition of the product function

The selection of the appropriate process model and task set

Decomposition of tasks

PERT chart for this application software is illustrated in figure 3.1. The critical Path for

this Project is Design, Code generation and Integration and testing.

Figure 4.1 PERT charts for Bus Route System.

Chapter-5

Integration

and test

July 20, 2010

Design

May 24, 2010

Requirement

Analysis

May 17, 2010

Start

Coding

June 10, 2010

Documentation and

Report

Aug 1, 2010

Finish

Aug 15, 2010


10/50

System Analysis

Software requirements analysis is a process of discovery, refinement, modeling, and

specification. Requirement analysis proves the software designer with a representation of

information, function, and behavior that can be translated to data, architectural interface,

and component -level designs. To perform the job properly we need to follow as set of

underlying concepts and principles of Analysis.

5.1 Analysis Principles

Over the past two decades, a large number of analysis modeling methods have been

developed. Investigators have identified analysis problems and their caused and have

developed a variety of modeling notations and corresponding sets of heuristics to

overcome them. Each analysis method has a unique point of view. However, all analysis

methods are related by a set of operational principles:

The information domain of a problem must be represented and understood.

The functions that the software is to perform must be defined.

The behavior of the software (as a consequence of external events) must be

represented.

The models that depict information function and behavior must be partitioned in a

manner that uncovers detail in layered (or hierarchical) fashion.

The analysis process should move from essential information toward

implementation detail.

By applying these principles, we approach the problem systematically. The information

domain is examined so that function may be understood more completely. Models are

used so that the characteristics of function and behavior can be communicated in a

compact fashion. Partitioning is applied to reduce complexity. Essential and

implementation vies of the software are necessary to accommodate the logical constraints

imposed any processing requirements and the physical constraints imposed by other


11/50

system elements.We have tried to takes above said principles to heart so that we could

provide an excellent foundation for design.

5.1.1 The Information DomainAll software applications can be collectively called data processing. Software is built to

process data, to transform data from one form to another; that is, to accept input,

manipulate it in some way, and produce output. This fundamental statement of objective

is true whether we build batch software for a payroll system or real-time embedded

software to control fuel flow to an automobile engine.

The first operational analysis principle requires an examination of the information domain

and the creation of a data model. The information domain contains three different views

of the data and control as each is processed by a computer program:

information contend and relationships (the data model)

information flow, and

Information structure.

To fully understand the information domain, each of these views should be considered.

Information content represents the individual data and control objects that constitute some

larger collection of information transformed by the software. For example, the data

object, Status declare is a composite of a number of important pieces of data: the

aircrafts name, the aircrafts model, ground run, no of hour flying and so forth.

Therefore, the content ofStatus declares is defined by the attributes that are needed to

create it. Similarly, the content of a control object called System status might be defined

by a string of bits. Each bit represents a separate item of information that indicates

whether or not a particular device is on-or off-line.

Data and control objects can be related to other data and control objects. For example, the

date object Status declare has one or more relationships with the objects like total no of

flying, period left for the maintenance of aircraft an others.

Information flow represents the manner in which date and control change as each moves

through a system. Referring to figure 6.1, input objects are transformed to intermediate


12/50

information (data and / or control), which is further transformed to output. Along this

transformation path, additional information may be introduced from an existing date store

( e.g., a disk file or memory buffer). The transformations applied to the date are functions

or sub functions that a program must perform. Data and control that move between two

transformations define the interface for each function.

Figure 5.1 Information flow and transformation.

5.1.2 Modeling

The second and third operational analysis principles require that we build models of

function and behavior.

Functional models. Software transforms information, and in order to accomplish this, it

must perform at lease three generic functions:

Input

Processing

And output.

The functional model begins with a single context level model (i.e., the name of the

software to be built). Over a series of iterations, more and more functional detail is

gathered, until a through delineation of all system functionality is represented.

Behavioral models. Most software responds to events from the outside world. This

stimulus/response characteristic forms the basis of the behavioral model. A computer

program always exists in some state- an externally observable mode of behavior (e.g.,

Transfor

m

#1

Transfo

rm

#2

Data/Contro

l

Store

Input

Objects

Intermediate

data and

control

Output

Object(s)


13/50

waiting, computing, printing, and polling) that is changed only when some even occurs.

For example, in our case the project will remain in the wait state until:

We click OK command button when first window appears

An external event like mouse click cause an interrupt and consequently main

window appears by asking the username and password.

This external system (providing password and username) signals the project to act

in desired manner as per need.

A behavioral model creates a representation of the states of the software and the events

that cause software to change state.

5.1.2 Partitioning (Divide)

Problems are often too large and complex to be understood as a whole, for this reason, se

tend to partition (divide) such problems into parts that can be easily under stood and

establish interfaces between the part so that overall function can be accomplished. The

fourth operational analysis principle suggests that the information, functional, and

behavioral domains of software can be partitioned.

In essence, partitioning decomposes problem intoits constituent parts. Conceptually, we

establish a hierarchical representation of function or information and then partition and

uppermost element by

exposing increasing detail by moving vertically in the hierarchy or

Functionally decomposing the problem my moving horizontally in the hierarchy.

To issulstate these partitioning approaches let us consider our project

Bus Route SystemBus Route System.. Horizontal partitioning and vertical partitioning of Bus RouteBus Route

systemsystem is shown below.


14/50

Horizontal partitioning:

Bus Route SystemBus Route System

System configuration Password acceptance Interact with user

During installation, the software (Bus Route System) used to program and configure thesystem. A master password is programmed for getting in to the software system. After

this step only user can work in the environments (right cornor naming operation,

administration and maintenance) only.

Vertical partitioning ofBus Route SystemBus Route System function

Bus Route SystemBus Route System

Configure system Username and Password

Acceptance Rejection

Interact with user Fail Retry


15/50

Chapter-6

Operating Environment

6.1 Hardware Specification

Server Side

Core 2 Due 2.4GHz and Above

2 GB of Random Access Memory and Above

160 GB Hard Disk

Client Side

Pentium-IV 1.5MHs and Above

512 MB of Random Access Memory and Above

80 GB Hard Disk

Software Specification

Environment . NET Framework 3.5

Technologies ASP.NET, C#

Database MY SQL5

Software: Visual Studio 2008

OS: Windows server 2003 R2, Windows XP SP2,Windows7

Browser: IE7, IE8, FF 3.5

6.2.1 Front-end Environment (.NET Framework)


16/50

The Internet revolution of the late 1990s represented a dramatic shift in the way

individuals and organizations communicate with each other. Traditional applications,

such as word processors and accounting packages, are modeled as stand-alone

applications: they offer users the capability to perform tasks using data stored on the

system the application resides and executes on. Most new software, in contrast, is

modeled based on a distributed computing model where applications collaborate to

provide services and expose functionality to each other. As a result, the primary role of

most new software is changing into supporting information exchange (through Web

servers and browsers), collaboration (through e-mail and instant messaging), and

individual expression (through Web logs, also known as Blogs, and e-zines Web based

magazines). Essentially, the basic role of software is changing from providing discrete

functionality to providing services.

The .NET Framework represents a unified, object-oriented set of services and libraries

that embrace the changing role of new network-centric and network-aware software. In

fact, the .NET Framework is the first platform designed from the ground up with the

Internet in mind.

Microsoft .NET Framework is a software component that is a part of several Microsoft

Windows operating systems. It has a large library of pre-coded solutions to common

programming problems and manages the execution of programs written specifically for

the framework. The .NET Framework is a key Microsoft offering and is intended to be

used by most new applications created for the Windows platform.

Benefits of the .NET Framework

The .NET Framework offers a number of benefits to developers:

A consistent programming model

Direct support for security

Simplified development efforts

Easy application deployment and maintenance

The .NET Class Library is a key component of the .NET Framework it is sometimes

referred to as the Base Class Library (BCL). The .NET Class Library contains hundreds

of classes you can use for tasks such as the following:
http://en.wikipedia.org/wiki/Software_componentryhttp://en.wikipedia.org/wiki/Software_componentryhttp://en.wikipedia.org/wiki/Microsoft_Windowshttp://en.wikipedia.org/wiki/Microsoft_Windowshttp://en.wikipedia.org/wiki/Operating_systemhttp://en.wikipedia.org/wiki/Library_(computing)http://en.wikipedia.org/wiki/Frameworkhttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Microsoft_Windowshttp://en.wikipedia.org/wiki/Microsoft_Windowshttp://en.wikipedia.org/wiki/Operating_systemhttp://en.wikipedia.org/wiki/Library_(computing)http://en.wikipedia.org/wiki/Frameworkhttp://en.wikipedia.org/wiki/Microsofthttp://en.wikipedia.org/wiki/Software_componentry


17/50

Processing XML

Working with data from multiple data sources

Debugging your code and working with event logs

Working with data streams and files

Managing the run-time environment

Developing Web services, components, and standard Windows applications

Working with application security

Working with directory services

The functionality that the .NET Class Library provides is available to all .NET languages,

resulting in a consistent object model regardless of the programming language

developers use.

Elements of the .NET Framework

The .NET Framework consists of three key elements as show in below diagram


18/50

Components of the .NET Framework

Common Language Runtime

.NET Class Library

Unifying components

Common Language Runtime

The Common Language Runtime (CLR) is a layer between an application and the

operating system it executes on. The CLR simplifies an application's design and reduces

the amount of code developers need to write because it provides a variety of execution

services that include memory management, thread management, component lifetimemanagement, and default error handling.

VB.NET VC#.NET VC++.NET JSCRIPT.NET

ASP.NETWeb Server Web Form Window Forms

.NET Class LibrarySystem Data I/O Security

Common Language RuntimeCommon Type System

Operating System

Visual

Studio.NET


19/50

The CLR is also responsible for compiling code just before it executes. Instead of

producing a binary representation of your code, as traditional compilers do, .NET

compilers produce a representation of your code in a language common to the .NET

Framework: Microsoft Intermediate Language, often referred to as IL. When your code

executes for the first time, the CLR invokes a special compiler called a Just In Time (JIT)

compiler, Because all .NET languages have the same compiled representation, they all

have similar performance characteristics. This means that a program written in Visual

Basic .NET can perform as well as the same program written in Visual C++ .NET.

.NET Class Library

The .NET Class Library containing hundreds of classes that model the system and

services it provides. To make the .NET Class Library easier to work with and understand,

it's divided into namespaces. The root namespace of the .NET Class Library is called

System, and it contains core classes and data types, such as Int32, Object, Array, and

Console. Secondary namespaces reside within the System namespace.

Chapter 7

System Design

E-R Diagram

BUSES

Work

area

Give

service

s Divide

d

BUS ROUTE SYSTEM


20/50

The following DFD shows how the working of a route system could be smoothly

managed:

Works

Care

of

SLEEPER

OR

WITHOUT

SLEEPER

DEPARTMENT

Full

of

DIFFERENT

TYPE OFBUSES

SEATS

examin

e

WORK AREAS

DEPTT WITH ITS

BUSESAGENT

BUSES

RECORDS

DAILY

ENTRY REC

RESERVED

AGENT

VISITING

AGENT

AGENTDETAILS

REPORT

TABLE


21/50

DETAIL DESCRIPTION OF DATA FLOW DIAGRAM:

We have STARBUS as our database and some of our tables (relation) are such as

AGENT_BASIC_INFO, FEEDBACK, PASSANGER_INFO, STATIS and TIMELIST

STARBUS

In our table AGENT_BASIC_INFO we have following field such as agent_id,

agent_name, agent_name, agent_fname, agent_shop_name, agent_shop_address,

agent_shop_city, agent_phon_number etc.

AGENT_BASIC_INFO

AGENTBASICINFO

FEEDBACK

PASSANGERIFNO

STATIS

TIMELIST

AGENT_ID

AGENT_NAME

AGENT_FNAME

AGENT_SHOP_NAME

AGENT_SHOP_ADDRESS

AGENT_SHOP_CITY

AGENT_PHON_NUMBER

AGENT_MOBIL_NUMBER

AGENT_CURRENT_BAL


22/50

In our FEEDBACK table we have fields like name, Email, Phon, Subject, Comment, and

User_type.

FEEDBACK

Name

Email

Comment

User_typ

e

Phone

Subject


23/50

In our table PASSANGER_INFO we have filed like bill_no, c_name, c_phone, c_to,c_from, c_time, Ttalseat, Seatnumber, Amount, Agent_id and Status.

PASSANGER

_INFO

Bill_no

C_name

AmountSeat_no

C_to

C_time

C_phon

C_from

Total_seat

Status

Agent_id


24/50

In the table of TIME_LIST we have fields such as Sno, Satation_name, Rate_per_seat,

Time, Reach_time and Bus_number.

TIME_LIST

Sno

Station_nam

e

Bus_numbe

r

Reach_time

Rate_perSeat

Time


25/50

PROCESS LOGIC::

As the privatization of buses is increasing thus the need of its smooth management isalso increasing the more we could facilitate the customers, the more they are

comfortable with us, the more customers we have visiting our route unit .the above

tables and modules facilitates many logics like:

Number of buses in one unit

Number of computers in particular department

Number of users in a department

Which bus has what tour on which day

What are time table for different buses of different department

What are the schedule for buses

Schedule of a particular bus

How many buses are there

Each bus has how many seats

How many seats are occupied

Advance booking for seat

How much money is collected in a particular day

Bills for different customers

Which seat has booked by agent


26/50

Chapter-8

SCREEN SHOTSIndex page

This webpage is the starting page of the Website. It gives the followings:

TollFree number of the other city. Display advantage of the StarBus


27/50

Links for Agent list and seat status.

Links for Feedback, FAQ, Terms and Conditions.

Status

As in the above image the Status webpage is displaying:

Accessed by anyone.

Information about the booking which seat is booked and which is empty.


28/50

Agent name

As in the above image the Agent name webpage is displaying:

Accessed by anyone.

Contains information about name, address and phone number of the agent.


29/50

Feedback

As in the above image Feedback webpage is displaying:

This page is access by any user

Anyone can give feedback related to the site or services.

Links for Terms and Conditions and Policy and Privacy.


30/50

FAQ

As in the above image FAQ webpage is displaying:


Contain information about tour and services of web site.

Such as how many agent office are there and what is the mode of the pament.


31/50

Privacy Policy

As in the above image the Privacy and Policy webpage is displaying:



32/50

This page say that when customer using our services, we required information

about customer his/her name, age, and email so that we can inform them to there

email also.

Terms and Conditions

As in the above image the Terms and Conditions webpage is displaying:

Accessed by anyone.


33/50

Useful for customer

Contain information when to reach the starting point and what should do, in case

when our ticket is lost.

Login page

As in the image Login webpage is displaying:

Accessed by the agent.

Agent entered its user name and password and click on login.

Contain link for Forget Password.

Forget Password Page


34/50

As in the image Forget Password webpage is displaying:

It required user name who forget its password and then click on Next button.

And also provide link for administration and other.

Identity Confirmation.

As in the above image Identify Confirmation for user webpage is displaying:

The Question you have select at the time of registration.

You need to enter the answer for that question.

Change Password


35/50

As in the above image the Change password web page is displaying:

Only accessed by the Agent

Agent can change password by entering the old and new password

Administrator Section

Create Agent

As in the above image the Change password web page is displaying:

Only accessed by the Administrator.


36/50

New agents are added by this page

Required following information

Username

Password

Email

Security Question

Security Answer.

After click on Create user button it will send you on Agent Basic Information

webpage.

Agent Basic Information page

As in the above image the agents Basic information web page is displaying:

Agents Basic Information are added by this page

Required following information are :-


37/50

Name

Fathers Name

Shop NameShop City

Shop phone number

Mobile Number

Deposit amount

Agent List page


38/50

As in the above image the agents List web page is displaying:


Displaying Agent information such as:-

Agent ID

Name

Shop Name

Shop City

Current Balance

Mobile Number

Agent Deposit Amount Page

As in the above image the agents Deposit Amount web page is displaying:


Requires agent name and amount he wants to deposit.


39/50

Search Agent Page


40/50

Bus List


41/50

Feedback List


42/50

Chapter-9

System Testing

System Testing

Once source code has been generated, software must be tested to uncover (and correct) as

many errors as possible before delivery to customer. Our goal is to design a series of test

cases that have a high likelihood of finding errors. To uncover the errors software

techniques are used. These techniques provide systematic guidance for designing test that

Exercise the internal logic of software components, and

Exercise the input and output domains of the program to uncover errors in

program function, behavior and performance.

9.1 Steps. Software is tested from two different perspectives:

Internal program logic is exercised using White box test case design techniques.

Software requirements are exercised using block box test case design techniques.


43/50

In both cases, the intent is to find the maximum number of errors with the minimum

amount of effort and time.

9.2 Strategies

A strategy for software testing must accommodate low-level tests that are necessary to

verify that a small source code segment has been correctly implemented as well as high-

level tests that validate major system functions against customer requirements. A strategy

must provide guidance for the practitioner and a set of milestones for the manager.

Because the steps of the test strategy occur at a time when deadline pressure begins to

rise, progress must be measurable and problems must surface as earl as possible.

Following testing techniques are well known and the same strategy is adopted during this

project testing.

9.2.1 Unit testing: Unit testing focuses verification effort on the smallest unit of software

design- the software component or module. The unit test is white-box oriented. The

module interface is tested to ensure that information properly flows into and of the

program unit under test the local data structure has been examined to ensure that data

stored temporarily maintains its integrity during all steps in an algorithms execution.

Boundary conditions are tested to ensure that the module operated properly at boundaries

established to limit or restrict processing. All independent paths through the control

structure are exercised to ensure that all statements in a module haven executed at least

once.

9.2.2 Integration testing: Integration testing is a systematic technique for constructing

the program structure while at the same time conducting tests to uncover errors associated

with interfacing. The objective of this test is to take unit tested components and build a

program structure that has been dictated by design.

9.2.3 Validation testing: At the culmination of integration testing, software is completely

assembled as a package, interfacing errors have been uncovered and corrected, and a final

series of software testsvalidation testing-may begin. Validation can be defined in many

ways, but a simple definition is that validation succeeds when software functions in a

manner that can be reasonably expected by the customer.


44/50

9.2.4 System testing: System testing is actually a series of different tests whose primary

purpose is to fully exercise the computer-based system. Below we have described the two

types of testing which have been taken for this project.

9.2.4.1 Security testing

Any computer-based system that manages sensitive information causes actions that can

improperly harm (or benefit) individuals is a target for improper or illegal penetration.

Penetration spans a broad range of activities: hackers who attempt to penetrate system for

sport; disgruntled employees who attempt to penetrate for revenge; dishonest individuals

who attempt to penetrate for illicit personal gain.

For security purposes, when anyone who is not authorized user cannot penetrate this

system. When programs first load it check for correct username and password. If any fails

to act according will be simply ignored by the system.

9.2.4.2 Performance Testing

Performance testing is designed to test the run-time performance of software within the

context of an integrated system. Performance testing occurs throughout all steps in thetesting process. Even at the unit level, the performance of an individual module may be

assessed as white-box tests are conducted.

9.3. Criteria for Completion of Testing

Every time the customer/user executes a compute program, the program is being tested.

This sobering fact underlines the importance of other software quality assurance

activities.

As much time we run our project that is still sort of testing as Musa and Ackerman said.

They have suggested a response that is based on statistical criteria: No, we cannot be

absolutely certain that the software will never fail, but relative to a theoretically sound

and experimentally validated statistical model, we have done sufficient testing to say with

95 percent confidence that the probability of 1000 CPU hours of failure free operation in

a probabilistically defined environment is at least 0.995.


45/50

9.4 Validation Checks

Software testing is one element of broader topic that is often referred to as verification

and validation. Verification refers to the set of activities that ensure that software

correctly implements a specific function. Validation refers to a different set of activities

that ensure that the software that has been built is traceable to customer requirements.

Boehm state this another way:

Verification: Are we building the product right?

Validation: Are we building the right product?

Validation checks are useful when we specify the nature of data input. Let us elaborate

what I mean. In this project while entering the data to many text box you will find the use

of validation checks. When you try to input wrong data. Your entry will be automatically

abandoned.

In the very beginning of the project when user wishes to enter into the project, he has to

supply the password. This password is validated to certain string, till user wont supply

correct word of string for password he cannot succeed. When you try to edit the record

for the trainee in Operation division you will find the validation checks. If you supply the

number (digits) for name text box, you wont get the entry; similarly if you data for

trainee code in text (string) format it will be simply abandoned.

A validation check facilitates us to work in a greater way. It become necessary for certain

Applications like this.


46/50

Chapter 10

System Implementation

Specification, regardless of the mode through which we accomplish it, may be viewed as

a representation process. Requirements are represented in manner that ultimately leads to

successful software implementation.

10.1 Specification principles

A number of specification principles, adapted from the work of balzer and Goodman can

be proposed:

Separate functionality from implementation.

Develop a model of the desired behavior of a system that encompasses date and

the functional responses of a system to various stimuli from the environment.


47/50

Establish the context in which software operates by specifying the manner in

which other system components interact with software.

Define the environment in which the system operates.

Create a cognitive model rather than a design or implementation model. The

cognitive model describes a system as perceived by its user community.

Recognize that the specifications must be tolerant of incompleteness and

augmentable.

Establish the content and structure of a specification in a way that will enable it to

be amenable to change.

This list of basic specification principles provides a basis for representing software

requirements. However, principles must be translated into realization.

10.1.2 Representation

As we know software requirement may be specified in a variety of ways. However, if

requirements are committed to paper a simple set of guidelines is well worth following:

Representation format and content should be relevant to the problem.

A general outline for the contents of a Software Requirements Specification can be

developed. However, the representation forms contained within the specification are

likely to vary with the application area. For example, for our automation system we used

different symbology, diagrams.

Information contained within the specification should be nested.Representations should reveal layers of information so that a reader can move to the level

of detail required. Paragraph and diagram numbering schemes should indicate the level of

detail that is being presented. It is sometimes worthwhile to present the same information

at different levels of abstraction to aid in understanding. Similar guidelines are adhered

for my project.


48/50

Chapter 11

Conclusion

To conclude, Project Grid works like a component which can access all the databases and

picks up different functions. It overcomes the many limitations incorporated in the .NET

Framework. Among the many features availed by the project, the main among them are:

Simple editing

Insertion of individual images on each cell

Insertion of individual colors on each cell

Flicker free scrolling

Drop-down grid effect

Placing of any type of control anywhere in the grid


49/50

Chapter12

Scope of the Project

Future scope of the project

The project has a very vast scope in future. The project can be implemented on internet in

future. Project can be updated in near future as and when requirement for the same arises,

as it is very flexible in terms of expansion. With the proposed software of Web Space

Manager ready and fully functional the client is now able to manage and hence run the

entire work in a much better, accurate and error free manner. The following are the future

scope for the project: -

The number of levels that the software is handling can be made unlimited in future

from the current status of handling up to N levels as currently laid down by the

software. Efficiency can be further enhanced and boosted up to a great extent by

normalizing and de-normalizing the database tables used in the project as well as

taking the kind of the alternative set of data structures and advanced calculation

algorithms available.


50/50

We can in future generalize the application from its current customized status

wherein other vendors developing and working on similar applications can utilize

this software and make changes to it according to their business needs.

Faster processing of information as compared to the current system with high

accuracy and reliability.

Automatic and error free report generation as per the specified format with ease.

Automatic calculation and generation of correct and precise Bills thus reducing

much of the workload on the accounting staff and the errors arising due to manual

calculations.

With a fully automated solution, lesser staff, better space utilization and peaceful

work environment, the company is bound to experience high turnover.

A future application of this system lies in the fact that the proposed system would remain

relevant in the future. In case there be any additions or deletion of the services, addition

or deletion of any reseller in any type of modification in future can be implemented

easily. The data collected by the system will be useful for some other purposes also

References

Complete Reference of C#

Programming in C# - Deitel & Deitel

www.w3schools.com

http://en.wikipedia.org

The principles of Software Engineering Roger S.Pressman

Software Engineering Hudson

MSDN help provided by Microsoft .NET

Object Oriented Programming Deitel & Deitel
http://www.w3schools.com/http://en.wikipedia.org/http://www.w3schools.com/http://en.wikipedia.org/

bus route system

Documents