Integrating domain knowledge, requirements, and specifications

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.

[1]  S. Fickas,et al.  A proposed perspective shift: viewing specification design as a planning problem , 1989, IWSSD '89.

[2]  W. Lewis Johnson.  Deriving specification from requirements , 1988, Proceedings. [1989] 11th International Conference on Software Engineering.

[3]  Amnon Naamad,et al.  Statemate: a working environment for the development of complex reactive systems , 1988, ICSE '88.

[4]  W. N. Robinson,et al.  Integrating multiple specifications using domain goals , 1989, IWSSD '89.

[5]  Victor Lesser,et al.  The GRAPPLE Plan Formalism , 1987 .

[6]  Andres Zellweger,et al.  The FAA's Advanced Automation System: Strategies for Future Air Traffic Control Systems , 1987, Computer.

[7]  Robert Balzer,et al.  Report on a knowledge-based software assistant , 1986 .

[8]  Alan M. Davis,et al.  Software requirements - analysis and specification , 1990 .

[9]  Neil M. Goldman.  Three Dimensions of Design Development , 1983, AAAI.

[10]  William R. Swartout,et al.  GIST English Generator , 1982, AAAI.

[11]  Donald Cohen.  Symbolic Execution of the Gist Specification Language , 1983, IJCAI.

[12]  W. Lewis Johnson.  Specification via scenarios and views , 1986, ISPW.

[13]  Michael R. Lowry,et al.  Automating software design , 1989, Digest of Papers. COMPCON Spring 89. Thirty-Fourth IEEE Computer Society International Conference: Intellectual Leverage.

[14]  John Mylopoulos,et al.  Knowledge Representation as the Basis for Requirements Specifications , 1985, Computer.

[15]  R. C. Waters,et al.  The requirements apprentice: an initial scenario , 1989, IWSSD '89.

[16]  Richard C. Waters.  The Programmer's Apprentice: A Session with KBEmacs , 1985, IEEE Transactions on Software Engineering.

[17]  Randall H. Trigg,et al.  Notecards in a nutshell , 1986, CHI '87.

[18]  Mehdi T. Harandi,et al.  Workshop on software specification and design , 1988, SOEN.

[19]  Thomas E. Cheatham,et al.  Software Technology in the 1990's: Using a New Paradigm , 1983, Computer.

[20]  Karen Henniger.  Data & Analysis Center for Software. , 1986 .

[21]  A. Pnueli,et al.  STATEMATE: a working environment for the development of complex reactive systems , 1988, Proceedings. [1989] 11th International Conference on Software Engineering.

[22]  Jie Lu,et al.  Declarative approach to information systems requirements , 1988 .

[23]  Richard C. Waters,et al.  Readings in artificial intelligence and software engineering , 1986 .

[24]  Douglas R. Smith,et al.  Research on Knowledge-Based Software Environments at Kestrel Institute , 1985, IEEE Transactions on Software Engineering.

[25]  Martin S. Feather.  Constructing Specifications by Combining Parallel Elaborations , 1989, IEEE Trans. Software Eng..

[26]  Robert Balzer,et al.  Kestrel Institute: REPORT ON A KNOWLEDGE-BASED SOFTWARE ASSISTANT , 1986 .

[27]  D. Schwabe,et al.  A look through PRISMA: towards pluralistic knowledge-based environments for software specification acquisition , 1989, IWSSD '89.

[28]  Richard C. Waters,et al.  Overview of the Programmer's Apprentice , 1979, IJCAI.

[29]  W. Lewis Johnson,et al.  The Use of Scenarios for the Development and Validation of Specifications , 1989 .

[30]  Joseph A. Goguen,et al.  Putting Theories Together to Make Specifications , 1977, IJCAI.