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
Are limited non-intrusive CMMI-based appraisals enough?
Mälardalen University, Department of Computer Science and Electronics.ORCID iD: 0000-0002-0921-0878
2003 (English)In: Proceedings of the ESEIW 2003 Workshop on Empirical Studies in Software Engineering WSESE 2003, 2003Conference paper, Published paper (Refereed)
Abstract [en]

An integral part of the strategy for performance improvement within the product development at ABB is the use of CMMI-based appraisals. Each appraisal represents an investment by the organization to lay the best possible foundation for improvements. The challenge is to balance the investment, the intrusiveness and the benefits. Depending on different organizational characteristics, different kinds of appraisals should be used. All appraisals are driven by data collection and consequently the quality of an appraisal depends on the data collection methods used. In this paper we outline strategies used in ABB for selection of appropriate CMMI appraisals and data collection methods. Early results indicate that the use of a series of appraisals can be a way to overcome the resistance in an organization. We also claim that a discussion is needed on the reliability and validity of the appraisal methodologies and on the feasibility to base decisions regarding process improvement strategies on appraisal results.

Place, publisher, year, edition, pages
2003.
National Category
Production Engineering, Human Work Science and Ergonomics
Identifiers
URN: urn:nbn:se:mdh:diva-4114OAI: oai:DiVA.org:mdh-4114DiVA: diva2:120899
Available from: 2005-11-18 Created: 2005-11-18 Last updated: 2015-06-30Bibliographically 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

Search in DiVA

By author/editor
Larsson, Stig
By organisation
Department of Computer Science and Electronics
Production Engineering, Human Work Science and Ergonomics

Search outside of DiVA

GoogleGoogle Scholar

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