Software Requirements Specification

SRS For Student Feedback System

1

Software Requirements Specification

For

Student Feedback System

Team Members

S.No. Name Roll No.

1. Girish Arora 10414302009

2. Pankaj Ghildiyal 06614302009

3. Sunder Gautam 07514302009

4. Ashish Kumar Singh 09214302009

Date: - August 28, 2011


2

Table of Contents

1. Introduction …………………………………………………………………………………………..4

1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms, and Abbreviations 1.4 References 1.5 Overview

2. The Overall Description ……………………………………………………………………….7

2.1 Product Perspective

2.1.1 System Interfaces 2.1.2 Interfaces 2.1.3 Hardware Interfaces 2.1.4 Software Interfaces 2.1.5 Communications Interfaces 2.1.6 Memory Constraints 2.1.7 Operations

2.2 Product Functions 2.3 User Characteristics 2.4 Assumptions and Dependencies

3. Specific Requirements …………………………………………………………..……………..13

3.1 External interfaces 3.2 Functions 3.3 Performance Requirements 3.4 Logical Database Requirements 3.5 Design Constraints

3.5.1 Standards Compliance 3.6 Software System Attributes

3.6.1 Reliability 3.6.2 Availability 3.6.3 Security


3

3.7 Organizing the Specific Requirements 3.7.1 Feature 3.7.2 Stimulus and Response 3.7.7 Functional Hierarchy

4. Change Management Process …………………………………………………………….18

5. Document Approvals …………………………………………………………………………18

6. Supporting Information…………………………………………………………………..…19


4

1. Introduction

1.1 Purpose

The following document describes the functional and non-functional

requirements for the “Student Feedback System”. The contents are intended to be utilized by the software engineering class as guidelines for implementation and testing. This Software Requirements Specification document only covers the main system and does not describe the implementation of the database in which the main system interacts. All the requirements stated in this document are slated for implementation in Student Feedback System, unless otherwise specified.

1.2 Scope

The Student Feedback System will allow Administrator to maintain a record of information provided by the students which is useful for the faculties as well as the college in the ongoing efforts and enhance the quality of education. The opinion provided by the student will be kept confidential. The evolution will be calculated on the basis of total scores from the responses from all students. Furthermore, the program provides different modes to edit details, view statistics, and take notes on elements pertaining to feedback. The aim of the study was to develop a World Wide Web-based course feedback system serving both students and teachers. The system includes generation and analysis of course feedback pages, provision of feedback, and a summary.

1.3 Definitions, Acronyms, And Abbreviations The .NET Framework is designed for cross-language compatibility. Cross-

language compatibility means, an application written in Visual Basic.NET may reference a DLL file written in C# (C-Sharp). A Visual Basic.NET class might be derived from a C# class or vice versa.

Components of .NET Framework

Common Language Runtime (CLR)

Class Libraries


5

DOT NET Architecture

Common Language Specification

The common Language Specification (CLS) describes a set of features that different languages have in common. The CLS includes a subset of Common Type System (CTS) which define the rules concerning data types and ensures that code is executed in a safe environment.

Windows

Forms

Controls Drawing

Windows Application Services

Active Server

Pages

Web Services Web Forms

ASP .NET Application Services

ADO.NET XML Threading

.NET Framework Base Classes

IO

Security Diagnostics Net Etc

Memory Management Common Type System

Common Language Runtime


6

Acronyms SRS SOFTWARE REQUIREMENT SPECIFICATION

SFS STUDENT FEEDBACK SYSTEM

WEB-BASED ABLE TO BE RUN OVER THE WEB,WITHOUT ANY

PERMANENT FILES ON THE USER’S COMPUTER

SQL STRUCTURED QUERY LANGUAGE.

BCA BACHELOR OF COMPUTER APPLICATION

B-TECH BACHELOR OF TECHNOLOGY

MCA MASTER OF COMPUTER APPLICATION

M-TECH MASTER OF TECHNOLOGY

1.4 References

http://www.w3schools.com/aspnet/default.asp

http://www.w3schools.com/ado/default.asp

http://www.w3schools.com/aspnet/aspnet_dbconnection.asp

1.5 Overview The application has a database of questionnaire which will be given to the

students after a secured login. A mechanism will be there to add, modify or delete a question to/from the database.

The application should evaluate the answers given by the students based on the feedback (which will be given by a no. 1 – 5) and a percentile / grade has to be generated to all the staff members of a particular department.

This feedback report was checked by the HOD’s. He can view overall grades and view the grades obtained to the faculty and give this report to the principal and he can give counseling to the college staff.

We have developed Student Feedback System to provide feedback in an easy and quick manner to the college principal and HOD’s. So we call it as Student Feedback System which delivers via the student staff interface as online system which acting as a Service Provider, By using this online system we make it better and quick way.

http://www.w3schools.com/aspnet/default.asp

http://www.w3schools.com/ado/default.asp

http://www.w3schools.com/aspnet/aspnet_dbconnection.asp


7

2. The Overall Description

2.1 Product Perspective The Student Feedback System is intended to replace the manual model of

feedback record keeping by means of paper records. The paper records are replaced with a single interaction between the students and the Student Feedback System. The features expressed in this Software Requirements Specification document are intended to be fully implemented in Student Feedback System. The system will be developed in such a way to provide easy and user friendly interface to students and as well as to the administrator.

2.2.1 System Interface

This application requires a web server connected to all the system of institution. The application will be a windows based, self-contained and independent software product.

Front end client application (with feedback entry, view, reporting faculty, semester results.)

Backend Database SQL


8

2.2.2 Interface

Student can give the feedback about the faculty on the scale of five. Students can give feedback about the lecturer based on interaction of lecturer in the class room with students. According to that, students can give feedback as per the given grades.

Student Interface


9

Administrator Interface

The feedback reports were checked by the Administrator. He/she can view overall grades and view the grades obtained to the faculty and give this report to the principal and he can give counseling to the college staff.

2.1.3 Hardware Interfaces

1. Standalone system or network based system required to open the

application page.


10

2. Processor : Intel P-IV System

3. Processor Speed : 250MHz 4. Primary Memory : 512MB RAM 5. Secondary Memory : 40GB 6. Support for printer (dot-matrix/ DeskJet/ inkjet etc.-any will do)-that is,

appropriate drivers are installed and printer connected printer will be

required for printing of report and mark-sheets.

The above specified requirements are the minimum requirements which are required to run the application.

2.1.4 Software Interfaces

1. Operating System: Windows NT/ME/2000/XP

2. Database: Sql Server

3. Server side technology:ASP.Net

4. Server side scripting: Java Scripting

5. Client side scripting: HTML

6. Web-Server: IIS

7. Tools used: Microsoft Visual Studio 2008, Sql Server Management 2008 R2, Internet explorer, Mozilla, Firefox.

2.1.5 Communications Interface

1. The security of a user must be consistent through the use of passwords.

2. The Student Feedback System will communicate to the database directly.

2.1.6 Memory Constraints

1. Processor: Pentium IV.

2. Speed: 1.00 GHZ.

3. Primary Memory: 256 MB RAM.

4. Hard Disk: 2GB.


11

5. Screen resolution of at least 1024 x 800-required for proper and complete

viewing of screens. Higher resolution would not be a problem.

The above specified requirements are the minimum required to run the

application.


12

2.1.7 Operations

The student will perform the operations on the following:

1. Login

2. View questions

3. Giving feedback about the faculties

4. Logout

The administrator will perform the operations on the following:

1. Add questions 2. Update questions 3. View questions 4. View report

2.2 Product Function

Functions performed by the Student Feedback System are as follows:

1. Student Feedback System is an online web application for issuing the feedback about the faculty by students.

2. It provides feedback in a easy and quick manner to the college principal and HOD’s.

3. Administrator can prepare questions and add, update these questions to the online system.

4. It also generates feedback report on the bases of the feedback given by the students.


13

2.3 User Characteristics

1. The system will provide an online user manual in HTML that describes the

functionality and options available to the user.

2. The system will provide a hard copy of the user manual, which is identical

to the manual.

2.4 Assumptions And Dependencies

1. The database mentioned within this Software Requirements Specification document is previously administered with the correct information needed by the Student Feedback System.

2. Student recognition is dependent on information in a database administered outside of the capabilities of the Student Feedback System.


14

3. Specific Requirements

3.1 External Interface

Student Feedback System external interface contains four things namely,

1. Students 2. Feedback Forms 3. Questions 4. Administrator 5. Reports


15

3.2 Function Following functions are performed in Student Feedback System by students and

administrator:

3.3 Performance Requirements

1. The program must be able to be run concurrently by multiple professors. 2. Transmission of data shall occur in less than 5 seconds. 3. Acknowledgement shall be received (confirmation) shall be returned within

8 seconds. 4. Queries upon the database shall be performed in less than 5 seconds. 5. On start of the feedback program, data information shall be displayed on the

user PC within 10 seconds. 6. The program shall support to give information of up to or more than50

faculty at a time. With a maximum size, performance must still conform to all performance requirements.


16

3.4 Logical Database Requirements

1. The system shall include a database: Student. 2. The Student database shall contain multiple tables. 3. Tables in the student database contain faculty information including name,

faculty identification number and department.

3.5 Design Constraints

1. The time allotted for this project will be limited to the november 2011

semester.

2. The language for the project will be .NET(C#) and the development environment will be the embedded ASP.NET 3.5 environment.

3. All the HTML code for the user manual will conform to the HTML 4.0

standard.

3.6 Software System Attributes

There are various software system attributes which are following: 3.6.1 Reliability:

1. Due to the use of a wired network, reliability of the system at all times

is guaranteed. However, overall reliability of the system and feedback

collection information shall be achieved through the process of

database manipulation.

2. The system shall be able to be reused for each new semester.

3. If no network connection can be established to receive the feedback,

the students, shall be allowed to enter feedback later.

4. If a network connection is lost during feedback collection, the

program shall allow the student to transmit feedback at a later time.


17

3.6.2 Availability

1. The system shall be available to all students through Information

Systems during their normal hours of operation.

2. During feedback collection every system is connected to the network

for entrance of feedback and data is to be transmitted over the

network and stored in database.

3.6.3 Security

1. The security of a user must be consistent through the use of

passwords.

2. In order to take feedback or edit database information, the instructor

shall be required to enter a password. This password shall be stored

on the instructor’s database after initial entry, in order that it must

only be entered once.

3. Passwords shall be stored in an instructor database and verified upon

each session of feedback database modification.

4. An instructor shall be allowed to change his/her password only by

supplying his/her Existing password. The updated password shall be

stored in the instructor database and on the instructor’s PC.

3.7 Organizing The Specific Requirements

3.7.1 Features

1. Cut your time – by giving feedback on online system when compared

to the manual process this saves time of user.

2. Manage the entire process – the entire process of giving feedback

and viewing that report after giving feedback can manage easily.

3. Enhance the staff – find the details about the lecturer’s interest in

teaching to the students.


18

4. Meet web standards – an easy to use system that successfully

combines form with function.

3.7.2 Stimulus and Response

1. Stimulus: User loads system.

Response: System queries server and if a database exists for the current date,

time, and user, then that roster is retrieved and displayed.

2. Stimulus: User requests that a student is entered the feedback.

Response: The students has entered feedback to a system and registered that

event as well.

3. Stimulus: User requests that the data be sent to the server for storage.

Response: The absence data for the current roster are transmitted to the server.

4. Stimulus: Server receives data indicating that the feedback about his/her is going less than required feedback.

Response: E-mail is sent to that faculty.


19

7. Change Management Process

1. Further enhancements can be made in designing the screens. 2. Some more forms can also be added so as to better retrieve the feedback

details. 3. Various other options can also be added for the better usability of project.

8. Document Approval

We extend our profound gratitude to our project Mentor Mr. Vikas Singal

for his valuable guidance, interest and suggestions throughout the course of the project. We feel honoured and privileged to work under him. He shared his vast pool of knowledge with us that helped us steer through all the difficulties with ease. This report would not have been possible without his guidance and we would like to thank him for everything he has done for us.

( Vikas Singal )

( Date: )


20

9. Supporting Information

The .NET Framework is designed for cross-language compatibility. Cross-

language compatibility means, an application written in Visual Basic.NET may

reference a DLL file written in C# (C-Sharp). A Visual Basic.NET class might be

derived from a C# class or vice versa.

Components OF .NET FRAMEWORK:

Common Language Runtime (CLR)

Class Libraries

Common Language Specification:

The common Language Specification (CLS) describes a set of features that

different languages have in common. The CLS includes a subset of Common Type

System (CTS) which define the rules concerning data types and ensures that code

is executed in a safe environment.

Software Requirements Specification

Documents

Transcript of Software Requirements Specification