Содержание
- 2. Levels and types of requirements Business Requirements User Requirements Functional Requirements
- 3. Characteristics of Good Requirements Examples of good and bad Requirements Requirements analysis AGENDA
- 4. HOW DO I KNOW WHETHER THE REQUIREMENT IS QUALITATIVE?
- 5. Necessary Complete Consistent Unambiguous Verifiable Traceable Characteristics of Good Requirements
- 6. Characteristics of Good Requirements Clear Correct Feasible Independent Atomic
- 7. A Necessary requirement Is one that can be traced back to the business problem or business
- 8. Necessary UNNECESSARY REQUIREMENT GOOD REQIURMENT REQ1: All requirements specified in the Vision document should be implemented
- 9. A Complete requirement Contains all the information that is needed to define the system function Leaves
- 10. UNCOMPLETE REQUIREMENT GOOD REQIURMENT REQ2: On loss of power, the battery backup must support normal operations.
- 11. A Consistent requirement Does not conflict with other requirements in the requirement specification Uses the same
- 12. REQUIREMENTS CONFLICT GOOD REQIURMENTS REQ3: Date should be displayed in the mm/dd/yyyy format. REQ32: Date should
- 13. An Unambiguous requirement Must be easily read and understood by non technical people, Must be interpreted
- 14. UNAMBIGUOUS REQUIRMENTS GOOD REQIURMENTS REQ5. All screens should appear on monitor quickly How quickly? REQ5. When
- 15. A Verifiable requirement Is stated in such a way that it can be tested by inspection,
- 16. UNVERIFIABLE REQUIRMENTS GOOD REQIURMENTS REQ7: The system must be user friendly. How should we measure user
- 17. A Traceable requirement is linked to its source: a higher-level system requirement, a use case, or
- 18. Traceable UNTRACEABLE REQUIREMENT GOOD REQIUREMENT REQ10: Page list should contain 3 products per line regularly according
- 19. Requirements analysis is a systematic project activity targeted at: determining whether the stated requirements possess qualities
- 20. Requirement Analysis in SCRUM
- 21. Requirement Analysis REVIEW OF REQUIREMENTS Test Requirements to be sure that they are qualitative. If no,
- 22. Requirement Analysis: OMS APPLICATION
- 23. To: po@training.local Product owner Subject: Clarification. OMS:LvQCQC-25. As a Supervisor I want to create a report
- 24. Requirement Analysis: OMS APPLICATION
- 26. Скачать презентацию