BA Prince the B.A. Subscribe

Home / Business Analysis Explained

Functional Requirements and Non Functional Requirements: 4 Tests to Tell Them Apart

Functional Requirements and Non Functional Requirements: 4 Tests to Tell Them Apart

Watch on YouTube Subscribe

Functional requirements and non functional requirements get mixed up all the time. In this video I take one messy list from a made-up online shop and sort it: 4 quick tests to tell them apart, the grey zone, 6 quality attributes you will meet all the time, how to turn "search must be fast" into a testable requirement with 4 parts, a worked example with requirement IDs, and the 5 mistakes to avoid.

Step by step

What it does vs how well it does it

  1. A functional requirement says what the system does. A non-functional requirement says how well it does it, or under what conditions. The online shop's sales manager sends a mixed list for product search: search by name, show prices, search must be fast, must work on phones.

Test 1: the verb test

  1. Verb test: is the line an action or a quality? Shoppers can search by product name is an action you can watch happen, so it is functional. Search must be fast describes a quality. A line full of adjectives like fast, safe, easy or reliable is probably non-functional.

Test 2: take it away

  1. Take-it-away test: delete the line. If a feature disappears, it was functional: remove shoppers can filter by size and the size filter is gone. If the feature stays but gets worse, it was non-functional: remove search must be fast and search still works, just slowly.

Test 3: one feature or many

  1. One-or-many test: a functional requirement usually belongs to one feature, like sorting results by price. A non-functional one often spans many: every page loads in under 2 seconds covers search, cart, checkout and accounts. Keep these in their own list and link the stories.

Test 4: the tester test

  1. Tester test: how would a tester check it? For functional, they act and check the result: search for red shoes, and red shoes come back. For non-functional, they measure, with a stopwatch, load test or survey. If it can't be checked at all, the requirement isn't finished.

The grey zone: security

  1. Security lines can feel like both. Write the behaviour as functional: the system asks the shopper to log in before showing order history. Write the level as non-functional: passwords are stored hashed and an account locks after 5 failed tries. Both matter more than the label.

Explain like I'm 5: buying a car

  1. Think of buying a car. Driving, braking, turning and playing the radio are functions every car has. You choose between cars on qualities: speed, crash safety, fuel use, comfort. Software is the same: qualities are often why people pick it, or leave it.

What the BABOK Guide says

  1. The BABOK Guide groups both as solution requirements. Functional ones describe capabilities: the behaviour and information the solution manages. Non-functional ones describe its qualities or the conditions it must work under, also called quality attributes.

Qualities 1-3: performance, availability, security

  1. Performance efficiency: how fast, with what resources, e.g. search results appear within 2 seconds. Availability: when it must be up, e.g. checkout up at least 99.9% of the time. Security: who can see and change what, e.g. the shop never stores full card numbers.

Qualities 4-6: usability, scalability, compatibility

  1. Usability: 9 out of 10 first-time shoppers find a product without help. Scalability: search handles 10 times normal traffic on Black Friday. Compatibility: works on the latest 2 versions of the main phone and desktop browsers. Pick the categories the business cares about.

Make it testable: 4 parts

  1. Make fast testable with 4 parts: the quality (performance), the measure (seconds from pressing search to seeing results, for 95% of searches), the target (2 seconds or less) and the conditions (500 shoppers online at once). Together, a tester can pass or fail it.

Where the numbers come from

  1. Get numbers from the business. Shoppers give up when search takes over about 3 seconds, and today it takes 4. Ask what each target costs: going from 99.9% to 99.99% uptime can cost a lot. Never write as fast as possible or user friendly; no tester can fail them.

Worked example: the sorted list

  1. FR1: shoppers search products by name or keyword. FR2: each result shows name, picture and price. FR3: shoppers filter by size and colour. NFR1, performance: with 500 shoppers online, 95% of searches show results within 2 seconds. NFR2 covers browsers, NFR3 usability.

Test it and play it back

  1. Write acceptance criteria. FR1: given a shopper on the search page, when they search for red shoes, then red shoes appear. For NFR1 the target is the criteria, checked by a load test. On playback, the sales manager asks about phones, so NFR1 now covers phones and desktops.

Where they go

  1. Functional requirements usually become Jira user stories or rows in a requirements table in Airtable or Confluence. Put non-functional ones on one quality page, add those that apply to every story to the definition of done, and give each an ID so a story can say: must meet NFR1.

5 common mistakes

  1. 5 common mistakes: never asking about non-functional requirements; vague words like fast or secure with no number; a number with no conditions (how many shoppers, which device?); targets nobody needs, like perfect uptime; and hiding one inside a single story.

Recap

  1. Functional says what the system does; non-functional says how well, and under what conditions. Use the verb, take-it-away, one-or-many and tester tests to sort them, and give every non-functional requirement a quality, measure, target and conditions.

Common mistakes

  • Vague words with no number. "Search must be fast" can never fail a test. Give it a measure and a target, like 95% of searches within 2 seconds.
  • A number with no conditions. 2 seconds for 1 shopper is very different from 2 seconds with 500 online. Say the load and the device, like phones and desktops.
  • Hiding a non-functional requirement inside one story. Rules like page load time apply to many stories. Keep them on a separate quality page with IDs, and link the stories to them.
  • Targets nobody needs. Asking for 99.99% uptime instead of 99.9% can cost a lot. Check today's numbers and what the business really needs before setting a target.

When a business analyst uses this

In a requirements workshop, a BA sorts the stakeholder's wish list into functional and non-functional lines, then rewrites each quality with a measure, target and conditions. The non-functional ones go on a quality page with IDs like NFR1, so stories can link to them before sign-off.

Questions people ask

What is the difference between functional and non-functional requirements?

Functional requirements say what the system does, like letting shoppers filter by size. Non-functional requirements say how well it does it, like how fast, how secure or how easy to use.

What are examples of functional and non-functional requirements?

Functional: shoppers can search products by name or keyword. Non-functional: with 500 shoppers online, 95% of searches show results within 2 seconds.

What are functional and non-functional requirements in software engineering?

They are the 2 main kinds of solution requirements. Functional ones describe the system's behaviour, and non-functional ones, also called quality attributes, describe qualities such as performance, availability and security.

More in Business Analysis Explained