Software engineering- Graded Lab-1 (17th June 2025)
Name-Ankit kumar sapid-1000019876
Questions:
1. Development of problem statement.
Problem Statement: Online Exam Registration System
In many academic institutions, students face challenges while registering for
exams due to outdated manual processes, inconsistent record management,
and lack of real-time availability of slots. These issues often result in
scheduling conflicts, errors in exam forms, and dissatisfaction among students
and administration.
To address this, we propose the development of an Online Exam
Registration System that allows students to register for exams via a web-
based platform. The system will automate the registration process, validate
inputs (course codes, prerequisites), prevent duplicate entries, and provide
confirmation and exam schedules in real-time. It will also allow admin staff to
monitor registration statistics and manage time slots effectively.
2. Preparation of Software Requirement Specification Document, Design
Documents and Testing Phase related documents.
A. Software Requirement Specification (SRS)
1. Introduction
Purpose: To automate the process of exam registration for students and streamline
admin tasks.
Scope: Web-based application for students and admin users. Accessible from any
internet-enabled device.
Users: Students, Admins/Staff
Assumptions: Internet connectivity is available; users have institutional login
credentials.
2. Functional Requirements
Student login/registration
View eligible courses and exams
Select subjects and time slots
Confirm exam registration
Admin login and dashboard
View and manage registrations
Generate reports
3. Non-Functional Requirements
Security (role-based access, data encryption)
Usability (user-friendly interface)
Availability (24/7 uptime during registration period)
Performance (support at least 500 concurrent users)
B. Design Documents
1. Entity-Relationship Diagram (ERD)
Entities:
o Student (Student_ID, Name, Email, Department)
o Exam (Exam_ID, Subject_Code, Date, Time, Venue)
o Registration (Reg_ID, Student_ID, Exam_ID, Status)
o Admin (Admin_ID, Username, Password)
2. Data Flow Diagram (DFD)
Level 1 DFD:
Processes:
o User Authentication
o Course/Exam Retrieval
o Registration Submission
o Confirmation Generation
o Admin View Reports
3. UML Diagrams
Use Case Diagram (Actors: Student, Admin; Use cases: Register, View Exams,
Confirm Registration, etc.)
Class Diagram
Activity Diagram
Sequence Diagram for registration flow
C. Testing Phase Documents
1. Test Plan
Define test cases for login, registration, course validation, confirmation, and admin
actions.
Test types: Unit Testing, Integration Testing, System Testing, Acceptance Testing
2. Sample Test Cases
Test Case ID Description Input Expected Output Status
TC001 Student login Valid email/pass Redirect to dashboard Pass
TC002 Register for exam Valid course and time Confirmation message Pass
TC003 Duplicate registration Same course twice Error: already registered Pass
3. Bug Reporting Format
Bug ID Module Description Severity Status
B001 Registration Incorrect time validation High Fixed
4. Traceability Matrix
Requirement ID Test Case ID Status
FR-001 (Login) TC001 Covered
FR-002 (Registration) TC002 Covered
