Bus Reservation System Final Report

CHAPTER 1

INTRODUCTION

1.1

MOTIV TIVATION TION AND AND OBJ OBJEC ECT TIVE IVE

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 and also provide following features:

1



Online Bus Ticket Booking Facility and ancellation Facility.



!nhance of the security level in centrali"ed system.



#egister $ew %gent.



&iew 'etails of %gent, Bus (nformation, )ser Feedback



'ifferent *ayment +ode: ash ard, redit ard !tc.

!-ealthare

CHAPTER 2

PROBLEM DEFINITION AND REQUIREMENT ANALYSIS ANALYSIS

2.1 IDENTIFICATION OF NEED

The main objective of this project is to provide the better work efficiency, efficiency, security, accuracy, accuracy, reliability, feasibility. The error occurred could be reduced to nil and working conditions can be improved and also provide following features: 

Online Bus Ticket Booking Facility and a nd ancellation Facility.



!nhance of the security level in centrali"ed system.



#egister $ew %gent.



&iew 'etails of %gent, Bus (nformation, )ser Feedback



Diferent Payment Mode: Cash Card, Credit Card Etc.

2.2 FEASIBILITY STUDY

% feasibii!" s!#$" is an evaluation and analysis of the potential of the proposed project which is based on etensive investigation and research to give full comfort to the decisions makers. Feasibility studies aim to objectively and rationally uncover the strengths and weaknesses of an eisting business or proposed venture, opportunities and threats as presented by the environment, the environment, the resources re/uired to carry through, and ultimately the prospects for success. (n its simplest terms, the two criteria to judge feasibility are cost re/uired cost re/uired and value to be attained. %s such, a welldesigned feasibility study should provide a historical background of the business or project, description of the product the product or or service, service, accounting statements, details of the operations and operations and management, marketing research and research and policies, financial data, legal re/uirements and ta obligations. 0enerally, feasibility studies precede technical development and project and project implementation. implementation.

2

Bus #eservation 1ystem

2.2.1 TECHNOLO%Y AND SYSTEM FEASIBILITY FEASIBILITY

The assessment is based on an outline design of system re/uirements, to determine whether the company has the technical epertise to handle completion of the project. 2hen writing a feasibility report, the following should be taken to consideration: 

% brief description of the business to assess more possible factor3s which could affect the study



The part of the business being eamined



The human and economic factor



The possible solutions to the problems

%t this level, the concern is whether the proposal is both technicall y and legally feasible 4assuming moderate cost5.

2.2.2 OPERATIONAL FEASIBILITY

Operational feasibility is a measure of how well a proposed system solves the problems, and takes advantage of the opportunities identified during scope definition and how it satisfies the re/uirements identified in the re/uirements analysis phase of system development. The operational feasibility assessment focuses on the degree to which the proposed development projects fits in with the eisting business environment and objectives with regard to development schedule, delivery date, corporate culture, and eisting business processes.

3


2.2.& ECONOMIC FEASIBILITY

The purpose of the economic feasibility assessment is to determine the positive economic benefits to the organi"ation that the proposed system will provide. provide. (t includes /uantification and identification of all the benefits epected. This assessment typically involves a cost3 benefits analysis.

2.2.' TECHNICAL FEASIBILITY

The technical feasibility assessment is focused on gaining an understanding of the present technical resources of the organi"ation and their applicability to the epected needs of the proposed system. (t is an evaluation of the hardware and software and how it meets the need of the proposed system .

2.2.( FINANCIAL FEASIBILITY

(n case of a new project, financial viability can be judged on the following parameters: 

Total estimated cost of the project.



Financing of the project in terms of its capital structure, debt e/uity ratio and promoter6s share of total cost.



!isting investment by the promoter in any other business



*rojected cash flow and profitability. profitability.

The financial viability of a project should provide the following information.

4




Full details of the assets to be financed and how li/uid those assets are.



#ate of conversion to cashli/uidity 4i.e. how easily can the various assets be converted to cash75.



*roject6s funding potential and repayment terms.



1ensitivity in the repayments capability to the following factors:

5

o

Time delays.

o

+ild slowing of sales.

o

%cute reduction3slowing of sales.

o

1mall increase in cost.

o

8arge increase in cost.

o

%dverse economic conditions.


2.& PROJECT PLANNIN%

The concept is further developed to describe how the business will operate once the approved system is implemented, and to assess how the system will impact the administrator and user privacy. To ensure the products and 3or services provide the re/uired capability on time and within budget, project resources, activities, schedules, tools, and reviews are defined. %dditionally, security certification and accreditation activities begin with the identification of system security re/uirements and the completion of a high level vulnerability assessment.

PROJECT MANA%EMENT ACTIVITIES

PROJECT PLANNIN% 

!stablishing objectives.



'efining project.



reating work breakdown 1tructure.



'etermining resources

These task defining following .

PROJECT OR%ANI)ATION *OR+S BEST *HEN

6




2orks can be defined with a specific goal deadlines



The job is uni/ue and somewhat unfamiliar to the eisting organi"ation.



The work contains comple interrelated tasks re/uiring speciali"ed skills.



The project is temporary but critical to organi"ation.



Often temporary structure.



)ses specialist from entire company .



-eaded by project manager



+onitor schedule 9 costs.



*ermanent structure called matri organi"ation;.

*OR+ BREA+DO*N STRUCTURE 

7

project



+ajor tasks in project.



1ubtasks in major tasks.



%ctivities.


2.'

DATA FLO* DIA%RAM ,DFD-

The 'ata Flow 'iagram 4'F'5 is the graphical representation of the processes and the flow of data among them. % data flow diagram illustrates the processes, data stores, eternal entities and the connecting data flows in a system. The following figure is an eample of a typical 'F'.

Figure: <.= !ample of a 'ata Flow diagram There are four components for a 'ata Flow 'iagram. They are

 E!e/0a E0!i!ies Te/i0a!3/s are outside of the system being modeled.

They represent where information comes from and where it goes. These are represented by /e4!a05es .

8


 P/34esses , usually represented by an ei6se 4circle5, which modify the

(nput to generate the output.  Da!a S!3/es represents a place in the process where data rests. This is

represented by an 36e07e0$e$ /e4!a05es 3/ a 4"i0$e/ symbol.  Da!a F38s, represented by a//38s, are how data moves between

Terminators, processes, and data stores.




DATA FLO* DIA%RAM ,DFD!o"in into

Passenger

Book

Ticket

Bus Reservaon System

Ticket etails

Bus

Agency/ Online Store in

Verify passenger

Report Information

Report Customer A\C Passenger

Information

Information Table

Passenger

can submit feed

back Feedback Table

1#


2.( ENTITY RELATIONSHIP DIA%RAM

%n !ntity #elationship 'iagram 4!#'5 gives a graphical representation of the tables 4entities5 in the database and the relation between them.  !ntity  %n aggregation of a number of data elements.  !ach data element is an attribute of the entity.  !ntity type  a class of entities with the same attributes  #elationship  %n association between two or more entities that is of particular interest.

ERD De9e36e0! P/34ess:

 (dentify the entities  'etermine the attributes for each entity  1elect the primary key for each entity  !stablish the relationships between the entities  'raw an entity model

Test the relationships and the keys

11


ER MODEL FEATURES TO DESCRIBE DATA

*hysical !ntity 1et

%ttributes

1peciali"ation

0enerali"ation

#elationship

1ingle 8ine

onnection Between !ntity and #elationship

#elationship

12


2.; USE CASE DIA%RAM

% #se 4ase $ia5/a at its simplest is a representation of a user6s interaction with the system and depicting the specifications of a use case. % use case diagram can portray the different types of users of a system and the various ways that they interact with the system. This type of diagram is typically used in conjunction with the tetual use case and will often be accompanied by other types of diagrams as well.

2.;.1 USE CASE FOR PASSAN%ER

Find 1ite or agency for ticket booking

*%11%$0! #

%pply for the ticket

%utomatic search will define that ticket is available or not +ap

Final *rint of Ticket onfirmation

13


2.;.2 USE CASE FOR A%ENT

Take inputs from customer

%0!$T heck the ticket mode

(f ticket is not booked he book a new ticket or he can also cancel booked ticket

Forward a message to customer;s mob no.

14


2.< FLO* DIA%RAM

Flow 'iagram for bus reservation system

15


&. PLATFORMTECHNOLO%Y IN PROJECT

&.1 F/30!7e0$ E09i/30e0! ,.NET F/ae83/=-

The (nternet revolution of the late =>>?s represented a dramatic shift in the way individuals and organi"ations 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 eecutes on. +ost new software, in contrast, is modeled based on a distributed computing model where applications collaborate to provide services and epose functionality to each other. %s a result, primary role of most new software is changing into supporting information echange 4through 2eb servers and browsers5, collaboration 4through email and instant messaging5, and individual epression 4through 2eb logs, also known as Blogs, and e"ines @ 2eb based maga"ines5. !ssentially, the basic role of software is changing from providing discrete functionality to providing services.

The .$!T Framework represents a unified, objectoriented set of services and libraries that embrace the changing role of new networkcentric and networkaware software. (n fact, the .$!T Framework is the first platform designed from the ground up with the (nternet in mind.

+icrosoft .$!T Framework is a software component that is a part of several +icrosoft 2indows operating systems. (t has a large library of precoded solutions to common programming problems and manages the eecution of programs written specifically for the framework. The .$!T Framework is a key +icrosoft offering and is intended to be used by most new applications created for the 2indows platform.

16


Be0efi!s 3f !>e .NET F/ae83/=

    

The .$!T Framework offers a number of benefits to developers: % consistent programming model 'irect support for security 1implified development efforts !asy application deployment and maintenance

The .$!T lass 8ibrary is a key component of the .$!T Framework @ it is sometimes referred to as the Base lass 8ibrary 4B85. The .$!T lass 8ibrary contains hundreds of classes you can use for tasks such as the following:

       

*rocessing A+8 2orking with data from multiple data sources 'ebugging your code and working with event logs 2orking with data streams and files +anaging the runtime environment 'eveloping 2eb services, components, and standard 2indows applications 2orking with application security 2orking with directory services

The functionality that the .$!T lass 8ibrary provides is available to all .$!T languages, resulting in a consistent object model regardless of the programming language developer;s use.

Pe/f3/a04e

%1*.$!T aims for performance benefits over other scriptbased technologies 4including lassic %1*5 by compiling the serverside code to one or more '88 files on the web server. This compilation happens automatically the first time a page is re/uested 4which means the developer need not perform a separate compilation step for pages5. This feature provides the ease of development offered by scripting languages with the performance benefits of a compiled binary.

17


-owever, the compilation might cause a noticeable but short delay to the web user when the newlyedited page is first re/uested from the web server, but won6t again unless the page re/uested is updated further. The %1*A and other resource files are placed in a virtual host on an (nternet (nformation 1ervices server 4or other compatible %1*.$!T servers see Other (mplementations, below5. The first time a client re/uests a page, the .$!T framework parses and compiles the file4s5 into a .$!T assembly and sends the response subse/uent re/uests are served from the '88 files. By default %1*.$!T will compile the entire site in batches of =??? files upon first re/uest. (f the compilation delay is causing problems, the batch si"e or the compilation strategy may be tweaked. 'evelopers can also choose to precompile their code before deployment, eliminating the need for justintime compilation in a production environment

&.2 Ba4=7e0$ E09i/30e0! ,Ms A44essMi4/3s3f! A44ess , also known as Mi4/3s3f! Offi4e A44ess , is a database management system from +icrosoft that combines the relational +icrosoft Cet 'atabase !ngine with a graphical user interface and softwaredevelopment tools. (t is a member of the +icrosoft Office suite of applications, included in the *rofessional and higher editions or sold separately.

+icrosoft %ccess stores data in its own format based on the %ccess Cet 'atabase !ngine. (t can also import or link directly to data stored in other applications and databases. D=E 1oftware developers and data architects can use +icrosoft %ccess to develop application software, and  power users can use it to build software applications. 8ike other Office applications, %ccess is supported by &isual Basic for %pplications, an object oriented programming language that can reference a variety of objects including '%O 4'ata %ccess Objects5, %ctiveA 'ata Objects, and many other %ctiveA components. &isual objects used in forms and reports epose their methods and properties in the &B% programming environment, and &B% code modules may declare and call 2indows operating system functions.

18


Fea!#/es )sers can create tables, /ueries, forms and reports, and connect them together with macros. %dvanced users can use &B% to write rich solutions with advanced data manipulation and user control. %ccess also has report creation features that can work with any data source that %ccess can access. The original concept of %ccess was for end users to be able to access data from any source. Other features include: the import and eport of data to many formats including !cel, Outlook , %1((, dBase, *arado, Fo*ro, 1G8 1erver , Oracle, O'B, etc. (t also has the ability to link to data in its eisting location and use it for viewing, /uerying, editing, and reporting. This allows the eisting data to change while ensuring that %ccess uses the latest data. (t can perform heterogeneous joins between data sets stored across different platforms. %ccess is often used by people downloading data from enterprise level databases for manipulation, analysis, and reporting locally. There is also the Cet 'atabase format 4+'B or %'B in %ccess
1


&.& I0!e/0e! I0f3/a!i30 Se/9e/ ,IIS-

I0!e/0e! I0f3/a!i30 Se/9i4es 4IIS5 L formerly called I0!e/0e! I0f3/a!i30 Se/9e/ L is a web server software application and set of feature etension modules created by +icrosoft for use with +icrosoft 2indows.D
%ll versions of ((1 prior to H.? running on client operating systems supported only =? simultaneous connections and a single web site.

FEATURES

((1 I.? and higher support the following authentication mechanisms:



$nonymo%s a%then&ca&on 'asic access a%then&ca&on



Di"est access a%then&ca&on



(nte"rated )indo*s $%then&ca&on



+C a%then&ca&on



.E- Passort $%then&ca&on /0emoed in )indo*s erer 2##8 and (( 7.#



Cer&cate a%then&ca&on



((1 H.? has a modular architecture. +odules, also called etensions, can be added or removed individually so that only modules re/uired for specific functionality have to be installed. ((1 H includes native modules as part of the full installation. These modules are individual features that the server uses to process re/uests and include the following:



ec%rity mod%es  +sed to erorm many tass reated to sec%rity in the re9%est rocessin" ieine, s%ch as seciyin" a%then&ca&on schemes, erormin" +0! a%thori;a&on, and terin" re9%ests.

2#










Content mod%es  +sed to erorm tass reated to content in the re9%est rocessin" ieine, s%ch as rocessin" re9%ests or sta&c es, ret%rnin" a dea%t a"e *hen a cient does not seciy a reso%rce in a re9%est, and is&n" the contents o a directory. Comression mod%es  +sed to erorm tass reated to comression in the re9%estrocessin" ieine, s%ch as comressin" resonses, ayin" <;i comression transer codin" to resonses, and erormin" recomression o sta&c content. Cachin" mod%es  +sed to erorm tass reated to cachin" in the re9%est rocessin" ieine, s%ch as storin" rocessed inorma&on in memory on the serer and %sin" cached content in s%=se9%ent re9%ests or the same reso%rce. !o""in" and Dia"nos&cs mod%es  +sed to erorm tass reated to o""in" and dia"nos&cs in the re9%estrocessin" ieine, s%ch as assin" inorma&on and rocessin" stat%s to >--P. sys or o""in", reor&n" eents, and tracin" re9%ests c%rrenty e?ec%&n" in *orer rocesses.

((1 H.J includes the following additional or enhanced security features:



Cient cer&cate main" (P sec%rity



0e9%est terin"



+0! a%thori;a&on



%uthentication changed slightly between ((1 I.? and ((1 H, most notably in that the anonymous user which was named ()1#NmachinenameP is a builtin account in &ista and future operating systems and named ()1#. $otably, in ((1 H, each authentication mechanism is isolated into its own module and can be installed or uninstalled.

SECURITY

!arlier versions of ((1 were hit with a number of vulnerabilities, especially the %
21


there be a vulnerability in a feature or in custom code it won6t necessarily compromise the entire system given the sandboed environment these worker processes run in. ((1 I.? also contained a new kernel -TT* stack 4 http.sys5 with a stricter -TT* re/uest parser and response cache for both static and dynamic content. %ccording to 1ecunia, as of Cune S of the world6s malware, the same as %pache servers whose market share was IIS. The study also observed the geographical location of these dirty servers and suggested that the cause of this could be the use of pirated copies of 2indows that could not obtain security updates from +icrosoft. +icrosoft has corrected this situation +icrosoft now supplies security updates even to pirated copies of 2indows.

22


CHAPTER '

SYSTEM DESI%N

S"s!es $esi50 is the process of defining the architecture, components,

modules, interfaces, and data for a system to satisfy specified re/uirements. 1ystems design could see it as the application of systems theory to product development. There is some overlap

with

the

disciplines

of systems

analysis, systems

architecture and systems

engineering.

L35i4a $esi50

The logical design of a system pertains to an abstract representation of the data flows, inputs and outputs of the system. This is often conducted via modeling, using an overabstract 4and sometimes graphical5 model of the actual system. (n the contet of systems design are included. 8ogical design includes !# 'iagrams i.e. !ntity #elationship 'iagrams.

P>"si4a $esi50

The physical design relates to the actual input and output processes of the system. This is laid down in terms of how data is input into a system, how it is verified3authenticated, how it is processed, and how it is displayed as output. (n *hysical design, following re/uirements about the system are decided. =. (nput re/uirement,

23


<. Output re/uirements, Q. 1torage re/uirements, M. *rocessing #e/uirements, J. 1ystem control and backup or recovery. *ut another way, the physical portion of systems des ign can generally be broken down into three subtasks: =. )ser (nterface 'esign <. 'ata 'esign Q. *rocess 'esign

)ser (nterface 'esign is concerned with how users add information to the system and with how the system presents information back to them. 'ata 'esign is concerned with how the data is represented and stored within the system. Finally, *rocess 'esign is concerned with how data moves through the system, and with how and where it is validated, secured and3or transformed as it flows into, through and out of the system. %t the end of the systems design phase, documentation describing the three subtasks is produced and made available for use in the net phase.

*hysical design, in this contet, does not refer to the tangible physical design of an information system. To use an analogy, a personal computer6s physical design involves input via a keyboard, processing within the *), and output via a monitor, printer, etc. (t would not concern the actual layout of the tangible hardware, which for a * would be a monitor, *), motherboard, hard drive, modems, video3graphics cards, )1B slots, etc. (t involves a detailed design of a user and a product database structure processor and a control processor. The -31 personal specification is developed for the proposed system.

24


'.1 MODULARI)ATION DETAILS

      

Ticket Booking +odule Ticket ancellation +odule heck Ticket 1tatus 1earch Bus between Two status 1end feedback 'isplay various reports like bus details, all passenger details %gent registration

$ow we consider each module in brief.

M.=.= T(!T BOO($0 +O')8!

(n this project ticket booking module re/uires following details: =. *erson name <. *$# no Q. 1ource M. 'estination J. %ge %t the first passenger will search for a booking agency or website or an agent then he can be able to book his travel ticket on particular date and time.

25


M.=.< T(!T %$!88%T(O$ +O')8!

This module is for canceling the booked ticket. This module takes following argument as input *$# no (f related ticket is booked then it cancel that ticket and if there is no such ticket is booked then it returns false result.

M.=.Q T(!T 1T%T)1 +O')8!

This module is for checking status of particular ticket whether it is booked or cancelled. %s above module 4Ticket cancellation module5 it also takes one argument: *$# no

M.=.M 1!%#- B)1!1 B!T2!!$ T2O 1T%T(O$1

This module is for searching buses between two desired stations. There are three arguments needed: 1ource 'estination 'ate (t returns a list of buses between those stations on a particular day.

26


M.=.J 1!$' F!!'B% +O')8!

This module enables user to send feedback to related bus agency so that possible flaws can be removed and maimum customer satisfaction can be achieved. )ser post his view with precious suggestions in comment bo.

M.=.I '(1*8%R &%#(O)1 #!*O#T1 8(! B)1 '!T%(81 %$' *%11%$0!# '!T%(81

This module provides information about bus and passenger as well. (f customer wants to know about a particular bus then he has to pass following information: Bus no 'ate %nd if he wants to know about a particular passenger or himself the he has to pass following input: *nr no or name 'ate

M.=.H %0!$T #!0(1T#%T(O$ +O')8!

2hen a new agent is hired, he must be registered before proceeding. %nd there are following inputs are re/uired: )ser name *assword onfirm password

27


1ecurity /uestion 1ecurity answer

'.2. DATABASE DESI%N

DATA STRUCTURES:

This part of the 'esign consists the overall database schema or we can say that tables which consists various types of records. Table of aa database consists attributes, entities, tuples for storing and manipulating records. 1ome of the tables are as follows:

'.2.1 A5e0! Basi4 i0f3/a!i30

%ttribute $ame 1$o %gent(' %gent$ame Father$ame 1hop$ame 1hopity 1hop1tate 1hop*in *hone$umber +obile$umber

'ata type %uto$umber Tet Tet Tet Tet Tet Tet $umber $umber $umber

onstraints *rimary ey $ot null $ot $ull       

This table is used for storing all details about agent of the bus agency.

28


'.2.2 FEEDBAC+ TABLE

%ttribute $ame 1$o $ame !mail *hone no 1ubject omment )ser type

'ata type %uto$umber Tet Tet $umber Tet Tet Tet

onstraints *rimary ey $ot null     $ot $ull

This table is used for storing all information about feedback vi" who posted this comment and his mob no, email etc

*#(+%#R !R :  1$o

'.2.& PASSAN%ER INFORMATION

2


%ttribute $ame *$# N$ame N*hone Nto Nfrom Ndate Ntime Total1eat %mount %gent('

'ata type $umber Tet Tet Tet Tet Tet Tet $umber $umber +emo

onstraints *rimary ey $ot null  

This table is used for 1toring all information about person who is going to tavel.

*#(+%#R !R :  *$#

'.2.' LO%IN INFORMATION

%ttribute $ame )sername *assword

'ata type Tet Tet

onstraints  

This table is used for storing all usernames and passwords.

3#


'.&. USER INTERFACE DESI%N

'.&.1 LO%IN FORM

31


This is 1tarting *age which is show in web browser.

'.&.2 ABOUT US PA%E

32


This page is for information about this software.

'.&.& BOO+ TIC+ET SCREEN PA%E

33


This page is for displaying before the user where he will input all the re/uired aspects.

'.&.' BOO+ TIC+ET SCREEN ,AFTER FILLIN% DETAILS-

34


'.&.( BOO+ED TIC+ET VIE*

35


This page shows preview of booking information.

'.&.; TIC+ET CANCELLATION SCREEN

36


This page is for canceling the booked ticket.

'.&.< CANCELLED TIC+ET VIE* ,AFTER FILLIN% DETAILS-

37


'.&.? CANCELLED TIC+ET VIE*

38


This form shows information regarding cancellation of ticket.

'.&.@ TIC+ET STATUS FORM

3


This form shows status of the ticket whether it is cancelled or still booked.

'.&.1 TIC+ET STATUS SCREEN ,AFTER INSERTIN% NUMBER-

4#


'.&.11 TIC+ET STATUS SCREEN

41


This form shows information about ticket;s mode 4cancelled or booked5.

'.&.12 A%ENT RE%ISTRATION FORM

42


(n this form registration of agent takes place.

'.&.1& A%ENT RE%ISTRATION FORM ,AFTER INSERTIN% DETAILS-

43


'.&.1' AFTER A%ENT RE%ISTRATION CON%RATULATION SCREEN

44


This ongratulation page appears after agent registration being completed.

'.&.1( BUS SEARCH FORM

45


(n this form user can search bus between two stations.

'.&.1; SEARCHED BUS LIST VIE*

46


(n this form result shows after completing searching.

'.&.1< A%ENT SEARCH FORM

47


(n this form agent can be search by name.

'.&.1? ALL SEARCHED A%ENT FORM

48


(n this form all the searched agents show.

'.&.1@ USER FEEDBAC+ SCREEN

4


(n this form user can enter feedback.

'.&.2 ALL USER FEEDBAC+ LIST FORM

5#


8isted feedback is shown in this form.

'.&.21 BUS LIST VIE* FORM

51


8isted buses are shown in this form.

'.&.22 PRIVACY AND POLICY

52


(n this form privacy and policy is shown.

'.&.2& TERMS AND CONDITION FORM

53


(n this form terms and conditions are shown.

'.&.2' FREQUENTLY AS+ED QUESTIONS FORM

54


This is F%G;s form.

'.&.2( CONTACT US FORM

55


This form is for helpdesk.

'.&.2; PHOTO %ALLERY SCREEN FORM

56


This form is for photos of buses.

'.&.2< PHOTO THUMBNAIL VIE* SCREEN

57


This form provides thumbnail view of photos.

CHAPTER (

IMPLEMENTATION AND MAINTENANCE

58


(.1 IMPLEMENTATION

INTRODUCTION

1ystem implementation is the stage when the user has thoroughly tested the system and approves all the features provided by the system. The various tests are performed and the system is approved only after all the re/uirements are met and the user is satisfied. The new system may be totally new, replacing an eisting manual or automated system, or it may be a major modification to an eisting system. (n either case, proper implementation is essential to provide a reliable system to meet organi"ational re/uirements. 1uccessful implementation may not guarantee improvement in the organi"ation using the new system 4that is a design /uestion5, but improper will prevent it. (mplementation is the process of having systems personnel check out and put new e/uipment into use, train users, install the new application and construct any files of data needed to use it. This phase is less creative than system design. 'epending on the si"e of the organi"ation that will be involved in using the application and the risk involved in its use, systems developers may choose to test the operation in only one area of the firm with only one or two persons. 1ometimes, they will run both old and new system in parallel way to compare the results. (n still other situations, system developers stop using the old system one day and start using the new one the net. The implementation of the web based or lan based networked project has some etra steps at the time of implementation. 2e need to configure the system according the re/uirement of the software.

TRAININ%

!ven well designed and technically elegant systems can succeed or fail because of

5


the way they are used. Therefore the /uality of the training received by the personnel involved with the system in various ways helps or hinders, and may even prevent, the successful implementation of an information system. 1ince, -uman #esource #ecruitment *rocess is webbased and user friendly, not much effort was re/uired in training process.

PARALLEL RUN

(n this approach, the old system and the new system are used simultaneously for some period of time so that the performance of the new system can be monitored and compared with that of the old system. %lso in case of failure of the new system, the user can fall back on the old system. The risk of this approach is that the user may never want to shift to new system.

IMMEDIATE CUT7OFF

(n this method, the use of the old system ceases as soon as the new system is implemented and bought in to palace. The old system becomes redundant from the day of implementation of the new system. There is the high risk involved in this approach if the new system is not tested rigorously. This is because of the fact that if the new system fails, then there will not be anything to fall back upon. The advantage of this approach is that both the systems need not be used simultaneously.

I6ee0!a!i30 T33s

6#


The project was implemented using Cava server pages with 1truts apabilities. The implementation work was carried out in 2indows H platform. =5 %1*.$et <5 ((1 server Q5 1G8 server

C3$i05

This means program construction with procedural specifications has finished and the coding for the program begins: 

Once the design phase was over, coding commenced



oding is natural conse/uence of design.



oding step translate a detailed design representation of software into a programming languae reali"ation.



+ain emphasis while coding was on style so that the end result was an optimi"ed code.

The following points were kept into consideration while coding:

C3$i05 S!"e

The structured programming method was used in all the modules the project. (t incorporated the following features



The code has been written so that the definition and implementation of each function is contained in one file.

61




% group of related function was clubbed together in one file to include it when needed and save us from the labors of writing it again and again.

Nai05 C309e0!i30 

%s the project si"e grows, so does the compleity of recogni"ing the purpose of the variables. Thus the variables were given meaningful names,whihch would help in understanding the contet and the purpose of the variable.



The function names are also given meaningful names that can be easily understood by the user.

I0$e0!a!i30

Cudicious use of indentation can make the task of reading and understanding a program much simpler. (ndentation is an essential part of a good program. (f code id intended without thought it will seriously affect the readability of the program. 

The higherlevel statements like he definition of the variables, constants and the function are intended, with each nested block intended, stating their purpose in the code.



Blank line is also left between each function definition to make the code look neat.



(ndentation for each source file stating he purpose of the file is also done.

(.2 MAINTENANCE:

62


+aintenance or enhancement can be classified as:  C3//e4!i9e A$a6!i9e Pe/fe4!i9e.

orrective maintenance means repairing processing or performance failures or making changes because of previously uncorrected problems or false assumptions. %daptive maintenance means changing the program function. *erfective maintenance means enhancing the performance or modifying the program4s5 to respond to the user;s additional or changing needs. +aintenance is actually the implementation of the post implementation review plan. %s important as it is, many programmers and analysts are reluctant to perform or identify themselves with the maintenance effort. There are psychological, personality and professional reasons for this. (n any case, a first class effort must be made to ensure that software changes are made properly and in time to keep the system in tune with user specifications. +aintenance is costly. One way to reduce maintenance costs is through maintenance management and software modification audits. 1oftware modification consists of program rewrites system level updates, and reaudits of low ranking programs to verify and correct the soft spots. The outcome should be more reliable software, a reduced maintenance backlog, and higher satisfaction and morale among the maintenance staff.

CHAPTER ;

63


TESTIN% AND DEPLOYMENT

;.1 SYSTEM TESTIN%:

-ere the 1ystem testing involved is the most widely used testing process consisting of five stages as shown in the figure. (n general, the se/uence of testing activities is component testing, integration testing, and then user testing. -owever, as defects are discovered at any one stage, they re/uire program modifications to correct them and this may re/uire other stages in the testing process to be repeated.

+nit tes&n"

Mod%e tes&n"

%=system tes&n"

ystem tes&n"

$ccetance tes&n"

,C3630e0! !es!i05-

,I0!e5/a!i30 !es!i05-

,Use/ !es!i05 5

Figure H.=

64


Testing is the process of detecting errors. Testing performs a very critical role for /uality assurance and for ensuring the reliability of the software. The results of testing are used later on during maintenance also. Testing is vital to the success of the system. 1ystem testing makes a logical assumption that if the parts of the system are correct, the goal will be successfully achieved. (n ade/uate testing or nontesting leads to errors that may not appear until months or even years later 4#emember the $ew Rork three day power failure due to a misplaced Break; statement5. This creates two problems: =.

The time lag between the cause and the appearance of the problem.

<.

The time interval effect of the system errors on files and the records on the system.

% small error can conceivably eplode into a much larger problem. !ffective testing early in the process translates directly into long term cost savings from a reduced number of errors. %nother reason for system testing is it;s utility as a user oriented vehicle before implementation. The best program is worthless if it does not meet the user re/uirements. )nfortunately, the user;s demands are often compromised by efforts to facilitate program or design efficiency in terms of processing time or design efficiency. Thus in this phase we went to test the code we wrote. 2e needed to know if the code compiled with the design or not7 2hether the code gave the desired outputs on given inputs7 2hether it was ready to be installed on the user;s computer or some more modifications were needed7 Through the web applications are characteristically different from their software counterparts but the basic approach for testing these web applications is /uite similar. These basic steps of testing have been picked from software engineering practices. The following are the steps, we undertook:

65


=. The content of the (ntranet site is reviewed to uncover ontent

!rrors. ontent

!rrors covers the typographical errors, grammatical errors, errors in content consistency, graphical representation and cross referencing errors <. The design model of the web application is reviewed to uncover the navigation errors. )se cases, derived as a part of the analysis activity allows a web designer to eercise each usage scenario against the architectural and navigational design. (n essence these noneecutable tests help to uncover the errors in navigation. Q. 2hen web applications are considered the concept of unit changes. !ach web page encapsulate content navigation links, content and processing elements4Forms, 1cripts, C1*;s as in our case5. (t is not always possible to test each of these individually. Thus is the base of the web applications the unit to be considered is the web page. )nlike the testing of the algorithmic details of a module the data that flows across the module interface, page level testing for web applications is driven by content, processing and links encapsulating the web page. M.

The %ssembled web application

is tested for overall functionality and content

delivery. the various user cases are used that test the system for errors and mistakes.

J. The 2eb application is tested for a variety of environmental settings and is tested for various configurations and upon various platforms. The modules are integrated and integration test are conducted. I. Thread based testing is done to monitor the regression tests so that the site does not become very slow is a lot of users are simultaneously logged on. H. % controlled and monitored population of end users tests (ntranet application, this all comprises of the )ser %cceptance Testing. Because web application evolves continuously, the testing process is an ongoing activity, conducted by web support staff in our case the Organi"ation;s (1 people who will finally update and manage the application.

66


PSYCHOLO%Y OF TESTIN%

The aim of testing is often to demonstrate that a program works by showing that it has no errors. The basic purpose of testing phase is to detect the errors that may be present in the program. -ence one should not start testing with the intent of showing that a program works, but the intent should be to show that a program doesn;t work. Testing is the process of eecuting a program with the intent of finding errors.

TESTIN% OBJECTIVES:

The main objective of testing is to uncover a host of errors, systematically and with minimum effort and time. 1tating formally, we can say, Testing is a process of eecuting a program with the intent of finding an error. % successful test is one that uncovers an as yet undiscovered error. % good test case is one that has a high probability of finding error, if it eists. The tests are inade/uate to detect possibly present errors. The software more or less confirms to the /uality and reliable standards.

67


;.2 LEVELS OF TESTIN%

(n order to uncover the errors present in different phases, we have the concept of levels of testing. The basic levels of testing are

lient $eeds

%cceptance Testing

#e/uirements

1ystem Testing

'esign

(ntegration Testing

ode

)nit Testing

68


U0i! !es!i05

)nit testing focuses verification effort on the smallest unit of software i.e. the module. )sing the detailed design and the process specifications, testing is done to uncover errors within the boundary of the module. %ll modules must be successful in the unit test before the start of the integration testing begins.

I0!e5/a!i30 Tes!i05

%fter unit testing, we have to perform integration testing. The goal here is to see if modules can be integrated properly, the emphasis being on testing interfaces between modules. This testing activity can be considered as testing the design and hence the emphasis on testing module interactions.

S"s!e Tes!i05

-ere the entire software system is tested. The reference document for this process is the re/uirements document, and the goal is to see if software meets its re/uirements.

A44e6!a04e Tes!i05

%cceptance Testing is performed with realistic data of the client to demonstrate that the software is working satisfactorily. Testing here is focused on eternal behavior of the system the internal logic of program is not emphasi"ed. Test cases should be selected so that the largest number of attributes of an e/uivalence class is eercised at once. The testing phase is an important part of software development. (t is the process of finding errors and missing operations and also a complete verification to determine whether the objectives are met and the user re/uirements are satisfied.

6


;.& *HITE BO TESTIN%

This is a unit testing method, where a unit will be taken at a time and tested thoroughly at a statement level to find the maimum possible errors. ( tested step wise every piece of code, taking care that every statement in the code is eecuted at least once. The white bo testing is also called 0lass Bo Testing. ( have generated a list of test cases, sample data, which is used to check all possible combinations of eecution paths through the code at every module level. 2hitebo test focuses on the program control structure. Test cases are derived to ensure that all statement in the program control structure. Test cases are derived to ensure that all statement in the program control structure. Test cases are derived to ensure that all statement in the program has been eecuted at least once during testing and that all logical conditions have been eercised. Basis path testing, a white bo techni/ue, makes use of program graphs 4or graph matrices5 to derive the set of linearly independent test that will ensure coverage. ondition and data flow testing further eercising degrees of compleity.

BLAC+ BO TESTIN%

This testing method considers a module as a single unit and checks the unit at interface and communication with other modules rather getting into details at statement level. -ere the module will be treated as a block that will take some input and generate output. Output for a given set of input combinations are forwarded to other modules. Blackbo test are designed to uncover errors functional re/uirement without regard to the internal workings of a program. Blackbo testing techni/ues focus on the information domain of the software, deriving test cases by partitioning the input and output domain of a program in manner that provides through test coverage. The blackbo test is used to demonstrate that software functions are operational, that input is properly produced, and that

7#


the integrity of eternal information are maintained. % blackbo test eamines some fundamental aspect of a system with little or no regard for the integral logical structure of the software. 0raph based testing methods eplore the relationship between and behavior of program objects. !/uivalence partitioning divides the input classes of data are likely to eercise specific software function. Boundary values analysis probes the program;s ability to handle data at the limits of acceptability.

;.' TEST INFORMATION FLO*

% strategy for software testing may also be viewed in the contet of the spiral. )nit testing begins at the vorte of the spiral and, concentrates on each unit, component of the software as implemented in source code. Testing progresses moving outward along the spiral to integration testing, where the focus is on designed the construction of the software architecture. Taking another turn outward on spiral, we encounter validation testing, 2here re/uirements established as part of software re/uirements analysis are validated against the software that has been constructed. Finally, we arrive at system testing, where the software and other system elements are tested as a whole. To test computer software, we spiral out along stream lines that broaden the scope of testing with each turn. onsidering the process from a procedural point of view, testing within the contet of software engineering is actually a series of four steps that are implemented se/uentially. The steps are shown in Figure. (nitially, tests focus on each component individually, ensuring that it functions properly as unit. -ence, the name unit testing. )nit testing makes heavy use of whitebo testing techni/ues, eercising specific paths in module;s control structure to ensure complete coverage and maimum error detection.

71


TESTIN% TECHNIQUES

System Tesng

Validaon Tesng

Integraon Tesng

Validaon tesng

72


INFORMATION FLO* OF DATA FOR TESTIN%

Evaluaton o@*are Con"%ra&on

-est 0es%ts

Error

Error 0ate Data

Testng

E?ected 0es%ts Debug

Reliabiliy Model -est Con"%ra&on

Predicated 0eia=iity

73


CHAPTER <

SYSTEM SECURITY

<.1 I0!/3$#4!i30

One might think that there is a little reason to be concerned about security in an intranet. %fter all, by definition an intranet is internal to ones; organi"ation outsider cannot access it. There are strong arguments for the position that an intranet should be completely open to its users, with little or no security. One might not have considered ones; intranet on any other light. On the other hand, implementing some simple, builtin security measures in ones; intranet can allow one to provide resources one might not have considered possible in such contet. For eample, one can give access to some 2eb *ages to some people without them available to owner entire customer base, with several kinds of authentication. (ntranet security is, then, a multifaceted issue, with both opportunities and dangers, especially if ones; network is part of the (ntranet.

There are basically two types of security associated with this system:

<.2 P>"si4a se4#/i!":7

'amage due to natural causes like earth tremor, flooding, water logging, fire ha"ards, atmospheric or environmental conditions etc..For overcoming these difficulties the replica of the data are automatically stored at various networks and for environmental conditions %ir conditioning environment is created.

74


<.&

Da!a se4#/i!":7

There are basically two problems associated with data security: a5. 'ata not being available to the authori"ed person at the time of need. b5. 'ata becoming available to the unauthori"ed person. To overcome these difficulties the following access facilities has been provided: i)

Identification:-

)ni/ue (ds for the different users have been provided.

ii)

Authentication:-

1ystem checks the password under the particular user identification. The computer permits the various resource to the authori"ed person.

iii)

Authorization:-

The access control mechanism to prevent unauthori"ed logging to the system.

<.' Nee$ f3/ Se4#/i!"

+any people view computer and network security in a negative light, thinking of it only in terms of restricting access to services. One major view of network security is Uthat which is not epressly permitted is denied.V %lthough this is a good way of thinking about how to connect other organi"ation to the internet, one can, and possibly should, view intranet security from a more positive angle. *roperty set up, intranet security can be an enabler, enriching ones; intranet with services and resources one would not otherwise be able to provide. 1uch an overall security policy might be described as Uthat which is not epressly denied is permitted.V

75


This does not mean that one should throw caution to the wind and make everything available to ones; users on ones; intranet. There are many things to consider when placing sensitive business data out on ones; intranet. (t may fall into the wrong hands, or worse, be used against ones; business. For eample, some of ones; users might have information they would li>ke to make available, provided access to it can be limited to a specified groupfor eample, confidential management or financial information. 2ithout the ability to ensure that only those who have the right to see such information will have access, the custodians of data will not be willing to put it on ones; intranet. *roviding security increases ones; organi"ation;s ability to use the important collaborative aspects of an intranet.

The more defensive approach, preventing abuse of one;s; intranet, is also given play, however. Organi"ations; needs for security in an intranet can vary widely. Businesses in which confidentiality and discretion are the norm in handling proprietary information and corporate intellectual property have different needs than a college or university, for eample. %cademic institutions generally tilt toward making the free echange of ideas a primary interest. %t the same time, though the curiosity 4to use a polite word5 of undergraduates re/uires strong needs for security. eeping prying sophomores out of university administration computing resources is a high priority for eample, students have been known to try to access grade records4their own or those of others5 for various reasons.

76


CHAPTER ?

SOFT*ARE AND HARD*ARE REQUIREMENT

?.1 Ha/$8a/e Re#i/ee0!s  *rocessor: *entium(&  #%+: J=< +B  O31: 2indowsA* 1*Q  -ard 'isk: <0B

?.2 S3f!8a/e Re#i/ee0!s  Operating 1ystem: +icrosoft 2indows A*3H.  ('!: &isual 1tudio
77


CHAPTER @

FUTURE ENHANCEMENT

= an be etended to manage inventory By integrating it with the inventory information and management techni/ues we can it as %ccounting with inventory 1ystem. < an be etended for Bi8anguage By integrating it with the !nglish language in project we can etend it to use bilanguage software 4-indi and !nglish5. Q an be etended for +ultiuser By integrating networking and other concepts we can etends it to use it as multiuser environment in place of single user environment. M an be added more #eports as per #e/uirement By integrating the more report like station wise report, ticket information etc. J +obile Ticket Booking This application can be upgraded from web application to mobile accounting.

78


Conclusion

%t the end of the #eport and project development we founds that overall performance of this project is K? to >? S are perfect, for its working functionality. Because project documentation provides such capabilities which can responsible to evaluates the performance and accuracy level of the project. 1o at the end of this, we found that this project provide the accurate result in the working area of Ticket Booking, ancellation, searching information and add the new user

7


Bus Reservation System Final Report

Recommend Documents