Which of the following is not a key strategy followed by the clean room approach to software development?
Pick an option to check yourself, or open the answer below.
Show answer & explanation
Correct answer: B. Dynamic verification
Explanation
The answer is Dynamic verification. Cleanroom software engineering deliberately replaces developer debugging and unit testing with static correctness verification: the program is mathematically argued to match its formal specification before it is ever executed. Its recognised key strategies are formal specification of the software using a state-transition model, incremental development in small certifiable increments, structured programming, static correctness verification by review teams, and statistical testing of the integrated system against an operational profile. Dynamic (execution-based) verification by the developers is exactly what cleanroom avoids, so options (1), (3) and (4) are all genuine cleanroom strategies.More Software Engineering questions
- Consider the following statements: P: Refactoring is the process of changing a software system in such a way that it does not alter the ext…
- Statistical software quality assurance in software engineering involves ______.
- A signal processor software is expected to operate for 91.25 days after repair, and the mean software repair time is expected to be 5 minut…
- Which of the following is not one of three software product aspects addressed by McCall's software quality factors?
- A server has 30 days mean time between failure (MTBF) and 12 hours mean time to repair (MTTR). The availability of the server is approximat…
- Software safety is quality assurance activity that focuses on hazards that