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

More documents

Recommendations

Info

3. Automotive Open System Architecture The AUTOSAR standard is subject to constant improvement. This causes the corresponding metamodel to evolve as well. Each new release of the AUTOSAR standard brings with it evolutionary modifications of the metamodel. If one compares the respective metamodels of AUTOSAR versions 3.1 ([auta]) and 4.0 ([autb]), one will notice structural changes in both parts describing the overall structure and very detailed parts of the metamodel. One metamodel always belongs to only one version of the AUTOSAR standard. 3.2. Artop Developing AUTOSAR systems (see section 3.1.2) is supported through the use of appropriate tools. All these tools must cover basic functionality related to handling AUTOSAR models. A simple example is the ability to load an AUTOSAR model into the memory so it can be manipulated through tool functions. The specific functionality of the tool vendor’s area of expertise can be built on top of the common functions. However, with every tool vendor implementing the common AUTOSAR functionality on their own, a great deal of redundant development occurs among the vendors [KRV + 10b]. This approach is illustrated on the left hand side in figure 3.5. Artop (AUTOSAR Tool Platform) addresses this by applying the ecosystem approach to the field of AUTOSAR tools in a way that resembles ecosystems found in open-source projects [KRV + 10a]. An ecosystem in this sense refers to a concept where the value of products and services of the ecosystem participants complement each other. Such an organization implies the requirement for using common technologies and standards. This approach is illustrated on the right hand side in figure 3.5. Figure 3.5.: Non-collaborative and collaborative AUTOSAR tool development approach in comparison (image adopted from [KRV + 10b]). Artop is an infrastructure platform for tools used to design, develop and configure AUTOSAR systems which provides an implementation of common tool functionality. The community developing Artop - the Artop User Group - consists of AUTOSAR members and partners. This way Artop offers both an organizational and a technical advantage: an improved cooperation with AUTOSAR partners as well as a high interoperability and integration of AUTOSAR tools [Rud10]. For a better understanding of how Artop works and its role in the AUTOSAR world, the Artop stakeholders are presented: 30 • Artop developers are the immediate creators of the infrastructure platform that constitutes Artop and that is defined in this section. Artop developers comprise the Artop User Group layer of the Artop architecture in figure 3.6.
3.2. Artop • Artop users or AUTOSAR tool developers utilize the infrastructure provided by Artop developers to create vendor-specific tools. AUTOSAR tool developers comprise the Tool Vendor layer of the Artop architecture in figure 3.6. • AUTOSAR tool users work with tools provided by AUTOSAR tool developers to create AUTOSAR models. Such tools are comprised of all the layers of the Artop architecture in figure 3.6. 3.2.1. Artop architecture Artop builds upon the Eclipse Platform and makes heavy use of the Eclipse Modeling Framework (see section 2.2) to create an infrastructure for realizing AUTOSAR tools. Where an adaption of existing Eclipse technologies is necessary, Artop provides a set of extensions to the respective Eclipse projects. Figure 3.6 shows the different layers of the Artop architecture: [Rud10] • Competitive Layer. Tool vendors commercially develop plugins at this level and realize their tool functionality by using the infrastructure provided by Artop. • Artop AUTOSAR Layer. This layer provides software components and plugins that implement AUTOSAR-specific functionality. • Artop Eclipse Complementary Layer. This layer implements Artop’s extensions to the Eclipse platform, but does not contain any AUTOSAR specific functions. Since Artop release 3.0 this layer has become a part of the Eclipse Sphinx project [sph] and is located in the Eclipse Platform layer. • Eclipse Platform. Eclipse is well-suited for developing domain-specific IDEs, hence it is used as Artop’s foundation. Figure 3.6.: Layers composing the Artop architecture (image adopted from [Rud10]). 31
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 36 and 37: 2. State of the Art The COPE (COuPl
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?