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
Software In-House Integration: Quantified Experiences from Industry
Mälardalen University, Department of Computer Science and Electronics.
Mälardalen University, Department of Computer Science and Electronics.ORCID iD: 0000-0003-3322-437X
Mälardalen University, Department of Computer Science and Electronics.ORCID iD: 0000-0002-0921-0878
Mälardalen University, Department of Computer Science and Electronics.ORCID iD: 0000-0002-5278-755X
2006 (English)In: Proceedings 32nd Euromicro Conference onSoftware Engineering and Advanced Applications (SEAA), 2006, 198-205 p.Conference paper, Published paper (Other academic)
Abstract [en]

When an organization faces new types of collaboration, for example after a company merger, there is a need to consolidate the existing in-house developed software. There are many high-level strategic decisions to be made, which should be based on as good foundation as possible, while these decisions must be made rapidly. Also, one must employ feasible processes and practices in order to get the two previously separate organizations to work towards a common goal. In order to study this topic, we previously performed an explorative and qualitative multiple case study, where we identified a number of suggested practices as well as other concerns to take into account. This paper presents a follow-up study, which aims at validating and quantifying these previous findings. This study includes a questionnaire distributed to in-house integration projects, aiming at validation of earlier findings. We compare the data to our previous conclusions, present observations on retirement of the existing systems and on the technical similarities of the existing systems. We also present some practices considered important but often neglected.

Place, publisher, year, edition, pages
2006. 198-205 p.
National Category
Engineering and Technology
Identifiers
URN: urn:nbn:se:mdh:diva-4008DOI: 10.1109/EUROMICRO.2006.57ISI: 000242376100025Scopus ID: 2-s2.0-34547405866ISBN: 0-7695-2594-6 (print)OAI: oai:DiVA.org:mdh-4008DiVA: diva2:120525
Conference
32nd EUROMICRO Conference onSoftware Engineering and Advanced Applications, 2006. SEAA '06, Cavtat/Dubrovnik (Croatia) August 29 - September 1, 2006
Available from: 2006-07-18 Created: 2006-07-18 Last updated: 2014-01-10Bibliographically approved
In thesis
1. Software Systems In-House Integration: Observations and Guidelines Concerning Architecture and Process
Open this publication in new window or tab >>Software Systems In-House Integration: Observations and Guidelines Concerning Architecture and Process
2006 (English)Doctoral thesis, comprehensive summary (Other scientific)
Abstract [en]

Software evolution is a crucial activity for software organizations. A specifc type of software evolution is the integration of previously isolated systems. The need for integration is often a consequence of different organizational changes, including merging of previously separate organizations. One goal of software integration is to increase the value to users of several systems by combining their functionality, another is to reduce functionality overlap. If the systems are completely owned and controlled in-house, there is an additional advantage in rationalizing the use of internal resources by decreasing the amount of software with essentially the same purpose. Despite in-house integration being common, this topic has received little attention from researchers. This thesis contributes to an increasing understanding of the problems associated with in-house integration and provides guidelines to the more efficient utilization of the existing systems and the personnel.

In the thesis, we combine two perspectives: software architecture and processes. The perspective of software architecture is used to show how compatibility analysis and development of integration alternatives can be performed rapidly at a high level of abstraction. The software process perspective has led to the identification of important characteristics and practices of the integration process. The guidelines provided in the thesis will help those performing future in-house integration to make well-founded decisions timely and efficiently.

The contributions are based on several integration projects in industry, which have been studied systematically in order to collect, evaluate and generalize their experiences.

Place, publisher, year, edition, pages
Västerås: Institutionen för Datavetenskap och Elektronik, 2006. 320 p.
Series
Mälardalen University Press Dissertations, ISSN 1651-4238 ; 31
Keyword
Architectural Compatibility, Software Architecture, Software Integration, Software Merge, Software Processes, Strategic Decisions
National Category
Computer Science
Research subject
Datavetenskap
Identifiers
urn:nbn:se:mdh:diva-146 (URN)91-85485-20-9 (ISBN)
Public defence
2006-09-15, Zeta, T, Högskoleplan 1, Västerås, 10:00
Opponent
Supervisors
Available from: 2006-07-18 Created: 2006-07-18

Open Access in DiVA

No full text

Other links

Publisher's full textScopus

Search in DiVA

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

Search outside of DiVA

GoogleGoogle Scholar

Altmetric score

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