Generating Domain-Specific Methodical Knowledge for Requirement Analysis Based on Methodology Ontology

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.

[1]  Jeffrey J. P. Tsai.  A Knowledge-Based Approach to Software Design , 1988 .

[2]  K. W. Short,et al.  Methodology integration: evolution of information engineering , 1991 .

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

[4]  Riichiro Mizoguchi,et al.  Task analysis interview based on task ontology , 1995 .

[5]  W. Guenther,et al.  Object-oriented design of ISDN call-processing software , 1993, IEEE Communications Magazine.

[6]  Bob J. Wielinga,et al.  CommonKADS: a comprehensive methodology for KBS development , 1994, IEEE Expert.

[7]  Gary S. Kahn,et al.  The Mud System , 1986, IEEE Expert.

[8]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[9]  M.J. Bickerton,et al.  The classification of requirements engineering methods , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[10]  Edward Yourdon,et al.  Object-oriented analysis , 2012 .

[11]  Neil A. M. Maiden,et al.  ACRE: selecting methods for requirements acquisition , 1996, Softw. Eng. J..

[12]  Guus Schreiber,et al.  KADS : a principled approach to knowledge-based system development , 1993 .

[13]  Richard C. Waters,et al.  The Requirements Apprentice: Automated Assistance for Requirements Acquisition , 1991, IEEE Trans. Software Eng..

[14]  Nancy Martin,et al.  Programming Expert Systems in OPS5 - An Introduction to Rule-Based Programming(1) , 1985, Int. CMG Conference.

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

[16]  Vijayan Sugumaran,et al.  A Knowledge-Based Software Engineering Environment for Reusable Software Requirements and Architectures , 1996 .

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

[18]  B. Chandrasekaran,et al.  Generic Tasks in Knowledge-Based Reasoning: High-Level Building Blocks for Expert System Design , 1986, IEEE Expert.

[19]  Jeffrey J. P. Tsai,et al.  Kb/RMS: an Intelligent Assistant for Requirement Definition , 1992, Int. J. Artif. Intell. Tools.

[20]  David R. Harris,et al.  KBRA: A new paradigm for requirements engineering , 1988, IEEE Expert.

[21]  Peter Jackson,et al.  Introduction to expert systems , 1986 .

[22]  Martin S. Feather,et al.  Representation and Presentation of Requirements Knowledge , 1992, IEEE Trans. Software Eng..

[23]  Ramanathan V. Guha,et al.  Building Large Knowledge-Based Systems: Representation and Inference in the Cyc Project , 1990 .

[24]  Chris F. Kemerer,et al.  Object-oriented and conventional analysis and design methodologies , 1992, Computer.

[25]  Edward Yourdon,et al.  Object-oriented analysis (2nd ed.) , 1991 .

[26]  W. Lewis Johnson,et al.  Developing formal specifications from informal requirements , 1993, IEEE Expert.