Logo
NeoArc Studio

Non-Functional View Template

Documenting how non-functional requirements are achieved architecturally, not just stated

The Non-Functional View template provides a structured approach to documenting how non-functional requirements are achieved architecturally, not just stated.

Template Sections

This template includes 9 sections.

Quality Attributes Overview
Describe the key quality attributes for this system, their relative priority, and how trade-offs between them are...
Performance Requirements
Define latency, throughput, and resource utilisation targets with specific measurable values
Performance Scenario
Document a scenario showing how the architecture handles peak load: stimulus, response, and the architectural...
Availability Requirements
Define uptime targets, maximum acceptable downtime, and recovery objectives
Availability Scenario
Document a scenario showing how the architecture recovers from a component failure: detection, failover, and recovery...
Security Requirements
Define security requirements: authentication strength, encryption standards, audit requirements, and compliance targets
Maintainability Requirements
Define maintainability targets: deployment frequency, mean time to recovery, change lead time, and test coverage
Quality Fitness Functions
Define automated checks that continuously validate quality attributes are met in production
Quality Attribute Trade-offs
Document trade-offs between competing quality attributes (e.g., security vs performance, availability vs consistency)

Section Details

Block Types Used

Content blocks used in this template
SectionBlock TypePurpose
Quality Attributes OverviewRich TextDescribe the key quality attributes for this system, their relative priority,...
Performance RequirementsNon-Functional RequirementDefine latency, throughput, and resource utilisation targets with specific...
Performance ScenarioQuality Attribute ScenarioDocument a scenario showing how the architecture handles peak load: stimulus,...
Availability RequirementsNon-Functional RequirementDefine uptime targets, maximum acceptable downtime, and recovery objectives
Availability ScenarioQuality Attribute ScenarioDocument a scenario showing how the architecture recovers from a component...
Security RequirementsNon-Functional RequirementDefine security requirements: authentication strength, encryption standards,...
Maintainability RequirementsNon-Functional RequirementDefine maintainability targets: deployment frequency, mean time to recovery,...
Quality Fitness FunctionsFitness FunctionDefine automated checks that continuously validate quality attributes are met...
Quality Attribute Trade-offsTrade-off MatrixDocument trade-offs between competing quality attributes (e.g., security vs...

Getting Started