K. L. Heninger, J. Kallander, D. L. Parnas, and J. E. Shore. Software requirements for the A-7E aircraft. Technical Report 3876, United States Naval Research Laboratory, Washington D. C., 1978. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Certifying Adaptive Flight Control Software - Vittorio Cortellessa Bojan (2000) (1 citation) (Correct)
....requirements of fault tolerant flight control systems. We have chosen to use SCR as the specification vehicle, because it lends itself to this type of application: requirements properties of the FTFCS. For example, tabular representations, which form the semantic foundations of SCR, were used in [8] to specify the requirements of the Navy s A7 E aircraft, and in [20] to specify nuclear power plant s control systems. SCR was also used to specify an autopilot [6] to specify a variety of high assurance applications [10, 11] and to specify some functions of the space shuttle software [27] The ....
K. L. Heninger, J. Kallander, D. L. Parnas, and J. E. Shore. Software requirements for the A-7E aircraft. Technical Report 3876, United States Naval Research Laboratory, Washington D. C., 1978.
Test Oracles - Baresi, Young (2001) (1 citation) (Correct)
....i.e. the oracle is decoupled from test case selection or generation. If the specification is already in the form of a state machine, or can be easily interpreted as a state machine, then it may be useful to derive test cases and corresponding oracles together. The SCR (Software Cost Reduction, HKPS78] method is a requirements specification methodology based on a tabular notation and on several accompanying tools for error detection. Gargantini and Heitmeyer have described an approach for deriving from SCR specification models of external system behavior, oracles paired with test 39 cases in ....
K. L. Heninger, J. Kallander, D. L. Parnas, and J. E. Shore. Software Requirements for the A-7E Aircraft. NRL Memorandum Report 3876, United States Naval Research Laboratory, November 1978.
Relational Semantics of Tabular Expressions: Talk Abstract - Desharnais, Khedri, Mili (Correct)
.... Ridha Kh edri Communications Research Laboratory McMaster University Hamilton, ON, L8S 4K1 Canada khedri mcserg.crl.mcmaster.ca Ali Mili Institute for Software Research 1000 Technology Drive Fairmont, WV, 26554 USA amili cs.wvu.edu 1 Specifying with Tabular Expressions Parnas et al. [2, 3, 4, 5, 6] have long advocated the use of relations to write specifications, and have produced ample evidence to the effect that relations are adequate to specify and verify complex, life critical, systems. Also, they have felt the need to represent complex relations by means of tabular representations, ....
K. L. Heninger, J. Kallander, D. L. Parnas, and J. E. Shore. Software requirements for the A-7E aircraft. Technical Report 3876, United States Naval Research Laboratory, Washington D. C., 1978.
Sequential Scenarios Verification and Integration using Tabular.. - Khedri (1999) Self-citation (Report) (Correct)
....reasons. They are intended 2 Sequential Scenarios Veri cation and Integration using Tabular Expressions 3 to supplement, not replace, notation that is already in use by many engineers. They have been found useful for describing the speci ed mathematical relations in practical applications [7, 21, 22, 23, 36, 48]. When they are handled by a tool, like Table Tool System [8, 9] they are suitable for managing change for systems and families of systems. Since, it is not true that determining requirements is an isolated and unique phase of the development. Engineers have to talk to a wide range of people ....
K. L. Heninger, J. Kallander, D. L. Parnas, and J. E. Shore. Software requirements for the A-7E aircraft. NRL Memorandum Report 3876, United States Naval Research Laboratory, Washington D. C., 1978.
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