Download P-0077--Online Cinema Ticket Booking System PDF

TitleP-0077--Online Cinema Ticket Booking System
File Size2.5 MB
Total Pages74
Table of Contents
                            LANGUAGES USED
ASP.NET:
COMPARISON OF ASP AND ASP.NET:
Client server means that SQL Server is designed to store data in the central location (the server) and deliver it on demand to numerous other locations (the client). SQL Server is also a Relational Database Management System (RDBMS).
INTRODUCTION:
Operational Feasibility
DATABASE DESIGN:
Data Integration
Data Integrity
Data Independence
The databases are implemented using a DBMS package. Each particular DBMS has unique characteristics and general techniques for Database Design.
In database design, several views of data must be considered along with the persons who use them. In addition to data structuring, where relationships are reflected between and within entities, we need to identify the application program’s logical views of data within an overall logical data structure. The logical view is what the data look like, regardless of how they are stored. The physical view is the way data exist in physical storage. It deals with hoe data are stored, accessed, or related to other data in storage.
The schema is the view that helps the DBMS decide in storage act upon as requested by the application program.
CODE DESIGN
The ability to interrupt codes, evaluate coding schemes and devices new or improved codes are important skills for a system analyst. Common types of codes are:
A sequence code has no relation to the characteristics of an item. Here a dictionary is required. The data is arranged alphabetically and numbered sequentially. When a new data item is added it is given the next sequence number. The advantage of this code is that it has the ability touched with an unlimited number of digits.
SIGNIFICANT DIGIT CODE:
Here, the item are specified by the user of letter and number combinations,
SELF CHECKING CODE:
VALIDATION CHECKS:
Sometimes incorrect data can actually cause a computer system to stop work temporarily. This is a particular problem in batch processing systems when data may be processed overnights. If incorrect data stops a batch processing systems for working then a whole night processing time may be lost.
People who develop computer systems go to a lot of trouble to make it difficult for incorrect data to be entered. The two main techniques used for this purpose are:
Verification:
Methods of Verification:
On-Screen prompts: After a user has entered some data it is redisplayed on the screen. The user is prompted to read the data and confirm that it has been entered correctly. If the user has entered any data incorrectly he should response that the data is inaccurate and retypes the incorrect parts.
A validation check is an automatic check made by computer to ensure that any data entered into the computer is sensible. A validation check does not make sure that data has been entered correctly. It only ensures that data is sensible. For this reason validation checks are not usually as effective as verification checks. They can however be carried out automatically by the computer and therefore require less work by the computer operators making them cheaper to use.
Methods of validation:
Presence Checks: checks that data has been entered into the field and that it has not been left blank, e.g. checks that Project ID is always entered into each record in a database of project details.
Length Checks: checks that an entered value, e.g. Project ID is no longer than a particular number of characters.
DATA DICTIONARY:
A data dictionary has many advantages. The most obvious is documentation; it is valuable reference in any organization. Another advantage is improving analyst/user communication by establishing consistent definition of various elements, terms and procedures. During implementation, it serves as a common base against which programmers who are working on the system compare data description. Also control information maintained for each data element is cross referenced in the data dictionary. E.g. program that use a given data element are cross referenced in a data dictionary, which makes it easy to identify them and make any necessary changes. Finally, a data dictionary is an important step in building a database. Most database management system has a data dictionary as a standard feature.
INPUT DESIGN:
The input design is the link between the information system and the user. It comprises developing specification and procedure for data preparation and those steps that are necessary to put transaction data into a usable form for processing data entry. The activity of putting data into the computer for processing can be achieved by instructing the computer to read data from a written or printed document or it can occur by having people key data directly into the system. The design of inputs focuses on controlling the amount of inputs required, controlling errors, avoiding delay, avoiding extra steps and keeping the process simple.
SYSTEM TESTING
INTRODUCTION:
System testing was conducted in order to detect errors and for comparing then the final system with the requirement specification reports, i.e. whether the system meets requirements. During testing the software was executed with the set of test cases and the output of programs for the test cases was evaluated to determine if the program is performing as it was expected to.
Testing presents an interesting challenge for the software engineers attempt to build software from an abstract concept to an acceptable implementation. In testing engineer create a series of test cases that occurs when errors are uncovered. Testing is the process of executing a program for finding errors. A good test is one that has the high probability of finding an uncovered error. A successful error is one that uncovers undiscovered errors.
The term error is used to refer the difference between actual output of the software and the current output. Fault is a condition that causes the software to fail to perform its required function. Software reliability is defined as a required function. Software reliability is defined as the probability that the software will not undergoes failures for a specified times under specified condition. Failure is the inability of a system or a component to perform a required function according to its specification. Different levels of testing were employed for software to make it error free, fault free and reliable.
Unit Testing:
Unit testing was conducted first. Different modules of the software were tested against the specifications produced during design of the modules. Verification of the code produced during the coding phase was done. Each module was tested separately.
Unit testing focuses verification effort on the smallest unit of software design module. This uncovers errors within the boundary of a module. Unit testing is actually White box testing both the external things as well as the internal codes are tested. In testing, the interfaces are tested in order to ensure the proper flow of data in and out of the module. The boundary testing is done to ensure that the module keeps the limit of it. All independent paths are tested to ensure that all statements are tested at least once. At last the error path is also tested.
Unit testing comprises the set of tests performed by an individual programmer prior to integration of the unit into a larger system. There are four categories of test that can be performed on a program unit
Functional Unit
Stress Unit
Then system testing was conducted. Here the entire software system was tested.
System testing includes the thorough testing of the product. System testing is actually a series of different tests whose primary purpose is to fully exercise the computer based system. The tests are recovery testing: this checks the recovery of the system when failure occurs. This is to ensure that there are recovery procedures for error occurrences.
Prepare test plan
Prepare test data for program testing
Plan user testing
Prepare job performance aids
Prepare operational documents
                        
Document Text Contents
Page 1

Online Cinema Ticket Booking System

Submitted in Fulfillment of the requirement for the
award of the degree of

Bachelor of Technology

In

Computer Engineering

By

SHIVIN BAWEJA(1106733)

DEPARTMENT OF COMPUTER ENGINEERING

M.M.Engineering College, Mullana, Ambala, Haryana
Kurukshetra University, Kurukshetra, Haryana, India

December 2009

Page 2

Table Of Contents

Page 37

Unit Testing:

Unit testing was conducted first. Different modules of the software were tested

against the specifications produced during design of the modules. Verification

of the code produced during the coding phase was done. Each module was

tested separately.

Unit testing focuses verification effort on the smallest unit of software design

module. This uncovers errors within the boundary of a module. Unit testing is

actually White box testing both the external things as well as the internal

codes are tested. In testing, the interfaces are tested in order to ensure the

proper flow of data in and out of the module. The boundary testing is done to

ensure that the module keeps the limit of it. All independent paths are tested

to ensure that all statements are tested at least once. At last the error path is

also tested.

Unit testing comprises the set of tests performed by an individual programmer

prior to integration of the unit into a larger system. There are four categories

of test that can be performed on a program unit

 Functional Unit

 Performance Unit

 Stress Unit

 Structure Unit

System Testing:

Then system testing was conducted. Here the entire software system was

tested.

The reference document used for this process was requirement document and the

goal was to see if the software meets its requirements.

Page 38

System testing includes the thorough testing of the product. System testing is

actually a series of different tests whose primary purpose is to fully exercise

the computer based system. The tests are recovery testing: this checks the

recovery of the system when failure occurs. This is to ensure that there are

recovery procedures for error occurrences.

System testing involves unit testing, integration testing, acceptance testing. Careful

planning and scheduling are required to ensure that modules will be available for

integration into the evolving software product when needed. A test plan has the

following steps:

 Prepare test plan

 Specify conditions for user acceptance testing

 Prepare test data for program testing

 Prepare test data for transaction path testing

 Plan user testing

 Compile/Assemble program

 Prepare job performance aids

 Prepare operational documents

Objectives of testing.

First of all objectives should be clear.

 Testing as a process of executing a program with the intent of finding errors.

 To perform testing, test cases are designed. A test case is a particular made up of

artificial situation upon which a program is exposed so as to find errors. So a good

test case is one that finds undiscovered errors.

 If testing is done properly, it uncovers errors and after fixing those errors we have

software that is being developed according to specifications.

Page 73

6. ASP.NET by Wrox Publications

7. ASP.NET 2.0 Unleashed

8. Comdex ASP.NET

Similer Documents