INF Lecture plan

Transcription

1 INF5120 Modellbasert Systemutvikling Modelbased System development Lecture 3: Arne-Jørgen Berre or 1 INF Lecture plan Part I: SSI Service Innovation and Agile Service/Software Engineering Part II: SSMDE Model Driven Engineering Part III Model Driven Interoperability and ADM 1: 16/1: Introduction to Model Based System Development (INF5120) 2: 23/1: SIE I: Enterprise Architecture, Role modeling-collaboration and Value Networks Verna Allee (VNA) 3: 30/1: SIE II:: Business Process Modeling with BPMN 2.0 and Business Model Innovation - Peter Lindgren (BMI) 4: 6/2: SIE III: AT ONE Service Design, Agile User-oriented design with Use cases/stories and UI models 5: 13/2: SIE IV: Service modeling with SoaML Service modeling - Design, patterns 6: 20/2: SIE V: Information Modeling with UML and Design with DCI - Design, patterns 7: 27/2: MDE I: Software Process Model Frameworks Essence/SEMAT, SPEM, EPF and ISO Shihong Huang/Brian Elvesæter 8: 5/3: MDE II: Metamodels, Domain specific languages and UML profiles (Franck Fleurey) 9: 12/3: MDE III: Metamodeling, MDLE and DSL Tools (EMF, GMF, ATL, Kermeta) 10: 19/3: MDE IV: Model transformations - MOFScript, QVT DSLs with examples 11: 26/3: MDE V: Internet Service Architectures - with BPM/BPEL and SOA/Cloud transformations 2/4, 9/4: EASTER 12: 16/4: MDE VI: User Interface Modeling IFML etc. - ESITO 13: 23/4: MDI I: Semantic technologies, Ontologies and Semantic annotations, Rules/SBVR 14: 30/4: MDI II: Model Driven Service Interoperability 15: 7/5: MDI III: ADM and Migration to Cloud computing 16: 13/5: Conclusion and Summary for INF Preparation of Exam Exam: Monday June 4th, 2011, (4 hours) 2 1

2 INF5120 Oblig/Exercise plan : 16/1: None 2: 23/1: Guest lecture: Value Networks Verna Allee (VNA) 3: 30/1: Guest lecture: Business Model Innovation - Peter Lindgren (BMI) Establish groups 4: 6/2: AT ONE initial exercise overall approach for Oblig 1 myservicefellow 5: 13/2: Group presentation 6: 20/2: Group presentation 7: 27/2: Group presentation 8: 5/3: MDE Tools introduction Oblig 2 intro 9: 12/3: MDE Tools II - EMF 10: 19/3: MDE Transformation tools 11: 26/3: MDE V: Internet Service Architectures - with BPM/BPEL and SOA/Cloud transformations 2/4, 9/4: EASTER 12: 16/4: MDE User Interface tools ESITO o.a. 13: 23/4: Oblig 2 questions 14: 30/4: Oblig 2 delivery 15: 7/5: Oblig 2 summary 16: 13/5: Conclusion and Summary for INF Preparation of Exam Exam: Monday June 4th, 2011, (4 hours) 3 Outline SiSaS methodology, sisas.modelbased.net Oblig 1 NEFFICS methodology, neffics.modelbased.net BPMN 2.0 Business Model Innovation 2

3 SiSaS SINTEF Software as a Service Methodology, sisas.modelbased.net 5 SiSaS Disciplines and Practices 6 3

4 7 8 4

5 Oblig 1 Group work Service Innovation and Design Service Innovation and Design - for the Informatics Department and students at the University of Oslo -Value Networks (23/1) -BPMN processes (30/1) -Business Model Innovation (30/1) -AT ONE methodology (6/2) -Service Innovation/identification/design/specification (13/2) -Any areas for innovative services/apps/applications? -Use Modelio UML tool, -Establish groups today 9 Oblig 1 Group work Service Innovation and Design Service Innovation and Design - for the Informatics Department and students at the University of Oslo Groups of 2-4 persons Select one focus area within the processes and services of Ifi that you would like to concentrate on. Course registration, Course interaction, Study lab,.. Consider all touchpoints between you and Ifi. 10 5

6 BPMN (Business Process Model and Notation) What is BPMN? 6

7 BPMN example BPMN 2.0 and SoaML tools today BPMN 2.0 Signavio has 2.0 Conversation and Choreography diagrams a SaaS solution Most BPMN 1.2 are doing stepwise migration, making existing parts 2.0 compliant SoaML (in most UML tools) Magic Draw (Cameo), Enterprise Architect, IBM RSA/RSM, Modelio, 7

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

9 BPMI.org Hourglass Audiences: tegy Consultants Business Analysts Business Environment BPMN Purposes: Modeling rocess Designers Focus BP Scope System Architects ftware Engineers BPEL Technology Implementation Execution BPMN requirements 9

10 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) 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. 10

11 Complete Set of Diagram Elements, Activities, Cont. A Sub-Process can be in an expanded form that shows the process details of the a lowerlevel set of activities. 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. 11

12 BPMN Diagram elements Diagram elements (2) 12

13 Activities Task 13

14 Sub-processes Events 14

15 Start Events Intermediate Events 15

16 Intermediate events (normal flow) Intermediate events (linked to Boundary) 16

17 End events Gateways 17

18 Exclusive Gateways Exclusive Gateways, based on data 18

19 Exclusive Gateways, based on events Inclusive Gateways 19

20 Complex Gateways Complex Gateways 20

21 Parallell Gateways Conectors 21

22 Sequence flow Conditions in sequence flow 22

23 Default sequence flow Message flow 23

24 Associations Swim lanes 24

25 Pool Lanes 25

26 Artifacts Text annotations 26

27 Data objects Groups 27

28 Extended artifacts Normal flow 28

29 Link events Process leves 29

30 Data flow Exceptions 30

31 Compenations and transacations Loops 31

32 Timers Ad hoc processes 32

33 EPC og BPMN EPC EPC BPMN Orchestration versus Choreography 33

34 Orkestrering Koreografi 34

35 Eksempel Prosess informasjon 35

36 Forslag BPMN Eksempler 36

37 37

38 38

39 Example doctor s office 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 39

40 40

41 41

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

43 Process diagram 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. Collaboration diagram 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. 43

44 Collaboration diagram example Conversation diagram example 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. 44

45 Corresponding choreography Provides a flowchart view to example sequence interactions between Participants Choreographies define a business contract or protocol to which the Participants agree to follow during real-time interactions. Content EA and the Zachman Framework Architectural Frameworks - (IEEE/ 1471/ISO 42010, UML 2.x, TOGAF, UPDM (DODAF/MODAF) OO Modeling and abstraction levels Role modeling UML Collaboration modeling GRASP - General Responsibility Assignment Software Patterns VNA Value Network Analysis, Verna Allee

46 Zachman Framework for Enterprise Architecture (IBM, 1987) VA Enterprise Architecture DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why Based on work by John A. Zachman SCOPE (CONTEXTUAL) Things Important to the Business Processes Performed Business locations Important Organizations Ev ents Significant to the Business Business Goals and Strategy SCOPE (CONTEXTUAL) Planner Entity = Class of Business Thing Function = Class of Business Process Node = Major Business Locations People = Major Organizations Time = Major Business Event Ends/Means = Major Business Goals Planner ENTERPRISE MODEL (CONCEPTU AL) Semantic Model Business Process Model Business Logistics System Work Flow Model Master Schedule Business Plan ENTERPRISE MODEL (CONCEPTU AL) Owner Ent = Business Entity Proc = Business Process Node = Business Location People = Organization Unit Time = Business Event Rel = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle End = Business Objectiv e Means = Business Strategy Owner SYSTEM MODEL (LOGICAL) Logical Data Model Application Architecture Distributed System Architecture Human Interface Architecture Processing Structure Business Rule Model SYSTEM MODEL (LOGICAL) Designer Ent = Data Entity Rel = Data Relationship Proc = Application Function Node = IS Function People = Role I/O = User Views Link = Line Characteristics Work = Deliverable Time = System Event End = Structural Assertion Cycle = Processing Cycle Means = Action Assertion Designer TECHNOLOGY MODEL (PHYSICAL) Physical Data Model System Design Technology Architecture Presentation Architecture Control Structure Rule Design TECHNOLOGY MODEL (PHYSICAL) Builder Ent = Segment/Table Rel = Pointer/Key Proc = Computer Function Node = Hardware/Softw are People = User I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Time = Ex ecute End = Condition Cycle = Component Cycle Means = Action Builder DETAILED Data REPRESENTATIONS Definition (OUT-OF-CONTEXT) Program Netw ork Architecture Security Architecture Timing Definition Rule Design DETAILED REPRESENTATIONS (OUT-OF-CONTEXT) Sub-Contractor Ent = Field Rel = Address Proc = Language Statement Node = Addresses I/O = Control Block Link = Protocols People = Identity Work = Job Time = Interrupt Cycle = Machine Cycle End = Sub-Condition Means = Step Sub-Contractor FUNCTIONING ENTERPRISE Data Function Netw ork Organization Schedule Strategy FUNCTIONING ENTERPRISE Ent = Rel = Proc = I/O = Node = Link = People = Work = Time = Cycle = End = Means = DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why

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

48 Interaction Structure Function Coordination Information Quality ASD Framework with INF5120 Modeling techniques Requirements Design UI Interactions Role Models SoaML Roles Context and Goals Functions collaboration BPMN Processes Goal oriented Use cases/stories UML Class Information Ontologies OCL EFA Extra Functional Aspects Implementation Interface Actors Tasks Orchestration Data Model Driven Architecture/MDE QoS SLA Infrastructure Channels Resources Executors Workflows Stores and Messages Monitoring, adaptation Businss Model Innovation The Alexander Osterwalder canvas 48

49

50 EU project, , 4 Meuro, led by SINTEF & Induct Business Model Innovation Peter Lindgren, Univ. of Aalborg Denmark

51 Business Model Frameworks with Modeling support from NEFFICS Building block Incremental innovation Do what we do but better Radical innovation Do something different Value proposition Offering more of the same Offering something different (at least to the company) Target customer Existing market New market Value chain architecture [Internal] Competences Exploitation (e.g. internal, lean, continuous improvements) Familiar competences (e.g. improvement of existing technology, HR, organizational system, culture) Exploration (e.g. open, flexible, diversified) Disruptively new, unfamiliar, competences (e.g. new emerging technology, new HR skills, organizational systems, culture) Network Partners Familiar (fixed) network New (dynamic) networks (e.g. alliance, jointventure, community) Relations Profit formula Continuous improvements of existing relations (e.g. channels) Existing processes to generate revenues followed-by/or incremental processes of retrenchments and cost cutting New relations, relationships (e.g. channels physical, digital, virtual, personal) New processes to generate revenues followedby /or disruptive processes of retrenchments and cost cutting 114 NEFFICS BMI (1/2) 51

52 NEFFICS BMI (2/2) Basis for VDML standardisation Porter Value Chain Organization Model Value Stream Capability Model VDML Value Network Business Model Shared Services REA-Resource Event Agent 52

53 Osterwalder versus NEFFICS + new idea: Enhance role collaborations (with value networks) as a focal point for relations supporting enactement and simulation of the model Value network Value stream Value chain Relations Network Competences Role collaborations Target customers Value proposition Profit formula (Cost+Revenue) REA (ownership - POA) Next Lecture February 6th, 2012 Service Innovation and Design AT ONE Requirements modeling and Use cases User stories Service Design, Service Innovation and User Experiences Oblig 1 further details