Quickly locate bugs

#efficient

Stimulus: Developers, testers or the build system execute automatic test cases (unit or integration tests).

Reaction: In that process, a test fails.

Metric: Based upon the error and/or log messages, a developer can locate the cause of the error in less than 10 minutes on average

Related Quality Requirements

Add new product under 60 minutes | #suitable #efficient #reliable
Affordable CRM (customer relationship management) | #efficient #suitable
Budget constrained library update | #efficient #suitable
Capacity to process 1000 sensor inputs per minute | #efficient
Consistent keyboard shortcuts | #usable #efficient
Data Throughput for Visual Test System | #efficient #usable
Easily understandable acceptance test cases | #usable #suitable #efficient
Easily understandable generated code | #efficient #usable #suitable
Efficient change of business rules | #flexible #efficient
Efficient generation of test data | #efficient #suitable
Efficient save function | #efficient
Efficient update of annual accounting report | #efficient #flexible
Fast and accurate sensor | #efficient #reliable
Fast creation of sales report | #efficient
Fast rollout of changes | #efficient #operable
Fast startup time | #efficient
Independent enhancement of subsystem | #efficient #flexible
Independent replacement of subsystem | #flexible #operable #efficient
Low impact diagnosis | #efficient
Low-overhead query execution measurement | #efficient
Maintainable checking strategies | #efficient
Modular System for Data Analysis | #efficient #flexible
Near instant search results | #usable #efficient
Reduce energy consumption with every new version | #efficient
Respond to 15000 requests per workday | #efficient
Response time for image rendering | #efficient
Restricted Memory | #efficient
Save at least 20% of carbon emissions with every new version | #efficient

Related Qualities

Efficiency
Maintainability