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>

Copyright1999byKarlE.Wiegers.Permissionisgrantedtouse,modify,anddistributethisdocument.
SoftwareRequirementsSpecificationfor<Gradereportsystem>
Pageii

TableofContents
TableofContents...........................................................................................................................ii
RevisionHistory.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 DocumentConventions..................................................................................................................1
1.3 IntendedAudienceandReadingSuggestions.................................................................................1
1.4 ProductScope.................................................................................................................................2
1.5 References......................................................................................................................................2
2. OverallDescription..................................................................................................................2
2.1 ProductPerspective........................................................................................................................2
2.2 ProductFunctions...........................................................................................................................2
2.3 UserClassesandCharacteristics....................................................................................................3
2.4 OperatingEnvironment..................................................................................................................3
2.5 DesignandImplementationConstraints.........................................................................................3
2.6 UserDocumentation.......................................................................................................................3
2.7 AssumptionsandDependencies.....................................................................................................3
3. ExternalInterfaceRequirements...........................................................................................4
3.1 UserInterfaces................................................................................................................................4
3.2 HardwareInterfaces........................................................................................................................4
3.3 SoftwareInterfaces.........................................................................................................................4
3.4 CommunicationsInterfaces............................................................................................................4
4. SystemFeatures.......................................................................................................................5
4.1 SystemFeature1...........................................................................Error!Bookmarknotdefined.
4.2 SystemFeature2(andsoon)..........................................................................................................5
5. OtherNonfunctionalRequirements.......................................................................................5
5.1 PerformanceRequirements.............................................................................................................5
5.2 SafetyRequirements.......................................................................................................................5
5.3 SecurityRequirements....................................................................................................................6
5.4 SoftwareQualityAttributes............................................................................................................6
5.5 BusinessRules................................................................................................................................6
6. OtherRequirements...................................................................Error!Bookmarknotdefined.
AppendixA:Glossary....................................................................................................................6
AppendixB:AnalysisModels.......................................................................................................6
AppendixC:ToBeDeterminedList............................................................................................6

RevisionHistory
Name Date ReasonForChanges Version
SoftwareRequirementsSpecificationfor<Gradereportsystem> Page1

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 DocumentConventions
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 keycaps by
the hyphen connecting each part of a key combination. For example:
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 IntendedAudienceandReadingSuggestions
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
SoftwareRequirementsSpecificationfor<Gradereportsystem> Page2

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.

1.3.4 We Need Feedback!

You should over ride this by creating your own local Feedback.xml file.

1.4 ProductScope
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
focusesonfeaturethatallowsTeacherstoenterthegradesofStudents.

1.5 References
1) Standard of IEEE Std. 829-1998
2) UOG: www.uog.edu.pk
3)Bird,K.(2006).Studentinformationsystems>>Howdoyouspellparentalinvolvement?
SIS.THEJournal:TechnologicalHorizonsinEducation.Retrievedfrom
http://thejournal.com/Issues/2006/February2006.aspx

2. OverallDescription

2.1 ProductPerspective

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 ProductFunctions

Isanonlinegradingprogramthatcalculatesstudentsgrades?Studentscanseetheirgradesanytime
theywantbyloggingontotheiraccount.Astudentcanonlyviewhisorherownaccount.Heorshe
cannotseeotherstudentsgrades.Studentscanalsocheckonhomeworkassignments,upcoming
events,andattendanceusingthissystem.Teacherscanpostassignmentsonthissystemthatallow
studentstoviewtheassignmentsandinstructionsanywheretheyhaveInternetaccess.
SoftwareRequirementsSpecificationfor<Gradereportsystem> Page3

2.3 UserClassesandCharacteristics

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
Students: The students are those who can view enroll subjects, view their basic
information and view grades.

2.4 OperatingEnvironment

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 DesignandImplementationConstraints

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 UserDocumentation

<List the user documentation components (such as user manuals, on-line help, and tutorials) that
will be delivered along with the software. Identify any known user documentation delivery formats
or standards.>

2.7 AssumptionsandDependencies

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
SoftwareRequirementsSpecificationfor<Gradereportsystem> Page4

3. ExternalInterfaceRequirements

3.1 UserInterfaces

Requirement Description

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

Standard.

UI-1 The Grading System shall display, in each view, an option

to navigate to the user documentation.

3.2 HardwareInterfaces

Requirement Description

HI-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 SoftwareInterfaces

Requirement Description

SI-0 MySQL Database Engine.

SoftwareRequirementsSpecificationfor<Gradereportsystem> Page5

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

SI-1 Internet Browsers

SI-1.1 The Grading System shall function on any Compatible

Internet Browser.

3.4 CommunicationsInterfaces

<Describe the requirements associated with any communications functions required by this
product, including e-mail, web browser, network server communications protocols, electronic
forms, and so on. Define any pertinent message formatting. Identify any communication
standards that will be used, such as FTP or HTTP. Specify any communication security or
encryption issues, data transfer rates, and synchronization mechanisms.>

4. SystemFeatures
Afeatureisadistinctivecharacteristicofagoodorservicethatsetitapartfromsimilaritems.
Customer,howeverwantabenefitanddonotcaremuchaboutthefeaturewhicharetoutedby
everysupplierasuniqueorsuperior.

4.1 SystemFeature1(Login)

4.1.1DescriptionandPriority
Allowausertologintothesystemusingausernametoauthenticateandauthorizeauser
accordingtotheirspecificusertype.

4.1.2Stimulus/ResponseSequences
Userencountersfrontpageoftheapplication,typesintheirusernameandpasswordand
clicksontheloginbutton.Ifnoerroroccursup,pointuserisredirectedtothemainpagewherethey
haveaccesstoallfeaturestheiruseraccountallows
4.1.3FunctionalRequirements
REQ1:Username Type:Alphanumeric
REQ2:Password Type:Alphanumeric
SoftwareRequirementsSpecificationfor<Gradereportsystem> Page6

4.1.4Administration
InstitutionStandards
Allows the admin/authorized personnel to input the educational standards of the
institution
ViewingTimeManager
Allowstheusertoindicatethespecifieddateandtimetoconstrainstudentstoview
theirgrades.
GradeEditor
Allowstheusertochangethegradesofthestudents.
4.1.5Teachers
Faculty Profile
To show/display the necessary information of the user (teacher)
Student Grading Manager
To allow user to input the final course grade of the student which cannot be tampered
without the authority of the admin.
4.1.6Students
StudentProfile
Displaysthebasicinformationoftheuser(student)
StudentGradeViewer
Displaysthefinalgradeoftheuserforthesemesterthatindicateswhethertheuser
passedorfailedhis/hersubjectstaken.

4.2 SystemFeature2(Signup)

4.2.1DescriptionandPriority
Allow an administrator to add a user to the system with a specific user role allowing
the user to use the system but only the features they are authorized to use.
4.2.2 Stimulus/Response Sequences
The administrator once logged into the system, selects feature to register a user.
4.2.3FunctionalRequirements
REQ1:administratormustbeloggedintothesystem
REQ2:Username Type:Alphanumeric
REQ3:Name Type:Alphanumeric
REQ4:Surname Type:Alphanumeric
REQ5:Password Type:Alphanumeric
REQ6:ContactNumber Type:Integer
REQ6:StudentNumber Type:Integer
REQ6:Role Type:Alphanumeric
SoftwareRequirementsSpecificationfor<Gradereportsystem> Page7

4.3 SystemFeature2(PrintForm)

4.3.1DescriptionandPriority
Allowsusertoprintahardcopyformatofgradesinthecurrentsemester
4.3.2Stimulus/ResponseSequences
Oncetheuserhaslogintotheiraccountandviewsthegrades,presstheprintbuttonandthe
formwillbeprintedoutinhardcopyformat
4.3.3FunctionalRequirements
REQ1:usermustlogintothesystem
REQ2:printahardcopyformatofgradesincurrentsemester

5. OtherNonfunctionalRequirements

5.1 PerformanceRequirements

PR-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.
PR-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.
PR-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 SafetyRequirements

SE-1: 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 SecurityRequirements

SR-1: The system has its own logging scheme to secure the information of users that is being
administered by an authorized personnel.
SR-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.
SR-3: The system shall permit only the authorized personnel who are on the list of authorized
Managers to create or edit grades.
SR-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.
SoftwareRequirementsSpecificationfor<Gradereportsystem> Page8

5.4 SoftwareQualityAttributes

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 BusinessRules

<List any operating principles about the product, such as which individuals or roles can perform
which functions under specific circumstances. These are not functional requirements in
themselves, but they may imply certain functional requirements to enforce the rules.>

AppendixA:Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire
organization, and just include terms specific to a single project in each SRS.>
SoftwareRequirementsSpecificationfor<Gradereportsystem> Page9

AppendixB:AnalysisModels
SoftwareRequirementsSpecificationfor<Gradereportsystem> Page10

AppendixC:ToBeDeterminedList
<Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they
can be tracked to closure.>