Business process modelling trends: model-oriented approach. Enterprise2.0Fyodor Prilipko, MSc-student
State University - Higher School of Economics, ERCIS / 2010AgendaAgendaTo-dos for todayModel-oriented approach
BPMN 2.0
Enterprise 2.0
Modeling practiceState University - Higher School of Economics, ERCIS / 2010Model-oriented approachMDA: what is it?Model-oriented approach descriptionThe MDA is a new way of developing applications and writing specifications, based on a platform-independent model (PIM) of the application.
MDA intends to promote the use of models as fundamental way of designing and implementing different kinds of systems.
MDA divorces implementation details from business functions. Thus, it is not necessary to repeat the process of defining an application or system's functionality and behavior each time a new technology (Web Services, for example) comes along. Other architectures are generally tied to a particular technology. With MDA, functionality and behavior are modeled once and only once. Mapping from a PIM through a PSM to the supported MDA platforms is being implemented by tools, easing the task of supporting new or different technologies.State University - Higher School of Economics, ERCIS / 2010Model-oriented approachMDA: historyModel-oriented approach key stepsIn 1996, OMG expanded its scope to include modeling and in 1997 adopted the Unified Modeling Language (UML)® and Meta-Object Facility (MOF™).
Although it has always been true that UML models can be implemented on any platform, the continuing proliferation of middleware "silver bullets" suggested that a platform-independent MOF-based model is the secret to software stability and ROI - a stake that remains fixed in the ground while the infrastructure landscape around it shifts over time.
The MDA was launched by OMG in 2001. It unites OMG's well-established modeling standards with every middleware technology - past, present, and future - to integrate what you've built, with what you're building, with what you're going to build. Rather than focusing on yet another "next best thing," MDA raises the bar and designs portability and interoperability into the application at the model level. The MDA is a new way of developing applications and writing specifications, based on a platform-independent model (PIM) of the application. State University - Higher School of Economics, ERCIS / 2010Model-oriented approachThe main features of MDAModel-oriented approach benefitsThe main motivation behind MDA is to transfer the focus of work from programming to solution modeling by treating models as the primary artifacts of development.
Transformation of models and mapping between models are the key aspects of MDA.
Well-defined transformations that support rigorous model evolution, refinement, and code generation are considered key elements of an MDA approach. MDA allows to program without actually writing the code
State University - Higher School of Economics, ERCIS / 2010Model-oriented approachMDA ViewpointsComputation Independent Viewpoint The computation independent viewpoint focuses on the on the environment of the system, and the requirements for the system; the details of the structure and processing of the system are hidden or as yet undetermined.
Platform Independent Viewpoint The platform independent viewpoint focuses on the operation of a system while hiding the details necessary for a particular platform. A platform independent view shows that part of the complete specification that does not change from one platform to another. A platform independent view may use a general purpose modeling language, or a language specific to the area in which the system will be used.
Platform Specific Viewpoint The platform specific viewpoint combines the platform independent viewpoint with an additional focus on the detail of the use of a specific platform by a system. State University - Higher School of Economics, ERCIS / 2010Model-oriented approachMDA ToolsCreation Tool: A tool used to elicit initial models and/or edit derived models.
Analysis Tool: A tool used to check models for completeness, inconsistencies, or error and warning conditions. Also used to calculate metrics for the model.
Transformation Tool: A tool used to transform models into other models or into code and documentation.
Composition Tool: A tool used to compose (i.e. to merge according to a given composition semantics) several source models, preferably conforming to the same metamodel.
Test Tool: A tool used to "test" models as described in Model-based testing.
Simulation Tool: A tool used to simulate the execution of a system represented by a given model. This is related to the subject of model execution.
Metadata Management Tool: A tool intended to handle the general relations between different models, including the metadata on each model (e.g. author, date of creation or modification, method of creation (which tool? which transformation? etc.)) and the mutual relations between these models (i.e. one metamodel is a version of another one, one model has been derived from another one by a transformation, etc.)
Reverse Engineering Tool: A tool intended to transform particular legacy or information artifact portfolios into full-fledged models. State University - Higher School of Economics, ERCIS / 2010AgendaAgendaTo-dos for todayModel-oriented approach
BPMN 2.0

Hse mda bpmn_210410

  • 1.
    Business process modellingtrends: model-oriented approach. Enterprise2.0Fyodor Prilipko, MSc-student
  • 2.
    State University -Higher School of Economics, ERCIS / 2010AgendaAgendaTo-dos for todayModel-oriented approach
  • 3.
  • 4.
  • 5.
    Modeling practiceState University- Higher School of Economics, ERCIS / 2010Model-oriented approachMDA: what is it?Model-oriented approach descriptionThe MDA is a new way of developing applications and writing specifications, based on a platform-independent model (PIM) of the application.
  • 6.
    MDA intends topromote the use of models as fundamental way of designing and implementing different kinds of systems.
  • 7.
    MDA divorces implementationdetails from business functions. Thus, it is not necessary to repeat the process of defining an application or system's functionality and behavior each time a new technology (Web Services, for example) comes along. Other architectures are generally tied to a particular technology. With MDA, functionality and behavior are modeled once and only once. Mapping from a PIM through a PSM to the supported MDA platforms is being implemented by tools, easing the task of supporting new or different technologies.State University - Higher School of Economics, ERCIS / 2010Model-oriented approachMDA: historyModel-oriented approach key stepsIn 1996, OMG expanded its scope to include modeling and in 1997 adopted the Unified Modeling Language (UML)® and Meta-Object Facility (MOF™).
  • 8.
    Although it hasalways been true that UML models can be implemented on any platform, the continuing proliferation of middleware "silver bullets" suggested that a platform-independent MOF-based model is the secret to software stability and ROI - a stake that remains fixed in the ground while the infrastructure landscape around it shifts over time.
  • 9.
    The MDA waslaunched by OMG in 2001. It unites OMG's well-established modeling standards with every middleware technology - past, present, and future - to integrate what you've built, with what you're building, with what you're going to build. Rather than focusing on yet another "next best thing," MDA raises the bar and designs portability and interoperability into the application at the model level. The MDA is a new way of developing applications and writing specifications, based on a platform-independent model (PIM) of the application. State University - Higher School of Economics, ERCIS / 2010Model-oriented approachThe main features of MDAModel-oriented approach benefitsThe main motivation behind MDA is to transfer the focus of work from programming to solution modeling by treating models as the primary artifacts of development.
  • 10.
    Transformation of modelsand mapping between models are the key aspects of MDA.
  • 11.
    Well-defined transformations thatsupport rigorous model evolution, refinement, and code generation are considered key elements of an MDA approach. MDA allows to program without actually writing the code
  • 12.
    State University -Higher School of Economics, ERCIS / 2010Model-oriented approachMDA ViewpointsComputation Independent Viewpoint The computation independent viewpoint focuses on the on the environment of the system, and the requirements for the system; the details of the structure and processing of the system are hidden or as yet undetermined.
  • 13.
    Platform Independent ViewpointThe platform independent viewpoint focuses on the operation of a system while hiding the details necessary for a particular platform. A platform independent view shows that part of the complete specification that does not change from one platform to another. A platform independent view may use a general purpose modeling language, or a language specific to the area in which the system will be used.
  • 14.
    Platform Specific ViewpointThe platform specific viewpoint combines the platform independent viewpoint with an additional focus on the detail of the use of a specific platform by a system. State University - Higher School of Economics, ERCIS / 2010Model-oriented approachMDA ToolsCreation Tool: A tool used to elicit initial models and/or edit derived models.
  • 15.
    Analysis Tool: Atool used to check models for completeness, inconsistencies, or error and warning conditions. Also used to calculate metrics for the model.
  • 16.
    Transformation Tool: Atool used to transform models into other models or into code and documentation.
  • 17.
    Composition Tool: Atool used to compose (i.e. to merge according to a given composition semantics) several source models, preferably conforming to the same metamodel.
  • 18.
    Test Tool: Atool used to "test" models as described in Model-based testing.
  • 19.
    Simulation Tool: Atool used to simulate the execution of a system represented by a given model. This is related to the subject of model execution.
  • 20.
    Metadata Management Tool:A tool intended to handle the general relations between different models, including the metadata on each model (e.g. author, date of creation or modification, method of creation (which tool? which transformation? etc.)) and the mutual relations between these models (i.e. one metamodel is a version of another one, one model has been derived from another one by a transformation, etc.)
  • 21.
    Reverse Engineering Tool:A tool intended to transform particular legacy or information artifact portfolios into full-fledged models. State University - Higher School of Economics, ERCIS / 2010AgendaAgendaTo-dos for todayModel-oriented approach
  • 22.
  • 23.
  • 24.
    Modeling practiceState University- Higher School of Economics, ERCIS / 2010BPMN 2.0Business process modeling notationWithin and between BPMN sub-models, many types of Diagrams can be createdHigh-level private process activities (not functional breakdown)
  • 25.
  • 26.
    As-is or oldbusiness process
  • 27.
    To-be or newbusiness process
  • 28.
    Detailed private businessprocess with interactions to one or more external entities (or “Black Box” processes)
  • 29.
    Two or moredetailed private business processes interacting
  • 30.
    Detailed private businessprocess relationship to Abstract Process
  • 31.
    Detailed private businessprocess relationship to Collaboration Process
  • 32.
    Two or moreAbstract Processes etc.BPMN 2.0 does not support any kind of organizational structure or data modeling: it is a process-oriented notation
  • 33.
    State University -Higher School of Economics, ERCIS / 2010BPMN 2.0BPMN 2.0: Diagram typesThere are three basic types of sub-models within an end-to-end BPMN modelProcesses (Orchestration), including:
  • 34.
  • 35.
  • 36.
  • 37.
  • 38.
    Collaborations, which mayinclude Processes and/or Choreographies
  • 39.
    A view ofConversations The structural elements of BPMN allow the viewer to be able to easily differentiate between
  • 40.
    State University -Higher School of Economics, ERCIS / 2010BPMN 2.0BPMN 2.0: ObjectsThe following object types are definedFlow Objects
  • 41.
  • 42.
  • 43.
  • 44.
  • 45.
  • 46.
  • 47.
  • 48.
  • 49.
  • 50.
  • 51.
  • 52.
  • 53.
  • 54.
    Annotation BPMN 2.0BPMN2.0: Collaboration/OrchestrationThe orchestration diagram represents the internal process tasks and the interaction between process participants
  • 55.
    BPMN 2.0BPMN 2.0:ChoreographyThe choreography diagram represents the dialog between process participants
  • 56.
    BPMN 2.0BPMN 2.0:ConversationThe conversation diagram represents the interaction between process participants
  • 57.
    State University -Higher School of Economics, ERCIS / 2010BPMN 2.0BPMN 2.0: Mapping to WS-BPELBPMN models can be transformed into executable codeNot all BPMN orchestration Processes can be mapped to WS-BPEL in a straight-forward way. That is because BPMN allows the modeler to draw almost arbitrary graphs to model control flow, whereas in WS-BPEL, there are certain restrictions such as control-flow being either block-structured or not containing cycles. For example, an unstructured loop cannot directly be represented in WS-BPEL.
  • 58.
    State University -Higher School of Economics, ERCIS / 2010BPMN 2.0BPMN 2.0: ToolsThe following tools support BPMN 2.0Intalio
  • 59.
  • 60.
  • 61.
  • 62.
  • 63.
    SAP Gravity (beta)State University - Higher School of Economics, ERCIS / 2010AgendaAgendaTo-dos for todayModel-oriented approach
  • 64.
  • 65.
  • 66.
    Modeling practiceState University- Higher School of Economics, ERCIS / 2010Enterprise 2.0Enterprise 2.0: DefinitionAndrew McAfee defines 7 key elements of E2.0Search: allowing users to search for other users or content
  • 67.
    Links: grouping similarusers or content together
  • 68.
  • 69.
    Tags: allowing usersto tag content
  • 70.
    Extensions: recommendations ofusers; or content based on profile
  • 71.
    Signals: allowing peopleto subscribe to users or content with RSS feeds
  • 72.
    Freeform function: nobarriers to authorship (meaning free from a learning curve or from restrictions)
  • 73.
  • 74.
    Socialfunction: stressing transparency(to access), diversity (in content and community members) and openness (to structure)
  • 75.
    Emergencefunction: requiring theprovision of approaches that detect and leverage the collective wisdom of the community Dion Hinchcliffe expands the list by adding
  • 76.
    State University -Higher School of Economics, ERCIS / 2010Enterprise 2.0Enterprise 2.0: ToolsSpecific social software tools for enterprise use includehypertext and unstructured search tools
  • 77.
  • 78.
  • 79.
  • 80.
    enterprise social bookmarkingfor tagging and building organizational knowledge
  • 81.
  • 82.
    collaborative planning softwarefor peer-based project planning and management ideas
  • 83.
    banks for ideation(idea generation)
  • 84.
  • 85.
  • 86.
    prediction markets forforecasting and identifying risks. SAP Gravity within Google Wave
  • 87.
    State University -Higher School of Economics, ERCIS / 2010AgendaAgendaTo-dos for todayModel-oriented approach
  • 88.
  • 89.
  • 90.
    Modeling practiceState University- Higher School of Economics, ERCIS / 2010AgendaAgendaTo-dos for todayModel-oriented approach
  • 91.
  • 92.
  • 93.