Non-Functional Requirements

Non-functional requirements (NFRs) define how a system should be, as opposed to what it should do; they are used to determine the quality of a technical solution. This quality evaluation allows Enterprise Architects to determine how well a technical solution aligns with both the State Information Technology Strategy and the Vermont Enterprise Architecture Framework.

The Enterprise Architecture Group at the State of Vermont is responsible for the writing, maintenance, and governance of NFRs. They also serve to assist business leads and vendors in understanding NFRs.

State business leads must consider NFRs throughout the lifecycle of a solution, from procurement and contracting, through design and implementation.

The Enterprise Architecture Group uses NFRs during Architecture Assessments. Enterprise Architects, during an Architecture Assessment, judge proposed solutions across all applicable NFR categories. Solutions are graded based on how effectively a solution addresses applicable NFRs.

You are able to download the most current draft  of the NFR list here.

The scope of the NFRs covers the following categories of interest listed below:

  • Data Center
  • Infrastructure
  • Security
  • Networking
  • Disaster Recovery
  • Capacity and Performance
  • Configuration Management
  • Release Management
  • Monitoring
  • Application and System Continuity
  • Maintenance and Operations
  • Governance
  • Service Level Agreements
  • SOA (Service Oriented Architecture)
  • Interfaces
  • Enterprise wide components
  • Usability
  • Database Management
  • Auditing
  • ETL (extract, transform and loading with respect to data)
  • Operating Constraints
  • Platform Constraints