R. C. Linger. Cleanroom Software Engineering for ZeroDefect Software. Proc. 15 th International Conference on Software Engineering, Baltimore, MD, May 1993.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....in field usage the behavior that it exhibits under test. For example, this idea is at the center of Cleanroom s discipline of reliability assessment, which generates test data to mimic usage patterns, and predicts reliability in the field as an extrapolation of reliability growth under test [3, 13, 12]. Of course, one may argue that although adaptive systems evolve over time, they change for the better. But better in the sense of adaptive systems (stability, convergence) does not mean better in the traditional sense of testing (satisfies the oracle condition more often) Concretely, an adaptive ....

R. C. Linger. Cleanroom Software Engineering for ZeroDefect Software. Proc. 15 th International Conference on Software Engineering, Baltimore, MD, May 1993.

....whether the NFR Framework reduces rework and scrap, hence inducing shorter production time and lower cost, like its sibling QFD. Thorough evaluations have been reported of some quantitative, more product oriented approaches which have an emphasis on defect defection and reduction. For instance, [37] gives an elegant evaluation of the cleanroom approach whose emphasis is on carrying out different inspection tasks by independent teams. Similarly, 57] gives a realistic evaluation of the N fold inspection technique whose emphasis is on replicating the same requirements inspection task by ....

R. C. Linger, "Cleanroom Software Engineering for ZeroDefect Software," Proc., 15th Int. Conf. on Software Eng., Baltimore, MD, May 1993, pp. 2--13.

....this goal, we submit input data to the program and observe its behavior, in the hope of showing that the program behaves according to its specifications for all instances of the test data. No modification of the product is involved under this goal. ffl Reliability estimation. Under this goal [1, 6, 5], we submit input data to the program and observe its behavior; whenever it fails, we identify the fault, remove it, then resume testing. By keeping track of the evolution of inter failure intervals, we hope to predict the reliability of the product after delivery. Because we are concerned with ....

R.C. Linger. Cleanroom software engineering for zero-defect software. In Proceedings, 15th Hawaii International Conference on Software Engineering, Baltimore, MD, May 1993.

....Cleanroom originally proposed by H.D. Mills [15] allows the development of near zero defect software with certifiable quality by using formal techniques, organizational principles, and statistical quality control. The application of Cleanroom has shown remarkable results. So NASA SEL [6] IBM [11], University of Maryland [19] Ericsson [22] and various other organizations have recognized that not only can productivity and product quality be increased, but effort and failure rates can also be decreased by applying the principles espoused by Cleanroom. In Cleanroom projects different ....

Richard C. Linger. Cleanroom Software Engineering for Zero -Defect software. In Proceedings of the 15th International Conference on Software Engineering, pages 2--13, Los Alamitos California, May 1993. IEEE CS Press.

....[5] ffl Design. Design is carried out by mapping black boxes into state boxes then clear boxes, which are increasingly detailed design representations [5] ffl Verification. Methods of correctness verification are deployed at each step of the transformation process. Also, under Cleanroom [1, 2, 4, 3], verification based inspections substitute for traditional unit testing. ffl Testing. Under Cleanroom, testing is used exclusively for certification and reliability estimation. Functional (black box) testing is applied, where input data is generated randomly to simulate the statistical usage ....

R.C. Linger. Cleanroom software engineering for zero-defect software. In Proceedings, 15th Hawaii International Conference on Software Engineering, Baltimore, MD, May 1993.

....whether the NFR Framework reduces rework and scrap, hence inducing shorter production time and lower cost, like its sibling QFD. Thorough evaluations have been reported of some quantitative, more product oriented approaches which have an emphasis on defect defection and reduction. For instance, Linger93] gives an elegant evaluation of the cleanroom approach whose emphasis is on carrying out different inspection tasks by independent teams. Similarly, Schneider92] gives a realistic evaluation of the N fold inspection technique whose emphasis is on replicating the same requirements inspection task ....

Richard C. Linger, "Cleanroom Software Engineering for Zero-Defect Software." In Proc., 15th Int. Conf. on Software Eng., Baltimore, MD, May 1993, pp. 2--13.

....and certification are carried out incrementally and the system integration is continuous. During the development of the later versions, earlier versions and their interfaces must not be changed. As a methodology, evolutionary software design is similar to IBM s Cleanroom Software Engineering [13], primarily because of the similarities in incremental development. The main difference is the treatment of incremental units. In case of evolutionary design, earlier versions include the core functions critical for the safety of the system and they may be invoked as independent programs in the ....

R. C. Linger, "Cleanroom Software Engineering for Zero-Defect Software," Proc. 15 th International Conferenceon Software Engineering, Baltimore, MD, May 1993.

....to result in systems which cannot be accredited, are more costly and less trustworthy. Quantitative and product oriented approaches for addressing NFRs have been proposed (e.g. Keller90] These approaches have been evaluated with an emphasis on defect defection and reduction. For instance, Linger93] provides an elegant evaluation of the cleanroom approach, whose emphasis is on carrying out different inspection tasks by independent teams. Similarly, Schneider92] gives some evaluation of the N fold inspection technique whose emphasis is on replicating the same requirements inspection task by ....

Richard C. Linger, "Cleanroom Software Engineering for Zero-Defect Software." In Proc., 15th Int. Conf. on Software Eng., Baltimore, MD, May 1993, pp. 2--13.

.... Cleanroom Software Engineering Reference Model n 1 1 The Cleanroom Software Engineering Reference Model Cleanroom software engineering is a theory based, team oriented process for development and certification of high reliability software systems under statistical quality control [Mills 92, Linger 93, Linger 94] A principal objective of the Cleanroom process is development of software that exhibits zero failures in use. The Cleanroom name is borrowed from hardware Cleanrooms, with their emphasis on rigorous engineering discipline and focus on defect prevention rather than defect removal. ....

Linger, R.C. "Cleanroom Software Engineering for ZeroDefect Software." Proceedings of 15th International Conference on Software Engineering. Baltimore, Md., May 17-21, 1993. Los Alamitos, Ca.: IEEE Computer Society Press, 1993.

....review and comments. CMU SEI 96 TR 023 Cleanroom Implementation of the CMM for Software n 1 1 Cleanroom and the CMM for Software The Capability Maturity Model sm for Software (CMM) CMU 95] developed by the Software Engineering Institute, and Cleanroom Software Engineering [Mills 87, Linger 93, Linger 94] developed by Dr. Harlan Mills and his associates in IBM and other organizations, share a common concern with software quality and the effectiveness of software development. The principal focus of the CMM is on process management maturity; the principal focus of Cleanroom is on ....

Linger, R.C. "Cleanroom Software Engineering for ZeroDefect Software." Proceedings of the 15th International Conference on Software Engineering. Baltimore, Md., May 17-21, 1993. Los Alamitos, Ca.: IEEE Computer Society Press, 1993.

No context found.

R.C. Linger, Cleanroom software engineering for zero-defect software, in Proc. 15th Int. Conf. Software Eng., 2#13, 1993.

No context found.

R.C. Linger, Cleanroom software engineering for zero-defect software, in Proc. 15th Int. Conf. Software Eng., pp. 2#13, 1993.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC