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, Assign a room according to Customer’s demand, checkout of a computer and 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 ? Check-in and check-out Detail Functions Admission of New customer Check-out of customer Room assigning related to customer’s need. ? Statement of Customer Details Check-in customer Check-out customer Room Details ? Total number of Customers in the Hotel
Individual customer Report OBJECTIVE 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 files thus keeping the record absolutely up-to-date. The entire information has maintained in the database or Files and whoever wants to retrieve can’t retrieve; only authorization user can retrieve the necessary Information which can be easily is accessible from the file. ? 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 customer’s demand, 4. Checkout of a computer and releasing the room 5. Packages available. 6. List of 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 SYSTEM REQUIREMENTS ? My SQL Server ? OS “Microsoft windows XP” ? 512 MB RAM ? Concept draw. ? CD writer for back up. ? Platform. ? Internet Explorer 6. 0 ? Microsoft Visual Studio 6. 0 LITERATURE REVIEW Database Management System (DBMS) is a set of computer programs that controls the creation, maintenance, and the use of a database.
It allows organizations to place control of database development in the hands of database (DBAs) and other specialists. A DBMS is a system software package that helps the use of integrated collection of data records and files known as databases. It allows different user application programs to easily access the same database. DBMSs may use any of a variety of database, such as the network model or relational model. In large systems, a DBMS allows users and other software to store and retrieve data in a structured way. Instead of having to write computer programs to extract information, user can ask simple questions in a query language.
Thus, many DBMS packages provide Fourth-generation programming language (4GLs) and other application development features. It helps to specify the logical organization for a database and access and use the information within a database. It provides facilities for controlling data access, enforcing data integrity, managing concurrency, and restoring the database from backups. A DBMS is a set of software programs that controls the organization, storage, management, and retrieval of data in a database. DBMSs are categorized according to their data structures or types.
The DBMS accepts requests for data from an application program and instructs the operating to transfer the appropriate data. The queries and responses must be submitted and received according to a format that conforms to one or more applicable protocols. When a DBMS is used, information systems can be changed much more easily as the organization’s information requirements change. New categories of data can be added to the database without disruption to the existing system. Database servers are computers that hold the actual databases and run only the DBMS and related software. Database servers are usually ultiprocessor computers, with generous memory and RAID disk arrays used for stable storage. Hardware database accelerators, connected to one or more servers via a high-speed channel, are also used in large volume transaction processing environments. DBMSs are found at the heart of most database applications. DBMSs may be built around a custom multitasking kernel with built-in networking support, but modern DBMSs typically rely on a standard operating system to provide ENTITY RELATIONSHIP DIAGRAM (ERD) Entity – Relationship Diagram: This depicts relationship between data objects.
The attribute of each data objects noted in the entity- relationship diagram can be described using a data object description. Data flow diagram serves two purposes: 1. To provide an indication of how data are transformed as they move through the system. 2. To depict the functions that transformation the data flow. Data Objects: A data object is a representation of almost any composite information that must be understood by the software. By composite information, we mean something that has a number of different properties or attributes. A data object encapsulates data only there is no reference within a data object to perations that act on the data. 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. Relationships: Data objects are connected to one another in a variety of different ways. We can define a set of object relationship pairs that define the relevant relationships. CARDINALITY AND MODALITY: Cardinality: 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: ? One-T0-One (1:1): An occurrence of object ‘A’ can relate to one and only one occurrence of object ‘B’ and vice versa. ? One-To-Many (1:N): One occurrence of object ‘A’ can relate to one or may occurrences of object ‘B’ but an occurrence of object ‘B’ can relate to only one occurrence of object ‘A’. ? Many-To-Many (M: N): An occurrences of ‘B’ occurrence of ‘B’ can relate to one or many occurrence of ‘A’, and vice versa. Modality: The modality of a relationship is zero if there is no explicit need for the relationship to occur or the relationship is optional.