THE UNIVERSITY OF ENGINEERING AND TECHNOLOGY, LAHORE

DEPARTMENT OF COMPUTER SCIENCE

CSC104 Term Project – Detailed Requirement Document

Project Title:
Quiz Management System

Submitted by:
Anas Sabir (2024-CS-137)
Faizan Ahmad (2024-CS-149)
Muhammad Rayyan (2024-CS-152)

Supervised by:
Dr. Samyan Qayyum Wahla
1.Introduction:

1.1 Purpose:
Online quiz management system is a software which is very helpful in current times when
education is delivered through online channels. This software will reduce the complexity of
taking tests online.
a. It saves time as several students can together give a particular exam.
b. The system automatically calculates the result, thus reducing the manual task of the evaluator
and results are available to students in no time.
c. Teachers can add/modify/delete questions.
d. Users must register, and they can give tests with their ID, thus enabling authenticity.

1.2 Document Conventions:

The following conventions are used throughout the SRS document:
a. Teacher/examiner - A user with administration privileges of the software and checks the
answer of tests and gives the result.
b. User - Target users of the software, students/applicants in this case.

1.3 Scope:
Scope of this software is very broad. It can be used in –
a. Conducting online exams in institutions
b. Conducting quiz & survey in corporate
c. It can be accessed remotely at any location & at any time.
d. Physical examiner need not be present.

2. Description:

a. Login
The user has to register to their account when they first enter the site.
b. Test
It is the most important page of the system. It includes:
i. Subject page to select the subject to give the exam.
ii. After starting the test, the timer starts according to the allotted time. It also shows the total
answered and unanswered questions. Grid form is also available where users can go to any
question without hassle.

2.1 System Functions

There are 2 types of users in this system and their flow is given:

a. Teacher/examiner
They have rights to do the following
i. Create / Edit / Delete a Course
User Action:
Teacher logs in → goes to the "Courses" section → clicks “Add Course” / “Edit” / “Delete”.
App Response:
● Show a form to enter course name, code, description.
● Save or update course details in the database.
● Show success/error message.
ii. Register / Unregister Students
User Action:
Teacher selects a course → clicks “Manage Students” → searches and selects students to register
or remove.
App Response:
● Show list of all users.
● Allow selection/deselection.
● Save changes in a Course_Enrollment table in the database.

iii. Check the Quiz

User Action:
Teacher selects a quiz → views all student submissions with their answers.
App Response:
● Fetch student responses from the database.
● Display question-wise attempts and answers.
● Show auto-calculated score (if it is objective) or let the teacher grade manually for
subjective.
iv. Modify/Edit Scores and Send to Students
User Action:
After viewing attempts → clicks “Edit Score” → enters new score or comments → clicks
“Send”.
App Response:
● Update marks in database.
● Notify students (in-app notification or email) about updated scores.
v. Create / Edit / Delete a Quiz
User Action:
Teacher selects the course → goes to the “Quiz” section → clicks “Create Quiz” → enters
questions, options, correct answers, time limit.
App Response:
● Save quiz and questions in the database.
● Option to “Edit” or “Delete” existing quizzes.
● Validate data before saving.
vi. See the Reports
User Action:
Teacher opens the “Reports” section → selects courses and quizzes → views charts/tables of
student performance.
● App Response:
● Generate summary: average, top scorers, weak topics.
● Export/download report options.

b. Student/user account
i. Login and Register
User Action:
New user → goes to Register page → fills out form → submits.
Returning user → goes to Login → enters credentials.
App Response:
● On registration: Validate input → store in user table.
● On login: Verify password → redirect to student dashboard.
ii. View Quizzes Available to Them
User Action:
Student logs in → opens dashboard → selects a course → sees quizzes listed with “Start” or
“Completed” tags.
App Response:
● Fetch available quizzes based on student’s enrolled courses and current time.
● Disable “Start” if expired or already attempted.
iii. View Their Quiz Marks
User Action:
Student goes to “My Results” section → sees scores, feedback for each quiz.
App Response:
● Show scores fetched from quiz submissions.
● Option to view correct answers (if allowed by teacher).
iv. Attempt Their Quizzes
User Action:
Click “Start Quiz” → timer starts → answers questions → submits.
App Response:
● Save answers in real-time or on submit.
● Lock access to quiz once submitted.
● Calculate auto-score (if MCQs) and store.
v. Enroll in Any Course
User Action:
Go to “Courses” page → click “Join Course” → enter course code or click “Enroll” button.
App Response:
● Add an entry in the table.
● Show course in their dashboard after enrollment.
2.2 User Flow

2.2.1 Teacher Flow

Step 1: Registration
The teacher registers by entering their personal details.
After successful registration, they log in to the system.
Step 2: Course Creation
After login, the teacher is shown a menu/dashboard.
They see a "My Courses" section where only the courses they created are visible.
They can:
● Create a new course
● Edit/Delete existing courses
Step 3: Quiz Management
When the teacher clicks on any course, they are shown the quizzes related to that course.
They can:
● Create a new quiz
● Edit/Delete quizzes
● Upload questions
USE CASE SECTION DETAILS
USE CASE NAME Create and Publish a Quiz
SCOPE Quiz Management System
LEVEL User-goal
PRIMARY ACTOR Teacher
STAKEHOLDERS AND Teacher wants to assess students efficiently.
INTERESTS Students want access to relevant and fair quizzes.
PRECONDITIONS Teacher must be registered and logged into the system.
At least one course must exist.
SUCCESS GUARANTEE The quiz is successfully saved, visible to the intended
students or group, and ready for attempt.
MAIN SUCCESS SCENARIO 1. Teacher logs into the system.
2. Selects a course.
3. Clicks "Create New Quiz".
4. Enters quiz title, description, questions, options,
correct answers, and max marks.
5. Sets quiz visibility (public or assigned class/group).
6. Clicks “Publish”.
7. System saves and displays quiz in “My Quizzes”.
EXTENSIONS 3a. If course is not selected → System prompts to
select or create a course.
5a. If visibility not selected → Default to private class.
6a. If form incomplete → Display error message.
SPECIAL REQUIREMENTS - UI must support rich text for questions.
- System must validate total marks per question.
- Must not allow quiz creation without questions.
TECHNOLOGY AND DATA - System may support file upload (e.g., diagrams).
VARIATIONS - Quiz data stored in relational database.
FREQUENCY OF High – teachers may create quizzes weekly or per
OCCURRENCE topic/module.
MISCELLANEOUS - Option to schedule a quiz for future date/time.
- Quiz auto-closes when time ends.

Step 4: Quiz Visibility Options

While uploading a quiz, the teacher chooses:
● Make quiz public (all students can view it)
● Make quiz private to a specific class or group
● The teacher may assign quizzes to:
● A specific class or
● A group of students they have already created
Step 5: Checking Quizzes
Teachers can view responses of students per quiz.
They can manually check short answer questions (e.g. descriptive answers).
For manual marking:
● The system will show the maximum marks for each question.
● The system will validate input so the teacher can’t assign marks more than the allowed
value.
● If an invalid score is entered (e.g., more than allowed), it will automatically become zero.
USE CASE SECTION COMMENT
USE CASE NAME Check and Grade a Quiz
SCOPE Quiz Management System
LEVEL User-goal
PRIMARY ACTOR Teacher
STAKEHOLDERS AND - Teacher: Wants to efficiently review, score, and
INTERESTS send results to students.
- Students: Expect timely and fair evaluation.
PRECONDITIONS - Teacher is logged in.
- Students have submitted their quizzes.
SUCCESS GUARANTEE - Quiz is checked, scored, and results are saved and
visible to students.
MAIN SUCCESS SCENARIO 1. Teacher logs in.
2. Opens “My Courses” and selects a course.
3. Clicks on the quiz.
4. System shows list of students who attempted it.
5. Teacher opens each attempt.
6. System auto-checks MCQs, teacher checks
subjective questions.
7. Teacher enters/edit marks if needed.
8. Clicks “Submit Scores”.
9. Students receive results.
EXTENSIONS - 4a. No submissions → Show message "No
attempts yet."
- 6a. If auto-check fails → Notify teacher to
manually review.
- 7a. Invalid marks entered → Show validation
message (e.g., cannot exceed question marks).
SPECIAL REQUIREMENTS - Auto-check for MCQs
- Manual marking interface for subjective questions
- Score validation
TECHNOLOGY AND DATA - Interface may include comment box for feedback
VARIATIONS LIST - Option to download responses as PDF
FREQUENCY OF Medium – after each quiz session
OCCURRENCE
MISCELLANEOUS - Option to re-check or update marks
- Scores can be exported or sent via email
Step 6: View Results
Teachers can:
● View the result of any quiz.
● See all student attempts and scores.
● Optionally, send results to students.

2.2.2 Student Flow

Step 1: Registration & Login
Students register their account and login to access the system.
Step 2: Viewing Available Quizzes
Students can see a section like “Available Quizzes” or “Current Quizzes”.
If a quiz is public, they will see it regardless of their class.
If it’s assigned to a specific class/group, only those students will see it.
Step 3: Attempting Quizzes

USE CASE SECTION COMMENT

USE CASE NAME Attempt a Quiz
SCOPE Quiz Management System
LEVEL User-goal
PRIMARY ACTOR Student
STAKEHOLDERS AND INTERESTS - Student: Wants to complete and submit the
quiz securely and on time.
- Teacher: Wants secure, fair quiz attempts.
PRECONDITIONS - Student is logged in.
- Quiz is published and accessible to the student.
SUCCESS GUARANTEE - Quiz is submitted successfully and responses
are recorded.
MAIN SUCCESS SCENARIO 1. Student logs in.
2. Opens “Available Quizzes”.
3. Selects the quiz.
4. Reads instructions.
5. Starts the quiz.
6. Answers questions within time.
7. Submits the quiz.
8. System records and confirms submission.
EXTENSIONS - 2a. No quiz available → "No quizzes
assigned."
- 4a. Quiz expired → "Quiz closed."
- 7a. Time ends → Auto-submit.
- 8a. Network issue → Auto-save answers
periodically.
SPECIAL REQUIREMENTS - Countdown timer
- Tab-switching detection
- Auto-save functionality
TECHNOLOGY AND DATA - Multimedia support (images, audio)
VARIATIONS LIST - Secure mode varies by browser/device
FREQUENCY OF OCCURRENCE Medium to High – multiple quizzes weekly
MISCELLANEOUS - Students can review their quiz history
- May see results instantly or after teacher
checks

Step 4: Viewing Results

Students can go to “My Results” section.
They can view:
● Their score
● Possibly feedback (if the teacher allows)
2.3 User Classes and Characteristics
There will be 2 kinds of users that will visit the System for different
reasons.

Physical actors:
a. The administrator/examiner will visit for admin privileges and for loading the test paper.
b. The student/user account will visit to appear for the test and to
check their marks.

System actors:
a. Client: The client is the system that connects to the server and
handles the tests based on the session and finally submits the
information back to the server.
b. Server: The server is the system that accepts multiple connections
from clients and saves the results.
c. Database Helper: The database editor handles all the queries
used to construct modify and save questions and make different
tests for the students. Also, it is responsible for logging the session
info and restores them for better study. The primary actor is the
client that connects to the server and takes the test. The term
student is to be used as a physical actor to describe the physical user
of the client. The same term is used for the teacher who is the
physical user of the database Helper and server and is responsible for
the good behaviour of the system and to make sure everything goes
well.

2.4 Operating Environment

This system will work in almost all web browsers. The only basic
requirement is an internet connection.

2.5 Design & Implementation Constraints

• SQL workbench will be used as SQL engine and database.
• Users may access from any computer that has Internet browsing
capabilities and an Internet connection.
• Users must have their correct usernames and passwords to enter
their online accounts and do actions.
We assume all users have basic computer operating knowledge and our
quiz system has a very interactive and user-friendly interface

3. System Features

3.1 Database

3.1.1 Description
This database is supposed to store, retrieve, update, or edit information
related to
• Profile of both types of users
• Student/admin details
• Test results

3.1.2 Response requests

For Administrator - The admin will login and the credentials will be
verified. If credentials are valid, the admin will be able to perform the
tasks like add/delete student records, add quiz details etc.

For user/student - The student can register by using their Name, Cnic,Reg No and email and
then login using their credential sent on email. From the menu they can appear for tests, view
scores, or view their profile.

3.2 Functional Requirements

Functional requirements the services provided to user by the system.
There are 2 subdivisions in the type of user.
• Administrator – The admin keeps track of the tests and scores and
creates/modifies the student account as per requirement.
• Candidate – The candidate will login and take the test as assigned.
The results will be displayed after completion of test.
3.2.1 Perform Validation
Input:
Input Unit Range:

Username Character 3-10

Password Character 6-15

Output:
User will go to the homepage.

3.2.2 Conduct Test

Input:
Input Unit Range

Question Integer 1-99

Answer Character A-D or A-E

Output:
After successful evaluation & validation in the backend, the result will
be displayed.

4. Non-Functional Requirements

4.1 Performance Requirements

Some performance requirements identified is listed below:
• The database shall be able to accommodate a minimum of 10,000 records of students.
• The software shall support use of multiple users at a time.

4.2 Safety Requirements

The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup.

4.3 Security Requirements

Some of the factors that are identified to protect the software from accidental or malicious
access, use, modification, destruction, or disclosure are described below. Keeps specific log or
history data sets.
• Assign certain functions to different modules.
• Restrict communications between some areas of the program.
• Check data integrity for critical variables.