Loading content
Non-functional testing is a structured method to evaluate system attributes such as performance, scalability, reliability, security and maintainability. It defines test scenarios, environments and metrics to validate non-functional requirements and supports architectural and operational decisions. It integrates with CI/CD and monitoring to enable continuous…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Non-functional testing evaluates qualities such as performance, security, reliability, usability, and compatibility.
It grew from the insight that correct functions alone do not guarantee a usable system. Quality models and standards such as ISO/IEC 25010 (2011) organize these qualities; the practice has no single originator.
Translate a quality goal into an observable question: how fast, under what load, how secure, or how accessible should the system be? Define a measure, conditions, and threshold. Test representatively and repeat after changes. Qualities can conflict: more security or consistency may affect latency and convenience.
An attribute describes how well a system performs a function, not which function it offers.
A measure and threshold make a quality goal testable.
Improving one attribute can create cost or degradation in another.
Non-functional testing exposes operational and usage quality early. It needs realistic conditions and priorities because not every attribute can be maximized.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.