Professional Documents
Culture Documents
The project is very flexible and it can be modified if the need arises. I
hope the user will find this project work quite pleasing in its output as
general sample designing has been done to enhance the view and simple
programming statement and commands have been made use of, so that
the user had no problem in understanding the listing of the project. Files
have been used to create a systematic medium of data storage and
retrieval.
I am sure that reader will like this effort and so, I wished him/her by
hearts to ahead and turn this page.
1|Page
OBJECTIVES
Airways has a number of reservation offices in each city where the flights operate. Each
reservation office has a number of reservation counters to handle reservations and
cancellations. Each counter has a counter assistant who is responsible for making
reservations or cancellations. The main objective of this project to performed
reservation, cancellation and report.
In concerned to reservations, the following activities are done.
Accepts the date, sector, and class of travel from the person and checks for the
availability of a seat in the Reservation file.
Confirms the details with the prospective passenger and accepts the remaining
details.
Update the seat availability status in the reservation file and adds the passenger
details to the file. The passenger is assigned a unique Passenger Name Request
(PNR) number,
Collects the fare amount.
Update the Daily Collection file with the fare amount.
In concerned to cancellation, the following activities is done
Retrieves the details from the file using the PNR number.
Verifies the details of the ticket and computes the refund amount.
Updates the seat availability status in the reservations file and marks the
corresponding details of the file.
Makes the refund and prints the refund receipt.
Files the receipt along with the signature of the passenger .
Updates the Daily Collection file.
2|Page
And Reports are generated as:-
Print the confirmed and wait-listed passenger list of flights departing .
Print the daily collection summary report.
It also generate view rates for different sector & view flight schedules for a
specific period
Show status of ticket with given PNR number.
Report on availability of flight & seats on desired date.
3|Page
SYSTEM ANALYSIS
SYSTEM ANALYSIS
Introduction of User
Definition of System
Identification of Need
Preliminary Investigation
4|Page
SYSTEM ANALYSIS
The most critical phase of managing system projects is planning to launch a system
investigation, we need plan detailing the steps to be taken, the people to be questioned
and they out come expected. The initial investigation has the objective of determining
whether the users request has potential merit. The major steps are defining user
requirements. When the initial investigation is completed. The user receives a proposal
summarizing the finding the recommendation of the analyst.
A key part of feasibility analysis is gathering information about the present system.
The analyst knows what information to gather, where to find it, how to collect it and
5|Page
what to make of it. The proper use of tools for gathering information is the key to
successful analysis. The tools are the traditional interview, questionnaire, and on-site
observation. We need to know, for example how to structure an interview, what makes
up a questionnaire, and what to look for on-site observations. These tools when learned
help analysis assess the effectiveness of the present system and provide the groundwork
for recommending a candidate system.
Identification of need
The system need accomplish the following functions:
The system should allow the counter assistants to handle ticketing and refunds.
While accepting reservation data, all necessary validations should be performed.
For example, the system should check whether a flight operates on the date of
travel specified by the passenger. It should also check the seat availability status.
After all data has accepted, the system should print the ticket. It should also store
the passenger details, update the daily collections, and update the seat plan.
In case of cancellation, the system should accept the PNR number from the user,
validate the PNR number and update the cancellation flag for the passenger. The
system should then print the refund receipt. It should also update the daily
collections to reflect the refund amount. The status of overbooked and wait-listed
tickets should be changed whenever a confirmed ticket is cancelled.
The system should generate the following reports:
In addition, the new system should provide facilitate passengers to perform the following
tasks:
Check the waiting list status.
6|Page
View rates for different sectors.
View flight schedules for a specific period. This module should be developed as
an affiliate program that can be easily integrated with various Web sites.
FEASIBILITY STUDY
The main objective of the preliminary analysis is to identify the problem, evaluate the
system concept of feasibility, and perform the economic and technical analyses
perform the cost benefit analysis. After the clarification analysis the solution
proposed it is checked that it is practical to implement that solution. This is done
through the feasibility study. It is checked for various aspects whether the proposed
solution is technically or economically feasible or not. On the basis if which it has
been categorized into four classes viz
1.) Technical
2.) Economic
3.) Operational
The outcome of the preliminary analysis should be clear so that an alternate way to
do the job can be found out?
1. Technical Feasibility:
During the technical feasibility studies following issues are taken into consideration
7|Page
As in our proposed system our team has technically trained manpower with
knowledge of developing the system. We are going to use web technology in our
system, which is readily available. Software to be used is also available easily.
2. Economic Feasibility:
For any system if the expected benefits equal or exceed the expected costs, the
system can be judged to be economically feasible. In economic feasibility, cost
benefit analysis is done in which expected costs and benefits are evaluated.
As in our institute the hardware and software required for this type of system
is already available so economically our project is feasible.
3. Operational Feasibility
The staff of the company (client) is used to the computer. They will only be given
training about the proposed system to make efficient use of it.
This feasibility study is carried out by a small group of people who are familiar with
information system techniques, who understand the part of the system that are
relevant to the project and are skilled in system analysis and design process.
Considering the above three feasibility we can say that the system is feasible and
ahead for analysis of the system.
8|Page
SOFTWARE ENGINEERING PARADISM
In the software principle we are using the incremental model (evolutionary software
process model). The incremental model combines elements of the linear sequential
10 | P a g e
PLATFORM USED
Hardware Requirement
2. Color Monitor
3. Keyboard
6. Speakers
11 | P a g e
Software Requirement
12 | P a g e
PROJECT ANALYSIS
Object Oriented Programming is a method of programming that seeks to mimic the way
we form models of the world. To cope with the complexities of life, we have evolved a
wonderful capacity to generalize, classify and generate abstractions. Almost every noun
behavioral traits.
The entire basis of Object Oriented Programming, infect is defining the Object in Object
Oriented Programming. Object is a unit that combines both code and data together. And
an object is an instance of a class. Class is a type of data structure defined to hold both
Object Oriented Programming also allows you to design and implement your application
more quickly than traditional approaches. Object Oriented Programming also makes
code easier to maintain so that you can refine the implementation without causing major
problems.
programming has taken the best ideas of structured programming and has combined
them with several powerful concepts that allow you to organize your programs more
13 | P a g e
a problem into its constituent parts. Each component becomes a self-contained object
that contains its own instructions and data related to that object. Through this process,
Encapsulation
As you probably know, all programs are composed of two fundamental elements:
program statements (code) and data. Code is that part of a program that performs
programming mechanism that binds together code and the data it manipulates,
and that keeps both safe from outside interference and misuse.
In an object-oriented language, code and data may be bound together in such a way
that a self-contained black box is created. Within the box are all necessary data and
code. When code and data are linked together in this fashion, an object is created.
Within an object, the code, data, or both may be private to that object or public.
Private code or data is known to, and accessible only by, another part of the object.
That is, private code or data may not be accessed by a piece of the program that exists
outside the object. When code or data is public, other parts of your program may access
it, even though it is defined within an object. Typically, the public parts of an object
are used to provide a controlled interface to the private elements of the object.
Polymorphism
14 | P a g e
Polymorphism (from the Greek, meaning “many forms”) is the quality that allows one
interface to be used for a general class of actions. The specific action is determined by
the exact nature of the situation. A simple example of polymorphism is found in the
Steering wheel of an automobile. The steering wheel (i.e., the interface) is the same no
matter what type of actual steering mechanism is used. That is, the steering wheel works
the same whether your car has manual steering, power steering, or rack-and-pinion
steering. Therefore, once you know how to operate the steering wheel, you can drive
any type of car. The same principle can also apply to programming. For example,
consider
a stack (which is a first-in, last-out list). You might have a program that requires three
different types of stacks. One stack is used for integer values, one for floating-point
values, and one for characters. In this case, the algorithm that implements each stack
is the same, even though the data being stored differs. In a non-object-oriented language,
you would be required to create three different sets of stack routines, calling each set
by a different name, with each set having its own interface. However, because of
polymorphism, in C++ you can create one general set of stack routines (one interface)
that works for all three specific situations. This way, once you know how to use one
“one interface, multiple methods.” This means that it is possible to design a generic
15 | P a g e
allowing the same interface to be used to specify a general class of action. It is the
compiler’s job to select the specific action (i.e., method) as it applies to each situation.
You, the programmer, don’t need to do this selection manually. You need only
was, of course, supported at run time. However, C++ is a compiled language. Therefore,
Inheritance
Inheritance is the process by which one object can acquire the properties of another
object. The reason this is important is that it supports the concept of hierarchical
hierarchical (i.e., top-down) classifications. For example, a Red Delicious apple is part
of the classification apple, which in turn is part of the fruit class, which is under the
larger class food. That is, the food class possesses certain qualities (edible, nutritious,
etc.) that also apply, logically, to its fruit subclass. In addition to these qualities, the
fruit class has specific characteristics (juicy, sweet, etc.) that distinguish it from other
food. The apple class defines those qualities specific to an apple (grows on trees, not
tropical, etc.). A Red Delicious apple would, in turn, inherit all the qualities of all
preceding classes, and would define only those qualities that make it unique.
Without the use of hierarchies, each object would have to explicitly define all of
its characteristics. However, using inheritance, an object needs to define only those
qualities that make it unique within its class. It can inherit its general attributes from
16 | P a g e
its parent. Thus, it is the inheritance mechanism that makes it possible for one object
As you will see as you progress through this book, many of the features of C++ exist
however, that you can use C++ to write any type of program, using any type of
approach. The fact that C++ supports object-oriented programming does not mean
that you can only write object-oriented programs. As with its predecessor, C, one of
17 | P a g e
RISK ANALYSIS
customer, and requirements problems and their impact on software. All the
verification, and maintenance problems. All the above factors have been
analyzed.
Business Risk: (1) Software is developed keeping in mind that there is demand in
custom, so that to avoid the market risk. (2) Software is designed to fit into the
overall business strategy for the custom department, to avoid the strategic risk.
(3) The software is easily understandable by the sales person’s team, so that
they could know much about the product working and sell in the market. (4) It
has the strong management support, and not likely to change in the management
people to avoid the management risk. (5) Software fits the budget and there is no
budget risk.
18 | P a g e
OJBECT ORIENTED DEVELOPMENT
An object-oriented system draws upon class definitions that are derived from the
analysis model. Some of these definitions will have to be built from scratch, but
many others may be reused it appropriate design patterns are recognized. Object
Oriented Design establishes a design blueprint that enables a software engineer to
define the Object Oriented architecture in a manner that maximized reuse, thereby
improving development speed and end-product quality.
The four layers of the Object Oriented design are:
The subsystem layer: It represents each of the subsystems that enable the software
to achieve its customer-defined requirements and to implement the technical
infrastructure that supports customer requirements, in the custom department.
The class and object layer: It contains the class hierarchies that enable the system
to be created using generalizations and increasingly more targeted specializations.
The message layer: It contains the design details that enable each object to
communicate with its collaborators. This layer establishes the external and inters
interfaces for the software.
The responsibilities layer: It contains the data structure and algorithmic design for
all attributes and operations for each object.
19 | P a g e
WORK FLOW THE PROJECT
User can view list of stations along with their code, charges for document and
non-document by selecting option 1 from the main menu.
User can book the courier by selecting option 2 from the main menu. Users
have to input details of courier, consignor and consignee, and data is saved in
the file – customer. at.
User can search for station information by giving station code, by selecting
option 3 from the main menu.
User can search and view customer details by selecting option 4 from the main
menu.
User can view daily booking status by selecting option 1 from the report menu.
User can view monthly booking status by selecting option 2 from the report
menu.
20 | P a g e
FEASIBILITY STUDY
21 | P a g e
TYPE OF FEASIBILITIES
1. Economic Feasibility
Economic analysis is the most frequently used technique for evaluating the
effectiveness of a proposed system. More commonly known as cost / benefit
analysis; in this procedure we determine the benefits and savings that are
expected from a proposed system and compare them with costs. We found the
benefits outweigh the costs; we take a decision to design and implement the
new proposed system.
2. Technical Feasibility
22 | P a g e
· Response time under certain conditions.
3. Operational Feasibility
23 | P a g e
· what new skills will be required? Do the existing staff members have these
skills?
4. Social feasibility
5. Management feasibility
24 | P a g e
It is a determination of whether a proposed project will be acceptable to
management. If management does not accept a project or gives a negligible
support to it, the analyst will tend to view the project as a non-feasible one.
6. Legal feasibility
7. Time feasibility
25 | P a g e
SYSTEM DESIGN
Introduction
System design provides the understandings and procedural details necessary for
implementing the system recommended in the system study. Emphasis is on the
translating the performance requirements into design specifications. The design has is a
transition from a user-oriented document (System proposal) to a document oriented to
the programmers or database personnel.
1) Logical Design
2) Physical Design
A data flow diagram shows the logical flow of the system. For a system it
describes the input (source), output (destination), FILE (data stores) and procedures (data
flows) all in a format that meets the user’s requirement. When analysis prepare the
logical system design, they specify the user needs at a level of detail that virtually
determines the information flow into an out of the system and the required data
resources. The logical design also specifies input forms and screen layouts.
The activities following logical design are the procedure followed in the physical
design e.g., producing programs, software, file and a working system. Design
specifications instruct the user about what the system should do.
26 | P a g e
another. The detailed specification for the new system was drawn on the bases of user’s
requirement data. The outputs inputs and databases are designed in this phase.
Output design is one of the most important features of the information system.
When the output is not of good quality the users will be averse to use the newly designed
system and may not use the system. There are many types of output, all of which can be
either highly useful or can be critical to the users, depending on the manner and degree
to which they are used.
Outputs from computer system are required primarily to communicate the results
of processing to users; they are also used to provide a permanent hard copy of these
results for later consultation. Various types of outputs required can be listed as below:
27 | P a g e
The End user, who will use the output.
When and how often output and their format is needed. While designing
output for project based Attendance Compilation System, the following
aspects of outputs designing were taken into consideration.
The outputs (i.e., well formatted table outputs in the screen itself) designed
are simple to read and interpret.
Format of each output was another important point taken into consideration.
Output media, for each output appropriate media is decided whether it will
be displayed on screen or will be taken to printer or both.
Other output design related specifications, i.e., how frequently the outputs
will be generated, how many pages or sheets approximately it will keep up,
what is its planned use and output distribution to users are also taken into
account.
These were a few major designing issues, which were taken into consideration,
while deciding the output specifications for the system. As direct beneficiary of reports is
the user community, they were consulted constantly at every level. Formats and screen
design for various reports were identified, taking into account the user requirements.
Before finalising these were given to users for any improvement and suggestions. End
users issues taken into consideration were Readability, Relevance and Acceptability.
Once all the output reports to be generated by HARS system were identified, they
were given to users for their acceptance. For prototyping various outputs, final outputs
models were created with dummy data, before they were finalized.
28 | P a g e
Output Sources:
Tabular contents
Graphic format
Using Icons
Output Definition:
Types of outputs
29 | P a g e
Data items
The name given to each data item should be recorded and its characteristics described
clearly in a standard form:
Number of characters
Input Design:
The input design is the link that ties the information system into the user’s world.
Input specifications describe the manner in which data enters the system for processing.
Input design features can ensure the reliability of the system and produce results from
accurate data, or they can result in the production of erroneous information.
Data entry, the activity of putting data into the computer processing.
30 | P a g e
Five objectives of design input focus on
Avoid delay
Input stages several activities have to be carried out as part of the overall input
process. They include some or all of the following.
Input Performa were designed, after a careful discussion with users. It was
attempted to cover all user requirements. Designed Performa were given to user for any
suggestion and final approval.
Various data items were identified and wherever necessary were recorded. As the
data concerning of HARS is voluminous in nature and number of case will grow
dynamically in future, proper care was taken for accuracy and consistency of data.
31 | P a g e
Input designs are aimed at reducing the chances of mistakes of errors. As the
human beings are prone to errors there is always a possibility of occurrence of chance of
errors. Adequate validation checks are incorporated to ensure error free data storage.
Some of the data validation checks applied are as following:
Wherever items are coded, input code is checked for it’s validly with respect
to several checks.
Utmost care has been taken to incorporate the validation at each stage of the
system. E.g. when entering records into employee information table for
employee, it is checked that whether the corresponding employee exists in
the employee information table etc.,
Enough messages and dialogue boxes are provided while design screen, which does guide user at
the time of any errors, or at time of entry. This feature provides a user-friendly interface to native
users. It can be emphasized that input deigns of HARS system is so designed that it ensures easy
and error free data entry mechanism. Once one is sure of input data the output formatting
becomes a routine work.
32 | P a g e
PROJECT DESIGN
Airways has a number of reservation offices in each city where the flights operate. Each
reservation office has a number of reservation counters to handle reservations and
cancellations. Each counter has a counter assistant who is responsible for making
reservations or cancellations. The procedure followed for performing reservations and
cancellations is given bellow.
Reservation
Reservations for a flight commence 30 days before the date of the flight. The procedure
for making reservations is given below. The procedure described below deals with the
provisional reservations the can be made through telephone conversation.
On receiving request for reservation from a person, the counter assistant performs the
following activities:
Accepts the date, sector, and class of travel from the person and checks for the
availability of a seat on the requested date. The details about the availability seats
and the seat plan are kept in the Reservation file.
Confirms the details with the prospective passenger and accepts the remaining
details. These details include the preferences such as a window or an aisle seat, a
smoking or a non-smoking zone, meal preferences such as vegetarian or non-
vegetarian, and special service requests (SSR), such as dietary and medical
considerations.
Update the seat availability status in the reservation file and adds the passenger
details to the file. The passenger is assigned a unique Passenger Name Request
(PNR) number, which is used to access ticket details for queries and cancellation.
33 | P a g e
Collects the fare amount.
Prints the ticket and gives it to the passenger.
Update the Daily Collection file with the fare amount.
Horizon Airways also provides for overbooked and wait-listed tickets for the economy
class. Overbooking is allowed for 10 seats per flight. For example, if the capacity of an
aircraft is 340 seats, booking are made for 350 seats, that is, 340 seats + 10 overbooked
tickets. If the number of bookings exceeds the capacity and overbooking, a wait-listed
ticket is issued to the passenger with his or her consent. An overbooked or wait-listed
passenger is accommodated on the flight depending on the availability of a seat when the
passenger checks in. A passenger who cannot be accommodated on a flight is given full
refund.
Cancellation
On receiving a cancellation request from a passenger the counter assistant performs the
following tasks:
Retrieves the details from the file using the PNR number.
Verifies the details of the ticket and computes the refund amount.
Updates the seat availability status in the reservations file and marks the
corresponding details of the file.
Makes the refund and prints the refund receipt.
Files the receipt along with the signature of the passenger.
Updates the Daily Collection file.
The amount of refund is calculated based on the ticket status and the date cancellation.
If the ticket is wait-listed or overbooked, full amount is refunded.
STATION
34 | P a g e
DATE
CUSTOMER
35 | P a g e
Modules in class CUSTOMER:
36 | P a g e
TABLE STRUCTURE
37 | P a g e
2. STATION.DAT (Stores all information
for Stations)
38 | P a g e
PROGRAM STRUCTURE
STATION
DATE
CUSTOMER
Modules in class STATION:
39 | P a g e
valid() : Function to check validity of the given
date.
40 | P a g e
FLOW CHART
41 | P a g e
START
Station Information
Booking
Search Station
Customer Record MENU
Reports
Edit Station
0. Quit
Enter your Choice :
Input Ch
If Y
1
Ch=1
If Y
2
Ch=2
If Y 3
Ch=3
N
N
Y If If Y 4
STOP Ch=0 Ch=4
N N
Y If N If Y 5
6 Ch=5
Ch=6
42 | P a g e
1
if Y
eof MENU
43 | P a g e
2
44 | P a g e
Input consinor, consinee and
courier information.
MENU
45 | P a g e
Input code no. of the station
if MENU
eof
if N
stcode = file.stcode
if Y
eof MENU
if
code = file.code N
If Y
R1
Ch=1
If Y
R2
Ch=2
If Y
Ch=0 MENU
R1
48 | P a g e
Read data from file.
if Y
eof 5
if N
date = booking date
R2
switch to next record
if N
month = booking month
Input Ch
50 | P a g e
If Y
E1
Ch=1
If Y
E2
Ch=2
If Y
Ch=3 E3
If Y
Ch=0 MENU
E1
51 | P a g e
Open file station.dat in append
mode.
write data in file.
E2
6
E3
54 | P a g e
ENTITY RELATIONSHIP DIAGRAM (ERD):
technique may well System in large part for the wide spread use of the E-R model.
55 | P a g e
Lines: which link attribute to entity set and entity set to relationship
sets
Entity-Relationship Diagram
The following diagram depicts various entities involved in the airline reservation
system the attributes of entities and the relationships between entities:
SSR
Seat Zone Aircraft Type First Class Seats available
Meal Status
Cancel Flag
Flight No. Dep. Time
Seat preference
Arr.Time
1
Travel Date
Business
First Name
Last Name
Operates in
56 | P a g e
1
Sector ID
SECTOR Week Day 2
Description
Week Day 1
Full descriptions of the system actually consist of a set of data flow diagram.
Specification:
57 | P a g e
Source or destination: External source or destinations of data
interact with the system. The terms source and sink are
system.
58 | P a g e
Data Flow Diagram
59 | P a g e
OUTPUT SCREEN
60 | P a g e
LOGIN PAGE OF
AIRLINES TICKET RESERVATION
61 | P a g e
62 | P a g e
Si NO. OF FLIGHTS
63 | P a g e
LIST OF THE FLIGHTS
64 | P a g e
PASSENGER RECORDS
65 | P a g e
LIST OF THE FLIGHTS
66 | P a g e
PASSENGERS INFORMATION
67 | P a g e
SOFTWARE TESTING & IMPLIMENTATION:
SOFTWARE TESTING:
The purpose of this document is to cover testing of Horizon Airways project from all
aspects i.e. from module wide testing to system integration testing.
Software testing is a process of executing a program with objective of finding an
error. Software quality should be a primary concern in software development efforts.
Software testing and evaluation are traditional method of checking software quality. It
consists of putting together various coded pieces of a design, testing them and correcting
the parts of the code or the design that is not correct. At this stage some errors are
introduced purposely to test whether the program will spot them.
Test summary document with test results (Quality Record) for each test case with
problems found during the test execution. After review of test summary document, it will
be decided if any test case is to be repeated or if the identified problem should be
converted into “a defect” to be fixed in subsequent release of product.
Data entry:
68 | P a g e
A strategy for software testing may also be viewed in the context of spiral. Unit testing
begins at the vertex of the spiral and concentrates on each unit of the software as
implemented in source code. Testing progresses the moving outward along the spiral to
integrations testing. Where the focus is on design and the and the construction of the
software architecture. Taking another turn outward on the spiral, we encounter validation
testing, where requirements established as part of software requirements analysis are
validated against the software that has been constructed. Finally, arrive at system testing,
where the software and other system elements are tested as a whole. Here I will specify
each testing but the outcome of the testing and reports is not included because they are
very large and I have to give Project- Report in limited page.
Unit testing: In Unit testing module interface, local data structures. Boundary
conditions, independent paths, error handling paths are tested.
Module interface is tested to ensure that information properly flows into and our of the
program unit under test. The local data is structure is examined to ensure that data stored
temporarily maintained its integrity during all steps in an algorithm’s execution.
Boundary conditions are tested to ensure that the module operates properly at boundaries
established to limit or restrict processing. All independent paths through the control
structure are exercised to ensure that all statements in a module have been executed at
lest once. And finally, all error handling paths are tested.
Thus the unit testing is done after code development, reviewed, and verified for correct
syntax and in unit testing we execute each module one by one and prepare a report of
result.
Integration technique:
Integration testing is a systematic technique for constructing the program structure while
conducting tests to uncover errors associated with interfacing. The objective is to take
69 | P a g e
unit tested modules and build a program structure that has been dictated by design. Their
are three type of integration testing, each are discussed below.
BOTTOM OF INTEGERATION:
This technique begins construction and testing with atomic modules. Because modules
are integrated from the bottom up, processing required for module subordinate to a given
level’s always available and the need for stubs are eliminated.
REGRESSION TESTING:
This technique is the activity that help to ensure that changes during the testing do not
introduce unintended behavior or additional errors.
Validation testing:
Validation succeeds when software functions in a manner that can be reasonably
expected by the customer. There are two types of validation testing these are discussed
below.
ALPHA TESTING:
The alpha tests are conducted at the developer’s site by a customer. The software is used
in a natural setting with the developer. Alpha tests are conducted in a controlled
environment.
BETA TESTING:
70 | P a g e
The beta tests are conducted at one or more customer sites by the end use of the
software. Unlike, the alpha testing, the developer is generally not present. Therefore, the
beta test is a “live” application of the software in an environment that cannot be
controlled by the developer. The customer records all problems that are encountered
during beta testing and reports these to the developer at regular intervals. As a results of
problems reported during beta test. The software developer makes modifications and
then prepares for release of the software product to the entire customer base.
System testing:
It is a series of different test whose primary purpose is to fully exercise the computer-
based system. These are discussed below:
RECOVERY TESTING:
It the system tests that forces the software to fail in a variety of ways and verifies that
recovery is properly performed.
SECURITY TESTING:
It attempts to verify that protection mechanisms built into a system will in fact protect, it
from improper penetration.
STRESS TESTING:
It executes a system in a manner that demands resources in abnormal quantity,
Frequency, or volume.
PERFORMANCE TESTING:
It is designed to test run-time performance of software within the context of an integrated
system. It occurs throughout all steps in the testing process.
71 | P a g e
TESTING METHODOLOGIES
GUI Verification
Consistency of GUIs
Database Script Testing
Compatibility Testing
72 | P a g e
IMPLEMENTATION
IMPLEMENTATION PLAN:
Implementation follows the forms to the detailed design stage. This effect of the
user department and system designer in getting the new steps in operation.
The following steps are performed during implementation:
1) System Testing: It is tested and ensured that the different modules are working
correctly individually and as a whole.
2) Review and Maintenance: Once the system becomes operational, it would be
examined to see if it has met its objective.
The system is reviewed and maintained periodically for the following reasons:
To deal with unforeseen problems arising in the operation i.e. programs may need
to be dealt with unforeseen circumstances.
To confirm that the planning objects have been met and if not work to achieve so.
To ensure that the system is able to cope with changing requirements.
73 | P a g e
IMPLEMNTATION PROCEDURE:
The users in the organization are familiar with the basics of computers but will not be aware
with working of the new system. A training program will be conducted for three days to guide
the user about the new system. After the completion of the training program actual
implementation will start as follows:-
A. Pilot run of system.
B. Parallel run of system.
C. Change over of the system.
Pilot Run of System:
In this phase historical data will be entered into the system as test data and the output of the
system will be checked against the historical reports.
Parallel Run of System:
In this phase both the systems will be run in parallel form for about two to three months and the
results of both will be checked manually. After the completion of the time period, system will be
handed over to the management.
Change Over of the System:
This is the last phase of the implementation procedure. In this phase all the data will be
entered into the system by the user and the management will discontinue the manual
system.
74 | P a g e
SYSTEM SECURITY MEASURES
To do an adequate job on security, a systems analyst must analyze the risk, exposure, and costs
and specify measures such as passwords and encryption to provide protection. The backup
copies of software and recovery restart procedures must be available when needed.
This system will provide the facilities for both customer & operators on the same portal. So
security constraints must be applied carefully. A customer wouldn’t require to login into the
reservation system for reservation. He will simply view all the information on web. While a
counter assistant will require to have user ID & Password. After proper validation checking of
that operator he can make transactions. His total transaction details will also be recorded along
with his ID in a log Table, so that any misusage of the system can be prohibited.
System security refers to various validations on data in form of checks and controls to avoid the
system from failing. It is always important to ensure that only valid data is entered and only
valid operations are performed on the system. The system employs two types of checks and
controls:
75 | P a g e
Tab-Indexes are set according to the need and taking into account the ease of user
while working with the system.
PERT Chart:
76 | P a g e
1 JUL 1 JUL, 1AUG 2AUG , 20 AUG
Start Analysis and Design Training on iButton
A PERT Chart is a network of boxes and arrows. To create PERT chart, first we
need to list all the activities required for completion of the project and estimate how long
each will take. Then we must determine the dependence of activities on each other. The
PERT chart gives a graphical representation of this information. PERT chart is always
used by the project manager to answer the questions like which all activities are
necessary or there in the project and how long each will take.
Here we are using boxes to represent the activities. The arrows are used to show the
dependencies of activities on one another. The activity at the head of an arrow
cannot start until the activity at the tail of the arrow is finished. The boxes in a PERT
chart can be decorated with starting and ending dates for activities.
GANTT Chart:
GANTT charts are a project control technique that can be used for several
purposes, including scheduling, budgeting, and resource planning. A Gantt chart is a bar
77 | P a g e
chart, with each bar representing an activity. The bars are drawn against a time line.
The length of each bar is proportional to the length of time planned for the activity.
Start
Analysis &
Design Training
Developing
API
Coding
Test
Help
file
creati
Finish
78 | P a g e
FUTURE SCOPE OF THE PROJECT
79 | P a g e
REFERENCES
80 | P a g e