B. Elvesæter and A.-J. Berre, "OMG Specifications for Enterprise Interoperability", paper presentation at IESA 2010 Workshop “Standards - a foundation for Interoperability”, Coventry, United Kingdom, 13 April 2010.
The document provides an overview of the Object Management Group (OMG) and some of the standards they have developed, including the Unified Modeling Language (UML) and Model Driven Architecture (MDA). It discusses the history and goals of OMG, key OMG standards like UML, MOF, CWM and CORBA, and how MDA uses these standards to separate application logic from implementation details. The document also summarizes some of the benefits of using MDA such as increased portability and integration across platforms.
Unified Component Model for Distributed, Real- Time and Embedded Systems Requ...Remedy IT
The objective of this RFP is to solicit proposals for a new component model called the “Unified Component Model” targeting Distributed, Real-Time and Embedded (DRTE) Systems. A component model defines a set of standards for component implementation, naming, interoperability, customization, composition, evolution, and deployment.
The UCM will be a simple, lightweight, middleware-agnostic, and flexible component model. The UCM will allow many different interaction models, including publish-subscribe and request-reply.
This document discusses the use of Model-Driven Architecture (MDA) and model transformations in software product lines (SPL). It begins by introducing SPLs and MDA. SPLs aim to increase productivity by leveraging commonalities between related products. MDA uses platform-independent and platform-specific models with transformations between them. The document then explores combining MDA and SPL approaches through the Modden framework and Baseline-Oriented Modeling. Modden develops reusable core assets through domain and application engineering processes with MDA. Baseline-Oriented Modeling produces expert systems as PRISMA architectural models from SPLs using MDA.
This document outlines the M3 modeling methodology, which provides a framework for developing and maintaining enterprise architecture models. The methodology uses the Unified Modeling Language (UML) and is based on the principles of Model Driven Architecture (MDA). Models are created at three levels - computation independent model (CIM), platform independent model (PIM), and platform specific model (PSM). Integration specific models (ISM) are also used to model different integration viewpoints. The methodology utilizes IBM Rational tools like RSA, RTC and RAM to support the modeling lifecycle.
Evolution of Modelling Techniques for Service Oriented ArchitectureIJERA Editor
Service-oriented architecture (SOA) is a software design and architecture design pattern based on independent pieces of software providing functionality as services to other applications. The benefit of SOA in the IT infrastructure is to allow parallel use and data exchange between programs which are services to the enterprise. Unified Modelling Language (UML) is a standardized general-purpose modelling language in the field of software engineering. The UML includes a set of graphic notation techniques to create visual models of object-oriented software systems. We want to make UML available for SOA as well. SoaML (Service oriented architecture Modelling Language) is an open source specification project from the Object Management Group (OMG), describing a UML profile and meta-model for the modelling and design of services within a service-oriented architecture. BPMN was also extended for SOA but there were few pitfalls. There is a need of a modelling framework which dedicated to SOA. Michael Bell authored a framework called Service Oriented Modelling Framework (SOMF) which is dedicated for SOA.
Process driven software development methodology for enterprise information sy...csandit
In today’s process-centered business organization, it is imperative that enterprise information
system must be converted from task-centered to process-centered system. Traditional software
development methodology is function-oriented, in which each function manages its own data
and it results in redundancy because data that belongs to one object are stored by several
functions. Proposed in this paper is a process-driven software development methodology, in
which business process is a major concern and workflow functionalities are identified and
specified throughout the entire development life cycle. In the proposed methodology, the
development process, modeling tools and deliverables are clarified explicitly. Proposed
methodology can be a guideline to practitioners involved in enterprise software development, of
which workflow is an essential part.
PHP modernization approach generating KDM models from PHP legacy codejournalBEEI
With the rise of new web technologies such as web 2.0, Jquery, Bootstrap. Modernizing legacy web systems to benefit from the advantages of the new technologies is more and more relevant. The migration of a system from an environment to another is a time and effort consuming process, it involves a complete rewrite of the application adapted to the target platform. To realize this migration in an automated and standardized way, many approaches have tried to define standardized engineering processes. Architecture Driven Modernization (ADM) defines an approach to standardize and automate the reengineering process. We defined an ADM approach to represent PHP web applications in the highest level of abstraction models. To do this, we have used software artifacts as a entry point . This paper describes the extraction process, which permits discovering and understanding of the legacy system. And generate models to represent the system in an abstract way.
This document summarizes a research paper that proposes using business process models and lifecycle management to provide context and improve the development and use of message standards for systems integration. Key points:
- Message standards are increasingly complex, making them difficult to use for specific integration cases. Context is needed to define how standards should be adapted and applied.
- The researchers developed tools called MSSRT and BPCCS that use business process models and lifecycle management to provide context definitions for message standards.
- BPCCS classifies and catalogs business process models using classification schemes to define contexts. MSSRT then applies these contexts to generate customized message standard profiles for specific integration cases.
The document provides an overview of the Object Management Group (OMG) and some of the standards they have developed, including the Unified Modeling Language (UML) and Model Driven Architecture (MDA). It discusses the history and goals of OMG, key OMG standards like UML, MOF, CWM and CORBA, and how MDA uses these standards to separate application logic from implementation details. The document also summarizes some of the benefits of using MDA such as increased portability and integration across platforms.
Unified Component Model for Distributed, Real- Time and Embedded Systems Requ...Remedy IT
The objective of this RFP is to solicit proposals for a new component model called the “Unified Component Model” targeting Distributed, Real-Time and Embedded (DRTE) Systems. A component model defines a set of standards for component implementation, naming, interoperability, customization, composition, evolution, and deployment.
The UCM will be a simple, lightweight, middleware-agnostic, and flexible component model. The UCM will allow many different interaction models, including publish-subscribe and request-reply.
This document discusses the use of Model-Driven Architecture (MDA) and model transformations in software product lines (SPL). It begins by introducing SPLs and MDA. SPLs aim to increase productivity by leveraging commonalities between related products. MDA uses platform-independent and platform-specific models with transformations between them. The document then explores combining MDA and SPL approaches through the Modden framework and Baseline-Oriented Modeling. Modden develops reusable core assets through domain and application engineering processes with MDA. Baseline-Oriented Modeling produces expert systems as PRISMA architectural models from SPLs using MDA.
This document outlines the M3 modeling methodology, which provides a framework for developing and maintaining enterprise architecture models. The methodology uses the Unified Modeling Language (UML) and is based on the principles of Model Driven Architecture (MDA). Models are created at three levels - computation independent model (CIM), platform independent model (PIM), and platform specific model (PSM). Integration specific models (ISM) are also used to model different integration viewpoints. The methodology utilizes IBM Rational tools like RSA, RTC and RAM to support the modeling lifecycle.
Evolution of Modelling Techniques for Service Oriented ArchitectureIJERA Editor
Service-oriented architecture (SOA) is a software design and architecture design pattern based on independent pieces of software providing functionality as services to other applications. The benefit of SOA in the IT infrastructure is to allow parallel use and data exchange between programs which are services to the enterprise. Unified Modelling Language (UML) is a standardized general-purpose modelling language in the field of software engineering. The UML includes a set of graphic notation techniques to create visual models of object-oriented software systems. We want to make UML available for SOA as well. SoaML (Service oriented architecture Modelling Language) is an open source specification project from the Object Management Group (OMG), describing a UML profile and meta-model for the modelling and design of services within a service-oriented architecture. BPMN was also extended for SOA but there were few pitfalls. There is a need of a modelling framework which dedicated to SOA. Michael Bell authored a framework called Service Oriented Modelling Framework (SOMF) which is dedicated for SOA.
Process driven software development methodology for enterprise information sy...csandit
In today’s process-centered business organization, it is imperative that enterprise information
system must be converted from task-centered to process-centered system. Traditional software
development methodology is function-oriented, in which each function manages its own data
and it results in redundancy because data that belongs to one object are stored by several
functions. Proposed in this paper is a process-driven software development methodology, in
which business process is a major concern and workflow functionalities are identified and
specified throughout the entire development life cycle. In the proposed methodology, the
development process, modeling tools and deliverables are clarified explicitly. Proposed
methodology can be a guideline to practitioners involved in enterprise software development, of
which workflow is an essential part.
PHP modernization approach generating KDM models from PHP legacy codejournalBEEI
With the rise of new web technologies such as web 2.0, Jquery, Bootstrap. Modernizing legacy web systems to benefit from the advantages of the new technologies is more and more relevant. The migration of a system from an environment to another is a time and effort consuming process, it involves a complete rewrite of the application adapted to the target platform. To realize this migration in an automated and standardized way, many approaches have tried to define standardized engineering processes. Architecture Driven Modernization (ADM) defines an approach to standardize and automate the reengineering process. We defined an ADM approach to represent PHP web applications in the highest level of abstraction models. To do this, we have used software artifacts as a entry point . This paper describes the extraction process, which permits discovering and understanding of the legacy system. And generate models to represent the system in an abstract way.
This document summarizes a research paper that proposes using business process models and lifecycle management to provide context and improve the development and use of message standards for systems integration. Key points:
- Message standards are increasingly complex, making them difficult to use for specific integration cases. Context is needed to define how standards should be adapted and applied.
- The researchers developed tools called MSSRT and BPCCS that use business process models and lifecycle management to provide context definitions for message standards.
- BPCCS classifies and catalogs business process models using classification schemes to define contexts. MSSRT then applies these contexts to generate customized message standard profiles for specific integration cases.
This document discusses various proposed software development methodologies that are based on model-driven architecture (MDA). It first provides background on MDA and its key concepts. It then examines how MDA can be mapped to the Rational Unified Process (RUP) software development lifecycle framework. The rest of the document describes several specific MDA-based methodologies: MODA-TEL, MASTER, MIDAS, C3, ODAC, and DREAM. It compares these methodologies based on which phases of the software development lifecycle they cover in detail. The document concludes that while many have invested in MDA, a standardized methodology for developing model-based systems is still lacking.
This document provides an overview of Industrial Modeling Frameworks (IMFs) developed by Industrial Algorithms LLC. IMFs are pre-configured solutions in the company's Industrial Modeling and Programming Language (IMPL) for specific industrial optimization problem domains like logistics or data mining. IMPL uses shapes and objects to model problems, avoiding the need for users to work with low-level modeling details. IMFs further focus IMPL by including pre-defined semantics for common problem types, reducing the time needed to capture benefits from optimized solutions.
BPM-X Pattern-based model transformations (v2)BPM-Xchange
Model data conversions can be achieved with a pattern-based transformation engine, a component included into the BPM-Xchange® enterprise application integration (EAI) software.
SEAA'2012: An MDE approach for Runtime Monitoring and Adapting Component-base...Applied Computing Group
This document proposes an MDE-based approach for runtime monitoring and adapting component-based user interface systems. The approach uses models to represent the user interface, observes the interface at runtime, and can transform models to adapt the interface by replacing or reconfiguring components. The goal is to provide a flexible way to adapt component-based user interfaces based on runtime conditions.
This document discusses transformation design patterns for model-driven development. It introduces model-driven development and model transformations. It then describes several common transformation design patterns: Reference Filter, One to Many, Filling the Gaps, Ask the User, Copy a Reference, and Chain. For each pattern, it provides a problem example, solution strategy, and consequences of the pattern. The patterns provide approaches for relating input and output models in model transformations.
The document describes an MDA-based environment called ONE for modeling and executing business negotiations. It uses an MDA approach with models defined at different abstraction levels (M3-M0). A domain-specific language was defined and used to generate a modeling editor, allowing users to create negotiation models. These models are then executed in a runtime environment. The runtime has a peer-to-peer architecture and is scalable to support growing model needs from the community. MDA principles were key to allowing new negotiation models to be added without software changes.
Application of SHAPE Technologies in Production and Process OptimizationBrian Elvesæter
B. Elvesæter, E. Landre, and A.-J. Berre, "Application of SHAPE Technologies in Production and Process Optimization", paper presentation at IESA 2010 Workshop “Use of MDI/SOA concepts in Industry”, Coventry, United Kingdom, 13 April 2010.
The document discusses modeling and the Model Driven Architecture (MDA) approach. It notes that modeling has been used for thousands of years in fields like engineering, architecture, and shipbuilding. The MDA aims to make adaptability the central design focus through the use of modeling. The key concepts of MDA include transformations between models at different levels of abstraction and a focus on graphical modeling languages. The ultimate goal is to specify architectures that can last for decades while facilitating integration and maintenance.
When talking about modeling, I think there will be a bundle of terms that will come to our mind, UML, domain driven development, DSL, forward/reverse enginerring, MDD, MDA, BPMN. These technology or methodology have been there for years; And obviously, modeling has proven itself to provide value by improving communication, business-alignment, quality, and productivity. Its applicability includes a number of disciplines such as analysis, design, or development. But why aren’t we all doing Model Driven Development yet?
This document provides an introduction to business modeling. It discusses that software includes more than just code and architecture, and includes all artifacts that contribute to a usable system. It notes that business process modeling notation (BPM) and the unified modeling language (UML) are examples of modeling languages used. The document focuses on domain models and requirements models. It provides an overview of how a domain model incorporates feature models, functional models, entity relationship diagrams, and business process models. It indicates that domain models can be used to understand dependencies and impacts of changes.
This document provides an overview of a five-day course on architecting and designing J2EE applications. The course objectives are to understand the process of developing an architecture from requirements to implementation using the J2EE framework. It will cover business and technical architecture design, mapping components to J2EE, and include hands-on labs. The agenda includes sections on business architecture, applying component modeling, J2EE technical overview, and mapping to the technical architecture.
The document discusses the role of the Object Management Group (OMG) and its Model Driven Architecture (MDA) standards in supporting Service Oriented Architectures (SOAs). It explains that MDA provides platform-independent modeling standards for the different layers of an SOA - from business processes to services to components. These standards, such as BPMN, UML, and SPEM, allow for complete modeling of SOA solutions and transformation between models. They provide a common foundation and approach that ensures interoperability and protects long-term investments in SOA systems.
Systems Modeling Language (SysML®) v2 Request For Proposal (RFP)Massimo Talia
This RFP specifies the requirements for the next generation of the OMG
Systems Modeling Language (OMG SysML® v2) that are intended to address many of the limitations of the current version of OMG SysML® to enable the
more effective application of model-based systems engineering (MBSE). The most used version of SysML is v.1.4 and UML v.2.0 for Software Systems.
The document summarizes the components and plans for the Model Development Tools (MDT) project in the upcoming Galileo release in June 2010. It outlines the key components including Business Process Model and Notation (BPMN2), Object Constraint Language (OCL), Papyrus, Semantics of Business Vocabulary and Rules (SBVR), Unified Modeling Language 2 (UML2), and proposals like the Metamodel Specification Tools (MST) and Ontology Definition Metamodel (ODM). It discusses themes and specific plans to improve compliance, extensibility, currency and usability for each component to appeal to a broader community.
Service Oriented & Model Driven ArchitecturesPankaj Saharan
The document discusses a seminar on combining Service-Oriented Architectures (SOA) and Model Driven Architectures (MDA). It first provides an overview of SOA and MDA individually, including their goals and characteristics. It then analyzes the similarities and differences between the two approaches when combining them. Some benefits are improved productivity and lower costs, while challenges include defining models and transformations between levels of abstraction. Overall, the document concludes that combining SOA with MDA's model-driven approach can provide benefits like business agility if key issues like semantics and metadata modeling are adequately addressed.
The document discusses process standards for business process modeling and management. It describes the risks and benefits of standards, prominent standards for graphical notation (BPMN), interchange formats (XPDL, BPDM), and execution (BPEL). It predicts that BPMN will remain the primary modeling notation, BPDM may replace XPDL as the interchange standard, and standards will continue evolving to improve integration of business and IT.
This document discusses model-driven architecture (MDA), an approach to system specification and interoperability based on the use of formal models. MDA uses platform-independent models that are translated to platform-specific models using formal rules. Core MDA standards like UML, MOF, XMI, and CWM define the infrastructure. The vision is for nearly seamless interoperability based on shared metadata and formal model translations, with a long-term goal of adaptive object models that can dynamically interpret models at runtime.
This document presents a reference architecture for developing an integrated healthcare management solution using Model-Driven Architecture (MDA), The Open Group Architecture Framework (TOGAF), and collaboration tools. It combines the M3 modeling framework with TOGAF to develop models at different levels of abstraction. These include computation independent, platform independent, and platform specific models. The reference architecture includes models for business architecture, applications architecture, and technology architecture. It demonstrates how the models map to TOGAF architecture domains and phases to represent the overall enterprise architecture.
enhanced Telecommunication Operating Model (e-TOM) is part of TM Frameworx. The eTOM is a comprehensive standard business processes framework. It is industry standard best practices and recommends for all business processes and or rules to support Business Support Systems (BSS) /Operation Support Systems (OSS) for communications Service providers (CSP) space. Please visit the TM Forum site for details:
https://www.tmforum.org/business-process-framework/
Executable UML (xUML) provides an executable version of UML with a precisely defined semantics for actions. xUML supports the separation of business logic from platform technology through platform independent models (PIMs) that can be automatically transformed into platform specific models (PSMs) through model mappings. Tools such as Kennedy Carter's iUML and Accelerated Technology's BridgePoint allow developers to simulate and test xUML models prior to translation into executable code.
Technology, Software, Architecture for P&C InsuranceGregg Barrett
This document summarizes Gregg Barrett's recommendations for technology platforms and standards/frameworks for Q1 2012. It recommends evaluating the Microsoft platform using SQL Server, BizTalk Server, and SQL Server Integration Services for ETL capabilities. If Microsoft is not suitable, it recommends considering Adeptia, Informatica, Software AG, TIBCO, and Progress Software. It outlines several relevant standards and frameworks in areas like insurance, data modeling, business processes, financial reporting, and more. It provides links and descriptions for some of the key standards.
This document provides an overview of BPMN (Business Process Modeling Notation) fundamentals. It discusses the history and development of BPMN, including its definition, initial charter within OMG, and key milestones. It also describes the BPMN notation elements, including the core and complete sets of diagram elements. Examples are given of how to model normal flow, B2B processes, exception handling, and compensation handling. Directions for 2005-2006 include finalizing the BPMN 1.x specification, aligning BPMN with other OMG process work like BPDM, developing a metamodel and schema for BPMN, and exploring extensions.
This document discusses various proposed software development methodologies that are based on model-driven architecture (MDA). It first provides background on MDA and its key concepts. It then examines how MDA can be mapped to the Rational Unified Process (RUP) software development lifecycle framework. The rest of the document describes several specific MDA-based methodologies: MODA-TEL, MASTER, MIDAS, C3, ODAC, and DREAM. It compares these methodologies based on which phases of the software development lifecycle they cover in detail. The document concludes that while many have invested in MDA, a standardized methodology for developing model-based systems is still lacking.
This document provides an overview of Industrial Modeling Frameworks (IMFs) developed by Industrial Algorithms LLC. IMFs are pre-configured solutions in the company's Industrial Modeling and Programming Language (IMPL) for specific industrial optimization problem domains like logistics or data mining. IMPL uses shapes and objects to model problems, avoiding the need for users to work with low-level modeling details. IMFs further focus IMPL by including pre-defined semantics for common problem types, reducing the time needed to capture benefits from optimized solutions.
BPM-X Pattern-based model transformations (v2)BPM-Xchange
Model data conversions can be achieved with a pattern-based transformation engine, a component included into the BPM-Xchange® enterprise application integration (EAI) software.
SEAA'2012: An MDE approach for Runtime Monitoring and Adapting Component-base...Applied Computing Group
This document proposes an MDE-based approach for runtime monitoring and adapting component-based user interface systems. The approach uses models to represent the user interface, observes the interface at runtime, and can transform models to adapt the interface by replacing or reconfiguring components. The goal is to provide a flexible way to adapt component-based user interfaces based on runtime conditions.
This document discusses transformation design patterns for model-driven development. It introduces model-driven development and model transformations. It then describes several common transformation design patterns: Reference Filter, One to Many, Filling the Gaps, Ask the User, Copy a Reference, and Chain. For each pattern, it provides a problem example, solution strategy, and consequences of the pattern. The patterns provide approaches for relating input and output models in model transformations.
The document describes an MDA-based environment called ONE for modeling and executing business negotiations. It uses an MDA approach with models defined at different abstraction levels (M3-M0). A domain-specific language was defined and used to generate a modeling editor, allowing users to create negotiation models. These models are then executed in a runtime environment. The runtime has a peer-to-peer architecture and is scalable to support growing model needs from the community. MDA principles were key to allowing new negotiation models to be added without software changes.
Application of SHAPE Technologies in Production and Process OptimizationBrian Elvesæter
B. Elvesæter, E. Landre, and A.-J. Berre, "Application of SHAPE Technologies in Production and Process Optimization", paper presentation at IESA 2010 Workshop “Use of MDI/SOA concepts in Industry”, Coventry, United Kingdom, 13 April 2010.
The document discusses modeling and the Model Driven Architecture (MDA) approach. It notes that modeling has been used for thousands of years in fields like engineering, architecture, and shipbuilding. The MDA aims to make adaptability the central design focus through the use of modeling. The key concepts of MDA include transformations between models at different levels of abstraction and a focus on graphical modeling languages. The ultimate goal is to specify architectures that can last for decades while facilitating integration and maintenance.
When talking about modeling, I think there will be a bundle of terms that will come to our mind, UML, domain driven development, DSL, forward/reverse enginerring, MDD, MDA, BPMN. These technology or methodology have been there for years; And obviously, modeling has proven itself to provide value by improving communication, business-alignment, quality, and productivity. Its applicability includes a number of disciplines such as analysis, design, or development. But why aren’t we all doing Model Driven Development yet?
This document provides an introduction to business modeling. It discusses that software includes more than just code and architecture, and includes all artifacts that contribute to a usable system. It notes that business process modeling notation (BPM) and the unified modeling language (UML) are examples of modeling languages used. The document focuses on domain models and requirements models. It provides an overview of how a domain model incorporates feature models, functional models, entity relationship diagrams, and business process models. It indicates that domain models can be used to understand dependencies and impacts of changes.
This document provides an overview of a five-day course on architecting and designing J2EE applications. The course objectives are to understand the process of developing an architecture from requirements to implementation using the J2EE framework. It will cover business and technical architecture design, mapping components to J2EE, and include hands-on labs. The agenda includes sections on business architecture, applying component modeling, J2EE technical overview, and mapping to the technical architecture.
The document discusses the role of the Object Management Group (OMG) and its Model Driven Architecture (MDA) standards in supporting Service Oriented Architectures (SOAs). It explains that MDA provides platform-independent modeling standards for the different layers of an SOA - from business processes to services to components. These standards, such as BPMN, UML, and SPEM, allow for complete modeling of SOA solutions and transformation between models. They provide a common foundation and approach that ensures interoperability and protects long-term investments in SOA systems.
Systems Modeling Language (SysML®) v2 Request For Proposal (RFP)Massimo Talia
This RFP specifies the requirements for the next generation of the OMG
Systems Modeling Language (OMG SysML® v2) that are intended to address many of the limitations of the current version of OMG SysML® to enable the
more effective application of model-based systems engineering (MBSE). The most used version of SysML is v.1.4 and UML v.2.0 for Software Systems.
The document summarizes the components and plans for the Model Development Tools (MDT) project in the upcoming Galileo release in June 2010. It outlines the key components including Business Process Model and Notation (BPMN2), Object Constraint Language (OCL), Papyrus, Semantics of Business Vocabulary and Rules (SBVR), Unified Modeling Language 2 (UML2), and proposals like the Metamodel Specification Tools (MST) and Ontology Definition Metamodel (ODM). It discusses themes and specific plans to improve compliance, extensibility, currency and usability for each component to appeal to a broader community.
Service Oriented & Model Driven ArchitecturesPankaj Saharan
The document discusses a seminar on combining Service-Oriented Architectures (SOA) and Model Driven Architectures (MDA). It first provides an overview of SOA and MDA individually, including their goals and characteristics. It then analyzes the similarities and differences between the two approaches when combining them. Some benefits are improved productivity and lower costs, while challenges include defining models and transformations between levels of abstraction. Overall, the document concludes that combining SOA with MDA's model-driven approach can provide benefits like business agility if key issues like semantics and metadata modeling are adequately addressed.
The document discusses process standards for business process modeling and management. It describes the risks and benefits of standards, prominent standards for graphical notation (BPMN), interchange formats (XPDL, BPDM), and execution (BPEL). It predicts that BPMN will remain the primary modeling notation, BPDM may replace XPDL as the interchange standard, and standards will continue evolving to improve integration of business and IT.
This document discusses model-driven architecture (MDA), an approach to system specification and interoperability based on the use of formal models. MDA uses platform-independent models that are translated to platform-specific models using formal rules. Core MDA standards like UML, MOF, XMI, and CWM define the infrastructure. The vision is for nearly seamless interoperability based on shared metadata and formal model translations, with a long-term goal of adaptive object models that can dynamically interpret models at runtime.
This document presents a reference architecture for developing an integrated healthcare management solution using Model-Driven Architecture (MDA), The Open Group Architecture Framework (TOGAF), and collaboration tools. It combines the M3 modeling framework with TOGAF to develop models at different levels of abstraction. These include computation independent, platform independent, and platform specific models. The reference architecture includes models for business architecture, applications architecture, and technology architecture. It demonstrates how the models map to TOGAF architecture domains and phases to represent the overall enterprise architecture.
enhanced Telecommunication Operating Model (e-TOM) is part of TM Frameworx. The eTOM is a comprehensive standard business processes framework. It is industry standard best practices and recommends for all business processes and or rules to support Business Support Systems (BSS) /Operation Support Systems (OSS) for communications Service providers (CSP) space. Please visit the TM Forum site for details:
https://www.tmforum.org/business-process-framework/
Executable UML (xUML) provides an executable version of UML with a precisely defined semantics for actions. xUML supports the separation of business logic from platform technology through platform independent models (PIMs) that can be automatically transformed into platform specific models (PSMs) through model mappings. Tools such as Kennedy Carter's iUML and Accelerated Technology's BridgePoint allow developers to simulate and test xUML models prior to translation into executable code.
Technology, Software, Architecture for P&C InsuranceGregg Barrett
This document summarizes Gregg Barrett's recommendations for technology platforms and standards/frameworks for Q1 2012. It recommends evaluating the Microsoft platform using SQL Server, BizTalk Server, and SQL Server Integration Services for ETL capabilities. If Microsoft is not suitable, it recommends considering Adeptia, Informatica, Software AG, TIBCO, and Progress Software. It outlines several relevant standards and frameworks in areas like insurance, data modeling, business processes, financial reporting, and more. It provides links and descriptions for some of the key standards.
This document provides an overview of BPMN (Business Process Modeling Notation) fundamentals. It discusses the history and development of BPMN, including its definition, initial charter within OMG, and key milestones. It also describes the BPMN notation elements, including the core and complete sets of diagram elements. Examples are given of how to model normal flow, B2B processes, exception handling, and compensation handling. Directions for 2005-2006 include finalizing the BPMN 1.x specification, aligning BPMN with other OMG process work like BPDM, developing a metamodel and schema for BPMN, and exploring extensions.
Open Digital Architecture (ODA) is a blueprint for modular, cloud-based, open digital platforms that can be orchestrated using AI.
Designed to support our industry into the cloud native era, ODA sets the framework required
for CSPs to invest in IT, transforming business agility and operations by creating simpler IT and network solutions that are easier and cheaper to deploy, integrate and upgrade. Enabling growth, profitability and a cutting-edge customer experience.
The document discusses extending the existing SRML metamodel to implement additional properties of interaction protocols and external policies. The main tasks are to define grammars for coordination and external policies, and extend the metamodel using the Xtext grammar. This will allow users to edit models and view changes in the SRML editor. The document also discusses transforming SRML models to BPEL for business processes, and improving the graphical representation of SRML models in Eclipse.
The document discusses the ONE (Open Negotiation Environment) project, which aims to create an MDA-based environment for modeling and executing business negotiations. The key aspects are:
1) The project defines a domain-specific language (DSL) for modeling negotiations using a metamodel. This DSL captures domain concepts like offers, agreements, and actions.
2) Models created with the DSL are stored in XMI files and can then be executed by a negotiation engine to run actual negotiations.
3) The DSL and tools were created using an MDA approach with transformations between metamodels, models, and runtime representations.
Similar to OMG Specifications for Enterprise Interoperability (20)
A Comparison of the Essence 1.0 and SPEM 2.0 Specifications for Software Engi...Brian Elvesæter
B. Elvesæter, G. Benguria, and S. Ilieva, "A Comparison of the Essence 1.0 and SPEM 2.0 Specifications for Software Engineering Methods", paper presentation at PMDE 2013, Montpellier, France, 2 July 2013.
Experiences with Migration from SPEM 2.0 to Essence 1.0 for the REMICS Method...Brian Elvesæter
"Experiences with Migration from SPEM 2.0 to Essence 1.0 for the REMICS Methodology", Essence Workshop, OMG Technical Meeting, Berlin, Germany, 20 June 2013.
Towards an Agile Foundation for the Creation and Enactment of Software Engine...Brian Elvesæter
B. Elvesæter, M. Striewe, A. McNeile, and A.-J. Berre, "Towards an Agile Foundation for the Creation and Enactment of Software Engineering Methods: The SEMAT Approach", paper presentation at PMDE 2012, Kongens Lyngby, Denmark, 3 July 2012.
Language (SoaML): A baseline for Specification of Cloud-based ServicesBrian Elvesæter
This document discusses using the Service-oriented architecture Modeling Language (SoaML) as a baseline for specifying cloud-based services. SoaML defines modeling constructs for services, but has some inconsistencies. The document outlines SoaML, identifies issues, provides an example, and discusses two approaches to service modeling in SoaML. It proposes using SoaML as a baseline and extending it towards a Cloud Modeling Language (CloudML) standardized by the Object Management Group. Future work includes specifying a SoaML4Cloud metamodel and profile and issuing a request for proposal for CloudML.
A Customizable Methodology for the Model-driven Engineering of Service-based ...Brian Elvesæter
M. Stollberg, B. Elvesæter, V. Shafran, and R. Magarshak, "A Customizable Methodology for the Model-driven Engineering of Service-based System Landscapes", paper presentation at MDA4ServiceCloud’10, Paris, France, 15 June 2010.
Networked Enterprise transformation and resource management in future interne...Brian Elvesæter
B. Elvesæter, A.-J. Berre, H. d. Man, and M.-S. Li, "Networked Enterprise transformation and resource management in future internet enabled Innovation Clouds", paper presentation at IESA 2010, Coventry, United Kingdom, 15 April 2010.
Towards a Model-Driven and Role-Configurable Methodology Suite for Enterprise...Brian Elvesæter
B. Elvesæter and A.-J. Berre, "Towards a Model-Driven and Role-Configurable Methodology Suite for Enterprise and Service-Oriented Interoperability", paper presentation at IESA 2010 Doctoral Symposium, Coventry, United Kingdom, 12 April 2010.
Towards Enterprise Interoperability Service UtilitiesBrian Elvesæter
This document discusses the development of baseline enterprise interoperability (EI) services as part of the COIN project. It provides an overview of EI challenges and proposes an EI services framework. A state-of-the-art analysis of existing EI tools from FP6 projects is presented. Based on this, 11 proposed baseline EI services across various categories like model-driven, semantic mediation, and data interoperability are described. The benefits of these services for reducing integration costs and enabling collaboration are highlighted. The conclusions discuss positioning the COIN platform to offer these EI services as utilities according to the Software-as-a-Service model.
A.-J. Berre, B. Elvesæter, N. Figay, C. Guglielmina, S. G. Johnsen, D. Karlsen, and S. Lippe, "The ATHENA Interoperability Framework", paper presentation at I-ESA 2007, Madeira, Portugal, 30 March 2007.
Rapid Prototyping for Service-Oriented ArchitecturesBrian Elvesæter
J. Vayssière, G. Benguria, B. Elvesæter, K. Fischer, and I. Zinnikus, "Rapid Prototyping for Service-Oriented Architectures", paper presentation at the 2nd Workshop on Web Services Interoperability (WSI 2006), Bordeaux, France, 21 March 2006.
B. Elvesæter, R. K. Rolfsen, F. Lillehagen, and D. Karlsen, "Integrated Enterprise Service Architecture", paper presentation at CE 2005, Fort Worth, Texas, USA, 26 July 2005.
Web Services og SOA – hvordan vi ser for oss bruk i fremtiden?Brian Elvesæter
This document discusses service-oriented architecture (SOA) and web services. It begins by defining SOA, web services architecture, and how they relate to enterprise architecture. It then covers topics like interoperability, integration approaches in SOA, and the evolution of web services standards. Semantic web services are introduced as the next generation that aims to automate discovery, composition and execution of web services through semantic annotations and ontologies. Research directions like model-driven architecture and combining different modeling languages are also mentioned. In summary, the document provides an overview of SOA, web services, integration, interoperability and research trends in the area.
This document discusses enterprise architecture, service-oriented architecture, and web services architecture. It begins with an outline that describes what will be covered, including definitions of the key terms and discussions of interoperability, the relationships between enterprise architecture, SOA, and web services, and references. It then provides more detailed explanations of enterprise architecture, including its role in governance and alignment with business goals. It also discusses service-oriented architecture and how it can help provide flexibility and integration. Finally, it briefly introduces web services architecture as a set of enabling technologies for implementing software systems based on SOA principles.
This document discusses service-oriented architecture (SOA) and web services. It begins with definitions of SOA and web services, noting that SOA is an architectural style while web services provide technology and protocol standards. The document then discusses characteristics of SOA like modularity, loose coupling, and standardization. It provides an overview of developments around these topics within the EU, noting projects focused on interoperability research. The document discusses requirements for foundational IT architecture, including the need for flexibility, adaptability, and separation of knowledge from non-interoperable systems. It presents a 4-layered view of an enterprise architecture.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
UiPath Test Automation using UiPath Test Suite series, part 5DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 5. In this session, we will cover CI/CD with devops.
Topics covered:
CI/CD with in UiPath
End-to-end overview of CI/CD pipeline with Azure devops
Speaker:
Lyndsey Byblow, Test Suite Sales Engineer @ UiPath, Inc.
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Introducing Milvus Lite: Easy-to-Install, Easy-to-Use vector database for you...Zilliz
Join us to introduce Milvus Lite, a vector database that can run on notebooks and laptops, share the same API with Milvus, and integrate with every popular GenAI framework. This webinar is perfect for developers seeking easy-to-use, well-integrated vector databases for their GenAI apps.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
OMG Specifications for Enterprise Interoperability
1. OMG Specifications for Enterprise
Interoperability
IESA 2010 Workshop
Standardisation – a foundation for
Interoperability
Brian Elvesæter1 and Arne-Jørgen Berre1
1
SINTEF ICT, P. O. Box 124 Blindern, N-0314 Oslo, Norway
ICT
2. Presentation Outline
Object Management Group (OMG)
Summary of specifications
Selected specifications positioned in Zachman
OMG and interoperability
Overview of standards
BPMN 2.0
SoaML
Conclusions
Questions
ICT
3. Object Management Group (OMG)
The Object Management Group (OMG) is an international, open
membership and not-for-profit industry consortium, which develops
enterprise integration standards for a wide range of technologies and
provide modelling standards to support enterprise architecture.
Summary of specifications
http://www.omg.org/technology/documents/spec_summary.htm
Business modelling specifications
BMM, BPDM, BPMM, BPMN, PRR, SBVR
Modelling and metadata specifications
CWM, MIPS, MOF, MDMI, MLTD, MOFM2T, QVT, MOFFOL, OCL,
SysML, ODM, RAS, FUML, SoaML, SPEM, UML, UMLDI, HUTN, XMI
UML profile specifications
SysML, smartant, CCMP, CCCMP, UML4DDS, EAI, EDOC, MARTE,
QFTP, SPTP, SoCP, SDRP, VOICP, UTP, UPDM
ICT
4. Selected Standard Initiatives
We give an overview of the newest OMG modelling standard
initiatives with respect to enterprise architecture.
Enterprises are today looking into enterprise architectures that provide
models that can be used to describe and understand how different
aspects of an enterprise work together.
A framework for enterprise architecture was first introduced by Zachman
in 1987
Business modelling specifications
Business Motivation Model (BMM), Business Process Modeling Notation
(BPMN), Organization Structure Model (OSM), Value Delivery Metamodel
(VDM), Case Management Process Modeling (CMPM), Semantics of
Business Vocabulary and Business Rules (SBVR), Date-Time Foundation
Vocabulary (DTFV)
IT modelling specifications
Unified Modeling Language (UML), Service oriented architecture Modeling
Language (SoaML), Ontology Definition Metamodel (ODM), Information
Management Metamodel (IMM)
ICT
5. OMG Specifications in Zachman (1/2)
Data
(What)
Function
(How)
Scope
(Contexts)
List of things important
to business
List of processes that
the business performs
SBVR
VDM
VDM
Business
(Concepts)
Semantic Model
Business Process
Model
Business Logistics
System
BPMN, CMPM
System
(Logic)
Logical Data Model
Technology
(Physics)
Component
(Assemblies)
Operation
(Instances)
ODM,
IMM (CWM)
Network
(Where)
People
(Who)
Time
(When)
List of locations which
List of organizations
List of events/cycles
the business operates important to the business important to the business
OSM
Motivation
(Why)
List of business
goals/strategies
DTFV
BMM
Workflow Model
Master Schedule
BPMN, CMPM,
DTFV
Business
Plan
BPMN, CMPM
OSM, BPMN,
CMPM
ODM,
IMM (CWM), UML
Application
Architecture
Distributed
System Architecture
Human Interface
Architecture
SoaML, UML
SoaML, UML
BPMN, CMPM
Physical Data Model
System Design
IMM (CWM), UML
SoaML, UML
Technology
Architecture
Data Definition
Program
IMM (CWM), UML
UML
Data
Function
SoaML, UML
Network
Architecture
UML
Network
Presentation
Architecture
Process Structure
BPMN, CMPM,
DTFV
Control Structure
SBVR
Business Rule
Model
SBVR
Rule
Design
BPMN, CMPM,
DTFV
SBVR
Timing
Definition
Rule
Definition
DTFV
SBVR
Schedule
Strategy
Security
Architecture
Organization
ICT
6. OMG Specifications in Zachman (2/2)
Data
(What)
SBVR
Network
(Where)
Function
(How)
VDMList of locations
which the business
People
(Who)
Time
(When)
Motivation
(Why)
List of events/cycles
important to the
business
List of business
goals/strategies
Workflow
Model
Master
Schedule
Business
Plan
Human
Interface
Architecture
Process
Structure
Business Rule
Model
OSM
List of things
important
to business
List of processes
that the business
performs
operates
Business
(Concepts)
Semantic Model
Business
Process
Model
Business
Logistics
System
System
(Logic)
Logical Data Model
Application
Architecture
Distributed
System
Architecture
Technology
(Physics)
Physical Data Model
IMM
(CWM)
System Design
Technology
Architecture
Presentation
Architecture
Structure
DTFV
Control
Rule
Design
Component
(Assemblies)
Data Definition
Program
Network
Architecture
Security
Architecture
Timing
Definition
Rule
Definition
Operation
(Instances)
Data
Function
Network
Organization
Schedule
Strategy
ODM
SoaML
List of organizations
important to the
business
BMM
Scope
(Contexts)
BPMN
CMPM
UML
ICT
SBVR
7. OMG and Interoperability
Enterprise Architecture
Zachman Framework introduced in 1987.
Today there exists several, e.g., DoDAF, MODAF, TOGAF.
Regardless of the differences between the enterprise
architectures,
the models within them must all represent the goals, processes,
rules, IT resources and relationships
that define how the enterprise operates.
Since all of OMG’s modelling specifications are based on
a common modelling infrastructure, namely the Meta-Object
Facility (MOF),
using OMG modelling standards help tie individual models
together in an overall architecture.
ICT
8. Metamodelling
System development is fundamentally based on the use of
languages to capture and relate different aspects of the
problem domain.
The benefit of metamodelling is its ability to describe these
languages in a unified way.
This means that the languages can be uniformly managed and
manipulated thus tackling the problem of language diversity.
For instance, mappings can be constructed between any number
of languages provided that they are described in the same
metamodelling language.
Using metamodels, many different abstractions can be defined
and combined to create new languages that are specifically
tailored for a particular application domain.
ICT
9. Three Modelling Levels
Minimum & Reflexive
M3
the MOF
MMM
level
M2 level
the BMM
MM
M1 level
M0 level
a UML
model m
a particular
use of m
the BPMN
MM
the UML
MM
another UML
model m’
another
use of m
“The real world”
ICT
11. Business Modelling Specifications (1/2)
Business Motivation Model (BMM)
Implementing enterprise
architecture typically starts with
documenting goals, strategy and
business plans.
BMM defines a set of concepts
(e.g., goal, objective, vision, means
and strategy) that can be used to
model the elements of business
plans.
These elements can be linked to
business roles, business rules and
organization unit that are specified
using other OMG modelling
standards.
Business Process Modeling
Notation (BPMN)
BPMN 2.0 is in the final stages of
standards adoption at OMG.
The specification provides a
notation and a model for business
processes and an interchange
format.
BPMN is designed to cover many
types of modelling and allows the
creation of end-to-end business
processes.
It allows the specification of private
processes (both non-executable
and executable), public processes,
choreographies and collaborations.
ICT
12. Business Modelling Specifications (2/2)
Value Delivery Metamodel (VDM)
This RFP solicits proposals for a
metamodel specification for
modelling customer value delivery.
Integrated value delivery models
provide context for understanding
the impact of services on multiple
lines of business.
These models also provide the
context for sharing services.
They make cost and time analysis,
in the context of strategic planning
and transformation, more efficient
by formalizing the structure of the
value delivery system.
Case Management Process
Modeling (CMPM)
This RFP solicits proposals for a
metamodel extension to BPMN 2.0
to support modelling of case
management processes.
Case Management focuses on
actions to resolve a case – a
situation to be managed toward
objectives.
Cases don’t have predefined
processes for achieving objectives.
Humans make decisions based on
observations, experience and the
case file.
ICT
13. BPMN History
The Business Process Management Institute (BPMI – now
a part of the OMG) develops BPML and realizes the need
for a graphical notation
BPML was later replaced by BPEL as the target execution
language
August 2001, the Notation Working Group is formed.
May 2004, the BPMN 1.0 specification was released.
BPMN1.x
BPMN 1.0 adopted as an OMG standard – February 2006
BPMN 1.1 (OMG) – January 2008
BPMN 1.2 (OMG) – January 2009
BPMN 2.0 expected finalized June 2010
http://www.omg.org/spec/BPMN/2.0/
13
ICT
14. New Features in BPMN 2.0
Formal metamodel specified in MOF
Interchange formats for model and diagram interchange
New process elements
Non-interrupting events
Event sub-process
New data elements
New interaction diagrams
Conversation
Choreography
14
ICT
15. Conversation Diagram
A Conversation is set of
Message exchanges (Message
Flow) that share the same
Correlation.
15
Conversation diagram depicting
several conversations between
Participants in a related
domain.
ICT
16. Choreography Diagram
Provides a flowchart view to sequence interactions between
Participants
Choreographies define a “business contract” or protocol to which the
Participants agree to follow during real-time interactions.
16
ICT
17. SoaML History
http://www.soaml.org
Issued September
29, 2006
LOI Deadline
November 28, 2006
IBM,...
SHAPE,...
Fujitsu,...
Initial Submission
Deadline June 4, 2007
S1(3)
Adaptive,...
S3(1) Revised Submission
Deadline May 26, 2008
S2(2)
Revised Submission
November 19, 2007
OMG Technical Meeting
June 23-27, 2008 *
Ontario Canada
B1
Revised Submission
Deadline Aug 25, 2008
SoaML FTF Feb., 2009
OMG Technical Meeting
Dec 08-12, 2008 *
Santa Clara EEUU
Voting List Deadline
August 5, 2007
S4
OMG Technical Meeting
Sept 22-26, 2008 *
Orlando EEUU
S5
Revised Submission
Deadline Nov 10, 2008
AMP, Aug. 2009
B2
SoaML FTF Nov., 2009
BPMN 2.0, Dec. 2009
SoaML FTF Rec. Dec.,
2009, Los Angeles
SoaML final standard
March, 2010 (veto, by
Oct. 2010)
Sx – Submission version x
Bx – Beta version x
17
ICT
18. SoaML Goals
Intuitive and complete support for modelling services in UML
Support for bi-directional asynchronous services between multiple
parties
Support for Services Architectures where parties provide and use
multiple services.
Support for services defined to contain other services
Easily mapped to and made part of a business process
specification
Compatibility with UML, BPDM and BPMN for business processes
Direct mapping to web services
Top-down, bottom up or meet-in-the-middle modelling
Design by contract or dynamic adaptation of services
To specify and relate the service capability and its contract
No changes to UML
ICT
19. SoaML Key Concepts
Services architecture – specification of community
Participants – role
Service contracts – collaboration (provide and consume)
Service contract – specification of service
Role – Provider and consumer
Interfaces
Choreography (protocol, behaviour)
Service interface – bi-directional service
Simple interface – one-directional service
ICT
20. Order
Conformation
Provider
Consumer
Marketplace Services – Example
Shipped
Mechanics Are Us
Dealer
Acme Industries
Manufacturer
Consumer Status
Ship Req
Shipped
Provider
Physical
Delivery
Provider
Delivered
GetItThere Freight
Shipper
ICT
Consumer
21. Services Architecture
Purchasing
service
Shipping
service
Ship
Status
service
A ServicesArchitecture (or SOA) is a network of participant roles providing and
consuming services to fulfil a purpose.
The services architecture defines the requirements for the types of participants and
service realizations that fulfil those roles.
The services architecture puts a set of services in context and shows how participants
work together for a community or organization without required process management.
A community ServicesArchitecture is defined using a UML Collaboration.
ICT
23. Service interfaces: ShippingService
The ShippingService service
interface refines the
ShippingContract service
contract.
The ShippingService service
interface involves two roles:
The shipper role is a provider
role. It is responsible for
fulfilling the shipping
responsibilities that are given
by its type, the shipping
interface.
The orderer role is responsible
for processing the shipping
schedule. This is shown by its
ScheduleProcessing type.
ICT
24. Message-centric vs. RPC-style services
There are several SOA interaction
paradigms in common use including
document centric messaging, remote
procedure calls (RPC), and publishsubscribe.
The decision depends on cohesion and
coupling, state management, distributed
transactions, performance, granularity,
synchronization, ease of development
and maintenance, and best practices.
SoaML supports both document-centric
messaging and RPC-style service data.
Service data is data that is exchanged
between service consumers and
providers. The data types of parameters
for service operations are typed by a
DataType, PrimitiveType, or
MessageType.
ICT
25. Service realization: Composite structures
A ServiceInterface can be the type of a service port.
The type of a Request port is also a ServiceInterface. The Request port is the conjugate
of a Service port in that it defines the use of a service rather than its provision.
This will allow us to connect service providers and consumers in a Participant.
Each service operation provided by a service provider must be realized by either a
behavior or an action.
ICT
26. Conclusions
OMG should be regarded as an important industry
consortium that standardizes and promotes many relevant
specifications to support interoperability.
One important benefit of using OMG standards is that all
standards are based on the common modelling
infrastructure MOF, which ensures that the models are
tied together in an overall architecture.
This has the advantage that tools and methodologies that
are based on OMG standards will be able to exchange
models and interpret the different models.
ICT