Domain-Frontier approach to. MDA based. software development

Transcription

1 Domain-Frontier approach to MDA based software development

2 Contents! Software Development Yesterday, Today and Tomorrow! Domain-Frontier Paradigms and Cornerstones! Domain-Frontier Development Process Map! Example Rosa s Breakfast Service! Future Work! Bibliography

3 Software Development Yesterday, Today and Tomorrow! Software Engineering History Continual Raise of Abstraction

4 Software Development Yesterday, Today and Tomorrow! Software Project Development Gradual Lowering of Abstraction

5 Software Development Yesterday, Today and Tomorrow Software Engineering Evolution and Software Product Evolution Follow the Same Paths, but in Opposite Directions Future Creative Efforts Manual Efforts Scientific Facts Automatic Compilers

6 Software Development Yesterday, Today and Tomorrow! Software Trends Today - Visual Programming Languages - Frameworks and Patterns - Pervasive Services Solutions - Partial Code Generators - Specific Domain Complete Generators, etc.

7 Software Development Yesterday, Today and Tomorrow! MDA Unifies and Standardizes Modern Trends in Software Development! Formalized System Analysis Method?

8 Software Development Yesterday, Today and Tomorrow! A Glimpse to the Future - Formal Problem (Requirements) Definition Language? - Will Domain Experts Be Able to Specify and Produce Software?

9 Domain-Frontier Aproach Paradigms! MOF and UML Unified Modeling Language - Standard Notation - Standard Models Repository -Executable UML! Aspect Oriented Analysis and Design - Overall Separation of Concerns - Problem Level: Domain and Frontier - System Level: Domain and Pervasive Services! Model Driven Architecture -Model Centric Development - Model Transformations, etc.

10 Domain-Frontier Aproach Cornerstones! Abstraction Management - Clear Abstraction Milestones: -Problem "Architecture " Solution - Early Milestones without ambiguity! Dynamics at High Level Model - Capture Behaviour from Begining! Focused on System External Interface - Low Domain-Frontier Correlation - User Interface Deserves Special Attention! world frontier domain

11 Domain-Frontier Models! Problem Model ( CIM ) UML with OCL - Business Process Model - Use Case Model - Conceptual Model with States - Sequence Diagrams - OCL Code! Architecture Model ( PIM ) UML with Actions - Analysis Model (Boundary, Control, Entity) with States - Sequence Diagrams - Action Semantics Code! Solution Model ( PSM ) UML with Target Language - Class Model - Component Model - Target Platform Code

12 Development Process Map! Phases and Milestones! Activities! Roles! Process Models (Artifacts)! Transformations

13 Development Process Map (cont.) Milestones:! Problem Modelling - Requirements Understood - Architecture Generated! Architecture Tuning - Design Generated - Scenarios Tested Problem Modelling Architecture Tuning! Solution Tuning - Solution Generated and Tested Solution Tuning! Solution Implantation - Solution Installed Solution Implantation

14 Problem Modelling Phase BreakfastOrder - deliveryaddress: Address Customer - deliverydate: Date +orders +c ust omer - accountnumber: Integer - deliverytime: Date - address: Address - discount: Real 1..* 1 - orderdate: Date + c reat eorder() + calculateprice() +order 1 +breakfast s 1..* Business Analyst Customer Customer Log-in «goal» Register Customers' Orders Breakfast Order Process Breakfast Order Standard Breakfast Business Modelling StandardBreakfast Breakfast +st andard - name: String - number: Integer * 1 - price: Real - style: Style * * Comestible +c omestible +c omestible - name: String * - minimalquant ity: Int eger 1..* - price: Real Change - transportform: String Part - quantity: Integer - quantity: Integer Breakfast Service Administration System Analyst Use Case Modelling Frontier Structure Modelling Domain Structure Modelling «UI» Create Order «UI» Modify Breakfast «extend» Initial User Interface Designer Customer «UI» Confirm Order «UI» Add Breakfast to Order «include» «SI» Execute Transaction Credit Card Company System Dynamics Modelling CREDIT CARD INPUT CREDIT CARD verify(creditcard Nr) VERIFICATION rejected aprobed CREDIT CARD REJECTED CREDIT CARD APROVED Final «UI» :BreakfastOrder «SI» Credit Card Aproved Confirm Order Execute Transaction R2 verify(credit Card Nr) Customer Architect aproved (o rejected) verify(credit Card Nr) aproved (o rejected) Architecture Generation (from Use Case Model) R3 Credit Card Verification +order R1 Credit Card (from Company Use Case Model) Orders Process +order Credit Card Input R4 +breakfast Order R5 BreakfastOrder Transactor

15 Architecture Tuning Phase self.name = rcvd_evt.name select many parameter from instances of rcvd_evt.parameters create object instance newparameter of Parameter newparameter.name = parameter.name newparameter.value = parameter.value relate self to newparameter across R10; Action Implementer self.time = Now self.status = rcvd_evt.status self.status = rcvd_evt.result «UI» Confirm Order Action Coding Pervasive Services Identification Architecture Refactoring Pervasive Services Specialist «trac e» «testcase» Confirm Order Scenario Testing Pervasive Services Configuration Operation - name: String - time: Date - result: String «Enum» +status Status 0..* 1 - ok: - error: User Interface 0..* +paramet ers 0..* Business Services Parameter Tester - name: String - Value: Architecture Integration Domain Logging Service Logging Service Credit Card Aproved R2 Operation +operat (from Pervasive ion Services) r10 +parameter 0..* Parameter (from Pervasive Services) Architect Customer (from Use Case Model) Credit Card Input R3 Credit Card Verification +order R1 +breakfast Order R6 Orders Process +order R4 Solution Generation R5 BreakfastOrder Transactor Credit Card (from Company Use Case Model)

16 Solution Tuning Phase Architect «testcase» Order Process «trace» Order Process Breakfast Order Logger Unit Testing Integration Testing Solution Refactoring User Interface Business Services Tester «UI» Confirm Order «trac e» «testcase» Confirm Order System Testing Installation Package Configuration Domain Logging Service Platform Specialist Installation Pachage Generation Order Process Breakfast Order Logger System

17 Process Roles Architect Business Analyst System Analyst User Interface Designer! Transformations! Overall Model Structure! Business Process Model! Business Rules! Domain Model! Scenarios! User Interface Design! User Interactions Action Implementer Pervasive Services Specialist Tester Platform Specialist! Action Programming! Architecture Model! Pervasive Services Integration! Scenario Testing! System Testing! Target Platform Integration and Installation

18 Example Rosa s Breakfast Service * Rosa has founded a company that supplies a complete breakfast delivered to the homes of its customers. Customers can order from one of the breakfast menus on Rosa s Web site, indicate the hour and the place of delivery, give their credit card number, and the ordered breakfast will be delivered.... Rosa wants to give to her customers a bit of flexibility. Customers may, after choosing a standard breakfast as basis, decide to put in extra comestibles, alter the amount of certain parts, and even remove parts from the breakfast. * Example problem statement taken, with permission, from MDA Explained, by Anneke Klepe, Jos Warmer and Wim Bast

19 The First Phase: : Problem Modelling ling Problem Modeling Architecture Tuning Solution Tuning Solution Implantation

20 Business Modelling Customer Customer Log- in Breakfast Order Process «goal» Register Customers' Orders! Artifact: Business Process Model! Semantics: Low to High Standard Breakfast Breakfast Order Breakfast Service Administration! Purpose: Understand Business Processes

21 Business Modelling (cont.) New Breakfast Order Creation! Variable Detail Level! Integration with Workflow Engine?! Early Class/State Identification Customer Builds Breakfast Customer Provides Credit Card Number Credit Card Number Verification [EMPTY]: BreakfastOrder :Breakfast! Use Case Secuencing Amount Ok? [no] Cancel Order [yes] Breakfast Order Registration [CANCELED]: BreakfastOrder [CONFIRMED]: BreakfastOrder

22 Domain Modelling BreakfastOrder - deliveryaddress: Address - deliverydate: Date +orders - deliverytime: Date - discount: Real 1..* - orderdate: Date + calculateprice() +order 1 Customer +customer - accountnumber: Integer 1 - address: Address + createorder() +breakfasts1..* StandardBreakfast Breakfast +standard - name: String - number: Integer* 1 - price: Real - style: Style * * Comestible +comestible +comestible - name: String * - minimalquantity: Integer1..* - price: Real Change - transportform: String Part - quantity: Integer - quantity: Integer! Artifact: Conceptual Model! Semantics: High! Goal: Understand Problem Structure

23 Domain Modelling Object States EMPTY Initial add(breakfast)! Concepts Lifecycles remove(breakfast) [breakfasts = 1] cancel remove(breakfast) [breakfasts > 1] READY! Rosa Example: -BreakfastOrder cancel add(breakfast) verify(credit Card Nr) CANCELED rejected CHECKING CREDIT CARD aproved Final CONFIRMED dispach CLOSED close DISPACHED

24 Use Case Modelling «UI» Create Order «UI» Modify Breakfast «extend» Customer «UI» Add Breakfast to Order Credit Card Company «UI» Confirm Order «include» «SI» Execute Transaction! Artifact: Use Case Model! Semantics: Medium! Purpose: Understand System Requirements

25 Frontier Modelling CREDIT CARD INPUT verify(creditcard Nr) CREDIT CARD VERIFICATION aproved rejected CREDIT CARD REJECTED CREDIT CARD APROVED! State Machine per Use Case! State per User Interface Presentation Unit (Page, Form, Electronic Device Screen, etc.)

26 System Dynamics Modelling «Human» :Customer «UI» Confirm Order DOMAIN Input (Credit Card Nr) verify(credit Card Nr) verify(credit Card Nr, BreakfastOrder) aprobed (or rejected) Requirements! Problem Level Interaction Diagram per Use Case! All Paths Covered! Domain Details Ignored! Role: UI Designer «UI» Confirm Order :BreakfastOrder «SI» Execute Transaction verify(credit Card Nr) aproved (o rejected) verify(credit Card Nr, Amount) aproved (o rejected)! Domain Level Interaction Diagram per Use Case! Domain Internal Details! Role: System Analyst

27 Architecture Generation! Unified Architecture Metamodel Unified Architecture Metamodel (UML Analysis Model with States and Actions)! Tasks - Select Architecture - Client/Server, Enterprise, Embedded, etc. - Mark Problem Model (Manual) - Generate Architecture Model (Automatic)! Model Transformations - UML Metamodel(Problem) " UML Metamodel (Architecture) - Problem Structure " Architecture Structure - Problem Dynamics " Architecture Dynamics -OCL " Action Language

28 Architecture Generation (cont.) Source Metamodel Destination Metamodel Element Element Stereotype Stereotype Tags (Marks) Tags (Marks) Additional Conditions (OCL?) Additional Instructions! Rosa Example - Architecture: Enterprise! Transformations: - Business Model " Architecture Model (Enterprise Business Services Layer) - Use Case Model " Architecture Model (Enterprise Presentation Layer) -Domain Model " Architecture Model (Enterprise Business Components Layer) - Problem Interaction Models " Architecture Interaction Models -OCL " Action Language Instructions

29 Architecture Generation Rosa s Breakfast Service Business Model " Analysis Model Source Destination Element Stereotype Tags Add. Cond. Element Stereotype Tags Add. Instr. Activity Process Class Control Activity Process Is Aggregated Class Control Association Aggregate - Agregated Use Case Model " Analysis Model Source Destination Element Stereotype Tags Add. Cond. Element Stereotype Tags Add. Instr. State Context UC is UI Class Boundary isui = true State Class Boundary isui = false State Transition Message is Self (interaction) Association Navigate Start State Class End State Class State Transition Message is not Self State Class Process Control Class

30 Architecture Generation Rosa s Breakfast Service! OCL " Action Language Compiler! Rosa Example: CalculatePrice() Operation BreakfastOrder - deliveryaddress: Address - deliverydate: Date - deliverytime: Date - discount: Real - orderdate: Date + calculateprice() : Real +order 1 +breakfasts 1..* Breakfast - number: Integer {context BreakfastOrder::calculatePrice() body: sum( self.breakfasts->collect( comestible.price * Change.quantity ) )} +breakfasts 1..* BreakfastOrder 1 R7 Change * - quantity: Integer +comestible * Comestible - name: String - minimalquantity: Integer - price: Real - transportform: String Breakfast select many breakfasts related by self->breakfast[r7] result = 0 for each breakfast in breakfasts select many comestibles related by breakfast->comestible[r8] for each comestible in comestibles select one charge related by comestible->charge[r8] result = result + comestible.price * charge.quantity next next

31 The Second Phase: Architecture Tuning Problem Modeling Architecture Tuning Solution Tuning Solution Implantation

32 Action Coding Credit Card Aproved R2! Complete State Procedures and Operations Code Customer (from Use Case Model) Credit Card Verification R3 +order R1 Credit Card Input Orders Process +order R4 +breakfastorder R5 BreakfastOrder Transactor Credit Card Company (from Use Case Model)

33 Scenario Testing «Human» :Customer Input (Credit Card Nr) Credit Card Input navigate(credit Card Nr) Credit Card Verification Credit Card Aproved verify(breakfastorderid, Credit Card Nr) aproved (o rejected) Orders Process verify(credit Card Nr) aprobed (o rejected) BreakfastOrder verify(credit Card Nr, Amount) aprobed (o rejected) Transactor navigate! Architecture Interaction Diagrams Generated from Problem Interaction Diagrams! Architecture Model Virtual Machine! Simulations Execution Traces

34 Pervasive Services Identification and Configuration! Identify Needed Pervasive Services (PS) - Select From Available PS Modules, or - Develop New PS Modules! Rosa Example: Logging Service Operation - name: String - time: Date - result: String 0..* +status 1 «enumeration» Status - ok: - error: 0..* +parameters 0..* Parameter - name: String - Value: Operation init(name, parameters) CREATED r10 +parameters 0..* Parameter log(status, result) LOGGED self.time = Now self.status = rcvd_evt.status self.status = rcvd_evt.result

35 Architecture Integration! Integrate System with Pervasive Services! Tasks: - Mark the Join Points in the Architecture Model - Weave the PS Modules with Architecture Model! Rosa Example: - Requirement: All the Executions of theorderprocess::verify() should be registered -Solution: Tag the OrderProcess::Verify() with islogged = true! Mapping Rules are Part of Every Individual PS Module

36 Architecture Integration (cont.) Logging Service Credit Card Aproved R2 Operation (from Pervasive Services) +operation +parameters r10 0..* Parameter (from Pervasive Services) Customer (from Use Case Model) Credit Card Input Credit Card Verification R3 +order R1 Orders Process +order R4 +breakfastorder R6 OrderProcess::Verify( CreditCardNr: Integer, BreakfastOrderID: Integer): Boolean //----- inserted by the Logger PS Weaver create object instance operation of Operation relate relate operation to self across R6 generate init("orderprocess::verify", {"CCNr", CreditCardNr, "OrderID", BreakfastOrderID}) to operation //----- finished // here goes the Verify() domain code //----- inserted by the Logger PS Weaver generate log(status, result) to operation unrelate operation from self across R6 //----- finished R5 BreakfastOrder +breakfasts R * Breakfast Transactor Credit Card Company (from Use Case Model)

37 Solution Generation! Unified Architecture Metamodel " Target Platform! Tasks: - Select the Platform (J2EE,.NET, etc) - Mark the Architecture Model (Manual) - Generate the Solution Model (Automatic)! Model Transformations: - UML Metamodel (Architecture) " UML Metamodel (Platform) - Action Language " Target Platform Language

38 Solution Generation Rosa s Breakfast Service Analysis Model " Solution Model Source Destination Element Stereotype Tags Add. Cond. Element Stereotype Tags Add. Instr. Class Boundary isui = true Has input Class JSP Class Boundary isui = true Has Control Class Servlet Class Boundary isui = false Class Stateless SessionBean Interface Home Interface Remote Class Control Class Stateless SessionBean Interface Home Interface Remote Class Entity Class EntityBean Interface Home Interface Remote

39 The Third Phase: Solution Tuning Problem Modeling Architecture Tuning Solution Tuning Solution Implantation

40 Solution Generation «JSP» CreditCardAproved «Servlet» CreditCardVerification «realize» OperationLocal +logger «EntityBean» Operation «JSP» CreditCardInput OrderProcess «realize»! Target Platform Testing - Functional and no Functional - Unit and Integration! Refactoring «StatelessSessionBean» OrderProcessBean + verify() : Boolean BreakfastOrderLocal «realize» «EntityBean» BreakfastOrder «StatelessSessionBean» TransactorBean +transactor «realize» Transactor! Platform Language Coding (if needed)! Installation Package Generation + CalculatePrice() : Real +breakfasts BreakfastLocal «realize» «EntityBean» Breakfast

41 The Last Phase: Solution Implantation Problem Modeling Architecture Tuning Solution Tuning Solution Implantation

42 Future Work! User Interface Interaction Modelling Metamodel - UML Profile v.s. Alternative Metamodel! Transformations - Transformation Definition Metamodel - Model Compiler v.s. Archetypes! Architecture Model Infrastructure -Virtual Machine -Simulator! Pervasive Services Integration - Aspect Oriented Technics Formalization

43 Bibliography! Executable UML, A Foundation for Model-Driven Architecture, S. J. Mellor, M. J. Balcer! MDA Explained, The Model Driven Architecture: Practice and Promise, A. Kleppe, J. Warmer, W. Blast! MDA Distilled, Principles of Model-Driven Architecture, S. J. Mellor, K. Scott, A. Uhl, D. Weise! Model Driven Architecture, Applying MDA to Enterprise Computing, D. S. Frankel! The Object Constraint Language Second Edition, Getting Your Models Ready for MDA, J. Warmer, A. Kleppe! Mastering AspectJ, J. D. Gradecki, N. Lesiecki!

44 Thank You! Aleksandar Orlic