The bookstore is just an example. I need a database on hotel management system - I am in America so everything would be in dollars, AC only and the variability in rooms would be smoking/non-smoking.
Database Project Name Term Project - Report Sample Table of Contents with Info Database Project Name Course Section: CS605.641.8x Summer, 2020 Prepared by First Name Last Name XX/XX/2020 Database Design Project Document Table of Contents 1.Introduction4 1.1.Scope and Purpose of Document4 1.2.Project Objective4 2.System Requirements4 2.1Hardware Requirements4 2.2Software Requirements4 2.3Functional Requirements4 2.4Database Requirements4 3.Database Design Description4 3.1Design Rationale4 3.2E/R Model4 3.2.1Entities5 3.2.2Relationships5 3.2.3E/R Diagram5 3.3Relational Model5 3.3.1Data Dictionary5 3.3.2Integrity Rules5 3.3.3Operational Rules5 3.3.4Operations5 3.4Security5 3.5Database Backup and Recovery5 3.6Using Database Design or CASE Tool6 3.7Other Possible E/R Relationships6 4.Implementation Description6 4.1Data Dictionary6 4.2Advanced Features6 4.3Queries6 4.3.1Customer Bills6 4.3.2Customer Rental History6 4.3.3Movie Rental History6 4.3.4List all videos by movie category6 4.3.5List video usage by movie category6 4.3.6List videos by format (Laser Disc or VHS)6 4.3.7List defective videos7 4.3.8List twenty popular videos by category for customers’ recommendations7 5.CRUD Matrix7 5.1List of Entity Types7 5.2List of Functions7 6.Concluding Remarks7 Appendices8 References8 (Note: Please provide some inputs for the sections in your DB design document template even though some of them may not be suitable for your project. The purpose for all different sections is to ask you to think about different perspectives of a database project. If a section does not apply to your project, you should make something up. Please do not skip them. For instance, Database Backup and Recovery is commonly implemented in a real database project. Even if you do not implement it, most RDBMSs may have incorporated backup and recovery tools into their interfaces and infrastructure. Give a short description of your RDBMS solution to demonstrate your thought process.) 1. Introduction Explain your database project at high-level and/or why you choose this database topic. 1.1. Scope and Purpose of Document Your document discusses the requirements, design, and implementation of your database. You can elaborate each section in your document that will be covered. Or you can describe the scope of your database project. The purpose of this document serves as a written record to demonstrate the thinking process regarding the conceptual design, logical design, and implementation of the database, and to summarize the features implemented by you. (Note, this document is a part of the requirements of the term project; the template helps you to go through documenting pieces of database design project.) 1.2. Project Objective Describe project objective. For instance, your project involves designing and implementing a database, using a relational DBMS that captures all informational aspects of the operations you plan to do for an organization or business entity. 2. System Requirements General System requirements 2.1 Hardware Requirements Min. requirements for memory, CPU etc. 2.2 Software Requirements Min. OS requirements/Any particular software that is required to run this application (e.g. MS Access) or, for web-based application, any particular browser version? 2.3 Functional Requirements Functionality the application supports 2.4 Database Requirements What database was used in this project? What version? 3. Database Design Description General database design descriptions 3.1 Design Rationale Why did you choose a particular ER design? Think about how your database design may be challenged and how you can defend your design. For example, did you use artificial primary keys and why? Why did you choose non-identifying relationship for two entities when it could be modeled as identifying relationship? Why? 3.2 E/R Model General E/R model descriptions 3.2.1 Entities Detailed descriptions of the entities 3.2.2 Relationships Detailed descriptions of the relationships 3.2.3 E/R Diagram E/R diagram 3.3 Relational Model 3.3.1 Data Dictionary Detailed descriptions of the metadata for the model. For example: Column Name Description Data Type Size Constraint Type Not Null? Valid Values SSN Social Security Number Varchar 9 Primary Key Y 9 numeric digits 3.3.2 Integrity Rules How did you handle the mandatory fields, data formatting/conversion, and valid values for the data? How are the referential integrity established? For example, which table references which other table(s)? 3.3.3 Operational Rules What are the constraints for some operations? For example, will the users be able to delete a patron’s information if he/she has outstanding videos? Can a patron be associated multiple records of checked-out videos? Will the application allow the users to enter a patron if the patron has the same first name and last name as an existing patron in the system? 3.3.4 Operations Describe what operations are involved for a particular use case. For example, does checking out videos involve insert/delete/update/retrieve? 3.4 Security Any security requirements and how are they addressed in the application? 3.5 Database Backup and Recovery Explain any database backup and recovery you may implement. Most RDBMSs may have incorporated backup and recovery tools into their interfaces and infrastructure. You may give a short description of. 3.6 Using Database Design or CASE Tool Software engineering tools provide automated or semiautomatic support for software development. A CASE (Computer-Aided Software Engineering) tool sometimes is more important than hardware for achieving good quality and productivity. Describe the tools you used to produce the artifacts for your project. 3.7 Other Possible E/R Relationships What were the other alternatives you considered when you designed your database? 4. Implementation Description General implementation requirements 4.1 Data Dictionary Data dictionary after you have your database set up. This dictionary is less detailed than the one in the previous section. Usually, a “DESCRIBE” operation in your database will provide the information needed for this section. If your RDBMS has a tool to show data dictionary; it is also fine too. 4.2 Advanced Features Describe any triggers, stored procedures, functions, or others used in the project to implement business rules specified in your database project. (For extended features, you may include user interfaces with screen shots if you have implemented a database application. You may include any special work such as reporting or data visualization tools you have done for your project that are not covered in this database design template.) 4.3 Queries General query information (Your specific database queries or reports) 4.3.1 Customer Bills How did you query customer bills? Provide SQL statements. 4.3.2 Customer Rental History Same as above. 4.3.3 Movie Rental History Same as above. 4.3.4 List all videos by movie category Same as above. 4.3.5 List video usage by movie category Same as above 4.3.6 List videos by format (Laser Disc or VHS) Same as above. 4.3.7 List defective videos Same as above 4.3.8 List twenty popular videos by category for customers’ recommendations Same as above 5. CRUD Matrix CRUD matrix as described in one presentation by Dr. Kung 5.1 List of Entity Types 5.2 List of Functions 6. Concluding Remarks Lessons learned and strengths and weaknesses, what you may add to the database project if you have more time. Appendices Additional information, such as known defects Appendix A - DDL, INSERT, SELECT Statements CREATE statements for creating database objects; INSERT statements to populate test data into the database; SELECT statements to display the test data Appendix B - Data Dictionary Index Index to the data dictionary (e.g., column_name in alphabetical order, table_name)) References Reference material Page 1 of 8 Page 2 of 2 Page 1 of 2 Database Term Project (Sample) A Bookstore Design and implement a database, using a relational and SQL-based DBMS, that captures all informational aspects of a bookstore: A bookstore will encompass the typical operations of a bookstore, including maintaining inventory, supporting the ordering process, gathering customer information, and customer service. The proposed database system includes the following functional requirements: • Track the current inventory of books using the International Standard Book Number (ISBN) • Add or edit records by bookstore employees • Place of one or more selected items in the customer’s shopping cart • Enable customers to view items in their shopping carts • Login for existing customers or register new customers who decide to place an order • Gather information from the customer needed to complete the order (e.g., payment and delivery methods, etc.) • Issue an order confirmation for each order • Keep track of shipments and charges by shipping invoice • Enable the staffs to generate ordering statistics for internal research, including monthly, quarter and annual sales • Enables the staffs to pull out the order with customer’s last name • Acquire of information for establishing a customer profile (name, address, phone, etc.) when customers create a customer account • Collect customer’s credit card information either at the time they establish their account, or when placing their order • Allow customers to update their own account information (name, address, phone, credit card, etc.) • Collect customer’s comments by providing a form with a multiple-choice section (unsatisfied, fair, good, or excellent) • Generate reports: o Annual, Monthly, and Quarterly Sales Report o Author, Publisher, and Book Information o Reorder Report o Customer Expenditure Report o Customer/Number of Orders o Books Returned within the past 30 days o Unsatisfied Customers Information You will use a given template for your database documentation. Your project documentation should include the database E/R model, the database dictionary, CRUD matrix and content, your design rationale, sample retrievals/updates and their corresponding output. A database application with a graphical user interface is not required. However, it is recommended that you can implement advanced database features such as triggers, stored procedures, functions, Page 2 of 2 Database Term Project (Sample) or others to demonstrate your advanced database knowledge on handling your database business rules. Your project will be graded on completeness, correctness, originality, unique design and/or advanced features, characteristics, and implementation.