Software requirements: objects, functions, and states
Software requirements: objects, functions, and states
Object-oriented methods (UML ed., 2nd ed.): a foundation
Object-oriented methods (UML ed., 2nd ed.): a foundation
Objects, components, and frameworks with UML: the catalysis approach
Objects, components, and frameworks with UML: the catalysis approach
A survey of structured and object-oriented software specification methods and techniques
ACM Computing Surveys (CSUR)
A language facility for designing database-intensive applications
ACM Transactions on Database Systems (TODS)
Computer
On the Frame Problem in Procedure Specifications
IEEE Transactions on Software Engineering
Understanding Redundancy in UML Models for Object-Oriented Analysis
CAiSE '02 Proceedings of the 14th International Conference on Advanced Information Systems Engineering
The Object Constraint Language: Getting Your Models Ready for MDA
The Object Constraint Language: Getting Your Models Ready for MDA
Unified Modeling Language Reference Manual, The (2nd Edition)
Unified Modeling Language Reference Manual, The (2nd Edition)
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition)
Software Engineering: A Practitioner's Approach
Software Engineering: A Practitioner's Approach
Reasoning on UML Conceptual Schemas with Operations
CAiSE '09 Proceedings of the 21st International Conference on Advanced Information Systems Engineering
From declarative to imperative UML/OCL operation specifications
ER'07 Proceedings of the 26th international conference on Conceptual modeling
Deriving operation contracts from UML class diagrams
MODELS'07 Proceedings of the 10th international conference on Model Driven Engineering Languages and Systems
| Hi-index | 0.00 |
This paper describes two different ways of understanding operation contracts in conceptual modeling: the strict and extended interpretations. The main difference between them lies in the way operation postconditions and integrity constraints are guaranteed, which has an impact on the desirable properties of operation contracts according to recommended good practice for requirements specification. Both interpretations are formalized and compared in terms of these properties. We find that the strict interpretation provides several advantages over the extended one. This conclusion is supported by evidence from a case study. The results of the case study also indicate that the strict interpretation significantly facilitates the specification task.