This document discusses non-functional requirements and their importance. It describes a workshop held to determine the top 3 non-functional requirements for Project X. The groups presented their results and rationale. Recent projects that lacked focus on non-functionals are discussed, and standards like ISO 9126 and QUINT that provide guidance. The conclusion questions whether more focus should be placed on non-functional requirements.

1. Non-functional requirementsJune 24, 2009(Patrick Kalkman, Robert-Jan Kuijvenhoven)

2. 2AgendaIntention of the meeting

3. Introduction

4. Workshop

5. Workshop Result

6. ISO 9126 / QUINT

7. ConclusionNon-Functional Requirements24/06/2009

8. 3Intention of this meetingSharing knowledge about Non-functional requirementsDetermine if Non-functional requirements need more attentionNon-Functional Requirements24/06/2009

9. Introduction4What are Non-functional requirements“Functional requirements define WHAT a system is supposed to do”“Non-Functional requirements define HOW a system is supposed tobe”“Non-functional requirements are often called qualities of a system”Non-Functional Requirements24/06/2009

10. 5Non-Functional RequirementsIntroductionNon-functional requirements are:Often implicit!

11. Often unclear!

12. Just as important as functional requirements?

13. Or are functional Requirements “Must Haves” and Non-functional Requirements “Nice to Have”?24/06/2009

14. 6Non-Functional RequirementsNon-functional Requirements?Who knows a Non-functional requirements?24/06/2009

15. 7Non-Functional RequirementsNon-Functional Requirements?Can Non-functional requirements conflict and interact with other Non-functional requirements?Who knows examples of these conflicts?24/06/2009

16. 8Non-Functional RequirementsWorkshop Non-Functional RequirementsDetermine the 3 most important Non-functional requirements for Project X.Write result on flip-overWhich Non-functionals?Rationale? Proces?Time: 30 minutes24/06/2009