1. Lempia, D. and Miller, S., "Requirements Engineering Management Findings Report," FAA report DOT/FAA/AR-08/34, May 2009.

2. Parnas, D. and Madey, J., "Functional Documentation for Computer Systems Engineering (Version 2)," Technical Report CRL 237, McMaster University, Hamilton, Ontario, September 1991.

3. Van Schouwen, A., "The A-7 Requirements Model: Re-examination for Real-Time Systems and an Application to Monitoring Systems," Technical Report 90−276, Queens University, Hamilton, Ontario, 1990.

4. Faulk, S., Brackett, J., Ward, P., and Kirby, J., Jr., "The CoRE Method for Real-Time Requirements," IEEE Software, Vol. 9, No.

5, September 1992, pp. 22−33. 5. Faulk, S., Finneran, L., Kirby, J., and Moini, A., "Consortium Requirements Engineering Guidebook," Technical Report SPC-92 060-CMS, Software Productivity Consortium, 2214 Rock Hill Road, Herndon, Virginia, December 1993.

6. Faulk, S., Finneran, L., Kirby, J., Shah, S., and Sutton, J., "Experience Applying the CoRE Method to the Lockheed C-130J Software Requirements," Proceedings of the Ninth Annual Conference on Computer Assurance, Gaithersburg, Maryland, June 1994, pp. 3−8.

7. Heitmeyer, C., Kirby, J., and Labaw, B., "Automated Consistency Checking of Requirements Specification," ACM Transactions on Software Engineering and Methodology (TOSEM), Vol. 5, No. 3, July 1996, pp. 231−261.

8. Leveson, N., Heimdahl, M., Hildreth, H., and Reese, J., "Requirements Specifications for Process-Control Systems," IEEE Transactions on Software Engineering, Vol. 20, No. 9, September 1994, pp. 684−707.

9. Leveson, N., Heimdahl, M., Hildreth, H., and Reese, J., "TCAS II Collision Avoidance System (CAS) System Requirements Specification Change 6.00," Federal Aviation Administration, U.S. Department of Transportation, March 1993.

10. Thompson, J., Heimdahl, M., and Miller, S., "Specification-Based Prototyping for Embedded Systems," Proceedings Seventh ACM SIGSOFT Symposium on the Foundations on Software Engineering, LNCS 1687, September 1999, pp. 163−179.

11. Leveson, N., Heimdahl, M., and Reese, J., "Designing Specification Languages for Process Control Systems: Lessons Learned and Steps to the Future," Proceedings Seventh ACM SIGSOFT Symposium on the Foundations on Software Engineering, LNCS 1687, September 1999, pp. 127−145.

12. Miller, S., Tribble, A., Whalen, M., and Heimdahl, M., "Providing the Shalls," International Journal on Software Tools for Technology Transfer (STTT), February 2006.

13. Howard, J. and Anderson, P., "The Safety Risk of Requirements Incompleteness," Proceedings of the 20th International System Safety Conference (ISSC 2002), Denver, Colorado, August 2002.

14. Lee, G., Howard, J., and Anderson, P., "Safety-Critical Requirements Specification Using SpecTRM," Proceedings of the 2nd Meeting of the US Software System Safety Working Group, February 2002.

15. Leveson, N., Reese, J., and Heimdahl, M., "SpecTRM: A CAD System for Digital Automation," Proceedings of 17th Digital Avionics System Conference (DASC98), Seattle, Washington, November 1998.

16. Leveson, N., "Intent Specifications: An Approach to Building Human-Centered Specifications," IEEE Transactions on Software Engineering, Vol. 26, No. 1, January 2000, pp. 15−35.

17. Cockburn, A., Writing Effective Use Cases, Addison-Wesley, Boston, Massachusetts, 2001.

18. Alexander, I. and Zink, T., "An Introduction to Systems Engineering With Use Cases," IEEE Computer and Control Engineering, December 2002.

19. Leffingwell, D. and Widrig, D., Managing Software Requirements, Addison-Wesley, Reading, Massachusetts, 2003.

20. Booch, G., Rumbaugh, J., and Jacobson, I., The Unified Modeling Language User Guide, Addison Wesley, Reading, Massachusetts, 1999.

21. Fowler, M., UML Distilled, A Brief Guide to the Standard Object Modeling Language, Third Edition, Addison Wesley, Reading, Massachusetts, September 2003.

22. Hooks, I. and Farry, K., "Customer Centered Products: Creating Successful Products Through Smart Requirements Management," AMACOM American Management Association, New York, New York, 2001.

23. Davis, A., Software Requirements (Revised): Object, Functions, and States, PrenticeHall, Englewood Cliffs, New Jersey, 1993.

24. Leveson, N., Safeware: System Safety and Computers, Addison-Wesley Publishing Company, Reading, Massachusetts, 1995.

25. "IEEE Guide for Developing System Requirements Specifications," IEEE Std 1233, The Institute of Electrical and Electronics Engineers, New York, New York, December 1998.

26. "IEEE Recommended Practice for Software Requirements Specifications," IEEE Std 830−1998, The Institute of Electrical and Electronics Engineers, New York, New York, June 1998.

27. "Software Considerations in Airborne Systems and Equipment Certification," DO-178B, RTCA, Washington, DC, December 1, 1992.

28. "Final Report for Clarification of DO-178B, "Software Considerations in Airborne Systems and Equipment Certification," DO-248B, RTCA, Washington, DC, October 12, 2001.

29. "Guidelines for Communication, Navigation, Surveillance, and Air Traffic Management (CNS/ATM) Systems Software Integrity Assurance," DO-278, March 5, 2002.

30. "Certification Considerations for Highly-Integrated or Complex Aircraft Systems," ARP 4754, SAE International, November 1996.

31. "Guidelines and Methods for Conducting the Safety Assessment Process on Civil Airborne Systems and Equipment," ARP 4761, SAE International, December 1996.

32. Hughes, D. and Dornheim, M., "Automated Cockpits Special Report, Parts I & II," Aviation Week & Space Technology, January 30-February 6, 1995.

33. Billings, C., Aviation Automation: The Search for a Human Centered Approach, Lawrence Erlbaum Associates, Inc., Mahwah, New Jersey, 1997.

34. Commercial Aviation Safety Team, "Final Report of the Loss of Control JSAT: Results and Analysis," P. Russell and J. Pardee, Co-chairs, December 15, 2000.

35. Leveson, N., et al., "Analyzing Software Specifications for Mode Confusion Potential," Proceedings of a Workshop on Human Error and System Development, Glasgow, Scotland, March 1997, pp. 132−146.

36. Leveson N., "Designing Automation to Reduce Operator Errors," Proceedings of the IEEE Systems, Man, and Cybernetics Conference, October 1997.

37. Sarter, N., Woods, D., and Billings, C., "Automaton Surprises," Handbook of Human Factors/Ergonomics, 2nd ed., G. Salvendy, ed., John Wiley & Sons, New York, New York, 1997.

38. Woodson, W., Tilman, P., and Tilman, B., Human Factors Design Handbook, Second Edition, McGraw-Hill Companies, 1992.

39. Boff, K. and Lincoln, J., Engineering Data Compendium: Human Perception and Performance, Wright-Patterson Air Force Base, Harry G. Armstrong Aerospace Medical Research Laboratory, Ohio, 1998.

40. Coplien, J., Hoffman, D., and Weiss, D., "Commonality and Variability in Software Engineering," IEEE Software, Vol. 20, No. 6, November 1998.

41. De Marco, T., "Structured Analysis and System Specification," Yourdon Press, New York, 1979.

42. Harel, D., "Statecharts: A Visual Formalism for Complex Systems," Science of Computer Programming, Vol. 8, 1987, pp. 231.

43. Hoffman, D. and Weiss, D., "Software Fundamentals: Collected Papers by David L. Parnas," Addison-Wesley Professional, Boston, Massachusetts, 2001.

44. Miller, S. and Tribble, A., "Extending the Four-Variable Model to Bridge the SystemSoftware Gap, 20th Digital Avionics Systems Conference (DASC01), Daytona Beach, Florida, October 14−18, 2001.

45. Stevens, R., Jackson, B., and Arnold, S., "Systems Engineering: Coping With Complexity," Prentice-Hall, London, 1998.

46. Brooks, F., "No Silver Bullet: Essence and Accidents of Software Engineering," IEEE Computer, April 1987.

47. Boehm, B., "Software Engineering Economics," Prentice-Hall, Englewood Cliffs, New Jersey, 1981.