> tpl_bsa_009
Non-Functional Requirements and Quality-Attribute Scenarios
Engineering quality specification defining verifiable non-functional requirements (NFRs) using SEI quality-attribute scenarios (Stimulus, Source, Environment, Artifact, Response, Response Measure) across ISO 25010 pillars.
Verifiable NFR engineering standard defining 6-part SEI quality scenarios, ISO 25010 characteristics, performance thresholds, availability budgets, and automated test acceptance gates.
Important Tech Document Template & Operational Notice
TinyCTO.tv Tech Document Template Notice: This template is a general educational and operational starting point. It is not legal, tax, accounting, investment, procurement, regulatory, security or certification advice. Requirements vary by jurisdiction, organization, contract and risk. Review and adapt it with qualified professionals before relying on it.
Problem Solved
NFRs are routinely written as unmeasurable wishes (e.g. "the system shall be fast and scalable"), leading to architectural misalignments, SLA failures in production, and intractable disputes between engineering and business.
When to Use
- •Translating business SLAs and performance expectations into mathematically testable engineering criteria
- •Conducting Software Engineering Institute (SEI) Quality Attribute Workshops with architects
- •Establishing automated performance, load, and security test gates in continuous integration pipelines
When NOT to Use
- •For functional user story step-by-step UI acceptance flows (use TPL-BSA-002)
- •For operational cloud budget cost allocation monitoring (use TPL-FIN-004)
5 Template Sections & Structural Outline
Classification across Performance Efficiency, Compatibility, Usability, Reliability, Security, Maintainability, and Portability.
Standardized scenario structure: Stimulus Source, Stimulus, Artifact, Environment, Response, and Response Measure.
Response latency (p50/p95/p99), throughput (RPS), concurrent users, peak multipliers, and memory/CPU limits.
Uptime targets (99.99%), error budget allocations, RTO/RPO limits, and automated failover recovery times.
Automated test tools (k6, Chaos Mesh), test environments, pass/fail gating thresholds, and sign-off accountability.
Completion Instructions
Independent Review Checklist
- All mandatory sections completed
- No secrets or passwords included
- Executive sponsor sign-off obtained
Non-Functional Requirements and Quality-Attribute Scenarios - Worked Case Study
Fictional Entity: AeroGlobal High-Volume Flight Reservation Engine
Real-world production case study demonstrating complete operational adoption for AeroGlobal High-Volume Flight Reservation Engine.
- •Authored 32 verifiable SEI quality scenarios covering 12,000 RPS flash-sale flight searches
- •Mandated p99 latency < 180ms with 99.99% availability budget across multi-cloud regions
- •Blocked 6 production performance regressions via automated k6 load gates in staging CI/CD
Frequently Asked Questions
What are the 6 parts of an SEI Quality Attribute Scenario?
The 6 parts are: 1. Source (who generates the stimulus), 2. Stimulus (the condition that arrives), 3. Artifact (the system component stimulated), 4. Environment (system state during stimulus, e.g. peak load), 5. Response (the action undertaken), and 6. Response Measure (the quantitative, testable threshold).
Why is a 99th percentile (p99) latency metric superior to an average latency metric?
Average latency hides the "long tail" of poor user experience. In a high-traffic system, a 50ms average might hide the fact that 1 in 100 users waits over 4 seconds, causing checkout abandonment.
How are NFRs validated continuously in modern software delivery?
Through automated performance regression tests (k6/JMeter) in staging, static security analysis (SAST) in pull requests, and real-time observability telemetry (Prometheus/Datadog) in production.
Download Tech Document Pack
Auth RequiredDownload all blank templates, worked scenarios, and verification manifests in a single verified archive.
Authoritative Sources
- ISO/IEC 25010:2011 Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE)ISO/IEC • OFFICIAL REQUIREMENT
- Software Engineering Institute (SEI): Quality Attribute ScenariosCarnegie Mellon SEI • OFFICIAL REQUIREMENT