Total: 100 marks across seven categories. Grading is primarily based on your video demonstration.
| Category | Marks | Description |
|---|---|---|
| 1. Conceptual Database Design (ER Model) | 20 | Clear ER diagram with entities, attributes, and relationships; correctly reflects real-world use cases and functions; appropriate use of cardinality and participation constraints; avoids redundancy. |
| 2. Mapping ER to Relational Schema | 20 | Accurate and complete conversion of ER model to relational schemas; all keys and constraints properly defined; handles weak entities and relationships well. |
| 3. Schema Quality and Normalization | 10 | Tables are normalized (at least to 3NF); no unnecessary redundancy. |
| 4. SQL Code (DDL, DML, Queries) | 20 | High-quality DDL.sql and DML.sql (or equivalent ORM code); includes constraints, sample data, and test cases; use of advanced SQL features (e.g., views, triggers, joins). |
| 5. Application Functionality | 20 | Number and correctness of implemented functions based on requirements; includes validation, constraints, and handles edge cases; proper user-role separation. |
| 6. User Interface / CLI Flow | 5 | Interface is functional, clear, and user-friendly; commands or menus are intuitive and role-specific; no major usability issues. |
| 7. Demo Video Presentation | 5 | Complete and well-paced walkthrough; demonstrates key components (ERD, mapping, code, functionalities); SQL or ORM code shown clearly. |
| Total | 100 |
The following provides guidance on how each grading category is assessed:
| Criterion | Description |
|---|---|
| Conceptual Database Design | ER diagram is clear, professional, and well-organized. All required entities and relationships are present and correctly modeled with appropriate cardinality. Attributes are appropriate and complete. ER model fully supports all implemented functions. No redundancy or design flaws. |
| Relational Schema Mapping | Accurate conversion of all entities to tables. All relationships properly represented (foreign keys, junction tables where needed). Primary keys correctly identified. Foreign keys properly defined with appropriate constraints. Weak entities and special relationships handled correctly. |
| Normalization | All tables normalized to at least 3NF. No unnecessary redundancy. Proper use of normalization principles. Design decisions are justified and appropriate. |
| SQL Implementation | High-quality, complete DDL.sql with all constraints (primary keys, foreign keys, NOT NULL, UNIQUE, CHECK). Comprehensive DML.sql with realistic sample data sufficient to test all operations. Appropriate use of views, triggers, and indexes to support system functionality. Well-written SQL queries in application code with proper use of joins, subqueries, and aggregations. |
| Functionality | All required functions implemented and working correctly. Proper validation and error handling for all functions. Both success and failure cases demonstrated. Business rules properly enforced. Proper role-based access control implemented. |
| User Interface | Interface is clear, intuitive, and user-friendly. Role-specific menus or commands. Easy to navigate and use. Even simple CLI interfaces are acceptable if functional and clear. |
| Video Presentation | Complete walkthrough of all required components (ER model, schema mapping, database definition, all required functions, code structure, user flow). Clearly demonstrates all required system components and functionality. All functions demonstrated with both success and failure cases. SQL or ORM code clearly shown. |
| Completeness | All required components present: video, report, source code, SQL files (or ORM code), ER diagram, README. All required functions implemented. All required database features included. Sample data supports testing all functions. |
Common mistakes that reduce grades include: hard-coded data instead of database queries, missing validation for business rules, ER model that doesn't support all 8 functions, poor normalization (redundancy, incorrect design), missing required SQL features (views, triggers, indexes), incomplete video demonstration, no error handling for failure cases, and poor documentation (README, report).
Video demonstration is the primary basis for grading. Demonstrate all 8 functions with success and failure cases. Code quality and organization affect marks. ORM usage must be clearly demonstrated if used.