Journal

ABSTRACT
During the past several decades personnel function has been transformed from a relatively obscure record keeping staff to central and top level management functions. There are many factors that have influenced this transformation like technological Advances, professionalism, and general recognition of human beings as most important resources. These were the main reasons which led us to develop an autonomous system for hotel management. The work of hotel management i.e. keeping all the records up to date by manually entering the records in registers is likely to be not error prone and the work is tiresome. The main features implicated in this management system are A computer based management system is designed to handle the entire primary Information required to calculate monthly statements. Separate database is maintained to handle all the details required for the correct statement calculation and generation. This project intends to introduce more user friendliness in the various activities such as record updating, maintenance, and searching. The searching of record has been made quite simple as all the details of the customer can be obtained by simply keying in the identification of that customer. Similarly, record maintenance and updating can also be accomplished by using the identification of the customer with all the details being automatically generated. These details are also being promptly automatically updated in the master file thus keeping the record absolutely up-to-date. The entire information has maintained in the database or Files and only authorized user can retrieve the necessary information which can easily be accessible from the file.
Department of Computer science & Engineering Nagaland university
Page 1
The main objective of the entire activity is to automate the process of day to day activities of Hotel like: 1. Room activities. 2. Admission of a New Customer. 3. Assign a room according to customers demand. 4. Checkout of a computer and releasing the room. 5. Finally compute the bill etc. 6. Packages available. 7. Advance online bookings. 8. Online Cancellation. 9. List of Regular customers. This project has some more features: System Connectivity No data duplication No Paper Work Required Time Efficient Cost Efficient Automatic data validation User friendly environment Data security and reliability Fast data insertion & retrieval Easy performance check
Page 2
ADVANTAGE: We have designed the given proposed system in the .Net Environment to automate the process of Hotel management. This project is useful for the authorities who keep track of all the users registered in a particular state .The authority can add hotel packages, room details, availability of rooms, online booking etc. system are:
The following steps that give the detailed information of the need of proposed Performance: During past several decades, the records are supposed to be manually handled for all activities. The manual handling of the record is time consuming and highly prone to error. To improve the performance of the Hotel
Management System, the computerized system is to be undertaken. This project is report and status of the company.
fully computerized and user friendly even that any of the members can see the Efficiency: The basic need of this website is efficiency. The website should be efficient so that whenever a new user submits his/her details the website is updated automatically. This record will be useful for other users instantly.
Control: The complete control of the project is under the hands of authorized
person who has the password to access this project and illegal access is not
supposed to deal with. All the control is under the administrator and the other members have the rights to just see the records not to change any transaction or entry. Security: Security is the main criteria for the proposed system. Since illegal access may corrupt the database. So security has to be given in this project.
Page 3
CHAPTER 1-
INTRODUCTION
Page 4
1.
INTRODUCTION
We have tried our best to make the complicated process of Hotel Management System as simple as possible using Structured & Modular technique & Menu oriented interface. We have tried to design the software in such a way that user may not have any difficulty in using this package & further expansion is possible without much effort. Even though we cannot claim this work to be entirely exhaustive, the main purpose of our exercise is to perform each Employees activity in computerized way rather than manually which is time consuming.
1.1) ABOUT THE PROJECT

Hotel management system is a web application system which is designed keeping in mind the application of autonomous system and the tiresome work of manual hotel management. Hotel needs to maintain the record of guests and reserve rooms beforehand. Customers should be able to know the availability of the rooms for a particular date. They should be able to reserve the available rooms according to their needs in advance. To make their stay comfortable, they are provided with food and other services. The record of the food taken by each customer and the services availed by the customer should be kept. These records will be retrieved during generating bill. The management work in a hotel is very tedious and tiresome work, maintaining all the records in registers, computing bills manually, reading and searching the data for some particular record manually in a large set of registers. These problems give rise to the implication of using a hotel management system which can perform this entire task in much shorter time and very much efficiently. This Hotel management System deals with all the necessary functions of a hotel, like lodging details, fooding details, customer record, etc.
Page 5
Assumptions:
This application is used to convert the manual application to the computerized application. Customized data will be used in this application. Employees does not have full access rights for e.g. to add or delete the services.
Maintaining authorization of usersWe are confident that this software package can be readily used by non-programming personal avoiding human handled chance of error. This project is used by two types of users, each of them have different authorization rights and can login only through their own password. The two types of users provided in this system arei. Front Desk Users. (Employees of the hotel) ii. Administrator (management of the Hotel). Front desk users are those employees of the hotel who will use this system to store data in the record, they have limited access and they are not allowed to modify the data from the database. Front desk users have their independent account with their unique login username and password. Only authorized users will be able to use the system to do the general operations of a hotel management and for viewing the data. Administrator can maintain daily updates in the hotel records. Administrator must be an authorized user with a unique login password. He/she can further change the password. There is the facility for password change, logout etc. administrators have full authority and privileged in modifying the data from the database.
Page 6
1.2)
Functionality of the system-
The main aim of the entire activity is to automate the process of day to day activities of Hotel like Room activities, Admission of a New Customer, Assigning room according to customers demand, checkout of a customer, releasing the room and finally compute the bill etc. The limited time and resources have restricted us to incorporate, in this project, only main activities that are performed in a HOTEL MANAGEMENT SYSTEM, but utmost care has been taken to make the system efficient and user friendly. HOTEL MANAGEMENT SYSTEM has been designed to computerize the following functions that are performed by the system: Room Detail Functions Adding or deleting Room Modification to room assigned Check-in and check-out Detail Functions Admission of New customer Customer Details for future reference Room assigning related to customers need. Statement of Customer Details Check-in customer Check-out customer Room Details Food Details Computation of bill. Total number of Customers in the Hotel Individual customer Report Modification of hotel details
Page 7
1.3 PROJECT CATEGORY

This Project is coupled with material on how to use the various tool, sub sets available in Microsoft .net. The need of todays software development is competence in a GUI based front-end tool, which can connect to Relational Database engines. This gives the programmer the opportunity to develop client server based commercial applications. These applications give users the power and ease of a GUI with the multi user capabilities of WinNT based RDBMS engines such as MS SQL. All the important coding techniques used by programmers, in OOPS based coding is brought out in full and in great detail. A database system is essentially a sophisticated, computerized record keeping system, a repository for a collection of computerized data files. A database system maintains information and makes that information available on demand, for this purpose a database system provides set of facilities to perform such operations. The benefits of a database system over any traditional system are obvious as database is integrated as well as shared, thus a database eliminates redundancy and also as a consequence, database lets multiple users access the same piece of data. The most important advantage of the database is to maintain the integrity i.e. it ensures that the change made to the database by authorized users do not result in a loss of data consistency and guard against accidental damage to the database.
TOOLS / PLATFORMS & LANGUAGE USED ->
FRONT END: BACK END: OPERATING SYSTEM:
ASP .NET MS SQL WINDOWS VISTA 2008
Page 8
CHAPTER 2-
THE PROJECT PLAN
Page 9
2. PROJECT PLAN2.1 INTRODUCTION Underpinning this approach is the concept that the project should be planned, initially at a high level for the entire duration and this plan should be reviewed at the end of each phase with detailed planning being done for the subsequent phase. The plan should be presented as a Giant chart with the major tasks of each phase being identified and an estimated duration placed against each. One of the final tasks at the end of each phase is to 'review' the current phase. Depending on what the phase is this may involve a walkthrough of the data model with an independent practitioner, or a walkthrough of the Requirements List with the sponsor. The plan should be re-negotiated at the end of each phase by the sponsor and the developer. By making the plan a phase deliverable, it ensures that both developer and sponsor are aware of any project slippage and/or creeping functionality changes.
Page 10
2.2 THE METHOD

THE PROJECT PLAN
Phase
Phase 1
Task Analysis Design
Description
Analyses the need of the Desired System, the limitations of the existing system. Analyses the plan to develop the project on the basis of the requirements Design the project plan in the form of DFD, flow chart, ER diagram. Design The overview of the System before actually starting the Coding. Implementing the system for use. The phase deals with the implementation job of developing the system.
The Development phase creates the system software. The phase commences with the data model, probably from the prototype, adds system queries, followed by forms and reports. Code is added last.
Phase 2
Phase 3
Implementation
Phase 4
Development
Phase 5
Integration
Integrate the Final Code segments together to make the complete project. Combine all the small units or the segments of the project together and design the final project. Test the completed project against the requirements provided at the time of analysis phase. Test for the successful completion and any types of errors.
Phase 6
Testing
Page 11
2.3
PROJECT AGGRESSION
Naturally, not every project activity follows a linear sequence. Some phases can be done in parallel. The details of the particular project need to be worked out, but the following general route map may be helpful:
Feasibility
Analysis
Prototyping
Design
CHAPTER 3
Developmen t
Testing
Page 12
Chapter 3-
LITERATURE SURVEY (SYSTEM ANALYSIS)
Page 13
3. LITERATURE SURVEY
3.1 SYSTEM ANALYSIS System Analysis is a detailed study of the various operations performed by a system and their relationships within and outside of the system. Here the key question is- what all problems exist in the present system? What must be done to solve the problem? Analysis begins when a user or manager begins a study of the program using existing system. During analysis, data collected on the various files, decision points and transactions handled by the present system. The commonly used tools in the system are Data Flow Diagram, interviews, etc. Training, experience and common sense are required for collection of relevant information needed to develop the system. The success of the system depends largely on how clearly the problem is defined, thoroughly investigated and properly carried out through the choice of solution. A good analysis model should provide not only the mechanisms of problem understanding but also the frame work of the solution. Thus it should be studied thoroughly by collecting data about the system. Then the proposed system should be analyzed thoroughly in accordance with the needs. System analysis can be categorized into different parts. System planning and initial investigation Information Gathering Applying analysis tools for structured analysis Feasibility study Cost/ Benefit analysis.
Department of Computer science & Engineering Nagaland university Page 14
PRINCIPLES OF SYSTEM ANALYSIS 1. Understand the problem before you begin to create the analysis model. interaction will occur.
2. Develop prototypes that enable a user to understand how human machine 3. Record the origin of and the reason for every requirement. models.
4. Use multiple views of requirements like building data, function and behavioral 5. Work to eliminate ambiguity. The analysis phase of this project Hotel management system, deals with
collecting the required information about the functionality of hotels by surveying the data from nearby hotels as well as from the online websites of the hotels. Determining the problems with the existing system and users demand are of prime concern in this phase. The working of this phase can be categorized in the following sub-phases.
SYSTEM STUDY & ANALYSIS

3.1.1 Existing System
The existing hotel management system makes use of manual data entry, The search operation is done manually through all the data registers. calculation or by using calculator. which is entered by the employee in the registers.
The bill is generated and computed manually by the employee, by rough Highly cost effective and time consuming. employees.
The data registers contains all data and can be accessed by all the
Page 15
3.1.2 Problems with the Existing system

The manual data entry is very tiresome and time consuming. registers to search for the data. consuming. Search operation is a nightmare, where employee has to go through data The manual generation of bill may result in incorrect data, and its time Data security is compromised due to the fact that anyone who is an employee of that hotel can access and manipulate the data.
3.1.3 Proposed System

Proposed system is an automated Hotel Management System. Through our software user can do room allocation, Check in, Checkout, Automatic computation and generation of bill, keep record of all services and other functionalities of a hotel. Administrator can add or delete records, manage the daily works of a hotel and control all the activities going on in the hotel management. Our proposed system has the following advantages. User friendly interface Fast access to database Less error More Storage Capacity Search facility Look and Feel Environment Quick transaction
Page 16
3.1.4 Advantages of proposed system

Low cost and less time consuming. system.
Records will be stored and modified much more easily than the manual Computation of bill is quick and correct. Data and system are secure, only privileged users can use the system. Backup of data will provide the security of records in case of any accident.
Less human dependent system, only one user can work very easily and efficiently and can operate many operations. All the manual difficulties in managing the Hotel have been rectified by implementing computerization.
3.2 FEASIBILITY ANALYSIS

Feasibility is the study of impact, which happens in the organization by the development of a system. The impact can be either positive or negative. When the positives nominate the negatives, then the system is considered feasible. Here the feasibility study can be performed in two ways such as technical feasibility and Economical Feasibility.
Page 17
3.2.1 Technical Feasibility: We can strongly says that it is technically feasible, since there will not be much difficulty in getting required resources for the development and maintaining the system as well. All the resources needed for the development of the software as well as the maintenance of the same is available in the organization here we are utilizing the resources which are available already.
3.2.2 Economical Feasibility: Development of this application is highly economically feasible .The organization needed not spend much money for the development of the system already available. The only thing is to be done is making an environment for the development with an effective supervision. If we are doing so, we can attain the maximum usability of the corresponding resources .Even after the development, the organization will not be in a condition to invest more in the organization. Therefore, the system is economically feasible.
Page 18
3.3 FUNCTIONALITY REQUIREMENTS

The hotel reservation system should be able to satisfy the following requirements: allotted to them. date. 1. The system should be able to keep the records of the guests and the room 2. Customers should be able to know the availability of the rooms on a particular 3. Guests should be able to book the available rooms according to their choice. 4. The record of food and services availed by the customer should be kept. 5. The system should be able to generate the bill for a customer. 6. The records of customer must be saved for any future reference. 8. The daily records must be generated each day for Admin use.
7. The Administrator should be able to add or delete data from the record. 9. The system should be secure, only authorized persons can use the system.
Page 19
3.4 SYSTEM REQUIREMENTS SPECIFICATION

3.4.1 SOFTWARE REQUIREMENTS Visual Studio (2005 /2008) MS SQL Server 2005 Web Browser(Internet Explorer/ Mozilla Firefox/ Any other)
3.4.2 HARDWARE REQUIREMENTS

PROCESSOR RAM MONITOR HARD DISK : : : : PENTIUM IV 2.6 GHz 512 MB DD RAM 15 COLOR 20 GB
Page 20
CHAPTER 4-
SYSTEM DESIGN
Page 21
4. SYSTEM DESIGN
4.1 System Design Overview
system. The system design stage is one of the important stages that deal with the design specification and the actual working of the system. The system design is the stage where the real working of the system, the relation An efficient system design is necessary to develop a working
between different modules of the system and the connection of the database Data flow diagram, flow chart or the Entity relationship diagram.
is realized and designed in the form of different designing standards like The system design stage starts as soon as the analysis phase
completes. On the basis of the report generated from the analysis phase, the structured and diagrammatic design of the system is prepared. The main is required to be developed before the developer starts any work. aim of this phase is to let the developer completely understand what exactly The working of the hotel management system requires a
perfect management and correlation among the different modules of the system. To design an efficient system, an efficient system design must be the system Design is that, without any designs ready beforehand the system designer will not be able to make the project, the relations of entities in the the system. completed before the actual starting of the system development. The need of
database and in the front end might vary which will result in the failure of
Page 22
INPUT DESIGN:
Input design is the process of converting user-oriented input to a computer based format. Input design is a part of overall system design, which requires very careful attention. Often the collection of input data is the most expensive part of the system. The main objectives of the input design are 1. Produce cost effective method of input 2. Achieve highest possible level of accuracy 3. Ensure that the input is acceptable to and understood by the staff.
The goal of designing input data is to make enter easy, logical and free from errors as possible. The entering data entry operators need to know the allocated space for each field; field sequence and which must match with that in the source document. The format in which the data fields are entered should be given in the input form .Here data entry is online; it makes use of processor that accepts commands and data from the operator through a keyBoard. The input required is analyzed by the processor. It is then accepted or rejected.
Page 23
Input stages include the following processes Data Recording Data Transcription Data Conversion Data Verification Data Control Data Transmission Data Correction
One of the aims of the system analyst must be to select data capture method and devices, which reduce the number of stages so as to reduce both the changes of errors and the cost. Input types, can be characterized as. External Internal Operational Computerized Interactive
Input files can exist in document form before being input to the computer. Input design is rather complex since it involves procedures for capturing data as well as inputting it to the computer.
Page 24
OUTPUT DESIGN:
Outputs from computer systems are required primarily to communicate the results of processing to users. They are also used to provide a permanent copy of these result for latter consultation .Computer output is the most important and direct source of information to the users. Designing computer output should proceed in an organized well throughout the manner. The right output must be available for the people who find the system easy o use. The outputs have been defined during the logical design stage. If not, they should defined at the beginning of the output designing terms of types of output connect, format, response etc. Various types of outputs are External outputs Internal outputs Operational outputs Interactive outputs Turn around outputs All screens are informative and interactive in such a way that the user can full fill his requirements through asking queries.
Page 25
DATABASE DESIGN:
The general theme behind a database is to handle information as an integrated whole. A database is a collection of interrelated data stored with minimum redundancy to serve many users quickly and effectively. After designing input and output, the analyst must concentrate on database design or how data should be organized around user requirements. The general objective is to make information access, easy quick, inexpensive and flexible for other users. During database design the following objectives are concerned: Controlled Redundancy Data independence Accurate and integrating More information at low cost Recovery from failure Privacy and security Performance Ease of learning and use
Page 26
4.2 System applications

the implementation phase. The hotel management system needs to have The hotel management system needs to be properly designed before
different access rights for different types of users. In this system two different types of users are:- F-desk user and Administrator. The different functionality of the system depends on the approach of the design. The functions of the hotel management must be properly linked with each other as well as with the database. The database is required to be properly connected with the system modules so that the changes can be directly updated in the system as soon as the modification is done.
data directly from the database, which gives the security to data. The user to be stored for any future reference. The room allotted the services provided to the customer; etc is recorded in the database for automatic generation of generated for all these services. the bill. The customer gets all the facilities that are demanded and the bill is
The F-desk user does not have the access rights to modify the
can access the system for daily working of a hotel. The customer details have
unlimited. The admin is permitted to modify the data, add or delete the records and to provide a login to other employees. The database can be directly retrieved by the system to view the data or to make changes.
The administrator is the owner of the system. The access rights are
Page 27
4.3 Design methods and Overview4.3.1 ENTITY RELATIONSHIP DIAGRAM (ERD)Entity Relationship Diagram: This depicts relationship between data objects. diagram can be described using a data object description. Data flow 1. To provide an indication of how data are transformed as they move 2. To depict the functions that transformation the data flow. Data Objects: A data object is a representation of almost any composite through the system. diagram serves two purposes: The attribute of each data objects noted in the entity- relationship
information that must be understood by the software. By composite information, we mean something that has a number of different reference within a data object to operations that act on the data. properties or attributes. A data object encapsulates data only there is no
Attributes: Attributes define the properties of a data object and take on one of three different characteristics. They can be used to: Name an instance of data object. Describe the instance.
Make reference to another instance in other table.
Page 28
CARDINALITY AND MODALITY:

The data model must be capable of representing the number of occurrences of objects in a given relationship. The cardinality of an object relationship pair is occurrence of object B and vice versa. One-T0-One (1:1): An occurrence of object A can relate to one and only one One-To-Many (1:N): One occurrence of object A can relate to one or may occurrence of object A. Cardinality:
occurrences of object B but an occurrence of object B can relate to only one Many-To-Many (M: N): An occurrences of B and an occurrence of B can relate to one or many occurrence of A. Modality:
The modality of a relationship is zero if there is no explicit need for the relationship to occur or the relationship is optional. The Modality is one if the occurrence of the relationship is mandatory. The object relationship pair can be represented graphically using the Entity Relationship Diagrams. A set of primary components are identified for the Entity Relationship Diagram, 1. Attributes, 2. Relationships and
3. Various Type Indicators.
The primary purpose of the Entity Relationship Diagram is to represent data objects and their relationships.
Page 29
4.3.2 DATAFLOW DIAGRAM (DFD)

A data flow diagram (DFD) is graphic representation of the "flow" of data through business functions or processes. More generally, a data flow diagram is used for the visualization of data processing. It illustrates the processes, data stores, external entities, data flows in a business or other system and the relationships between them.
4.3.3 FLOW CHART

Flow charts are used to describe the basic flow of data in a system. The operation of a particular function can be best understood by designing a flow chart for the function. The predefined symbols are used to describe the various operations being performed on the system. The flow chart simply describes the basic flow of control in a function.
Page 30
DATA FLOW DIAGRAM

CONTEXT LEVEL DFD HOTEL MANAGEMENT SYSTEM USER CUSTOMER
HOTEL MANAGEMENT SYSTEM
CUSTOMER CHECKOUT
PRINT DEVICE
Page 31
DATA FLOW DIAGRAM CHECK- IN OF A NEW CUSTOMER

CUSTOMER
1. SELECT NEW ROOM NUMBER
FILE
1.1 DISPLAY FORM
PROCESS
1.2 GET DETAILS
UPDATE TABLE
CUSTOMER DOCUMENT
1.4 UPDATE 1.3 OPEN ROOM
Page 32
CHECK-OUT OF CUSTOMER
USER
SELECT CUSTOMERS ROOM NUMBER
FILE
1.1 DISPLAY FORM
UPDATE TABLE
PROCESS
CUSTOMER DETAILS
1.3 UPDATE
1.2 GET DETAILS
Page 33
RECORD MODIFICATION
USER
READ THE RECORD
SCAN RECORD
2. SHOW THE DETAILS OF RECORD
FILE
PROCESSING UPDATE
3.
MODIFY
Page 34
GENERATING BILL OF CUSTOMER
SCAN MANGEMENT
1.READ ROOM NUMBER
FILE
PROCESSING
2. CHECK FOR CHECKOUT
3. COMPUTE BILL
4. CLOSE DATABASE
UPDATE CASH
MANGEMENT
Page 35
LIST OF ALL RECORDS MANGEMENT

1.READ THE REQUEST
FILE
2. SELECT RECORD FROM FILE
3. COPY SELECTED RECORD
Processing
4. COMPUTE TOTAL 6. COPY SELECTED RECORD 5. SELECT RECORD
output
Processing
7. COMPUTE TOTAL 8. GENERATE TOTAL LIST
Final Output
To Screen
OUTPUT UNIT
Page 36
FLOW CHART
1. LOGIN FORM
START
USERNAME=ADMINISTRATOR USERNAME=USER PASSWORD=
IF USERNAME= ADMINISTRATOR
NO
USERNAME= USER
YES
ENTER THE PASSWORD
IF CORRECT PASSWORD
NO
DISPLAY INCORRECT PASSWORD
YES
CLICK WELCOME BUTTON
LOAD MDI FORM
Page 37
2. GENERATE BILL FORM

start
Select generate bill option
Select room number
Select generate bill option
Retrieve billing detail from database
Print Billing Information
Page 38
3. GUEST ENTRY FORM

START
CHECK FOR AVAILABILITY
SELECT ROOM AVAILABLE FILL FORM
Room booking form Is loaded
Add the customer information
ADD THE BOOKING INFORMATION
Click submit button
NO
If any entry is empty

YES
Display room is booked
UPDATE DATABASE
Display please fill the entry Department of Computer science & Engineering Nagaland university
Page 39
4. ADD ENTRIES FORM

Start
Enter the entries for the new room/ food item
If room /food item
YES
Enter another
exist
room no./ food item
NO
This record set is stored in database
Page 40
5. DELETE ENTRIES FORM

START
Select room no./ fooding item
Click on delete button
Display are u sure u want to delete this room
If YES Or NO
NO
No record is deleted
YES
Record deleted successfully
Page 41
6. CHECKOUT FORM
Start
Select the Room number
Generate Bill
Bill Paid?
NO
Collect the payment
YES
Click Checkout Button
CHECKOUT SUCCESSFUL
Page 42
ENTITY- RELATIONSHIP DIAGRAM (ER)
HOTEL
CUSTOMER
ROOM INFORMATION
CHECKIN
ROOM
Page 43
ER DIAGRAM HOTEL
ROOM RECORD
CUSTOMER
CUSTOMER
CHECKOUT
ROOM
BILL GENERATION
HOTEL
Page 44
Page 45
WORKING OF HOTEL MANAGEMENT SYSTEM
Page 46
LAYOUT OF HOTEL MANAGEMENT SYSTEM
Page 47
STRUCTURE OF HOTEL MANAGEMENT SYSTEM

HOTEL MANAGEMENT SYSTEM HOTEL NAME HOTEL ADDRESS ROOM -Type -Rate -Status -Room Id + Update room status + Check Availability HOTEL OWNER OWNER NAME OWNER PHONE No. E-MAIL CUSTOMER -NAME -Address -ID Type & Number -Phone Number + Add Customers Info
USER -UserName -Password -Name + Update Login Time
Food & Services -Service Id -Service rate -Item Qty + Update order
ADMINISTRATOR + Maintain room + Maintain F-desk user +Update Hotel Details +Maintain Services offered +View and Update records
F-DESK USER +Perform CheckIn/Checkout +Maintain Payment +Maintain Order Details
PAYMENT -Payment mode -Amount -Date -Payee Name + Retrieve Billing Info +Update Payment details +
RESERVATION -Checkin Time -CheckIn Date -No. Of Occupants -Room Number +Maintain Reservation +Update room Availability + Maintain Billing details + Maintain customer details
Page 48
4.4 DATA MODELLING

Data modeling defines primary data objects, composition of each data object, and between objects and the processes. 1. Field AdminId UName Name Pass Added On Added By LastLogin IsActive 2. Fields CustomerId CName Caddress CPhone EnteredBy EnteredOn IdType IdNo. Type Numeric(18,0) Varchar(150) Varchar(200) Varchar(11) Varchar(50) DateTime Varchar(50) Varchar (50) NotNull NotNull Type Numeric(18,0) Varchar(50) Varchar(100) Varchar(50) Datetime Varchar(50) Date time SmallInt CUSTOMER TABLE contraint NotNull NotNull NotNull NotNull Description The Id of the customer Name of the customer Address of the customer Phone number of customer Name who entered the details Time of entry Id type provided Number of the Id and attributes of the object, relationships between each object and other objects ADMIN TABLE constraint NotNull NotNull NotNull NotNull Description The Id of the administrator The username to be displayed The name of the admin Password to login Date when the Admin was added Existing Admin who added Time of last login Is allowed to login or not
Page 49
3. Fields BookingId RoomId CustomerId FromDate ToDate BookedBy BookedOn CheckedOut AmtPaid Adult Children 4. Field FDeskId UName Name Pass Added On Added By LastLogin IsActive Type Type
BOOKING TABLE Constraint NotNull NotNull NotNull NotNull NotNull Description The booking id The id of the room allotted The id of the customer Reserved from date Reserved till date Employee who booked Booking time NotNull NotNull NotNull NotNull Whether checkedout or not The amount to be paid No. of adults No. of childrens
Numeric(18,0) Numeric(18,0) Numeric(18,0) Datetime Datetime Varchar(50) DateTime SmallInt Numeric(10,2) Numeric(2,0) Numeric(2,0)
F-DESK TABLE constraint NotNull NotNull NotNull NotNull Description The id of the F-desk user The username of the user The name of the user The password of the user The date when user was added The admin who added NotNull The time of last login Whether active or not
Numeric(18,0) Varchar(50) Varchar(100) Varchar(50) Datetime Varchar(50) Date time SmallInt
Page 50
5. Fields FoodingId FoodId BookingId Orderedon IsPaid DishNo DishAmt Type
FOODING TABLE constraint Notnull NotNull Notnull Description The serial number of order The id of the item ordered The booking id Time when it was ordered Whether amount paid or not NotNull NotNull Number of dishes ordered The amount of dish ordered
Numeric(18,0) Numeric(18,0) Numeric(18,0) Datetime SmallInt Numeric(3,2) Numeric(7,0)
6. Fields RoomId RoomNo Rent Type Details Booked AddedOn AddedBy IsDeleted Type
ROOM TABLE
constraint NotNull NotNull NotNull NotNull
Description The id of the room The room number The rent of the room Type of the room Details if any Whether booked or not Date when the room added who added the room Whether room is deleted
Numeric(18,0) Varchar(50) Numeric(7,2) Varchar(50) Varchar(200) SmallInt DateTime Varchar(50) SmallInt
Page 51
7. Fields FoodId Details Amount IsDeleted AddedOn AddedBy
FOOD TABLE Type Varchar(150) Numeric(7,2) SmallInt Datetime Varchar(50) NotNull constraint Description The id of the food item Details if any Amount of the dish Whether record deleted Date when record is added Who added the record
Numeric(18,0) NotNull
8. Fields Name Address OwnerName Phone Email EnteredOn EnteredBy STax PhotoUrl Type
HOTEL DETAILS TABLE
constraint Notnull NotNull NotNull NotNull NotNull
Description The name of the hotel The hotel address The name of the owner Phone number of the owner Email of the owner Date records were added Records added by
Varchar(150) Varchar(200) Varchar(100) Varchar(11) Varchar(150) Datetime Varchar(50) Numeric(4,2) Varchar(150)
NotNull
Service tax applied url of the phoyo if any
Page 52
CHAPTER 5SYSTEM IMPLEMENTATION
Page 53
5. SYSTEM IMPLEMENTATION
5.1 INTRODUCTION Implementation is the stage in the project where the theoretical design is turned into a working system. The implementation phase constructs, installs and operates the new system. The most crucial stage in achieving a new successful system is that it will work efficiently and effectively. There are several activities involved while implementing a new project they are End user training End user Education Training on the application software System Design Parallel Run And To New System Post implementation Review
End user Training: The successful implementation of the new system will purely upon the involvement of the officers working in that department. The officers will be imparted the necessary training on the new technology.
Page 54
End User Education: The education of the end user start after the implementation and testing is over. When the system is found to be more difficult to understand and complex, more effort is put to educate the end used to make them aware of the system, giving them lectures about the new system and providing them necessary documents and materials about how the system can do this.
Training of application software: After providing the necessary basic training on the computer awareness, the users will have to be trained upon the new system such as the screen flows and screen design type of help on the screen, type of errors while entering the data , the corresponding validation check at each entry and the way to correct the data entered. It should then cover information needed by the specific user or group to use the system.
Post Implementation View: The department is planning a method to know the states of the past implementation process. For that regular meeting will be arranged by the concerned officers about the implementation problem and success.
Page 55
5.2 MICROSOFT .NET OVERVIEW
5.2.1
MICROSOFT .NET DESCRIPTION
Microsoft.NET is product suite that enables organizations to build smart, strategy, whereas J2EE is a standard to which products are written.
enterprise-class web services. Note the important difference: .NET is a product Microsoft.NET is largely a rewrite of Windows DNA, which was Microsoft's previous platform for developing enterprise applications. Windows DNA includes many proven technologies that are in production today, including Microsoft the Microsoft SQL Server database. Transaction Server (MTS) and COM+, Microsoft Message Queue (MSMQ), and The new .NET Framework replaces these technologies, and includes a web
services layer as well as improved language support. The .NET application is hosted within a container, which provides qualities of service necessary for The business layer of the .NET application is built using .NET managed enterprise applications, such as transactions, security, and messaging services. components. This layer performs business processing and data logic. It connects to databases using Active Data Objects (ADO.NET) and existing systems using services provided by Microsoft Host Integration Server 2000, such as the COM
Transaction Integrator (COM TI). It can also connect to business partners using web services technologies (SOAP, UDDI, WSDL). Business partners can connect with the .NET application through web services technologies (SOAP, UDDI, WSDL, BizTalk). Traditional 'thick' clients, web browsers, wireless devices connect to Active Server Pages (ASP.NET) which render user interfaces in HTML, XHTML, or WML. Heavyweight user interfaces are built using Windows Forms.
Page 56
5.2.2 The .NET Framework

Microsoft.NET offers language-independence and language-interoperability. This is one of the most intriguing and fundamental aspects of the .NET platform. A single .NET component can be written, for example, partially in VB.NET, the .NET version of Visual Basic, and C#, Microsoft's new object oriented programming language.
How does this work?
First, source code is translated into Microsoft Intermediate Language, sometimes abbreviated as MSIL, and Sometimes IL. This IL code is language-neutral, and is analogous to Java byte code. The IL code then needs to be interpreted and translated into a native executable. The .NET Framework includes the Common Language Runtime (CLR), analogous to the Java Runtime Environment (JRE), which achieves this goal. The CLR is Microsoft's intermediary between .NET developers' source code and the underlying hardware, and all .NET code
ultimately runs within the CLR. This CLR provides many exciting features not available in earlier versions of Windows DNA, such as automatic garbage by- side" execution of different versions of the same .NET component. collection, exception handling, cross-language inheritance, debugging, and "side-
Page 57
5.2.3 .NET SERVERS

The .NET platform includes the following .NET Enterprise Servers. Many of these are repackaging of existing products under a common marketing term: SQL Server 2000 is Microsoft's relational database.
Exchange 2000 Server is a messaging and collaboration platform useful in Windows 2000.
developing and running core business services and is now tightly integrated with Commerce Server 2000 offers you quicker and less complicated development and deployment of customizable online e-commerce solutions. clustered servers. Application Center Server 2000 Application Center Server 2000 lets you manage Host Integration Server 2000 Host Integration Server 2000 gives you access to selected legacy systems running on other platforms (primarily IBM-based). caching capabilities. Internet Security and Acceleration (ISA) Server 2000 offers firewall and Web BizTalk Server 2000 is Microsoft's XML-based collaborative e-business solution for integrating applications, trading partners and business processes via the Internet.
Page 58
5.2.4 .NET ADVANTAGES

.NET has Microsoft's A-team marketing it mindshare
.NET released their web services story before J2EE did, and thus has some .NET has a better story for shared context today than J2EE .NET has an awesome tool story with Visual Studio.NET be productive without shooting themselves in the foot .NET has a simpler programming model, enabling rank-and-file developers to .NET gives you language neutrality when developing new ebusiness applications System
applications, whereas J2EE makes you treat other languages as separate .NET benefits from being strongly interweaved with the underlying operating
Page 59
CHAPTER 6-
SYSTEM DEVELOPMENT
Page 60
SYSTEM DEVELOPMENT
6.1
INTRODUCTION
The Development phase creates the system software. The phase commences with the data model, probably from the prototype, adds system queries, followed by forms and reports. Code is added last. The deliverable from this phase is: Software The system Documentation A statement of functional conformance 'Version two' Functional Requirements List
6.2 FUNCTION DETAILS

The basic objective of HOTEL MANAGEMENT SYSTEM is to generalize and Simplify the monthly or day to day activities of Hotel like Room activities, Check in of New Customer, Check out of customer, assigning a room according to customer requirement, and finally compute the bill etc. which has to be performed repeatedly on regular basis. To provide efficient, fast, reliable and user-friendly system is the basic motto behind this exercise. Let us now discuss how different functions handle the structure and data files:
Page 61
1. LOGIN/ PASSWORD In this module, this website is for multiple users. If a User enters a password and the software checks its validity. If the password is valid then option is given to perform operations on the system, otherwise Invalid User/Password message is displayed. There is an option for password changes in the site after login. The two types of login are-
change, log out, login, new users sign in. The Administrator can also update a) F-Desk User- The user can checkIn, checkout, generate bill, take order for food and perform some other operations of a general hotel management.
b) Admin- The user can read, delete and add the entries. Can modify the data permanently. Allow access to other users as F-Desk User.
2. Edit rooms-
The module provided to the admin page to add or delete the rooms from the database. Change the rate or modify the details about the room.
3. Edit Food Details-
The module provided to the admin page to add or delete the entries of food item. To change the price or modify the details of the food item.
4. Edit restaurant Details-
The module provided to the admin page to edit the details of the hotel. For eg. Name, address, owners name, owners details, etc.
Page 62
5. Manage F-Desk User-
The module provided to the admin to add or delete the F-Desk users. And even edit the details of the existing users.
6. Change password-
The module provided to both types of users to change their password , if they are successfully logged in to their account.
7. Daily Report-
The module provided to the admin to view the daily report, the overall
transaction and their respective details. This function is used to display all is a global report to display all the transaction records in the screen. 8. Customer List-
the transaction including the customers stay , the food items ordered. This
The module provided to the Admin to view the list of all the customers, of the customer, if there is any query regarding the customer.
whoever have once checkedin in their hotel. To view the respective details
9. LogOutThe module provided to both types of users to successfully logout from their account, once they have finished their job. 10. CheckIn
The module provided to the F-Desk user to perform the task ofadd all the necessary information about the user. about the customer from the dat
a) Add- to add the details of a new customer to the system database. To b) Book- to book the room for the customer by retrieving the details
Page 63
11. CheckOut-
The module is provided to the F-Desk users. This function is used to
checkout the customer details from database. When the user inputs his
room number, the same room number will be checked in the database, if the room number is matched in the database, then the customer will be check-out from the database and transferred the record of the checkout to another table of database so that the Hotel Management has the record of customers who have check-out to fulfill his legal liabilities. 12. Fooding-
The module used by F-Desk user to take orders of the food according to the room number. The records of the order are saved with the dish item, quantity and the amount.
13. Generate Bill-
This module is used by the F-Desk user to generate the bill for a particular printed. When any customer check-out, his/her bill is generated
customer. On the basis of customers room number the bill is generated and automatically by calculated check-out date minus check-in date and getting multiplied it by daily room charge plus other charges and the bill has to be saved in the table in the database. 14. Validation of data entered and validation control
In this function, the validity of data entered by the user during the various business processes is checked through various validation checks. For example, there should not be any characters entered in the numeric fields, likewise if there is any error occurs than it should handle that particular error and give the required messages.
Page 64
15. Report Generation In this function reports are generated for the following entities: a) Customer Details. c) Bill Details b) Rooms Details
d) Checkin Reports e) Booking Details f) Online Bookings
g) Checkout Details
Page 65
CHAPTER- 7
SYSTEM TESTING
Page 66
7. SYSTEM TESTING
7.1 Testing Objectives
All field entries must work properly. Pages must be activated from the identified link. The entry screen, messages and responses must not be delayed.
7.2 Testing Principles

Verify that the entries are of the correct format No duplicate entries should be allowed All links should take the user to the correct page.
7.3 Testing Design 7.3.1. White box Testing

White Box Testing is a testing in which the software tester has knowledge of the inner workings, structure and language of the software, or at least its purpose. It is used to test areas that cannot be reached from a black box level .
Page 67
7.3.2. Black box Testing

Black Box Testing is testing the software without any knowledge of the inner workings, structure or language of the module being tested . Black box tests, as most other kinds of tests, must be written from a definitive source document, such as specification or requirements document. It is a testing in which the software under test is treated, as a black box .
7.4 Testing Strategies
7.4.1. Unit Testing

Unit testing is usually conducted as part of a combined code and unit test phase of the software lifecycle, although it is not uncommon for coding and unit testing to be conducted as two distinct phases. Unit testing involves the design of test cases that validate that the internal program logic is functioning properly, and that program input produce valid outputs. All decision branches and internal code flow should be validated. It is the testing of individual software units of the application .it is done after the completion of an individual unit before integration. This is a structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform basic tests at component level and test a specific business process, application, and/or system configuration. Unit tests ensure that each unique path of a
Page 68
business process performs accurately to the documented specifications and contains clearly defined inputs and expected results.
7.4.2. Integration Testing

Software integration testing is the incremental integration testing of two or more integrated software components on a single platform to produce failures caused by interface defects. The task of the integration test is to check that components or software applications, e.g. components in a software system or one step up software applications at the company level interact without error.
Integration testing for Database Connection:

Testing the proper working of database. i.e. updating and deletion. The modules must properly work and perform the users operation. Database must be accessible to only the authorized users according to their access rights.
Page 69
7.4.3. Functional test

Functional tests provide a systematic demonstration that functions tested are available as specified by the business and technical requirements, system documentation, and user manuals. Functional testing is centered on the following items: Valid Input: identified classes of valid input must be accepted. Invalid Input: identified classes of invalid input must be rejected. Functions: identified functions must be exercised. Output: identified classes of application outputs must be exercised. Systems/Procedures: interfacing systems or procedures must be invoked.
7.4.4. System Test

System testing ensures that the entire integrated software system meets requirements. It tests a configuration to ensure known and predictable results. An example of system testing is the configuration oriented system integration test. System testing is based on process descriptions and flows, emphasizing pre-driven process links and integration points.
Page 70
7.5 Test Conditions

Sr. No. Test Condition 1. Pre-requisite data Expected Test Result
Check for entry in Login form is opened. User Incorrect Password password enters incorrect password Message is prompted
and presses OK button
3.
Check for entry in Login form is open. User Main form is displayed username and enters combination of to the user, consisting password menu options correct user name and of password and presses OK enabled.
button
4.
Check for guest All entries are filled entries in room booking Invalid Data Type
Message room is booked.
5. 6.
User has entered the Warning to enter invalid data type. correct data type.
Check for guest User has left the entries Message fill all the entries in room to be fulfilled, blank entries. booking Check entries for User fill entry for Message adding new room already existing room already exists. room
7.
Page 71
8. 9.
Check entries for User update entries for Message room is not updating of room the empty room. booked. Check entries for User delete the entries Message room is not cancellation of for the empty room booked. room
7.6 ERROR HANDLING

Error Error no 1 Message Fill entry Cannot enter alphabets and Enter numbers , hyphen, some special symbols in this properly ( opening bracket or field ) closing bracket Fill entry Cannot enter numbers and Enter only alphabets special symbols in this field properly Entry already existing
Duplicate value entered. Enter other unique Cannot enter already existing Room no. values in room add form.
Correction
2 3
Enter LOGIN and PASSWORD Enter same value in Enter LOGIN and field do not match. LOGIN and PASSWORD PASSWORD fields
Page 72
CHAPTER 8-
SNAPSHOTS
Page 73
8. OUTPUT FORMS
8.1 The home PageShowing two types of login 1) F-Desk user 2) Admin
Page 74
8.2 Admin Home Page
8.3 Managing F-Desk Users
Page 75
8.4 Edit Restaurant details
8.5 Manage Hotel Rooms
Page 76
8.6
Manage Food Dishes
8.7 change Password
Page 77
8.8 View Daily Report
Page 78
8.9 View Customers list
8.10 Home page of F-Desk User
Page 79
8.11 Adding a new customer
8.12 Booking Room for an existing customer
Page 80
8.13 Food service
8.14 Checkout
Page 81
8.15 Generating Bill
8.16 Printing Bill
Page 82
CHAPTER 9-
OTHER ISSUES
Page 83
9. OTHER ISSUES
9 .1 PROBLEMS
Most difficulties between sponsors and developers occur because of vague, 'I think I understand what you want', or 'isn't it obvious?' statements by each party. Sponsors are often genuinely unaware how easily developers become immersed in the entrails of their systems and simply cannot see the 'obvious'. These guidelines try to minimise such conflict by ensuring that the delivered system is literally a summation of the Functional and Non-Functional Requirements Lists. For example, if the developer is expected to provide hypertext help, a manual, certain performance compliance or a particular report then it must be documented. If it hasn't been documented then the developer is simply not responsible for creating it. If a requirement has been omitted then at the end of the phase a new version of the Requirements List can be created and the impact on delivery/cost can be assessed. The omitted item will either be essential and the project timescales are adjusted accordingly, or it can wait until the next version and will be added to the 'Version two' wish list. The aim is to remove any ambiguity between the sponsor and the developer. Likewise by ensuring that each phase completion is subject to a QA review by a 'qualified' person (e.g. domain expert or technique expert) there is the benefit of ensuring that the project meets the required standard before moving onto the next phase.
Page 84
9.2 RESPONSIBILITIES
9.2.1 Sponsor & Developer
The roles and responsibilities need to be agreed between the sponsor and the developer. The following initial ones are suggested:
Sponsor The 'domain' expert. Responsible for creating the Initial scoping document and maintaining the Functional Requirements List and nonfunctional Requirements List. The Tester. Responsible for 'signing off' conformance to Functional Requirements and for 'Black Box' system testing to ensure system errors are uncovered. In this phase errors uncovered should only be against Functional Requirements or logic errors. Changes required to the application should be documented in the 'Version two' Requirements List. The Documenter. Creates the manual and hypertext files. Developer The 'practitioner'. Responsible for adapting and applying standard analysis and design techniques to the project in hand to ensure that project is conducted professionally and remains visible throughout. The 'project manager'. Responsible for creating and amending a project plan that provides appropriate milestones to ensure sponsor is kept informed. The 'QA' manager. At appropriate stages ensure that the development work is independently reviewed to ensure compliance with functional requirements and quality standards. Consultant The 'methods' person. Provides a 'route list' and technique guidance if and when appropriate. The 'data modeller'. Reviews the data model.
Page 85
Chapter 10-
Conclusion
Page 86
10.1 CONCLUSION
This project is designed to meet the requirements of Online Hotel Management. It has been developed in .net environment keeping in mind the specifications of the system. Our project is only a humble venture to satisfy the needs in a HOTEL MANAGEMENT. Several user friendly coding have also been adopted. This package shall prove to be a powerful package in satisfying all the requirements of managing a hotel. From a proper analysis of positive points and constraints on the component, it can be safely concluded that the product is a highly efficient GUI based component. This application is working properly and meeting to all user requirements. For designing the system we have used simple data flow diagrams. Overall the project teaches us the essential skills like: * Using system analysis and design techniques like data flow diagram in designing the system. * Understanding the database handling and query processing.
Page 87
10.2 Scope of Future Application

This project can be used in the hotel after adding some more useful modules in the project for which hotel are providing services. Utmost care and back-up procedures must be established to ensure 100%
successful implementation of the computerized hotel system. In case of system
failure, the organization should be in a position to process the transaction with to complete it manually.
another organization or if the worst comes to the worst, it should be in a position
10.3 Scope of Improvement

Nowadays hotel are providing many other facilities, this project can also be improved with the improvement in the Hotels. Utmost care and back-up procedures must be established to ensure 100%
successful implementation of the computerized banking system. In case of system failure, the organization should be in a position to process the transaction with to complete it manually. We are planning to give the access to online users to another organization or if the worst comes to the worst, it should be in a position check the availability of rooms and book rooms for themselves. We also want to add the feature to record the services offered by the customer so that in case of their next visit, the same services can be provided.
Page 88
10.4 FUTURE USABILITY ASPECTS

As the number of hotels are increasing very rapidly and they all prefer to use autonomous system instead of manual system, the future aspects of Hotel Management System are very bright. The numbers of hotels are increasing day by day, thus increasing the competition in the market of hotel industries. To win in this competition the hotel industries have to be fast enough to implement
functionalities and give much more comfort to their customers. One best way of implementing that is to use autonomous record based system, which is cheap, efficient and very fast as compared to the manual system. The numbers of hotels are increasing very rapidly. The rate of error is very less in this new system. The future aspects of this system are great because-
The manual systems are very less efficient as compared to this system. The records stored in the database gives the details of customers visited increases.
earlier which gives the customer a good feel and thus the business of hotel
The records can be easily retrieved for any reference.
Page 89
BIBLIOGRAPHY
BOOK REFERENCES
Beginning Visual Web Programming in VB NET ........Daniel Cazzulino, Craig Bowes Beginning VB NET: Unmasking Visio for ..Richard Blair, Matthew Reynolds ASP.NET and VB.NET Web programming........Matt J. Crouch Learning SQL on SQL Server 2005 ..Sikha Bagui, Richard Earp Microsoft SQL Server 2005 Stored Procedure ....... Dejan Sunderic Xml: The Complete Reference.........By Williamson Pro ASP.NET 2.0 website programming.......Damon Armstrong 2005 .net framework 2.0 by Gleen Johnson & tony Northrup
WEBSITES REFERENCES
www.vbdotnetheaven.com www.developers.net www.learnvisualstudio.net www.w3schools.com www.wikipedia.org
Page 90

Journal

Uploaded by

Copyright:

Available Formats

You might also like

Journal

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Journal

Uploaded by

Copyright:

Available Formats

ABSTRACT

Department of Computer science & Engineering Nagaland university

Department of Computer science & Engineering Nagaland university

Department of Computer science & Engineering Nagaland university

Department of Computer science & Engineering Nagaland university

1.1) ABOUT THE PROJECT

Department of Computer science & Engineering Nagaland university

Department of Computer science & Engineering Nagaland university

Functionality of the system-

Department of Computer science & Engineering Nagaland university

1.3 PROJECT CATEGORY

FRONT END: BACK END: OPERATING SYSTEM:

ASP .NET MS SQL WINDOWS VISTA 2008

Department of Computer science & Engineering Nagaland university

THE PROJECT PLAN

Department of Computer science & Engineering Nagaland university

Department of Computer science & Engineering Nagaland university

2.2 THE METHOD

Task Analysis Design

Department of Computer science & Engineering Nagaland university

Department of Computer science & Engineering Nagaland university

LITERATURE SURVEY (SYSTEM ANALYSIS)

Department of Computer science & Engineering Nagaland university

SYSTEM STUDY & ANALYSIS

Department of Computer science & Engineering Nagaland university

3.1.2 Problems with the Existing system

3.1.3 Proposed System

Department of Computer science & Engineering Nagaland university

3.1.4 Advantages of proposed system

3.2 FEASIBILITY ANALYSIS

Department of Computer science & Engineering Nagaland university

Department of Computer science & Engineering Nagaland university

3.3 FUNCTIONALITY REQUIREMENTS

Department of Computer science & Engineering Nagaland university

3.4 SYSTEM REQUIREMENTS SPECIFICATION

3.4.2 HARDWARE REQUIREMENTS

Department of Computer science & Engineering Nagaland university

Department of Computer science & Engineering Nagaland university

Department of Computer science & Engineering Nagaland university

Department of Computer science & Engineering Nagaland university

Department of Computer science & Engineering Nagaland university

Department of Computer science & Engineering Nagaland university

Department of Computer science & Engineering Nagaland university

4.2 System applications

Department of Computer science & Engineering Nagaland university

Make reference to another instance in other table.

Department of Computer science & Engineering Nagaland university

CARDINALITY AND MODALITY:

3. Various Type Indicators.

Department of Computer science & Engineering Nagaland university

4.3.2 DATAFLOW DIAGRAM (DFD)

4.3.3 FLOW CHART

Department of Computer science & Engineering Nagaland university

DATA FLOW DIAGRAM

HOTEL MANAGEMENT SYSTEM

Department of Computer science & Engineering Nagaland university

DATA FLOW DIAGRAM CHECK- IN OF A NEW CUSTOMER

Department of Computer science & Engineering Nagaland university