CS 255 Business Requirements Document Template

.docx

School

Southern New Hampshire University *

*We aren’t endorsed by this school

Course

CS-255

Subject

Computer Science

Date

Dec 6, 2023

Type

docx

Pages

3

Uploaded by CaptainGoldfish3589

Report
CS 255 Business Requirements Document Template Complete this template by replacing the bracketed text with the relevant information. This template lays out all the different sections that you need to complete for Project One. Each section has guiding questions to prompt your thinking. These questions are meant to guide your initial responses to each area. You are encouraged to go beyond these questions using what you have learned in your readings. You will need to continually reference the interview transcript as you work to make sure that you are addressing your client’s needs. There is no required length for the final document. Instead, the goal is to complete each section based on your client’s needs. Tip: You should respond in a bulleted list for each section. This will make your thoughts easier to reference when you move into the design phase for Project Two. One starter bullet has been provided for you in each section, but you will need to add more. System Components and Design Purpose What is the purpose of this project? Who is the client and what do they want their system to be able to do? [Insert text] System Background What does DriverPass want the system to do? What is the problem they want to fix? What are the different components needed for this system? [Insert text] Objectives and Goals What should this system be able to do when it is completed? What measurable tasks need to be included in the system design to achieve this? [Insert text] Requirements Nonfunctional Requirements In this section, you will detail the different nonfunctional requirements for the DriverPass system. You will need to think about the different things that the system needs to function properly. Performance Requirements What environments (web-based, application, etc.) does this system need to run in? How fast should the system run? How often should the system be updated? [Insert text] 1
Platform Constraints What platforms (Windows, Unix, etc.) should the system run on? Does the back end require any tools, such as a database, to support this application? There aren't really many platform constraints from Windows, Mac OS, Linux, Unix, or any of the other major operating systems. Accuracy and Precision How will you distinguish between different users? Is the input case-sensitive? When should the system inform the admin of a problem? Inputs like username and password must be case sensitive to ensure privacy. However, other things like imports of names. ID's and any other form of identification may not have to be case sensitive depending on the laws in that state. Adaptability Can you make changes to the user (add/remove/modify) without changing code? How will the system adapt to platform updates? What type of access does the IT admin need? Due to the fact that I'll be using a modular method, it will be very easy to change text and other characteristics about the user interface, making it a lot more adaptable. In addition to this, having one or two admins checking the website will make sure that it is easy to update information within a day or two that the information is changed. Security What is required for the user to log in? How can you secure the connection or the data exchange between the client and the server? What should happen to the account if there is a “brute force” hacking attempt? What happens if the user forgets their password? Security is very important here as there are some information that you definitely don't want other people knowing when going to driving school. Therefore, security would be a big part, so things like single sign on will definitely help. Functional Requirements Using the information from the scenario, think about the different functions the system needs to provide. Each of your bullets should start with “The system shall . . .” For example, one functional requirement might be, “The system shall validate user credentials when logging in.” First of all, you should be able to see what progress you've made on driving. That is one of the functional requirements as it is one of the main things that the driverpass CEO has asked us to put in the interface. Second, the volume should be able to see all current information that they have measured stirred into their database and you should be able to change it. This is inside the website in case any of the information is wrong or changes. User Interface 2
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help