Sample Software Requirement Specification

Software Requirements Specification for Smart Electronic License Plate System Version 1.0 approved Prepared by Hoang Le Thanh Son Class SE1201 , FPT University June 11, 2018 Copyright © 1999 by Karl E Wiegers Permission is granted to use, modify, and distribute this document Software Requirements Specification for Page ii Table of Contents Introduction Overall Description 3 External Interface Requirements 4 System Features 18 4.3 Change password 26 4.4 Driver’s car position 29 4.5 Payment Management 31 4.6 Add balance to account 34 4.7 Parking Payment (automatic) 36 4.8 Parking History 37 4.9 Traffic Control 39 4.10 Get Notifications 41 Other Nonfunctional Requirements .43 Other Requirements 44 Revision History Name Date Reason For Changes Version SonHLT June 11, 2018 Start wrting document 1.0 Software Requirements Specification for Electronic Smart License Plate System Page 1 Introduction 1.1 Purpose For drivers who need time to other things in their life than waiting for ticket and going to pay fees for their cars, the Smart License Plate is a smart device that is embedded into the plate of the cars The plate will store the exact position of the driver by GPS connection, it will be synchronized with its owner’s banking accounts, that will help drivers pay their fees automatically and they not need to go to the centers to pay anymore The device will save a huge time for drivers, and save 400$ each month for the parking area thanks to removing the ticket and keeping staff Time to handle traffic situations will be reduced 50% because government can know exactly where the car is to go in time Unlike the current traditional license plate with no utilities, our product will synchronize with drivers’ banking accounts to help them pay their fees automatically, keep their safety on the road by the GPS tracking system 1.2 Document Conventions I D Acronym Definition SRS Software Requirement Specification App Application SLPS OS Operating System GUI Graphic User Interface CMS Content Manager System DB Database Smart License Plate System (Product’s name) Software Requirements Specification for Electronic Smart License Plate System Page 1.3 Intended Audience and Reading Suggestions - 1.4 Reader : developers of the product, project managers, marketing staff, users, testers and documentation writers This SRS contains : o Overview about product o Product’s features o Product non-functional requirements o Use Cases and Use Case Diagram Product Scope - Business benefits : o Drivers requested a method that can decrease their time for buying ticket at parking area, paying the fees at many place They want a software system can be embed in their License plate to these things, and can synchronize with their banking account to pay the fees o Government need to keep tracks of cars (this is a sensitive case, but can bring many benefits), to find the exact position of a car when it is in an accident or its driver has just violated the transport law o Parking area managers want to decrease or remove money to hire staff for keeping the cars and selling tickets o Driver need to find a way that can help them renew their licenses without going to centers (of course they need to be qualified for the new license) o Businesses are finding ways to display marketing and advertising - Business Objectives : - BO – : Reduce time spent for paying, waiting for drivers : o No need to wait to buy ticket to park cars o License plate can be synchronized with driver’s accounts, help them pay their fees automatically o Software will automatically renew driver license as long as drivers pass the test before - 1.5 BO – : Reduce 400$ each month for the parking area thanks to removing the ticket and keeping staff BO – : Reduce 50% time to handle transport problems such as accidents References - SRS Template by Karl E Wiegers Permission Software Requirements by Karl E.Wiegers and Joy Beaty, Third Edition, Mircrosoft Press Software Requirements Specification for Electronic Smart License Plate System Page Overall Description 2.1 Product Perspective - - 2.2 Drivers in the city get into trouble of wasting time when buying ticket at the parking area entrance They spend an average of minutes each time they go to park their cars, for going in and out They also need to spend time on many fees related to their cars, and renewal their licenses Government need to keep track of cars running on the road in case of traffic accidents, they can handle in time and avoid traffic jams Drivers nowadays don’t want to spend too much time paying the fees for their cars the overall system, subsystem interconnections, and external interfaces can be helpful Product Functions Main functions : - FE – : Using GPS system to identify the exact position of the driver and his car - FE – : Auto-pay when crossing the electronic barrier in the parking areas - FE – : Create an emergency signal and send to the government information when the car have problems like accidents - FE – : Auto-pay the traffic fees by subtracting directly into driver’s banking accounts - FE – : Show the bill for owner after each time of transaction - FE – : Display marketing and advertising 2.3 User Classes and Characteristics System has kinds of users : drivers, parking pass staffs, local authorities , adminstrators, banks - Drivers : have full permission to manage accounts, payment, their car positions - Parking pass staffs : have permission to know cars using their services, their accounts - Local authorities : have permission to know the position of the emergengy car - Banks : Manage reference of their customers’ accounts to the product for payment - Adminstrators : have full permission to system management but no permission to business management 2.4 Operating Environment - 2.5 Device : computers, smart phones Operating system : Windows (or higher), iOS, Android Design and Implementation Constraints - LI – : Local authorities have to upgrade their infrastructure to be suitable with the product with new technologies LI – : New plate will be more vulnerable than the old one, users should be careful to protect them Software Requirements Specification for Electronic Smart License Plate System Page 2.6 User Documentation - 2.7 Product tutorials document Author’s contact : leson1998ls@gmail.com Assumptions and Dependencies - AS – : The system will provide user an appropriate graphic interface to help them the tasks more easily AS – : Other platforms – based applications will be made to connect with system, help the system to be more interactive AS – : New technologies will be integrated into parking areas External Interface Requirements 3.1 User Interfaces - Driver’s UI Software Requirements Specification for Electronic Smart License Plate System Page Figure - Driver’s Account Detail Screen Software Requirements Specification for Electronic Smart License Plate System Page Figure - Driver's Home Screen Figure - Update Driver's Information Software Requirements Specification for Electronic Smart License Plate System Page Figure - Driver Position Screen Software Requirements Specification for Electronic Smart License Plate System Page Figure - Driver Payment Screen Software Requirements Specification for Electronic Smart License Plate System Page 30 UC ID and Name: UC – 004 : Driver’s Car Position Created By: SonHLT Date Created: 13/06/2018 Actor: Drivers Trigger: Description: User checks his car’s position Preconditions: User loged in to system Postconditions: User gets hist car position Software Requirements Specification for Electronic Smart License Plate System Page 31 Normal Flow: User logs in to the application successfully User clicks on “Position” button System shows to user his car position on map and the geographical address Alternative Flows: Exceptions: Priority: Frequency of Use: Business Rules: + User has not turned on his phone’s GPS before using the feature Normal Normal + GPS must be turned on before using this feature Other Information: Assumptions: Table - Use Case UC-004 4.5 Payment Management Software Requirements Specification for Electronic Smart License Plate System Page 32 Figure 18 - Driver Payment Management Software Requirements Specification for Electronic Smart License Plate System Page 33 UC ID and Name: UC – 005 : Driver Payment Management Created By: SonHLT Date Created: 13/06/2018 Actor: Drivers Trigger: Description: User checks his payment history and detail Preconditions: User loged in to system Postconditions: User gets payment information Normal Flow: User logs in to the application successfully User clicks on “Payment Management” button System shows to user his payment history and his account balance Alternative Flows: Exceptions: Priority: Normal Frequency of Use: Normal Business Rules: Other Information: Assumptions: Table - Use Case UC-005 Software Requirements Specification for Electronic Smart License Plate System Page 34 4.6 Add balance to account Software Requirements Specification for Electronic Smart License Plate System Page 35 UC ID and Name: UC – 006 : Add Account Balance Created By: SonHLT Date Created: 13/06/2018 Actor: Drivers Trigger: Description: User add balance to his application account Preconditions: User loged in to system Postconditions: User’s balance added Normal Flow: User logs in to the application successfully User clicks on “Payment Management” button User clicks on “Add Balance” button User enters amount of balance to add User confirms transaction by his bank account’s PIN code Sytem notices that user’s balance has been added Alternative Flows: Exceptions: + User enters characters that are not numbers + User enters negative number or + User enters a number that is greater than his balance account Priority: Normal Frequency of Use: Normal Business Rules: + Amount must be a positive number + Amount must be less than or equal to the amount of the user’s bank balance Other Information: Assumptions: Table - Use Case UC-006 Software Requirements Specification for Electronic Smart License Plate System Page 36 4.7 Parking Payment (automatic) UC ID and Name: UC – 007 : Parking Payment Created By: SonHLT Date Created: 13/06/2018 Actor: Parking staffs Trigger: Car goes across the electronic barrier in the parking pass Description: Smart License automatically pays parking fee Preconditions: Postconditions: Normal Flow: Car goes across the electronic barrier in the parking pass License plate automatically requests system substract owner’s balance to pay for parking fee System adds new record to driver’s payment history System adds new record to parking staff’s payment account Alternative Flows: Exceptions: Priority: Frequency of Use: Business Rules: User’s balance is not enough to pay for parking fee Normal Normal User’s balance must be greater or equal to the parking fee Other Information: Assumptions: Table - Use Case UC-00 Software Requirements Specification for Electronic Smart License Plate System Page 37 4.8 Parking History UC ID and Name: UC – 008 : Parking History Created By: SonHLT Date Created: 13/06/2018 Software Requirements Specification for Electronic Smart License Plate System Page 38 Actor: Parking staffs Trigger: Description: Preconditions: Postconditions: Normal Flow: Car goes across the electronic barrier in the parking pass Smart License automatically pays parking fee User logs in to system User gets parking history and details User logs in to the application successfully User is redirected to payment history page System shows to user table of parking history System shows to user total parking fee User checks history and then closed Alternative Flows: + User choose “Export to excel to excel file”, system will export a excel file contains parking history to user computer Exceptions: Priority: Normal Frequency of Use: Normal Business Rules: Other Information: Assumptions: Table 10 - Use Case UC-008 Software Requirements Specification for Electronic Smart License Plate System Page 39 4.9 Traffic Control Software Requirements Specification for Electronic Smart License Plate System Page 40 UC ID and Name: UC – 009 : Traffic Control Created By: SonHLT Date Created: 13/06/2018 Actor: Local authorities Trigger: Description: Authorities control traffic through system Preconditions: User logs in to system Postconditions: Authorities gets traffic stats through system Normal Flow: User logs in to the system successfully User chooses “Traffic Control” System shows to user map of cars using system System shows to user potitental problem User checks map and then make decision to handle situation or not Alternative Flows: Exceptions: Priority: Normal Frequency of Use: Normal Business Rules: Other Information: Assumptions: Table 11 - Use Case UC-009 Software Requirements Specification for Electronic Smart License Plate System Page 41 4.10 Get Notifications Software Requirements Specification for Electronic Smart License Plate System Page 42 UC ID and Name: UC – 0010 : Get Notification Created By: SonHLT Date Created: 13/06/2018 Actor: Local authorities Trigger: Description: Authorities control traffic through system Preconditions: User logs in to system Postconditions: Authorities gets traffic stats through system Normal Flow: User logs in to the system successfully User clicks on “Notification” button System shows to user list of notifications Unchecked notifications shall be highlighted System shows to user potitental problem User checks map and then make decision to handle situation or not Alternative Flows: Exceptions: Priority: Normal Frequency of Use: Normal Business Rules: Other Information: Assumptions: Table 12 - Use case UC-0010 Software Requirements Specification for Electronic Smart License Plate System Page 43 Other Nonfunctional Requirements 5.1 Performance Requirements - 0.1 second is about the limit for having the user feel that the system is reacting instantaneously, meaning that no special feedback is necessary except to display the result - 1.0 second is about the limit for the user’s flow of thought to stay uninterrupted, even though the user will notice the delay Normally, no special feedback is necessary during delays of more than 0.1 but less than 1.0 second, but the user does lose the feeling of operating directly on the data -10 seconds is about the limit for keeping the user’s attention focused on the dialogue For longer delays, users will want to perform other tasks while waiting for the computer to finish, so they should be given feedback indicating when the computer expects to be done Feedback during the delay is especially important if the response time is likely to be highly variable, since users will then not know what to expect 5.2 Safety Requirements  The server must not return a restricted web page to any browser that it cannot authenticate  The server must not return a restricted web page to a user who is not authorized to access it  The software must not accept overlong input data  The application must not accept invalid URLs 5.3 5.4 Security Requirements  The software must remain resilient in the face of attacks  The behavior of the software must be correct and predictable  The software must be available and behave reliably even under DOS attacks  The software must ensure the integrity of the customer account information Software Quality Attributes Software Requirements Specification for Electronic Smart License Plate System Page 44 5.5 Business Rules Other Requirements Appendix A: Glossary Appendix B: Analysis Models Appendix C: To Be Determined List ... Interface Requirements 3.1 User Interfaces - Driver’s UI Software Requirements Specification for Electronic Smart License Plate System Page Figure - Driver’s Account Detail Screen Software Requirements... Figure - Driver Position Screen Software Requirements Specification for Electronic Smart License Plate System Page Figure - Driver Payment Screen Software Requirements Specification for Electronic... Add Balance For Drivers Software Requirements Specification for Electronic Smart License Plate System Page 10 Figure - Enter PIN to confirm adding Software Requirements Specification for Electronic