Choosing an inappropriate notation for specifying software requirements is likely to compromise the effectiveness and efficiency with which the requirements process can be conducted. A proper choice of notation should ideally take into account both the characteristics of available notations and the many, and often conflicting requirements and constraints placed on notations by the circumstances of the project. This paper discusses the application of case-based reasoning technology to the problem of choosing notations. Our aim is to provide a decision-support tool for managers of the requirements process which will facilitate choices about notations by exploiting knowledge about both project development contexts and the notations themselves.
|Name||UH Computer Science Technical Report|
|Publisher||University of Hertfordshire|
- requirements specification
- case-based reasoning
- project context