Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Supporting model evolution in model-driven development of automotive embedded system
KTH, School of Industrial Engineering and Management (ITM), Machine Design (Dept.), Mechatronics.
2010 (English)Licentiate thesis, comprehensive summary (Other academic)
Abstract [en]

Innovative functions in cars, such as active safety systems and advanced driver assistance systems, are realized as embedded systems. The development of such automotive embedded systems is challenging in several respects: the product typically has several crosscutting system properties, experts of diverse disciplines need to cooperate and appropriate processes and tools are required to improve the effciency and the complexity management of development. Model-driven development captures the architecture of the embedded system in the form of models with well-defined metamodels. Model-driven development provides a partial solution to some of the challenges of embedded systems development, but it also introduces new challenges. Models do not remain static, but they change over time and evolve. Evolution can change models in two ways: (1) by making design decisions and adding, deleting or changing model elements, or (2) by reusing models in different tools. We propose support for both aspects of model evolution. (1) When models are changed, the design decisions and the justification for the change are usually neither captured nor documented in a systematic way. As a result, important information about the model is lost, making the model more difficult to understand, which hampers model evolution and maintenance. To support model evolution, design decisions need to be captured explicitly using an appropriate representation. This representation reduces the overhead of capturing design decisions, keeps the model and the design decision documentation consistent and links the design decision documentation to the model. As a result, the captured design decisions provide a record of the model evolution and the rationale of the evolution. (2) Several models and views are used to describe an embedded system in different life cycle stages and from the viewpoints of the involved disciplines. To create the various models, a number of specialized development tools are used. These tools are usually disconnected, so the models cannot be transferred between different tools. Thus, models may become inconsistent, which hampers understandability of the models and increases the cost of development. We present a model-based tool integration approach that uses a common metamodel in combination with model transformation technology to build bridges between different development tools. We apply this approach in a case study and integrate several tools for automotive embedded systems development: A systems engineering tool, a safety engineering tool and a simulation tool. As a part of future work, we plan to extend the tool integration approach to exchange not only models but also the attached documentation of design decisions. As a result, the design decision documentation is linked consistently to corresponding model elements of the various tool-specific models, supporting model evolution across several development tools

 

Place, publisher, year, edition, pages
Stockholm: US-AB , 2010.
Series
Trita-MMK, ISSN 1400-1179 ; 2010.18
Identifiers
URN: urn:nbn:se:kth:diva-27323ISBN: 978-91-7415-723-9 (print)OAI: oai:DiVA.org:kth-27323DiVA: diva2:376022
Presentation
2010-11-26, A325, KTH, Brinellvägen 83, Stockholm, 16:08 (English)
Opponent
Supervisors
Note
QC 20101209Available from: 2010-12-09 Created: 2010-12-09 Last updated: 2010-12-09Bibliographically approved
List of papers
1. Literature study on the state of the art in model transformation technology
Open this publication in new window or tab >>Literature study on the state of the art in model transformation technology
2010 (English)Report (Other academic)
Abstract [en]

Model transformation is a central concept in model-driven development approaches,  as it provides a mechanism for automating the manipulation of models. In this document we survey and classify existing model transformation technology. The classification differentiates between the problem space, i.e. characteristics of the problem to be solved by model transformation technology, and the mechanism, i.e. characteristics of the model transformation language. We show typical usage scenarios for model transformations and identify characteristics of the problems that can be solved with the help of model transformations. We synthesize a unifying classification scheme for model transformation languages based on several existing classification schemes. We introduce a selection of model transformation tools available today and compare them using our classification scheme.

Place, publisher, year, edition, pages
Stockholm: KTH, 2010
Series
Technical Report, Royal Institute of Technology, ISSN 1400-1179 ; 2010:07
Identifiers
urn:nbn:se:kth:diva-27208 (URN)
Note
QC 20101209Available from: 2010-12-09 Created: 2010-12-09 Last updated: 2010-12-09Bibliographically approved
2. Integrating safety analysis into the model-based development tool chain of automotive embedded systems
Open this publication in new window or tab >>Integrating safety analysis into the model-based development tool chain of automotive embedded systems
2010 (English)In: ACM SIGPLAN Notices, ISSN 0362-1340, Vol. 45, no 4, 125-132 p.Article in journal (Refereed) Published
Abstract [en]

The automotive industry has a growing demand for the seamless integration of safety analysis tools into the model-based development tool chain for embedded systems. This requires translating concepts of the automotive domain to the safety domain. We automate such a translation between the automotive architecture description language EAST-ADL2 and the safety analysis tool HiPHOPS by using model transformations and by leveraging the advantages of different model transformation techniques. By means of this integration, the safety analysis can be conducted early in the development process, when the system can be redesigned to fulfill safety goals with relatively low effort and cost.

Place, publisher, year, edition, pages
ACM, 2010
Keyword
safety analysis, model-based development, architecture description language, tool intergration
National Category
Mechanical Engineering
Research subject
SRA - ICT
Identifiers
urn:nbn:se:kth:diva-27210 (URN)10.1145/1755888.1755907 (DOI)000277056500014 ()2-s2.0-77954461067 (Scopus ID)
Conference
the ACM SIGPLAN/SIGBED 2010 conference on Languages, compilers, and tools for embedded systems
Note

QC 20101209

Available from: 2010-12-09 Created: 2010-12-09 Last updated: 2016-03-10Bibliographically approved
3. A modular tool integration approach: experiences from two case studies
Open this publication in new window or tab >>A modular tool integration approach: experiences from two case studies
2010 (English)In: 3rd Workshop on Model-driven tool and Process Integration (MDTPI2010), 2010Conference paper, Published paper (Refereed)
Abstract [en]

 

In the model-driven development process of automotive embedded systems a number of specialized tools are used to support various development tasks. Each tool needs to work seamlessly with artifacts created by other tools to increase the efficiency of development. We identify desirable properties for integrating the data of different tools. We then propose an approach for decomposing the data integration into modular steps that fulfill these properties. We report our experiences from applying this approach to integrate simulation capabilities and functionality for safety analysis into a model-based development environment.

Keyword
tool integration, model transformation
Identifiers
urn:nbn:se:kth:diva-27216 (URN)
Note
QC 20101209Available from: 2010-12-09 Created: 2010-12-09 Last updated: 2013-01-07Bibliographically approved
4. Literature study on design rationale and design decision documentation for architecture descriptions
Open this publication in new window or tab >>Literature study on design rationale and design decision documentation for architecture descriptions
2010 (English)Report (Other academic)
Abstract [en]

 

In this document we provide an overview of the state of the art in documentation of design rationale and design decisions for architecture descriptions. We define the terminology of the area and compare the concept of rationale to similar concepts. We provide an overview of areas of contemporary research in design rationale. For each of the identified areas, we describe both the challenge and proposed solutions. Based on the findings from the literature we present evaluations of rationale and design decision documentation. The findings from this survey are promising and many open research questions with respect to rationale and design decision documentation need to be addressed. In the literature reviewed in this document it is for example not addressed how design decisions and design rationale should be represented, captured and used in model-based and model-driven development approaches. A need for further research in this area exists.

Place, publisher, year, edition, pages
Stockholm: KTH, 2010
Series
Technical Report, Royal Institute of Technology, 2010:06
Identifiers
urn:nbn:se:kth:diva-27218 (URN)
Note
QC 20101209Available from: 2010-12-09 Created: 2010-12-09 Last updated: 2010-12-09Bibliographically approved
5. An executable design decision representation using model transformations
Open this publication in new window or tab >>An executable design decision representation using model transformations
2010 (English)In: Proceedings - 36th EUROMICRO Conference on Software Engineering and Advanced Applications, SEAA 2010, Lille, 2010, 131-134 p.Conference paper, Published paper (Other academic)
Abstract [en]

Design decisions are often tacit knowledge of an architecture and consequently they are easily lost during software evolution, a phenomenon known as knowledge vaporization. As a countermeasure design decisions can be documented explicitly. However, documenting design decision is expensive because they need to be captured in addition to the changes in the architecture. We propose an executable representation for design decisions using model transformations which is independent of a particular component model or architectural description language. As a result we get all the advantages of explicitly captured design decisions such as the potential to reduce knowledge vaporization while preventing the high capturing cost since the corresponding architectural change can be computed automatically. The approach is illustrated by a case study in the context of embedded software architectures.

Place, publisher, year, edition, pages
Lille: , 2010
Identifiers
urn:nbn:se:kth:diva-27221 (URN)10.1109/SEAA.2010.11 (DOI)2-s2.0-78449286956 (Scopus ID)9780769541709 (ISBN)
Note
QC 20101209Available from: 2010-12-09 Created: 2010-12-09 Last updated: 2010-12-09Bibliographically approved
6. Documenting stepwise model refinement using executable design decisions
Open this publication in new window or tab >>Documenting stepwise model refinement using executable design decisions
2010 (English)In: International Workshop on Models and Evolution (ME2010), 2010Conference paper, Published paper (Refereed)
Abstract [en]

During model refinement a wealth of knowledge about the model under development is accumulated that is only partly represented by the model itself. Design decisions and the considered modeling alternatives are neither represented by the model nor are they documented. During later lifecycle stages this information is often not available any more, which reduces the understandability of the model and potentially leads to inconsistencies and erosion of the model. We propose an approach to capture and store the design decisions in model-driven development. We represent design decisions as model transformations and propose tool support that applies this representation to capture design decision with low effort. The captured design decisions provide a record of the model evolution and the rationale of the evolution.

 

Keyword
Design Decision, Evolution, Model Transformation, Refinement
Identifiers
urn:nbn:se:kth:diva-27322 (URN)
Note
QC 20101209Available from: 2010-12-09 Created: 2010-12-09 Last updated: 2010-12-09Bibliographically approved

Open Access in DiVA

fulltext(865 kB)805 downloads
File information
File name FULLTEXT01.pdfFile size 865 kBChecksum SHA-512
aa9a9d17a27a4389c618a7b6b754fac4b1a5a87a1c7a9a9429fa0fa20ef608f109b9b3ad6d8e3fb4dcfb2605339d104dc3b9a5a34722750eb3a2eb9248f751d0
Type fulltextMimetype application/pdf

Search in DiVA

By author/editor
Biehl, Matthias
By organisation
Mechatronics

Search outside of DiVA

GoogleGoogle Scholar
Total: 805 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

isbn
urn-nbn

Altmetric score

isbn
urn-nbn
Total: 561 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf