Requirements for Module RM13 Development

Requirements for Module RM13 Development
Slide Note
Embed
Share

This course material was created with an NSF TUES award, focusing on both stated and implied requirements for Instructor Slides Exercise within Module RM13. Through this content, learners can gain insights into identifying and addressing these requirements effectively.

  • Requirements
  • Module RM13
  • Instructor Slides
  • NSF TUES award

Uploaded on Mar 01, 2025 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. Stated and Implied Requirements Stated and Implied Requirements Instructor Slides Exercise Module Number: RM13 This course material was developed with NSF TUES award # 1245036

  2. Read the given stated need and suggest implied need(s).

  3. The software system shall require a user id and password for access. What do the students say?

  4. The software system shall require a user id and password for access. Implied needs? Verify User ID Verify Password Permit up to X tries for access Lock the account Allow User to reset the password Etc.

  5. The software shall be able to create five types of reports. What do the students say?

  6. The software shall be able to create five types of reports. Implied needs? List standard reports Create customizable reports Allow editing of reports Allow printing of reports Etc.

  7. The software shall be able to create and save a document. What do the students say?

  8. The software shall be able to create and save a document. Implied needs? Edit document Use save as feature Select a directory Etc.

  9. The software shall permit the use of Credit Card for merchandise purchase. What do the students say?

  10. The software shall permit the use of Credit Card for merchandise purchase. Implied needs? Allow entry of various types of credit cards Allow entry of card number, card older name, expiry date, security code Allow the user to keep the card on profile if requested Etc.

  11. The pop up window shall have a cancel button. What do the students say?

  12. The pop up window shall have a cancel button.. Implied needs? Allow the user to select a cancel button to cancel operation Allow the user to confirm cancellation Etc.

  13. Facilitated application specification technique Meeting between customers and developers at a neutral site (no home advantage). Goals identify the problem propose elements of solution negotiate different approaches specify preliminary set of requirements 13

  14. Rules for participation and preparation established ahead of time. Agenda suggested brainstorming encouraged Facilitator appointed. Definition mechanism sheets, flipcharts, wallboards, stickers, etc. 14

  15. Quality Function Deployment Customer s needs imply technical requirements: Normal requirements (minimal functional & performance). Expected requirements (important implicit requirements, i.e. ease of use). Exciting requirements (may become normal requirements in the future, highly prized & valued). 15

  16. Function Deployment: Determines value of required function. Information Deployment: Focuses on data objects and events produced or consumed by the system. Task Deployment: product behavior and implied operating environment. 16

  17. Value Analysis makes use of: Customer interviews. Observations. Surveys. Historical data. to create Customer Voice Table extract expected requirements derive exciting req. 17

Related


More Related Content