The FAA's Advanced Automation System: Strategies for Future Air Traffic Control Systems
Computer - The FAA's Advanced Automation Program
Report on a knowledge-based software assistant
Readings in artificial intelligence and software engineering
Deriving specifications from requirements
ICSE '88 Proceedings of the 10th international conference on Software engineering
IWSSD '89 Proceedings of the 5th international workshop on Software specification and design
A proposed perspective shift: viewing specification design as a planning problem
IWSSD '89 Proceedings of the 5th international workshop on Software specification and design
The requirements apprentice: an initial scenario
IWSSD '89 Proceedings of the 5th international workshop on Software specification and design
Integrating multiple specifications using domain goals
IWSSD '89 Proceedings of the 5th international workshop on Software specification and design
Software requirements: analysis and specification
Software requirements: analysis and specification
The programmer's apprentice
The Definition and Implementation of a Computer Programming Language Based on Constraints
The Definition and Implementation of a Computer Programming Language Based on Constraints
The GRAPPLE Plan Formalism
An approach to the classification of domain models in support of analogical reuse
SSR '95 Proceedings of the 1995 Symposium on Software reusability
| Hi-index | 0.00 |
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.