Four dark corners of requirements engineering

ABSTRACT

Research in requirements engineering has produced an extensive body of knowledge, but there are four areas in which the foundation of the discipline seems weak or obscure. This article shines some light in the “four dark corners,” exposing problems and proposing solutions. We show that all descriptions involved in requirements engineering should be descriptions of the environment. We show that certain control information is necessary for sound requirements engineering, and we explain the close association between domain knowledge and refinement of requirements. Together these conclusions explain the precise nature of requirements, specifications, and domain knowledge, as well as the precise nature of the relationships among them. They establish minimum standards for what information should be represented in a requirements language. They also make it possible to determine exactly what it means for requirements and engineering to be successfully completed.

REFERENCES

• 1: Martín Abadi , Leslie Lamport, Composing specifications, ACM Transactions on Programming Languages and Systems (TOPLAS), v.15 n.1, p.73-132, Jan. 1993 [doi>10.1145/151646.151649]
• 2: ALPERN, B. AND SCHNEIDER, F.B. 1987. Recognizing safety and liveness. Distrib. Comput. 2, 117-126.
• 3: Joanne M. Atlee , John Gannon, Analyzing timing requirements, ACM SIGSOFT Software Engineering Notes, v.18 n.3, p.117-127, July 1993
• 4: BALZER, R. AND GOLDMAN, N. 1979. Principles of good software specification and their implications for specification language. In Proceedings of the Specifications of Reliable Software Conference. IEEE Computer Society, Washington, D.C., 58-67.
• 5: BRACHMAN, R. J., FIKES, R. E., AND LEVESQUE, H.J. 1983. Krypton: A functional approach to knowledge representation. IEEE Comput. 16, 10 (Oct.), 67-73.
• 6: BUBENKO, J. A., JR., Ed. 1983. On concepts and strategies for requirements and information analysis. In Information Modeling. Chartwell-Bratt, Bromley, England, 125-169.
• 7: Bill Curtis , Herb Krasner , Neil Iscoe, A field study of the software design process for large systems, Communications of the ACM, v.31 n.11, p.1268-1287, Nov. 1988 [doi>10.1145/50087.50089]
• 8: Anne Dardenne , Axel van Lamsweerde , Stephen Fickas, Goal-directed requirements acquisition, Science of Computer Programming, v.20 n.1-2, p.3-50, April 1993
• 9: J. E. Dobson , A. J. C. Blyth , J. Chudge , R. Strens, The ORDIT approach to organisational requirements, Requirements engineering: social and technical issues, Academic Press Professional, Inc., San Diego, CA, 1994
• 10: Eric Dubois , Philippe Du Bois , Michaël Petit, O-O Requirements Analysis: an Agent Perspective, Proceedings of the 7th European Conference on Object-Oriented Programming, p.458-481, July 26-30, 1993
• 11: Martin S. Feather, Language support for the specification and development of composite systems, ACM Transactions on Programming Languages and Systems (TOPLAS), v.9 n.2, p.198-234, April 1987 [doi>10.1145/22719.22947]
• 12: FEATHER, M. S. 1994. Towards a derivational style of distributed system design--An example. Automated Softw. Eng. 1, 1 (Mar.), 31-59.
• 13: FEATHER, M. S., FICKAS, S., AND HELM, B.R. 1991. Composite system design: The good news and the bad news. In Proceedings of the 6th Annual Knowledge-Based Software Engineering Conference. IEEE Computer Society, Washington, D.C., 16-25.
• 14: David Gries , Fred B. Schneider, A logical approach to discrete math, Springer-Verlag New York, Inc., New York, NY, 1993
• 15: David Harel, Statecharts: A visual formalism for complex systems, Science of Computer Programming, v.8 n.3, p.231-274, June 1, 1987 [doi>10.1016/0167-6423(87)90035-9]
• 16: HEITMEYER, C., BULL, A., GASARCH, C., AND LABAW, B. 1995a. SCR*: A toolset for specifying and analyzing requirements. In Proceedings of the l Oth Annual Conference on Computer Assurance (COMPASS '95). IEEE, New York, 109-122.
• 17: C. Heitmeyer , B. Labaw , D. Kiskis, Consistency checking of SCR-style requirements specifications, Proceedings of the Second IEEE International Symposium on Requirements Engineering, p.56, March 27-29, 1995
• 18: HENINGER, K.L. 1980. Specifying software requirements for complex systems: New techniques and their application. IEEE Trans. Softw. Eng. 6, 1 (Jan.), 2-13.
• 19: C. A. R. Hoare, Communicating sequential processes, Prentice-Hall, Inc., Upper Saddle River, NJ, 1985
• 20: Neil Iscoe , Gerald B. Williams , Guillermo Arango, Domain modeling for software engineering, Proceedings of the 13th international conference on Software engineering, p.340-343, May 13-17, 1991, Austin, Texas, United States
• 21: Daniel Jackson, Structuring Z specifications with views, ACM Transactions on Software Engineering and Methodology (TOSEM), v.4 n.4, p.365-389, Oct. 1995 [doi>10.1145/226241.226249]
• 22: M M Jackson, Information systems: Modelling, sequencing and transformations, Proceedings of the 3rd international conference on Software engineering, p.72-81, May 10-12, 1978, Atlanta, Georgia, United States
• 23: M. A Jackson, System development (Prentice-Hall International series in computer science), Prentice-Hall, Inc., Upper Saddle River, NJ, 1983
• 24: Michael Jackson, Software requirements & specifications: a lexicon of practice, principles and prejudices, ACM Press/Addison-Wesley Publishing Co., New York, NY, 1995
• 25: Michael Jackson , Pamela Zave, Deriving specifications from requirements: an example, Proceedings of the 17th international conference on Software engineering, p.15-24, April 24-28, 1995, Seattle, Washington, United States [doi>10.1145/225014.225016]
• 26: JARKE, M., BUBENKO, J., ROLLAND, C., SUTCLIFFE, A., AND VASSILIOU, Y. 1992. Theories underlying requirements engineering: An overview of NATURE at genesis. In Proceedings of the IEEE International Symposium on Requirements Engineering. IEEE Computer Society, Washington, D.C., 19-31.
• 27: JEREMAES, P., KHOSLA, S., AND MAIBAUM, T. S.E. 1986. A modal (action) logic for requirements specification. In Software Engineering 86, D. Barnes and P. Brown, Eds. Peter Peregrinus, 278-294.
• 28: W. L. Johnson, Deriving specifications from requirements, Proceedings of the 10th international conference on Software engineering, p.428-438, April 11-15, 1988, Singapore
• 29: Cliff B. Jones, Systematic software development using VDM (2nd ed.), Prentice-Hall, Inc., Upper Saddle River, NJ, 1990
• 30: S. Khoshafian , G. P. Copeland, Object identity, Readings in object-oriented database systems, Morgan Kaufmann Publishers Inc., San Francisco, CA, 1989
• 31: Leslie Lamport, A simple approach to specifying concurrent systems, Communications of the ACM, v.32 n.1, p.32-45, Jan. 1989 [doi>10.1145/63238.63240]
• 32: LEHMAN, M.M. 1980. Programs, life cycles, and laws of software evolution. Proc. IEEE 68, 9 (Sept.), 1060-1076.
• 33: Nancy G. Leveson , Mats Per Erik Heimdahl , Holly Hildreth , Jon D. Reese, Requirements Specification for Process-Control Systems, IEEE Transactions on Software Engineering, v.20 n.9, p.684-707, September 1994 [doi>10.1109/32.317428]
• 34: LISKOV, B. H. AND ZILLES, S.N. 1975. Specification techniques for data abstractions. IEEE Trans. Softw. Eng. 1, 1 (Mar.), 7-19.
• 35: MOSTOW, J. 1983. A problem-solver for making advice operational. In Proceedings of the National Conference on Artificial Intelligence (AAAI-83). AAAI, Menlo Park, Calif., 279-283.
• 36: D L Parnas , P C Clements, A rational design process: How and why to fake it, IEEE Transactions on Software Engineering, v.12 n.2, p.251-257, Feb. 1986
• 37: David Lorge Parnas , Jan Madey, Functional documents for computer systems, Science of Computer Programming, v.25 n.1, p.41-61, Oct. 1995 [doi>10.1016/0167-6423(95)96871-J]
• 38: J. Michael Spivey, Specifying a Real-Time Kernel, IEEE Software, v.7 n.5, p.21-28, September 1990 [doi>10.1109/52.57889]
• 39: J. M. Spivey, The Z notation: a reference manual, Prentice Hall International (UK) Ltd., Hertfordshire, UK, 1992
• 40: William Swartout , Robert Balzer, On the inevitable intertwining of specification and implementation, Communications of the ACM, v.25 n.7, p.438-440, July 1982 [doi>10.1145/358557.358572]
• 41: W. M. Turski, Time considered irrelevant for real-time systems, BIT, v.28 n.3, p.473-486, 1988 [doi>10.1007/BF01941129]
• 42: VAN SCHOUWEN, A. g., PARNAS, D. L., AND MADLY, g. 1992. Documentation of requirements for computer systems. In Proceedings of the IEEE International Symposium on RequiremeAts Engineering. IEEE Computer Society, Washington, D.C., 198-207.
• 43: Jeannette M. Wing, A Specifier's Introduction to Formal Methods, Computer, v.23 n.9, p.8-23, September 1990 [doi>10.1109/2.58215]
• 44: J. B. Wordsworth, Software Development with Z: A Practical Approach to Formal Methods in Software Engineering, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1992
• 45: Yu, E., Du BoIs, PH., DUBOIS, E., AND MYLOPOULOS, g. 1995. From organization models to system requirements: A "cooperating agents" approach. In Proceedings of the 3rd International Conference on Cooperative Information Systems. 194-204.
• 46: ZAVE, P. 1982. An operational approach to requirements specification for embedded systems. IEEE Trans. Softw. Eng. 8, 3 (May), 250-269.
• 47: Pamela Zave , Michael Jackson, Conjunction as composition, ACM Transactions on Software Engineering and Methodology (TOSEM), v.2 n.4, p.379-411, Oct. 1993 [doi>10.1145/158431.158438]

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications
          Subjects: Methodologies (e.g., object-oriented, structured)

General Terms:
Theory

Keywords:
control of actions, domain knowledge, implementation bias, refinement of requirements