A sample text widget

Etiam pulvinar consectetur dolor sed malesuada. Ut convallis euismod dolor nec pretium. Nunc ut tristique massa.

Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan. Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem, suscipit in posuere in, interdum non magna.

What is meant by clean-room software engineering?

In order to get a software of high quality, a formal approach to software development known as cleanroom software engineering can be used. It focuses on defect prevention rather than defect removal.

What it uses?
Integrated use of:
– software engineering modeling
– program verification
– statistical software quality assurance.

What are key characteristics of Cleanroom strategy?
– Incremental Development
– Defect Prevention
– Disciplined software engineering methods

What is meant by Incremental Development?
– Customer involvement and feedback is required for developing the right system in the first place.
– Facilitates the customer’s clarification of system requirements.
– Requires management control of resources and technical control of complexity.
– Product quality requires process measurement and control throughout the SW development cycle.

What is it actually?
– It verifies design specification
– It relies heavily on statistical use testing
– It generally follows an incremental development process

What are its benefits?
– Zero failures in the field
– Short development cycles
– Longer product life

What are its principles?
– Small teams which includes independent specification, development, and certification sub-teams.
– Incremental development under statistical quality control
– Software development based on mathematical principles
– Testing based on statistical principles

What are cleanroom strategies?
– Increment planning.
– Requirements gathering
– Box structure specification which isolates and separates the definition of behavior, data, and procedures at each level of refinement.
– Formal design.
– Correctness verification
– Code generation, inspection, verification
– Statistical test planning.
– Statistical use testing.
– Certification

Development in cleanroom strategy depends on three things:
– Black box
Data implementation and process implementation are hidden.
– State box
It shows data implementation but hides process implementation.
– Clear box
It shows both data implementation and process implementation.

Common Points between Cleanroom and Object Oriented Software Engineering
– Usage : Same as object oriented use case.
– Life cycle : Both follow incremental development.
– State Machine Use : cleanroom state box and OO transition diagram
– Reuse

Key Differences between Cleanroom and Object Oriented Software Engineering
– Object Oriented software engineering depends on composition whereas Cleanroom depends on decomposition.
– Object Oriented software engineering allows informal use case definition and testing whereas Cleanroom depends on formal methods.
– Cleanroom usage hierarchy is system itself whereas Object Oriented software engineering inheritance hierarchy is a design resource.
– Object Oriented software engineering practitioners prefer graphical representations while cleanroom practitioners prefer tabular representations.
– Tool support is good for most Oriented software engineering processes, but usually tool support is only found in cleanroom testing not design.

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>