CONFERENCE ROOM

BOOKING IN AAI

SUBMITTED BY:
AKSHAY
BHAVYA SATIJA
DRON KAPIL
HARSH SRIVASTAVA
KARTIK CHUGH
NEERAJ
NISHANT SRIVASTAVA
SHASHANK MISHRA
SHIVAM KWATRA
TARUN GUPTA
TANVI SOOD
VIKAS SANGWAN

1|P ag e
 Airport Authority of India

The Airport Authority of India (AAI) is an organization working under the Ministry of Civil
Aviation that manages all the airports in India. The AAI manages and operates 126 airports
including 12 international airports, 89 domestic airports and 26 civil enclaves. The corporate
headquarters (CHQ) are at Rajiv Gandhi Bhawan, Safdarjung Airport, NewDelhi. V.P
Agrawal is the current chairman of the AAI. AAI provides air navigation services over 2.8
million square nautical miles of airspace. During the year 2002-03, AAI at various airports
handled about 5 lakhs aircraft movements (4 lakhs domestic and 1 lakh international); 40
million passengers (26 million domestic and 14 million international) and 9 lakh tons of
cargo (3 lakh domestic and 6 lakh international).

History

The AAI was formed on 1 April 1995 by merging the National Airports Authority (NAA)
and International Airports Authority of India (IAAI), to create a centralized organization that
could effectively manage both the international and domestic airports. Presently, it is owned
100% by the Government of India.

2|P ag e
Bengaluru International Airport

Hyderabad – Rajiv Gandhi International Airport

3|P ag e
Mumbai – Chhatrapati Shivaji International Airport

4|P ag e
Functions

Control and Management of the Indian airspace extending beyond the territorial limits of the
country, as accepted by the ICAO
 Design, Development. Operation and Maintenance of International and Domestic
Airports and Civil Enclaves.
 Construction, Modification and Management of Passenger Terminals.
 Development and Management of Cargo Terminals at International and Domestic
Airports.
 Provision of Passenger Facilities and Information System at the Passenger Terminals
at airports.
 Expansion and strengthening of operation area viz. Runways, Aprons, Taxiway, etc.
 Provision of visual aids.
 Provision of Communication and Navigational aids viz. ILS, DVOR, DME, Radar,
etc.

Revenue

Most of AAI’s revenue is generated from landing/parking fees and fees collected by
providing Air Traffic Control services to aircraft over the Indian airspace.

International Projects

The AAI has been involved in various consultancy projects with Libya, Algeria, Yemen,
Maldives, Nauru and Afghanistan. The AAI also provides trained personnel for operation,
maintenance and management of airports in these countries.

5|P ag e
 ABSTRACT

This project is of ‘Conference Room Booking’ built with the help of Android (Java) as
front end and SQL and PHP as back end. This project has been built in order to eliminate
the problem related to the booking of conference rooms. The aim of this project is to help
people in booking conference room of their choice on a particular date and at particular
time for a particular duration easily.
The main achievements during the development of the project we have achieved is the
elimination of previous problem regarding security of the software and the effective flow
of control of the software so that it can run without any error and easy understanding of
the working of the software to the end users.

6|P ag e
 ACKNOWLEDGEMENT

It is obvious that the development of a project and the dissertation is the beyond the scope
of one person alone. Although it is not feasible to list the names of each and every person
who helped me in the successful completion of the project, the following persons’ support
and endless help and contribution needs special mention:

Mr. V.K. SHARMA-(General Manager IT Department, Airport Authority of India)

For his constant support and guidance as without him this project could not have been
successful.

7|P ag e
 TABLE OF CONTENTS

CHAPTERS

1. INTRODUCTON
1.1 Background
1.2 Objectives
1.3 Purpose, Scope and Applicability
1.3.1 Purpose
1.3.2 Scope
1.3.3 Applicability
1.4 Achievements
1.5 Organization of Report
2. SURVEY OF TECHNOLOGIES
3. REQUIREMENTS AND ANALYSIS
3.1 Problem Definition
3.2 Requirements Specification
3.3 Planning and Scheduling
3.4 Software and Hardware Requirement
3.5 Preliminary Product Description
3.6 Conceptual Models
4. SYSTEM DESIGN
4.1 Basic Modules
4.2 Data Design
4.2.1 Schema Design
4.2.2 Data Integrity and Constraints
4.3 Procedural Design
4.3.1 Logic Diagram
4.3.2 Data Structures
4.4 User Interface Design
4.5 Security Issues
4.6 Test Cases Design
5. IMPLEMENTATION AND TESTING
5.1 Implementation Approaches
5.2 Testing Approach
5.2.1 Unit Testing
5.2.2 Integrated Testing
5.3 Modifications and Improvements
6. RESULTS AND DISCUSSION
6.1 Test Reports

8|P ag e
 6.2 User Documentation
7. CONCLUSIONS
7.1 Conclusion
7.2 Limitation of the System
7.3 Future Scope of the Project

REFERENCES

9|P ag e
 TABLE OF FIGURES

1. DFD (Data Flow Diagrams)

2. E-R Diagram
3. Schema Design
4. Screenshots

10 | P a g e
 Chapter 1: INTRODUCTION

 BACKGROUND
 OBJECTIVE
 PURPOSE
 SCOPE
 APPLICABILITY
 ACHIEVEMENTS
 ORGANISATION OF REPORT

11 | P a g e
1.1 Background:-
In order to develop software some background knowledge is essential in that field. We
too have developed small scale software previously like of billing system of a particular
shop. We have gained knowledge of Java and SQL in 5th Semester of B.TECH. This
knowledge has brought in us a confidence in building this project.

1.2 Objectives:-

The majority of problem in booking maintenance are an account of poor administrative,

functioning or efficiency of the various system generating high volume of dynamics data
24 hours a day through various departments involving large numbers of people. This
project has been designed to overcome the entire problem with the following objectives

 To develop an efficient communication channel in the computerized customers’

connection.
 To maintain a common centralized database for the entire booking record.
 To provide quick and accurate retrieval of data in flexible manner.
 To maintain proper security and confidentially of data.
 To develop a modular user friendly system.
 To ensure optimum utilization of expensive resources.
 To establish standard of data exchange between various systems.
 To assist planning, monitoring and budgeting processor.
 To increase organization efficiency through production in the overall cost of
delivery member case
 To provide useful accurate, complete and timely information to meet the
requirements of the various authorities requiring such data.
 To improve managerial effectiveness in planning, allocating and controlling the
connection and expensive resources of the organization.
 To improve the management information system.
 To reduce the clerical work loads.
 To reduces total costs.

12 | P a g e
To produce a simple, yet suitably effective user interface, and a system that is easily
maintainable, efficient and practical and does the following tasks –
 Adds new Conference Room Booking details.
 Update old booking details
 Retrieve booking details
 Generate the reports on booking details whenever wished.
 Generate a Booking ID, Customer ID to the customer.

Calculate the Booking Amount, Balance Amount by deducting the advance account from
booking account.

1.3 Purpose, Scope and Applicability:-

1.3.1 Purpose:-
This project is of Conference Room Booking deals with the booking of various conference
room available and also provide the details of the equipment available in the corresponding
conference room.
The aim of this project is to actually understand the practical implementation of the
knowledge we possess. The project is built by using Android as the front end and Oracle as
Back-end.
The main purpose of this project is to make an application that works real time on wifi and
any person connected on that network can Login with his/her password and can get the
details of the rooms available at a particular date and time and he/she can also book the
available rooms on that particular date and time online.

1.3.2 Scope:-
 Software is user friendly.
 Less time consuming than manual system.
 Maintenance of records is easier.
 No need to store thick files.
 Not very costly
 Data integrity is present.
 App is data dependent.
 No chances of redundancy in records.
Application will be applicable for a long period as provisions are there for further additions
and developments.

13 | P a g e
1.3.3 Applicability:-
The software can be used directly by any person who owns rooms for conference room
booking. He/She can easily hand on experience with this software it is very erasy to operate
and provides them flexibility in their work. This app can have a broad applications in the long
run

1.4 Achievements:-
This project has brought us a lot of changes. It made us handle real life problems that can be
solved through computers. We learnt a lot about programming language like Android and
used it to build the application. We came across certain difficulties which required intensive
research and referring to various materials in order to solve them, and also taking help by our
counsellor.

1.5 Organisation of Report:-

The remaining chapters deal with the various aspects regarding building of this application,
different types of designs and models like data design, Data Flow Diagrams, ER Diagrams,
Algorithms design etc., different types of testing their reports, User Documentation etc.

14 | P a g e
 Chapter 2: Survey of Technology

Today in order to develop applications various technologies are available which include
language and software and out of which we’ve used Android for our front end and Oracle as
our back end.

Reasons for selecting such application:-

 It improved services, which emphasizes quick availability of information of rooms,
improved accuracy, and fast turnaround.
 It helps in the early detection of problems and the ability to expand operation without
adding users help.
 Through this we can maintain the time management, reduces the cost of maintenance
and improve the ability to predict business trends.
 Android is an Object Oriented Language which makes us understand the problem
quite closely in terms of various types of objects and the relationship between them.
 The offered application is not too costly and is easily available on the store.
 Maintenance of this application isn’t a tough task
 We can provide security to prevent unauthorized access with the help of this
application.
 Oracle is a back end application. It can be used as database because it is efficient for
our project and it provides many features of automatic backup thus protecting our data
in any case.

Justification of the proposed application:-

The proposed application is to reduce the cost and increase the efficiency of the entire
process. We have used Android as the front-end because it provides more flexibility in
developing user friendly environment that means not an expert is required to maintain the
record. For database we have used Orcale because it is sufficient to maintain booking records
of conference hall and oracle is highly reliable database and is easily available in the market.

15 | P a g e
 Chapter 3: Requirements and Analysis

 PROBLEM DEFINITION
 REQUIREMENT SPECIFICATIONS
 PLANNING AND SCHEDULING
 SOFTWARE AND HARDWARE REQUIREMENTS
 PRELIMINARY PRODUCT DESCRIPTION
 CONCEPTUAL MODELS

16 | P a g e
3.1 Problem Definition:-
The problem was to book a particular Conference Room on a particular date, at a particular
time and for a particular duration. This should be available online also in a wifi environment.
Any known customer having his/her User_ID and password can login and book rooms for
himself/herself on a particular date and at a particular time connecting to wifi. He can also
book the various devices/equipments required with the booking such as amplifier, projectors
of different types such as slide projectors, film projector etc. video switch, microphones,
computers etc.

3.2 Requirement Specification:-

After the preliminary survey and listening to the client’s requirements following were listed:
 To develop a conference room booking system.
 The present manual system being employed should be selected as client system.
 The system should ensure that a quick response is given to user queries in areas of
requests.
 A simple user interface should provide to the user easy access to requested
information.
 The front end should have a GUI.
 Every transaction should be dealt with minimum delay.
 The system should provide information dynamically, example booking status, room
details, customer details, employee details.
 The system should allow records to be added and deleted with ease, in order to hasten
the cancellation process.
 Proper relationship between tables should be maintained so that data integrity is
maintained.
 Data deleted from one form should be automatically updated in other related forms as
well.
 Each module should have a password to avoid unauthorized users.

17 | P a g e
3.3 Planning and Scheduling
Planning
In the planning phase of the project, the rules and constraints associated with the project is
described which controls the flow of execution of the software whenever certain tasks can or
cannot happen.
Firstly, no booking can be done on a day prior to the current date. If this happens the app
must show some error message and post that return to its previous working condition.
Secondly there shouldn’t be any conflict of rooms as same room cannot be booked by two
different parties. If users do so, then it must return some error message.
No unauthorized person shall be able to login onto the app. If someone tries so gain access
using unauthorized username, password, it should ask for the correct one.
Booking should only be done of a room that exists on a particular date and time. If it is
violated then room not available should be displayed on the screen.
No cancellation is done of the booking ID that does not exist or of previous date than the
current date. If user wants to do so respective error message should be displayed by the
software.

Scheduling
Scheduling of app is co-related to various tasks with respect to their cost, value and duration.
Depending upon the project scheduling can be done dynamic in implementation. The
following are the various types of scheduling techniques.

18 | P a g e
3.4 Software and Hardware Requirements:-

Tools Used:-
 Android
 Oracle

Software Requirement (Environment)

 Operating System Android 4.0 or above
 Front End Android
 Back End Orcale 8i onwards

Hardware Requirement (Environment)

 Processor (1 GHz or above)
 Memory 1 GB
 ROM (45 MB)

19 | P a g e
3.5 Preliminary Product Description
The new system is more advanced than the previous ones. It provides more security
and easy access to the app with enhancement of backup and recovery so the proposed system
need more advanced software installed in the system. In order to achieve all of its objectives
proper knowledge of how to handle the software is also mandatory. The main objectives of
the new system are as follows:-
 To maintain a common centralized database for the entire booking record.
 To provide quick and accurate retrieval of data in a flexible manner.
 To maintain proper security and confidentiality of data.
 To develop a modular user friendly system.
 To ensure optimum utilization of expensive resources.
 To establish standard of data exchange between various systems.
 To assist planning, monitoring and budgeting processor.
 To increase organization efficiency through reduction in the overall cost of delivery
member case services.
 To provide useful accurate, complete and timely information to meet the requirements
of various authorities requiring such data.
 To improve managerial effectiveness in planning.
 To reduce critical and clerical work loads.

The new system will function very efficiently, having proper management of data and
information regarding the list of users and their authorization level. It’ll also have the
functionalities of changing the password, maintaining employee information, customer’s
information and many more features besides booking the conference room.

3.6 Conceptual Models:-

This is the most creative and challenging phase of the system life cycle. It describes the final
system process by which it is developed.
The major steps in design are present in the following figure:
Following are the designing tools used for designing the app
 DFD
 ERD

Data flow diagram (DFD)

A DFD is also known as a “bubble Chart” has the purpose of clarifying system
requirements and identifying major transformations that will become programs in system
design. So it is the starting point of the design to the lowest level of detail. A DFD consists
of a series of bubbles joined by data flows in the system.
20 | P a g e
DFD symbols:

In the DFD, there are four symbols

1. A square defines a source (originator) or destination of system data

2. An arrow identifies data flow. It is the pipeline through which the information flows

3. A circle or a bubble represents a process that transforms incoming data flow into
outgoing data flows.

4. An open rectangle is a data store, data at rest or a temporary repository of data

21 | P a g e
CONSTRUCTING A DFD:
Several rules of thumb are used in drawing DFD’s:
1. Process should be named and numbered for an easy reference. Each name should be
representative of the process.
2. The direction of flow is from top to bottom and from left to right. Data traditionally flow
from source to the destination although they may flow back to the source. One way to
indicate this is to draw long flow line back to a source. An alternative way is to repeat the
source symbol as a destination. Since it is used more than once in the DFD it is marked with
a short diagonal
3. When a process is exploded into lower level details, they are numbered.
4. The names of data stores and destinations are written in capital letters. Process and
dataflow names have the first letter of each work capitalized

0’(zero) LEVEL DFD :-

Get users created Gets
and jobs done booking
generate Booking Clerk
Administrator d and
jobs done

Generate booking
Manages
and manage
user and
customer’s
employee Conference records
details
Room
Booking

Queries about rooms Gets the desired

available, their cost details and room
per hour booked

Customers

22 | P a g e
DFD for Administration:-
1st level DFD :-

Administrator

User Table

Login as Admin Verifies

Password
1

Changes
Stores
Password
Employee
3
Records
2
CRB
Database

Administrator

23 | P a g e
 2nd level DFD:-

Verifies the
old Replaces
password the old
password
Verifies the with new
employee Stores in
details the
database
Stores the
details in Derives
the information
database from the
database by
supplying Administrator
the userid

DFD for Booking Clerk:-

1st level DFD
Booking Clerk

Verifies User Table

Password
1

CRB
Database Changes
Adds new Password
customer 4
Generate details
new 3
Booking
2
Booking Clerk

24 | P a g e
 2nd Level DFD

Confirms
old Replaces
password the old
password
with new
Verifies
customer Stores in
Stores
details the
details in
database
database
Retrieves data Retrieves
for new information
booking from
database
Generate
New Stores
booking record of
new
booking in
the Booking Clerk
database

Entity Relationship Diagram (ERD)

Entity Relationship Diagram is used to understand and document the system data independent
of how the data is being used or will be used. ERD describe the relation between groups of
data.
Data is the centre of any processing system. It is therefore necessary to understand it and the
relationship between the groups of data to be able to model a system.
The basic concepts of an ERD are entity and data relationships. In a system there may be
several entities question bank, student details etc
The ERD is a representation of the relationship between entity types.

25 | P a g e
ER- diagrams consist of following components:-
 Rectangles – represent Entity sets.
 Ellipses – represent attributes.
 Diamonds – represent relationship sets.
 Lines – link attributes to entity sets and entity sets to relationship sets.
 Double Ellipses – represent multi valued attributes.
 Double lines – indicate total participation of an entity in a relationship set.
 Dashed ellipses – denote derived attributes.

26 | P a g e
 Chapter 4: System Design
 BASIC MODULES
 DATA DESIGN
 PROCEDURAL DESIGN
 USER INTERFACE DESIGN
 SECURITY ISSUES
 TEST CASE DESIGN

27 | P a g e
4.1 Basic Modules: -
1. Login check
2. Change Password
3. Create User
4. Drop user
5. New Employee Entry
6. View Employee Details
7. Book Room
8. Cancel the Room Booking
9. View Booking Details
10. New Customer Entry
11.View Customer Details

1. Login Check: This Module is meant for checking the valid Admin/user logging into the
software.
2. Change Password: This Module is responsible for changing the existing password of
the valid user.
3. Create user: This Module works for administrator in order to create a User: This
Module works for administrator in order to create a new user who can log on the software.
4. Drop User: This Module also works for administrator in order to delete any existing user
for the database.
5. New Employee Entry: This Module provides the facility of the entering the details of
any new employee by the administrator which after submission added to the database and
generates and displays the employee_id.
6. View Employee Entry: This Module provides the details of any existing employee
when provided the employee_id by the administrator.
7. Book Room: This Module is the main module of the entire software. It takes input from
the booking clerk/customer, the date of booking, starting time, ending time and the capacity
of the room to be booked and displays the list of available rooms if it exists.
Further, one can book the desired room from the list of available rooms by clicking the book
button. If the customer is a new customer then the details of the customer must be entered in
the database so that he/she own id. After that when provided the customer id it displays the
booking amount and asks for the advance amount. After entering the advance amount, it
generates the booking details with booking id and related information if there is no error in
this booking regarding the constraints applied to the tables if there is any error it displays an
error message.
8. Cancel Room Booking: This module is responsible for cancelling of the room booked
when provided a valid booking id by the booking clerk.

28 | P a g e
9. View Booking Details: This module is meant for displaying the details of any booking
if provided a valid Booking id
10. New Customer Entry: This module is meant for entering the details of a new
customer. After submitting it generates the customer id which can be used at the time of
booking of conference rooms. The details are saved to the database in the customer table.
11.View Customer Details: This module is meant for viewing the details of any
customer when provided the valid customer id.

4.2 Data design: -

4.2.1 Schema design: -

User Table
Field Name Data type Description
User id VarChar2(20) Unique for each other
Password VarChar2(15) Password

Cust_Detail Table
Field Name Data type Description
Cust_ID Number(5) Automatic generate
Cust_Name VarChar2(20) Name of customer
Cust_Address VarChar2(30) Address of customer
Cust_Gender VarChar2(6) Sex of customer
Cust_Phoneno VarChar2(15) Phone no of customer

Conf_Room Table
Field Name Data type Description
Room no Number(2) Room No
Capacity Number(3) Capacity of room
Rate_per_hr Number(5) Amt. paid per hour

29 | P a g e
Booking Table
Field Name Data type Description
Booking ID Number(5) Automatic generate
Cust_ID Number(5) Customer’s id
Room_no Number(2) Room No
Booking_date Date Date of booking
Start_time Varchar2(5) Start time of booking
End_Time Varchar2(5) End time of booking
Booking_amount Number(6) Total amount for booking
Advance Number(6) Advance given by the
customer
Balance Number(6) Total amount-Advance

Emp_Details Table
Field Name Data type Description
Emp_Id Number(5) Automatic generate
Emp_Name Varchar2(20) First name of Employee
Emp_Fname Varchar2(20) Employee’s Father Name
Emp_DOB Date Date of Birth
Emp_Joiningdate Date Date of Joining
Emp_Gender Varchar2(6) Sex of Employee
Emp_Address Varchar2(30) Address of Employee
Emp_Ismarried Varchar2(10) Material Status of Employee
Emp_Designation Varchar2(20) Designation of Employee
Emp_Phoneno Varchar2(15) Phone No. of Employee
Emp_Salary Number(5) Salary of Employee

4.2.2 Data Integrity and Constraints:

Primary Key Constraint: -

1. User_id: User id is taken as primary key in the user table. This will avoid the entry of
duplicate users.
2. emp_ID: emp_ID is taken as primary key in the emp_Details table so that no two
employees get the same id.
3. room_no: room_no is taken as the primary key in the conf_Room table. This restricts the
entry of duplicate room no.
4. cust_ID: cust_ID is taken as the primary key in the booking table such that no two
booking exist with same id

30 | P a g e
Foreign Key Constraint:-
1. cust_ID: cust_ID is taken as foreign key in the booking table so that the booking
can be related to the particular customer that exist in the cust_Details table.
2. 2.room_no: room_no is taken as foreign key in the booking table so that the booking
can be related to a particular room that exist in the conf_Room table.

1. The validity of the Employee age:
2. Valid booking date:
3. Valid booking date, time and room no
The validity has been applied on the
Employee table to check that the difference
between the date of birth and the joining date
of the employee must be greater than or equal
to 18 years.
This constraint checks for valid booking date
entered for booking it must not be any date
before the system date
This constraint checks for a valid booking
date and time that is no any booking exists
with same date and same time having the
same room no as it will lead to conflict
between the two bookings of the same room
on the same date and same time

4.3 Procedural Design:-

4.3.1 Logic Diagrams:-

Software has different modules to perform various functions which contain a set of
instruction in order to perform that function effectively. The flow of execution of instruction
may change whenever the program contains jumps, loops, etc. A control flow graph describes
the sequence in which different instructions of a program get executed. It also describes how
the flow of control passes through the program. Here is some common flow of execution of
the program has been represented through various CFG.

31 | P a g e
4.3.2 Data Structures:-
The programs contain different types of variables which carry the value specified for a
particular purpose. The variables can be declared as per the requirement of the program. The
variables can be declared as per the requirement of the program. Various can be declared as
per the requirement of the program. Various types of data can be classified linearly or having
tree type data structure. Here if the requirement to store the values of similar data type in the
program occurs, then array type of data structure can be used. Also, as we are using JAVA as
a programming language to develop the software we are aware of that it is an object oriented
programming language having class as a data structure wrapping in it the variables and
functions that operate on those variables.

4.3.3 Algorithm Design:-

1. Algorithm for login check:

Input Data: User id and password.
Output if input data is correct: Administrator/Booking clerk window depending on the user id
and password.
Output if input data is incorrect: Error message to enter the correct user id and password.
Algorithm Used:
The user id and password provided by the user is passed to the login check which is checked
if it exists in the database then 1 is returned else it returns 0. Further if 1 is returned then it is
checked that the user is an Administrator or other than the administrator. If it is administrator
window is displayed else booking clerk window is displayed.

2. Algorithm for change of password: -

Input data: User name, old password and new password.
Output if input data is correct: Updating of password field in the user table and message of
password changed successfully is displayed.
Output if input data is incorrect: Message of incorrect username or incorrect old password
should be displayed.
Algorithm used:
To change the password first the username and old password is passed to check, if the person
changing the password has provided valid username and password then only the function
related to change of password is called else the error message is displayed regarding the entry
of correct username and password.

32 | P a g e
 3. Algorithm to generate a new booking: -
Input data: Data of booking, starting time of booking, ending time of booking, capacity,
advance amount.
Input data: room no, customer id, booking amount, balance.
Output data: List of available rooms determine the booking done with booking id.
Algorithm used:
First of all date of booking, starting time, ending time and capacity is entered by the user
which is passed to function which displays the list of available room based on the
requirements from the database with their corresponding details like capacity and rate per
hour.
Choice of room is selected from the list of available room which further asks for the customer
id if the customer is any of the existing customers. If it is new one then customer entry from
is displayed by clicking on new customer button. After filing the form customer id is
generated which can be used to pass in the booking table?
Calculation of booking amount is done as follows:
Duration=End time-Start time
Booking amount = Rate per hour*Duration
Advance amount is taken as input from the user and is deducted from booking amount and
the result is stored in the balance variable as follows:
Balance=Booking amount- Advance amount.
All the above explicit and implicit data are sent to the database to store the values in the
booking table which after entering the data returns the booking id.
This booking id is further passed to the function responsible for displaying the booking
details which finally displays all the above input data after retrieving from the database.

4.4 User interface design: -

The user of the system may be an administrator or A booking clerk. Based on their respective
privileges the user interface has been designed. An administrator has user interface with
rights to enter employee details and if the right has been eliminated from a booking clerk user
interference. Booking clerk can enter customer’s details, new customer’s details, change
his/her password, book room, cancel booking and display booking details. There are various
types of form like of entry of the details of a new employee by the user with the facility of
getting autogenerated Emp id after submitting. Similarly, there is new customer every form
also in the system with the facility of providing auto generated customer id after submitting
the new booking entry form is also available.

The pictorial representation of the user interfaces is shown with the help of falling screen
shots: -

33 | P a g e
34 | P a g e
35 | P a g e
36 | P a g e
4.5 Security Issues:-
As any softwasre is built it requires protection from unauthorized access so that no any
inconsistent data should be there that could cause problem. Thus, software must be secure
enough to handle these types of situations. There must be authorization level assigned with
each used level wise.
We have created two types of authorization level one for administration and other for
booking clerk. An administrator is responsible for creating any new employee with their
corresponding details. He/she can also create users who can work as booking clerk to book
rooms available but with limited access of the software. An administrator can view the details
of any employee thus hiding the data from unauthorized access.
4.6 Test cases design: -
Login form:

S.no Initial Expected Output

1. Login failure Login when Wrong
when password is password matches
correct.
2. Unable to access Data should be Wrong
data meant for accessed
Administrator.
3. Password data Password retrieve Corrected
access from user
table.
4. Login rechecked Worked out Corrected
for Admin and
Booking clerk
5. Primary key Primary key Wrong
validation not validation
working available
6. Numeric Numeric Wrong
validation for validation for
numerical fields numeric fields
not functioning should be working
7. Error in automatic Emp id should be Wrong
generation of Emp generated
id correctly
8. Scroll bar in Scroll bar should Wrong
address field not work
working
9. Primary key Worked out Corrected
validation
available with
error if duplicate
10. Numeric Worked out Corrected
validation for
numerical fields

37 | P a g e
 Chapter 5: Implementation and Testing

 IMPLEMENTATION APPROACHES
 TESTING APPROACH
 UNIT TESTING
 INTEGRATED TESTING
 MODIFICATION AND IMPROVEMENTS

38 | P a g e
5.1 Implementation Approaches:-
Installation Procedure of the Software:
In order to run the software proper installation of the software is necessary. This software
has been developed by using ANDROID as front end and ORACLE as back end that’s why
first of all to run the software we need to install ANDROID and ORACLE in the system .
Following steps should be performed to run the software:-
i) Install ORACLE in the system.
ii) Install Android in the system.
iii) After installing the same we need to create a connection between the two through
JDBC- ODBC bridge. To create a connection go to Control Panel and then to
Administrative Tools in case of Windows 2000 or higher versions else directly go
to Data Sources(ODBC).
iv) A dialog box appears, select system DSN tab.
v) Click on Add button.
vi) Select Oracle ODBC driver from the list of options.
vii) Write the Data Source name as conf. This is the name of DSN used in the
program.
viii) Create desired table in Oracle given in Schema Design with various constraints.
ix) Create the administrator account with the password. This value will be given by
the administrator at running time of the software.
x) Compile the source code of Android and run the software by double clicking on
the conference batch file icon.

5.2 Testing Approach:-

Even completion of the design stage does not imply thst the development of software
is complete. The system designed needs to be verified so that the errors don’t creep in,
although it is inevitable to develop a system without any errors.
The project was under constant scrutiny to ensure that its implementation was not
deviating from its original plan, and that functions that were implemented were doing their
jobs correctly. The main functions of this system or user options on which testing were done
can be summarized as follows:-

 Retrieve a booking detail from the database.

 Add an employee detail in the database.
 Add a new booking and customer’s details to the database.
 Amend an existing record from the database.
 Remove an existing record from the database.
 Generate a detailed report about the bookings

39 | P a g e
Each of these functions would need to ensure that they do only just what the user requests,
and not something other than that. The system that has been implemented will need to
stimulate typical situations that are currently being frequently performed manually at home,
as well as typical ones. As will explain later, these typical cases were tested more thoroughly
than a typical one.
The main objective of the testing is to show the presence of bugs, not the absence. No
absolute certainty can be gained from the testing. The testing just ensures that the candidate
system is an efficient alternative to the present system.

The cautions kept in mind while choosing the tests are:

1. The testing should be based on sound and systematic techniques.

2. Testing should help locate errore, not just detect their presence.

3. Testing should be repeatable, i.e. , repeating the same experiment, supplying

the same input data to the same piece of code, produces the same results.

The tests done on the designed software was to verify the following properties of the
software:
 Correctness (satisfaction of the specifications)
 Reliability (how well it meets the requirement)
 Portability (running in different environments)
 Usability (ease with which user can use the software)
 Maintainability (modifications after initial release), etc.

Black Box Testing:-

Black box testing also called functional testing, is based on the definition of what a (piece of)
program is intended to do (i.e., it is based on the program’s specifications)
We will list a few examples of test that were performed to check the reliability and validity of
the system:
Upon removing a booking record no other records were affected.
It ensured that removing every existing record from the database did exactly that, leaving to
lingering records.
It was checked that duplicating an existing record’s details in a new record was not possible.
When amending a record, the amendments were actually updated in the database immediately
after the user had accepted the amendment.
This form of testing was found to be limited somewhat in certain cases, and hence the white
box methods proved more productive, but there was often no distinct margin separating one
from the other.
40 | P a g e
Some of the results of black box testing are as follows:-

Password Choice Login succeeded

Main Menu Main Menu displayed
Employee choice Employee screen display
Add booking details Saved in database
Generate new booking Booking generated
Calculate booking amount Booking amount calculated
ID enter to search Result displayed
Exit Choice Exit

White Box Testing:-

White box testing is also called structural testing, because it uses the internal structure of the
program to derive the test data.

White Box Testing is checking every single path of the program, so the errors can be traced
than compare to the black box testing.

5.3.1 Unit Testing:-

Individual components are tested to ensure that they operate correctly. Unit testing treats each
component as a stand-alone entity which does not need other components during the testing
process. In our project, every single button has been checked individually, such as Add
Employee Detail, Display Employee Detail, Change Password, play Button, Submit Button,
Cancel Button, etc.

5.3.2 Integrated Testing:-

Once testing is over the different modules were integrated to develop the complete software.
The various types of testing done at this stage regarding the functions passing their results to
different functions in order to continue the flow of execution of the program effectively and
the different modules are tested which are integrated with each other.

Example:-
Calculation of booking amount is integrated with the rate per hour of a particular room and
calculation of duration of booking which we can get after subtracting end time of booking
and start time of booking.

Similarly calculation of balance amount is integrated with the subtracted result of booking
amount and Advance amount. The result is checked with the desired result and found it
correct.

41 | P a g e
5.4 Modification and Improvements:-

After completion of testing various bugs found which were debugged. The source code has
been modified and some of the algorithms has been changed in order to ccorrect the output of
the system.
Example:-
The automatic generation of Employee_Id, Cutomer_Id and Booking_Id was found not
working properly so the algorithm for the generation of these Ids has been changed and later
on it was found that it was working properly with the implementation of the new algorithm.

PAY NOW button was not functioning properly in the Booking Report of a particular
booking. This button was meant for paying of the balance amount if it is and updating the
value of the balance to zero. If there is no balance amount left for a particular booking then
Amount already Paid message should be displayed. This was not working properly so the
algorithm has been changed in order to make the desired changes in the database
permanently.

42 | P a g e
 Chapter 6: Results and Discussions

 TEST REPORTS
 USER DOCUMENTATION

43 | P a g e
6.1 Test Reports:-
After all the tests on the designed software to verify its various qualities following
conclusions were attained:

 Correctness: The designed software meets the functional requirement specifications to

a fair degree of correctness.
 Reliability: Based on the test data, the client termed the software reliable.
 Robustness: the various message and error codes enhanced the robustness of the
software.

6.2 User Documentation:-

The working of the software is better explained with the help of various screen shots
presented on the subsequent pages. The step by step procedures are shown through the
pictures:-

44 | P a g e
45 | P a g e
46 | P a g e
47 | P a g e
48 | P a g e
49 | P a g e
50 | P a g e
51 | P a g e
 Chapter 7: Conclusion

 CONCLUSION
 LIMITATION OF THE SYSTEM
 FUTURE SCOPE OF THE SYSTEM

52 | P a g e
7.1 Conclusion:-
This chapter will review the initial objective and the extent to which they were fulfilled. It
will summarise the project’s success and weakness and what was learnt during it duration.

Extent to Which Original Objectives Were Met

The project Objectives, as defined in chapter 1 can be summarized as follows. To produce a
system that provides a very friendly graphical user interface, permitting the user to perform
basic administration duties on a database containing records of books. In doing so, an
appreciation of project management , communication and consultancy skills should be
acquired, along with a thorough understanding of the development of android based
applications achieved, some to greater extent than others .The objects has been broken in the
following section, and discussion on what was achieved from them.

1. User Friendly Interface:-

The final result of the Conference Room Booking consolidated an easy to use and hence
effective user interface with basic user functionality requested from the management of the
client. A lot of time and careful consideration was taken to ensure that it encompassed all of
the characteristics of a successful user interface, and one which tried to inspire confidence in
its user. Continual communication, in the form of message and the dialogue facility, from the
system to its user gives them a feeling of security and power.

2. Project Management ,Consultancy and Communications Skills

Acquired:-
We learnt a great deal from setting our self the objective training experience in these areas.
We have accomplished project by putting all necessary skills into practice proficiently. On
the contrary, upon reflection of the project and its end result, we believe that the time
scheduling was very weak. We now know that these skills are on-going learning experiences,
and upon the scheduling of further projects, the accuracy of estimation should increase.
It was not conceived that the allocation of timing constraints to the project’s associated life-
cycle processes, for example, its design and testing phased, could be so inaccurate.

3. Extent to Which User Requirements were Met:-

Great emphasis was laid n the requirements as specified by the management be incorporated
into the system. The requirements demands the system to be safe and easy to use , promptly
displaying any necessary requested information via graphical user interface, were carefully
considered before being implemented, so that they would be successful and effective.

53 | P a g e
 4. Help Facility Review:-
The requirements demanded a user friendly system that had the possibility of the helping the
user where appropriate. This is achieved through the facility of continual communication
from the system ,in the form of the on-line help guidance and also messages the system
displays to the user about possible mistakes that could be remedied and whether processed
should continue or not.

7.2 Limitations of the System:-

The System has the following limitations:-
 The proposed system can login into itself only two types of user i.e. Administrator
and Booking clerk.
 We can enter the date in the desired format provided in the system . No any other
format will be accepted.
 We can enter the time of booking in 24hrs format only , no any other format accepted.
 Payment of booking can be made in two installments only i.e. Advance Payment and
payment of balance Amount.

7.3 Future Scope of the Project

The project has been designed to work on the large scale, so according to our analysis in the
future scope of this project is bright and would have an everlasting effect on the current
system. The future scope of the project is that it would be provided with the functionalities of
Bugs Report and submitting facility in case there are any abnormal failures in the software.
Next, we would like to make the software work even faster in case the database size
increases. We would also like to include safe mode facility in the software so as to recover
the software hangs out or has abnormal crashes or errors.

54 | P a g e
 References:-

1. Complete Reference java 2 (Tata McGram hill) schildt.

2. Java 2 jdk 5th edition (dreamtech) Ant – striven Holzmeral.
3. Head First Android Development (by Anthony J.F. Griffiths and Thomas
Asbridge).

55 | P a g e