SoftwareRequirementsSpecification

for
WorkMonitoringSystem

Version1.0approved

Preparedby
Sr.N
NAME
o
1 SmritiMurali
2 V.Krishnapriy
a

ROLL
NUMBER
13CO246
13CO153

COURSESoftwareEngineering

DATE17/01/2015

TableofContents

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

1.

Introduction

1.1

Purpose

ThepurposeofthisdocumentistopresentadetaileddescriptionoftheWeb
applicationforNITKtenderallocationsystem.Itwillexplainthepurposeand
featuresofthesystem,theinterfacesofthesystem,whatthesystemwilldo,
theconstraintsunderwhichitmustoperateandhowthesystemwillreactto
externalstimuli.Thisdocumentisintendedforboththestakeholdersandthe
developersofthesystemandwillbeproposedtotheconcernedProjectHead
forit'sapproval.
1.2

DocumentConventions

IngeneralthisdocumentfollowstheIEEEformattingrequirements.UseArial
fontsize11,or12throughoutthedocumentfortext.Useitalicsforcomments.
Documenttextshouldbesinglespacedandmaintainthe1marginsfoundin
thistemplate.
2.
1.3IntendedAudience
Theintendedreadersofthisdocumentarethedeveloperofthewebsite,
testers,NITKadministrators,managersandcoordinatorsaswellasbusinesses
intendingwithprovisionofgoods/servicestotheinstitute
1.4ProductScope
ThissoftwaresystemwillbeaTenderAllocationApplicationforNITk
Surathkal.Thissystemwillbedesignedtosimplifythetenderallocation
processoftheinstitutebyprovidingtoolstoassistinautomatingthetask,
whichwouldotherwisehavetobeperformedmanually.Bymaximizingthe
workefficiencyandproductionthesystemwillmeettheinstitute'sneedswhile
remainingeasytounderstandanduse.
Morespecifically,thissystemisdesignedtoallowaninstitutecommunicate
withagroupofinterestedbusinesses.Thisprocessinvolves:
displayingnoticesfortendersissuedbyvariousdepartmentsoftheinstitute
submissionoftendersbyserviceproviders
openingofthetendersonthespecifieddate
selectionofasuitabletenderbytheinstitute.
correspondancebetweentheadministrativeofficesoftheinstituteand

concernedserviceprovider.
Preformattedformsareusedineverystageofthetenderallocationprocess
throughthesystemtoprovideauniformtaskmanagementprocess.Thesystem
alsocontainsadatabasecontainingalistofprojectsandtendersissued.
1.2References
[1]IEEE.IEEEStd8301998IEEERecommendedPracticeforSoftware
RequirementsSpecifications.IEEEComputerSociety,1998.
[2]IanSomerville,SoftwareEngineering,NewYork,PrincetonHallIndia
Publishing,2005.
2.OverallDescription
2.1ProductPerspective
Thisproduct/applicationaimstoreplacethetediousmanualtenderallocation
process,whichiscurrentlyfollowed,withonlinewebapplicationenhancing
efficiency,transparency,datastorageandretrievalsystems.Henceitimproves
thelargersystemwhichoutsourcesdevelopment/renovationprojects
undertakenbytheinstitutetointerestedcompanies.
2.2ProductFunctions
Itprovidesaplatformforvariousdepartmentsoftheinstituteto:
Publishnoticesofproposedrequestsfortenders
Advertiserequestfortenders
Sendnotificationstoregisteredbusinessesaboutnewopportunities
Provideaccesstotenderdocumentationandotherdetailedinformation
Issueupdatesandadjustmentsregardingtenders
Receiveelectronictenderdocuments
Reportcontractinformationtothemarket
Italsoprovidesaconvenientmechanismbywhichvariouscompaniescan:
Searchandbrowsetenderadvertisementsandinvitations
Accesstenderdocumentsandotherspecificinformation
Lodgetendersonlin
Learnaboutthetenderingprocess,rulesandguidelines
2.3UserClassesandCharacteristics
ThereareessentiallytwoclassesofusersfortheOTA:
theinstitutewhowishestocreate/assigntendersfortheprojects,
thecompaniesinterestedinprovidingtherequiredgoods/servicestothe
institute.
Thecompanyneedstoknowtheexactnatureoftheproposedproject,suchas
thedeadlineaswellasresourcesrequired,andmustpossessthetechnical
knowhowtousetheinterfaceforsubmittingetenders.Theinstitute
administratorsmustbefullyqualifiedinusingOTAapplicationaswell.
2.4*OperatingEnvironment
TheOTAwebapplicationshalloperateonallpopularbrowsers.
2.5*DesignandImplementationConstraints
Themobileapplicationisconstrainedbythesystemhardwareandsoftware
resourcesavailableontheuser'sdevice.Thecommunicationinterfaceis
dependentonthespeedoftheInternetconnectionwithinthedevice.Since
thereareseveralcompanieswhoprovidesinternet,thecommunicationspeed
ofmayvary.Sincetheapplicationfetchesdatafromthedatabaseoverthe
Internet,itiscrucialthatthereisanInternetconnectionfortheapplicationto
function.
Themobileapplicationwillbeconstrainedalsobythecapacityofthe

database.
2.6UserDocumentation
Ausermanualintendedforfirsttimeusersofthesoftwarehasbeendesigned
andwillbeprovidedtoallcompanies/organisationswhowishtousethe
applicationatthetimeofdownload/purchase.
2.7*AssumptionsandDependencies
Oneassumptionabouttheproductisthatitwillalwaysbeusedonbrowsersor
machinesthathaveenoughperformanceandsupportthelatestframeworks.
3.

ExternalInterfaceRequirements

3.1

UserInterfaces

Thissectionprovidesadetaileddescriptionofallinputsintoandoutputsfrom
thesystem.Italsogivesadescriptionofthehardware,softwareand
communicationinterfacesandprovidesbasicprototypesoftheuserinterface.
3.2

HardwareInterfaces

Since neither the mobile application nor the server have any designated
hardware, it does not have any direct hardware interfaces. The hardware
connection to the database server is managed by the underlying operating
systemonthemobilephone.
3.3

SoftwareInterfaces

Themobileapplicationc+ommunicatesthroughinternet.Thecommunication
betweenthedatabaseandmobileapplicationconsistsofoperationconcerning
bothreadingandwritingthedatabytheowner,employeeandsupervisor.The
ownerhasmaximumprivilegeswhiletheemployeeanduserhavelimited
privileges.
3.4

CommunicationsInterfaces

Thecommunicationbetweenthedifferentpartsofthesystemsuchasowner
,employeeandsupervisorisimportantsincetheydependoneachotherfor
efficientallotmentofresources.However,inwhatwaythecommunicationis
achieved is not important for the WMS and is therefore handled by the
underlyingoperatingsystemsfortheapplication.
4.

FUNCTIONALREQUIREMENTs
ID:FR1
TITLE:Downloadmobileapplication

DESC:Ausershouldbeabletodownloadthemobileapplicationthrough
eitheranapplicationstoreorsimilarserviceonthemobilephone.The
applicationshouldbefreetodownload.
RAT:Inorderforausertodownloadthemobileapplication.
DEP:None
ID:FR2
TITLE:Downloadandnotifyusersofnewreleases
DESC:Whenanew/updatedversionorreleaseofthesoftwareisreleased,
theusershouldcheckforthesemanually.Thedownloadofthenew
releaseshouldbedonethroughthemobilephoneinthesamewayas
downloadingthemobileapplication.
RAT:Inorderforausertodownloadanew/updatedrelease.
DEP:FR1
ID:FR3
TITLE:UserregistrationMobileapplication
DESC:Giventhatauserhasdownloadedthemobileapplication,thenthe
usershouldbeabletoregisterthroughthemobileapplication.The
usermustprovideusername,passwordandemailaddress.Theuser
canchoosetoprovidearegularlyusedphonenumber.Theusershould
alsobeabletoregisterasauserandaddemployeesandsupervisorsto
hiscircle.
RAT:Inorderforausertoregisteronthemobileapplication.
DEP:FR1
ID:FR4
TITLE:UserloginMobileapplication
DESC:Giventhatauserhasregistered,thentheusershouldbeabletolog
intothemobileapplication.Thelogininformationwillbestoredon
thephoneandinthefuturetheusershouldbeloggedin
automatically.
RAT:Inorderforausertoregisteronthemobileapplication.
DEP:FR1,FR3
ID:FR5
TITLE:MobileapplicationProjectFeed
DESC:Giventhatauserisloggedintothemobileapplication,thenthefirst
pagethatisshownshouldbetheprojectfeedpage.Theusershouldbe
abletoseetherecentupdatesmadetohis/hercurrentprojects.Auser

shouldalsobeabletoposthisownupdatesregardingtheprojects.
Thisfeedvarieswiththetypeofuseremployee,ownerorsupervisor.
RAT:Inorderforthevarioususerstosatyupdatedontheongoingprojects
andmodifythem.
DEP:FR1,FR3,FR4
5.

OtherNonfunctionalRequirements

5.1

PerformanceRequirements

5.1.1 Responsetime
Themaximumresponsetimeforthesubmissionofajobwillbe0.5minutes.
5.1.2 Capacity
Themaximumnumberofprojectsschedulableislimitedonlybythecapacity
ofthenodestofulfillthejobsdeadlines;thereisnoupperlimitinherentinthe
WMSassuch.
5.1.3 Deadlinesensitivity
Assumingsubmittedstatisticsforjobsareaccurate,theWMSwillensurethat
alljobsarecompletedwitha10%errorallowance.
5.1.4 Costsensitivity
Under all circumstances, the maximum cost payable as submitted by the
developerwillbethemaximumcostchargedtotheowneroftheapplication.
5.2

SafetyRequirements

Asitisstatedwithmanywarningsintheprogram,datalossisaserious
posiibility.Backupalldataand/orusetheprogramwithextremecaution.WMS
comeswithabsolutelynowarrantyandcannotbemaderesponsibleforanyloss
ofdata.

5.3

SecurityRequirements

5.3.1 DataTransfer
Thesystemshallusesecuresocketsinalltransactionsthatincludeany
confidentialcustomerinformation.
Thesystemshallconfirmalltransactionswithuser'swebbrowser.
Thesystemshallnotleaveanycookiesonthecustomerscomputercontaining
theuserspassword.
Thesystemshallnotleaveanycookiesonthecustomerscomputercontaining
anyoftheusersconfidentialinformation.
5.3.2 DataStorage
Theuser'swebbrowsershallneverdisplayauser'spassword.Itshallalways
beechoedwithspecialcharactersrepresentingtypedcharacters.
Thesystemsbackendserversshallneverdisplayauser'spassword.Theuser's
passwordmayberesetbutnevershown.
Thesystemsbackendserversshallonlybeaccessibletoauthenticated
administrators.
Thesystemsbackenddatabasesshallbeencrypted.
5.4

SoftwareQualityAttributes

Theapplicationprovidesaquitefriendlyuserfriendlyinterfacewithit's
operationsaccessiblefromthemenubarandthemaintoolbar.Anaverageor
casualusershouldnotfaceanyproblemsusingtheapplication.
CurrentlythissoftwarerunsonlyontheAndroidOperatingSystemandcannotbe
exportedtootherplatforms.
AppendixA:Glossary
Term
User

Defination
Someonewhointeractswiththemobilephoneapplication.
Therearethreetypes
1.OwnerHe/sheisresponsibleforaddingandmanagingall
projectsandemployees.
2.Supervisorisresponsibleformonitoringthecompletion

oftheprojectsassignedtotheirrespectiveworkstations.
3.Employeecanviewtheprojectsassignedtohim/herand
thedeadlines.
Application
Store

Aninstalledapplicationonmobilephonewhichhelpsuserto
findnew
compatible applications with mobile phone platform and
downloadthem
fromInternet

Stakeholder

Anypersonwhohasinteractionwiththesystemwhoisnota
developer.

DESC

Description

RAT
DEP

Rational
Dependency