Object-oriented software engineering
Object-oriented software engineering
ACL '85 Proceedings of the 23rd annual meeting on Association for Computational Linguistics
Ad-Hoc and personal ontologies: a prototyping approach to ontology engineering
PKAW'06 Proceedings of the 9th Pacific Rim Knowledge Acquisition international conference on Advances in Knowledge Acquisition and Management
Hi-index | 0.00 |
In requirements engineering use cases are employed to describe the flow of events and the occurrence of states in a future information system. Use cases consist of a set of scenarios each of them describing an exemplary behaviour of the system to be developed. Different stakeholders describe the steps in varying ways since they perceive the state of affairs in the application domain from different viewpoints. This results in ambiguous use cases written in natural language that use different terminology and are therefore difficult to reconcile. To solve this problem, we have developed a set of simple guidelines to rewrite use cases and scenarios in a controlled language. The sentences are translated into flat logical forms by the Prolog module of our RECOCASE system. These resulting flat logical forms are used by RECOCASE to generate graphical models for the elaboration and refinement of functional requirements between project stakeholders. As an experiment we have chosen Formal Concept Analysis to automatically represent the viewpoints of different stakeholders graphically in a concept lattice.