Viewpoint consistency in ODP

Boiten, Eerke Albert; Bowman, Howard; Derrick, John; Linington, Peter F.; Steen, Maarten

doi:10.1016/s1389-1286(00)00114-6

Cited by 40 publications

(33 citation statements)

References 58 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…View-based process modelling has its roots in Software Engineering techniques to design a system using viewpoints, see [35,36,37,38,39,40]. Viewpoints capture different aspects of a system and, therefore, may serve different purposes.…”

Section: View-based Process Modellingmentioning

confidence: 99%

Propagating changes between aligned process models

Weidlich

Mendling

Weske

2012

Journal of Systems and Software

View full text Add to dashboard Cite

There is a wide variety of drivers for business process modelling initiatives, reaching from organisational redesign to the development of information systems. Consequently, a common business process is often captured in multiple models that overlap in content due to serving different purposes. Business process management aims at flexible adaptation to changing business needs. Hence, changes of business processes occur frequently and have to be incorporated in the respective process models. Once a process model is changed, related process models have to be updated accordingly, despite the fact that those process models may only be loosely coupled. In this article, we introduce an approach that supports change propagation between related process models. Given a change in one process model, we leverage the behavioural abstraction of behavioural profiles for corresponding activities in order to determine a change region in another model. Our approach is able to cope with changes in pairs of models that are not related by hierarchical refinement and show behavioural inconsistencies. We evaluate the applicability of our approach with two real-world process model collections. To this end, we either deduce change operations from different model revisions or rely on synthetic change operations.

show abstract

Section: View-based Process Modellingmentioning

confidence: 99%

Propagating changes between aligned process models

Weidlich

Mendling

Weske

2012

Journal of Systems and Software

View full text Add to dashboard Cite

show abstract

“…In some approaches such as the OpenViews framework [19], two views are consistent if a design can be found that is a refinement of both views. Other approaches, such as Viewpoints [20], consistency requirements are defined in terms of rules, which are specified as queries on the database that contains the viewpoints.…”

Section: Viewpoint Integration and Consistencymentioning

confidence: 99%

Behavior, Time and Viewpoint Consistency: Three Challenges for MDE

Rivera

Romero

Vallecillo

2009

Models in Software Engineering

View full text Add to dashboard Cite

Abstract. Although Model Driven Software Development (MDSD) is achieving significant progress, it is still far from becoming a real Engineering discipline. In fact, many of the difficult problems of the engineering of complex software systems are still unresolved, or simplistically addressed by many of the current MDSD approaches. In this position paper we outline three of the outstanding problems that we think MDSD should tackle in order to be useful in industrial environments.

show abstract

“…[4,5,9,10,17,24], highlight the need to explicitly define and establish these correspondences but do not represent them as independent entities. Rather, they form part of the logical framework they define for checking the consistency of viewpoint specifications.…”

Section: Expressing Correspondences: Related Workmentioning

confidence: 99%

“…Following this standard, current architectural practices for designing open distributed systems define several distinct viewpoints. Examples include the viewpoints described in the "4+1" view model [16], Viewpoints [9], OpenViews [4], Dijkman's framework [5], or the growing plethora of Enterprise Architectural Frameworks (EAF): the Zachman's framework [26], ArchiMate [17], the US Department of Defense Architectural Framework (DoDAF), The Open Group Architectural Framework (TOGAF), the Federal Enterprise Architecture Framework (FEAF), or the Reference Model of Open Distributed Processing (RM-ODP), among others. In particular, the RM-ODP provides five generic and complementary viewpoints on the system and its environment [12].…”

Section: Introductionmentioning

confidence: 99%