Your SlideShare is downloading. ×
  • Like
Protectourwater.ie SRS
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply
Published

 

Published in Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
799
On SlideShare
0
From Embeds
0
Number of Embeds
4

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. CS4566 - ASSIGNMENT NUMBER 2Protectourwater.ie SRSFormat Used: IEEE STD 830Computer Systems: Kenny Barry – 09006369 | Jonathan Curran 0848255Digital Media Design: Killian Stone - 09005157 | Killian Vigna - 10129758Date: 26thApril 2013
  • 2. iiTable of ContentsSection One: Introduction.......................................................................................................................1I. Purpose .......................................................................................................................................1II. Scope...........................................................................................................................................1III. Definitions, Acronyms and Abbreviations...............................................................................1IV. Overview of Document...........................................................................................................1Section Two: Overall Description............................................................................................................2I. Context........................................................................................................................................2II. Product Perspective....................................................................................................................2III. Product Functions...................................................................................................................2IV. Characteristics of the Users ....................................................................................................3V. Constraints..................................................................................................................................3VI. Assumptions and Dependencies.............................................................................................3Section Three: Specific Requirements ....................................................................................................31. External Interface........................................................................................................................32. Functional Requirements............................................................................................................43. Performance Requirements........................................................................................................54. Logical Database Requirements..................................................................................................65. Design Constraints ......................................................................................................................7
  • 3. 1Section One: IntroductionI. PurposeThe purpose of this document is to provide the system developers with the necessary detailsfor the successful completion of the product. These details include the requirements for theintended audiences listed below:Household & companies whose building is connected to a septic tank systemThe State, as it will be a means of generating revenueLocal Authorities, who will carry out the tank inspections.Environmental Protection Agency (EPA)Also included, are descriptions of suggested functionality the system should cater to.II. ScopeThis document does not cover hardware suggestions; platform suggestions; and non-functional requirements, save for, performance and security.This document does cover the functional requirements of the system through user stories;input and output requirements for product functions; and the design constraints of thesystem.III. Definitions, Acronyms and AbbreviationsEPA – Environmental Protection AgencyCoR – Certificate of RegistrationMPRN – Meter Point Reference NumberIV. Overview of DocumentThis document is organized in the following manner:ContextProduct PerspectiveProduct FunctionsCharacteristics of the UsersConstraintsAssumptions and DependenciesThe context requires homeowners and companies with a septic tank to obtain a Certificateof Registration through local authorities in order to allow for the inspection and complianceof proper standards along with raising state revenue.The product perspective if based on the efficiency of a third party service which allows forpayment of the CoR and its ability to obtain and store records of registration.The product functions provide a chart showing and individual’s status (from property ownerto a local authority inspector), what they want to do (from creating an online account, to
  • 4. 2acquiring a list local properties with septic tanks) so that they can (register their properties’septic tank, or perform a thorough inspection).Characteristics of Users define the different roles between users, for a homeowner toreceive a CoR, they must have basic computing knowledge, the local authorities must find asystem to allow for more efficient inspections and the EPA must inform the public why it isnecessary to purchase a CoR.The Constraints revolve around the limitations of the system, how technical is it to registerfor a CoR depending on the users computing knowledge, how do the local authorities storeCertifications of Registration, and how accessible are these records to the EPA.Assumptions and Dependencies are the list of factors this report depends on.Section Two: Overall DescriptionI. ContextFigure 1:Context diagramII. Product Perspective(Assumption) Dependent on the possible third-party payment system. Unable tocomplete registrations without this system.(Assumption) Dependent on a system that has prior knowledge of known properties withseptic tank installations (paper-trail).III. Product FunctionsThe following functions have been identified as core functions to the product.ID As a... I want to... So that...1 Property Owner Create an accountI can register myproperties’ septic tank
  • 5. 32 Property Owner Log in to my accountI can add new, and managecurrent septic tanks3 System Admin Log into an admin accountI can manage propertyowner account accounts4 Property OwnerBe able to recover myaccount detailsI can log into my account5 Property Ownerget information on septictank legislationI am better informed onthe subject6 EPA/ Local AuthorityProvide the necessaryinformation and forms tothe publicTheir properties’ septictanks are properlyregistered7 Local Authority InspectorAcquire a list of localproperties/septic tanksI can perform a thoroughinspectionTable 1: Table of account function to be in the productIV. Characteristics of the UsersProperty Owners: own a septic tank and requiring a CoR. Age and computer knowledgeof varying standard.Local Authority Inspectors: require a product or system to allow more thorough andefficient inspections.EPA:wish to impart knowledge to the public about septic tank legislation and whyregistration is needed.V. ConstraintsUser-friendly UI, due to the varying computer skills of users.Platform must be cost effective while being widely available to property owners.Storage used for data must be secure and must be adequate in size for the currentnumber of systems as well as future growth.Uptime of system must be, or as close to as possible, 24/7.VI. Assumptions and DependenciesProgrammers Skill Level – Does he/she have the skill to create what’s needed?Computer literacy of Users – Will ALL users be able to understand the system?Simple change-over – Will the new system be able to take information from the oldsystem? (registered septic tanks and owners, etc)Internet users – Will all septic tank owners have access to internet in order to registerwith the new system?Section Three: Specific Requirements1. External InterfaceThe system will be required to link to certain external interfaces in order to gather requiredinformation. External interfaces such as a list of all local residents who own a septic tank,registered or unregistered, or local authority inspectors databases which would show whoseseptic tanks have been inspected and which ones are left to be inspected.
  • 6. 4Overall, the new system would need access to names, addresses, email addresses of septic tankowners and the registration status of the septic tank in question.2. Functional RequirementsThe functional requirements are based on Table 1, shown above and detailed as follows:Product Function 1:Account CreationUser must choose which type of property they to wish to register a septic tank for -Private or Corporate.User must enter their email address. Confirmation of this email will be done by theuser re-entering their email.User must enter a password for their account. Confirmation will be done in the sameway as above.The system will require the user to enter valid personal details, such as: Forename,Surname, Contact Number etc. They will also be required to pick and answer asecurity question.User will then be required to input an address for correspondence (This does notneed to be the property of the septic tank).Confirmation of inputs should then be preformedA unique account verification code should be generated and sent to the suppliedemail address.Account is successfully createdProduct Function 2: Log inThe user should use the previously given verification code and decided password tolog in.Product Function 3: Admin Log inSame as Product Function 2, above, except user is a System Admin.Product Function 4: Account RecoveryInput Reqs. (a) Email, PasswordInputReqs.Email address, password, full name, contact details, securityquestion answer, MPRN (Optional)OutputReqs.Account verification codeInput Reqs. Account verification code, passwordOutput Reqs. N/AInput Reqs. Admin-account verification code, passwordOutput Reqs. N/A
  • 7. 5(b) Account Reference code, EmailOutput Reqs.(a) Account reference code(b) New passwordUser will provide necessary inputs for desired detail recoverySystem should supply log in details via email.Product Function 5: Attaining Legislative InformationUsers will search the system for relevant information.System should provide detailed information to the user.Product Function 6: Obtaining Registration FormsEPA and Local Authority users provide the system with legislative information andregistration forms, respectively.The system should display this information and forms for public consumption.Product Function 7: Inspection List GenerationLocal Authority user should be able tolog in and specify desired area for inspection.System should provide list of properties in specified area for inspection.3. Performance RequirementsAccount CreationOnce confirmation of inputs has been performed by the user a unique account verificationcode should be sent by email to the user within 8.5 seconds. This is the optimum time toallow the user confirm their details, change from the registration page to their email, andopen up their account verification code without the need to wait and become distracted.Log in (or Admin)Input Reqs. Search keywordsOutput Reqs. Relevant informationInput Reqs. Legislative information, registration formsOutput Reqs. N/AInput Reqs. Local Authority account-verification code, Area(City/County)Output Reqs. List of properties with septic tanks in specified areaInputReqs.Email address, password, full name, contact details, securityquestion answer, MPRN (Optional)OutputReqs.Account verification code
  • 8. 6The time taken once account verification code and password have been entered should beno more than 2 seconds to access the user’s personal account.Account RecoveryInput Reqs.(c) Email, Password(d) Account Reference code, EmailOutput Reqs.(c) Account reference code(d) New passwordLike setting up a new account, to receive a new password an email should be sent to therecipient within 8.5 seconds of order.Attaining Legislative Information95% of relevant information should be sent to the user within 2 seconds of entering searchkeywords.Obtaining Registration FormsOnce EPA and local authority users have input legislative information and registration forms,the aforementioned information should become available to the public within 15 minutes ofuploading.Inspection List GenerationA 95%list of properties with septic tanks in a town or city area should become available tolocal authority users within 5 seconds of entering their local authority account verificationcode and the area desired and up to 8.5 seconds for a full County.4. Logical Database RequirementsHere are the logical database requirements to be placed into the database;a) Types of information used by various functions;b) Frequency of use;c) Accessing capabilities;Input Reqs. (Admin) Account verification code, passwordOutput Reqs. N/AInput Reqs. Search keywordsOutput Reqs. Relevant informationInput Reqs. Legislative information, registration formsOutput Reqs. N/AInput Reqs. Local Authority account-verification code, Area(City/County)Output Reqs. List of properties with septic tanks in specified area
  • 9. 7d) Data entities and their relationships;e) Integrity constraints;f) Data retention requirements.5. Design Constraintsa) Standards compliance – the system must comply with standards in the industry.b) Database integrity – how well the system will work.c) Limits on amount of memory available – limited space for information storage.d) Design of system – must be simple enough to be used by a varying array of users.*** End of the SRS ***