|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
 Digg  Furl  Spurl  Blink  Simpy  Google  Del.icio.us  Y!MyWeb | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Andrew J. Czuchry, Jr., David R. Harris, "KBRA: A New Paradigm for Requirements Engineering," IEEE Intelligent Systems, vol. 3, no. 4, pp. 21-24, 26-32, 34-35, Winter, 1988. | |||
| BibTex | x | ||
| @article{ 10.1109/64.10017, author = {Andrew J. Czuchry, Jr. and David R. Harris}, title = {KBRA: A New Paradigm for Requirements Engineering}, journal ={IEEE Intelligent Systems}, volume = {3}, number = {4}, issn = {0885-9000}, year = {1988}, pages = {21-24, 26-32, 34-35}, doi = {http://doi.ieeecomputersociety.org/10.1109/64.10017}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Intelligent Systems TI - KBRA: A New Paradigm for Requirements Engineering IS - 4 SN - 0885-9000 SP21 EP24, 26-32, 34-35 EPD - 21-24, 26-32, 34-35 A1 - Andrew J. Czuchry, Jr., A1 - David R. Harris, PY - 1988 VL - 3 JA - IEEE Intelligent Systems ER - | |||
The authors present a knowledge-based requirements assistant (KBRA) that is a component of the knowledge-based software assistant (KBSA). The idea behind KBSA is to create a knowledge-based life-cycle paradigm spanning software development from requirements to code and to formalize software practice so that computers can be used as active reasoning agents in developing software. The authors identify knowledge-representation issues associated with requirements acquisition and analysis, and note the three realms in which mechanisms operate to resolve knowledge issues: presentations, structured text, and evolving system description. They describe artificial intelligence techniques used to provide consistent reasoning processes for the intelligent assistant: inheritance of properties from generic object types, automatic classification based on discriminators indicating how to specialize instances, and constraint propagation for processing ramifications of requirements decisions and for supporting retraction when people change their minds.