A Rigorous Approach to Relate Enterprise and Computational Viewpoints

Multiviewpoint approaches allow stakeholders to design a system from stakeholder-specific viewpoints. By this, a separation of concerns is achieved, which makes designs more manageable. However, to construct a consistent multiviewpoint design, the relations between viewpoints must be defined precisely, so that the consistency of designs from these viewpoints can be verified. The goal of this paper is to make the consistency rules between (a slightly adapted version of) the RM-ODP enterprise and computational viewpoints more precise and to make checking the consistency between these viewpoints practically applicable. To achieve this goal, we apply a generic framework for relating viewpoints that includes reusable consistency rules. We implemented the consistency rules in a tool to show their applicability

Consistency in Multi-Viewpoint Architectural Design of Enterprise Information Systems

Different stakeholders in the design of an enterprise information system have their own view on that design. To help produce a coherent design this paper presents a framework that aids in specifying relations between such views. To help produce a consistent design the framework also aids in specifying consistency rules that apply to the view relations and in checking the consistency according to those rules. The framework focuses on the higher levels of abstraction in a design, we refer to design at those levels of abstraction as architectural design. The highest level of abstraction that we consider is that of business process design and the lowest level is that of software component design. The contribution of our framework is that it provides a collection of basic concepts that is common to viewpoints in the area of enterprise information systems. These basic concepts aid in relating viewpoints by providing: (i) a common terminology that helps stakeholders to understand each others concepts; and (ii) a basis for defining re-usable consistency rules. In particular we define re-usable rules to check consistency between behavioural views that overlap or are a refinement of each other. We also present an architecture for a tool suite that supports our framework. We show that our framework can be applied, by performing a case study in which we specify the relations and consistency rules between the RM-ODP enterprise, computational and information viewpoints

Tele-education Process Modelling supported by the ODP Enterprise Viewpoint Language

This paper reports on applying the ODP enterprise viewpoint in the domain of tele-education. The work is conducted as part of a research activity that aims at designing a tele-education system to support planning, execution and evaluation of dynamic distributed educational processes. We explore the ODP enterprise viewpoint as a basis for communication and co-operation between educational scientists and ODP systems designers involved in the design process. Our application of the enterprise viewpoint involves four main steps. First, an educational language is proposed to describe educational processes in generic terms. Second, a set of appropriate enterprise language concepts is selected. Third, a relationship is established between the educational language and enterprise language concepts. Fourth, an educational process is modelled in terms of an entity-oriented model and a behaviour-oriented model. It is hoped that the experience gained in this exercise will provide useful feedback to both the educational and ODP communitie

Semantic verification of Behavior Conformance

This paper introduces a formal yet practical method to verify whether the behavior design of a distributed application conforms to the behavior design of the enterprise in which the application is embedded. The method allows both enterprise architects and application architects to talk about designs in their own terms, and introduces a common set of terms as the linking pin between enterprise and application designs. The formal semantics of these common terms allows us to verify the conformance between an enterprise and its applications formally and automatically

On the Notion of Abstract Platform in MDA Development

Although platform-independence is a central property in MDA models, the study of platform-independence has been largely overlooked in MDA. As a consequence, there is a lack of guidelines to select abstraction criteria and modelling concepts for platform-independent design. In addition, there is little methodological support to distinguish between platform-independent and platform-specific concerns, which could be detrimental to the beneficial exploitation of the PIM-PSM separation-of-concerns adopted by MDA. This work is an attempt towards clarifying the notion of platform-independent modelling in MDA development. We argue that each level of platform-independence must be accompanied by the identification of an abstract platform. An abstract platform is determined by the platform characteristics that are relevant for applications at a certain level of platform-independence, and must be established by balancing various design goals. We present some methodological principles for abstract platform design, which forms a basis for defining requirements for design languages intended to support platform-independent design. Since our methodological framework is based on the notion of abstract platform, we pay particular attention to the definition of abstract platforms and the language requirements to specify abstract platforms. We discuss how the concept of abstract platform relates to UML

Multi-perspective requirements engineering for networked business systems: a framework for pattern composition

How business and software analysts explore, document, and negotiate requirements for enterprise systems is critical to the benefits their organizations will eventually derive. In this paper, we present a framework for analysis and redesign of networked business systems. It is based on libraries of patterns which are derived from existing Internet businesses. The framework includes three perspectives: Economic value, Business processes, and Application communication, each of which applies a goal-oriented method to compose patterns. By means of consistency relationships between perspectives, we demonstrate the usefulness of the patterns as a light-weight approach to exploration of business ideas

An integrated component-oriented framework for effective and flexible enterprise distributed systems development

Although component-based platforms and technologies such as CORBA, COM+/.NET and Enterprise Java Beans (EJB) are now widely used for implementation and deployment of complex systems, the component way of thinking is still immature. Current CBD best practices, concepts, approaches and methods do not provide a full and consistent support for various component concepts, and therefore are not able to provide a full benefit of the CBD paradigm. This paper defines a new approach to components through an Integrated Component- Oriented Framework that provides a comprehensive component-oriented support for enterprise systems development. The framework enables that the same component way of thinking and the same consistent set of technology- independent component concepts can be applied in different aspects of enterprise systems development, from business services to distributed components

An Analysis of the OSI Systems Management Architecture from an ODP Perspective

This paper analyses the OSI Systems Management Architecture (SMA) in terms of the RM-ODP concepts and architecture. It explains why ISO and ITU are considering new modelling techniques for implementing distributed systems management. In the information viewpoint, these new techniques might be inspired from GDMO. The paper also examines the use of automatic translation tools (GDMO to CORBA IDL translators) to integrate existing management agents within the future Open Distributed Management Architecture (ODMA)