Technology and Engineering Atlas

How Things Are Built
Sign In
Text size
100%
Theme
Method

Functional requirement

Software Engineering

A functional requirement defines a function of a system or one of its components, where a function is a summary of the behavior linking a system inputs to its outputs, covering calculations, data manipulation, technical details and the specific behavior a system must exhibit. Functional requirements are typically phrased as the system must do something, while non-functional or quality requirements, phrased as the system shall be something, describe overall characteristics such as performance, security and reliability instead of specific actions. Functional requirements are detailed in a system design and drive its application architecture, while non-functional requirements are detailed in system architecture and drive its technical architecture. Functional requirements often originate from organizational or business rules discovered through discussions with users and stakeholders, and form the basis for use cases, from which analysts derive specific requirements based on observed user needs. This description is adapted from Wikipedia contributors under CC BY-SA 4.0; changes were made. https://creativecommons.org/licenses/by-sa/4.0/

Facts
Core Principle
Define a function of a system or its component. 1
Connections

Associated With

In Field

Sources
1. Functional requirement (Wikipedia)
Lead paragraph, first sentence
Quote, Lead paragraph, first sentence
a functional requirement defines a function of a system or its component
View the Source
Comments (0)
No comments yet. Be the first to share a thought.
Reader Challenges (0)
No disputes yet. Spotted an error or a better source? Open the first one.