[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-240744-105":53,"doc-detail-240744-en":127},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","integration-of-software-systems-process-challenges","Integration of Software Systems - Process Challenges","","Integration of existing software systems requires different assumptions, requirements, and goals than typical maintenance and development, which leads to distinct integration processes. When similarities exist, proven processes should be reused. The paper analyzes how a recently merged company handled integration planning for three systems, identifying key observations that characterize the approach and outlining challenges that remain for future work.",{"@graph":63,"@context":119},[64,80,102],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/integration-of-software-systems-process-challenges/240744/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/integration-of-software-systems-process-challenges/240744.png","ImageObject",442,249,{"name":88,"@type":89},"Mack Lee","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-19","2026-09-11",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",10,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"Why does software integration differ from other software activities like maintenance and development?","Question",{"text":109,"@type":110},"Software integration involves different assumptions, requirements, and goals compared with maintenance and development, so the integration processes should also differ.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What was the main goal of the case study in this paper?",{"text":114,"@type":110},"To decide on an integration approach for three systems after a company merger, focusing on the architectural-level decision process.",{"name":116,"@type":107,"acceptedAnswer":117},"How did the decision process evolve during the meetings before a final choice was made?",{"text":118,"@type":110},"Initial meetings led to “almost” agreements, repeated three times with no decision; after about half a year, higher management mandated a more structured effort split into Evaluation, Design, and Decision phases.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},240744,1791166636,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":79,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":73},1236954509970,"https://us-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","Integration of Software Systems – Process Challenges  \nRikard Land, Ivica Crnkovic, Christina Wallin  \nMälardalen University  \nDepartment of Computer Science and Engineering  \nPO Box 883, SE-721 23 Västerås, Sweden  \n+46 21 10 70 35, +46 21 10 31 83  \n{[rikard.land](rikard.land), ivica.crnkovic, [christina.wallin}@mdh.se](christina.wallin}@mdh.se)  \n[http://www.idt.mdh.se/{](http://www.idt.mdh.se/{)~rld, ~icc}  \nAbstract  \nThe assumptions, requirements, and goals of integrating existing software systems are different compared to other software activities such as maintenance and development, implying that the integration processes should be different. But where there are similarities, proven processes should be used.  \nIn this paper, we analyze the process used by a recently merged company, with the goal of deciding on an integration approach for three systems. We point out observations that illustrate key elements of such a process, as well as challenges for the future.  \nKeywords  \nSoftware Architecture, Software Evolution, Software Integration, Software Process Improvement.  \n1. Introduction  \nSoftware integration as a special type of software evolution has become more and more important in recent years [7], but brings new challenges and complexities. There are many reasons for software integration; in many cases software integration is a result of company mergers. In this paper we describe such a case, which illustrates the challenges of the decision process involved in deciding the basic principles of the integration on the architectural level.  \n2. Case Study  \nOur case study concerns a large North-American industrial enterprise with thousands of employees that acquired a smaller (~800 employees) European company in the same, non-software, business area where software, mainly in-house developed, is used for simulations and management of simulation data, [i.e. as](i.e. as) tools for development and production of other products. The expected benefits of an integration were increased value for users (more functionality and all related data collected in the same system) as well as more efficient use of software development and maintenance resources. The first task was to make a decision on an architecture to choose for the  \nintegrated system. The present paper describes this decision process.  \nFigure 1 describes the architectures of the three existing systems in a high-level diagram blending an execution view with a code view [3] . The most modern system is built with a three-tier architecture in Java 2 Enterprise Edition (J2EE), while the two older systems are designed to run in a Unix environment with only a thin “X”client displaying the user interface (the “thin” client is denoted by a rectangle with zero height in the figure); they are written mostly in Tcl and C++, and C++ with the use of Motif. The Tcl/C++ system contains ~350 KLOC (thousands of lines of code), the C++/Motif system 140 KLOC, and the Java system 90 KLOC. The size of the rectangles in the figure indicates the relative sizes between the components of the systems (as measured in lines of code) . The Tcl/C++ system uses a proprietary objectoriented database, implemented as files accessed through library functions, while the two other systems, which were developed at the same site, share data in a common commercial relational database executing as a database server.  \nSince the two software development departments (the North American and the European) had cooperated only toa small extent beforehand, the natural starting point was simply to meet and discuss solutions. The managers of the software development departments accompanied by a few software developers met for about a week, outlined several high-level alternatives and discussed their implications both in terms of the integrated system’s technical features and the impact on the organization. Since the requirements for the integrated system was basically to provide the same functionality as the existin","cbCaieArEUjcqHN0","https://ap.wps.com/l/cbCaieArEUjcqHN0","pdf",198563,"English","# Abstract\n# 1. Introduction\n# 2. Case Study","[{\"question\":\"Why does software integration differ from other software activities like maintenance and development?\",\"answer\":\"Software integration involves different assumptions, requirements, and goals compared with maintenance and development, so the integration processes should also differ.\"},{\"question\":\"What was the main goal of the case study in this paper?\",\"answer\":\"To decide on an integration approach for three systems after a company merger, focusing on the architectural-level decision process.\"},{\"question\":\"How did the decision process evolve during the meetings before a final choice was made?\",\"answer\":\"Initial meetings led to “almost” agreements, repeated three times with no decision; after about half a year, higher management mandated a more structured effort split into Evaluation, Design, and Decision phases.\"}]","Integration of Software Systems - Process Challenges | PDF",1789165207]