Applying the SCR requirements method to a weapons control panel

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

	1	T. A. Alspaugh, S. R. Faulk, K. H. Britton, R. A. Parker, D. L. Parnas, and J. E. Shore. Software requirements for the A-7E aircraft. Technical Report NRL-9194, Naval Research Lab., Wash., DC, 1992.
	2	M. Archer and C. Heitmeyer. TAME: A specialized specification and verification system for timed automata. In Proc., Real-Time Systems Symposium Work-in-Progress Session, 1996.
	3	R. Bharadwaj and C. Heitmeyer. Applying the SCR requirements method to a simple autopilot. In Proc., Fourth NASA Langley Formal Methods Workshop (Lfm97), 1997.
	4	R. Bharadwaj and C. Heitmeyer. Model checking complete requirements specifications using abstraction. Technical Report 97-7999, Naval Research Lab., Wash., DC, 1997.
	5	R. Bharadwaj and C. Heitmeyer. Verifying SCR requirements specifications using state exploration. In Proc., First A CM SiGPLAN Workshop on Automatic Analysis of Software, 1997.
	6	Norm Brown, Industrial-Strength Management Strategies, IEEE Software, v.13 n.4, p.94-103, July 1996 [doi>10.1109/52.526836]
	7	Edmund M. Clarke , Orna Grumberg , David E. Long, Model checking and abstraction, Proceedings of the 19th ACM SIGPLAN-SIGACT symposium on Principles of programming languages, p.343-354, January 19-22, 1992, Albuquerque, New Mexico, United States [doi>10.1145/143165.143235]
	8	J. Crow and B. L. Di Vito. Formalizing space shuttle requirements. In Proc. of FMSP'96, The 1st Workshop on Formal Methods in Software Practice, 1996.
	9	Bruno Dutertre , Victoria Stavridou, Formal Requirements Analysis of an Avionics Control System, IEEE Transactions on Software Engineering, v.23 n.5, p.267-278, May 1997 [doi>10.1109/32.588520]
	10	Steve Easterbrook , John Callahan, Formal Methods for V&V of Partial Specifications: An Experience RSeport, Proceedings of the 3rd IEEE International Symposium on Requirements Engineering (RE'97), p.160, January 05-08, 1997
	11	Steve Easterbrook , John Callahan, Formal methods for verification and validation of partial specifications: a case study, Journal of Systems and Software, v.40 n.3, p.199-210, March 1998 [doi>10.1016/S0164-1212(97)00167-2]
	12	S. R. Faulk, L. Finneran, J. Kirby, Jr., S. Shah, and J. Sutton. Experience applying the CoRE method to the Lockheed C-130J. In Proc. 9th Annual Conf. on Computer Assurance (COMPASS 'gd), pages 3- 8, Gaithersburg, MD, June 1994.
	13	A. Flora-ttolmquist and M. Staskauskas. Moving formal methods into practice: The VFSM experience. In Proc. of FMSP'96, The 1st Workshop on Formal Methods in Software Practice, 1996.
	14	Anthony Hall, Using Formal Methods to Develop an ATC Information System, IEEE Software, v.13 n.2, p.66-76, March 1996 [doi>10.1109/52.506463]
	15	Mats P. E. Heimdahl , Nancy G. Leveson, Completeness and consistency analysis of state-based requirements, Proceedings of the 17th international conference on Software engineering, p.3-14, April 24-28, 1995, Seattle, Washington, United States [doi>10.1145/225014.225015]
	16	C. Heitmeyer, J. Kirby, and B. Labaw. Tools for formal specification, verification, and validation of requirements. In Proc. l~h Annual Conf. on Cornpater Assurance (COMPASS '97), Gaithersburg, MD, June 1997.
	17	C. Heitmeyer, J. Kirby, B. Labaw, M. Archer, and R. Bharadwaj. Using model checking and simulation to detect a safety violation in a control system specification. Submitted for publication.
	18	C. L. Heitmeyer, R. D. Jeffords, and B. G. Labaw. Tools for analyzing SCR-style requirements specifications: A formal foundation. Technical Report NRL-7499, Naval Research Lab., Wash., DC. In preparation.
	19	Constance L. Heitmeyer , Ralph D. Jeffords , Bruce G. Labaw, Automated consistency checking of requirements specifications, ACM Transactions on Software Engineering and Methodology (TOSEM), v.5 n.3, p.231-261, July 1996 [doi>10.1145/234426.234431]
	20	K. L. Heninger. Specifying software requirements for complex systems: New techniques and their application. IEEE Trans. Softw. Eng., SE-6(1):2-13, Jan. 1980.
	21	S. D. Hester, D. L. Parnas, and D. F. Utter. Using documentation as a software design medium. Bell System Tech. J., 60(8):1941-1977, Oct. 1981.
	22	Gerard J. Holzmann, The Model Checker SPIN, IEEE Transactions on Software Engineering, v.23 n.5, p.279-295, May 1997 [doi>10.1109/32.588521]
	23	R. P. Kurshan, Formal verification in a commercial setting, Proceedings of the 34th annual conference on Design automation, p.258-262, June 09-13, 1997, Anaheim, California, United States [doi>10.1145/266021.266089]
	24	S. Meyer and S. White. Software requirements methodology and tool study for A6-E technology transfer. Technical report, Grumman Aerospace Corp., Bethpage, NY, July 1983.
	25	Steven P. Miller, Specifying the mode logic of a flight guidance system in CoRE and SCR, Proceedings of the second workshop on Formal methods in software practice, p.44-53, March 04-05, 1998, Clearwater Beach, Florida, United States [doi>10.1145/298595.298856]
	26	Sam Owre , John Rushby , Natarajan Shankar , Friedrich von Henke, Formal Verification for Fault-Tolerant Architectures: Prolegomena to the Design of PVS, IEEE Transactions on Software Engineering, v.21 n.2, p.107-125, February 1995 [doi>10.1109/32.345827]
	27	A. J. van Schouwen, D. L. Pumas, and J. Madey. Documentation of requirements for computer systems. In Proc. RE'93 Requirements Syrup., pages 198-207, San Diego, CA, Jan. 1993.