1. INF5120 BMM and BPMN ”Modelbased System development”
INF5120 Model based System Development
INF5120 BMM and BPMN ”Modelbased System development”
Lecture 2:
Arne-Jørgen Berre

2. Lecture plan
1: 19/1: Introduction to MBSU, MDA, OO and Service/SOA modeling, Overall EA (AJB)
2: 26/1: MS I: Business Process Modeling (CIM) - with BPMN and BMM (AJB), Objecteering UML Modeler
3: 2/2: MS II: UML2 and SysML, Objecteering SOA and Scope, – Collaboration /Component models
4: 9/2: MDE I: Metamodeling , DSL and UML profiles, MDA technologies (XMI, Eclipse, EMF/GMF) (GO/BRE)
5: 16/2: MS III: SoaML I (PIM) and Requirements modeling , CIM->PIM,
6: 23/2: MS IV: Method Engineering and SPEM / EPF (BRE)
7: 2/3: MS V: SoaML II and Service Design (AJB)
8: 9/3: MDE II: Model transformations with MOScript, (ATL and QVT) – and JEE (GO)
9 :16/3:: MDE II: Code generation with MOFScript and other technologies (GO)
10: 23/3: MDE IV: PIM and Web Services teknologi (PSM) for SOA with WSDL/XML/BPEL (PSM) (BRE)
11: 30/3: MDI I: Model Driven Interoperability I (AJB)
EASTER
12: 20/4: MDE V: Open ArchitectureWare/Kermeta, Microsoft OSLO etc. (Neil, Franck, Anthe)
13: 27/4: MDI II: Model Driven Interoperability - II - Ontologies, Semantic web and Semantic Modeling (AJB)
14: 4/5: Course summary
Exam: May 29th, (Friday)
AJB – Arne J. Berre
BRE – Brian Elvesæter
GO – Gøran Olsen

3. BMM and BPMN on the CIM level
Aspect
Level
Information
Service
Process
Rules
Events
Organization
Goals
NFA
CIM
BPMN
BMM
CIM2PIM
PIM
PIM2PSM
PSM

4. Business Motivation Model
The Business Motivation Model (BMM) is a meta-model of the concepts essential for business governance.
underlying principle is “Businesses are driven, not by change, but by how they decide to react to change”
vocabulary for governance
influencer
assessment
business policy
strategy
tactic
goal
Governance
Governance is necessary for the successful adoption of SOA partly because of the cross-organizational nature of SOA where service funders, designers, implementers, maintainers, or consumers are not located in the same organization, business, IT department, LOB, division, or enterprise.

5. two major areas of the Business Motivation Model
The first is the Ends and Means of business plans. Among the Ends are things the enterprise wishes to achieve — for example, Goals and Objectives. Among the Means are things the enterprise will employ to achieve those Ends — for example, Strategies, Tactics, Business Policies, and Business Rules.
The second is the Influencers that shape the elements of the business plans, and the Assessments made about the impacts of such Influencers on Ends and Means (i.e., Strengths, Weaknesses, Opportunities, and Threats).

6. Simplified View of BMM BMM and GRC
What you decided your Enterprise should do
Means
Ends
Courses of Action
Business Operations
Business Processes
Business Rules
Responsibilities
Resources
Services
References to
Directives
Govern the Courses of Action
Influencers
Assessments
BMM and GRC
© Model Systems, September 2008

7. Core concept for BMM

8. BMM Core Concepts
BMM and GRC
© Model Systems, September 2008

9. BMM meta-model in GMF

10. Buyers ends

11. Sellers ends

12. Buyer’s means

13. Seller’s means

14. High-Tech Marketing Business Plan

15. High-Tech Marketing Business Plan

16. Business Motivation Model (BMM) with MeansRealizations

17. Buyer/Seller reference example

18. What is BPMN (Business Process Modeling Notation) ?

19. BPMN example

20. EPF Composer Note: This is also a Business Process – for Software dev.
EPF Composer is a tool platform for process engineers, project leads, project and program managers who are responsible for mainteining and implementing processes for development organizations or individual projects
Aims to:
provide for development practitioners a knowledge base of intelectual capital that allows them to browse, manage and deploy content.
provide process engineering capabilities by supporting processe engineers and project managers in selecting, tailoring, and rapidly assembling processes for their concrete development process.
Note: This is also a Business Process – for Software dev.
The knowledge base can be used for reference, knowledge and form the basis for a development process.
EPF Composer is designed to be a content management system, rather than a document management system. It provides process building, the capability paterns from last slide, that represent best development practicies for specific disciplines, technologies or development styles.

21. BPMN (Business Process Modeling Notation)

22. What is BPMN ?

23. History for BPMN

24. Technology Implementation
BPMI.org Hourglass
Audiences:
Business Environment
Purposes:
Strategy Consultants
Execution
Modeling
Business Analysts
BPMN BP
Process Designers
Focus 
Scope 
BPEL
System Architects
, Java
Software Engineers
Technology Implementation

25. BPMN requirements

26. Core Set of Diagram Elements
The core set of modeling elements enable the easy development simple Business Process Diagrams that will look familiar to most Business Analysts (a flowchart diagram)

27. Complete Set of Diagram Elements, Events
An Event is something that “happens” during the course of a business process. These Events affect the flow of the Process and usually have a trigger or a result. They can start, interrupt, or end the flow.

28. Complete Set of Diagram Elements, Activities, Cont.
A Sub-Process can be in an expanded form that shows the process details of the a lower- level set of activities.

29. Complete Set of Diagram Elements, Gateways
Gateways are modeling elements that are used to control how Sequence Flows interact as they converge and diverge within a Process. If the flow does not need to be controlled, then a Gateway is not needed.

30. BPMN Diagram elements

31. Diagram elementer (2)

32. Activities

33. Task

34. Sub-processes

35. Events

36. Start Events

37. Intermediate Events

38. Intermediate events (normal flow)

39. Intermediate events (linked to Boundary)

40. End events

41. Gateways

42. Exclusive Gateways

43. Exclusive Gateways, based on data

44. Exclusive Gateways, based on events

45. Inclusive Gateways

46. Complex Gateways

47. Complex Gateways

48. Parallell Gateways

49. Conectors

50. Sekvens flyt

51. Conditions in sequece floww

52. Default sekvens flow

53. Message flow

54. Associations

55. Swim lanes

56. Pool

57. Lanes

58. Artifacts

59. Text annotations

60. Data objects

61. Groups

62. Extended artifacts

63. Normal flow

64. Link events

65. Process leves

66. Data flow

67. Exceptions

68. Compenations and transacations

69. Loops

70. Timers

71. Ad hoc processes

72. EPC og BPMN
EPC
EPC
BPMN

73. Orkestering versus Koreografi

74. Orkestrering

75. Koreografi

76. Eksempel

77. Prosess informasjon

78. Forslag

79. BPMN Eksempler …

80. BPMN eksempel – Buyer/Seller

86. Eksempel - legekontor
A text description of the choreography was presented as so:
1) Patient send a "I want to see doctor" message to the Receptionist
2) Receptionist send a "Are you available ?" message to a a list of Doctors
3) One doctor send a "I'm available" message to the Receptionist.
4) Receptionist send a "I'll book you" message to the Doctor.
5) Receptionist send a "Go see doctor" message to the Patient
6) Patient send a "I feel sick" message to Doctor
7) Doctor send a "Prepare this medicine" message to Receptionist
8) Doctor send a "Pickup your medicine and you can leave" message to Patient
9) Patient send a "I need my medicine" message to Receptionist
10) Receptionist send a "Here is your medicine" message to Patient

92. Next Lecture – February 2nd, 2009
UML 2.0
Collaboration Diagrams
Port Connector Models and Components
SysML
Use of Softeam UML/BPMN modeling tool