CateyesJhingaLalaLife

SoftwareRequirementsSpecification
V1.0
10thMarch,2016
MDMajidJahangir
LifesArchitect

Preparedfor
CateyeKiZindagiLifePrinciples
Instructor:KhadijaChowdhry
Ph.D(PassedHighSchoolwithDifficulty)
Spring2016

RevisionHistory
Date
03.10.201
6

Description
V1.0

Author
MdMajidJahangir

Comments
((shit))2Shitjustgot
real.

DocumentApproval
ThefollowingSoftwareRequirementsSpecificationhasbeenacceptedandapprovedbythe
following:
Signature

PrintedName

Title

MDMajidJahangir

LifesArchitect

KhadijaChowdhry

Instructor

Date

TableofContents
REVISIONHISTORY................................................................................................................................................II
DOCUMENTAPPROVAL........................................................................................................................................II
1.INTRODUCTION.....................................................................................................................................................1
1.1PURPOSE...............................................................................................................................................................1
1.2SCOPE...................................................................................................................................................................1
1.3DEFINITIONS,ACRONYMS,ANDABBREVIATIONS................................................................................................1
1.4REFERENCES.........................................................................................................................................................1
2.GENERALDESCRIPTION....................................................................................................................................2
2.1PRODUCTPERSPECTIVE........................................................................................................................................2
2.2PRODUCTFUNCTIONS...........................................................................................................................................2
2.3USERCHARACTERISTICS......................................................................................................................................2
2.4GENERALCONSTRAINTS.......................................................................................................................................2
2.5ASSUMPTIONSANDDEPENDENCIES......................................................................................................................2
3.SPECIFICREQUIREMENTS................................................................................................................................2
3.1EXTERNALINTERFACEREQUIREMENTS...............................................................................................................3
3.1.1UserInterfaces.............................................................................................................................................3
3.1.2HardwareInterfaces....................................................................................................................................3
3.1.3SoftwareInterfaces......................................................................................................................................3
3.1.4CommunicationsInterfaces.........................................................................................................................3
3.2FUNCTIONALREQUIREMENTS...............................................................................................................................3
3.2.1<FunctionalRequirementorFeature#1>..................................................................................................3
3.2.2<FunctionalRequirementorFeature#2>..................................................................................................3
3.3USECASES............................................................................................................................................................3
3.3.1UseCase#1.................................................................................................................................................3
3.3.2UseCase#2.................................................................................................................................................3
3.4CLASSES/OBJECTS..............................................................................................................................................3
3.4.1<Class/Object#1>....................................................................................................................................3
3.4.2<Class/Object#2>....................................................................................................................................3
3.5NONFUNCTIONALREQUIREMENTS......................................................................................................................4
3.5.1Performance.................................................................................................................................................4
3.5.2Reliability.....................................................................................................................................................4
3.5.3Availability...................................................................................................................................................4
3.5.4Security........................................................................................................................................................4
3.5.5Maintainability.............................................................................................................................................4
3.5.6Portability....................................................................................................................................................4

3.6INVERSEREQUIREMENTS......................................................................................................................................4
3.7DESIGNCONSTRAINTS..........................................................................................................................................4
3.8LOGICALDATABASEREQUIREMENTS..................................................................................................................4
3.9OTHERREQUIREMENTS........................................................................................................................................4
4.ANALYSISMODELS..............................................................................................................................................4
4.1SEQUENCEDIAGRAMS..........................................................................................................................................5
4.3DATAFLOWDIAGRAMS(DFD)...........................................................................................................................5
4.2STATETRANSITIONDIAGRAMS(STD)................................................................................................................5
5.CHANGEMANAGEMENTPROCESS................................................................................................................5
A.APPENDICES..........................................................................................................................................................5
A.1APPENDIX1.........................................................................................................................................................5
A.2APPENDIX2.........................................................................................................................................................5

1.Introduction
1.1 Purpose
ThepurposeofthisdocumentistoprovidelifechangingsolutionstothesubjectCateye,
providingdetailedimpedimentstoitslifecycleandcomingupwithamodeltomitigatethose
threatsandimpediments.

1.2 Scope
ThesesolutionsystemwillbeaGenericProblemSolverforpeoplewhoselivesrevolvearound
MaandMaasikeDaabiswithsomeextraGaramMasala.Thissystemwillbedesignedto
maximizetheCateyesproductivityandthinkingprocessbyprovidingreadymadesolutionsto
assistinautomatingthedecisionmakingprocess,whichwouldotherwisehavetobeperformed
manually,whichthesubjectistoolazytoperform.

1.3 Definitions, Acronyms, and Abbreviations

CateyeThesubjectbeingdiscussed,havinghighentropy,withaweirdwalkstanceand

abitofpakodanose,sometimestooflashyandhavingweird,crazypeopleinitslife.
BateyeAnothersubject,havingthebestintentions,abitcrazy,likeVodafonespug:
alwaysthereforfriends.NeverknewwhyitgottermedasBateye.
VNPItstandsforVeryNicePerson.Anothersubject,selfproclaimedniceperson,
indeednicebutstupidandcrazylikeabovetwo.
DulYetanothersubject,moviebuff.Irony:itslifehasbecomelikeaChinesemovie,it
isjustwatching,andnotabletocomprehendwhatexactlyitis.

1.4 References
Thereferenceshavebeentakenfromsourcessuchasfollows:
Chitchat@NovellCafeteria.
Chitchatpostdinner.
HikeandWhatsApp
ChaiPointpeCharcha
RMZkiwaadiyomediscussions.

2.GeneralDescription
2.1 Product Perspective
ThissubsectionoftheSRSputstheproductintoperspectivewithotherrelatedproductsor
projects.(SeetheIEEEGuidetoSRSformoredetails).

2.2 Product Functions

ThissubsectionoftheSRSshouldprovideasummaryofthefunctionsthatthesoftwarewill
perform.

2.3 User Characteristics

ThissubsectionoftheSRSshoulddescribethosegeneralcharacteristicsoftheeventualusersof
theproductthatwillaffectthespecificrequirements.(SeetheIEEEGuidetoSRSformore
details).

2.4 General Constraints

ThissubsectionoftheSRSshouldprovideageneraldescriptionofanyotheritemsthatwill
limitthedevelopersoptionsfordesigningthesystem.(SeetheIEEEGuidetoSRSforapartial
listofpossiblegeneralconstraints).

2.5 Assumptions and Dependencies

ThissubsectionoftheSRSshouldlisteachofthefactorsthataffecttherequirementsstatedin
theSRS.Thesefactorsarenotdesignconstraintsonthesoftwarebutare,rather,anychangesto
themthatcanaffecttherequirementsintheSRS.Forexample,anassumptionmightbethata
specificoperatingsystemwillbeavailableonthehardwaredesignatedforthesoftwareproduct.
If,infact,theoperatingsystemisnotavailable,theSRSwouldthenhavetochangeaccordingly.

3.SpecificRequirements
ThiswillbethelargestandmostimportantsectionoftheSRS.Thecustomerrequirementswill
beembodiedwithinSection2,butthissectionwillgivetheDrequirementsthatareusedto
guidetheprojectssoftwaredesign,implementation,andtesting.
Eachrequirementinthissectionshouldbe:

Correct

Traceable(bothforwardandbackwardtoprior/futureartifacts)

Unambiguous

Verifiable(i.e.,testable)

Prioritized(withrespecttoimportanceand/orstability)