Functional and Non-Functional Requirements in Software
Functional and Non-Functional Requirements in Software
in Software
Engineering
Systems utility
It is determined by both its functional
(physical requirements) and
non-functional
characteristics
(usability, flexibility, performance,
interoperability and security).
Non-functional requirements
a) Describe the non-behavioral aspects of a
system, capturing the properties and
constraints under which a system must operate.
More definitions.
Quality: Noun -- S: (n) quality (an essential and
distinguishing attribute of something or someone)
Functional: Adjective -- S: (adj) functional (designed
for or capable of a particular function or use)
Non-functional: Adjective -- S: (adj) non-functional
(not having or performing a function); S: (adj)
malfunctioning, non-functional (not performing or
able to perform its regular function)
Functionality: Noun -- S: (n) functionality (capable of
serving a purpose well)
ISO/IEC 9126
It distinguishes 4 types of quality
levels:
quality in use
external quality
internal quality
process quality.
FURPS
A model for classifying software
quality attributes or non-functional
requirements.
Developed at Hewlett-Packard