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
On the expected synergies between component-based software engineering and best practices in production integration
Mälardalen University, Department of Computer Science and Electronics.ORCID iD: 0000-0002-5278-755X
2004 (English)In: Proceeding EUROMICRO '04 Proceedings of the 30th EUROMICRO Conference, 2004, 430-436 p.Conference paper, Published paper (Refereed)
Abstract [en]

The expectations for a well working integration process are described in the Capability Maturity Model Integration (CMMI). Often during the integration process, weaknesses of the entire development process become visible. This is usually too late and too costly. Particular development processes and use of particular technologies may help to improve the performance of the integration process by providing proper input to it. For example, by the use of a component-based approach, the development process changes. Some of these changes may help in performing according to the process expectations. In this paper, examples of problems that have been observed in the integration process are described. Through a case study we describe a number of practical problems in current development projects. Based on this case study, we analyze how a component-based approach could help and lead to a more effective integration process.

Place, publisher, year, edition, pages
2004. 430-436 p.
National Category
Engineering and Technology
Identifiers
URN: urn:nbn:se:mdh:diva-4116DOI: 10.1109/EUROMICRO.2004.63ISBN: 0-7695-2199-1 (print)OAI: oai:DiVA.org:mdh-4116DiVA: diva2:120901
Available from: 2005-11-18 Created: 2005-11-18 Last updated: 2013-12-19Bibliographically approved
In thesis
1. Improving software product integration
Open this publication in new window or tab >>Improving software product integration
2005 (English)Licentiate thesis, comprehensive summary (Other scientific)
Abstract [en]

The idea with product integration is that separate components are combined into a working system. However, this process of assembling parts into bigger units, products and systems is not well performed in industry, especially not when a substantial part of the product functionality is implemented in software. Many faults that are introduced in early phases are found as late as in the product integration phase, or even worse, in the verification or validation of the final delivery, or after delivery of the product or system. This leads to high costs for error correction and additional efforts for re-testing. There is consequently a need to further investigate the area of product integration to understand how the performance can be improved. Different practices have been described in standards and models, but the area is still under development. No widely agreed upon body-of-knowledge has so far been defined for product integration. A large part of the development of products containing software for industrial use is conducted in small or medium sized teams. This requires that any data collection methods used to acquire reliable information regarding performance in a project or organization minimize the intrusion. A facilitating approach was needed to understand how units with distinct characteristics should be approached. Based on several years of interaction with different types of organization, the presented research includes an analysis of various methods for data collection. The result is a proposed method for selecting different sizes of investigations based on the openness and maturity of the organization. The main purpose of this research is to understand which factors influence the integration process and what can be done to improve the execution of it. It includes investigations to understand if the described best practices are appropriate, and if there are other means to achieve successful product integration. The research combines investigations of existing compilations of best practices with case studies in industry. Our conclusion is that the type of organization that we have investigated can reduce problems in the product integration process by following the basic practices described in standards and reference models. Problems found in product integration can in most cases be related to the fact that the organization does not follow the proposed practices. The investigations have revealed that the practices are not used in a sufficient way, that additional efforts must be put into fulfilling the requirements in standards and models, and that it is difficult to implement the practices. We have also found indications that specific technology, component based software, may assist in executing the practices. Finally, we conclude that not all standards and models include support to avoid all types of problems in product integration. This is an indication that the on-going development of the area is necessary and that an increased agreement on what can be considered to be best practices is needed.

Place, publisher, year, edition, pages
Västerås: Institutionen för Datavetenskap och Elektronik, 2005. 108 p.
Series
Mälardalen University Press Licentiate Theses, ISSN 1651-9256 ; 51
Identifiers
urn:nbn:se:mdh:diva-41 (URN)91-88834-65-4 (ISBN)
Available from: 2005-11-18 Created: 2005-11-18 Last updated: 2013-12-19

Open Access in DiVA

No full text

Other links

Publisher's full text

Search in DiVA

By author/editor
Larsson, StigCrnkovic, Ivica
By organisation
Department of Computer Science and Electronics
Engineering and Technology

Search outside of DiVA

GoogleGoogle Scholar

Altmetric score

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