liveBook · Manning

Functional requirement

As explained in Functional Design and Architecture: Examples in Haskell

A functional requirement specifies functionality that an application must provide for users to complete tasks.

A functional requirement specifies what an application must do so users can complete their tasks. It describes required functionality rather than general qualities such as performance, security, or availability. section 1.2.1

Spacecraft control

A spacecraft application has a functional requirement to let an astronaut control the ship’s systems manually and automatically. Robustness, fault tolerance, security, and compatibility are nonfunctional requirements instead. section 1.2.1

Functional requirements guide the transition from gathered requirements into software design. They clarify the application’s intended behavior while leaving qualities such as maintainability and stability to separate requirements. section 1.2.1

How Functional Design and Architecture: Examples in Haskell covers it

How deep it goes
Defines functional requirements and contrasts them with nonfunctional requirements, without detailing implementation techniques.
Examples
Uses manual and automatic spacecraft control as the central functional example.
How it connects
Connects functional requirements with nonfunctional requirements, software design, maintainability, and user tasks.

Also explained in

Compare how 6 books explain functional requirement →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Functional Design and Architecture: Examples in Haskell. The section links point to the parts of the book it draws on.