ACADEMICRESULTMANAGEMENTSYSTEM

ReportI

03/09/2015

AyushiJain(04)
AyushiKumari(06)

TableofContents
1.INTRODUCTION.....................................................................................................................................................1
1.1PURPOSE...............................................................................................................................................................1
1.2SCOPE....................................................................................................................................................................1
1.3DEFINITIONS,ACRONYMS,ANDABBREVIATIONS................................................................................................1
1.4REFERENCES.........................................................................................................................................................1
1.5OVERVIEW
2.GENERALDESCRIPTION....................................................................................................................................2
2.1PRODUCTPERSPECTIVE........................................................................................................................................2
2.2PRODUCTFUNCTIONS...........................................................................................................................................2
2.3USERCHARACTERISTICS......................................................................................................................................2
2.4GENERALCONSTRAINTS.......................................................................................................................................2
2.5ASSUMPTIONSANDDEPENDENCIES......................................................................................................................3
3.SPECIFICREQUIREMENTS................................................................................................................................2
3.1EXTERNALINTERFACEREQUIREMENTS...............................................................................................................3
3.1.1UserInterfaces.............................................................................................................................................3
3.1.2HardwareInterfaces....................................................................................................................................4
3.1.3SoftwareInterfaces......................................................................................................................................4
3.1.4CommunicationsInterfaces..........................................................................................................................4
3.2FUNCTIONALREQUIREMENTS...............................................................................................................................4
3.3OTHERREQUIREMENTS........................................................................................................................................4
4.ANALYSISMODELS..............................................................................................................................................5
4.1FLOWCHART........................................................................................................................................................5
4.2.MODULEDESCRIPTION........................................................................................................................................5

ACADEMICRESULTMANAGEMENTSYSTEM

1.Introduction
ThisdocumentaimsatdefiningoverallsoftwarerequirementforACADEMICRESULT
MANAGEMENTSYSTEM.Effortshavebeenmadetodefinetherequirements
exhaustivelyandaccurately.Thefinalproductwillbehavingonly
features/functionalitiesmentionedinthisdocumentandassumptionsforany
additionalfunctionality/featureshouldnotbemadebyanyofthepartiesinvolved
indeveloping/testing/implementing/usingthisproduct.

1.1Purpose
Thisspecificationdocumentdescribesthecapabilitiesthatwillbeprovidedbythe
softwareapplicationSTUDENTRESULTMANAGEMENTSYSTEM.Italsostatesthe
variousconstraintsbywhichthesystemwillabide.Theintendedaudienceforthis
documentarethedevelopmentteam,testingteamandendusersoftheproduct.

1.2Scope
Theapplicationwillmanagetheinformationaboutvariousstudentsenrolledinthis
courseindifferentyears,thesubjectsofferedduringdifferentsemestersofthecourse,the
marksobtainedbythevariousstudentsinvarioussubjectsindifferentsemesters.
Theapplicationwillgreatlysimplifyandspeeduptheresultpreparationandmanagement
process.

1.3Definitions,Acronyms,andAbbreviations
SRSSoftwareRequirementSpecification
IEEEThe Institute of Electrical and Electronics Engineers
DFDDataFlowDiagram
DBDatabase
OSOperatingSystem

1.4References
IEEE8301998standardforwritingSRSdocument.
Wikipedia
SoftwareengineeringbyKKAgrawal
SoftwareengineeringbyRogerS.Pressman

SoftwareRequirementsSpecification

ACADEMICRESULTMANAGEMENTSYSTEM

1.5Overview
StudentsinformationisstoredinmysqltheauthorityisgiventoAdministrator;hegives
thepermissiontoinstructortoenterthedepartmentdataandstudentinformation.The
securityisprovidingbygivingpasswordtoeachinstructor..

2.GeneralDescription
ThissectionoftheSRSshoulddescribethegeneralfactorsthataffect'theproductandits
requirements.Itshouldbemadeclearthatthissectiondoesnotstatespecific
requirements;itonlymakesthoserequirementseasiertounderstand.

2.1ProductPerspective
Theapplicationwillbewindowsbased,selfcontainedandindependentsoftwareproduct.
FrontendclientApplication
(with
data/entry/update/delete/view
andreportingfacility)

Backend
DB

2.2ProductFunctions
1)InformationaboutthevariousUsers
2)Informationaboutsubjectsofferedinvarioussemesters
3)MarksobtainbyStudentsindifferentsemesters
4)GenerationofReports

2.3UserCharacteristics
ThissubsectionoftheSRSshoulddescribethosegeneralcharacteristicsoftheeventual
usersoftheproductthatwillaffectthespecificrequirements.(SeetheIEEEGuideto
SRSformoredetails).

2.4GeneralConstraints

Usersatuniversitywillhavetoimplementasecuritypolicytosafeguardthe
marksrelatedinformationbeingmodifiedbyunauthorizedusers(bymeansof
gainingaccesstothebackenddatabase)

SoftwareRequirementsSpecification

ACADEMICRESULTMANAGEMENTSYSTEM

2.5AssumptionsandDependencies
1)Thenumberofsubjectstobetakenbythestudentineachsemesterdoesnotchange.
2)Thesubjecttypesdonotchange.
3)Thenumberofsemesterdonotchange.
4) The users have sufficient knowledge of computers.
5) The users know the English language, as the user interface will be provided in
English.

3.SpecificRequirements
Thissectioncontainsthesoftwarerequirementstoalevelofdetailsufficienttoenable
designerstodesignthesystemandtesterstotestthatsystem.

3.1ExternalInterfaceRequirements
3.1.1UserInterfaces
Thefollowingscreenswillbeprovided:
Loginscreen:Thiswillbethefirstscreenthatwillbedisplayed.Itallowsusertoaccess
differentscreensbasedupontheuserrole.Variousfieldsavailableonthisscreenwillbe
Userid:alphanumericoflengthupto10char.
Password:alphanumericoflengthupto10char
Role:Willhavethefollowing
Values:Administrator,DataentryOperator,student,teacher
2)SubjectinfoParameterScreen:
ThisscreenwillbeaccessibleonlytotheAdministrator.Itwillallowtheusertoenterthe
semesternumberforwhichtheuserwantstoaccessthesubjectinformation.
3)StudentinfoParameterScreen:
ThisscreenwillbeaccessibleonlytotheAdministrator.Itwillallowtheusertoenterthe
BatchYearforwhichtheuserwantstoaccessthestudentinformation.
4)StudentInformationScreen:ThisscreenwillbeaccessibleonlytotheAdministrator.
Itwillallowtheusertomodifytheinformationaboutnew/existingstudentforparticular
batchyear.Variousfieldsavailableonthesescreenare:
StudentEnrollmentNo:oftheformatB.E/YYYYwhereYYYYrepresentsthebatchyear
StudentName:onlyalphabeticlettersandlengthupto40chars.
BatchYear:oftheformatYYYY
5)MarksEntryParameterScreen:ThisscreenwillbeaccessibleonlytotheTeacher.It
willallowtheusertoentertheBatchYear,thesemesternumberandthesubjectfor
whichtheuserwantstoaccessthemarksinformation.
6)Marksentryscreen:Screen:ThisscreenwillbeaccessibleonlytotheTeacher.Itwill
SoftwareRequirementsSpecification

ACADEMICRESULTMANAGEMENTSYSTEM

allowtheusertoadd/modify/deleteinformationaboutthemarksobtainedintheselected
subjectbydifferentstudents.ItincludesStudentenrollmentno,studentname,internal
marks,externalmarks,totalmarks.

3.1.2HardwareInterfaces
1)Intelp4processorwithminimum2GHzspeed.
2)RAM:Minimum1GB
3)HardDisk:min20GB

3.1.3SoftwareInterfaces
1)TurboC++
2)DBServer:SQLSERVER2008
3)OS:WindowVista/XP/7/8/10

3.2FunctionalRequirements
Dependingupontheuserrolehe/shewillbeabletoaccessonlythespecificmodulesof
thesystem.
1)Loginfacilityforenablingonlyauthorizedaccesstothesystem
2)User(withroleDataEntryoperator)willbeabletomodify/add/deleteinformation
aboutdifferentstudentsthatareenrolledforthecourseindifferentyears.

3.3OtherRequirements
NONFUNCTIONALREQUIREMENT
1.SafetyRequirements
Thedatabasemaygetcrashedatanycertaintimeduetovirusoroperatingsystem
failure.Therefore,itisrequiredtotakethedatabasebackup
2.SecurityRequirements
Wearegoingtodevelopasecureddatabasefortheuniversity.Dependinguponthe
categoryofusertheaccessrightsaredecided.Itmeansiftheuserisanadministratorthen
hecanbeabletomodifythedata,delete,appendetc.Allotherusersotherthanstaffonly
havetherightstoretrievetheinformationaboutdatabase.
3.HardwareConstraints
Thesystemrequiresadatabaseinordertostorepersistentdata.Thedatabaseshould
SoftwareRequirementsSpecification

ACADEMICRESULTMANAGEMENTSYSTEM

havebackupcapabilities
DBRequirement
The following information will be placed in DB:
1) Subject info: Subject Name, Code, Semester
2) Student Info: Student Enrolment Number, Student name, enrollment year.
3) Marks info: Student Enrolment , Semester, internal marks in each subject, external
marks in each subject
4) User Account Info: UserName, User Id, password, role

4.AnalysisModels
4.1FlowChart
Contextdiagram

SoftwareRequirementsSpecification

ACADEMICRESULTMANAGEMENTSYSTEM

LEVEL1DFD

SoftwareRequirementsSpecification

ACADEMICRESULTMANAGEMENTSYSTEM

LEVEL2DFD

SoftwareRequirementsSpecification

ACADEMICRESULTMANAGEMENTSYSTEM

USECASEDIAGRAM

SoftwareRequirementsSpecification

ACADEMICRESULTMANAGEMENTSYSTEM

SoftwareRequirementsSpecification

ACADEMICRESULTMANAGEMENTSYSTEM

USECASEDIAGRAM

SoftwareRequirementsSpecification

Page

ACADEMICRESULTMANAGEMENTSYSTEM

ERDIAGRAM

SoftwareRequirementsSpecification

Page

ACADEMICRESULTMANAGEMENTSYSTEM

SoftwareRequirementsSpecification

Page