TESTING PRACTICE AND PLANS

Testing is an important function to success of the system. System testing makes a logical
assumption that if all the parts of the system are correct, the goal will be successfully
activated. Another reason for system testing is its utility as a user oriented vehicle before
implementation.
System testing consists of the following five steps:
Program testing-:
A program represents the logical elements of a system. For a
program to run satisfactorily, it must compile and test data correctly and tie in
properly with other programs. It is the responsibility of a programmer to have error
free programs.
String testing-:
rogram is invariably related to one another and interacts in total
system. !ach program is tested to see whether it conforms to related programs in the
system. !ach part of the system is tested against the entire module with both test and
live data before the whole system is ready to be tested.
System testing -:
System testing is designed to uncover weaknesses that were
not found in earlier tests. This includes forced system failure and validation of total
system, as its user in the operational environment will implement it. "nder this
testing, generally we take low volumes or transactions type is reached.
User acceptance testing-;
An acceptance test has the ob#ective of selling the user
on the validity and reliability of the system. It verifies that the system$s procedures
operate to system specifications and that the integrity of important data is maintained.
erformance of an acceptance test is actually the user$s show. "ser motivation is very
important of the successful performance of the system. After that a comprehensive
test report is prepared. This report shows the system$s tolerance performance range,
error rate and accuracy.
Peak oa! testing-:
It determines whether the system will handle the volume of
activities that occur when the system is at peak of it processing demand. For e%ample
test the system by activating all terminals at the same time.
Storage testing-:
It determines the capacity of the system too store transaction
data on a disk or in other files. For e%ample verifier documentation statements that
the system will store &',''' records of ('' bytes length on a single fle%ible disk.
Per"ormance testing-:
&')
It determines the length of time system used by the
system to process transaction data. This test is conducted prior to implementation to
determine how long it takes to get a response to an in*uiry, make a backup copy of a
file, or send a transmission and get a response.
Reco#ery testing-:
This testing determines the ability of user to recover data or
restart system after failure. For e%ample, load backup copy of data and resume
processing without data or integrity loss.
Designing Test Data-:
The proper designing of test data is as important as the test
itself. If test data as input are not valid or representation of the data to be provided by the
user, then the reliability of the output is doubtful. Test data may be live or artificial. The
live data is that which is actually e%tracted from the users files. After a system is partially
constructed the programmers or analysts as the users to key in set of data from their
normal activities. It is difficult to obtain live data in sufficient amount to conduct
e%tensive testing.
The artificial tests data is created solely for test purposed. roperly created artificial data
should provide all combinations of values and formats and make it possible to test all
logic and control paths through the program. "nlike live data, which are biased toward
typical values, artificial data provide e%treme values of testing the limits of the proposed
system. A test case is a set of data that the system will process as normal input. +owever,
the *uantities to be withdrawn from inventory e%ceed, e*ual and ate less than the actual
*uantities to be withdrawn from inventory e%ceed, e*ual and are less than the actual
*uantities on hand. !ach test case is designed with the intent of finding errors in the way
the system will process it. There are two general strategies for testing software: ,ode
testing, and specification testing. In code testing, the analyst develops those cases to
e%ecute every instructions and path in program. "nder specification testing that cases to
e%ecute every instruction and path in a program. "nder specification testing the analyst
e%amines the program specification and then writes test data to determine how the
program operates under specific conditions.
&'-
LI$ITATI%N %& T'E PR%(ECT
.nly two types of the room are available, vi/0 single bedroom and double
bedroom. "ser can$t introduce his own type of rooms.
1ill payment is not allowed by credit card.
The salary payment for the predefined designations in the system can be possible
only. .ther designations are not considered.
&'2
USER $ANUAL
'ARD)ARE RE*UIRE$ENTS
-( 31 4A3
entium II 5 III rocessor or later
6 71 of +ard 8isk
S%&T)ARE RE*UIRE$ENTS
9indows :%5;T56'''5< or =ater
3icrosoft .ffice 6''' or =ater
INSTALLATI%N STEPS
Insert the Software package ,8 into your ,8>4.3.
4un the setup program from the file setup.e%e that is placed under the folder
named ?+otel 3anagement System@ on the ,8>4.3.
Follow the instruction on the screen and the software package will be installed on
your machine.
;ow you can run the software program directly from the start menu.
USER GUIDELINES
.n the very first run of the software program, the user has to register the software
by giving a valid key number. The key number has been provided with the
package itself. A file named ,8AB!C.t%t has been placed in ?Support@ subfolder
of the folder ?+otel 3anagement System@.
The default password of the system is ?hotel@ De%actlyE, however it can be
changed later in the program.
lease do not modify or delete the Rooms+m!, file that will be created in the
folder in which the software program is installed, as it may result into erroneous
operations.

&'F
&':