IT:AD:Non-Functional Requirements

• (UP)

  • IT:AD:Non-Functional Requirements:Compliance
  • IT:AD:Non-Functional Requirements:Full List
    • IT:AD:Non-Functional Requirements:Full List:Import
    • IT:AD:non-functional_requirements:Full List:Safe Copy
    • IT:AD:non-functional_requirements:full_list:Editable
    • IT:AD:non-functional_requirements:full_list:Searchable
    • IT:AD:non-functional_requirements:full_list:Test
  • IT:AD:Non-Functional Requirements:Localisation
  • IT:AD:Non-Functional Requirements:System Requirements
  • IT:AD:Non-Functional Requirements:UX
    • IT:AD:Non-Functional Requirements:UX:Web
    • IT:AD:Non-Functional Requirements:UX:Web Server
  • IT:AD:Non-Functional Requirements:APIs
  • IT:AD:Non-Functional Requirements:Data Migration
  • IT:AD:Non-Functional Requirements:Data Storage
  • IT:AD:Non-Functional Requirements:Documentation
  • IT:AD:Non-Functional Requirements:Maintainability
  • IT:AD:Non-Functional Requirements:Monitoring
  • IT:AD:Non-Functional Requirements:Qualities
  • IT:AD:Non-Functional Requirements:Security
  • IT:AD:Non-Functional Requirements:Technical Requirements
• See also:
  • IT:AD:Definition
  • IT:AD:Requirements
  • IT:AD:Functional Requirements
  • IT:AD:Supplemental Specifications
  • IT:AD:Functional Requirements
  • IT:AD:System Functional Requirements
  • IT:AD:Non-Functional Requirements:Qualities
  • IT:AD:System Constraints
  • NFRD
  • IT:AD:Checklists/Development ← these Specifications inform the development process.
  • Best Practices
  • IT:AD:ISO 9126
  • IT:AD:ISO 25010
  • IT:AD:Requirements:Diagrams
  • General:Business:Concepts:Quality
  • General:Business:Concepts:Requirement

There is quite a lot of confusion in the field as to what exactly constitutes IT:AD:Non-Functional Requirements.

The source of this confusion are several causes.

The first is the confusion as to what actually are IT:AD:Functional Requirements (ie: there are both Domain and System Functional Requirements).

Another point of confusion is around whether IT:AD:Non-Functional Requirements describe Qualities and Constraints, or whether Constraints should be listed separately (they are often lumped together). In the IT:AD:RUP methodology, IT:AD:Non-Functional Requirements are a part of the IT:AD:Supplemental Specifications,addressing Qualities, and Constraints are listed separately.

A third point of confusion is what actually make up IT:AD:Non-Functional Requirements. A long time ago IT:AD:FURPS defined 5 categories (4 being for NFRs). IT:AD:ISO 9126 supplanted those 5 those with 6, and IT:AD:ISO 25010 currently has 8 categories:

• (System) Functional
• Performance Efficiency
• Compatibility
• Usability
• Reliability
• Security
• Maintainability
• Portability

IT:AD:ISO 25010 is an improvement over IT:AD:FURPS – but there are still omissions and questions: * Issues

At this point in time I'm arguing that IT:AD:ISO 25010 and IT:AD:SQuaRE have not addressed or dismissed the need to define Enterprise, Infrastructure, and Architecture Constraints.