Patterns of conflict among software components
Journal of Systems and Software
Software systems in-house integration: Architecture, process practices, and strategy selection
Information and Software Technology
Florida Public Hurricane Loss Model (FPHLM): research experience in system integration
dg.o '08 Proceedings of the 2008 international conference on Digital government research
Computer Standards & Interfaces
| Hi-index | 0.00 |
Software systems no longer evolve as separate entities butare also integrated with each other. The purpose ofintegrating software systems can be to increase user-valueor to decrease maintenance costs. Different approaches,one of which is software architectural analysis, can beused in the process of integration planning and design.This paper presents a case study in which three softwaresystems were to be integrated. We show how architecturalreasoning was used to design and compare integrationalternatives. In particular, four different levels of theintegration were discussed (interoperation, a so-calledEnterprise Application Integration, an integration based ona common data model, and a full integration). We alsoshow how cost, time to delivery and maintainability of theintegrated solution were estimated.On the basis of the case study, we analyze the advantagesand limits of the architectural approach as such andconclude by outlining directions for future research: howto incorporate analysis of cost, time to delivery, and risk inarchitectural analysis, and how to make architecturalanalysis more suitable for comparing many aspects ofmany alternatives during development. Finally we outlinethe limitations of architectural analysis.