|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| W. Lewis Johnson, Kevin M. Benner, David R. Harris, "Developing Formal Specifications from Informal Requirements," IEEE Intelligent Systems, vol. 8, no. 4, pp. 82-90, August, 1993. | |||
| BibTex | x | ||
| @article{ 10.1109/64.223994, author = {W. Lewis Johnson and Kevin M. Benner and David R. Harris}, title = {Developing Formal Specifications from Informal Requirements}, journal ={IEEE Intelligent Systems}, volume = {8}, number = {4}, issn = {0885-9000}, year = {1993}, pages = {82-90}, doi = {http://doi.ieeecomputersociety.org/10.1109/64.223994}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Intelligent Systems TI - Developing Formal Specifications from Informal Requirements IS - 4 SN - 0885-9000 SP82 EP90 EPD - 82-90 A1 - W. Lewis Johnson, A1 - Kevin M. Benner, A1 - David R. Harris, PY - 1993 VL - 8 JA - IEEE Intelligent Systems ER - | |||
The Aries environment, which solves many of the challenges of applying knowledge-based methods to the development of software requirements and specifications, is described. Using Aries, analysts can develop detailed, precise, validated system specifications without getting bogged down in mundane details. They can also avoid considerable formal syntax and compose solutions in an order-independent way. Aries modularized central knowledge base uses a common underlying representation, enabling analysts to reuse and share various types of knowledge. Its presentation facility lets analysts encode and view a system description using various notations, and focus on specific aspects of the system being described. Its analysis tools help validate even incomplete system descriptions, and a library of transformations lets analysts elaborate and modify system descriptions without introducing inadvertent errors.

