From the course: Applying Agile MoSCoW Prioritization

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Functional and nonfunctional requirements

Functional and nonfunctional requirements

From the course: Applying Agile MoSCoW Prioritization

Start my 1-month free trial

Functional and nonfunctional requirements

- Projects have all sorts of requirements. To build them into your user stories, it's helpful to understand which are functional and which are non-functional requirements. Functional requirements describe what the requirement must do or how it must behave. Non-functional requirements describe how well they must perform when doing that. Non-functional requirements tend to describe what is known as the ilities of the project like functionality, availability, capacity, reliability, maintainability and so on. It's really important to describe these criteria with user stories as they help us to understand how we will develop the requirement and more importantly, how to test it. Let's take an example from the list of user stories and see how this might work. A user story is, as a user of a website, I want to book tickets for attractions in advance so that I don't have to queue up on the day. Describing what the requirement must do, the functional requirements, is often best phrased as a…

Contents