Abstract
This paper describes efforts to develop a transformation-based software environment that 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 analysts 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.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
J.S. Anderson and S. Fickas, “A proposed perspective shift: Viewing specification design as a planning problem,” in Proc. 5th Int. Workshop Software Specification and Design, Pittsburgh, PA, pp. 177–184, Computer Society Press of the IEEE, May 1989.
ASA, Airman’s Information Manual. Aviation Supplies and Academics: Seattle, WA, 1989.
R. Balzer, D. Cohen, M.S. Feather, N.M. Goldman, W. Swartout, and D.S. Wile. “Operational specification as the basis for specifiction validation,” Theory and Practice of Software Technology, pp. 21–49. North-Holland: Amsterdam, 1983.
R. Balzer, C. Green, and T. Cheatham. “Software technology in the 1990s using a new paradigm,” IEEE Computer, vol. 16, no. 11, pp. 39–45, November 1983.
K. Benner, “Using simulation techniques to analyze specifications,” in Proc. 5th KBSA Conf., Syracuse, NY, pp. 305–316, 1990. Data Analysis Center for Software.
K. Benner and W.L. Johnson, “The use of scenarios for the development and validation of specifications,” in Proc. Comput. Aerospace VII Conf., Monterey, CA, 1989.
A. Borgida, S. Greenspan, and J. Mylopoulos. “Knowledge representation as the basis for requirements specifications,” IEEE Comput., vol. 18, no. 4, pp. 82–91, April 1985.
R.M. Burstall and J. Goguen. “Putting theories together to make specifications,” in Proc. 5th Int. Conf. Artificial Intell., Cambridge, MA, pp. 1045–1058, August 1977.
D. Cohen. Symbolic execution of the gist specification language,“ in Proc. 8th Int. Joint Conf. Artificial Intell., pp. 17–20, IJCAI, Karlsruhe, 1983.
D. Cohen. AP5 Manual. USC-Information Sciences Institute: Marina del Rey, CA, June 1989. Draft.
A.M. Davis. Software Requirements Analysis and Specification. Prentice-Hall: Englewood Cliffs, NJ, 1990.
M.S. Feather,“Constructing specifications by combining parallel elaborations,” IEEE Trans. Software Eng. vol. 15, no. 2, pp. 198–208, February 1989. Available as research report #RS-88–216 from ISI, 4676 Admiralty Way, Marina del Rey, CA 90292.
S. Fickas, “A knowledge-based approach to specification acquisition and construction,” Technical Report 86–1, Computer Science Dept., University of Oregon, Eugene, 1986.
N.M. Goldman, “Three dimensions of design development,” in Proc. 3rd Nat. Conf. Artificial Intell., Washington, DC, pp. 130–133, August 1983.
C. Green, D. Luckham, R. Balzer, T. Cheatham, and C. Rich. “Report on a knowledge-based software assistant,” Readings in Artificial Intelligence and Software Engineering, pp. 377–428, Morgan Kaufmann: Los Altos, CA, 1986.
J. Hagelstein, “Declarative approach to information system requirements,” J. Knowledge-Based Syst., vol. 1, no. 4, pp. 211–220, September 1988.
F.G. Halasz, T.P. Moran, and R.H. Trigg, “Notecards in a nutshell.” Technical Report, Xerox PARC, 1986.
D. Harel, H. Lachover, A. Naamad, A. Pnueli, M. Politi, R. Sherman, and A. Shtul-Trauring, “Statemate: A working environment for the development of complex reactive systems,” in Proc. 10th Int. Conf Software Eng., Singapore, pp. 396–406, 1988.
D. Harris and A. Czuchry, “The knowledge-based requirements assistant,” IEEE Expert, vol. 3, no. 4, 1988.
K.E. Huff and V.R. Lesser, “The GRAPPLE plan formalism,” Technical Report 87–08, University of Massachusetts, Department of Computer and Information Science, April 1987.
V. Hunt and A. Zellweger, “The FAA’s advanced automation system: Strategies for future air traffic control systems,” IEEE Comput. vol. 20, no. 2, pp. 19–32, February 1987.
W.L. Johnson, “Specification via scenarios and views,” in Proc. 3d Int. Software Process Workshop, Breckenridge, CO, pp. 61–63, 1986.
W.L. Johnson, “Deriving specifications from requirements,” in Proc. 10th Int. Conf. Software Eng., Singapore, pp. 428–437, 1988.
W.L. Johnson, “Specification as formalizing and transforming domain knowledge,” in Proc. AAAI Workshop on Automating Software Design, St. Paul, MN, pp. 48–55, 1988.
W.L. Johnson and M.S. Feather, “Using evolution transformations to construct specifications,” Automating Software Design. AAAI Press: Cambridge, MA, 1991, in press.
W.L. Johnson and K. Yue, “An integrated specification development framework,” Technical Report RS-88–215, University of Southern California, Information Sciences Institute, Marina del Rey, CA, 1988.
V.E. Kelly and U. Nonnenmann, Reducing the complexity of formal specification acquisition,“ in Proc. AAAI-88 Workshop on Automating Software Design, St. Paul, MN, pp. 66–72, 1988.
R. Mac Gregor. Loom Users Manual, USC/ISI, Marina del Rey, CA, 1989.
J.J. Myers and W.L. Johnson, “Towards specification explanation: Issues and lessons,” in Proc. 3d Knowledge-Based Software Assistant Conf., Rome, NY, pp. 251–269, 1988.
C. Niskier, T. Maibaum, and D. Schwabe, “A look through PRISMA: Towards pluralistic knowledge-based environments for software specification acquisition, ”in Proc. 5th Int. Workshop on Software Specification and Design, Pittsburgh, PA, pp. 128–136. Computer Society Press of the IEEE, May 1989.
The KBSA Project. Knowledge-based specification assistant: Final report. Unpublished, USC/ISI, Marina del Ray, CA, 1988.
. Refine User’s Guide, Reasoning Systems, Palo Alto, CA, 1986.
H.B. Rubenstein and R.C. Waters, “The requirements apprentice: An initial scenario,” in Proc. 5th Int. Workshop on Software Specification and Design, Pittsburgh, PA, May, pp. 211–218. Computer Society Press of the IEEE, 1989.
C. Rich, H.E. Schrobe, and R.C. Waters, “An overview of the programmer’s apprentice, in Proc. 6th Int. Joint Conf. Artificial Intell., Tokyo, pp. 827–828, 1979.
W.N. Robinson, “Integrating multiple specifications using domain goals,” in Proc. 5th Int. Workshop on Software Specification and Design, Pittsburgh, PA, May, pp. 219–226. Computer Society Press of the IEEE, 1989.
D.R. Smith, G.B. Kotik, and S.J. Westfold, “Research on knowledge-based software environments at Kestrel Institute,” IEEE Trans. Software Eng., vol. SE-11, no. 11, pp. 1278–1295, 1985.
G.L. Steele,Jr., “The definition and implementation of a computer programming language,” Technical Report 595, MIT Artificial Intelligence Laboratory, Cambridge, MA 1980.
W. Swartout, “Gist English generator,” in Proc. Nat. Conf. Artificial Intell., Pittsburgh, PA, pp. 404–409, AAAI, 1982.
R.C. Waters, “The programmer’s apprentice: A session with KBEmacs,” IEEE Trans. Software Eng., vol. SE-11, no. 11, pp. 1296–1320, November 1985.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 1991 Springer Science+Business Media New York
About this chapter
Cite this chapter
Johnson, W.L., Feather, M.S., Harris, D.R. (1991). Integrating Domain Knowledge, Requirements, and Specifications. In: Yeh, R.T. (eds) Case Technology. Springer, Boston, MA. https://doi.org/10.1007/978-1-4615-3644-4_3
Download citation
DOI: https://doi.org/10.1007/978-1-4615-3644-4_3
Received:
Revised:
Publisher Name: Springer, Boston, MA
Print ISBN: 978-1-4613-6621-8
Online ISBN: 978-1-4615-3644-4
eBook Packages: Springer Book Archive