INF5120 Modellbasert Systemutvikling Modelbased System development

Transcription

1 INF5120 Modellbasert Systemutvikling Modelbased System development Lecture 10: Arne-Jørgen Berre or 1

2 Course parts (16 lectures) n January February (1-7) (BAE/WebRatio): n MDE-1: Introduction to INF5120 n MDE-2: Modeling structure and behaviour (UML and UML 2.0 and metamodeling) ( B. Hjelle) n BAE-1: Business Architecture Business Model Canvas - Strategyzer tool. n SAE-1: WebRatio for Mobile App development (Get an App up and running!) n BAE-2: Essence, Scrum, User stories and Use cases 2.0, Backlog, with Someone n BAE-3: BPMN process, VDML and UML Activ.Diagrams, (MD/EA, Smaply and Balsamiq) n BAE-4: Service Design, AT ONE,Touchpoints, UI, UX, Smaply and Balsamiq (Ragnhild) n Oblig 1: BA Spec, WebRatio App1 (individual) (end of February, March 7 th ), Agile Scrum n March (8,9) (MDE/IFML/Client-Side): n MDE-3: Model driven engineering Metamodels, DSL, UML Profiles, EMF, Sirius Editors n SAE-2: IFML Interaction Flow Modeling Language, WebRatio advanced n April (10, 11,12,13) (BPMN, SAE/UML/Server-side): n SAE-3 (Lecture 10, April 4 th ): BPMN and WebRatio BPM platform/magicdraw BPMN n Oblig 2: Sirius DSL Editor for IFML +/- (indivual), WebRatio/IFML App2 UI (simple) (April 11 th ) n SAE-4: UML Service Modeling, ServiceML,SoaML, REST, UML 2.0 Composition, MagicDraw n MDE-4: Guest lecture: DSL and ThingML, Franck Fleurey) and Web Meet with project from Florida Atlantic University, FAU, Boca Raton, FL, USA (at 1700) n SAE-5: MDE transformations, Non Functional requirements OCL and PLanguage n Oblig 3: SA Spec (More models), WebRatio/IFML App 3 Server (May 2 nd ) n May (14,15,16): (Bringing it together) n SAE-6: Final WebRatio App demo and discussion day (May 2 nd ) n MDE-5: Enterprise Architecture, TOGAF, UPDM, SysML DSLs etc. Big picture n MDE-6: Conclusions/Summary of the course n Exam (4 hours), (June 6 th ) 2

3 Relevant Essence-related practice descriptions Business Model Canvas design - Strategyzer Value Proposition Design - Strategyzer AT ONE Service Design Workshops SymphonicalSomeOne/UpWave Service Journey designs Smaply, Vocabulary, Terminology, Information, Ontology designs - MagicDraw User Story and Use Cases Business ProcessModeling with BPMN 2.0 UI Mockup/Concept designs Balsamiq Scrum development practices IFML based developmnet WebRatio Graphical Editor design Sirius.. See also 3

4 Customer Journey & adapted BPMN 4

5 OMG Modeling languages and Zachman Framework Data (What) Function (How) Network (Where) People (Who) Time (When) Motivation (Why) Scope (Contexts) Business (Concepts) System (Logic) SBVR List of things important to business Semantic Model ODM Logical Data Model List of processes that the business performs Business Process Model IFML Application Architecture VDM SoaML List of locations which the business operates Business Logistics System Distributed System Architecture BPMN CMPM OSM List of organizations important to the business Workflow Model Human Interface Architecture List of events/cycles important to the business BPMN Master Schedule Process Structure BMM List of business goals/strategies Business Plan SBVR Business Rule Model Technology (Physics) Component (Assemblies) IMM (CWM) Physical Data Model UML Data Definition SoaML System Design Program UML Technology Architecture Network Architecture Presentation Architecture Security Architecture Control Structure DTFV Timing Definition Rule Design Rule Definition Operation (Instances) Data Behaviour Data Function Network Organization Schedule Strategy Service User interaction Process 5

6 BPMN (Business Process Model and Notation) See also: INF Process improvement and agile methods in systems development and

7 7

8 The need of process modeling n Process improvement is created with better understanding, communication, and organization n Modeling is an important aspect of these n Modeling translates verbal or tacit understanding into simple metaphors that assist these objectives n A metaphor is a way of reducing the dimensions of the description of a process to a more understandable and visible basis n Metaphors bridge complex concepts and build an understanding of the relationships between them

9 Three manners of thinking - Process n Can be defined as an organization of activities that happen in a series, relevant to a business s goals and objectives n At a fundamental level, a process diagram represents a single instance of a process n For example, a purchase order process reflects an instance of a single purchase order, not an organization processing their work load of purchase orders

10 Three manners of thinking - Event n From another perspective, a process is actually a connected sequence of events that respond to states, causes, and conditions n In an event-based view, the process is a linkage of the transitions from one processing state to another

11 Three manners of thinking - Decision n From yet another viewpoint, all activities and responses to events should be the result of a conscious decision by the organization. n The decisions are an assemblage of business rules n A process model is not merely a scenario; n It is a scenario that exists within the context of the process, events, and decisions n All these different perspectives are appropriately incorporated in a robust process model

12 Business Process n A business process is a sequence of activities that carry out a business goal n A business process is an organized, coordinated flow of activities, conducted by participants, acting on and deciding with data, information, and knowledge, to achieve a business goal

13 Business rules n A business rule is a mediator of information in computer systems for decision-making process participants, such as managers, employees, and salespeople n More accurately, from the viewpoint of the business process: n a business rule is an atomic logic step that uses data and knowledge to evaluate part of a proposition about a process decision n The business rule meets the process through the decision when you change the business rule, you change decision outcome n Think of a set of business rules as conditions that match data and create conclusions

14 Business Event n In a modern process modeling approach, opportunities, conditions, and factors that events must respond to are handled or managed with business events n A business even is an event that is meaningful for conducting commercial, industrial, and governmental, or trade activities n In BPMN, we have start, intermediary, non-interrupting, and end events n Correspond directly to a process instance

15 What is BPMN?

16 BPMN example

17 BPMN 2.0 and SoaML tools today n BPMN 2.0 n Signavio has 2.0 Conversation and Choreography diagrams a SaaS solution n Most BPMN 1.2 are doing stepwise migration, making existing parts 2.0 compliant n SoaML (in most UML tools) n Magic Draw (Cameo), Enterprise Architect, IBM RSA/RSM, Modelio, n We will use MagicDraw - Cameo Enterprise Architecture - version in the course in spring 2015

18 18

19 19

20 20

21 21

22 22

23 23

24 24

25 25

26 BPMN History n BPMN 1.0 (BPMI) Mai 2004 n BPMN1.x n BPMN 1.1 (OMG) Januar 2008 n BPMN 1.2 (OMG) Januar 2009 n BPMN 2.0 final Juni 2010 n 26

27 History for BPMN

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

29 BPMN requirements

30 BPMN Building blocks of the foundation n Some of the concepts are part of the definitions of business process n An event-activated flow of coordinated activities, conducted by participants, and acting on and deciding with data, information, and knowledge that achieve a goal n Participant, Activity, Flow, Process event, Data

31 Participant n A participant is an actor or a person that interacts in a process n The actor includes any human, digital, or virtual resource that involved in a business process

32 Participant examples People participants: n Inventory receipt clerk inspecting the order n Employee filling out a request n Patient in hospital n Manager approving a requisition n Technician restoring a disk drive System Participants: n SAP, PeopleSoft n DB server n Rules engines n A Web service n A custom-build UI n A telephony queuing switch

33 Activity n An activity is work the participant performs with business process n Is the basic units of process work, can be n Atomic (lowest level, indivisible unit of work) n Non-atomic (involving many steps) n Process and subprocesses are compound activities n In BPMN, the types of process activities include: n Tasks is the atomic activity n Subprocesses is compound activity, might contain other activities

34 Activity examples n An activity can be manual, as a human participant completes the activity, or n It might be automated by a system participant n Examples: n Inspecting material delivery n Restoring a server n Completing contract requisition n Reviewing and approving a requisition n Reviewing loan application

35 Flow n Is the order (and data) in which the activities or process steps are performed n Multiple flows might occur within multiple participants roles n Two types of flows in BPMN diagram n Sequence defines the order in which activities are performed for any given process participants n Sequence flow never occurs between participants in different pools n Message defines the flow of information and message between participants within a process n Messages never occur within the same pool

36 Flow: transition n Describes the hand-off between activities n Transition means that one activity has stopped and another has started n Transition never occurs between multiple participants n e.g,a work area with people and workstations for each person s activities (tasks) n As each task is completed, the person transitions to the next task at another workstation n Any communication is an interaction, not a transition

37 Flow: interaction n Is the communication between participants n Interactions occur between two or more participants in the form of message n Interactions never occur from one participant back to itself n Note: a flow from one participant back to itself is an activity transition, not an interaction

38 Process Event n An event is something that happens n A process event defines a point where the process is either started, stopped, halted, or continued n Events define occurring activities of interest n Participant actions, choices, or activities define or create events n Examples: n Contract order submitted n DB unavailable n Requisition rejected

39 Data n Data shapes in BPMN are artifacts, meaning, or an effect of process events occurring n Data is never a cause of process activity occurring. Events trigger activity, resulting in data n Data mostly originates from events, for example: n An airplane is cleared for a final approach. This event is added to the flight log (data) n The log data is a chorological series of event snapshots

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

41 Complete Set of Diagram Elements, Events nan 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.

42 Complete Set of Diagram Elements, Activities, Cont. na Sub-Process can be in an expanded form that shows the process details of the a lowerlevel set of activities.

43 Complete Set of Diagram Elements, Gateways ngateways 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.

44 BPMN Diagram elements

45 Diagram elements (2)

46 Activities

47 Task

48 Sub-processes

49 Events

50 Start Events

51 Intermediate Events

52 Intermediate events (normal flow)

53 Intermediate events (linked to Boundary)

54 End events

55 Gateways

56 Exclusive Gateways

57 Exclusive Gateways, based on data

58 Exclusive Gateways, based on events

59 Inclusive Gateways

60 Complex Gateways

61 Complex Gateways

62 Parallell Gateways

63 Conectors

64 Sequence flow

65 Conditions in sequence flow

66 Default sequence flow

67 Message flow

68 Associations

69 Swim lanes

70 Pool

71 Lanes

72 Artifacts

73 Text annotations

74 Data objects

75 Groups

76 Extended artifacts

77 Normal flow

78 Link events

79 Process leves

80 Data flow

81 Exceptions

82 Compenations and transacations

83 Loops

84 Timers

85 Ad hoc processes

86 EPC og BPMN EPC EPC BPMN

87 Orchestration versus Choreography

88 Orchestration

89 Choreography

90 Example

91 Process information

92 Proposal

93 Sources n The (beta) BPMN 2.0 specification - n Bruce Silver n Rick Geneva n Stephen White - n BPMN 0.9, 1.0, 1.1, 1.2,..

94 BPMN Examples

95

96

97

98

99

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

101

102

103

104

105

106 BPMN 2.0: Major changes from BPMN1.x n Notational changes n New diagrams for Choreography and Conversation n New event-types (escalation, ) n Non-interrupting events n Event sub-process n Call Activity replaces linked/reusable activity n Technical changes n Formal metamodel specified in UML n Interchange formats for semantic model interchange (XMI, XSD) n Interchange formats for diagram interchange (XMI, XSD) n XSLT transformations between XMI and XSD formats

107 Process diagram n n n Flowchart view to sequence activities within an organization Support the modeling of simple processes Enhanced by BPMN to handle more complex concepts, such as exception handling, transactions, and compensation.

108 Collaboration diagram n n Provides a view of the interactions (flow of messages) between two or more business partners (Participants). Collaborations can be combined with Processes to show how the interactions are related to the internal Process activities.

109 Collaboration diagram example

110 Conversation diagram n n Allows a modeler to group Collaboration interactions between two or more Participants, which together achieve a common goal, e.g. negotiate delivery The grouping can be based on business keys such as customer id or shipping id.

111 Conversation diagram example n Allows a modeler to group Collaboration interactions between two or more Participants, which together achieve a common goal, e.g. negotiate delivery n The grouping can be based on business keys such as customer id or shipping id.

112 Corresponding choreography example 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.

113 Choreography diagram n n 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.

114 Activity types - visualised

115 Multi-instance activites - visualised Parallel Serial

116 New Artifact Shapes Data Artifact Data Artifact Collection Data Artifact Input Data Artifact Output Data Source Artifact

117 New Event Gateways n Current event-based gateway n Event Based Exclusive Intermediate n Event Based Exclusive Start Gateway n Event Based Inclusive Start n Event Based Inclusive Intermediate

118 Non-interrupting Intermediate Events n Boundary intermediate events in BPMN are interrupting n BPMN2.0 introduces new non-interrupting intermediate events n Boundary events n Catching n Example of use

119 Non-interrupting Event Sub-process (expanded)

120 Non-interrupting Event Sub-process (collapsed)

121 Interrupting Event Sub-process

122 BPMN 2.0 Event Gallery