Using the SCR* toolset to specify software requirements

@article{Heitmeyer1998UsingTS,
  title={Using the SCR* toolset to specify software requirements},
  author={Constance L. Heitmeyer},
  journal={Proceedings. 2nd IEEE Workshop on Industrial Strength Formal Specification Techniques},
  year={1998},
  pages={12-13}
}
  • C. Heitmeyer
  • Published 20 October 1998
  • Computer Science
  • Proceedings. 2nd IEEE Workshop on Industrial Strength Formal Specification Techniques
Formulated in the late 1970s to specify the requirements of the Operational Flight Program of the A-7 aircraft, the SCR (Software Cost Reduction) requirements method is a method based on tables for specifying the requirements of software systems. During the 1980s and the early 1990s, many companies, including Bell Laboratories, Grumman, Ontario Hydro, and Lockheed, applied the SCR requirements method to practical systems. Each of these applications of SCR had, at most, weak tool support. To… 
SCR requirements using XSPIN model checking to Elevator Case Study
TLDR
The power of formality maintained and practical usability increased in this project, and SCR (Software Cost Reduction) is a tabular notation, which has a tool call SCRTool, which allow the tabular specification covert to formal specification for spin to check safety critical and liveness property.
Completeness in formal specification language design for process-control systems
TLDR
It is shown how most of the criteria can be embedded in a formal specification language in ways that potentially allow automated checking or assist in manual reviews.
A novel requirement analysis approach for periodic control systems
TLDR
This paper proposes a novel requirement analysis approach, which supports the automated validation of the informal requirement specifications and enables the analysis of the dataflow relations in SPARDL models.
An Approach to Requirement Analysis for Periodic Control Systems
  • Jianwen Li, G. Pu, B. Gu
  • Computer Science
    2012 35th Annual IEEE Software Engineering Workshop
  • 2012
TLDR
A requirement analysis approach to periodic control systems that are widely used as one of the real time systems by regulating the initial requirement documents with key words in natural language into an intermediate model specified by SPARDL language with formal syntax and semantics is proposed.
Test-driven specification: paradigm and automation
TLDR
An automated tool, the test-driven specification assistant (TDSA), which supports the use of test cases in the specification process, and decision tables are used as a lightweight specification language capable of modeling black-box and Mills' state box specifications.
SPARDL: A Requirement Modeling Language for Periodic Control System
TLDR
To analyze periodic control systems in SPARDL, a requirement prototype generation algorithm is proposed to simulate and test the requirements, and a structural operational semantics is proposed forSPARDL.
Tabular Expressions in Software Engineering
TLDR
A brief history of tabular expressions, motivation for the development of semantics for tables, a description of a semantic definition of tables, and a discussion on notation and use of tables in practice are presented based on many years of experience of using tables in industrial software development projects.
Extent and characteristics of dependencies between vehicle functions in automotive software systems
TLDR
Structural models of a modern realistic automotive vehicle system are analyzed with the aim to assess the extent and characteristics of interactions between system functions and show that at least 69% of the analyzed system functions depend on each other or influence each other.
Why feature dependencies challenge the requirements engineering of automotive systems: An empirical study
TLDR
The results show that within the functional architecture at least 85% of the analyzed vehicle features depend on each other, and show that the developers are not aware of a large number of these dependencies when they are modeled solely on an architectural level.
A framework for defining and analysing access policies in requirements models
TLDR
The framework presented in this thesis makes a novel contribution to the modelling of access policies as requirements, enabling us to define access policies using actors derived from the organisational context, that satisfy the minimum privileges principle.
...
1
2
...

References

SHOWING 1-10 OF 15 REFERENCES
Specifying Software Requirements for Complex Systems: New Techniques and Their Application
TLDR
The purpose of the paper is to introduce the A-7 document as a model of a disciplined approach to requirements specification and the document is available to anyone who wishes to see a fully worked-out example of the approach.
SCR: a toolset for specifying and analyzing requirements
  • C. Heitmeyer, A. Bull, C. Gasarch, B. Labaw
  • Computer Science
    COMPASS '95 Proceedings of the Tenth Annual Conference on Computer Assurance Systems Integrity, Software Safety and Process Security'
  • 1995
TLDR
A set of CASE tools is described for developing formal requirements specifications expressed in the SCR (Software Cost Reduction) tabular notation, which include an editor for building the specifications, a consistency checker for testing the specifications for consistency with a formal requirements model, and a verifier for checking that the specifications satisfy selected application properties.
Experiences Using Lightweight Formal Methods for Requirements Modeling
TLDR
In all three cases, formal methods enhanced the existing verification and validation processes by testing key properties of the evolving requirements and helping to identify weaknesses.
SCR*: A Toolset for Specifying and Analyzing Software Requirements
TLDR
The SCR (Software Cost Reduction) tools are described, part of a “practical” formal method—a.
Tools for formal specification, verification, and validation of requirements
TLDR
Recent enhancements to the SCR tools are described: a new dependency graph browser which displays the dependencies among the variables in the specification, an improved consistency checker which produces detailed feedback about detected errors, and an assertion Checker which checks application properties during simulation.
Automated consistency checking of requirements specifications
TLDR
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 expressed in the SCR (Software Cost Reduction) tabular notation.
A Toolset for Specifying and Analyzing Requirements
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
Specifying the mode logic of a flight guidance system in CoRE and SCR
TLDR
The experiences of Rockwell Avionics & Communications in using the CORE and SCR methods to specify the requirements for the mode logic of a Flight Guidance System for a General Aviation class aircraft are described.
Using Abstraction and Model Checking to Detect Safety Violations in Requirements Specifications
TLDR
A "practical" formal method that can expose inconsistencies in software requirements specifications and the SCR (software cost reduction) tabular notation is described, which most software developers should be able to apply without extraordinary effort.
Automatic generation of state invariants from requirements specifications
TLDR
An algorithm for the automatic generation of state invariants that derives invariants from requirements specifications from specifications expressed in the SCR (Software Cost Reduction) tabular notation is described.
...
1
2
...