Anda di halaman 1dari 13

Software Requirements

Specification
for

< Grade Report System >


Version 1.0 approved

Prepared by < Mona Javed 001>

<Noman Ali 008>

<Amara Arshad 013>

<Anila Sabir 064>

<University of Gujrat> <25 August, 2017>

Copyright 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Grade report system> Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ........................................................................................................................... iii
1. Introduction ..............................................................................................................................1
1.1 Purpose ............................................................................................................................................ 1
1.2 Document Conventions.................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions .................................................................................. 1
1.4 Product Scope .................................................................................................................................. 2
1.5 References........................................................................................................................................ 2

2. Overall Description ..................................................................................................................2


2.1 Product Perspective ......................................................................................................................... 2
2.2 Product Functions ............................................................................................................................ 2
2.3 User Classes and Characteristics ..................................................................................................... 2
2.4 Operating Environment.................................................................................................................... 3
2.5 Design and Implementation Constraints .......................................................................................... 3
2.6 User Documentation ........................................................................................................................ 3
2.7 Assumptions and Dependencies ...................................................................................................... 3

3. External Interface Requirements ...........................................................................................3


3.1 User Interfaces ................................................................................................................................. 3
3.2 Hardware Interfaces ......................................................................................................................... 4
3.3 Software Interfaces .......................................................................................................................... 4
3.4 Communications Interfaces ............................................................................................................. 5

4. System Features........................................................................................................................5
4.1 System Feature 1 .............................................................................................................................. 5
4.2 System Feature 2 (and so on)........................................................................................................... 6

5. Other Nonfunctional Requirements .......................................................................................6


5.1 Performance Requirements .............................................................................................................. 6
5.2 Safety Requirements ........................................................................................................................ 7
5.3 Security Requirements ..................................................................................................................... 7
5.4 Software Quality Attributes ............................................................................................................. 7
5.5 Business Rules ................................................................................................................................. 7
Software Requirements Specification for <Grade report system> Page iii

6. Other Requirements .................................................................. Error! Bookmark not defined.


Appendix A: Glossary....................................................................................................................8
Appendix B: Analysis Models .......................................................................................................9
Appendix C: To Be Determined List ..........................................................................................10

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Grade report system> Page 1

1. Introduction
1.1 Purpose
This SRS specifies software requisite for release 1.0 of the Grading System. This document
is intended to be used by the members of the project team to substantiate and effectuate the proper
functioning of the system. Consumers will scrutinize this document in order to assimilate the goals
of the Grading System furthermore to conclude the business potential of this product. All
requirements specified here are high priority and are committed for release 1.0 unless otherwise
noted.
The purpose of grading is to describe how well students have achieved the learning objectives or
goals established for a class or course of study. Grades should reflect students performance on
specific learning criteria. Establishing clearly articulated criteria for grades makes the grading
process more fair and equitable. Progress criteria are used by educators who believe the most
important aspect of grading is how much students gain from their learning experiences

1.2 Document Conventions


Four typographic conventions are used to call attention to specific words and phrases. These
conventions, and the circumstances they apply to, are as follows. Mono-spaced Bold Used to
highlight system input, including shell commands, file names and paths. Also used to highlight
keycaps and key combinations.
For example: To see the contents of the file my_next_bestselling_novel in your current working
directory, enter the cat my_next_bestselling_novel command at the shell prompt and press Enter to
execute the command.
The above includes a file name, a shell command and a keycap, all presented in mono-spaced bold
and all distinguishable thanks to context. Key combinations can be distinguished from it.
Press Enter to execute the command. Press Ctrl+Alt+F2 to switch to the first virtual terminal. Press
Ctrl+Alt+F1 to return to your X-Windows session.

1.3 Intended Audience and Reading Suggestions


1.3.1. Note:
Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should
have no negative consequences, but you might miss out on a trick that makes your life easier.
1.3.2. Important:
Important boxes detail things that are easily missed: configuration changes that only apply
to the current session, or services that need restarting before an update will apply. Ignoring a box
labeled Important will not cause data loss but may cause irritation and frustration.
1.3.3 Warning:
Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
Software Requirements Specification for <Grade report system> Page 2

1.4 Product Scope


The Grading System is a based grading system that will allows Administrator to save grade
information. The system also allows Student to view grade information. The Grading System
focuses on feature that allows Teachers to enter the grades of Students.

1.5 References
1) Standard of IEEE Std. 829-1998
2) UOG: www.uog.edu.pk
3) Bird, K. (2006). Student information systems >> How do you spell parental involvement?
S-I-S. THE Journal: Technological Horizons in Education. Retrieved from
http://thejournal.com/Issues/2006/February- 2006.aspx

2. Overall Description

2.1 Product Perspective


The Grading System is a process of applying standardized measurements of varying levels of
achievement in a course. Shows the administration input grades of every student in every level.

2.2 Product Functions


Is an online grading program that calculates students grades? Students can see their grades
anytime they want by logging onto their account. A student can only view his or her own account.
He or she cannot see other students grades. Students can also check on homework assignments,
upcoming events, and attendance using this system. Teachers can post assignments on this system
that allow students to view the assignments and instructions anywhere they have Internet access.

2.3 User Classes and Characteristics


The administration can access the system anytime. The administrations are those who are
responsible in making the system accessible by anyone or for themselves only. They are those
authorized personnel to input the educational standards of the desired institution.
Faculty: The faculty members are responsible in creating and managing the record.
Students: The students are those who can view enroll subjects, view their basic
information and view grades.
Software Requirements Specification for <Grade report system> Page 3

2.4 Operating Environment


The Grading system shall operate with Local Area Network exclusively for schools
computer laboratories only. The Grading System shall permit the user access from the administrator.

2.5 Design and Implementation Constraints


The designing and implementation of grading system is consisted on different constraints as
different language are used to develop this system. Languages use in this system is CSS, java-script,
PHP, jQuery, HTML and My SQL database are used while developing this system.

2.6 User Documentation


Technical documentation refers to the documentation that describes how a product or service
operates. For example, software code documentation, technical specifications and API
documentation. User documentation refers to the documentation for a product or service provided to
the end users. The user documentation is designed to assist end users to use the product or service.
This is often referred to as user assistance. The user documentation is a part of the overall product
delivered to the customer.

2.7 Assumptions and Dependencies


1) The Grading System can be access by the administration.
2) Students can review their information depending on the given schedule.
3) Faculty members can edit the grades depending on the given time that the system will be
open and access by the admin

3. External Interface Requirements

3.1 User Interfaces

Requirement Description

User Interface-0 The Grading System displays shall conform to our UI


Standard.
Software Requirements Specification for <Grade report system> Page 4

User Interface-1 The Grading System shall display, in each view, an option
to navigate to the user documentation.

3.2 Hardware Interfaces

Requirement Description

Hardware Interface-0 The Grading System shall function on any client computer
that has Windows XP, Vista 7, or 8, 10;
2 GHz or faster processor or at least 2 GB of RAM.

3.3 Software Interfaces

Requirement Description

Software Interface-0 MySQL Database Engine.

Software Interface-1 The Grading System shall transmit the Grades that are
being saved to the MySQL Database Engine, after
checking to ensure they are valid.

Software Interface-2 Internet Browsers


Software Requirements Specification for <Grade report system> Page 5

Software Interface-3 The Grading System shall function on any Compatible


Internet Browser.

3.4 Communications Interfaces


HTTP (Hypertext Transfer Protocol) and FTP (File Transfer Protocol) are only two of the
multitude of protocols that are being used in the internet, each with its own function. The purpose of
HTTP is to serve as a means of accessing the world wide web. Websites are accessed using http
with the help of browsers. FTP, as the name implies, is used in transferring files from one computer
to another. It is a less popular protocol due to small number of people who actually use FTP, and
even fewer people who know that they are using it.

FTP is also a good option for people who want to download files. There are FTP servers who host
files and allow people to anonymously login to their site and download huge files. But downloading
isnt a capability that is purely held by FTP, it can also be done with HTTP. The rise in popularity of
downloads in HTTP is due largely to its linkage with the world wide web. Most sites that offer
content for downloads have their files hosted in an HTTP server so that visitors can easily browse
and select their files.

4. System Features
A feature is a distinctive characteristic of a good or service that set it apart from similar
items. Customer, however want a benefit and do not care much about the feature which are touted
by every supplier as unique or superior.

4.1 System Feature 1 (Login)

4.1.1 Description and Priority


This is to use the system but only the features they are authorized to use.
4.1.2 Stimulus/Response Sequences
The administrator once logged into the system, selects feature to register a user.
Software Requirements Specification for <Grade report system> Page 6

4.1.3 Functional Requirements


REQ-1: administrator must be logged into the system
REQ-2: Username Type: Alphanumeric
REQ-3: Name Type: Alphanumeric
REQ-4: Surname Type: Alphanumeric
REQ-5: Password Type: Alphanumeric
REQ-6: Contact Number Type: Integer
REQ-6: Student Number Type: Integer
REQ-6: Role Type: Alphanumeric

4.2 System Feature 2 (Print Form)

4.2.1 Description and Priority


Allows user to print a hard copy format of grades in the current semester
4.2.2 Stimulus/Response Sequences
Once the user has login to their account and views the grades, press the print button and the form
will be printed out in hard copy format
4.2.3 Functional Requirements
Requirement-1: user must log into the system
Requirement-2: print a hardcopy format of grades in current semester

5. Other Nonfunctional Requirements

5.1 Performance Requirements


Performance Requirement-1:
The system will accommodate users with valid accounts inside the database where they can
use the system within a limited period of time and every session will have no time duration.
Performance Requirement-2:
User Interfaces inside the system will take a response no longer than two seconds after users
have logged inside the database since it is an offline database.
Software Requirements Specification for <Grade report system> Page 7

Performance Requirement-3:
The system will display messages to users not more than 2 seconds every time the users
submit or take necessary information to the system.

5.2 Safety Requirements


The system is an offline database which protects it from unwanted viruses as well as online
hackers coming from the internet that can harm the vital resources inside it.

5.3 Security Requirements


Security Requirement-1:
The system has its own logging scheme to secure the information of users that is being
administered by an authorized personnel.
Security Requirement-2:
The system also has its own idle-state log off program if the user is in the idle state for at
least ten minutes in time.
Security Requirement-3:
The system shall permit only the authorized personnel who are on the list of authorized
Managers to create or edit grades.
Security Requirement-4:
The database manager will set an account to each user to be able to log in the system by
providing a default username and password that can be replaced once the user has entered into their
accounts.

5.4 Software Quality Attributes


Availability-1: The Grading System is accessible to users having an account encrypted inside the
database with limited amount of time to secure important data.
Robustness-1: If the Grading System has faced some technical error prior to grades that are being
submitted or cancelled, the system will automatically recover incomplete files.
Operability-1: The system provides restrictions to users by adding security features (i.e. having a
time frame) for the system be protected from hackers

5.5 Business Rules


Grade report system is very beneficial for any educational institute because they provide
online grading facility. Students and his parents view your result anywhere and anytime.
Software Requirements Specification for <Grade report system> Page 8

6.Other Requirements

6.1 Availability
The Grading System is accessible to users having an account encrypted inside the database
with limited amount of time to secure important data.
6.2 Robustness
If the Grading System has faced some technical error prior to grades that are being submitted
or cancelled, the system will automatically recover incomplete files.

6.3Operability
The system provides restrictions to users by adding security features (i.e. having a time
frame) for the system be protected from hackers.

Appendix A: Glossary
A Grade report system, student management system, school administration
software or student administration system is a management information system for education
establishments to manage student data. Student information systems provide capabilities for
registering students in courses, documenting grading, transcripts, results of student tests and
other assessment scores, building student schedules, tracking student attendance, and managing
many other student-related data needs in a school. A Grade report system should not be confused
with a learning management system or virtual learning environment, where course materials,
assignments and assessment tests can be published electronically.
Software Requirements Specification for <Grade report system> Page 9

Appendix B: Analysis Models


Software Requirements Specification for <Grade report system> Page 10

Appendix C: To Be Determined List


Word Abbreviation
PHP Personal home page

CSS Cascading style sheet

HTML Hypertext markup language

SQL Structured query language

HTTP Hypertext transport protocol

FTP File transport protocol

SRS Software Requirement Specification