Mastering the Requirements Process, 4th Edition
by James Robertson, Suzanne Robertson, Adrian Reed
25
Functional Requirements
Functional requirements are what the software product must do; what actions it must take to satisfy the business need. For example, it might be to calculate a premium, or plot a trajectory, or record a transaction, or check a password, or any of the almost infinite number of things that our software solutions do. It’s a functional requirement because it describes some activity, whereas a non-functional requirement (covered in the next chapter) describes the qualities or properties of that functionality.
Functional requirements come from the business activity that you discover when you are trawling or prototyping. From that activity—a mix of current and proposed future activities—you determine how much of it is to be ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access