CHAPTER 1

INTRODUCTION
1.1 INTRODUCTION:The toll system existing nowadays is quit time consuming one. We cant get desired information about any specific vehicle from the existing toll system. Many manual processing is required to be done in order to data and still we cant get all the information. This drawback of existing system can be overcome by the automated toll system which we are going to develop. Following are some advantages which we will get from this system !eople dont have to wait for long time on toll booth to pay toll. "ll users traveling information is maintained. #o need to carry money on toll booth. $ashless transactions with the help of swap card. %asy to operate and understand. &elp to generate collection reports. Thus we get number of benefits from the new system as compared to the old one. 1.1.2 SCOPE:!repaid Toll 'ystem pro(ect gives the information of vehicles and the places visited by that vehicle) without any manual processing and within very less time period. This can be used on the toll booths for maintenance of database of vehicle and to detect criminal activities.

VACOE Computer Engineering 2012 1

1.1.3 OBJECTIVE:The main ob(ective of the system we are going to develop is that the system should be user friendly and time saving system for toll pla*a. This system should minimi*e manual processing load and should help us to detect criminal activities and reduces the manpower requirement. The system should maintain information of transaction history of every user. 1.1.4 LITERATURE REVIEW The literature review began with a search for any resources that had the potential for further review. "n online search was conducted using traffic resource websites and search engines to gather available electronic resources. This was followed by contact with representatives of different DOTs) toll a t!o"#t#$s) %o&' "at#&( a($&)#$s) and %o&' #&s "a&)$ a($&)#$s) as well as with academics. The literature review and sources of data focused primarily on +.'. practice and experience. &owever) there are several international pro(ects that have come into existence within the last ,- years in #orth "merica and in %urope.These are relatively state of the practice and provide the added benefit of being completed studies with tangible results .$.(.* t!$ H#(!+a, 4-. El$)t"o&#) Toll H#(!+a, #& Ca&a'a/. 0elevant publications and reports were not limited to) the following five sources of information1 2nline Transportation 0esearch 3nformation 'ervice .T03'/ The state of the practice survey $ontacts from the 42Ts) toll authorities) bond rating agencies) and bond insurance agencies .including members of the topic panel/ The consultants internal library and The Travel Model 3mprovement !rogram .TM3! 5/ 4igest. T03' 2nline is the web based version of the T03' database.3t provides links to full text and to resources for document delivery or access to documents where such
VACOE Computer Engineering 2012 2

information is available. These may include links to publishers) document delivery services) and6or distributors.The state of the practice survey) %stimating Toll 0oad 4emand and 0evenue) asked respondents to forward copies.$ontacts at the 42Ts) toll authorities) bond rating agencies)and bond insurance agencies provided hard copies or electronic versions of various reports where possible .i.e.)feasibility studies) risk assessment studies) traffic and revenue studies) etc./. They also provided information as traffic and revenue studies) travel pricing strategies) highway finance theory) and practice research) toll roads with respect to modeling) revenue) electronic toll and traffic management and toll road forecasting.

1.1.4.1 SURVE/ O0 PRACTITIONERS:" web based survey was sent to four types of organi*ations throughout the +nited 'tates1 'tate 42Ts) Toll authorities) 7ond rating agencies) and 7ond insurance agencies. The surveyincluded both the 8traditional9 transportation community .the first two types/ as well as the financial community .the last two types/. This diversity in the survey group was intended to capture the viewpoints and experience of the forecasting and modeling process from as many participants involved in the process as possible. !articipants were given the option of answering directly online through a web based survey program .Websurveyor/ or completing a hard copy of the survey that was included in the e mail as a pdf) which could be returned to the consultant by mail or by fax. The survey was divided into three self contained sections .designated as !arts 3) 33) and 333/.This made the survey more 8respondent friendly)9 to specifically target areas of interest in the modeling and forecasting process. !art 3 determined the type of agency that was responding to the survey and who from that agency was completing the questionnaire. !art 33 pertained to the forecasting model itself and its variables. This section was answered either by the original respondent) if the responding organi*ation performed the modeling and forecasting in house) or could
VACOE Computer Engineering 2012 3

be forwarded to a consultant or the agency that actually developed or applied the model for the original responding agency.!art 333 asked the respondent to discuss a specific example of a toll road traffic demand and revenue study carried out by the esponding organi*ation. 3n sum) ,:; surveys were sent to different organi*ations.There were << respondents) for a respons e rate of =->. 1.1.1 SO0TWARE RE2UIRE3ENT SPECI0ICATION:" software requirements specification .'0'/ is a complete description of the behavior of the system to be developed. 3t includes a set of use cases that describe all of the interactions that the users will have with the software. These specifications are of three types 1 1.1.1.1 NOR3AL RE2UIRE3ENTS: #, Time saving system. #? Maintain database of all users. #: 0educed manual processing on toll pla*a. #= 0educed man power on toll pla*a. #< $ollection report generation. 1.1.1.2 E4PECTED RE2UIRE3ENTS: %, +ser friendly system. %? $apture criminal activities. %: 'olves change problem. 1.1.1.3 E4CITED RE2UIRE3ENTS: @, Transaction message sending to owner. @? #o need to carry cash on toll pla*a. 1.1.5 VALIDATION O0 RE2UIRE3ENTS:VACOE Computer Engineering 2012 4

0equirement validation examines that all system requirements have been stated unambiguously and inconsistencies and errors have been detected and corrected. 3t also ensures that the work products confirmed to the standards established for the process) pro(ect and product. The work products produced as a consequence of requirements engineering are assessed during validation.

1.1.5.1 VALIDATION O0 NOR3AL RE2UIRE3ENTS: #, The system should be time saving one. #? A We should get information of every user from system database. #: A Manual process load should be minimi*ed. #= Manpower requirement on toll booth should be minimi*ed by the system. #< A We should get the collections reports from the system. 1.1.5.2 VALIDATION O0 E4PECTED RE2UIRE3ENTS: %, 'ystem should be user friendly and easy to operate. %? A 'ystem should help to detect the criminal activities. %: A 'ystem should solve change problem on toll booth. 1.1.5.3 VALIDATION O0 E4CITED RE2UIRE3ENTS: @, A 2wner of vehicle should be informed each time card is swapped. @? A $ashless transactions can be done by the swap card. 1.1.. HARDWARE RE2UIRE3ENTS: !rocessor != onwards.

VACOE Computer Engineering 2012 1

 <,? M7 0"M. 'wap $ard. 'wapping Machine. Mobile !hone.

1.1.6 SO0TWARE RE2UIRE3ENTS: Windows ?--- onwards "'!. #et $B 2racle ,-C

VACOE Computer Engineering 2012 5

CHAPTER 2 PROJECT PLANNIN7 AND 3ANA7E3ENT

2.1 SELECTIN7 PROJECT LI0E C/CLE 3ODELIN7 :3n contrast to software life cycle models) software process models often represent a networked sequence of activities) ob(ects) transformations) and events that embody strategies for accomplishing software evolution. 'uch models can be used to develop more precise and formali*ed descriptions of software life cycle activities. Their power emerges from their utili*ation of a sufficiently rich notation) syntax) or semantics) often suitable for computational processing. It$"at#8$ a&' I&)"$9$&tal '$8$lo:9$&t is at the heart of a cyclic software development process developed in response to the weaknesses of the waterfall model. 3t starts with an initial planning and ends with deployment with the cyclic interactions in between. 3terative and incremental developments are essential parts of the 0ational +nified !rocess) %xtreme !rogramming and generally the various agile software development frameworks. The basic idea is to develop a system through repeated cycles .iterative/ and in smaller portions at a time .incremental/) allowing the developer to take advantage of what was learned during the development of earlier portions or versions of the system. 5earning comes from both the development and use of the system) where possible key

VACOE Computer Engineering 2012 .

steps in the process start with a simple implementation of a subset of the software requirements and iteratively enhance the evolving versions until the full system is implemented. "t each iteration) design modifications are made and new functional capabilities are added. The incremental process model is suitable for our pro(ect as the number of developers is less. The product is delivered to the customer in the form of increments and any modifications suggested by the user are accommodated in the successive increments.

'ystem engineering
"nalysis 4esign $ode Test

4elivery of ,st increment

"nalysis

4esign

$ode

Test

4elivery of ?nd increment

"nalysis

4esign

$ode

Test

4elivery of :rd increment 4elivery of =th increment

"nalysis

4esign

$ode

Test

0#( 2.1 T!$ I&)"$9$&tal P"o)$ss 3o'$l W!, #&)"$9$&tal 9o'$l s #t o " :"o;$)t< 3f we are not getting the proper result in first increment then that can be modified in next increment. ,D 3t is a simple management model.

VACOE Computer Engineering 2012 6

2.2 BREA=DOWN STRUCTURE :The following figure shows the breakdown structure of the !repaid Toll 'ystem. 3t contains following main components A Ealidation 7alance deduction 0eport generation Mobile 'M' sending

The validation module includes validation of customer information) account balance and vehicle number in the card and actual number of vehicle.

VACOE Computer Engineering 2012 >

0#( 2.2 B"$a?'o+& St" )t "$ o@ S,st$9

2.3 COST AND E00ORT ESTI3ATION:!ro(ect estimation is nothing but calculating the time requirement and efforts required to complete the pro(ect. We can also determine the line of code of the pro(ect.

2.3.1 ESTI3ATION O0 =LOC:Craphical +ser 3nterface 4ata transfer from card to m6c ,.? F52$ -.< F52$
VACOE Computer Engineering 2012 1-

Ealidation of information 7alance deduction Mobile 'M' sending 0eport generation Total F52$ 2.3.2 E00ORTS :-

-.G F52$ -.? F52$ -.: F52$ -.= F52$ :.? F52$ ."pprox./

%fforts required to implement the pro(ect can be calculated by using the following formula % H :.? I .F52$/ J,.-< % H :.? I .:.?/ J,.-< % H ,-.;: person month 2.3.3 DEVELOP3ENT TI3E :4H%6# % H ,-.;: person month and #H: 4 H :.G, months i.e. #o. of persons.

2.3.4 TOTAL DEVELOP3ENT TI3E :Total development time for a pro(ect is equal to the time required for requirement analysis and system design and time required for implementation K testing.

VACOE Computer Engineering 2012 11

Time required for 0equirement "nalysis and 'ystem 4esign - A 1 .2 9o&t!B C Time required for 3mplementation K Testing Total '$8$lo:9$&t t#9$ - A 3.5 9o&t!s B A4.6 9o&t!s a::"oD.B

Thus) we requires total =.; months to complete the pro(ect.

2.4 PROJECT SCHEDULIN7:2.4.1 PROJECT SCHEDULIN7 AND TRAC=IN7:!ro(ect 'cheduling and Tracking is important because in order to build a complex system) many software engineering tasks occur in parallel) and the result of work performed during one task may have a profound effect on work to be conducted in another task. These interdependencies are very difficult to understand without a detailed schedule.

2.4.1.1 PROJECT WOR= BREA=DOWN STRUCTURE AANAL/SISB:-

VACOE Computer Engineering 2012 12

0#( 2.4.1.1 P"o;$)t Wo"? B"$a?'o+& St" )t "$ AA&al,s#sB

Fig ?.=.,., shows the !ro(ect Work 7reakdown 'tructure. The proposed system is divided into five main tasks vi*.) $ommunication) !lanning) Modeling) $onstruction and 4eployment.. These Tasks are further divided in subtasks.

2.4.1.2 TAS=S:T,1 !ro(ect 4efinition 'earching. T?1 Material $ollection. T:1 0equirement Cathering and Ealidating. T=1 !ro(ect !lanning. T<1 'ystem 4esign. TG1 !ro(ect 'cheduling and Tracking.

VACOE Computer Engineering 2012 13

TL1 $reation of "nalysis Model. T;1 0isk "nalysis and Management. TM1 3nitial Craphical +ser 3nterface. T,-1 Writing 3nformation into 'wap $ard. T,,1 Transfer 3nformation from $ard to M6$. T,?1 Ealidation $ard 3nformation. T,:1 $hecking $ard 'tatus. T,=1 4educting 7alance. T,<1 'end 'M' to 2wner of $ard. T,G1 'tore the 3nformation about $ustomer Transaction &istory. T,L1 +pdate 3nformation in 4atabase. T,;1 0eport Ceneration. T,M1 Testing. T?-1 Feedback from $ustomer. T?,1 Make 0equired Modifications. T??1 0elease of Final 'oftware. 2.4.2 PROJECT SCHEDULE:The table ?.=.,., describes the schedule for pro(ect development and also highlights all the tasks to be carried out along with their duration) dependency and developer.s/ assigned to accomplish the task. Tas?s T, T? T: T= T< TG TL T; TM T,T,, Da,s : = < < G ; ,? ,,, L : D$:$&'$&)#$s D$8alo:$"s Ass#(&$' 4,)4?)4: 4,)4?)4: 4,)4?)4: 4,)4?)4: 4,)4?)4: 4,)4?)4: 4,)4?)4: 4?)4: 4,)4? 4,)4?)4: 4,)4?

T, T,)T? T: T: T=)T< T=)T< T<)TG TL T,-

VACOE Computer Engineering 2012 14

T,? T,: T,= T,< T,G T,L T,; T,M T?T?, T?? Total 4ays

? < G ,? < L ; G = ; : ,=-

T,-)T,, T,? T,-)T,? TG T,, T,G T,L T?-

4?)4: 4,)4? 4?)4: 4,)4?)4: 4,))4: 4,)4?)4: 4,)4?)4: 4,)4?)4: 4,)4?)4: 4,)4?)4: 4,)4?)4:

Ta%l$ 2.4.2 P"o;$)t S)!$' l$

2.4.2.1 TI3E LINE CHART:-

1 3ndicates Milestone M,/ Finali*ation of 0equirements M?/ 'ystem 4esign

VACOE Computer Engineering 2012 11

0#( 2.4.2.1 T#9$ L#&$ C!a"t

0#( 2.4.2.2 T#9$ L#&$ C!a"t2

1 3ndicates Milestone M,/ $reating 'wap $ard M?/ 'M' 'ending to 2wner M:/ Testing 2.4.3 PROJECT TABLE:Tas? &o T, T? T: T= T< TG TL T; TM Sta"t#&( t#9$ ED:$)t$' A)t al ,,6-L6,, ,;6-L6,, ?<6-L6,, -,6-;6,, -G6-;6,, ,,6-;6,, ,M6-;6,, -,6-M6,, ,<6-M6,, ,?6-L6,, -G6-;6,, ,:6-;6,, ,M6-;6,, ?<6-;6,, :-6-;6,, -L6-M6,, ,:6-M6,, -=6,-6,, E&'#&( T#9$ ED:$)t$' A)t al ,=6-L6,, ??6-L6,, :-6-L6,, -G6-;6,, ,?6-;6,, ,M6-;6,, :,6-;6,, ,-6-M6,, ?G6-M6,, -L6-;6,, ,?6-;6,, ,;6-;6,, ?:6-;6,, ?M6-;6,, -G6-M6,, ,=6-M6,, -?6,-6,, ,=6,-6,, D$8$lo:$"s Ass#(&$' 4,)4?)4: 4,)4?)4: 4,)4?)4: 4,)4?)4: 4,)4?)4: 4,)4?)4: 4,)4?)4: 4?)4: 4,)4? R$9a"?

VACOE Computer Engineering 2012 15

T,T,, T,? T,: T,= T,< T,G T,L T,; T,M T?T?, T??

:-6-M6,, -M6-,6,? -M6-,6,? -:6-?6,? -G6-?6,? -M6-?6,? ?M6-?6,? -<6-:6,? ,?6-:6,? ,M6-:6,? ?G6-:6,? -?6-=6,? -M6-=6,?

,=6,-6,, ,?6-,6,? ,?6-,6,? -L6-?6,? ,?6-?6,? ,=6-?6,? -?6-:6,? ,?6-:6,? ,;6-:6,? ??6-:6,? -,6-=6,? ,,6-=6,? ,M6-=6,?

-L6,-6,, -?6-?6,? ,,6-?6,? -;6-?6,? ,?6-?6,? ?,6-?6,? -:6-:6,? ,?6-:6,? ?-6-:6,? ?<6-:6,? :-6-:6,? ,-6-=6,? ,?6-=6,?

,M6,-6,, -;6-?6,? ,<6-?6,? ,-6-?6,? ,=6-?6,? ?<6-?6,? -;6-:6,? ,M6-:6,? ?=6-:6,? -,6-=6,? ,-6-=6,? ,;6-=6,? ??6-=6,?

4,)4?)4: 4,)4? 4?)4: 4,)4? 4?)4: 4,)4?)4: 4,))4: 4,)4?)4: 4,)4?)4: 4,)4?)4: 4,)4?)4: 4,)4?)4: 4,)4?)4:

Ta%l$ 2.4.3 P"o;$)t Ta%l$

CHAPTER 3 ANAL/SIS
3.1 USECASE 3ODEL:-

3.1.1 USE CASE DIA7RA3AS/STE3 OVERVIEWB:" use case involves a sequence of interactions between the initiator and the system) possibly involving other actors.

VACOE Computer Engineering 2012 1.

0#( 3.1.1 Us$ Cas$ D#a("a9 @o" S,st$9 O8$"8#$+

3.1.2 USE CASE DIA7RA3APREPAID TOLL S/STE3B:-

VACOE Computer Engineering 2012 16

0#( 3.1.2 Us$ Cas$ D#a("a9 @o" P"$:a#' Toll S,st$9

3.2 PROCESS 0LOW DIA7RA3S:3.2.1 ACTIVIT/ DIA7RA3:-

VACOE Computer Engineering 2012 1>

"ctivity diagrams are very similar to a flowchart because you can model a workflow from activity to activity. 7elow is the activity diagram for !repaid Toll 'ystem.

0#( 3.2.1 A)t#8#t, D#a("a9 @o" t!$ S,st$9

3.2.2 CONTROL 0LOW DIA7RA3:The large class of applications having following characteristics requires control flow modeling1

VACOE Computer Engineering 2012 2-

 The applications those are driven by the events rather than data. The applications those produce control information rather than reports or displays. The application those process information in specific time.

0#( 3.2.2 Co&t"ol @lo+ D#a("a9

3.2.3 DATA 0LOW DIA7RA3:-

VACOE Computer Engineering 2012 21

4ata flow diagram .4F4/ is also called as N7ubble $hart is a graphical technique) which is used to represent information flow) and transformers those are applied when data moves from input to output. 4F4 represents system requirements clearly and identify transformers those becomes programs in design. 4F4 may further partitioned into different levels to show detailed information flow e.g. level-) level, etc.

0#( 3.2.3.1 Data 0lo+ D#a("a9Al$8$l -B

0#( 3.2.3.2 Data 0lo+ D#a("a9Al$8$l 1B

CHAPTER 4

VACOE Computer Engineering 2012 22

DESI7N
4.1 DETAILED CLASS DIA7RA3:4.1.1 CLASS DIA7RA3:3n design specification it can be used to specify interfaces and classes that will be implemented in an ob(ect oriented program. $lass diagram shows the interdependencies between the classes of the system.

0#( 4.1.1 Class D#a("a9

4.2 DESI7N LEVEL SE2UENCE DIA7RA3:-

VACOE Computer Engineering 2012 23

4.2.1 SE2UENCE DIA7RA3:" sequence diagram is a graphical view of a scenario that shows ob(ect interaction in a time based sequence. 'equence diagrams establish the roles of ob(ects and help provide essential information to determine class responsibilities and interfaces. This type of diagram is best used during early analysis phases in design because they are simple and easy to comprehend. 'equence diagrams are normally associated with use cases.

0#( 4.2.1 S$E $&)$ D#a("a9 @o" t!$ S,st$9

4.3 STATE TRANSITION DIA7RA3:VACOE Computer Engineering 2012 24

'tate chart diagrams model the dynamic behavior of individual classes or any other kind of ob(ect. They show the sequences of states that an ob(ect goes through) the events that cause a transition from one state to another and the actions that result from a state change.

0#( 4.3 Stat$ T"a&s#t#o& D#a("a9

VACOE Computer Engineering 2012 21

CHAPTER 1 RIS= 3ANA7E3ENT

R#s? 9a&a($9$&t is the identification) assessment) and prioriti*ation of risks followed by coordinated and economical application of resources to minimi*e) monitor) and control the probability and6or impact of unfortunate events or to maximi*e the reali*ation of opportunities

1.1 RIS= IDENTI0ICATION:-

1.1.1 CUSTO3ER RELATED:0, $ustomer may not be a technical person) so understanding exact

requirements of customer may not be possible. 0? 3f non feasible or irrelevant requirements are provided by the customer) it may generate some unknown risk. 1.1.2 PRODUCT SIFE RELATED:0: !roduct si*e may increase due to inefficient implementation of system. 1.1.3 BUSINESS I3PACT:0= 4elay in pro(ect delivery .violation of time constraints/ can hamper the

customer economically.

VACOE Computer Engineering 2012 25

1.1.4 STA00 SIFE RELATED:0< "s the scope of the pro(ect is too large) it may be difficult to complete it in given span of time with : persons.

1.1.1 DEVELOP3ENT ENVIRON3ENT RELATED:0G 5ack of training on the development tools may cause an inefficiency and difficulty in pro(ect completion. 0L 'oftware !rocess Model is not followed upto the defined degree. 0; 3f customer asks for modification.s/ in later stages of development) it is difficult to alter the entire system in accordance with that change.s/.

1.1.5 PRODUCT RELATED:0M 3f customer forgets to bring swap card at toll pla*a. 0,- 3f customer does not have sufficient balance. 0,, 3nput should not be other than swap card. 0,? 3f customer lost his swap card or vehicle.

1.2 STRATE7IES USED TO REDUCE RIS=S:

VACOE Computer Engineering 2012 2.

', 0egular meeting with the customer reduces risks. '? More time should be spend upon testing and improvement. ': Time constraints must be followed to avoid economical risks. '= 'election of incremental model so that the pro(ect can be completed with less '< reduces risk. 'G 0edefine software process at a higher degree. 'L 'ystem should be flexible enough to adopt future changes and number of persons. !roper training on required technical tools for development of pro(ect

modifications suggested by user. '; $ustomer has to make cash payment. 'M message. ',- $ustomer has to purchase new swap card and make status of old card as inactive. 3f card information does not match with database then show error

VACOE Computer Engineering 2012 26

1.3 RIS= PROJECTION:

Table below lists all possible risks which may occur at any stage during development of pro(ect. Table also clearly shows the impact of risks and 0MMM .0isk Mitigation Monitoring and Management/ plan to deal with any such risks.

R#s? 0, 0? 0: 0= 0< 0G 0L 0; 0M 0,0,, 0,?

Cat$(o", $ustomer related $ustomer related !roduct si*e related 7usiness impact 'taff si*e related 4evelopment %nvironment related 4evelopment %nvironment related $ustomer related $ustomer related $ustomer related $ustomer related $ustomer related

P"o%a%#l#t, Moderate 5ess More More More 5ess 5ess 5ess Moderate Moderate 5ess 5ess

I9:a)t &igh Medium 5ow &igh &igh 5ow &igh &igh 5ow 5ow 5ow Medium

R333 Pla& ', ', '? ': '= '< 'G 'L '; '; 'M ',-

Ta%l$ 1.1 R#s? Ta%l$

CHAPTER 5

VACOE Computer Engineering 2012 2>

I3PLE3ENTATION AND CODIN7

5.1 7UI I3PLE3ENTATION:3n the C+3 implementation we have designed front end for user interaction with the system. C+3 is the backbone of every pro(ect for user interaction. Cood C+3 will marginally improve the popularity of the pro(ect.C+3 consists of following forms ,/ 5ogin Form ?/ $ustomer 0egistration Form :/ 2perator 0egistration Form =/ 'alepoint 0egistration Form </ Toll !oint 0egistration Form G/ Toll !oint Main Form L/ 'ale !oint Main Form ;/ "dmin Main Form M/ Weekly $ollection 0eport Form ,-/ 5ist 2f "ll Toll !oints Form ,,/ 5ist 2f "ll 'ale !oints Form ,?/ 5ist 2f "ll 2perators Form ,:/ 4aily $ollection 0eport Form ,=/ Web 'ervice Form

5.1.1 LO7IN 0OR3:-

VACOE Computer Engineering 2012 3-

This is the first form of the pro(ect. There are three different logins as "dmin) 'ale!oint and Toll!oint. %very +ser is having saperate access rights to the system. 4epending on the type of user the access rights are granted. +sername and password of user is validated and if the user is authorised then accrss is granted otherwise access denied.

0#(. 5.1.1 Co99o& Lo(#& 0o"9

5.1.2 CUSTO3ER RE7ISTRATION 0OR3:VACOE Computer Engineering 2012 31

%very customer have to register himself6herself while purchasing the card. 2nce the customer is registered successfully then he6she can start using the card for the toll transactions. %ach customer is identified by its card number and the customer id which he6she obtain at the time of registration.

0#( 5.1.2 C sto9$" "$(#st"at#o& @o"9

5.1.3 OPERATOR RE7ISTRATION 0OR3:-

VACOE Computer Engineering 2012 32

There are many operators working on various toll points and salepoints. %ach operator is also registered with a unique operator 34. The operator has to enter his6her operator id while registering on the toll point or salepoint. Following is the operator registration form

0#( 5.1.3 O:$"ato" R$(#st"at#o& 0o"9

5.1.4 SALEPOINT AND TOLLPOINT RE7ISTRATION 0OR3:VACOE Computer Engineering 2012 33

%very sale point and toll point is also registered with the central database. %ach salepoint as well as tollpoint is have a name)city)district and password for secure login. 'alepoints and tollpoints are registered as new stations establishes on various places.

0#( 5.1.4.1 Sal$:o#&t R$(#st"at#o& 0o"9

VACOE Computer Engineering 2012 34

0#( 5.1.4.2 Toll:o#&t R$(#st"at#o& 0o"9

VACOE Computer Engineering 2012 31

5.1.1 DAIL/ AND WEE=L/ COLLECTION REPORTS:We can analysis the toll point and salepoint depending on the collection reports generated from recharge collection and toll collection. We have generated the daily as well as weekly recharge and toll collection reports for analysis purpose. " list of all tollpoints) salepoints) operators) lost cards and issued cards can be obtained. These collection reports are very useful for the toll company who establishes a toll station for profit A loss anlysis.

0#( 5.1.1.1 Da#l, "$)!a"($ "$:o"t

VACOE Computer Engineering 2012 35

0#( 5.1.1.2 W$$?l, Toll "$:o"t Weekly toll collection reports are used to calculate the total collection in the perticular week of the month. Thus collection reports are playing very vital role in the estimation of the total profit from particular toll station or sale point station.

VACOE Computer Engineering 2012 3.

5.1.5 WEB SERICES USED:We have created web methods for each task and called these web methods in our pro(ect by using the web service. The main web service is 8trans9 and all the web methods are accessed through this web service. Following is the sample web service which contains many web method like $ustomerOregistration 2peratorOregistration Toll!ointOregistration 'alepointOregistration 0echargeOcard etc.

0#( 5.1.5 W$% S$"8#)$s

VACOE Computer Engineering 2012 36

5.1.. LIST O0 ALL SALEPOINTS:This Form is mainly used for getting the list of all salepoints in the area. %ach sale point is registered in the central database at the time of the registration of the salepoint. Thus we can easily retrieve the information about any sale point from the database. We can easily get the list of the all salepoints by using queries.

0#( 5.1.. L#st o@ sal$:o#&ts

VACOE Computer Engineering 2012 3>

5.1.6 LIST O0 ALL TOLLPOINTS:Many times it is required to have the list of all toll stations. This Form is mainly used for getting the list of all toll points in the area. %ach toll point is registered in the central database at the time of the registration of the salepoint. Thus we can easily retrieve the information about any toll point from the database. We can easily get the list of the all toll points by using queries.

0#( 5.1.6 L#st o@ Toll :o#&ts

VACOE Computer Engineering 2012 4-

5.1.> TOLL POINT 3AIN 0OR3:Following is the toll point main form which is visible to the end user at the toll station. 3t consists of reading the card data and validating it. We read the card information and check the card balance) if balance is sufficient then transaction completes otherwise the message wii be displayed to the customer. $ard balance will be deducted as per the vehicle type.

0#( 5.1.> Toll Po#&t 3a#& 0o"9

VACOE Computer Engineering 2012 41

5.1.1- SALE POINT 3AIN 0OR3:'ale point can register the new customer and issue new cards to the new users. "lso the customer can get new card if he6she lost his6her old card. $ustomer has to register the lost card details to the sale point for making that card status as 83nactive9 to prevent the misuse. $ustomer can recharge his6her account balance at the sale point.

0#( 5.1.1- Sal$ Po#&t 3a#& 0o"9

VACOE Computer Engineering 2012 42

5.1.11 AD3IN 3AIN 0OR3:"dmin can register the new operator) new sale point) new toll point. "lso he can get many kind of collection reports as well as list reports. #ew operator) new sale point) new toll point has to register details to the admin for making the database entry.. $ustomer card history can be taken by history report.

0#( 5.1.11 A'9#& 3a#& 0o"9

VACOE Computer Engineering 2012 43

CHAPTER . TESTIN7
..1 UNIT TESTIN7:" series of stand alone tests are conducted during +nit Testing. %ach test examines an individual component that is new or has been modified. " unit test is also called a module test because it tests the individual units of code that comprise the application. %ach test validates a single module that) based on the technical design documents) was built to perform a certain task with the expectation that it will behave in a specific way or produce specific results. +nit tests focus on functionality and reliability) and the entry and exit criteria can be the same for each module or specific to a particular module. +nit testing is done in a test environment prior to system integration. 3f a defect is discovered during a unit test) the severity of the defect will dictate whether or not it will be fixed before the module is approved. ..1.1 SA3PLE ENTR/ AND E4IT CRITERIA:ENTR/ CRITERIA: 7usiness 0equirements are at least ;-> complete and have been approved to date Technical 4esign has been finali*ed and approved 4evelopment environment has been established and is stable $ode development for the module is complete E4IT CRITERIA: $ode has version control in place #o known ma(or or critical defects prevents any modules from moving to 'ystem Testing " testing transition meeting has be held and the developers signed off !ro(ect Manager approval has been received
VACOE Computer Engineering 2012 44

..2 INTE7RATION TESTIN7:3ntegration testing examines all the components and modules that are new) changed) affected by a change) or needed to form a complete system. Where system testing tries to minimi*e outside factors) integration testing requires involvement of other systems and interfaces with other applications) including those owned by an outside vendor) external partners) or the customer. For example) integration testing for a new web interface that collects user input for addition to a database must include the databases %T5 application even if the database is hosted by a vendorPthe complete system must be tested end to end. 3n this example) integration testing doesnt stop with the database loadQ test reads must verify that it was correctly loaded. 3ntegration testing also differs from system testing in that when a defect is discovered) not all previously executed tests have to be rerun after the repair is made. 2nly those tests with a connection to the defect must be rerun) but retesting must start at the point of repair if it is before the point of failure. For example) the retest of a failed FT! process may use an existing data file instead of recreating it if up to that point everything else was 2F. ..2.1 SA3PLE ENTR/ AND E4IT CRITERIA:ENTR/ CRITERIA: 'ystem testing has been completed and signed off 2utstanding issues and defects have been identified and documented Test scripts and schedule are ready The integration testing environment is established

VACOE Computer Engineering 2012 41

E4IT CRITERIA: "ll systems involved passed integration testing and meet agreed upon functionality and performance requirements 2utstanding defects have been identified) documented) and presented to the business sponsor 'tress) performance) and load tests have been satisfactorily conducted The implementation plan is final draft stage " testing transition meeting has been held and everyone has signed off ..3 ACCEPTANCE TESTIN7:"cceptance Testing is also called 7eta testing) application testing) and end user testing. Whatever you choose to call it) its where testing moves from the hands of the 3T department into those of the business users. 'oftware vendors often make extensive use of 7eta testing) some more formally than others) because they can get users to do it for free. 7y the time "T is ready to start) the 3T staff has resolved in one way or another all the defects they identified. 0egardless of their best efforts) though) they probably dont find all the flaws in the application. " general rule of thumb is that no matter how bulletproof an application seems when it goes into "T) a user somewhere can still find a sequence of commands that will produce an error. To be of real use) "T cannot be random users playing with the application. " mix of business users with varying degrees of experience and sub(ect matter expertise need to actively participate in a controlled environment. 0epresentatives from the group work with Testing $oordinators to design and conduct tests that reflect activities and conditions seen in normal business usage. 7usiness users also participate in evaluating the results. This insures that the application is tested in real world situations and that the tests cover the full range of business usage. The goal of "T is to simulate realistic business activity and processes in the test environment. " phase of "T called 8+nstructured Testing9 will be conducted whether or not its in the Test !lan. "lso known as guerilla testing) this is when business users bash away at the keyboard to find the weakest parts of the application. 3n effect) they try to break it. "lthough its a free form test) its important that users who participate
VACOE Computer Engineering 2012 45

understand that they have to be able to reproduce the steps that led to any errors they find. 2therwise its of no use. " common occurrence in "T is that once the business users start working with the application they find that it doesnt do exactly what they want it to do or that it does something that) although correct) is not quite optimal. 3nvestigation finds that the root cause is in the 7usiness 0equirements) so the users will ask for a change. 4uring "T is when change control must be most seriously enforced) but change control is beyond the scope of this paper. 'uffice to say that scope creep is especially dangerous in this late phase and must be avoided. ..3.1 SA3PLE ENTR/ AND E4IT CRITERIA:ENTR/ CRITERIA: 3ntegration testing signoff was obtained 7usiness requirements have been met or renegotiated with the 7usiness 'ponsor or representative "T test scripts are ready for execution The testing environment is established 'ecurity requirements have been documented and necessary user access obtained E4IT CRITERIA: "T has been completed and approved by the user community in a transition meeting $hange control is managing requested modifications and enhancements

VACOE Computer Engineering 2012 4.

CHAPTER 6 RESULT AND DISCUSSIONS

!repaid toll system pro(ect comes handy as it provides the totally automated version of the toll pla*a. Following are some advantages of the prepaid toll system. OVERALL ADVANTA7ES: 3n our pro(ect) we provided the following facilities1 ,D !roviding automated sustem for toll pla*a. ?D Making the prepaid toll transactions. :D Finding the history of the card. =D.Making fast toll transactions <D !roviding reports for analysis GD 4etecting criminal activities LD 0educe sound pollution in heavy traffic places 2ur software is much more easy to use interact in comparison to the other similar software present in the market. From above listed facilities) we can say that there are many advantages of our pro(ect. When the user will register with us through his6her card) we will provide him6her assistance for fats toll transactions. We will also protect users card from unauthorised use which may cause harm. We also provided admin facilities such as report generation for the analysis and making decisions for traffic analysis for certain areas. "part from that our software will also inform the user about his6her previous toll transactions and current actions by sending transaction messages on his6her mobile phone. LI3ITATIONS: The basic limitation of our system is that it is time consuming under some instances such as if server connection is not good)internet facility is not present or it is not good enough etc.

VACOE Computer Engineering 2012 46

CHAPTER > CONCLUSION

The system comes handy as it provides automation for toll system. There is no need to carry cash on toll pla*a while travelling on roads for the card holders as we are providing swap card for each customer. The system is very much time saving and user friendly which is easy to operate and understand. The 8!0%!"34 T255 'R'T%M9 reduces manual processing done on the toll pla*a and hence the manpower requirement on the toll pla*a is reduced.

VACOE Computer Engineering 2012 4>

BIBLIO7RAPH/

2nline Transportation 0esearch 3nformation 'ervice .T03'/ The state of the practice survey $ontacts from the 42Ts) toll authorities) bond rating agencies) and bond insurance agencies .including members of the topic panel/ The consultants internal library and The Travel Model 3mprovement !rogram .TM3! 5/ 4igest.

http166www.fhwa.dot.gov6eigd6e*pass.html ww.rppi.org6transportation6index.html www.path.berkeley.edu6itsdecision6servOandOtech6%lectronicOtoll collection6electronOtollOcollectionOreport.html www.e*pass.com

VACOE Computer Engineering 2012 1-