Gathering the Right Requirements
•Download as PPTX, PDF•
1 like•997 views
A deep insight into the much neglected non-functional requirements. A categorising effort of requirements order to assist practitioners in their day to day requirements elicitation process.
Recommended
More Related Content
What's hot
Similar to Gathering the Right Requirements
Similar to Gathering the Right Requirements (20)
Recently uploaded
Recently uploaded (20)
Gathering the Right Requirements
- 1. GATHERING THE RIGHT REQUIREMENTS Tips for uncovering the ‘real’ requirements Amin Kazemi http://www.linkedin.com/in/aminkazemi
- 2. Presentation Content The content of this presentation is based on the published book, ‘Mastering the Requirements Process – Getting Requirements Right’ by Suzanne Robertson and James Robertson (Addison-Wesley, 2012) All Information presented today is readily available on the public domain.
- 3. Overview Software can solve almost any problem. The problem is that we don't always understand what the problem is. Understanding the problem - the real problem - is the role of the requirements process.
- 4. Functional Requirements Functional requirements are the fundamental or essential subject matter of the product They describe what the product has to do or what processing actions it is to take.
- 6. Non-Functional Requirements Non-functional requirements are the properties that the functions must have, such as performance and usability They describe how well your product does the things it does
- 7. Link between functional and non-functional
- 8. Look and Feel Requirements The product shall comply with corporate branding standards
- 9. Usability Requirements The product shall be useable by users with limited experience of using computers
- 10. Performance Requirements The product shall support 2,000 concurrent users
- 11. Operational Requirements The product shall be used by Field Staff at night and during rain, heat, and ‘Melbourne’ conditions
- 12. Maintainability Requirements The product shall be readily portable to smartphone handhelds as applications and web-based systems.
- 13. Security Requirements The product shall ensure that only authorised users have access to the OMS system.
- 14. Cultural Requirements The product shall not display religious symbols or words associated with mainstream religions. The product shall use Australian English spelling, not American.
- 15. Legal Requirements The product shall comply with the Australian Privacy Act as amended. The product shall comply with W3C recommendations
- 16. Finding the non-functional’s Like all requirements, the non-functional ones can come to light at any time, Nevertheless, there are certain places where we can look that give us better opportunities to discover them,