Software Requirement Specification (SRS)

Version 1.0

SEMESTER DECEMBER 2016 APRIL 2017

GROUP: M3CS110 4D

MUHAMMAD NURAZIM BIN AZMAN, 2015844038

AHMAD AMIRUL ARIF BIN AZAHARI, 2015823092
MOHAMMAD NAIM BIN OTHMAN, 2015847214

1
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

Table of Contents
1. Overall Description...........................................................................................................2
1.1 Product Perspective...........................................................................................................2
1.2 Product Functions..............................................................................................................3
1.3 User Characteristics..........................................................................................................4
1.4 Operating Environment...................................................................................................5
1.5 General Constraints...........................................................................................................6
1.6 References.............................................................................................................................7
2. External Interface Requirements................................................................................8
2.1 User Interfaces....................................................................................................................8
2.2 Hardware Interfaces.........................................................................................................8
2.3 Software Interfaces............................................................................................................9
2.4 Communications Interfaces...........................................................................................9
3. Functional Requirements.............................................................................................10
4. Other Nonfunctional Requirements........................................................................11
4.1 Performance Requirements.........................................................................................11
4.2 Safety and Security Requirements.............................................................................11
Appendix....................................................................................................................................12

Revision History
Name Date Reason For Changes Version
<name> <dd/mm/yyyy> <reason to change the documentation <x.x>
contents>

1. Overall Description
1.1 Product Perspective

1
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

This system will consist of one part : which is a web portal. The web portal is used by the
supplier,managers and staff to manage the system and also the web portal gives information to the
staffs and managers about program,course and fee in this kindergarten.

ThewebapplicationwillneedtoconnecttoasecureInternetline.TheInternetlinewillprovide
connectiontothewebportalfortheuserstoseetheinformationofsuppliers.Supplierwillusethe
webportaltoupdatetherequiredinformationofthekidsinformationandparentsinformation.

Sincethisisadatacentricproductitwillneedsomewheretostorethedata.Forthat,adatabasewill
beused.Thewebportalwillcommunicatewiththedatabase,howeverinslightlydifferentways.
Thewebportalwillalsogaindatafromthemanagersandstaffandthewebportalwillalsoaddand
modifydata.AllofthedatabasecommunicationwillgoovertheInternet.

Thewebportaldoeshaverestrictions.itmusthavea10mbpsfortheuserandadministratortoadd
andmodifydataofthewebportal.Themaximumamountofharddrivespaceisalso20megabytes.

1.2 Product Functions

Withthewebportal,onlytheuserandadministratorwillonlyusethesystem.Theresultwillbe
basedonthecriteriathestaffsinputs.Thereareseveralsearchcriteriaanditwillbepossibleforthe
administratorandsupplierofthesystemtomanagetheoptionsforthosecriteria.Theresultofthe
searchwillbeviewedeitherinalistview.

2
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

Thewebportalisusebythesupplierandstafftoupdateorenteranewproductinformation
insidethewebportal.Themanagersandalsostaffaretheonlyonethatcanusethewebportal
systemforupdatingprivatedata.Meanwhile,theotheruserscanonlyviewtheinformationbased
ontheupdatemadebythetheuserandadministrator.

1.3 User Characteristics

Therearetwotypesofusersthatinteractwiththesystem:userandadministrators.Eachofthese
fourtypesofusershasdifferentuseofthesystemsoeachofthemhastheirownrequirements.

3
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

Thewebportalisusedbythemanagerstoseeinformationoftheproduct.Thismeansthatthe
managershavetobeabletolookfortheinformationoftheproduct.

Thedoctorwillusethewebportalinstead.Theretheywillmanagetheinformationaboutthepatient
information,forexamplepatientsname,address,contactnumberandalsotheillnessofthepatients.
Thewebsitealsowillalsogiveinformationanyinformationregardingtohealth..Thedoctoralso
willupdatethetreatmentinfoofthepatientinthesystem.

Theadministratorsalsoonlyinteractwiththewebportal.Theyaremanagingtheoverallsystemso
thereisnoincorrectinformationwithinit.Theadministratorcanmanagetheinformationforthe
healthunitandalsogivetheusersanddoctorstousethewebportal.

1.4 Operating Environment

The operating environment of the web portal is based on a software made by the system developer. The
software will be installed inside a computer and other computers devices. The software will be save in a hard
drive.

4
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

The system also needs a fast internet connection in order for the web portal too work. If the operating
environment is slow, for example, the internet connection, the user might not be able to update or store data
inside the web portal due to slow connection. The software must need to be installed if the users wants to use
the system, it is only for the users and also the administrator.

1.5 General Constraints

5
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

ThewebportalneedsagoodInternetconnectionfortheportaltowork,TheInternetaccessis
importantorelsethewebportalcannotbeopenduetoslowinternetconnection.Itwillhardenthe
userandalsothedoctortousethewebportal.

TheInternetconnectionisalsoaconstraintfortheapplication.Sincetheapplicationfetchesdata
fromthedatabaseovertheInternet,itiscrucialthatthereisanInternetconnectionforthe
applicationtofunction.

Thewebportalwillbeconstrainedbythecapacityofthedatabase.Sincethedatabaseisonlyonthe
webportal,itmaybeforcedtoqueueincomingrequestsandthereforincreasethetimeittakesto
fetchdata.

1.6 References

Print References

6
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

Book

-[1] IEEE Software Engineering Standards Committee, IEEE Std 830-1998, IEEE
Recommended Practice for Software Requirements Specifications, October 20, 1998.

[2] Feldt R,re_lecture5b_100914, unpublished.

[3] Davis M A, Just Enough Requirements Management: Where Software Development

Meets Marketing, New York, Dorset House Publishing, 2005.

[4] Karlsson J, A Cost-Value Approach for Prioritizing Requirements, Norges Teknisk-

Naturvitenskapelige Uni. 1997

2. External Interface Requirements

Thissectionprovidesadetaileddescriptionofallinputsintoandoutputsfromthesystem.Italso
givesadescriptionofthehardware,softwareandcommunicationinterfacesandprovidesbasic
prototypesoftheuserinterface.

7
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

2.1 User Interfaces

A first-time user of the web application should see the log-in page when he/she opens the
application. If the staff has not registered, he/she should be able to do that on the log-in page.

If the staff is not a first-time user, he/she should be able to see the search page directly when the
application is opened. Here the user chooses the type of search he/she wants to conduct.

Everyusershouldhaveaprofilepagewheretheycanedittheiremailaddress,phonenumberand
password.Also,theusercansetthemobileapplicationtohis/herpreferredlanguage.ThePicon
showswheretheusercanclicktonavigatetohis/herprofilepage.

Thelistviewfortheresultsisshown.Whenausersearchesbyfee,thisviewshouldbethedefault
one.Thesortingheaderallowstheusertosorttheresultsaccordingtosubject,ageandother
services.Thereisalsoafilteringoption,wheretheusercanchoosetofiltertheresultsbyincreasing
ordecreasingthepriceorpackage.

Theuserandadministratorsinteractwiththesystemthroughawebportal.Ausershouldbeableto
registeronthewebportalinordertologintoregistertheirchildrenintothetuitionandeducare
information.Anadministratorshouldalsobeabletologintothewebportalwherehe/shecan
administerthesystembyforinstanceeditingtuitionandeducareorchildreninformation.

2.2 Software Interfaces

The web application get information about the student details, and with the database to get the
information about the student, see Figure 1. The communication between the database and the web
portal consists of operation concerning both reading and modifying the data, while the
communication between the database and the web application consists of only reading operations.

8
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

2.3 Communications Interfaces

Thecommunicationbetweenthedifferentpartsofthesystemisimportantsincetheydependon
eachother.However,inwhatwaythecommunicationisachievedisnotimportantforthesystem
andisthereforehandledbytheunderlyingoperatingsystemsforboththewebapplicationandweb
portal.

3. Functional Requirements

Users/Stakeholders Function Description

Admin Update Information
After successful login as an

9
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

admin, system will display the

updated students information
such as new students and paid
or unpaid fees.

Admin will confirm the

payment and update the
students information into the
system.

Admin can update any new

subject is available, extra
services, programs and
information of the educare and
tuition center which are
currently stored in the
database. Admin also be able to
delete any students and their
information that are currently
stored.

User will be able to register

their children or check about
their children information or
status in the system that
Register provided by the admin.
User
Access Information
Users also can share their
suggestion for the company or
comments and reports to the
staff or services.

4. Other Nonfunctional Requirements

4.1 Performance Requirements

Thesystemmustbeinteractiveandthedelaysorsystemnotrespondingmustbeless.Soinevery
actionoftheusertothe,thereshouldbenodelays.Incaseofopeningwindowedforms,orpopping
errormessagesandsavingthesettingsorsessionsthereisdelaymuchbelow2seconds.Othercase
ofopeningdatabases,sortingquestionsandevaluationtherearenodelaysandtheoperationis
performedinlessthan2secondsforopening,sorting,computing,posting>95%ofthefiles.Also
whenconnectingtotheserverthedelayisbasedonthedistanceofthe2systemsandthe
configurationbetweenthemsothereisaprobabilitythattherewillbeanunsuccessfulconnectionin
lessthan20seconds.

Reducingthetimeneededtoopenthesystem.

10
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

Reducingthetimeittakestoconvergeontherightworkflowswhichhavethehighestimpact
onoutcomes.

Appendix

11
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

DFD

12
<Project Name> Version: <1.0>
Software Requirement Specification (SRS) Date: <dd/mm/yyyy>
<person in charge>

13