A Metamodel for Enabling a Service Oriented Architecture

Abstract

Abstract. Process modelling initiatives generally develop their process models without much emphasis on data, burying their sequence of operations as a thread within a non-elementary process. More often than not, these buried operations are elementary atomic reusable components. The resulting models are generally not flexible or sufficiently reusable, suffering from update anomalies and redundancies. Addressing "service" as a major deliverable component, an ORM metamodel was developed in line with ISO 19763-5 Metamodel Framework for Interoperability: Metamodel for Process Model Registration, to harmonize atomic component processes using a control sequence and event models to enable the delivery of a totally flexible model set facilitating metamodel interoperability and cooperation between systems via their respective models. The paper provides a limited ORM based review of ISO 19763-5, and uses underlying component processes to develop a metamodel for a deliverable Services Oriented Architecture containing control sequence models, event models, and bridges to associated data models or web services.

The Systematic Discovery of Services in Early Stages of Agile Developments: A Systematic Literature Review

“…Title Q1 Q2 Q3 [22] "Development of service-oriented architectures using model-driven development: A mapping study" Yes P No [23] "MISS: A Metamodel of Information System Service" P Yes No [24] "S3: A Service-Oriented Reference Architecture" Yes No No [25] "A metamodel for the Web Services Standars Yes Yes No [26] "A platform independent model for service oriented architectures" Yes Yes P [27] "A Review and Comparison of Service E-Contract Architecture Metamodels" Yes Yes No [28] "AIRES: An Architecture to Improve Software Reuse" Yes No No [29] "Method Engineering: A Service-Oriented Approach" Yes No No [30] "Service portfolio management: A repository-based framework" Yes P Yes [31] "Design of a Model-generated Repository as a Service for USDL" P P No [32] "Model-driven development of SOA services" P Yes P [33] "Scaling for agility: A reference model for hybrid traditional-agile software development methodologies" Yes P No [34] "Agent-based Extensions for the UML Profile and Metamodel for Service-oriented Architectures" Yes Yes No [35] "Composite service metamodel and auto composition" Yes Yes No [36] "A Generic Metamodel for Adaptable Service Oriented Systems Modeling using DSM Approach" Yes Yes P [37] "Foundations of a Reference Model for SOA Governance" No P No [38] "A metamodel and taxonomy to facilitate context-aware service adaptation" Yes Yes No [39] "A Metamodel for Enabling a Service Oriented Architecture" Yes Yes No [40] "An EA-approach to Develop SOA Viewpoints" Yes Yes Yes [41] "Towards services paradigm: principles and models" Yes P No [42] "A Simplified Approach to Describing, Discovering and Composing Situational Enterprise Services" Yes P No…”

Object-Role Modeling

“…Fact-oriented modeling has been used productively in industry for over three decades, with many case studies attesting to its practical benefits for information systems engineering in a variety of areas, including service oriented architecture (Piprani, Wang, & He, 2008), data warehousing (Hansen & dela Cruz, 2006), data quality (Piprani & Ernst, 2008), and decision support (Piersen & dela Cruz, 2005). Apart from its use in model driven engineering, fact-orientation is well suited for requirements analysis (Evans, 2005; as well as business rules and regulations modeling.…”