Содержание
- 2. Requirements sources Levels and types of requirements Functional requirements Nonfunctional requirements Explicit and Implicit requirements AGENDA
- 3. Requirements sources HOW TO GET AN EFFECTIVE SOFTWARE REQUIREMENTS?
- 4. Discovery Requirements sources Gathering Analysis Validation Documentation
- 5. Requirements sources Stakeholders Existing documents Existing systems
- 6. Requirements sources Users Customer Sponsor Market Stakeholders
- 7. Requirements sources Existing documents Interface documentation Strategy Legal restrictions Design documentation Standards Technical implementation Constraints
- 8. Requirements sources Existing systems Adjacent system Previous versions Reports Trouble tickets
- 9. Elicitation Techniques Workshops Interviews Discussions Document analysis Prototyping Interface Identification Marketing Survey and User Questionnaires Observing
- 10. Elicitation Techniques Workshops Interviews Discussions Document analysis Prototyping Interface Identification Marketing Survey and User Questionnaires Observing
- 11. Levels and Types of requirements BUSINESS REQUIREMENTS USER REQUIRMENTS FUNCTIONAL REQIURMENTS Business Level User Level Product
- 12. Levels and Types of requirements BUSINESS REQUIREMENTS USER REQUIRMENTS FUNCTIONAL REQIURMENTS Business Level User Level Product
- 13. Levels and Types of requirements BUSINESS REQUIREMENTS USER REQUIRMENTS FUNCTIONAL REQIURMENTS Business Level User Level Product
- 14. Levels and Types of requirements BUSINESS REQUIREMENTS USER REQUIRMENTS FUNCTIONAL REQIURMENTS Business Level User Level Product
- 15. Business Level User Level Product Level Levels and Types of requirements "OMS application should reduce errors
- 16. Traceability is a technique that provides a relationship between different levels of requirements in the system
- 17. Traceability plays several important roles: Verifying that an implementation fulfills all requirements. Verifying that the application
- 18. Nonfunctional Requirements Business Rules Quality Attributes External Interfaces Requirements Design and Implementation Constraints Corporate policies, Government
- 19. Explicit Explicit and Implicit Requirements Hidden or ‘assumed’ and not stated explicitly Clearly defined and documented
- 20. Explicit and Implicit Requirements Password encryption Auto complete Short keys Default behavior of UI controls
- 21. Requirements types. Example Requirement Types. Example User Requirements Business Requirements Functional Requirements Nonfunctional Requirements
- 22. REQUIRMENT TYPES. EXAMPLE User Requirements Business Requirements Functional Requirements Nonfunctional Requirements tOn he 'Login' page, pressing
- 24. Скачать презентацию