Conceptual Database Design Methodology

CS403 Database Management Systems Lecture 12 explores the practical methodology of conceptual database design through a comprehensive, real-world case study of a University Examination System operating under a semester framework. Conceptual database design translates unstructured institutional operational workflows and stakeholder requirements into formal, high-level data models. The design methodology begins with a preliminary study and rigorous requirements elicitation, analyzing business processes governing degree programs, student admissions, course offerings, prerequisite validations, class assignments, teacher allocations, continuous assessments, grade point calculations, and cumulative GPA tracking. To establish formal system boundaries and trace data movement, database engineers construct Data Flow Diagrams (DFDs). The context diagram, or Level-0 DFD, models the global scope by representing interactions between external entities—including student applicants, teaching faculty, registration administrative systems, and examination controllers—and the central examination system process. The lecture decomposes this high-level abstraction into a detailed Level-0 functional diagram structured around three core operational modules: Subject Registration (Process 1.0), which verifies student eligibility and validates prerequisite course clearances; Result Submission (Process 3.0), where instructors submit discrete assessment scores spanning quizzes, assignments, sessional tests, and terminal examinations; and Result Calculation (Process 7.0), which computes individual subject grade points, term GPAs, and cumulative GPAs. To ensure comprehensive coverage of institutional reporting requirements, designers formulate a Cross-Reference Matrix (CRM). The CRM cross-tabulates essential system attributes and data fields against required output documents—such as student transcripts, semester result cards, attendance sheets, subject grade rosters, and overall class rankings. By analyzing matrix intersections, designers systematically identify candidate entity types, isolate multi-valued dependencies, and verify that all reporting needs are satisfied. Crucially, the lecture teaches entity filtering criteria: external actors such as the examination controller are intentionally excluded as database entities because a single organizational role instance does not warrant entity table representation. This curriculum guide equips Virtual University students with practical competencies for CS403 midterm examinations, solved past papers by Moaaz and Waqar Siddhu, and practice MCQs.