institut f¨ur informatik - PST Thesis Management Interface - LMU

More documents

Recommendations

Info

2. State of the Art The COPE (COuPled Evolution of metamodels and models) project developed from a thesis done at BMW Car IT [Her07]. The term coupled evolution is used to describe the process of breaking down metamodel history into small steps of metamodel evolution and the associated model adaptation. In more detail, it is denoted that some primitive changes only make sense when regarded in combination with others, such as the migration of a class attribute to the superclass. In this case, primitive changes need to be combined and interpreted as a compound change. Coupled evolution steps can be divided in the same way as the types of changes referenced at the beginning of this section. The evolution steps can be complete if no manual interaction is necessary to correctly adapt a model or incomplete otherwise. Furthermore, the evolution steps are open if domain-specific knowledge is necessary to fully adapt the model and closed otherwise. This distinction is equivalent to the distinction between automatic and semi-automatic adaptation. For open coupled evolution, the approach consists of maintaining metamodel history as a sequence of changes that lead from an empty metamodel to the current version. In the course of evolution history, previous versions of the metamodel are constructed at some point in time. Then model transformation rules in a sufficiently expressive language can be attached to any number of primitive metamodel changes. Closed coupled evolution provides a mechanism to specify transformation rules in form of coupled evolution operations independently of the metamodel, which can then be instantiated and applied in a model adaptation template. 2.4. Summary This chapter explained the events that led to the increased complexity of modern software systems and how models can be used to tackle this issue. Examples from the automotive industry were used to illustrate applications of the model-driven approach. Capabilities of the Eclipse Modeling Framework were explored in the context of creating a modeling tool for basic AUTOSAR software components. The chapter was concluded with an overview of model evolution, its common problems and research directions aiming at solving these problems. 24
3. Automotive Open System Architecture This chapter introduces specialized technologies that rely on model-driven software development to solve the complexity issue in developing automotive software. These technologies represent the scope of work concerned in this thesis. 3.1. The AUTOSAR standard AUTOSAR (AUTomotive Open System ARchitecture) is an open standard that applies the model-driven approach (see section 2.1) to software development for Electronic Control Units (ECUs) in automobiles. AUTOSAR is motivated by the increasing complexity of modern automotive electric and electronic (E/E) architecture (see section 2.1.5). In order to manage this complexity, automobile manufacturers, suppliers and tool developers have formed a development partnership that cooperates on developing common, basic functions and supports competition on innovative functions [Hei04]. The ability to manage this complexity results in improved quality and reliability of automotive E/E systems. Furthermore, the AUTOSAR development partnership aims at creating scalable solutions that can be reused within and across vehicle and component product lines and at an improved development process. 3.1.1. AUTOSAR architecture The AUTOSAR architecture (see figure 3.1) provides a common software infrastructure for automotive systems of all vehicle domains. It consists of multiple software layers that build up on each other and are interconnected through standardized interfaces. This approach is considered fundamental to achieving the following technical goals: [Hei04, AUT11c] • Modularity: enables combining functional modules from different suppliers. • Scalability: ensures compatibility of common software modules to different vehicle platforms. • Transferability: optimizes the use of resources throughout the electronic architecture of a vehicle. • Reusability: enables integration of software modules into new environments. The remaining part of this section describes the essential concepts of the AUTOSAR architecture in more detail. 25
Page 1: INSTITUT FÜR INFORMATIK DER LUDWIG
Page 5: Hiermit versichere ich, dass ich di
Page 9: Acknowledgments I would like to tha
Page 12 and 13: Contents 4.2.2. Model comparison in
Page 14 and 15: 1. Introduction The automation conc
Page 16 and 17: 2. State of the Art like abstract d
Page 18 and 19: 2. State of the Art Metamodels and
Page 20 and 21: 2. State of the Art Figure 2.3.: Th
Page 22 and 23: 2. State of the Art In a roundtrip
Page 24 and 25: 2. State of the Art 2.2. Eclipse Mo
Page 26 and 27: 2. State of the Art Finally, an Eco
Page 30 and 31: 2. State of the Art } SoftwareComp
Page 34 and 35: 2. State of the Art A model-centric
Page 38 and 39: 3. Automotive Open System Architect
Page 50 and 51: 4. Automation of Generic AUTOSAR 1.
Page 52 and 53: 4. Automation of Generic AUTOSAR an
Page 54 and 55: 4. Automation of Generic AUTOSAR fr
Page 56 and 57: 4. Automation of Generic AUTOSAR an
Page 58 and 59: 4. Automation of Generic AUTOSAR Fi
Page 60 and 61: 4. Automation of Generic AUTOSAR of
Page 62 and 63: 4. Automation of Generic AUTOSAR 4.
Page 64 and 65: 4. Automation of Generic AUTOSAR Pa
Page 66 and 67: 4. Automation of Generic AUTOSAR Ty
Page 68 and 69: 4. Automation of Generic AUTOSAR Fi
Page 70 and 71: 4. Automation of Generic AUTOSAR se
Page 72 and 73: 4. Automation of Generic AUTOSAR 60
Page 74 and 75: 5. Results Figure 5.1.: Two excerpt
Page 76 and 77: 5. Results Figure 5.2.: PhysicalDim
Page 78 and 79: 5. Results Figure 5.3.: Aggregated
Page 80 and 81: 5. Results 68
Page 82 and 83: 6. Conclusion The prototype impleme
Page 84 and 85: 6. Conclusion 72
Page 86 and 87:
A. Appendix 74 Figure A.1.: Two tes
Page 88 and 89:
A. Appendix Figure A.3.: Two-way, n
Page 90 and 91:
A. Appendix Figure A.5.: Modified c
Page 92 and 93:
List of Figures 80 4.3. The resulti
Page 94 and 95:
List of Listings 82
Page 96 and 97:
CD Contents 84
Page 98 and 99:
Bibliography [emfa] EMF Compare - E
Page 100:
Bibliography [relc] subversion.tigr
show all

institut f¨ur informatik - PST Thesis Management Interface - LMU

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?