Cleanroom process model

Linger, Richard C.

doi:10.1109/52.268956

Cited by 99 publications

(24 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In programming, a new form of development is called cleanroom development (Linger, 1994). In this approach, the program is proven to be correct mathematically before it is written.…”

Section: Implications For Developmentmentioning

confidence: 99%

What We Know About Spreadsheet Errors

Panko

1998

Journal of Organizational and End User Computing

291

202

View full text Add to dashboard Cite

Although spreadsheet programs are used for small "scratchpad" applications, they are also used to develop many large applications. In recent years, we have learned a good deal about the errors that people make when they develop spreadsheets. In general, errors seem to occur in a few percent of all cells, meaning that for large spreadsheets, the issue is how many errors there are, not whether an error exists. These error rates, although troubling, are in line with those in programming and other human cognitive domains. In programming, we have learned to follow strict development disciplines to eliminate most errors. Surveys of spreadsheet developers indicate that spreadsheet creation, in contrast, is informal, and few organizations have comprehensive policies for spreadsheet development. Although prescriptive articles have focused on such disciplines as modularization and having assumptions sections, these may be far less important than other innovations, especially cell-by-cell code inspection after the development phase.

show abstract

“…In programming, a new form of development is called cleanroom development (Linger, 1994). In this approach, the program is proven to be correct mathematically before it is written.…”

Section: Implications For Developmentmentioning

confidence: 99%

What We Know About Spreadsheet Errors

Panko

1998

Journal of Organizational and End User Computing

291

202

View full text Add to dashboard Cite

show abstract

“…One of the main problems lay in the requirements themselves. Having been written over a period of time, several inconsistencies had crept in, despite the best efforts of the WRAIR researchers to apply rigorous, cleanroombased techniques to requirement capture [23]. A more precise design language that would overcome the natural ambiguities and unstructuredness of a textual description of such a complex system would have been very helpful in this regard.…”

Section: Discussion and Related Workmentioning

confidence: 99%

Unit verification: the CARA experience

Ray

Cleaveland

2004

International Journal on Software Tools for Technology Transfer

View full text Add to dashboard Cite

Abstract. The Computer-Aided Resuscitation Algorithm, or CARA, is part of a US Army-developed automated infusion device for treating blood loss experienced by combatants injured on the battlefield. CARA is responsible for automatically stabilizing a patient's blood pressure by infusing blood as needed, based on blood-pressure data the CARA system collects. The control part of the system is implemented in software, which is extremely safety-critical and thus must perform correctly.This paper describes a case study in which a verification tool, the Concurrency Workbench of the New Century (CWB-NC), is used to analyze a model of the CARA system. The huge state space of the CARA makes it problematic to conduct traditional "push-button" automatic verification, such as model checking. Instead, we develop a technique, called unit verification, which entails taking small units of a system, putting them in a "verification harness" that exercises relevant executions appropriately within the unit, and then model checking these more tractable units. For systems, like CARA, whose requirements are localized to individual system components or interactions between small numbers of components, unit verification offers a means of coping with huge state spaces.

show abstract

“…Legacy system wrapping:-Legacy systems that can be "wrapped" by defining a set of interfaces and providing access to these legacy systems through these interfaces [6].…”

Section: Component-based Development:-mentioning

confidence: 99%

Reusability of the Software

Singh¹,

Singh²,

Singh³

2010

IJCA

View full text Add to dashboard Cite

Reusability is the likelihood a segment of source code that can be used again to add new functionalities with slight or no modification. Reusable modules and classes reduce implementation time, increase the likelihood that prior testing and use has eliminated bugs and localizes code modifications when a change in implementation is required. Subroutines or functions are the simplest form of reuse. A chunk of code is regularly organized using modules or namespaces into layers. Proponents claim that objects and software components offer a more advanced form of reusability, although it has been tough to objectively measure and define levels or scores of reusability. Reusability implies some explicit management of build, packaging, distribution, installation, configuration, deployment, maintenance and upgrade issues. If these issues are not considered, software may appear to be reusable from design point of view, but will not be reused in practice. This paper presents an empirical study of the software reuse activity by expertdesigners in the context of object-oriented design. Our study focuses on the three following aspects of reuse : (1) the interaction between some design processes, e.g. constructing a problem representation, searching for and evaluating solutions, and reuse processes, i.e. retrieving and using previous solutions, (2) the mental processes involved in reuse, e.g. example-based retrieval or bottom-up versus top-down expanding of the solution, and (3) the mental representations constructed throughout the reuse activity, e.g. dynamic versus static representations.

show abstract

Cleanroom process model

Cited by 99 publications

References 6 publications

What We Know About Spreadsheet Errors

What We Know About Spreadsheet Errors

Unit verification: the CARA experience

Reusability of the Software

Contact Info

Product

Resources

About