Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • 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
Towards a guideline for refactoring of embedded systems
Mälardalen University, School of Innovation, Design and Engineering.ORCID iD: 0000-0002-0527-169X​
2012 (English)Licentiate thesis, comprehensive summary (Other academic)
Abstract [en]

The electronics in automotive systems give great possibilities. It has contributed to environmental improvements through reduced emissions and reduced fuel consumption, safety, driver assistance, and quality through better diagnostic capabilities.

Automotive systems are today distributed embedded systems that consist of several nodes that communicate with each other. The increasing possibilities have led to a situation where functions that used to be stand-alone, are today dependent on several inter-connected systems which all contribute to the desired functionality. This has increased the costs and the complexity to deal with the systems.

The automotive industry is adopting a new open software architecture, called AUTOSAR, that is intended to reduce the complexity. AUTOSAR also gives possibilities for coping with large product ranges and for component sharing. The introduction of AUTOSAR is an example of an architecture change without modifying the external functionality. We have chosen to call such changes system refactoring.

However, if the introduction of AUTOSAR is not successfully performed, there are risks for delayed development projects, which are costly for the automotive companies. Unfortunately, existing engineering standards and literature focus mostly on new product development and less on system re-factoring, and this gap needs to be filled. The goal of this research is to provide guidelines for refactoring, which provides support throughout the complete process of system architects in efforts to refactor the system.

This thesis identifies the characteristics of refactoring processes. This is done by empirical studies of the drivers behind refactoring, the effects we can expect from refactoring, and the process activities and characteristics. The result can be used to create guidelines for improving the work of refactoring.

Place, publisher, year, edition, pages
Västerås: Mälardalen University , 2012.
Series
Mälardalen University Press Licentiate Theses, ISSN 1651-9256 ; 152
National Category
Software Engineering
Research subject
Computer Science
Identifiers
URN: urn:nbn:se:mdh:diva-14592ISBN: 978-91-7485-070-3 (print)OAI: oai:DiVA.org:mdh-14592DiVA: diva2:525669
Presentation
2012-05-31, Lambda, Mälardalens högskola, Västerås, 13:15 (English)
Opponent
Supervisors
Available from: 2012-05-09 Created: 2012-05-08 Last updated: 2014-12-12Bibliographically approved
List of papers
1. Effect Analysis of the Introduction of AUTOSAR - a Systematic Literature Review
Open this publication in new window or tab >>Effect Analysis of the Introduction of AUTOSAR - a Systematic Literature Review
2011 (English)In: Proceedings - Software Engineering and Advanced Applications (SEAA), 2011 37th EUROMICRO, 2011, 239- p.Conference paper, Published paper (Refereed)
Abstract [en]

Many complex software-intensive systems have a long life time, and undergo substantial evolution. These evolutions are either additions of functionality or system refactoring, i.e., updating the architecture to improve quality attributes without changing functionality. However, the return of investment for such a system refactoring is not easily measured due to a lack of understanding of its effects. In order to improve our understanding of these effects, we have conducted a systematic literature review of the reported effects of one such refactoring: the introduction of AUTOSAR, an open automotive software architecture standard. The effects include both benefits, like lower complexity and more efficient system development, and costs, like performance risks. We have investigated how the effects depend on different elements in AUTOSAR, and how the reports correspond to the stated objectives of the standard. It is also discussed to what extent these effects can be generalized to other types of refactoring.

National Category
Software Engineering
Identifiers
urn:nbn:se:mdh:diva-13596 (URN)10.1109/SEAA.2011.44 (DOI)2-s2.0-82955227638 (Scopus ID)978-076954488-5 (ISBN)
Conference
37th EUROMICRO Conference on Software Engineering and Advanced Applications, SEAA 2011;Oulu;30 August 2011through2 September 2011
Available from: 2011-12-15 Created: 2011-12-15 Last updated: 2014-12-12Bibliographically approved
2. Characteristics of a System Refactoring Process in Embedded Systems Development
Open this publication in new window or tab >>Characteristics of a System Refactoring Process in Embedded Systems Development
2012 (English)Conference paper, Published paper (Refereed)
National Category
Software Engineering Embedded Systems
Identifiers
urn:nbn:se:mdh:diva-14578 (URN)
Conference
7th Workshop on SHAring and Reusing architectural Knowledge, Helsinki, 2012
Note

Submitted

Available from: 2012-05-07 Created: 2012-05-07 Last updated: 2015-10-12Bibliographically approved
3. An empirical study of refactoring decisions in embedded software and systems
Open this publication in new window or tab >>An empirical study of refactoring decisions in embedded software and systems
2012 (English)In: Procedia Computer Science, ISSN 1877-0509, E-ISSN 1877-0509, Vol. 8, 279-284 p.Article in journal (Refereed) Published
Abstract [en]

This paper describes an empirical study of decision-making when changing the architecture in embedded systems. A refactoring of the system architecture often gives effects on both system properties and functions in the company organization, and there is a lack of efficient analysis methods for decision support in the system architecture process. This study investigates the information needed to make a decision about a system refactoring. Scenario-based interviews have been conducted with managers and system architects from companies developing embedded systems. The results show that the companies investigate similar issues regardless of their industry sector. The most wanted information prior to a decision is also presented.

National Category
Software Engineering Embedded Systems
Identifiers
urn:nbn:se:mdh:diva-14580 (URN)10.1016/j.procs.2012.01.058 (DOI)000306293000040 ()2-s2.0-84896998728 (Scopus ID)
Conference
10th Annual Conference on Systems Engineering Research (CSER) Location: St Louis, MO Date: MAR 19-22, 2012
Funder
XPRES - Initiative for excellence in production research
Available from: 2012-05-07 Created: 2012-05-07 Last updated: 2017-12-07Bibliographically approved
4. Analysis of the Business Effects of Software Architecture Refactoring in an Automotive Development Organization
Open this publication in new window or tab >>Analysis of the Business Effects of Software Architecture Refactoring in an Automotive Development Organization
2010 (English)In: Proceedings - 36th EUROMICRO Conference on Software Engineering and Advanced Applications, SEAA 2010, 2010, 269-278 p.Conference paper, Published paper (Refereed)
Abstract [en]

This paper presents an exploratory study of an automotive manufacturer, which develops embedded software for over 150 products and has adopted a company-wide software product-line approach. The company is facing the introduction of a new software architecture in all products in near time. This architecture introduces new paradigms more explicitly, such as explicit software components and signal-based communication, newer technologies, and adheres to new standards. Concretely, the architecture consists of common infrastructure and other generic components. Such a fundamental and drastic technology change can be expected to have far-reaching consequences, both of technical and non-technical nature. In this study we systematically investigate the introduction of the new software architecture, by mapping individual elements of the architectural change to system properties and company functions. The study implies that the whole organization is affected, and the new architecture also influences the cooperation with suppliers.

National Category
Engineering and Technology
Identifiers
urn:nbn:se:mdh:diva-10849 (URN)10.1109/SEAA.2010.13 (DOI)000395720700035 ()2-s2.0-78449304324 (Scopus ID)978-076954170-9 (ISBN)
Conference
36th EUROMICRO Conference on Software Engineering and Advanced Applications, SEAA 2010; Lille; France; 1 September 2010 through 3 September 2010
Available from: 2010-11-10 Created: 2010-11-10 Last updated: 2014-12-12Bibliographically approved

Open Access in DiVA

fulltext(959 kB)1129 downloads
File information
File name FULLTEXT02.pdfFile size 959 kBChecksum SHA-512
c6120813df74aa683b41a8db0b3e09addba6ec30c0485b7ccfae9ddc670dd41b343993b6eb3e843e413f1068c9a371b9ede84653e67a1c89ce85495e57cb49c5
Type fulltextMimetype application/pdf

Search in DiVA

By author/editor
Dersten, Sara
By organisation
School of Innovation, Design and Engineering
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 1129 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: 724 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • 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