Experience applying the CoRE method to the Lockheed C-130J software requirements

Faulk, Stuart; Finneran, Lisa; Kirby, James; Shah, Syed Zafar Ali; Sutton, James

doi:10.1109/cmpass.1994.318472

Cited by 33 publications

(18 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A considerable number of successful experiences have been reported on the application of FMs to real industrial projects [AF&92,FF&94,Hal96,FMAD,LRD95,B&H95]; almost unanimously they confirm the major expected benefits, mostly in terms of early error detection and, ultimately, in terms of increased reliability. Nevertheless their adoption within standard industrial practices is still an exception and several typical criticisms and skepticisms are emphatically claimed by their opponents.…”

Section: Introductionmentioning

confidence: 92%

From formal models to formally based methods

Ciapessoni

Mirandola

Coen‐Porisini

et al. 1999

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

We address the problem of increasing the impact of formal methods in the practice of industrial computer applications. We summarize the reasons why formal methods so far did not gain widespread use within the industrial environment despite several promising experiences. We suggest an evolutionary rather than revolutionary attitude in the introduction of formal methods in the practice of industrial applications and we report on our long-standing experience which involves an academic institution, Politecnico di Milano, two main industrial partners, ENEL and CISE, and occasionally a few other industries. Our approach aims at augmenting an existing and fairly deeply rooted informal industrial methodology with our original formalism, the logic specification language TRIO. On the basis of the experiences we gained we argue that our incremental attitude towards the introduction of formal methods within the industry could be effective largely independently from the chosen formalism.

show abstract

Section: Introductionmentioning

confidence: 92%

From formal models to formally based methods

Ciapessoni

Mirandola

Coen‐Porisini

et al. 1999

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

show abstract

“…This document i n troduces many features associated with the SCR requirements method|the tabular notation, the underlying nite state machine model, and special constructs for specifying requirements, such as conditions and events, input and output data items, mode classes, and terms. Recently, a n umber of researchers, including Faulk 7,8 ,9 , van Schouwen 24, 25 , and Parnas 21 , have extended and re ned the original SCR method and strengthened the method's formal foundation.…”

Section: Review Of the Scr Methodsmentioning

confidence: 99%

SCR*: A Toolset for Specifying and Analyzing Requirements

Heitmeyer¹,

Bull²,

Gasarch³

et al. 1995

View full text Add to dashboard Cite

A set of CASE tools is described for developing formal requirements speci cations expressed in the SCR Software Cost Reduction tabular notation. The tools include an editor for building the speci cations, a consistency checker for testing the speci cations for consistency with a formal requirements model, a simulator for symbolically executing the speci cations, and a veri er for checking that the speci cations satisfy selected application properties. As background, the SCR method for specifying requirements is reviewed, and a formal requirements model is introduced. Examples are presented to illustrate the tools.

show abstract

“…More recently, a version of the SCR method called CoRE ] was used to document requirements of Lockheed's C-130J Operational Flight Program (OFP) [Faulk et al 1994]. The OFP consists of more than 100K lines of Ada code, thus demonstrating the scalability of the SCR method.…”

Section: Performing Organization Name(s) and Address(es)mentioning

confidence: 99%

Automated consistency checking of requirements specifications

Heitmeyer

Jeffords

Labaw

1996

ACM Trans. Softw. Eng. Methodol.

478

325

View full text Add to dashboard Cite

This article describes a formal analysis technique, called consistency checking, for automatic detection of errors, such as type errors, nondeterminism, missing cases, and circular definitions, in requirements specifications. The technique is designed to analyze requirements specifications expressed in the SCR (Software Cost Reduction) tabular notation. As background, the SCR approach to specifying requirements is reviewed. To provide a formal semantics for the SCR notation and a foundation for consistency checking, a formal requirements model is introduced; the model represents a software system as a finite-state automaton, which produces externally visible outputs in response to changes in monitored environmental quantities. Results of two experiments are presented which evaluated the utility and scalability of our technique for consistency checking in a real-world avionics application. The role of consistency checking during the requirements phase of software development is discussed.

show abstract

Experience applying the CoRE method to the Lockheed C-130J software requirements

Cited by 33 publications

References 4 publications

From formal models to formally based methods

From formal models to formally based methods

SCR*: A Toolset for Specifying and Analyzing Requirements

Automated consistency checking of requirements specifications

Contact Info

Product

Resources

About