Complete project submit deadline: 17:00, 10 April 2026, Friday

In this course, each student is required to complete a database application project. For this project, you are required to pick a real-world scenario and build a substantial database application for it.

You need to analyze the business logic in your chosen scenario, identify the domain data that can and should be managed by a database management system, design a relational schema for the database, and develop a user-friendly interface for an application that implements some representative operations in the chosen scenario using the data stored and managed in the database.

When you pick an application scenario, you should pick one that is both enjoyable and manageable to you. And your application should not be trivial. That is, when you construct an ER diagram for your application, there should be about four or so entity sets, and a similar number of relationship sets. And it would be the best if there are different types of relationships (e.g., many-to-one, many-to-many, etc) in the design. You can use advanced features, such as inheritance, aggregation, weak entity sets, etc, if they are really needed. But they are not required.

You will only receive one mark for your project. And it is worth 10 percent in your final grade. Your project will be marked based on the novelty of your chosen application domain, the logical coherence and the representativeness of the operations you choose to implement for your application, the presentation quality in your project report and the implementation quality of your project application.

In the end, you need to submit the source code, relevant database queries (including the table creation ones and data population ones) and a report document for your project. Your report document MUST include at least the following sections:

1. Application Domain Introduction: introduce the background information of your application, including but not limited to, the relevant domain knowledge used/assumed in your project and the target user(s) of your application.
2. Business Data Description: describe any relationship among the data used in your application. This description should match with your database design in the later section.
3. Application (Business Logic) Specifications: list and explain at least three to five substantially distinct and representative functionalities that will be implemented in your project. List and explain as many reasonable functionalities in your selected application domain as you like. It would be the best if all your listed functionalities logically belong to the same audience group.
4. Database Design: identify what kind of data should be collected and maintained in your selected application domain. The data should at least be sufficient to support the functionalities you intend to implement.
   Draw the ER diagram and translate it into the database schema. The database schema can be presented as sql statements (create table statements).
5. Implementation Notes: document which part of the application has been completed. the sample data used to test run the functionality that has been achieved and the test run result.
6. Testing Summary: describe the sample data used to populate your databased used in the application, and test run your application with different scenarios and present the results (and database changes) generated by your application.
7. Conclusion and Future Work.

Because there is only one mark for the whole project, you don't have to submit your intermediate work. However, to make sure that you can finish your project on time, you are strongly recommended to meet the following milestones:

• Step 0: It is strongly recommended that you talk to your instructor about your project ideas before you finalize your project proposal. You can do it during your lab time, during my office hours, or by appointment to set up a time.
• Step 1: Your project proposal should be done no later than March 1st. In your proposal, you should describe your application domain and audience, list the requirements from the (hypothetical) customer. Essentially, that's the first three sections of your report. Note that you may be asked to re-do or modify your proposal to make your project more appropriate for the course.
• Step 2: Database schema, sample data and interface design should be done no later than March 15th. In this submission, you should include the ER diagram, the database schema of your application domain, the sample data you plan to use to populate your database and the interface layout (menus, etc) of your application and describe the functionalities supported by your application. That's essentially the first four sections of your report.
• Step 3: Implement your application and write your project report. Submit what you have done before the deadline.