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
Key Elements of Software Product Integration Processes
Mälardalen University, Department of Computer Science and Electronics.ORCID iD: 0000-0002-0921-0878
2007 (English)Doctoral thesis, comprehensive summary (Other scientific)
Abstract [en]

The product integration is a particularly critical phase of the software product development process as many problems originating from earlier phases become visible in this phase. Problems in product integration result in delays and rework. One of the measures to decrease the late discovery of problems is the use of development standards and guidelines that define practices to ensure correctness of the product integration. However, even if such standards and reference models exist, they are in not used consistently. One of the reasons is a lack of a proof that they indeed improve the integration process, and even more important, that they are sufficient for performing efficient and correct product integration.

The conclusion of the presented research is that the available descriptions in standards and reference models taken one by one are insufficient and must be consolidated to help development organizations improve the product integration process. The research has resulted in a proposed combination of the activities included in the different reference models. This combination has been based on a number of case studies. Through the case studies performed in seven different product development organizations, a relationship between problems that are observed and the failure to follow the recommendations in reference models is identified. The analysis has indicated which practices are necessary, and how other practices support these. The goal with the research is to provide product development organizations with guidelines for how to perform software product integration.

One additional finding of the research is the existence of relation between software architecture and the development process. A method for identifying dependencies between evolvement of software architectures and adaptation of integration practices has been demonstrated.

Place, publisher, year, edition, pages
Institutionen för datavetenskap och elektronik , 2007. , p. 62
Series
Mälardalen University Press Dissertations, ISSN 1651-4238 ; 50
Keywords [en]
product integration, software development, process improvement
National Category
Software Engineering
Research subject
Computer Science
Identifiers
URN: urn:nbn:se:mdh:diva-444ISBN: 978-91-85485-61-1 (print)OAI: oai:DiVA.org:mdh-444DiVA, id: diva2:120956
Public defence
2007-12-06, Delta, R-huset, Högskoleplan 1, Västerås, Västerås, 10:00
Opponent
Supervisors
Available from: 2007-10-29 Created: 2007-10-29 Last updated: 2018-01-13Bibliographically approved
List of papers
1. On the Expected Synergies between Component-Based Software Engineering and Best Practices in Product Integration
Open this publication in new window or tab >>On the Expected Synergies between Component-Based Software Engineering and Best Practices in Product Integration
2004 (English)In: Proceedings of the 30th EUROMICRO Conference, 2004, p. 430-436Conference paper, Published paper (Other academic)
Abstract [en]

The expectations for a well working integration process are described in the Capability Maturity Model Integration (CMMI). Often during theintegration 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 acomponent-based approach could help and lead to a more effective integration process.

National Category
Software Engineering
Identifiers
urn:nbn:se:mdh:diva-4129 (URN)2-s2.0-11844263320 (Scopus ID)
Conference
30th EUROMICRO Conference; Rennes; France; 31 August 2004 through 3 September 2004
Available from: 2007-10-29 Created: 2007-10-29 Last updated: 2018-01-13Bibliographically approved
2. Case study: Software product integration practices
Open this publication in new window or tab >>Case study: Software product integration practices
2005 (English)In: Lecture Notes in Computer Science, vol. 3457, Springer, 2005, p. 272-285Chapter in book (Refereed)
Abstract [en]

Organizations often encounter problems in the Product Integration process. The difficulties include finding errors at integration related to mismatch between the different components and problems in other parts of the system than the one that was changed. The question is if these problems can be decreased if the awareness of the integration process is increased in other activities. To get better understanding of this problem we have analyzed the integration process in two product development organizations. One of the organizations has two different groups with slightly different integration routines while the other is basing the development on well defined components. The obstacles found in product integration are highlighted and related to best practices as described in the interim standard EIA-731.1. Our conclusion from this study is that the current descriptions for best practices in product integration are available in standards and models, but are insufficiently used and can be supported by technology to be accepted and utilized by the product developers

Place, publisher, year, edition, pages
Springer, 2005
Series
Lecture Notes in Computer Science, ISSN 0302-9743 ; 3457
National Category
Engineering and Technology
Identifiers
urn:nbn:se:mdh:diva-4117 (URN)10.1007/11497455_23 (DOI)000230389600021 ()978-3-540-26200-8 (ISBN)978-3-540-31640-4 (ISBN)
Note

6th International Conference on Product Focused Software Process Improvement, PROFES 2005; Oulu ;13 June 2005 through 18 June 2005

Available from: 2005-11-18 Created: 2005-11-18 Last updated: 2018-08-22Bibliographically approved
3. Product integration improvement based on analysis of build statistics
Open this publication in new window or tab >>Product integration improvement based on analysis of build statistics
2007 (English)In: 6th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering, ESEC/FSE 2007, 2007, p. 505-508Conference paper, Published paper (Other academic)
Abstract [en]

Process improvement efforts based on best practices and standards such as the CMMI use appraisal results as input and focus on implementing processes as described in reference models. Since these models are of a general character the conclusions from the assessments could easily overlook problems experienced in the daily work. In addition, process improvement programs often fail to engage practitioners. To improve this, data that can be related to the daily work can help. This paper reports on the results from a study performed to understand how process data can complement project appraisals in finding improvement possibilities. A method for mapping process data to different practices and combining this with project appraisals to form a basis for focused performance improvement is proposed and a study including four projects from three organizations is presented. 

National Category
Software Engineering
Identifiers
urn:nbn:se:mdh:diva-4131 (URN)10.1145/1287624.1287696 (DOI)2-s2.0-37849032494 (Scopus ID)978-159593811-4 (ISBN)
Conference
6th Joint Meeting of the European Software Engineering Conference and the 14th ACM SIGSOFT Symposium on the Foundations of Software Engineering, ESEC/FSE 2007; Dubrovnik; Croatia; 3 September 2007 through 7 September 2007
Available from: 2007-10-29 Created: 2007-10-29 Last updated: 2018-01-13Bibliographically approved
4. How to Improve Software Integration
Open this publication in new window or tab >>How to Improve Software Integration
(English)In: Information & Software Technology journalArticle in journal (Refereed) Submitted
National Category
Engineering and Technology
Identifiers
urn:nbn:se:mdh:diva-4132 (URN)
Available from: 2007-10-29 Created: 2007-10-29 Last updated: 2018-03-15Bibliographically approved
5. Assessing the Influence on Processes when Evolving the Software Architecture
Open this publication in new window or tab >>Assessing the Influence on Processes when Evolving the Software Architecture
2007 (English)In: 9th International Workshop on Principles of Software Evolution, IWPSE 2007, Held in Conjunction with the 6th ESEC/FSE Joint Meeting, 2007, p. 59-66Conference paper, Published paper (Other academic)
Abstract [en]

Software intensive products and systems evolve over the life-cycle. Changing business objectives may drive architectural or process changes. Altering either architecture or process mightinfluence the other. Also the organization may influence and be influenced. This paper describes these relationships and proposes a method for assessing the influence on process that a proposed architectural change can have. The method includes the use of scenarios and process reference models. A case study where the method has been used is described, identifying the need for changes in the processes to be able to utilize the advantages made possible due to the architectural evolution. The case study supports our proposal that a structured method to assess the impacts on process when changing the architecture of a system helps to reduce risks and to facilitate the envisioned business benefits. This also identifies the need to devise methods for other types of changes, e.g. how a process change may influence architecture or organization.

National Category
Engineering and Technology
Identifiers
urn:nbn:se:mdh:diva-4133 (URN)10.1145/1294948.1294963 (DOI)2-s2.0-41149116791 (Scopus ID)978-159593722-3 (ISBN)
Conference
9th International Workshop on Principles of Software Evolution, IWPSE 2007, Held in Conjunction with the 6th ESEC/FSE Joint Meeting; Dubrovnik; 3 September 2007 through 4 September 2007
Available from: 2007-10-29 Created: 2007-10-29 Last updated: 2016-09-27Bibliographically approved

Open Access in DiVA

fulltext(590 kB)8228 downloads
File information
File name FULLTEXT01.pdfFile size 590 kBChecksum MD5
504f62c8ac82261b1fca7e9fbb3cc45ad53cc557dab0e64b98a66face50de0e7efc7e950
Type fulltextMimetype application/pdf

Authority records BETA

Larsson, Stig

Search in DiVA

By author/editor
Larsson, Stig
By organisation
Department of Computer Science and Electronics
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar
Total: 8229 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: 591 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