Programming expert systems in OPS5: an introduction to rule-based programming
Programming expert systems in OPS5: an introduction to rule-based programming
Report on a knowledge-based software assistant
Readings in artificial intelligence and software engineering
The Requirements Apprentice: Automated Assistance for Requirements Acquisition
IEEE Transactions on Software Engineering
Software requirements: objects, functions, and states
Software requirements: objects, functions, and states
Object-oriented analysis (2nd ed.)
Object-oriented analysis (2nd ed.)
Representation and Presentation of Requirements Knowledge
IEEE Transactions on Software Engineering
Methodology integration: evolution of information engineering
Information and Software Technology - Special issue on CASE (computer-aided software engineering)
Introduction to Expert Systems
Introduction to Expert Systems
Building Large Knowledge-Based Systems; Representation and Inference in the Cyc Project
Building Large Knowledge-Based Systems; Representation and Inference in the Cyc Project
KBRA: A New Paradigm for Requirements Engineering
IEEE Expert: Intelligent Systems and Their Applications
Developing Formal Specifications from Informal Requirements
IEEE Expert: Intelligent Systems and Their Applications
CommonKADS: A Comprehensive Methodology for KBS Development
IEEE Expert: Intelligent Systems and Their Applications
Object-oriented design of ISDN call-processing software
IEEE Communications Magazine
A context-based enterprise ontology
BIS'07 Proceedings of the 10th international conference on Business information systems
| Hi-index | 0.07 |
A methodology ontology is proposed to help requirement analysis. It helps the software engineer to generate methodical knowledge for requirement analysis (RA). It includes a method library and a set of modeling support entities. The method library contains method templates and components, e.g., primitive methods, inference functions, inference structures, domain models, and a domain ontology. The modeling support entities use the library to construct the desired methodical knowledge. An example is given showing how this approach constructs an object-oriented RA method. Thus generated methodical knowledge can be further coupled with domain knowledge to form a domain-specific RA tool, which relieves the software engineer of selecting and applying a distinct RA tool for a domain. This approach allows ready enhancement, since it is designed as an open architecture, which helps us to evolve it to assimilate new software methodology.