Methods for the Development

Transcription

1 Methods for the Development Of Dependable and Adaptive Information Systems Carolina Gomez Hernandez

2 Index of Contents History of Modeling Methods for the Development of DAIS: Model Driven Architecture (MDA) An MDA specific Application Enterprise Knowledge Development Change Management Method (EKD- CMM) MDA vs. EKD-CMM Conclusions

3 History of Modeling Modeling Evolution Time Line Machine Code High Level Coding O-O Coding Model Code High Level Programming (FORTRAN) O-O Programming (JAVA) Compiler Compiler Assembler Assembler Program Generated Assembler Code Generated Assembler Code

4 History of Modeling Modeling Evolution Time Line 1995 Early Modeling 200x MDA Model UML Model UML Model Code Assembler Updated Manually OO - Code Partially Generated Generated Assembler Code Generate Compiler Generate OO Code Completely Generated Compiler Generated Assembler Code

5 History of Modeling Modeling has evolved in order to: Handle the complexity of today s software systems Achieve a higher level of abstraction that allows a human to better understand a problem.

6 History of Modeling Complexity of today s software system: FORMERLY Applications were developed by thinking of technical specifications of a specific technology. TODAY The development of Information Systems involves a wide range of concepts including the implementation technology. This rising complexity requires a higher level of abstraction = 5 User Requirements Business Processes Domains

7 History of Modeling A higher level of abstraction allows a human to better understand a problem. Growing Levels of abstraction MDA UML Java, C# Book x = new Book() ASSEMBLER LTR L1,L2 FORTRAN,C int x = 0; x Time

8 Methods for the Development of DAIS Model Driven Architecture (MDA): For the development of an information system Enterprise Knowledge Development Change Management Method (EDK-CMM): Allow to choose an information system suitable for an enterprise

9 Model Driven Architecture (MDA) DEFINITION Method used for developing software that uses models to specify the behavior and requirements of a system, independently from the platform in which the system is finally implemented.

10 Model Driven Architecture (MDA) GOALS 1. To make a distinction between the logic of business and the platform implementation. 2. To offer a standard to develop and create models. 3. To create code implementation directly from models.

11 Model Driven Architecture-MDA 1. Logic of Business vs. Platform UML platform independent model UML model link between model and code UML model for the System Behavior Transformation Intermediate UML model According to a specific platform Modeling Layer Generated Code from the platform specific UML model Transformation Implementation Code ready for compilation Code Layer

12 Model Driven Architecture (MDA) Models Modeling Layer Computation Independent Model Platform Independent Model CIM PIM Use Case No1 Description: Actors: Related Use Cases: Class1 Class2 Class3 Platform Model PM Platform Specific Model PSM UML Profile for.net

13 Model Driven Architecture (MDA) 2. Modeling Standards and Languages Unified Modeling Language (UML) : Used to create graphical representation of systems requirements and behavior. PIM Use Case No1 Description: Actors: Related Use Cases: Class1 Class2 Class3 PSM XML Metadata Interchange (XMI): Used to integrate XML data and model objects UML Profile for.net Class1 Class2 Class3

14 Model Driven Architecture (MDA) 2. Modeling Standards and Languages Meta Object Facility (MOF) M3 MOF Meta-Metamodel Language in which Modeling systems Are specified Class Attribute1 Attribute2 Attributen Book ISBN Name Author M2 M1 Defined by UML Metamodel Defined by UML Model UML Class Metamodel: Concepts of an UML Class UML Class Model for a particular application M0 Instance of Book Harry Potter JK Rowling Object instance of a UML Class Model.

15 Model Driven Architecture (MDA) 2. Modeling Standards and Languages Common Warehouse Metamodel (CWM): Used to integrate warehouse metadata. Warehouse Repository CWM

16 Model Driven Architecture (MDA) 3. Implementation code derived from models: MDA Transformation Transformation in MDA is the process of converting one model into another of the same system. Within a system models are classified in three different layers, called viewpoints.

17 Model Driven Architecture-MDA MDA Transformation: Viewpoints The environment and requirements of a system Focuses on Computation Independent Viewpoint Model from CIVP 1. Transformed into The operation of a system without specifying details of any platform Focuses on Platform Independent Viewpoint Model from PIVP Program Code = specification of a system +platform Focuses on Platform Specific Viewpoint 2. Transformed into Model from PSVP Models are transformed from one to another viewpoint.

18 Model Driven Architecture (MDA) MDA Transformation Guides: Mappings Mapping gives rules and specifications to transform one model into another of a specific platform. Mapping UML-XML ISBN Name Author Book XMLSchema <?xml version="1.0"?> <Schema xmlns="schemas-microsoftcom:xml-data"> <ElementType name="book"> <element type="isbn" /> <element type="author" /> <element type="name" /> </ElementType> </Schema>

19 Model Driven Architecture (MDA) MDA Transformation Guides: Mappings Model Type Mappings: Mapping Rules are defined by using a Platform Model. Model Instance Mappings: Mapping Rules are defined by using Marks. + MARKS

20 Model Driven Architecture (MDA) Case of transformation Using Model Instance Mappings UML Model PIM Are applied to Marks Marks PIM with Marks Mapping Based on Marks Mapping PSM public Class Book { protected int ISBN; private string Name; private string Author; public void ModifyName(){} public string GetAuthor(){} } C# Class

21 MDA & Avionics Industry Why MDA in the avionics? To improve their existing method of developing software: waterfall method To integrate all functionality blocks in a standardized way Sensors and Weapons Aircraft communications equipment AIRCRAFT PLATFORM INDEPENDENCE Hardware Interface Domain Communications Domain Software Architecture Domain Pilot Interface Domain EXECUTION PLATFORM INDEPENDENCE Interface for communicating with the Pilot PLATFORM INDEPENDENT LAYER Mapping Rules from PIM to PSM OS, Programming Languages and Processors TARGET EXECUTION ENVIRONMENT TARGET HARDWARE PLATFORM SPECIFIC LAYER

22 MDA & Avionics Industry MDA approach used by the Military Aircraft System Specify Domains By using System Use Cases Specify Mapping Rules from PIMs to PSMs Build Platform Independent Models Class diagram, state charts Action Models Generate System Generate code for the Target system Validate PIMs By executing and simulating System Use Cases

23 MDA & Avionics Industry Example of the MDA approach: Transform an application into a set of processing modules Independent Execution Layer Application 1 Application 2 Application n iuml tool: Model Builder Tags A PIM is built A PIM is tagged PIM (Application) PIM (Application) Specific Execution Layer Operating System Module Support Layer Processing Module 1 Processing Module n Processing Module 2 Blue Print tool: Store information of the OS Mapping Rules are Provided iccg tool: Code Generator A PIM is validated iuml tool: Model Tester PIM (Application) PSI Processing Module

24 MDA & Avionics Industry Why does MDA improve dependability? It verifies platform independent models against the system requirements before a transformation. It performs an automated transformation process.

25 EKD-CMM Enterprise Knowledge Development Change Management Method DEFINITION Choose an information system suitable for an enterprise: First define the objectives and processes of an enterprise. Second, define the requirements of the information system suitable for the enterprise.

26 Enterprise Knowledge Development EKD-CMM Change Management Method Layers of Modeling BUSINESS OBJECTIVES Goals Enterprise Goal Models BUSINESS PROCESSES Actors Roles Processes Enterprise Processes Models INFORMATION SYSTEMS Systems Enterprise System Model

27 Enterprise Knowledge Development EKD-CMM Change Management Method Road Map: Approaches to follow this method Start b a c Elicit Enterprise Business Model a a Conceptualise Information System model c Conceptualise Business Processes Model b b c End a a. Forward Engineering b. Reverse Engineering c. Business Process Reengineering or Improvement

28 Enterprise Knowledge Development EKD-CMM Change Management Method EDK-CMM approach example : Forward Engineering Business Objectives Business Objectives Model Requirements only Business Processes Business Processes Model Business Object Model (BOM) Technical Concepts Information Systems Enterprise System Model Technical Business Object Model (TBOM) Business Process Rules (BPR)

29 MDA & EKD-CMM Similarities Use of Model Driven Development (MDD) Use of Transformations Use of the concept of layers Refinement of models to keep integrity

30 MDA & EKD-CMM Differences The final product of MDA is a platform specific model (PSM) : Implementation Code The final product of EDK-CMM is an Enterprise System Model: List of requirements of an Information System suitable for an Enterprise.

31 Conclusions Dependability MDA Reliability: MDA performs an automated transformation from models to code. Validation: The PIMs are validated against the requirements of a system before being transformed. Integrity: MDA provides an alternative to coding. EKD-CMM EKD-CMM defines an enterprise system model, that describes how to support business processes at operational levels.

32 Conclusions Adaptability MDA In MDA, changes in the system are updated dynamically: MDA allow to make an update of the system directly in the models. MODEL REPOSITORY MODEL REPOSITORY + Class1 Class2 Class3 = Use Case No1 Description: Actors: Related Use Cases: Use Case No1 Description: Actors: Related Use Cases: Class1 Class2 Class3

33 THE END