Quiz Application SRS

Contents
1 Introduction 2
1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 Overall Description 2
2.1 Product Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.2 Product Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.3 User Classes and Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.4 Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.5 Design and Implementation Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.6 Assumptions and Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3 External Interface Requirements 3

3.1 User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2 Software Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

4 System Features 3
4.1 Feature 1: User Registration & Authentication . . . . . . . . . . . . . . . . . . . . . . . . 3
4.2 Feature 2: Quiz Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.3 Feature 3: Quiz Taking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.4 Feature 4: Performance Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.5 Feature 5: Admin Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

5 Other Non-Functional Requirements 4

5.1 Performance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.2 Usability Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.3 Maintainability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

6 Use Case Diagram 4

1
1 Introduction
1.1 Purpose
The purpose of this document is to provide a detailed description of the Quiz Application, which is
intended to enable users to create and take quizzes and evaluate performance based on scores and time
taken. The audience of this document includes project managers, developers, testers, and end-users of
the system.

1.2 Scope
The Quiz Application is a web-based platform where users can create, manage, and take quizzes consisting
of multiple question types (e.g., MCQs). The application will calculate performance based on both marks
and time. The application will allow administrators to manage users and quizzes. The primary users
will include quiz takers, quiz creators, and administrators.

1.3 References
• IEEE Standard for Software Requirements Specifications.

• Other project-specific documents and standards as applicable.

1.4 Overview
This document describes the functional and non-functional requirements, external interfaces, system
features, and the overall architecture of the Quiz Application.

2 Overall Description
2.1 Product Perspective
The Quiz Application is a standalone web-based application that provides users with the ability to create
and take quizzes. The application interacts with a backend database for storing quiz questions, user data,
and performance reports.

2.2 Product Features

• User Registration and Login: Users will be able to register and log in to access the quiz system.

• Quiz Creation: Users will be able to create quizzes with different types of questions (e.g., MCQs,
true/false).
• Quiz Taking: Users will take quizzes and view scores.
• Performance Evaluation: The system will evaluate student performance based on marks and
the time taken to attempt MCQs.
• Admin Features: Admin users can manage quizzes and user accounts.

2.3 User Classes and Characteristics

• student: Users who gave quizzes.
• Admin: Users who have full control over managing quizzes and users.

2.4 Operating Environment

The application will be hosted on a web server and will be accessible via standard browsers on desktops,
tablets, and mobile devices.

2
2.5 Design and Implementation Constraints
The application will rely on standard web technologies such as HTML, CSS, JavaScript,flask and a
relational database for storage.

2.6 Assumptions and Dependencies

• The application assumes a reliable internet connection for optimal performance.
• Dependencies include third-party libraries for UI components, performance calculation, and API
integrations.

3 External Interface Requirements

3.1 User Interfaces
The UI will include:

• Login Page: Where users can register or log in.

• Dashboard: Where users will manage quizzes and view performance reports.
• Quiz Interface: Where users will take quizzes and view results.

3.2 Software Interfaces

The application will interact with:
• Database: For storing user data, quiz questions, and results.
• Email API: For user registration confirmation and notifications.

4 System Features
4.1 Feature 1: User Registration & Authentication
Description: Users will be able to register and log in to the system.
• FR1.1: The system shall allow users to register using an email and password.

• FR1.2: The system shall allow users to log in using their registered credentials.
• FR1.3: The system shall send a verification email upon registration.

4.2 Feature 2: Quiz Creation

Description: Users can create quizzes by selecting different question types and settings.
• FR2.1: The system shall allow users to add MCQs and true/false questions.
• FR2.2: The system shall allow users to set time limits for quizzes.

• FR2.3: The system shall allow users to edit and delete quizzes.

4.3 Feature 3: Quiz Taking

Description: Users will be able to take quizzes created by quiz creators.

• FR3.1: The system shall allow users to answer multiple-choice questions.

• FR3.2: The system shall display a countdown timer for timed quizzes.
• FR3.3: The system shall submit answers automatically once the time is up.

3
4.4 Feature 4: Performance Evaluation
Description: The system evaluates a student’s performance based on both marks and time taken to
complete MCQs.

• FR4.1: The system shall calculate total marks based on correct and incorrect answers.
• FR4.2: The system shall record the time taken to complete each quiz.
• FR4.3: The system shall compute a performance score considering both marks and time.

• FR4.4: The system shall display the performance score and detailed report on the user’s dashboard.

4.5 Feature 5: Admin Management

Description: Admin users can manage quizzes and users.

• FR5.1: The system shall allow admins to view all quizzes created on the platform.
• FR5.2: The system shall allow admins to block or delete users.
• FR5.3: The system shall allow admins to generate usage reports.

5 Other Non-Functional Requirements

5.1 Performance Requirements
• The system must support up to 10,000 simultaneous users.
• Quiz results must be calculated and displayed in less than 2 seconds.

5.2 Usability Requirements

• The application must be responsive and accessible from both desktop and mobile devices.

5.3 Maintainability
• The system must be modular and support easy updates and maintenance.

6 Use Case Diagram

Below is a simplified use case diagram showing the interactions of users with the system.

• Actors: student, Admin

• Use Cases:
– Register/Login: Actor - student, Admin
– Create Quiz: Actor - admin
– Take Quiz: Actor - student
– View Performance: Actor - admin
– Manage Users and Quizzes: Actor - Admin