02291: System Integration

Transcription

1 02291: System Integration Week 10 Hubert Baumeister DTU Compute Technical University of Denmark Spring 2018

2 Last Week Principles of good design: layered architecture Software Development Processes Introduction to Examination Project

3 Contents Software Development Process Agile Modeling Model Driven Architecture More UML Diagrams

4 Resource Triangle Plan Driven Features Agile User User User Story Story Story Presentation Layer A D I T Application Layer Domain Layer Database / Infrastructure Layer Release date Time

5 extreme Programming (XP) Kent Beck Practices Kent Beck, Extreme Programming 1st ed.

6 Scrum file:///users/huba/desktop/scrum_process.svg 24 h 30 days Product Backlog Sprint Backlog Sprint Working increment of the software Wikipedia Robert Martin (Uncle Bob) about The Land that Scrum Forgot History about agile methods, the agile manifesto, and Scrum and its relationshop to XP 1 of 1 / :16

7 Lean Software Development Lean Production: Value for the customer Reduce the amount of waste in the production process Generate flow Waste: resources used which do not produce value for the customer time needed to fix bugs time to change the system because it does not fit the customers requirements time waiting for approval...

8 Leaf Composite Assembly Generating flow using Pull and Kanban WIP = Work in Progress Limit Work Item A D T I Queue WIP 3 Queue WIP 3 Queue WIP 3 Queue WIP Done Blah 4 2 3

9 Flow through Pull with Kanban Process controlling: local rules Load balancing: Kanban cards and Work in Progress (WIP) limits Integration in other processes Figure from David Anderson

10 Online Kanban Tool: Trello Electronic Kanban board useful for your project Kanban board the exam project example https: //trello.com/b/cqzwtirt/02291-example-lean Another Example https: //trello.com/b/4wddd1zf/kanban-workflow

11 Contents Software Development Process Agile Modeling Model Driven Architecture More UML Diagrams

12 Agile Modelling Traditional modelling: Requirements model, design model waterfall What is the role of modelling in agile software development? XP and documents XP and modelling Agile modelling

13 Agile Modelling Agile Modelling: values, principles, and practices References (Scott Ambler) Agile Modelling Scott Ambler, Wiley 2002

14 Agile Modelling Values Communication Simplicity Feedback Courage Humility

15 Agile Modelling Principles Core Principles Software is your primary goal Enabling the next effort is your secondary goal Travel light Incremental change Model with a purpose Multiple models...

16 Practices Core Practices Supplementary Practices Real Good Ideas

17 Core Practices Active Stakeholder Participation Collective Ownership Model in Small Increments Create Several Models in Parallel Iterate to Another Artifact Display Models Publicly Model With Others Prove it With Code Use the Simplest Tools... List of practices:

18 Disciplined Agile Development (DAD) Hybrid Agile development method evolved from Agile Modelling Agile Unified Process Based on SAFe: Scaled Agile Framework, Outside In Dev.: Focus on stakeholder requirements, Evo: Evolutionary Development

19 Iterative Processes: E.g. Rational Unified Process (1996)

20 DAD Focus on complete lifecycle

21 DAD DAD + Lean Initial Architectural Vision New features Identify, prioritize, and select projects Initial Vision and Funding Initial modeling, planning, and organization Business Roadmap, Technology Roadmap Envision the future Initial Require -ments Business Value Fixed Delivery Date Expedite Intangible Options Replenishment modeling session Work items are pulled when capacity is available to address them New features Daily work Demo Feedback Retrospective Learnings Strategy Coordination Meeting Enhancement Requests and Defect Reports Release solution into production Operate and support solution in production Inception Stakeholder vision Proven architecture F 10. T DAD L. strategies should enhance the ability of DAD teams to deliver business value to their stakeholders in a cost effec ve and mely manner. Unfortunately many exis ng IT governance strategies are based on a Construction Continuous stream of development Sufficient functionality Transition Production ready Delighted stakeholders intelligence approach supported via automated dashboards. Being enterprise aware has several important implica ons

22 Contents Software Development Process Agile Modeling Model Driven Architecture More UML Diagrams

23 Traditional Development to MDA

24 Traditional Development to MDA

25 Traditional Development to MDA

26 MDA Model Driven Architecture (MDA) Derive code from models through transformations Literature Anneke Kleppe, Jos Warmer, Wim Bast MDA Explained, 2003, Addison Wesley Professional MDA Website by OMG (

27 Example I: Attributes Platform Independent Model (PIM):

28 Example I: Attributes Platform Specific Model (PSM) for Java: Transformation PIM PSM Introduce getter and setter methods for each attribute

29 Example II: Associations PIM:

30 Example II: Associations PSM for Java Transformation PIM PSM Introduce an attribute for a navigable association

31 PIM for Rosa s Breakfast Service

32 MDA for Rosa s Breakfast Service Three PSM s Relational database model Enterprise Java Beans implementation Web interface

33 PSM Relational database model

34 PSM EJB

35 PSM Web Interface

36 Communication Bridge EJB relational DB

37 Principles of MDA: Models

38 Principles of MDA: Models

39 Principles of MDA: Models

40 Principles of MDA: Transformations

41 Principles of MDA: Transformations

42 Principles of MDA: Transformations Another example: Java Emitter Templates

43 Transformations Standard transformations Customised transformations

44 Example Transformation Transformation classes to DB schema (Pseudo Code) if the association A to B is adorned by an association class or the multiplicity at both ends is more-than-one then create a table representing the association class or the association and create foreign keys in both the table representing A and the table representing B referring this new table else if the multiplicity at one end is zero-or-one then create a foreign key in the table representing the class at that end, referencing the other end else // the multiplicity of the association is one-to-one create a foreign key in one of the tables, referencing the other end endif endif

45 MDA and Metamodels I

46 MDA and Metamodels II Short notation for the previous diagram

47 MDA and Metamodels III UML: Meta Object Facility (MOF) EMF: Eclipse Modelling Framework Software Engineering II

48 The MDA/MDA promise

49 The MDA/MDA promise

50 MDA Benefits Higher productivity Portability Interoperability Maintenance and Documentation Issues Modelling is abstraction Transformations need to add things Multiple models Behavioural models

51 Contents Software Development Process Agile Modeling Model Driven Architecture More UML Diagrams Object Diagrams Package Diagrams Deployment Diagram

52 Object Diagram Example Class Diagram Object Diagram

53 Object Diagram Purpose Snapshot of a running system objects: Instance of a class links: instance of an association Communication diagram

54 Update operation of Account State before executing update(n) State after executing update(n) {n + b >= 0} a: Account bal = b + n a: Account bal = b h1: History bal = b bal = m h: History bal = m prev h: History

55 Notation Variant 1: an object with name and class Variant 2: an anonymous object of a class Variant 3: a named object of unknown class

56 Notation Value Specifications Slots Links to other objects

57 Package Diagram Groups model elements: classes, objects, use cases, packages,... Structures the model, not the system c.f. component diagram Define a name space P::C means class C in package P Java packages

58 Package notation Notations for packages

59 Examples Dependencies between packages

60 Deployment Diagram Martin Fowler, UML Distilled

61 Next Week Validation of models: Model checking Summary of the course