8/17/2019 65465465

1/32

1

Maintains the new entry broker who are wanted to do testing, getting

detail knowledge of 

the testing own Bikes, searching Bike Information who was tested,

searching about

Testing, and also done the modify any test and bike or staff information

and so on . This

Task is usually entrusted to a single person, the system administrator,

also known as the

super user. He has vest powers, having access to practically everything.

 

8/17/2019 65465465

2/32

System planning

 !cheduling of a software pro"ect does not differ greatly from !ystem

administrator in window #p is not $uite demanding and re$uires form the

administrator an in depth knowledge of the different components. The above stated

task of a system administration is considered as routine duties of an administrator.

But system problem can be $uite grave and une#pected By identify the system

responsibilities of a administrator to be $uite demanding re$uiring a through

knowledge of the system, which makes it a cumbersome "ob. %e identified a need of 

&graphical tool for the task of system administration as its menu and screens will

guide him through the whole process.'scheduling of any multitask engineering

effort. Therefore, generali(ed pro"ect scheduling tool and techni$ues can be applied

with little modification to software pro"ects. )rogram evaluation and review

Techni$ue *)+T- and critical path method *)M- are two pro"ect scheduling

method that can be applied to software development. Both techni$ues are driven by

information already development in pro"ect planning activities/

⇒ +stimates of +ffort

⇒ 0 decomposition of the product function

⇒ The selection of the appropriate process model and task set

⇒ ecomposition of tasks

8/17/2019 65465465

3/32

2

Project Estimation:-

The pro"ect si(e is another important factor for the pro"ect estimation that can affect

accuracy and efficacy of estimations. 0s si(e increase, the interdependency among

various elements of the software grown rapidly.

Risk Analysis:-

isk analysis and management are a series of steps that help a software team to

understand and manage uncertainty. Many problems can infected a software pro"ect.

0

risk is a potential problem3it might happen it might not. But regardless of the

outcome,

it4s a really good idea of identify it, assess its probability of occurrence, estimate its

impact, and establish a possibility plan should the problem actually occur.

5or isk analysis firstly recogni(ing what can go wrong that is called &risk

Identification

&.6e#t, each risk is analy(ed to determine the probability that it will occur and the

damage that will do if it does occur. 7nce this information is established, risks are

ranked, by probability and impact. 5inally a plan is developed to manage those risks

with

high probability and high impact.

8/17/2019 65465465

4/32

8

Chapter 4

  System Designing

+3 I090M

0T0 5:7% 0I90M

 

I6);T

8/17/2019 65465465

5/32

=

8/17/2019 65465465

6/32

>

!I96 ;)

+9

I!T 

0TI

76

:79I6

+?M0I: ;!+ 0MI6

;!+ 60M+0+!!

)0!!%7

M7BI:+ 67

TH+0T+ +6T@

+6T 

@

0+!!!H7%TH+0T+ 60M+

+6T

@

 

+6T

@0T+ +6T@ M7AI+! +6T@

0M7;6TTH+0T+ 60M+ I!I)TI76

0M7;6T!+0TTI+T 67.

!H7%!+0T T@)+

TI+T +T0I:!T0T 0T+

TH+0T+ 60M+ M7AI+ 60M+ +6 0T+

8/17/2019 65465465

7/32

C

Data flow diagram

  ER! "E#E" DA$A %"!& D'A(RA)

 

;!+ 

+9I!T0TI76

!I96 ;)

+ MI0:;!+ 60M+

)I6 7+)0!!%7

0+!!M7BI:+ 67.

7;T);TI6);T

)7+!!

8/17/2019 65465465

8/32

D

0T0B0!+

 

%'RS$ "E#E" DA$A %"!& D'A(RA)

 

;!+

0MI6

 

:79I6

8/17/2019 65465465

9/32

E

SEC!*D "E#E" DA$A %"!&D'A(RA)

 

TH+0T+ 60M+

TH+0T+

+6T@

TH+0T+

+6T@!H7%

0+!!

TH+0T+ 60M+

M7AI+ 60M+

M7AI+!

+6T@

M7AI+

+6T@ !T0T 0T+

+6 0T+

I!I)TI76

TH+0T+ 60M+

0T+ +6T@!H7%0T+

+6T@

!+0T T@)+

0M7;6T

TI+T 67.

TI+T

+T0I:

0M7;6T

!+0T 67.

TI+T

+T0I:

8/17/2019 65465465

10/32

1F

 SDLC Model 

FROM ANALYSIS 

1

+T0I:+ !@!T+M

7;M+6T0TI76

7;T);T

+!I96

I6);T

+!I96 7!T G;!TI5I0TI76 !@!T+M +!I96+!I96

!;BMITT+ T7

M060M+6T 57 

0))7A0:

5I:+

+!I96

8/17/2019 65465465

11/32

11

 NO

 

GO TO

 IMPLEMENTATION 

 

)7+!!I69

+!I96 +!I96  0+)T

0B0676)7G+T

  T+!T)790M

2

8/17/2019 65465465

12/32

1

"!('* %!R)

Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EentAr!s" #andles Button1.Click  $% (&adioButton1.C'ecked )rue" )'en  $% ()e*tBo*1.)e*t +moie+" )'en  $% ()e*tBo*.)e*t +satna+" )'en

  &es-onse.&edirect(+t'eater entry.as-*+"  End $%  End $%  End $%  cmd e/  System.0ata.SlClient.SlCommand(+select 2 %romsi!nu-+, con"  dtr cmd.E*ecute&eader("

  $% (&adioButton.C'ecked )rue" )'en  dtr.&ead("  $% ()e*tBo*1.)e*t dtr(+username+".)oStrin!("" )'en  $% ()e*tBo*.)e*t dtr(+-ass/ord+".)oStrin!("" )'en

8/17/2019 65465465

13/32

12

&es-onse.&edirect(+a%ter user lo!in.as-*+"  End $%  End $%  End $%  dtr.Close("  End Sub

  S'(* +P

Partial Class 0e%ault  $n'erits System.3eb.4$.Pa!e  0im con As e/  System.0ata.SlClient.SlConnection  0im cmd As e/  System.0ata.SlClient.SlCommand  0im dtr As  System.0ata.SlClient.Sl0ata&eader

  Protected Sub Pa!e_5oad(ByVal sender As Object, ByVal e As System.EentAr!s" #andles 6e.5oad  con e/  System.0ata.SlClient.SlConnection(+0ataSource.7S85E9P&ESS:Attac'0b;ilenameC:4ser $nstance)rue+"  con.O-en("  End Sub

  Protected Sub Button=_Click(ByVal sender As Object, ByVal e As System.EentAr!s" #andles Button=.Click  cmd e/  System.0ata.SlClient.SlCommand(+insert intosi!nu- alues(?+ @ )e*tBo*1.)e*t @ +?,?+ @ )e*tBo*.)e*t @ +?,?+ @)e*tBo*=.)e*t @ +?,?+ @ )e*tBo*.)e*t @ +?,?+ @ )e*tBo*.)e*t @+?,?+ @ )e*tBo*.)e*t @ +?"+, con"  cmd.E*ecuteon8uery("  )e*tBo*1.)e*t ++  )e*tBo*.)e*t ++

  )e*tBo*=.)e*t ++  )e*tBo*.)e*t ++  )e*tBo*.)e*t ++  )e*tBo*.)e*t ++

  End SubEnd Class

 

$,EA$ER E*$R

Partial Class 0e%ault  $n'erits System.3eb.4$.Pa!e  0im con As e/  System.0ata.SlClient.SlConnection  0im cmd As e/  System.0ata.SlClient.SlCommand  0im dtr As  System.0ata.SlClient.Sl0ata&eader

  Protected Sub Pa!e_5oad(ByVal sender As Object, ByVal e As System.EentAr!s" #andles 6e.5oad

8/17/2019 65465465

14/32

18

con e/  System.0ata.SlClient.SlConnection(+0ataSource.7S85E9P&ESS:Attac'0b;ilenameC:4ser $nstance)rue+"  con.O-en("  End Sub

  Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EentAr!s" #andles Button1.Click  cmd e/  System.0ata.SlClient.SlCommand(+insert intot'eaterentry alues(?+ @ )e*tBo*1.)e*t @ +?,?+ @ )e*tBo*.)e*t @+?,?+ @ )e*tBo*=.)e*t @ +?,?+ @ 5abelD.)e*t @ +?,?+ @ 5abel1>.)e*t @+?,?+ @ 5abel11.)e*t @ +?"+, con"  cmd.E*ecuteon8uery("  5abel1=.)e*t 6s!Bo*(+record sae+"  )e*tBo*1.)e*t ++  )e*tBo*.)e*t ++  )e*tBo*=.)e*t ++

  End Sub

  Protected Sub Button_Click(ByVal sender As Object, ByVal e As System.EentAr!s" #andles Button.Click  cmd e/  System.0ata.SlClient.SlCommand(+u-datet'eaterentry set address?+ @ )e*tBo*.)e*t @ +?,moie?+ @)e*tBo*=.)e*t @ +?,s'o/1 ?+ @ 5abelD.)e*t @ +?,s'o/?+ @5abel1>.)e*t @ +?,s'o/=?+ @ 5abel11.)e*t @ +? /'ere t'eatername?+ @ )e*tBo*1.)e*t @ +?+, con"  cmd.E*ecuteon8uery("  5abel1.)e*t 6s!Bo*(+u-date record+"  )e*tBo*1.)e*t ++  )e*tBo*.)e*t ++  )e*tBo*=.)e*t ++

  End Sub

  Protected Sub Button=_Click(ByVal sender As Object, ByVal e As System.EentAr!s" #andles Button=.Click  cmd e/  System.0ata.SlClient.SlCommand(+delete %romt'eaterentry /'ere t'eatername?+ @ )e*tBo*1.)e*t @ +?+, con"  cmd.E*ecuteon8uery("  5abel1.)e*t 6s!Bo*(+0elete record+"  )e*tBo*1.)e*t ++  )e*tBo*.)e*t ++  )e*tBo*=.)e*t ++  End Sub

  Protected Sub Button_Click(ByVal sender As Object, ByVal e As System.EentAr!s" #andles Button.Click  &es-onse.&edirect(+rate entry.as-*+"  End SubEnd Class

RA$E E*$R

Partial Class 0e%ault  $n'erits System.3eb.4$.Pa!e  0im con As e/  System.0ata.SlClient.SlConnection

8/17/2019 65465465

15/32

8/17/2019 65465465

16/32

8/17/2019 65465465

17/32

1C

con.O-en("  $% $sPostBack ;alse )'en

  adt e/ System.0ata.SlClient.Sl0ataAda-ter(+select 2%rom moiesentry+, con"

  ds e/ System.0ata.0ataSet("  adt.;ill(ds, +moiesentry+"  0ro-0o/n5ist1.0ataSource ds  0ro-0o/n5ist1.0ata)e*t;ield +t'eater_name+  0ro-0o/n5ist1.0ataBind("  End $%

  End Sub

  Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EentAr!s" #andles Button1.Click  cmd e/  System.0ata.SlClient.SlCommand(+insert into

moiesentry alues(?+ @ 0ro-0o/n5ist1.Selected$tem.)e*t @+?,?+ @)e*tBo*.)e*t @ +?,?+ @ )e*tBo*=.)e*t @ +?,?+ @ )e*tBo*.)e*t @+?,?+ @ )e*tBo*.)e*t @ +?"+, con"  cmd.E*ecuteon8uery("  6s!Bo*(+record sae+"

  )e*tBo*.)e*t ++  )e*tBo*=.)e*t ++  )e*tBo*.)e*t ++  )e*tBo*.)e*t ++

  End Sub

  Protected Sub  0ro-0o/n5ist1_Selected$nde*C'an!ed(ByVal sender AsObject, ByVal e As System.EentAr!s" #andles 0ro-0o/n5ist1.Selected$nde*C'an!ed  cmd e/  System.0ata.SlClient.SlCommand(+select 2 %rommoiesentry +, con"  dtr cmd.E*ecute&eader("  3'ile (dtr.&ead(""  )e*tBo*.)e*t dtr.$tem(+moie_name+"  )e*tBo*=.)e*t dtr.$tem(+start_date+"  )e*tBo*.)e*t dtr.$tem(+end_date+"  )e*tBo*.)e*t dtr.$tem(+0iscri-tion+"  End 3'ile

  End Sub

  Protected Sub Button_Click(ByVal sender As Object, ByVal e As System.EentAr!s" #andles Button.Click  &es-onse.&edirect(+rate entry.as-*+"  End Sub

  Protected Sub Button_Click(ByVal sender As Object, ByVal e As System.EentAr!s" #andles Button.Click  &es-onse.&edirect(+ticket detail.as-*+"

8/17/2019 65465465

18/32

1D

End SubEnd Class

A%$ER +SER "!('*

Partial Class 0e%ault1

  $n'erits System.3eb.4$.Pa!e  0im con As  System.0ata.SlClient.SlConnection  0im cmd As  System.0ata.SlClient.SlCommand  0im dtr As  System.0ata.SlClient.Sl0ata&eader

  Protected Sub Pa!e_5oad(ByVal sender As Object, ByVal e As System.EentAr!s" #andles 6e.5oad  con e/  System.0ata.SlClient.SlConnection(+0ataSource.7S85E9P&ESS:Attac'0b;ilenameC:4ser $nstance)rue+"  con.O-en("  cmd e/  System.0ata.SlClient.SlCommand(+select 2 %romt'eaterentry+, con"

  dtr cmd.E*ecute&eader("  dtr.&ead("  0ro-0o/n5ist1.0ataSource dtr  0ro-0o/n5ist1.0ata)e*t;ield +t'eatername+  0ro-0o/n5ist1.0ataBind("  0ro-0o/n5ist1.0ataSource dtr  0ro-0o/n5ist1.0ata)e*t;ield +s'o/+  0ro-0o/n5ist1.0ataBind("

  0ro-0o/n5ist1.0ataSource dtr  0ro-0o/n5ist1.0ata)e*t;ield +moies name+  0ro-0o/n5ist1.0ataBind("  dtr.Close("

  cmd e/  System.0ata.SlClient.SlCommand(+select 2 %romrate_entry+, con"  dtr cmd.E*ecute&eader("  dtr.&ead("  0ro-0o/n5ist.0ataSource dtr  0ro-0o/n5ist.0ata)e*t;ield +amount+  0ro-0o/n5ist.0ataBind("  dtr.Close("  End Sub

  Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EentAr!s" #andles Button1.Click  &es-onse.&edirect(+-ayment detail.as-*+"

  End Sub  Public ;unction run(" As $nte!er  0im r As e/ &andom  &eturn r.e*t(1>>, 1>>>"  End ;unction

  Protected Sub Button=_Click(ByVal sender As Object, ByVal e As System.EentAr!s" #andles Button=.Click  0im s As $nte!er  s run("  5abel1>.)e*t Conert.)oStrin!(s"

8/17/2019 65465465

19/32

1E

Button=.Enabled ;alse  Button1.Enabled )rue

  End Sub

  Protected Sub Button_Click(ByVal sender As Object, ByVal e As System.EentAr!s" #andles Button.Click  &es-onse.&edirect(+'ome.as-*+"  End SubEnd class

PAYMENT DETAIL

Partial Class 0e%ault1>  $n'erits System.3eb.4$.Pa!e  0im con As e/  System.0ata.SlClient.SlConnection

  0im cmd As e/  System.0ata.SlClient.SlCommand  0im dtr As  System.0ata.SlClient.Sl0ata&eader

  Protected Sub Pa!e_5oad(ByVal sender As Object, ByVal e As System.EentAr!s" #andles 6e.5oad  con e/  System.0ata.SlClient.SlConnection(+0ataSource.7S85E9P&ESS:Attac'0b;ilenameC:4ser $nstance)rue+"  con.O-en("  cmd e/  System.0ata.SlClient.SlCommand(+select 2 %romrate_entry+, con"  dtr cmd.E*ecute&eader("  dtr.&ead("

  0ro-0o/n5ist1.0ataSource dtr  0ro-0o/n5ist1.0ata)e*t;ield +amount+  0ro-0o/n5ist1.0ataBind("  dtr.Close("  End Sub

  Protected Sub Button_Click(ByVal sender As Object, ByVal e As System.EentAr!s" #andles Button.Click  cmd e/  System.0ata.SlClient.SlCommand(+insert into-aymentdetail alues(?+ @ )e*tBo*1.)e*t @ +?,?+ @ )e*tBo*.)e*t @+?,?+ @ 0ro-0o/n5ist1.Selected$tem.)e*t @+?"+, con"  cmd.E*ecuteon8uery("  6s!Bo*(+record sae+"

  )e*tBo*1.)e*t ++  )e*tBo*.)e*t ++

  End Sub

  Protected Sub Button_Click(ByVal sender As Object, ByVal e As System.EentAr!s" #andles Button.Click  &es-onse.&edirect(+'ome.as-*+"  End Sub

8/17/2019 65465465

20/32

8/17/2019 65465465

21/32

1

$ask $esting:-

The first step in the testing of real time software is to test each task

independently. That is white bo# testing and black bo# testing are designed and

e#ecuted for each task. +ach task is e#ecuted independently during these tests.

Task testing uncovers error in logic and function but not timing or behavioral.

  1eha2ioral $esting:-

;sing system models created with 0!+ tools, it is possible to simulate the

 behavioral of a real3time system and e#amine its behavioral as a conse$uence of

e#ternal events. These analysis activities can serve as the basic for the design of

test case that is conducted when the real time software has been built. ;sing a

techni$ue that is similar to e$uivalent partitioning, events *e.g. interrupts,

control signals- are categori(ed for testing. 5or e#ample, events for the

 photocopier might be user interrupts *e.g. reset counter-, mechanical interrupts

*e.g., paper "ammed-, system interrupts *e.g., toner low-, and failure mode *e.g.,

roller overhead-. +ach of these events tested individually and the behavioral of

the e#ecutable system is e#amined to detect errors that occur as a conse$uence

of processing associated with these events. The behavior of system model and

as the e#ecutable software can be compared for performance.

8/17/2019 65465465

22/32

System $esting:-

!oftware and hardware are integrated and a full range of the system test are

conducted in an attempt to attempts to uncover error at the software < hardware

interface. Most real3time system process interrupts. The tester develops a list of

all possible interrupts and the processing that occurs as a conse$uence of the

interrupts. Tests are then designed to asses the following system characteristics/

0re interrupts priorities properly assigned and properly handle

Is processing for each interrupts handled correctly

oes the performance of each interrupts3handling procedure conform to

re$uirements

oes a high volume of interrupts arriving at critical times create problem in

5unction of performance

  3 &hite 1o $esting

It is also called glass bo# testing. It is a test case design method that uses the

control structure of the procedural design to derive test cases. In this all

statement in the program has been e#ecuted at least once during testing that all

logical conditions have been e#ercised. ;sing white bo# testing methods ,

software engineer can derive test cases that

9uarantee that all independent paths within a module have been e#ercised at

least once.

+#ercise all loops at their boundaries and within their operational bounds.

+#ercise all logical decision on their true and false sides.

8/17/2019 65465465

23/32

2

+#ercise internal data structure to assure their validity.

Basic path testing, a white bo# techni$ue, makes use of program graphs to drive

the set of linearly independent tests that will insure coverage. onditional and

data flow testing further e#ercise program logic, and loop testing complements

other white bo# techni$ue by providing a procedure for e#ercising loops of

varying degrees of comple#ity.

    1lack 1o $esting:-

It focuses on the functional re$uirements of the software i.e. black bo# testing

enables the software engineer to derive sets of input condition that will fully

e#ercise all functional re$uirements for a program. Black bo# Testing is not

alternative to white bo# testing. ather, it is a complementary approach that is

likely to uncover different class errors than white bo# testing.

. Black bo# Testing attempts to find errors in the following categories/3

I. Incorrect or missing function.

II. Interface error.

III. +rrors in the data structure or e#ternal database.

IA. )erformance error.

A. Initiali(ation and termination errors.

The testing process which we have followed for our software is black bo#

testing. In this type of testing we test the software looking it as a black bo#

testing without considering the internal details. 0 re$uired set of inputs are to

8/17/2019 65465465

24/32

8

 be supplied depending upon the software and we get our desired outputs.

In the testing phase of our software we have followed the approach where testing is

done in step/3

5irst we have tested all the function individually by e#ecuting then with the

re$uired inputs. If these functions are called by some other functions then it is

checked that the functions returning the correct value, then it is checked that

these ob"ects are created in the desired format. %e had to test the functions by

making changes in the code itself so that their returning value can be printed,

giving us the idea about their being correct. This is approach is time consuming

 but the functionality of each and every function can be best tested using it. The

function is also tested for its synta# and if some syntactical errors was present

then it was also removed and the function was made correct this is called

testing.

 

'nstallation:-To install the network management software on your computer network. !ome

follows the instructions of step to step/3

Insert the setup in 3rive of a computer and double click the setup.

Install the software by setup.

8/17/2019 65465465

25/32

=

5ollow the step to install the software.

 

%easi5ility:-

5easibility of pro"ect can pro"ect can be e#plained in two terms below/

$echnical %easi5ility:-

7ur pro"ect is technically feasible, as we have taken visual basic as our front end.

0dvantages of language are achieved as/3

9ood interface for user.

0llow changes as when re$uired.

It is rapid action development tool, which makes processing fast.

oding make technical processing easy.

AB is event driven which means use is in control of application.

AB is infinitely e#tensible through the use of 0ctive3J control.

ynamically linked libraries and add3ins.

Economical %easi5ility:-

1. Before creation of this pro"ect all the database and function were

managed

manually by persons but after creation there is a need of "ust a single

operator

for complete management, which makes it economically feasible.

. 7ur pro"ect is $uite affordable in term of using of any level and provides

complete functionality as desired.

2. )ro"ect can be also being called feasible economically in terms of

convenience.

0s booking can be phone dialing.

8/17/2019 65465465

26/32

>

)ethodology Adopted

To solve the actual problem in an agency setting, software engineer or a team of

engineers must incorporate a development strategy encompasses the process

method and tool and generic phase. This strategy is often referred to as a

 process model or a software engineering paradigm. 0 process model for

software engineering is chosen base on the nature of the pro"ect and application,

the methods and tools to used, and the controls and deliverables that are re$uired.

0ll software development can be categori(ed as a problem solving loop in

which four distinct stages are encounters. !tatus $uo &represents the current

states of affairs'K problem definition identifies the specific problem to be solveK

technical development solve the problem through the application of some

technology, and the solution integration delivers the result those who re$uested

the solution in the place.

There is a verity of different process model for software engineering. +ach

represents attempts to bring order to an inherently chaotic activity it is

important to remember that each of model of the models has been categories.

Pro5lem definition

  Stat0s

60o$echnical

De2elopments

  Sol0tion

'ntegration

8/17/2019 65465465

27/32

C

"inear se/0ential model/3

!ome linear se$uential some time called classic life cycle waterfall model. The

linear se$uential model suggests a systemic se$uential approach to software

development that begins system at the level and progresses through analysis,

design, coding, testing and support. Below figure illustrate the linear se$uential

model for the software engineering the linear se$uential model encompasses

following activities/3

 

System 7 'nformation engineering and

modeling :

Because a software is a part time of a large system, were beginning by

established re$uirement for all system element the allocating some subset of

these re$uirements to software. This system view essential when software must

Interact with other element such as hardware, people and database. !ystem

engineering and analysis encompasses re$uirements gathering at the system

level with a small amount of top level design analysis.

 

Software re/0irement analysis :-

The re$uirements gathering process is intensified and focused specifically on

software. To understand the nature of program to be built, The software

engineer must understand the information domain for the software as well as

re$uire function, behavior, performance, and interface.

8/17/2019 65465465

28/32

8/17/2019 65465465

29/32

E

5ig/ linear se$uential model

SEC+R'$ !% $,E SS$E):-

omputer is a versatile instruction with almost enormous capacity computation at

an unimaginable speed. The end user is concerned about security along with

increased dependence on the computer. In system development, the pro"ect

manager must consider measures for marinating data and controlling secret at

all time. This involves built in hardware feature, programs procedures to protect

andidate system from unauthori(ed access. The level of protection depends on

the sensitivity of the data, the reliability of the user, the comple#ity of the

 system. 0 well designed system includes control procedure to provide physical

)rotection *hardware security- and restrict system access *database security-.

Application sec0rity:In our pro"ect, going password an application security. In our pro"ect, if the user

type wrong password and user name then he

8/17/2019 65465465

30/32

2F

enter any type.

$ransaction Sec0rity:-In this pro"ect, several kinds of transaction securities have been provided such as/ 3

0. %e cannot enter the wrong value

8/17/2019 65465465

31/32

21

Software sec0rity:-

!oftware security may need striker control on person an access to the

 processing center, the data file storage and the programs file. 0 copy of all

 program May be file stored away from the computer installation as a security

measure.

 

"imitation:-

7ur pro"ect has the following limitations /

• In this system the customer will not select seat number .The authori(ed

 people in this process will be employee who works at the cinema.

• In this system the customer can book the tickets only for the present day.

0dvanced booking upcoming movies is not be included but can be included

later.

• 0lso, a printing system will not be in this pro"ect. In future ,a ticket printing.

• The customer who has booked the ticket must reach the multiple# 2F minutes

 prior to the show time or else ticket will get cancelled.

 

C!*C"+S'!*

This pro"ect is facilitating to its best to a particular &Music collection of shop

Information'. I have tried my best to do each and every aspect of the &Music

collection of

shop Information'. I go to survey to the entire the bike agency. This was a great

activity

which was performed by me my pro"ect provides me really a grate thing which I

have

8/17/2019 65465465

32/32

2

achieve in my study period.

  1'1"'!(RAP,

#is0al 1asic 8net  G+55+@ .!H0)I!7

#18net 1lack 1ook   !teven hol(ner 

'ntrod0ction to #18net  obert ". oberge

Application De2elopment  obert ". oberge

  +sing #182et

College notes