Hotel Aditi (m)[1]

8/2/2019 Hotel Aditi (m)[1]

1/57

HOTEL MANAGEMENT SYSTEM

A Minor Project Report

Submitted in partial fulfilment of the requirements for the

Award of degree of Master of Computer Application

Submitted by: Guided by

Manik Kukreja Ms. Aparna Marwah

BHARATI VIDYAPEETH DEEMED UNIVERSITY SCHOOL OFDISTANCE EDUCATION

Academic Study Centre - BVIMR, New Delhi

An ISO 9001:2008 Certified Institute

NAAC Accredited Grade A University


2/57

Student Undertaking

This is to certify that I Manik Kukreja has completed the Project titledImplementation of Hotel Management System using C Language under the

guidance of Ms. Aparna Marwah in the partial fulfilment of the requirement for

the award of degree of Masters of Computer Applications (MCA) from Bharati

Vidyapeeth Deemed University, SDE, Academic Study Centre - BVIMR, New

Delhi. This is an original piece of work and I have neither copied nor

submitted it earlier elsewhere.

Manik kukreja

Course: MCA

Semester1st

(First)

Dated -


3/57

Acknowledgement

I take this opportunity to express my sincere gratitude to Ms. Aparna Marwah,Assistant Professor, Bharati Vidyapeeth Deemed University, SDE, Academic

Study Centre BVIMR, New Delhi for allowing me to carry out the projectunder her guidance.

I further thank her, for giving me the necessary instructive and administrative

support required for the completion of the project.

I therefore pay my great regards to madam who enriched me with valuable

guidance and all his technical support.

Manik kukreja


4/57

Preface

Manik kukreja


5/57

CHAPTER 1 INTRODUCTION

1.1 Introduction about Project

1.2 Present state of the art

1.3 Need of Computerization of System1.4 Proposed Software (What would s/w accomplish)1.5 Importance of the Work


6/57

1.1 INTRODUCTION ABOUT THE PROJECT

Our project Implementation of Hotel management System using C includes registration of

new customers, storing their details into the system, and also computerized billing of each

and every customer. Our software has the facility to give a unique code for every customer

and stores the details of every customer automatically. It includes a facility to know the

current status of hotel -stay i.e., to know about all the customers staying in their hotel their

respective bills. Administration can delete or modify any details with respect to the

customers, hotel rooms using the privileges provided to them.


7/57

1.2 PRESENT STATE OF THE ART (PROBLEM DESCRIPTION)

The purpose of the project entitled as Implementation of HOTEL MANAGEMENT

SYSTEM using C is to computerize / automate the front office operations of Hotel i.e.,

customer details management, room booking and bill generation etc. to develop software

which is user friendly, simple, fast, and cost effective. It deals with the collection of

customers information, room details, bills, etc. Traditionally, it was done manually through

conventional record keeping.

The main function of the system is to register and store customer details and retrieve

these details as and when required, and also to manipulate these details meaningfully to aid in

the front office operations.


8/57

1.3 NEED OF COMPUTERIZATION OF SYSTEM

ConvenienceConvenience includes the overall ease of finding information through various

searches thus minimizing time spent on searching in documents for any information.

It also enables administrator to get details of the customers by simply searching for a

given criteria. The application is required to have some amendment just in master

code and entire application could be changed.

TimesavingIt is much easier to just run a search and get a result than to search all the documents

and it also saves a lot of time corresponding to time involved in searching

information one customers detail at a time. But all the records could be arranged in

such manner that on a finger tips any record searching, updating, deleting and other

features could be maintained by the application user.

Secure Storage

Data security is maintained to relatively high level by implementing it at Databaselevel, so as to ensure that only authorized application users have access to mobile

customers confidential information. But the whole information is being stored by

using the file operation concept. The entire record is being stored in a file called

customer_rec. So the whole information could be only accessed by the file holder.


9/57

1.4 PROPOSED SOFTWARE

GOAL AND OBJECTIVES

The hotel has decided to make a computerized system for supporting various tasks done by

the staff members. The proposed system will perform many other functions along with the

functions performed by the current manual system. The system will help the hotel staff a lot

as well as supporting the management in various ways. The objective of the proposed system

is to computerized all the activities of the HOTEL MANAGEMENT SYSTEM:

This project provides complete Analysis of customer and their activities in thehotel and also keeps the record of all the clients of the hotel.

It gives the details of particular customer and their respective bills. Provides complete reporting of your customers. Provides very much user friendly input forms on which most of the work is done

at the click of the mouse, enter and tab key.

Generate various reports to support the management in taking fast and betterdecisions.

Minimizes the paper work, which is very time consuming. Make Each And Every Transaction Computerized.

The software is proposed to provide the following advantages:

The software is a highly efficient GUI based component and developed in C (a 4GL). This component can be easily plugged in many other systems. Also the component is user friendly. Generally the Hotel monitoring system has to

face a lot of problems in management of the customers details, bills details. This all

information has to be managed manually. So, there is a need to develop a system that

can solve the mentioned problem.


10/57

This software comes with an appropriate solution as per the situation faced by thehotel staff.

It also saves the amount of storage required to keep the customer and bill records. It also provides security as data security is maintained to relatively high level by

implementing it at database level, so as to ensure that only authorized users have

access to confidential client information.


11/57

CHAPTER 2 SYSTEM ANALYSIS

2.1 Feasibility Study of s/w includes its types

2.2 Analysis Methodology (Types)

2.3 Choice of Platforms s/w & l/w2.3.1 Software used2.3.2 Hardware used


12/57

2.1 FEASIBILITY STUDY

Depending on the results of the initial investigation, the survey is expanded to a

more detailed feasibility study. Feasibility study is a test of system proposal according

to its workability, impact on the organization, ability to meet user needs, and

effective use of resources. The objective of the feasibility study is not to solve the

problem but to acquire a sense of its scope . During the study, the problem definition

is crystallized and aspects of the problem to be included in the system are

determined. Consequently, costs and benefits are described with greater accuracy at

this stage. It consists of the following:

1.Statement of the problem: A carefully worded statement of the problem that

led to analysis.

2.Summary of finding and recommendations: A list of the major findings and

recommendations of the study. It is ideal for the user who requires quick access to

the results of the analysis of the system under study. Conclusion are stated ,

followed by a list of the recommendation and a justification for them .

3. Details of findings : An outline of the methods and procedures under-taken by the

existing system, followed by coverage of the objectives and procedures of the

candidate system. Included are also discussions of output reports, file structures, and

costs and benefits of the candidate system.

4. Recommendations and conclusions: Specific recommendations regarding the

candidate system, including personnel assignments, costs, project schedules, and target

dates.


13/57

Thus, Feasibility Study has to be done to check whether the project is worth doing i.e., it is

practicable or not. Since the project under consideration is for a specific purpose (hotel

management). Therefore, depending upon the user (hotel staff) needs, it will be necessary to

conduct the feasibility study in detail. This study results in feasibility analysis report that will

be used for deciding whether to proceed, postpone or cancel the project. Care should be taken

to accurately judge the user requirements since feasibility study may lead to commitment of

large resources Mainly, three issues/ aspects are to be addressed during this study.

OPERATIONAL FEASIBILITYThere is sufficient support for the proposed project from the management and users as it will

enhance their productivity and also reduce the amount of time required to view and access

any set of data. The new proposal system goes as per the business methods acceptable to the

users, thus there will be very less order of resistance from the users of the system.Although

the current technical staff is comfortable with the manual working regarding to the database

maintenance, management will find working with it very easy, simple and much cheaper at

cost. Once implemented, the staff will also find it very comfortable to work with it, and will

get addicted to working with such convenient and user friendly software.

TECHNICAL FEASIBILITYA numbers of technical issues were raised and examined during the stage of

investigation. These are: -

Does the necessary technology (Hardware, Software, Skill etc.) exist in thepremises (i.e., hotel)?

Does the proposed system can have the technical capacity to hold the enormousvolume of data processed?


14/57

Can the proposed system be upgraded in future as per increase in demand forfurther enhancement of the system?

Whats the technical guarantee of accuracy, reliability, ease of access and aboveall data security, once the system is installed?

ECONOMIC FEASIBILITYUnder the study of the Economic Feasibility, we found that the proposed software is

economical from the study done so far. In this respect, Cost Benefit Analysis has been do

so far.

TIME FEASIBILITYGiven our technical expertise, the proposed system will be well implemented into the Hotel

Management System with a period of 4 to 5 months. All the technical staff members and

management will be able to access the system within this stipulated period after the

successful implementation.


15/57

2.3 CHOICE OF PLATFORM :

Programming Language C

C Language is the fourth-generation programming language and integrated development

environment (IDE) is considered a relatively easy to learn and use programming language,

because of its easy and compatibility of development features

C language was derived from procedural system and enables the rapid application

development (RAD) of applications, access to databases using file opening and randonand

serial access of file system that, Data of controls and objects could be accessed.

Because C is known as parent of most of 4GL and their after its further development is

taken as class, object, method based system in C++ , so once this application has

implemented, it must be used for further optimization.


16/57

2.3.1 SOFTWARE USED

Operating System

A standard Windows PC running WINDOW XP C Language and Compiler as Turbo C


17/57

2.3.2 HARDWARE USED

Processor : Window 7

RAM : 2 GB

HDD : 250 GB


18/57

CHAPTER 3 SYSTEM DESIGN

3.1 Design methodology

3.2 Database Design

3.3 Screen Design

3.4 Report Design (Include DFD/ERD/OOAD/Screen Shots/ Reports & Data Base Design)


19/57

3.1 Design methodology

The Hotel Management System will provide the following types of easy-to-use, interactive,

and telephonic interfaces.

The HMS will provide an easy-to-use,Command User Interface (CUI) as part of the

Clerk/Administrators working desktop environment.

The above Hotel Management System interfaces shall help provide the following

functionalities to the users - access to the Hotel Management System to check the schedule,

availability of seats, ticket price and to block, reserve, cancel, and reschedule tickets.

This interface shall provide access, only to the following functionalities, namely,schedule

and check status including any change in the flight timings. The functionality available

through this telephonic interface is limited because of security constraints.The closed

boundary above clearly delineates the system and the environment. The project shows the

interactions between the HMS software and the databases inside the system. There are two

databases internal to the system and which the system maintains. DB-user is the database

containing all the personal information of the registered users of the Hotel Mangement

System . This can be updated by the user by logging in to the system. DB-schedule is a copy

of the database. The latter exists independently and is updated by a rooms scheduler system

which is out of scope of the Hotel Mangement System. DB-schedule is updated with the

latest status of the database whenever there is any change in the latter.DB-schedule gets

updated with this change through a process with which we are not concerned. It is external to

the system and is out of the scope of this SRS. DB-schedule also contains the base prices of

for various rooms numbers. DB-reservations are a database containing information regarding

the number of seats available on each class on different rooms. It has provision for marking

how many of the reserved seats have been blocked but not yet bought.There are three

interfaces, one for the administrator, one for the customer via web and another for the

customer via phone. The administrator can update DB-schedule with any changes in the base

prices of rooms tickets. The system uses a pricing algorithm and dynamically determines the

actual price from this base price depending on the date of reservation vis--vis date of

departure


20/57

Waterfall development

The Waterfall model is a sequential development approach, in which development is seen as

flowing steadily downwards (like a waterfall) through the phases of requirements analysis,

design, implementation, testing (validation), integration, and maintenance.

The basic principles are:

Project is divided into sequential phases, with some overlap and splashback acceptable

between phases.

Emphasis is on planning, time schedules, target dates, budgets and implementation ofan entire system at one time.

Tight control is maintained over the life of the project via extensive writtendocumentation, formal reviews, and approval/signoff by the user and information

technology management occurring at the end of most phases before beginning the next

phase.

The Waterfall model is a traditional engineering approach applied to software engineering. In

the traditional waterfall model of system development, each phase must be completed

before a subsequent phase can commence. Although development of software is not generally

as straightforward as this diagram makes it look, we still need to understand each phase

individually before we can understand how they fit together for a software design project.
http://en.wikipedia.org/wiki/Waterfall_modelhttp://en.wikipedia.org/wiki/Waterfall_model


21/57

Since I have implemented the hotel management system using C Language which is a

procedural language. Therefore, the choice of software development methodology is

Waterfall Model.


22/57

3.3 SYSTEM DESIGN

Software design is both a process and a model. The design process is a sequence of steps that

enable the designer to describe all aspects of the software to be built. Designing software is

not an easy task; it requires creative skill, past experience, a general sense of what makes a

good software and undying

Commitment to quality.

The design model begins by representing the totality of the thing to be built and slowly each

detail is constructed. Following points should be kept in mind before designing software:

The design process should not suffer from tunnel vision. Alternate approachesshould also be considered, judging each based on the requirements of the

problem.

The design should be traceable to the analysis model. Time is short and resources are limited. Design time should be utilized in

representing new ideas and integrating those patterns that already exist.

The structure of the software design should imitate the structure of the problemdomain.

The design should exhibit uniformity and integration. The design should be structures to accommodate changes. Design is not coding and coding is not design. The design should be assessed for quality, as it is being created, not after the

fact.

The design should be reviewed to minimize semantic errors


23/57

Modularity (both in program and data) and the concept of abstraction enable the designer to

simplify and reuse software components. Refinement provides a mechanism for representing

for representing successive layers of functional details. Procedure provides the detail

necessary for algorithm implementation. Information hiding and functional independence

provide heuristics for achieving effective modularity.

Database models are broadly classified into two categories. They are:

Object-based logical models - can be defined as a collection of ideal tools fordescribing data, data relationships, and data constraints.

Record-based logical modelsdescribes the data structures and accesstechniques of a DBMS. There are four types of record-based logical models.

They are the file management system, the hierarchical database system, the

network database system and the relational database system.


24/57

3.4SCREEN DESIGN

SCREEN DESIGN REFERS TO THE SELECTION AND PLACEMENT OF OBJECTS on a screen.The two elements of screen design that viewers are most attuned to be organization and visual

interest. Organization involves deciding how many objects to use, what types of objects to use (text,

images, windows, buttons, video, etc.), and where to place the various objects. Objects should be

placed in logical positions on the screen, for example, the NEXT button should always appear to the

right of the BACK button. Generally we assume that larger items are more significant, items "above"

have primacy over items "below", and "more to come" signals will appear at the bottom

centre or right.


25/57

3.4DATA FLOW DIAGRAM

A data-flow diagram (DFD) is a graphical representation of the "flow" of data through an

information system. DFDs can also be used for the visualization of data processing

(structured design).

On a DFD, data items flow from an external data source or an internal data store to an

internal data store or an external data sink, via an internal process.

A DFD provides no information about the timing or ordering of processes, or about whether

processes will operate in sequence or in parallel. It is therefore quite different from a

flowchart, which shows the flow of control through an algorithm, allowing a reader to

determine what operations will be performed, in what order, and under what circumstances,

but not what kinds of data will be input to and output from the system, nor where the data

will come from and go to, nor where the data will be stored (all of which are shown on a

DFD).


26/57

FIRST LEVEL DATA FLOW DIAGRAM

Registration

Daily Register

Search customer

Updation Details

HotelDatabaseMonitoringSystem

Customer Details

Modifying

Billing details

Deletion Details


27/57

SCREEN SHOTS

MAIN SCREEN


28/57

We Enter The Choice As 1

Registration Of A New Customer In The Hotel


29/57

We Enter The Choici As 2

View Of Daily Entry Register Of The Hotel


30/57


Deletion Of Existing Record


31/57


Searching Of A Record


32/57


33/57


Modifying A Customers Record


34/57


35/57

We Enter Tha Choice As 6

Resturant Billing Of The Customer


36/57


37/57


38/57


Total Bill Of A Customer


39/57


40/57

CHAPTER 4 TESTING AND IMPLEMENTATION

4.1 Testing Methodology (Types)

4.2 Unit Testing4.3 Module Testing

4.4 System Testing

4.5 Alpha/ Beta Testing

4.6 White Box Black Box Testing

4.7 Implementation4.8 Post Implementation


41/57

4.1TESTING AND IMPLEMENTATION

VALIDATION AND VERIFICATION

Validation and verification is a important aspect of software engineering. Verification

refers to the set of activity that ensures that software correctly implemented a specific

function. Validation refers to a different set of activity that ensures that the software that hasbeen built is traceable to customer requirement.

Verification Are we building the project right?

Validation Are we building the right product?

The definition of validation and verification encompasses many of the activity that we

have referred to as software quality assurance (SQA) .

Verification and validation encompasses a wide array of SQA activity that include

formal technical review, quality and configuration audit, performance monitoring, simulation,

feasibility study, documentation review, algorithm analysis, development testing,

qualification testing and installation testing.


42/57

TESTING OBJECTIVES:

Testing is a process of executing a program with the intent of finding an error. A goal test case is one that has a probability of finding an as-yet undiscovered error. A successful test is one that uncovers an asyet undiscovered error.

A systematic and wholly procedural plan for testing was adopted. The procedure while

implementing testing went in hand with preparing a Unit Test plan.

Test the modules thoroughlycover all the access paths. Generate enough data to coverall the access paths arising from conditions.

Test the modules by passing wrong type and number of data items. To test the different access pathslook at the conditional statements (IFs & LOOPs etc).

Enter some data in the test file which would satisfy the condition and again test the

script. Repeat this process many times.

After each test -- analyze the log file to ensure proper, understandable and usefulmessages are present in the log file.

Test for locking by invoking multiple concurrent processes.


43/57

TESTING PRINCIPLE:

All tests should be traceable to customer requirements. Test should be planned long before testing begins. The testing should begin in the small and progress towards testing in the large. Exhaustive testing is not possible. To be most effective, testing should be conducted by an independent third party.


44/57

CHARACTERISTICS OF A GOOD TEST:

A good test has a high probability of finding an error. A good test is not redundant. A good test should be best of breed. A good test should be neither too simple nor too complex.


45/57

TYPES OF TESTING:

4.2UNIT TESTING:

This test involves into the testing of individual module/program, And all programs are

successfully running and giving output according to it requirements.

4.4SYSTEM TESTING:

After success of unit test the complete system is tested. At this stage end user and operators

becomes actively involved in testing. While testing operators also tested discrepancies

between the system and its original objective, current specification and system

documentation.

PERFORMANCE TESTING:

This test referred to the response time of the system being installed. This testing has been

conducted before the implementation to determine how long it takes to receive a response to

an inquiry.

RECOVERY TESTING:

Under this testing Modules / Procedures are written and that are able to store data so that user

can recover their data even after crashing of system.

PROCEDURE TESTING:

This test contains complete instruction to handle to software by the user. i.e. Steps to be taken

to load the program into the memory, and whatever data they require to perform those tasks.


46/57

4.5ALPHA TESTING

Alpha testing is simulated or actual operational testing by potential users/customers or an

independent test team at the developers' site. Alpha testing is often employed for off-the-shelf

software as a form of internal acceptance testing, before the software goes to beta testing.

BETA TESTING:

Beta testing comes after alpha testing. Versions of the software, known as beta versions, are

released to a limited audience outside of the programming team. The software is released to

groups of people so that further testing can ensure the product has few faults or bugs.

Sometimes, beta versions are made available to the open public to increase the feedback field

to a maximal number of future users.

4.6 WHITE BOX TESTING:

White box testing is performed early in the testing process. White box testing is also called

glass-box testing. Using white box testing, the s/w engineer can derive test cases that-----

Guarantee that all independent paths within a module have been exercised at least once. Exercise all logical decisions on their true and false sides. Execute all loops at their boundaries and within their operational bounds. Exercise internal data structure to assure their validity.


47/57

BLACK BOX TESTING:

Black box testing is to be applied during later stages of testing. Black box testing focuses on

the functional requirement of the s/w. The black box testing enables the s/w engineer to

derive sets of input conditions that will fully exercise all functional requirements for a

program. Black box testing attempts to find an error in the following categories.

Incorrect or missing functions Interface errors Errors in data structures or external database access Performance errors Initialization and termination errors.

By applying black box testing a set of test cases that satisfy the following criteria

Test cases that reduce, by a count that is greater than one, the no. of additional testcase must be designed to achieve reasonable testing.

Test cases that tell us something about the presence or absence of classes of errors,rather associated only with the specific test at hand.


48/57

4.7IMPLEMENTATION

A crucial phase in the software design is its implementation. It simply means converting a

new system design into operation. The objective of conversion is to put the tested system into

operation while holding costs, risks and personnel irritation to a minimum. It involves :

Creating computer compatible files. Training the operating staff. Installing terminals and hardware.

A critical aspect of the implementation is not disrupting the functioning of the

organization. It should be exciting because it is the last step before the candidate system

begins to show results. It should be carefully planned otherwise it can turn out to be chaotic

and traumatic as the system breaks down, data files are damaged and tempers grow short.


49/57

EVALUATION:

Operational systems are quickly taken for granted. Every system requires periodic evaluation

after implementation. A post-implementation review measures the system performance

against predefined requirements. Unlike system testing, which determines where the system

fails, an evaluation review determines how well the system continues to meet performance

specifications. It is after the fact - after design and implementation are complete. It also

provides information to determine whether major redesign is necessary.

The evaluation team prepares a formal evaluation plan around the objective(s) of the review,

the type of evaluation to be carried out, and the time schedule required. An overall plan

covers the following areas:

1. Administrative PlanEvaluates area objectives, operating costs, actual operatingperformance and benefits.

2. Personnel Requirement PlanEvaluates performance objectives and trainingperformance to date.

3. Hardware PlanEvaluates performance specification.4. Documentation Evaluation PlanReviews the system development effort.


50/57

MAINTENANCE:

Maintenance is the enigma of system development. It holds the software industry captive,

tying up programming resources. Maintenance can be classified as corrective, adaptive or

perceptive.

Corrective Maintenancemeans repairing processing or performance failures or making

changes because of previously uncorrected problems or false assumptions.

Adaptive Maintenance means changing the program function.

Perceptive Maintenancemeans enhancing the performance or modifying the program(s) to

respond to the users additional or changing needs.

Of these more time and money is spent on perceptive than on corrective and adaptive

maintenance together.

Maintenance is expensive. One way to reduce maintenance costs is through

maintenance management and software modification audits. Software modification consist of

program rewrites system level updates, and reaudits of low ranking programs to verify andcorrect the soft spots. The outcome should be more reliable software, a reduced maintenance

backlog, higher satisfaction and morale among the maintenance staff.


51/57

CHAPTER 5 CONCLUSION AND REFERENCES

5.1 Conclusion

5.2 Limitation of System

5.3 Future Scope for Modification5.4.1 H/W Requirement

5.4.2 S/W Requirement

5.5 References/ Bibliography


52/57

5.1CONCLUSION AND REFERENCE

LIMITATIONS AND CONSTRAINTS

Following could be the few possible barriers of Hotel Database Monitoring System:

Apprehension that the technology could be too expensive The staff will have to undergo extensive training. Lack of support from the management, may be owing to budget constraintsA close examination each of the points is presented now.

If we analyze the various jobs one can conclude that human interference is necessary at each

and every step. The manpower is thus saved. Therefore, there will be no adverse impact on

employment. There is an apprehension that the technology, both hardware and software

would be expensive and unaffordable. The cost of hardware and software depends on the

level of automation.

The in-house training for handling the software is usually provided by the developers.

The training of staff also depends on the level of automation. If one decides to go only for

cataloguing a minimum training of one or two weeks duration will enable the department or

new operators to develop a database and maintain it. With this basic training one can easily

transfer the same data on a server/main machine in a network environment. The job becomes

easy as most of the institutions have systems department with computer professionals

maintaining the network.


53/57

Lack of support from the management, may be owing to budget constraints, will be

one of the barriers. Here the role of operators becomes crucial in convincing the management.

Also, the skill and initiative play a major role in convincing the management.


54/57

5.1CONCLUSION:

The HOTEL MANAGEMENT SYSTEM is a great improvement over the manual system

using case fields and paper. The computerization of the system has sped up the process. In the

current system, the front office managing is very slow. The hospital managing system was

thoroughly checked and tested with dummy data and thus is found to be very reliable.

ADVANTAGES:

It is fast, efficient and reliable Avoids data redundancy and inconsistency Very user-friendly Easy accessibility of data Number of personnel required is considerably less Provides more security and integrity to data


55/57

5.3FUTURE SCOPE OF MODIFICATION

This all information has to be managed manually. So, there is a need to develop a system that

can solve the mentioned problem. This software comes with just that solution.

Also, it provides freedom from the paper work involved in manual operation and thus

from the amount of storage required to keep them. It also provides security as data security is

maintained to relatively high level by implementing it at Database level, so as to ensure that

only authorized users have access to confidential client information.


56/57

5.4.2SOFTWARE REQUIREMENT:

Operating System

A standard Windows PC running WINDOW XP/ VISTA

Front endC language

Back endFile system


57/57

5.5BIBLIOGRAPHY:

To present the Hotel ManagementSystemwith a large number of interesting and useful

features, I had gone thoroughly a number of books. These books proved helpful in adding

special facilities and gave detailed help regarding c and its special features.

System Analysis and Design by V.K JainANSI C (Bal guru swami)Let us C by Yashwant KanetkarC in depth for various theoretical concepts to be applied wherever

needed, in the whole system.

Dennis Ritchie.

Documents

Hotel Aditi (m)[1]