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
Architectural reuse in software systems in-house integration and merge - Experiences from industry
Mälardalen University, School of Innovation, Design and Engineering, Embedded Systems.ORCID iD: 0000-0002-0921-0878
Mälardalen University, School of Innovation, Design and Engineering. Eindhoven University of Technology, Department of Mathematics and Computing Science, Netherlands.
2005 (English)In: Lect. Notes Comput. Sci., 2005, 123-139 p.Conference paper, Published paper (Refereed)
Resource type
Text
Abstract [en]

When organizations cooperate closely, for example after a company merger, there is typically a need to integrate their in-house developed software into one coherent system, preferably by reusing from all of the existing systems. The parts that can be reused may be arbitrarily small or large, ranging from code snippets to large self-containing components. Not only implementations can be reused however; sometimes it may be more appropriate to only reuse experiences in the form of architectural solutions and requirements. In order to investigate the circumstances under which different types of reuse are appropriate, we have performed a multiple case study, consisting of nine cases. Our conclusions are, summarized: reuse of components from one system requires reuse of architectural solutions from the same system; merge of architectural solutions cannot occur unless the solutions already are similar, or if some solutions from one are incorporated into the other. In addition, by hierarchically decomposing the systems we make the same observations. Finally, among the cases we find more architectural similarities than might had been expected, due to common domain standards and common solutions within a domain. Although these observations, when presented, should not be surprising, our experiences from the cases show that in practice organizations have failed to recognize when the necessary prerequisites for reuse have not been present.

Place, publisher, year, edition, pages
2005. 123-139 p.
Series
Lecture Notes in Computer Science, ISSN 0302-9743 ; 3712 LNCS
Keyword [en]
Computer architecture, Computer software, Mergers and acquisitions, Standards, Architectural reuse, Architectural solutions, Self-containing components, Software systems, Software engineering
Identifiers
URN: urn:nbn:se:mdh:diva-31911DOI: 10.1007/11558569_10Scopus ID: 2-s2.0-33646185616ISBN: 3540290338 (print)ISBN: 9783540290339 (print)OAI: oai:DiVA.org:mdh-31911DiVA: diva2:937509
Conference
20 September 2005 through 22 September 2005, Erfurt
Available from: 2016-06-15 Created: 2016-06-14 Last updated: 2016-06-15Bibliographically approved

Open Access in DiVA

No full text

Other links

Publisher's full textScopus

Search in DiVA

By author/editor
Crnković, IvicaLarsson, Stig
By organisation
Embedded SystemsSchool of Innovation, Design and Engineering

Search outside of DiVA

GoogleGoogle Scholar

Altmetric score

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