recategorized by
2,731 views
2 votes
2 votes

Which of the following is not a key strategy followed by the clean room approach to software development?

  1. Formal specification
  2. Dynamic verification
  3. Incremental development
  4. Statistical testing of the system
recategorized by

2 Answers

2 votes
2 votes

Option (2) Dynamic Verification is not a key strategy.

There are following Key strategies for clean Room Software Development

  • Formal specification
  • Incremental development
  • Structured programming
  • Static verification 
  • Statistical testing of the system 
1 votes
1 votes

Answer :  (2). Dynamic verification

Reason :

Cleanroom software development is a software development philosophy that is based on avoiding software defects by using formal methods of development and a rigorous inspection process. The name ‘Cleanroom’ was derived by analogy with semiconductor fabrication units. In these units (cleanrooms) defects are avoided by manufacturing in an ultra-clean atmosphere. The objective of this approach to software development is zero-defect software.
The Cleanroom approach to software development is based on five key strategies:
  • Formal specification The software to be developed is formally specified. A state-transition model which shows system responses to stimuli is used to express the specification.
  • Incremental development The software is partitioned into increments which are developed and validated separately using the Cleanroom process. These increments are specified, with customer input, at an early stage in the process.
  • Structured programming Only a limited number of control and data abstraction constructs are used. The program development process is a process of stepwise refinement of the specification. A limited number of constructs are used and the aim is to apply correctness-preserving transformations to the specification to create the program code.
  • Static verification The developed software is statically verified using rigorous software inspections. There is no unit or module testing process for code components.
  • Statistical testing of the system The integrated software increment is tested statistically (see Chapter XX), to determine its reliability. These statistical tests are based on an operational profile which is developed in parallel with the system specification.

Related questions

2 votes
2 votes
3 answers
2
Pooja Khatri asked Jul 13, 2018
2,754 views
Match the following in Software Engineering :$\begin{array}{clcl} &\textbf{List-I}& & \textbf{List-II} \\ \text{(a)}& \text{Product Complexity} & \text{(i)} & \text{Soft...
1 votes
1 votes
4 answers
3
Pooja Khatri asked Jul 13, 2018
1,733 views
Which one of the following is not typically provided by Source Code Management Software?SynchronizationVersioning and Revision historySyntax highlightingProject forking
0 votes
0 votes
3 answers
4
Pooja Khatri asked Jul 13, 2018
2,000 views
A software system crashed 20 times in the year 2017 and for each crash, it took 2 minutes to restart. Approximately, what was the software availability in that year?96.99...