mdh.sePublications
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
Limiting Practices in Developing and Managing Software-Intensive Systems: A Comparative Study
Mälardalen University, School of Innovation, Design and Engineering.ORCID iD: 0000-0002-2726-4503
Mälardalen University, School of Innovation, Design and Engineering.ORCID iD: 0000-0002-3530-2266
Mälardalen University, School of Innovation, Design and Engineering.ORCID iD: 0000-0002-0921-0878
Mälardalen University, School of Innovation, Design and Engineering.ORCID iD: 0000-0002-3986-1196
2010 (English)In: PICMET 2010: TECHNOLOGY MANAGEMENT FOR GLOBAL ECONOMIC GROWTH, Phuket, Thailand, 2010Conference paper, Published paper (Refereed)
Abstract [en]

Within the automotive industry, up to 90 percent of all new features are dependent on electronics and software. Consequently, the amount of software and electronics in vehicles is rapidly increasing. The same trend has been observed in other domains, such as telecom, avionics, trains, and more. An important factor in dealing with this inherent complexity is the use of a system architecture. The architecture is typically an enabler for both efficiency and effectiveness in the development of software-intensive systems but not directly connected to the customer needs. For example, the architecture can increase the agility of upcoming product releases in order to cost effectively satisfy future customer needs. By combining two parallel multiple case studies, one focusing on the architects view, and the other one focusing on the managerial perspective, we have identified six limitations. Our results indicate that the focus is on customer requirements for the current product, on the expense of the internal requirements related to the development of the architecture and long-term profitability. Further, even if the early phases of development are identified as a success criterion, they are still not given enough attention.

Place, publisher, year, edition, pages
Phuket, Thailand, 2010.
National Category
Engineering and Technology
Identifiers
URN: urn:nbn:se:mdh:diva-10864ISI: 000287527800168ISBN: 978-1-890843-22-9 (print)OAI: oai:DiVA.org:mdh-10864DiVA: diva2:369203
Conference
Portland International Center for Management of Engineering and Technology (PICMET 10) Location: Natl Elect & Comp Technol Ctr (NECTEC), Natl Sci & Technol Dev Agcy (NSTDA, Portland
Available from: 2010-11-10 Created: 2010-11-10 Last updated: 2016-09-27Bibliographically approved
In thesis
1. Identifying and Managing Key Challenges in Architecting Software-Intensive Systems
Open this publication in new window or tab >>Identifying and Managing Key Challenges in Architecting Software-Intensive Systems
2011 (English)Doctoral thesis, comprehensive summary (Other academic)
Abstract [en]

In many traditional industry applications, such as automotive, process automation and manufacturing automation, software plays a crucial role as an enabler for the introduction of new functionality and retaining competitiveness. The system and software architecture plays an important part in ensuring the systems’ qualities. However, the design of the architecture may be neglected during system development, whilst development efforts are centered on implementing new functionality. The architecture is supposed to support and enable key quality attributes such as safety, reliability, maintainability and flexibility, and so on. This thesis identifies some of the key issues in architecting these software intensive systems. In total, 21 issues have been identified; examples of these issues are (1) there is a lack of process for architecture development, (2) there is a lack of method or model to evaluate business value when choosing architecture, (3) there is a lack of clear long-term architectural strategy, and (4) processes and methods are less valued than individuals’ knowledge and competence. Through a series of workshops, root causes were identified for a selection of these issues. Based on these root causes, five success factors were identified. The success factors are (1) define an architectural strategy (2) implement a process for architectural work (3) ensure authority for architects (4) clarify the business impact of the architecture and (5) optimize on the project portfolio level instead of optimizing each project. In an attempt to provide a possible solution to some of the issues, a method has been created to evaluate how new functionality is successfully integrated into an existing architecture. The method is a combination of the Architecture Tradeoff Analysis Method, ATAM, and the Analytical Hierarchy Process, AHP. The method firstly supports a structured way of listing system goals, and secondly, it also supports design decision-making. Since several issues relate to the organization and are affected by management, a comparison was made between the view of management and architects. This study revealed that one cause for the lack of focus on architecture could be that the existing performance measurement systems used by management all focus on the later phases of development when the architecture is already set.

 

Place, publisher, year, edition, pages
Västerås: Mälardalen University, 2011
Series
Mälardalen University Press Dissertations, ISSN 1651-4238 ; 96
National Category
Information Science Software Engineering
Research subject
Computer Science
Identifiers
urn:nbn:se:mdh:diva-11816 (URN)978-91-7485-004-8 (ISBN)
Public defence
2011-03-18, Beta, Mälardalens högskola, Västerås, 09:00 (English)
Opponent
Supervisors
Projects
CoSy
Available from: 2011-02-14 Created: 2011-02-12 Last updated: 2016-09-27Bibliographically approved

Open Access in DiVA

No full text

Search in DiVA

By author/editor
Wallin, PeterCedergren, StefanLarsson, StigAxelsson, Jakob
By organisation
School of Innovation, Design and Engineering
Engineering and Technology

Search outside of DiVA

GoogleGoogle Scholar

Total: 38 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