Software requirements engineering glossary

Software Requirements Engineering

Volumn , Issue , 2011, Pages 489-528

  Thayer, Richard H ^a   Thayer, Mildred C ^a  

^a Software Management Consultants   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

SOFTWARE ENGINEERING;

REQUIREMENTS ENGINEERING;

EID: 85036595612     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1109/9781118156674.gloss     Document Type: Chapter

References (79)

1. ANSI N45.2.10-1973, Quality Assurance Terms and Definitions, American National Standards Institute, NY, 1973.
2. ANSI/ASQC A3-1978, Quality Systems Terminology, American National Standards Institute, NY, 1978.
3. ANSI/IEEE Standard 729-1983, IEEE Standard Glossary of Software Engineering Terminology, The Institute of Electrical and Electronics Engineers, New York, N.Y., approved by American National Standards Institute Aug. 9, 1983.
4. ANSI/IEEE Standard 829-1983, IEEE Standard for Software Test Documents, The Institute of Electrical and Electronics Engineers, New York, NY, approved by American National Standards Institute Aug. 19, 1983.
5. ANSI/IEEE Standard 830-1984, IEEE Guide for Software Requirements Specifications, The Institute of Electrical and Electronics Engineers, New York, N.Y., approved by American National Standards Institute July 20, 1984.
6. ANSI/IEEE Standard 1058.1-1987, IEEE Standard for Software Project Management Plans, The Institute of Electrical and Electronics Engineers, New York, N.Y., approved by American National Standards Institute Oct. 6, 1988.
7. Bersoff, E.H., “Elements of Software Configuration Management,” IEEE Trans. Software Engineering, Vol. SE-10, No. 1, Jan. 1984, pp. 79-87.
8. Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.
9. Boehm, B.W., Software Risk Management, IEEE Computer Society Press, Los Alamitos, Calif., 1989.
10. Boehm, B.W., “A Spiral Model of Software Development and Enhancement,” in Thayer, R.H., ed., Tutorial: Software Engineering Project Management, IEEE Computer Society Press, Los Alamitos, Calif., 1988. Also published in Computer, Vol. 21, No. 5, Apr. 1988, pp. 61-72.
11. Boehm, B.W., “Verifying and Validating Software Requirements and Design Specifications,” IEEE Software, Vol. 1, No. 1, Jan. 1984, pp. 75-88.
12. Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, CA, 1990.
13. Booch, Grady, Object-Oriented Analysis and Design, Benjamin/Cummings, Redwood City, Calif., 1994.
14. Either the term is unique to the United Kingdom or the definition is different from that used in the United States.
15. Chen, P.P., “Entity-Relationship Approach to Data Modeling,” in Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.
16. Davis, A.M., “The Analysis and Specification of System and Software Requirements,” in Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.
17. Davis, A.M., E.H. Bersoff, and E.R. Comer, “A Strategy for Comparing Alternate Software Development Life Cycle Models,” IEEE Trans. Software Eng., Vol. SE-14, No. 10, Oct. 1988, pp. 1453-1461.
18. Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.
19. Davis, A.M., “A Comparison of Techniques for the Specification of External System Behavior,” Comm. ACM, Vol. 31, No. 9, Sept. 1988, pp. 1098-1115.
20. Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.
21. MoD, Hazard Analysis and Safety Classification of the Computer and Programmable Electronic System Elements of Defence Equipment, Def Stan 00-56/Issue 1, Ministry of Defence, United Kingdom, Apr. 5, 1991.
22. DeMarco, T., Structured Analysis and System Specification, Prentice-Hall, Englewood Cliffs, N.J., 1979.
23. DoD Directive 5010.19, Configuration Management, U.S. Department of Defense, Oct. 28, 1987.
24. DoD Standard 480B, Configuration Control-Engineering Changes, Deviation and Waivers, U.S. Department of Defense, July 15, 1988.
25. DoD Standard 2167A, Defense System Software Development, U.S. Department of Defense, Feb. 29, 1988.
26. Technical Management Department, Defense Systems Management College (DSMC), System Engineering Management Guide, 2nd ed., DSMC, Fort Bel-voir, V.A., 1986.
27. Dorfman, M., “System and Software Requirements Engineering,” in Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.
28. Draft ESPRIT Work programme, Commission of the European Communities, Brussels, July 22, 1987.
29. FIPS Publication 101, Guideline for Lifecycle Validation, Verification, and Testing of Computer Software, Federal Information Processing Standards Publication 101, Institute for Computer Science and Technology, National Bureau of Standards, Gaithersburg, M.D., 1983.
30. Flynn, R.F., and M. Dorfman, “The Automated Requirements Traceability System (ARTS): An Experience of 8 Years,” in Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.
31. Forsberg, K., and H. Mooz, “System Engineering Overview,” in Software Requirements Engineering, Thayer, R.H., and M. Dorfman, eds., IEEE Computer Society Press, Los Alamitos, Calif., 1997.
32. Foster, J.R., A.E.P. Jolly, and M.T. Norris, “An Overview of Software Maintenance,” British Telecom Technology Journal, Vol. 7, No. 4, October 1989, pp. 37-46.
33. Gane, C.P., and Sarson, T., Structured Systems Analysis: Tools and Techniques, Prentice-Hall, Englewood Cliffs, NJ, 1979.
34. Gehani, N., “Specifications: Formal and Informal-A Case Study,” Software Practices and Experiences, Vol. 12, 1982, pp. 433-444.
35. Heninger, K.L., “Specifying Software Requirements for Complex Systems: New Techniques and Their Application,” IEEE Trans. Software Eng., Vol. SE-6, No. 1, Jan. 1980, pp. 2-13.
36. Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.
37. Hollocker, C.P., “Requirement Specification Examinations,” in Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.
38. Humphrey, W.S., Managing the Software Process, Addison-Wesley, Reading, Mass., 1989.
39. IEE/BCS, Software in Safety-Related Systems, The Institution of Electrical Engineering and The British Computer Society, Oct. 1989.
40. IEEE P1362, IEEE Guide for Concept of Operations Document, Draft 2.5, The Institute of Electrical and Electronics Engineers, NY, Feb. 26, 1996.
41. Keller, S.E., L.G. Kahn, and R.B. Panara, “Specifying Software Quality Requirements with Metrics,” in Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.
42. G. Kotonya, and Sommerville, I., “Requirements Engineering with Viewpoints,” Software Engineering J., Vol. 11, No. 1, Jan. 1996, pp. 5-18.
43. 2 Chart,” TRW-SS-77-04, TRW Defense and Space Systems Group, Redondo Beach, CA, 1977. Republished as A Technique for Software and Systems Design, Vol. 3, North-Holland Publishing Co, New York, N.Y., 1979.
44. R.H. Thayer and M. Dorfman (eds.), System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.
45. Manley, J.H., “Computed Aided Software Engineering (CASE): Foundation for Software Factories,” Proc. IEEE COMPCON ’84 Fall Computer Conference on the Small Computer (R) IEEE Computer Society Press, Los Alamitos, Calif., 1984, pp. 84-91.
46. McDermid, John A., Software Engineering Reference Book, Butterworth Heine-mann, Jordon Hill, Oxford, England, 1991.
47. Military Standard 499A, Engineering Management (USAF), U.S. Department of Defense, May 1, 1974.
48. Military Standard 1521B (USAF), Technical Reviews and Audits for Systems, Equipment, and Computer Programs, U.S. Department of Defense, 1985.
49. Martin, R.J., and W.M. Osborne, Guidance on Software Maintenance, NBS Special Publication 500-106, Institute for Computer Science and Technology, National Bureau of Standards, Gaithersburg, MD, 1983.
50. The National Computer Centre, The Starts Guide, 2nd Ed., Vol. I, Chapter 5, The National Computer Centre, Manchester, England, 1987.
51. Nelsen, E.D., “System Engineering and Requirement Allocation,” in Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.
52. Norris, M., “Z (A Formal Specification Method): A Debrief Report,” The National Computing Centre, Manchester, England, 1986.
53. Thayer, R.H., and M. Dorfman, eds., IEEE Computer Society Press, Los Alamitos, Calif., 1990. See also STARTS Debrief Reports for reports on other software tools and methods.
54. Northrop, Linda M., “Object-Oriented Development,” in Software Engineering, Dorfman, M., and R.H. Thayer, eds., IEEE Computer Society Press, Los Alamitos, Calif., 1996.
55. Oxford Dictionary of Computing, 3rd Ed., Oxford University Press, Oxford, England, 1990.
56. Bowen, T.P., G.B. Wigle, and J.T. Tsai, Specification of Software Quality Attributes, Vol. 1, Final Technical Report; Vol. 2, Software Quality Specifications Guidebook; Vol. 3, Software Quality Evaluation Guidebook;RADC TR-85-37, prepared by Boeing Aerospace Company for Rome Air Development Center, Griffiss AFB, N.Y., Feb. 1985.
57. Ramamoorthy, C.V., A. Prakash, W. Tsai, and Y. Usuda, “Software Engineering: Problems and Perspectives,” Computer, Vol. 17, No. 10, Oct. 1984, pp. 191-209.
58. Thayer, R.H., ed., Tutorial: Software Engineering Project Management, IEEE Computer Society Press, Los Alamitos, Calif., 1988.
59. Rich, C, R.C. Waters, and H.B. Reubenstein, “Toward a Requirements Apprentice,” Proc. 4th Inťl Workshop Software Specifications and Design, IEEE Computer Society Press, Los Alamitos, Calif., 1987, pp. 79-86.
60. Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.
61. Robson, D.J., K.H. Bennett, B.J. Cornellius, and M. Munro, “Approaches to Program Comprehension,” J. Systems and Software, Vol. 14, No. 2, Feb. 1991, pp. 79-84.
62. Rook, P., “Controlling Software Projects,” Software Engineering J., Jan. 1986, pages 716. In R.H. Thayer (ed.), Software Engineering Project Management, IEEE Computer Society Press, Los Alamitos, Calif., 1988.
63. Rumbaugh, J., “Getting Started: Using Use Cases to Capture Requirements,” J Object Oriented Programming, Sept. 1994, pp. 812-823.
64. Thayer, R.H., and M. Dorfman, eds., IEEE Computer Society Press, Los Alamitos, Calif., 1997.
65. Rzepka, W., and Y. Ohno, “Requirements Engineering Environments: Software Tools for Modeling User Needs,” Guest Editors Introduction, Computer, Vol. 18, No. 4, Apr. 1985, pp. 9-12.
66. Sailor, J.D., “System Engineering Overview,” in System and Software Requirements Engineering, Thayer, R.H., and M. Dorfman, eds., IEEE Computer Society Press, Los Alamitos, Calif., 1990.
67. Sayani, H.H., “PSL/PSA at the Age of Fifteen,” in System and Software Requirements Engineering, Thayer, R.H., and M. Dorfman, eds., IEEE Computer Society Press, Los Alamitos, Calif., 1990.
68. Scharer, L., “Pinpointing Requirements,” Datamation, April 1981, pp. 139-151.
69. Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.
70. Searle, L.V., An Air Force Guide to System Specification, ESD TR-81-128, Electronic Systems Division, Hanscom AFB, Mass., 1981.
71. Spivey, J.M., “An Introduction to Z and Formal Specifications,” Software Engineering J., Vol. 4, No. 1, Jan. 1989, pp. 40-50.
72. National Computing Centre, The STARTS Guide, 2nd Ed., The National Computing Centre, Manchester, England, 1987.
73. Thayer, R.H., A.B. Pyster, and R C. Wood, “Major Issues in Software Engineering Project Management,” IEEE Trans. Software Eng., Vol. SE-7, No. 4, July 1981, pp. 333-342.
74. The term is primarily used by the U.S. Department of Defense and the aerospace industry.
75. Ward, P.T., and S.J. Mellor, Structured Development for Real-Time Systems: Vol. 1, Introduction & Tools; Vol. 2, Essential Modeling Techniques; Vol. 3, Implementation Modeling Techniques; Yourdon Press, New York, N.Y., 1986. (Note: The principal [first] author for Vol. 3 is S.J. Mellor.)
76. Wasserman, A.I., and P.A. Pircher, “A Graphic, Extensible Integrated Environment for Software Development,” Proc. 2nd ACM SIGSOFT/SIGPLAN Software Engineering Symp., Practical Software Development Environment ACM Press, New York, N.Y., 1986. Published in ACM SIGPLAN Notices, Vol. 22, No. 1, Jan. 1987, pp. 131-142.
77. Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.
78. Williams, J., “SSADM-System Building Made Simple,” Systems International, Nov. 1987, pp. 91-92.
79. Thayer, R.H., and M. Dorfman, eds., System and Software Requirements Engineering, IEEE Computer Society Press, Los Alamitos, Calif., 1990.