Applying domain and design knowledge to requirements engineering

ABSTRACT

This paper describes efforts to develop a transformation-based software environment which supports the acquisition and validation of software requirements specifications. These requirements may be stated informally at first, and then gradually formalized and elaborated. Support is provided for groups of requirements analysis working together, focusing on different analysis tasks and areas of concern. The environment assists in the validation of formalized requirements by translating them into natural language and graphical diagrams, and testing them against a running simulation of the system to be built. Requirements defined in terms of domain concepts are transformed into constraints on system components. The advantages of this approach are that specifications can be traced back to requirements and domain concepts, which in turn have been precisely defined.

REFERENCES

• 1: J. S. Anderson , S. Fickas, A proposed perspective shift: viewing specification design as a planning problem, Proceedings of the 5th international workshop on Software specification and design, p.177-184, April 1989, Pittsburgh, Pennsylvania, United States
• 2: [2] ASA. Airman's Information Manual. Aviation Supplies and Academics, Seattle, WA, 1989.
• 3: [3] K. Benner. Using simulation techniques to analyze specifications. In Proceedings of the 5th KBSA Conference, pages 305-316, Syracuse, NY, 1990. Data Analysis Center for Software.
• 4: [4] A. Borgida, S. Greenspan, and J. Mylopoulos. Knowledge representation as the basis for requirements specifications. IEEE Computer, 18(4):82- 91, 1985.
• 5: [5] R.M. Burstall and J. Goguen. Putting theories together to make specifications. In Proceedings of the Fifth International Conference on Artificial Intelligence, pages 1045-1058, August 1977.
• 6: [6] D. Cohen. AP5 Manual. USC-Information Sciences Institute, June 1989. Draft.
• 7: Alan M. Davis, Software requirements: analysis and specification, Prentice Hall Press, Upper Saddle River, NJ, 1990
• 8: [8] S. Fickas. A knowledge-based approach to specification acquisition and construction. Technical Report 86-1, CS Dept., University of Oregon, Eugene, 1986.
• 9: [9] N.M. Goldman. Three dimensions of design development. In Proceedings, 3rd National Conference on Artificial Intelligence, Washington D.C., pages 130-133, August 1983.
• 10: C. Green , D. Luckham , R. Balzer , T. Cheatham , C. Rich, Report on a knowledge-based software assistant, Readings in artificial intelligence and software engineering, Morgan Kaufmann Publishers Inc., San Francisco, CA, 1986
• 11: [11] D. Harris and A. Czuchry. The knowledge-based requirements assistant. IEEE Expert, 3(4), 1988.
• 12: Karen Huff , Victor R. Lesser, The GRAPPLE Plan Formalism, University of Massachusetts, Amherst, MA, 1987
• 13: Valerio R. Hunt , Andres Zellweger, The FAA's Advanced Automation System: Strategies for Future Air Traffic Control Systems, Computer, v.20 n.2, p.19-32, February 1987 [doi>10.1109/MC.1987.1663475]
• 14: W. L. Johnson, Deriving specifications from requirements, Proceedings of the 10th international conference on Software engineering, p.428-438, April 11-15, 1988, Singapore
• 15: [15] W.L. Johnson. Specification as formalizing and transforming domain knowledge. In Proceedings of the AAAI Workshop on Automating Software Design, pages 48-55, St. Paul, MN, 1988.
• 16: [16] W.L. Johnson and K. Yue. An integrated specification development framework. Technical Report RS-88-215, USC / Information Sciences Institute, 1988.
• 17: [17] V.E. Kelly and U. Nonnenmann. Reducing the complexity of formal specification acquisition. In Proceedings of the AAAI-88 Workshop on Automating Software Design, pages 66-72, St. Paul, MN, 1988.
• 18: C. Niskier , T. Maibaum , D. Schwabe, A look through PRISMA: towards pluralistic knowledge-based environments for software specification acquisition, Proceedings of the 5th international workshop on Software specification and design, p.128-136, April 1989, Pittsburgh, Pennsylvania, United States
• 19: [19] The KBSA Project. Knowledge-based specification assistant; Final report. unpublished, 1988.
• 20: H. B. Reubenstein , R. C. Waters, The requirements apprentice: an initial scenario, Proceedings of the 5th international workshop on Software specification and design, p.211-218, April 1989, Pittsburgh, Pennsylvania, United States
• 21: Charles Rich , Richard C. Waters, The programmer's apprentice, ACM, New York, NY, 1990
• 22: W. N. Robinson, Integrating multiple specifications using domain goals, Proceedings of the 5th international workshop on Software specification and design, p.219-226, April 1989, Pittsburgh, Pennsylvania, United States
• 23: Guy L. Steele, Jr., The Definition and Implementation of a Computer Programming Language Based on Constraints, Massachusetts Institute of Technology, Cambridge, MA, 1980

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

General Terms:
Design, Languages