Skip to main content
Log in

Supporting the reconciliation of models of object behaviour

  • Special section on OOIS 01
  • Published:
Software and Systems Modeling Aims and scope Submit manuscript

Abstract

This paper presents Reconciliation+, a method which identifies overlaps between models of software systems behaviour expressed as UML object interaction diagrams (i.e., sequence and/or collaboration diagrams), checks whether the overlapping elements of these models satisfy specific consistency rules and, in cases where they violate these rules, guides software designers in handling the detected inconsistencies. The method detects overlaps between object interaction diagrams by using a probabilistic message matching algorithm that has been developed for this purpose. The guidance to software designers on when to check for inconsistencies and how to deal with them is delivered by enacting a built-in process model that specifies the consistency rules that can be checked against overlapping models and different ways of handling violations of these rules. Reconciliation+ is supported by a toolkit. It has also been evaluated in a case study. This case study has produced positive results which are discussed in the paper.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Similar content being viewed by others

References

  1. Boehm B, In H (1996) Identifying Quality Requirements Conflicts. IEEE Software 25–35

  2. Cheung K, Chow K, Cheung T (1998) Consistency Analysis on Lifecycle Model and Interaction Model. Proc. of the 7th Int. Conference on Object-Oriented Information Systems, pp 427–441

  3. Easterbrook S (1991) Handling Conflict between Domain Descriptions with Computer-Supported Negotiation. Knowledge Acquisition 3:255–289

    Google Scholar 

  4. Emmerich W, Finkelstein F, Montangero C, Antonelli S, Armitage S (1999) Managing Standards Compliance. IEEE Transactions on Software Engineering 25(6):836–851

    Google Scholar 

  5. Finkelstein A, Gabbay D, Hunter A, Kramer J, Nuseibeh B (1994) Inconsistency Handling In Multi-Perspective Specifications. IEEE Transactions on Software Engineering 20(8):569–578

    Google Scholar 

  6. Glinz M (1995) An Integrated Formal Model of Scenarios Based on Statecharts. Proc. of the 5th European Software Engineering Conference, LNCS, vol 989. Springer-Verlag, pp 254–271

  7. Heimdahl MPE, Leveson N (1996) Completeness and Consistency in Hierarchical State-Based Requirements. IEEE Transactions in Software Engineering 22(6):363–377

    Google Scholar 

  8. Heitmeyer C, Jeffords R, Kiskis D (1996) Automated Consistency Checking Requirements Specifications. ACM Transactions on Software Engineering and Methodology 5(3):231–261

    Google Scholar 

  9. OMG (2003) Unified Modeling Language Specification (Action Semantics) – V. 1.5. Available from: http://www.omg.org/technology/documents/modeling_spec_catalog.htm

  10. Papadimitriou C, Steiglitz K (1982) Combinatorial Optimisation: Algorithms and Complexity. Prentice-Hall Inc

    Google Scholar 

  11. Pohl K (1996) Process-Centred Requirements Engineering. In: Kramer J (ed) Advanced Software Development Series. Research Studies Press Ltd., ISBN 0-86380-193-5, London

  12. Robinson W, Fickas S (1994) Supporting Multi-Perspective Requirements Engineering. Proc. of the IEEE Conference on Requirements Engineering. IEEE Computer Society Press, pp 206–215

  13. Si-Said S, Rolland C, Grosz G (1996) MENTOR: A Computer Aided Requirements Engineering Environment. Proc. of the 8th International Conference on Advanced Information Systems Engineering, pp 22–43

  14. Spanoudakis G, Constantopoulos P (1996) Elaborating Analogies from Conceptual Models. International Journal of Intelligent Systems 11(11):17–974

    Google Scholar 

  15. Spanoudakis G, Finkelstein A (1997) Reconciling requirements: a method for managing interference, inconsistency and conflict. Annals of Software Engineering, Special Issue on Software Requirements Engineering 3:459–475

    Google Scholar 

  16. Spanoudakis G, Zisman A (2001) Inconsistency Management in Software Engineering: Survey and Open Research Issues. In: Chang SK (ed) Handbook of Software Engineering and Knowledge Engineering. World Scientific Publishing Co, pp 329–380

  17. Lamsweerde A, Darimont R, Letier E (1998) Managing Conflicts in Goal-Driven Requirements Engineering. IEEE Transactions on Software Engineering 24(11):908–926

    Article  Google Scholar 

  18. Zisman A, Emmerich W, Finkelstein A (2000) Using XML to Specify Consistency Rules for Distributed Documents. Proc. of 10th Int. Workshop on Software Specification and Design

  19. Shafer G (1976) A Mathematical Theory of Evidence. Princeton University Press

  20. http://java.sun.com/j2se/1.3/docs/guide/awt/

  21. Spanoudakis G (2000) An Algorithm for Detecting Overlaps between Models of Object Interactions. Technical Report Series, TR-2000/03, ISSN 1364-4009, Department of Computing, City University

  22. http://www.rational.com/products/rose/index.jsp

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to George Spanoudakis.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Spanoudakis, G., Kim, H. Supporting the reconciliation of models of object behaviour. Softw Syst Model 3, 273–293 (2004). https://doi.org/10.1007/s10270-004-0054-1

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s10270-004-0054-1

Keywords

Navigation