This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
Non-functional requirement
Non-functional requirement

Version management

Difference between version and

At line 1 added 79 lines
!!! Overview
[{$pagename}] ([NFR]) within design is a [requirement] of a system of __how it should perform__
[{$pagename}]s define such as runtime qualities such as scalability, and [reliability].
[{$pagename}]s often address the [User Experience]
[{$pagename}]s also define qualities including
* maintainability by the [Operations Team]
* [Testing]
* extensibility
* deployability
!! [Agile] and [{$pagename}]
[{$pagename}]s are effectivly [Backlog] [Constraints]
[{$pagename}] are persistent qualities and [constraints] that, unlike [Functional Requirements], are typically revisited as part of the [Definition of Done] (DoD) for each [Iteration], Program Increment (PI), or release. [NFRs] influence all [backlogs]
[{$pagename}]s are __NOT__ themselves [backlog] items. They are [constraints] on development that limit some degree of design freedom for those building the [system]. These [constraints] are often defined in the acceptance criteria ([Definition of Done]) for multiple [backlog] items.
[{$pagename}]s are often driven by [Compliance] to ensure the [Product] meets the [Regulatory compliance] or [Standard compliance]
The following criteria help define NFRs:
* Bounded – When they lack [Bounded Context], NFRs may be irrelevant and lead to significant additional work.
** For example, an airplane’s flight controls should be more rigid reliability than the infotainment system.
* Independent – NFRs should be independent of each other so that they can be evaluated and tested without consideration of or impact from other system qualities.
* Negotiable – Understanding NFR business drivers and bounded context mandates negotiability.
* Testable – NFRs must be stated with objective, measurable, and testable criteria.
© Scaled Agile, Inc.
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [Nonfunctional Requirements|https://www.scaledagile.com/training/calendar/|https://www.scaledagileframework.com/nonfunctional-requirements/|target='_blank'] - based on information obtained 2019-03-21
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop