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 Systems Integration and Architectural Analysis: A Case Study
Mälardalen University, Department of Computer Science and Electronics.
Mälardalen University, Department of Computer Science and Electronics.ORCID iD: 0000-0002-5278-755X
2003 (English)In: IEEE International Conference on Software Maintenance, ICSM2003, 2003, 338-347 p.Conference paper, Published paper (Other academic)
Abstract [en]

Software systems no longer evolve as separate entities but are also integrated with each other. The purpose of integrating software systems can be to increase user-value or to decrease maintenance costs. Different approaches, one of which is software architectural analysis, can be used in the process of integration planning and design. This paper presents a case study in which three software systems were to be integrated. We show how architectural reasoning was used to design and compare integration alternatives. In particular, four different levels of the integration were discussed (interoperation, a so-called Enterprise Application Integration, an integration based on a common data model, and a full integration). We also show how cost, time to delivery and maintainability of the integrated solution were estimated. On the basis of the case study, we analyze the advantages and limits of the architectural approach as such and conclude by outlining directions for future research: how to incorporate analysis of cost, time to delivery, and risk in architectural analysis, and how to make architectural analysis more suitable for comparing many aspects of many alternatives during development. Finally we outline the limitations of architectural analysis.

Place, publisher, year, edition, pages
2003. 338-347 p.
National Category
Computer Systems
Identifiers
URN: urn:nbn:se:mdh:diva-4005DOI: 10.1109/ICSM.2003.1235441ISI: 000185997500040Scopus ID: 2-s2.0-77956613703ISBN: 0-7695-1905-9 (print)OAI: oai:DiVA.org:mdh-4005DiVA: diva2:120522
Conference
International Conference on Software Maintenance; Amsterdam,; Netherlands; 22 September 2003 through 26 September 2003
Available from: 2006-07-18 Created: 2006-07-18 Last updated: 2015-07-29Bibliographically 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, RikardCrnkovic, Ivica
By organisation
Department of Computer Science and Electronics
Computer Systems

Search outside of DiVA

GoogleGoogle Scholar

Altmetric score

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