Object-oriented software engineering
Object-oriented software engineering
Guiding the construction of textual use case specifications
Data & Knowledge Engineering - Special jubilee issue: DKE 25
Use case driven object modeling with UML: a practical approach
Use case driven object modeling with UML: a practical approach
Requirements engineering: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Requirements engineering in the year 00: a research perspective
Proceedings of the 22nd international conference on Software engineering
Automatic labeling of semantic roles
Computational Linguistics
Developing Sequence Diagrams in UML
ER '01 Proceedings of the 20th International Conference on Conceptual Modeling: Conceptual Modeling
Guiding Use Case Authoring: Results of an Empirical Study
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
A UML-Based Pattern Specification Technique
IEEE Transactions on Software Engineering
A specification pattern for use cases
Information and Management
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition)
Interaction transformation patterns based on semantic roles
NLDB'05 Proceedings of the 10th international conference on Natural Language Processing and Information Systems
Integrating natural language techniques in OO-Method
CICLing'05 Proceedings of the 6th international conference on Computational Linguistics and Intelligent Text Processing
Hi-index | 0.00 |
Many object-oriented development approaches specify the system functional requirements by means of use cases. During the requirements analysis, these approaches generally agree on expressing the system behaviour using two representations: the Object Model and the Interaction Model. The Interaction Model development is subordinated to the Object Model construction, which provides the former with the basic information of the object classes. The Interaction Model contributes to identifying the class operations. Although these models are closely linked and their development is supposed to be iterative, in practice, there are no established mechanisms that guarantee the consistency of both models throughout their construction. The Interaction Model information is also under-used or underestimated in the Object Model. Persistent connections between the analysis models and the Use Case Model are not recognized. A framework to simultaneously construct the Object Model and the Interaction Model from use cases is described in this paper. Its main purpose is to strengthen the information exchange between the models so that it is complementary and consistent. To fulfil this purpose, the framework is centered on a transformation model based on linguistic patterns.