Functional and Non- Functional requirement.
Basically, functional requirements describe the features, functioning, and
usage of a product/system/software from the perspective of the product and
its user.
Although referred to as "requirements," they really are a form of design, albeit
high-level.
Functional requirements also often are called "functional specifications," and
"specification" is a synonym for design.
Non-functional requirements are not non-functional at all.
Rather, they describe various quality factors, or attributes, which affect the
functionality's effectiveness.
They do not exist in the abstract but only with respect to relevant functionality.
They are often called "ilities," because many end in "ility," such as, usability,
reliability, and maintainability
usage of a product/system/software from the perspective of the product and
its user.
Although referred to as "requirements," they really are a form of design, albeit
high-level.
Functional requirements also often are called "functional specifications," and
"specification" is a synonym for design.
Non-functional requirements are not non-functional at all.
Rather, they describe various quality factors, or attributes, which affect the
functionality's effectiveness.
They do not exist in the abstract but only with respect to relevant functionality.
They are often called "ilities," because many end in "ility," such as, usability,
reliability, and maintainability
Comments
Post a Comment