The document discusses model-oriented approaches, BPMN 2.0, and Enterprise 2.0. It describes the model-driven architecture approach, its history and key aspects. It outlines the different types of diagrams in BPMN 2.0 including processes, collaborations, and choreographies. It defines the key elements of Enterprise 2.0 including search, links, authoring, tags, and social functions. It also lists example tools that support these approaches.
6. MDA intends to promote the use of models as fundamental way of designing and implementing different kinds of systems.
7.
8. 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.
11. 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
12.
13. 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.
14.
15. Analysis Tool: A tool used to check models for completeness, inconsistencies, or error and warning conditions. Also used to calculate metrics for the model.
16. Transformation Tool: A tool used to transform models into other models or into code and documentation.
17. 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.
18. Test Tool: A tool used to "test" models as described in Model-based testing.
19. 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.
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.)
32. Two or more Abstract Processes etc.BPMN 2.0 does not support any kind of organizational structure or data modeling: it is a process-oriented notation
55. BPMN 2.0 BPMN 2.0: Choreography The choreography diagram represents the dialog between process participants
56. BPMN 2.0 BPMN 2.0: Conversation The conversation diagram represents the interaction between process participants
57. State University - Higher School of Economics, ERCIS / 2010 BPMN 2.0 BPMN 2.0: Mapping to WS-BPEL BPMN models can be transformed into executable code Not 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.
75. Emergencefunction: requiring the provision of approaches that detect and leverage the collective wisdom of the community Dion Hinchcliffe expands the list by adding