Online Examination System: Project Report and Software Requirements Specification, Lecture notes of Software Engineering

An introduction, general description, functional requirements, interface requirements, and performance requirements for an online examination system. The system allows students to take exams worldwide, saves time, and displays results in real-time. Administrators can create, modify, and delete test papers and questions. data flow diagrams, user manual instructions, and hardware and software requirements.

Typology: Lecture notes

2019/2020

Uploaded on 03/02/2020

lodu123
lodu123 🇿🇼

1 document

1 / 22

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Project report on online examination
system
Prepared by : Guided by :
Patel vipul B. (04) Prof. H.B.Patel
Patel pratik A. (07) Prof. K.L.Patel
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16

Partial preview of the text

Download Online Examination System: Project Report and Software Requirements Specification and more Lecture notes Software Engineering in PDF only on Docsity!

Project report on online examination

system

Prepared by : Guided by :

Patel vipul B. (04) Prof. H.B.Patel

Patel pratik A. (07) Prof. K.L.Patel

Software Requirements Specification for Online Examination System TABLE CONTENTS

1 INRODUCTION .................................................................................................................

1.1 PURPOSE ........................................................................................................................

1.2 SCOPE ............................................................................................................................

1.3 OVERVIEW .....................................................................................................................

2 GENERAL DESCRIPTION ..............................................................................................

2.1 USER MANUAL ................................................................................................................

3 FUNCTIONAL REQUIREMENTS .................................................................................

3.1 DESCRIPTION ..................................................................................................................

3.2 TECHNICAL ISSUES .........................................................................................................

4 INTERFACE REQUIREMENTS .....................................................................................

4.1 GUI ................................................................................................................................

4.2 HARDWARE INTERFACE ..................................................................................................

4.3 SOFTWARE INTERFACE ..................................................................................................

5 PERFORMANCE REQUIREMENTS .............................................................................

6 DESIGN CONSTRAINTS .................................................................................................

7 OTHER NON FUNCTIONAL ATTRIBUTES .............................................................

7.1 SECURITY .......................................................................................................................

7.2 RELIABILITY ...................................................................................................................

7.3 AVAILABILITY ................................................................................................................

7.4 MAINTAINABILITY ..........................................................................................................

7.5 REUSABILITY ..................................................................................................................

8 OPERATIONAL SCENARIOS .......................................................................................

9 PRELIMINARY SCHEDULE .........................................................................................

1. INRODUCTION

1.1 Purpose

  • This Web Application provides facility to conduct online examination world wide.

4. Interface Requirements Various Interfaces for the products could be

Login form Examination form Result form C Language exam form C++ language exam form Operating system exam form Registration form Reports form

4.1 GUI

4. C language exam form

5. C++ LANGUAGE EXAM FORM :

4.2 Hard ware Requirements

  1. The application demands that all the PCs must be present in the internet .
  2. Pc should be sufficiently fast with adequate memory at least 64 MB RAM and 2 GB hard – disk space is required to run this application.
  3. Screen resolution of at least 800*600 required to properly view the screen.
  4. It should be support the printers

4.3 Software Requirements

  1. Any Window Operating System.
  2. The PHP must be installed. For the database handling MYSQL must be installed.
  3. The final application must be packaged in a set up program, so that the product can be easily installed on the clients-machine. 5. Performance Requirements - The E-mail should be sent within one hour after the registration.
  • The system should support registration for examination maximum of Students.

6. Design Constraints

The system should be designed within in 7 months.

7. Other Non Functional Attributes

7.1 Security

Application will allow only valid users to access the system. Access to any will application resource depend upon user’s designation. There are two types of users namely Administrator and Student. Security is based upon the individual user ID and Password.

7.2 Reliability

The application should be highly reliable and it should generate all the updated information in correct order.

7.3 Availability

System will be available around the clock except for the time required for the back up of data.

7.4 Maintainability

The installation and operation manual of examination management system will be provided to user.

7.5 Portability

The application should be portable on any windows based system

8. Operational Scenarios

There will be student database, examination database. The student database will contain students name, e-mail address, address, phone number, qualification.