Any
good system (in this case, a good system to produce clean software) should be effective, consistent,
efficient, scalable, visible and agile.
The figure shown below outlines the various approaches deployed to produce clean software. The various approaches are highlighted as rows with the system attributes shown as columns. A dark blue dot represents that attribute is well met while a light blue dot implies that it may not that well met.
An “Hypothesis-based Testing” approach that takes scientific view to detecting defects has a higher ability to satisfy all the attributes.
In STEM, there is a clear distinction between Test level, Test technique and Test Type.
In STEM, we apply an appropriate technique at each level for designing test scenarios/cases for a given test type.
In STEM, the objective is to discover issues as early in the SDLC; hence applicable test types are executed early in the lifecycle.
In STEM, a judicious application of structural (White) and Functional (Black) techniques is applied to cost-effectively generate optimal test cases.
In STEM, defects are categorized into different types.
In STEM, different defect types are expected to detect at different stages i.e. different levels of testing detect different types of defects. The impact of the defect increases at every level, hence STEM ensures that defects escapes are minimized.
STEM has yielded significant results for our customers. Some of the key results are highlighted below.
 |
WHY STEM? | OBJECTIVES OF STEM | STEM Way | STEM Core | HYPOTHESIS-BASED TESTING
|
