1 / 6

User Requirements To System Requirements

User Requirements To System Requirements. Pepper modifying Sommerville's Book slides. Requirements engineering. Types User requirements

kaz
Download Presentation

User Requirements To System Requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. User Requirements To System Requirements Pepper modifying Sommerville's Book slides Chapter 4 Requirements engineering

  2. Requirements engineering • Types • User requirements • Purpose: Describe everything the user wants the system to accomplish. This can include non-functional requirements such as needing the system to respond to any command within 5 seconds • Audience: Written for customers and business managers, not prog • Language: Primarily uses the language of the business • System requirements • Purpose: How the system will implement the user's requirement, without giving detail design • Audience: Technical design team, though users must be able to understand it. - not business manager, programmer will read this • Language: Mix of business and plain English to describe any technical concepts Chapter 4 Requirements engineering

  3. Readers of different types of requirements specification Chapter 4 Requirements engineering

  4. User and system requirements Chapter 4 Requirements engineering

  5. Security Example • User Requirements: • The system will keep track of how many programs each child attempts and how successful those attempts are. • Managers can see the statistics on successful attempts for everyone, but children can only see their own statistics. • System Requirements: • The system will maintain a list of users with passwords. • The system will maintain a list of separate functions that each user is allowed to access. • An audit trail will be created to track every program run, listing the child username, date, program name, #steps attempted, number of successful steps • The statistics screen will ask which child if the user is authorized to view more than one child's stats Chapter 4 Requirements engineering

  6. An Industry Guide Onfi Systems • User requirements: http://www.ofnisystems.com/services/validation/user-requirement-specifications/ • System requirements (but they call it functional requirements - not the same use of functional we have) http://www.ofnisystems.com/services/validation/functional-requirements/ Chapter 4 Requirements engineering

More Related