CS 255 Business Requirements Document - Chatman

docx

School

Southern New Hampshire University *

*We aren’t endorsed by this school

Course

255

Subject

Computer Science

Date

Feb 20, 2024

Type

docx

Pages

4

Uploaded by MinisterMonkeyPerson767

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? The client is DriverPass The client wants to provide students with access to online practice exams and on-the-road training to prepare them for their driving test. 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? DriverPass wants to be able to provide student drivers with online practice exams and on-the- road training to prepare them for their driving test. DriverPass wants system data to be accessible for offline use. The system must have multiple roles with different levels of system access. The system should keep an activity log of all changes made to reservations that is downloadable Customers should be able to schedule online or via call in. Driver packages that are customizable and or be able to be deactivated Reservations should include registration intake information System should be web-based and data back and security be maintained by third party contractor System should connect to local DMV websites for most up-to-date practice exams as well as rules and policy updates. 1
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? Provide customers with on-the-road trainings Allow system access for certain roles online and offline Download activity reports Be able to match a student driver to the scheduled Driver Trainer Online and over the phone reservation functionality 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? The system application that connects to an online server but still have access to documents off- line if downloaded The application should be simple to navigate and just be able to display the different pages and videos, it needs to be fast page to page The system should be updated when the DMV has a change in policy and practices 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? Windows and MacOs are the most popular operating systems Back end databases is required to store user records 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? There will be different users with login requirements username and password System will need to make sure their no duplicate login names already listed IT officer Customers Secretary Owner Input should be case sensitive Admin needs to be to keep track of reservations, who makes it, who cancels it, who modify it lasts If there are passwords resets needed, a need for users to update their information 2
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? System should allow admins to add/remove employee users without changing code System should allow admins to reset employee users password IT admin should be able to download activity report, add/remove employee users and reset employee passwords 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? Different access for different employees Passwords and usernames for everybody Ability to access accounts and block/restrict others 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.” The system should validate user credentials when logging in The system should allow to change personal information like addresses and appointments if need be The system should provide information for the practice exams The System needs to be kept up to date with what the DMV requires User Interface What are the needs of the interface? Who are the different users for this interface? What will each user need to be able to do through the interface? How will the user interact with the interface (mobile, browser, etc.)? Liam, Owner, will be a system admin and will need to be able to download system data online and offline and be able to disable DriverPass packages Ian, IT Officer, will be a system admin will be able to main the system, modify employee access, download system activity report and reset those with employee access passwords Secretary will have employee access to schedule or cancel sessions for customers, select a DriverPass packager, update personal information and see what Driver Trainer is paired to a customer Customers will have user access to schedule or cancel sessions, select a DriverPass packager, update personal information and access exams 3
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
Assumptions What things were not specifically addressed in your design above? What assumptions are you making in your design about the users or the technology they have? Allow multiple languages Colorblindness option Visual appealing and easy to navigate Limitations Any system you build will naturally have limitations. What limitations do you see in your system design? What limitations do you have as far as resources, time, budget, or technology? Adding or removing modules for a future release will require a system analyst be apart of DriverPass team Budget will only allow resources to come from what the development team already has Timeline is 22-Jan to 10-May, so it will take roughly 4.5 months to complete Gantt Chart Please include a screenshot of the GANTT chart that you created with Lucidchart. Be sure to check that it meets the plan described by the characters in the interview. 4