Software Cost Reduction

Abstract

Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

Model-based adaptation of flight-critical systems

“…T-Vec is a best-ofbreed automatic test vector and test harness generator that uses, as input, detailed requirements models developed in the standard Software Cost Reduction (SCR) language [31]. Developed at the Naval Research Laboratory, SCR is a formal language and a standard methodology created to describe requirements as a set of causal relationships presented in a tabular form for ease of understandability.…”

Modular Functional Descriptions

“…As generally used, e.g., in embedded systems, functions are intended for the description of signal-based reactive systems, using asynchronous communication unlike [5] or [10]. They use a communication paradigm similar to [9], [4], or [3]. Therefore, they provide similar forms of conjunctive and disjunctive compositions as provided for the modules introduced in [4] or the states introduced in [2].…”

“…However, while the descriptive form of general functional descriptions eases the combination and reuse of functions and the reasoning about the overall functionality, for the final implementation of the intended behavior in general more constructive forms of descriptions are used, as provided, e.g., by corresponding tools like or [2], [3], or [6]. As stated in Section 1, these descriptions correspond to a restricted form of functions, avoiding the introduction of partiality and ensuring input enabledness.…”

“…As stated in Section 1, these descriptions correspond to a restricted form of functions, avoiding the introduction of partiality and ensuring input enabledness. On this constructive level, input enabledness is either established implicitly by completion (as, e.g., in [6]) or explicitly by analysis (as, e.g., in [3]). However, to integrate these different applications of functional descriptions are integrated in a function-based development process, the more descriptive and more constructive forms must linked by an implementation relation, introduced in the following.…”

Systematic Development of Requirements Documentation for General Purpose Scientific Computing Software

“…A systematic approach to requirements documentation has been effectively used in other application areas, such as with business applications [12] and for real-time systems, such as the shutdown systems of the Darlington nuclear generating station [9] and flight guidance and weapons systems [5]. However, the characteristics of scientific software mean that methods that have been successful elsewhere will have to be modified and adapted [16].…”