Problems and Deficiencies of UML as a Requirements Specification Language
IWSSD '00 Proceedings of the 10th International Workshop on Software Specification and Design
Event-Based Traceability for Managing Evolutionary Change
IEEE Transactions on Software Engineering
Specification and checking of dependency relations between UML models
UML and the unified process
A Petri Net Based Method for Refining Object Oriented System Specifications
Electronic Notes in Theoretical Computer Science (ENTCS)
Requirements Modeling and Validation Using Bi-layer Use Case Descriptions
MoDELS '08 Proceedings of the 11th international conference on Model Driven Engineering Languages and Systems
IEICE - Transactions on Information and Systems
Integrated System Analysis Environment for the Continuous Consistency and Completeness Checking
Proceedings of the 2006 conference on Knowledge-Based Software Engineering: Proceedings of the Seventh Joint Conference on Knowledge-Based Software Engineering
A rule-based system for assessing consistency between UML models
MICAI'07 Proceedings of the artificial intelligence 6th Mexican international conference on Advances in artificial intelligence
Tool support for essential use cases to better capture software requirements
Proceedings of the IEEE/ACM international conference on Automated software engineering
An approach to test-driven development of conceptual schemas
Data & Knowledge Engineering
| Hi-index | 0.00 |
Today, object-oriented requirements specifications typically combine a scenario (or use case) model and a class model for expressing functional requirements. With any such combination, the problem of consistency between these two models arises. In this paper, we present a lightweight approach to consistency between a scenario model and a class model. We assume semi-formal, loosely coupled models that are complementary: scenarios model the external system behavior; the class model specifies the internal, state-dependent functionality that cannot be expressed easily in a scenario (but is required to specify external behavior properly). We achieve consistency by minimizing overlap between the two models and by systematically cross-referencing corresponding information. We give a set of rules that can be used both for developing a consistent specification and for checking the consistency of a completed specification. Some rules can be checked automatically, the others are rules for manual inspection.