# |
Core concept |
Short description |
| 1
|
Value prioritization |
A technique to understand the business value of system requirements/ features |
2 |
Attribute analysis |
A technique to understand the system attributes and ensure that they are testable |
3 |
Landscapes |
A technique to understand the system and construct the product landscape |
4 |
Viewpoints |
A technique to understand end user expectations via different points of view |
5 |
Interaction matrix |
A technique to understand the between the various parts of the software |
6 |
Reductionist principle |
A principle to demystify the complexity by a logical breakdown of the system |
7 |
EFF model |
A technique to identify probable faults by understanding potential failures and error injection opportunities |
8 |
Defect centricity principle |
A principle to identify different types (patterns) of defects that cause 'dirtiness' |
9 |
Negative thinking |
A technique to help identify potential defects in the system |
10 |
Orthogonality principle |
A principle that helps understand the relationship between defect, test type, test level and test technique |
11 |
Approximation principle |
A principle that allows for scientific approximation |
12 |
Defect centered activity breakdown |
A technique for estimating effort by applying a defect centric thinking to arrive the list of activities |
13 |
Quality growth principle |
A principle to create a quality growth model for optimal testing |
14 |
Techniques landscape |
A guideline that outlines the various test techniques and its applicability |
15 |
Process landscape |
A guideline that outlines the various process models for effective and efficient testing |
16 |
Behavior Stimuli approach |
A technique for designing test cases by understanding the behavior model and its excitations |
17 |
Operational profiling |
A technique to model the profile of usage in real-life |
18 |
Box model |
A technique to understand the functional behavior of function/requirement |
19 |
Input granularity principle |
A principle that aids in understanding the specification of input(s) to ensure testability |
20 |
Test coverage evaluation |
A technique to to assess the adequacy/coverage of test cases |
21 |
Complexity assessment |
A technique to assess the complexity of a function/requirement |
22 |
GQM |
A technique to design measurements/metrics that are focused on the end goal |
23 |
Quality quantification model |
A technique to come with objective evaluation of quality |
24 |
Metrics landscape |
A guideline to help formulate metrics |
25 |
Automation complexity assessment |
A technique to assess the complexity of automating a feature/requirement |
26 |
Minimal babysitting principle |
A principle to design automation scripts to ensure unattended test runs do not abort midway |
27 |
Separation of concerns principle |
The principle to ensure that the automation scripts are better maintainable |
28 |
Tooling need analysis |
A technique to logically analyze the needs of tooling for optimal ROI |
29 |
Contextual awareness |
A principle to help being context sensitive to aid in better testing |
30 |
Defect rating principle |
A principle to rate the defects in terms of severity and priority |
31 |
Gating principle |
A principle to setup effective 'gates' in the test process to optimize test effort |
32 |
Cycle scoping |
A technique to formulate the scope of a test cycle |
