Skip to main content
Article thumbnail
Location of Repository

Supporting the reconciliation of models of object behaviour

By George Spanoudakis and Hyoseob Kim

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

Topics: G400 Computer Science
Publisher: Springer
Year: 2004
DOI identifier: 10.1007/s10270-004-0054-1
OAI identifier: oai:eprints.lincoln.ac.uk:41

Suggested articles

Citations

  1. (1976). A Mathematical Theory of Evidence, doi
  2. (2000). An Algorithm for Detecting Overlaps between Models of Object Interactions,
  3. (1995). An Integrated Formal Model of Scenarios Based on Statecharts, doi
  4. (1996). Automated Consistency Checking Requirements Specifications, doi
  5. (1982). Combinatorial Optimisation: Algorithms and Complexity, doi
  6. (1996). Completeness and Consistency in Hierarchical State-Based Requirements, doi
  7. (1998). Consistency Analysis on Lifecycle Model and Interaction Model, doi
  8. (1996). Elaborating Analogies from Conceptual Models, doi
  9. (2000). Finkelstein A doi
  10. (1991). Handling Conflict between Domain Descriptions with doi
  11. (1996). Identifying Quality Requirements Conflicts, doi
  12. (1994). Inconsistency Handling In MultiPerspective Specifications, doi
  13. (1998). Managing Conflicts in Goal-Driven Requirements Engineering, doi
  14. (1996). MENTOR: A Computer Aided Requirements Engineering Environment, doi
  15. Modeling Language Specification (Action Semantics) - doi
  16. (1997). Reconciling requirements: a method for managing interference, inconsistency and conflict,
  17. (1994). Supporting Multi-Perspective Requirements Engineering, doi

To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.