Exam Date sheet Scheduler
Design Document
Version 2.0
Group Id: S240233FF0
Supervisor Name: Hasnain Ahmed
Revision History
Date Version Description Author
10/07/2024 2.0 The purpose of this phase in a BC210204438
software development project is
to create a detailed plan that
guides the development process.
It provides a clear and structured
approach, ensuring that all
aspects of the system are well-
understood and documented
before actual development
begins. This phase is crucial for
mitigating risks, managing
changes, and ensuring that the
final product meets the
requirements and expectations of
stakeholders. By investing time
in creating a comprehensive
design document, we lay a strong
foundation for a successful
project, ultimately saving time
and resources during the
development and maintenance
phases
Table of Contents
1. Introduction of Design Document
2. Entity Relationship Diagram (ERD)
3. Sequence Diagrams
4. Architecture Design Diagram
5. Class Diagram
6. Database Design
7. Interface Design
8. Test Cases
Introduction of Design Document
I have meticulously crafted a comprehensive design document that encapsulates various
critical components essential for the successful development of the software. The document
includes the following elements:
1. Entity Relationship Diagram (ERD): This diagram illustrates the relationships
between different entities within the system, providing a clear visual representation of
how data interacts and interrelates, which is fundamental for creating an efficient and
coherent database structure.
2. Sequence Diagrams: These diagrams depict the sequence of interactions between
different objects in various scenarios, ensuring a clear understanding of the dynamic
behavior of the system. They help in identifying the flow of messages and the order in
which processes occur.
3. Architecture Design Diagram: This diagram provides a high-level overview of the
system's architecture, showcasing the structure and organization of the system
components and their interactions. It is crucial for ensuring that all parts of the system
integrate seamlessly and work together effectively.
4. Class Diagram: The class diagram outlines the system's classes, their attributes,
methods, and the relationships between them. This serves as a blueprint for the object-
oriented design and helps in understanding the static structure of the system.
5. Database Design: This section details the structure of the database, including tables,
fields, and relationships. A well-thought-out database design is vital for efficient data
storage, retrieval, and management, ensuring the system can handle data operations
smoothly.
6. Interface Design: The interface design focuses on the user interface (UI) aspects,
detailing how users will interact with the system. It includes mockups and descriptions
of various UI elements, ensuring a user-friendly and intuitive experience.
7. Test Cases: Test cases are included to define various scenarios for testing the system,
ensuring that all functionalities are working as intended. This helps in identifying and
fixing any issues before the system goes live.
The purpose of this phase in a software development project is to create a detailed plan that guides
the development process. It provides a clear and structured approach, ensuring that all aspects of the
system are well-understood and documented before actual development begins. This phase is crucial
for mitigating risks, managing changes, and ensuring that the final product meets the requirements
and expectations of stakeholders. By investing time in creating a comprehensive design document,
we lay a strong foundation for a successful project, ultimately saving time and resources during the
development and maintenance phases.
Entity Relationship Diagram (ERD
Sequence Diagrams
Sequence Diagram for Admin
Sequence Diagram for Exam-Coordinator
Sequence Diagram for Superintendent
Sequence Diagram for Students
Architecture Design Diagram
Class Diagram
Database Design
Interface Design
Test Cases
Test Case ID Pre- Description Input Expected Output Pass/Fail Tested By
Condition
CE-01 Website Admin logs UserName: Access granted to Pass BC210204438
must be in and grants Rana Asad Exam Coordinator
available access to Password: and students
Exam ******
Coordinator
and students
CE-01 Admin has Student UserName: Enrollment saved Pass BC210204438
granted selects Rana Asad successfully
access course and Password:
saves ******
enrollment
CE-01 Exam Coordinator UserName: Activities list Pass BC210204438
Coordinator views Rana Asad displayed
has access activities Password:
performed ******
by student
CE-01 Incorrect Error UserName: Error message Pass BC210204438
info entered handling for Rana Asad displayed
wrong Password:
information ******
Test Case Pre- Description Input Expected Pass/Fail Tested By
ID Condition Output
EH-02 Admin Admin adds a new Hall Hall added Pass BC210204438
logged in examination hall details successfully
and has (name,
permission capacity
)
EH-02 Admin Admin edits an Hall ID, Hall details Pass BC210204438
logged in existing updated updated
and has examination hall details successfully
permission
EH-02 Admin Admin deletes an Hall ID Hall Pass BC210204438
logged in examination hall deleted
and has successfully
permission
EH-02 Incorrect Error handling for Invalid Error Pass BC210204438
info wrong information hall ID message
entered displayed
Test Pre-Condition Description Input Expected Pass/ Tested By
Cas Output Fail
e ID
MS- Admin or Admin adds Superintendent Superintend Pass BC210204438
03 Superintendent a new details (name, ent added
logged in superintend contact info) successfully
ent
MS- Admin or Admin edits Superintendent ID, Superintend Pass BC210204438
03 Superintendent an existing updated details ent info
logged in examination updated
hall successfully
MS- Admin logged in Admin Superintendent ID Superintend Pass BC210204438
03 deletes an ent deleted
examinatio successfully
n hall
MS- Incorrect info Error Invalid Error Pass BC210204438
03 entered handling for superintendent ID message
wrong displayed
information
Test Pre- Description Input Expected Pass/ Tested By
Case ID Condition Output Fail
CEDS-04 Both users Admin and Course Exam date Pass BC210204438
logged in Coordinator enrollments, sheet
enter required hall generated
data assignments,
superintendent
assignments
CEDS-04 Both users System Valid input data Schedule Pass BC210204438
logged in calculates displayed
exam date without errors
sheet
Test Pre- Description Input Expected Pass/ Tested By
Case ID Condition Output Fail
UMF- Admin Admin creates Interface Interface Pass BC210204438
05 logged in user-friendly design designed as per
interface requirement
UMF- Admin Admin User Accounts Pass BC210204438
05 logged in manages user account managed
accounts details successfully
UMF- Incorrect Error handling Invalid Error message Pass BC210204438
05 info for wrong superintend displayed
entered information ent ID
