Functional vs nonfunctional requirements
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
separate what the system does from how well it must do it.
Planned topics
- Functional: behavior ("a customer can cancel an order before shipment").
- Nonfunctional (quality): availability, latency, durability, security, operability.
- Nonfunctional requirements drive architecture far more than functional ones.
- Each needs a measure and a condition, otherwise it is a wish.
Draft outline details
Demonstration
a two-column table for orders: "cancel before shipment" (functional) beside "order confirmation survives loss of one availability zone" (nonfunctional, measurable).
Check your understanding
Which kind of requirement usually shapes the architecture most?
Show answer
Nonfunctional.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.