Fall 2025/26—ISOM5260: Project Description
Note: This project is recommended for students who have taken Database Management courses in their Undergraduate/Postgraduate studies or have practical experience working on databases. |
Due Date: Oct 18, 2025 (before 9am)
You are required to build a simple information system with graphical user interface and a database, and also to compile managerial reports from the database using SQL. You may choose to build with any database product, e.g., Microsoft Access, Oracle, MySQL, etc. The steps are explained briefly below:
1. Identify the functional requirements of the “Coffee Ordering System”
The system should involve 5-7 entities in the E-R diagram or at least 10 tables in the relational database. The following data has to be captured by the system: members’ personal data and preference, the drinks information to be chosen by members and walk-in customers, order quantity and status, etc. You should also document the scope and business values of the system, other requirements can be documented if necessary.
2. Conceptual Data Modeling
After identifying entities and attributes, make use of E-R diagram to show the relationship among entities. Note that the E-R diagram should show all entities, attributes, primary keys, maximum and minimum cardinalities. You can make use of online drawing tool draw.io for drawing the E-R model. You may also consider using Computer Aided Software Engineering (CASE) tools, for instance, Data Modeler, to build the E-R model.
A list of business rules and assumptions that must be enforced in the database are required to be documented in detail.
3. Create a logical database design and physical database development
From the E-R model you created, develop a Relational Schema of the database. As a logical database design, show all functional dependencies in the database. Normalization is to be performed in logical database design, if necessary. The logical database design should be normalized into third normal form (3NF). You should also document any further assumptions, constraints, and business rules.
4. Input records to each of the tables via user interface
There are no absolute requirements on how much data should be in tables of the database, however, you should input adequate records to facilitate queries and reports generation. Input the records into the database using INSERT INTO statements of SQL.
5. Setup queries using SQL
Create 10-15 sets SQL statements in which you feel users may find useful in their operations. Document the SQL statements and state the purposes. Besides basic SQL statements, you should also write up advanced SQL statements like processing multiple tables. Aggregation functions may be applicable in dealing with numbers in tables.
Note: The above description is the basic requirement of the project. You can provide more deliverables if you wish.
Basic Deliverables
– A softcopy of documentation showing the following:
1. Project Initiation Document
• Business Values of the system
Briefly mention the reasons for supporting the development of this new database system and to determine what benefits the system will bring users, or other stakeholders.
• Scope of the system
Briefly describe the basic requirements that the system will perform.
State any other requirements if necessary.
2. Design Specification
• Conceptual Data Model – E-R diagram and Business Rules
Present the finalized E-R diagram and provide necessary explanations of the model, such as why specific entity class, relationships and attributes are modeled in your model. State all the business rules, constraints and assumptions you made that must be enforced in the database system.
• Logical Data Model – Relational Schema
You should map the E-R diagram into relations, normalize the relations into 3NF. Show all the functional dependencies for every relation and state which normal form each relation is in.
• Data Dictionary
Explain all relations including their attributes, primary keys and foreign keys.
Show the description of all tables in the database.
3. Configuration Specification
• SQL Statements configurations and specifications
Document all SQL statements (10-15 sets) you used in the database, explain the SQL statements and describe how these statements are useful to users.
4. A brief conclusion about any thoughts you have on the project, such as, suggestions and comments for further development.
– A working database system
Note: If you choose Oracle database as your platform. for the substitute project, a new Oracle database account, password and connection string will be provided. You do not need to build the substitute project using your OWN Oracle database. |
Reviews
There are no reviews yet.