Content deleted Content added
mNo edit summary |
JakeBosworth (talk | contribs) m grammar |
||
| (25 intermediate revisions by 17 users not shown) | |||
Line 1:
{{short description|Bringing together component sub-systems into one system}}
{{Software development process}}
'''System integration''' is defined in [[engineering]] as the process of bringing together the component sub-[[system]]s into one system (an aggregation of subsystems cooperating so that the system is able to deliver the overarching functionality) and ensuring that the subsystems function together as a system,<ref name="Heat">{{Citation| last = Gilkey| first = Herbert T | year = 1960| contribution = New Air Heating Methods| title= New methods of heating buildings: a research correlation conference conducted by the Building Research Institute, Division of Engineering and Industrial Research, as one of the programs of the BRI fall conferences, November 1959.| publisher=National Research Council (U.S.). Building Research Institute| place=Washington | pages = 60 | oclc =184031}}</ref> and in [[information technology]]<ref>For computer systems, the term "systems integration" has included the plural word "systems" although the singular form has also been used in referring to computer systems.</ref> as the process of linking together different [[computing]] systems and
The [[system integrator]] [[data integration|integrates]] discrete systems utilizing a variety of techniques such as [[computer network]]ing, [[enterprise application integration]], [[business process management]] or manual [[Computer programming|programming]].<ref name="Info">{{Citation| last=Moore | first=June | date =13 December 1982| contribution= Software Reviews, BusinessMaster II+, ledger for CP/M systems| title=InfoWorld | publisher=InfoWorld Media Group, Inc| page = 31 | issn=0199-6649}}</ref>
Line 8:
==Methods of integration==
'''[[Vertical integration]]''' (as opposed to "[[horizontal integration]]") is the process of integrating subsystems according to their functionality by creating functional entities also referred to as [[Information silo|silos]].<ref name="E-gov">{{Citation | last = Lau| first = Edwin | year =2005
| contribution = Multi-channel Service Delivery|title=OECD e-Government Studies e-Government for Better Government|publisher=OECD| place =Paris|pages = 52| isbn = 9789264018334 |oclc =224889830}}</ref> The benefit of this method is that the integration is performed quickly and involves only the necessary vendors, therefore, this method is cheaper in the short term. On the other hand, cost-of-ownership can be substantially higher than seen in other methods, since in case of new or enhanced functionality, the only possible way to implement (scale the system) would be by implementing another silo. Reusing subsystems to create another functionality is not possible.<ref name="Integ">{{Citation | last1 = Gold-Bernstein| first1 = Beth| last2 = Ruh| first2 = William A| year =2005|title=Enterprise integration: the essential guide to integration solutions|publisher=Addison Wesley|isbn= 0-321-22390-X}}</ref>
'''Star integration''', also known as '''spaghetti integration''', is a process of systems integration where each system is interconnected to each of the remaining subsystems. When observed from the perspective of the subsystem which is being integrated, the connections are reminiscent of a star, but when the overall diagram of the system is presented, the connections look like spaghetti, hence the name of this method. The cost varies because of the interfaces that subsystems are exporting. In a case where the subsystems are exporting heterogeneous or proprietary interfaces, the integration cost can substantially rise. Time and costs needed to integrate the systems increase exponentially when adding additional subsystems. From the feature perspective, this method often seems preferable, due to the extreme flexibility of the reuse of functionality.<ref name="Integ"/>
Line 16:
The horizontal scheme can be misleading, however, if it is thought that the cost of intermediate data transformation or the cost of shifting responsibility over business logic can be avoided.<ref name="Integ"/>
'''Industrial lifecycle integration''' is a system integration process that considers four categories or stages of integration: initial system implementation, engineering and design, project services, and operations.<ref>{{Cite web|title=The Value of Data-Centric Execution Architecture in System Integration Frameworks for Industrial Energy Assets|url=https://www.vistaprojects.com/system-integration/|website=Vista Projects Limited}}</ref> This approach incorporates the requirements of each lifecycle stage of the industrial asset when integrating systems and subsystems. The key output is a standardized data architecture that can function throughout the life of the asset.
A '''common data format''' is an integration method to avoid every adapter having to [[data conversion|convert data]] to/from every other applications' formats, [[Enterprise application integration]] (EAI) systems usually stipulate an application-independent (or common) data format.<ref>{{Citation|title=Aircraft/Store Common Interface Control Document Format Standard|publisher=SAE International|doi=10.4271/as5609a}}</ref> The EAI system usually provides a data transformation service as well to help convert between application-specific and common formats. This is done in two steps: the adapter converts information from the application's format to the bus' common format. Then, semantic transformations are applied on this (converting zip codes to city names, splitting/merging objects from one application into objects in the other applications, and so on).
==Challenges of integration==
System integration can be challenging for organizations and these challenges can diminish their overall return on investment after implementing new software solutions. Some of these
On the other hand, system integration projects can be incredibly rewarding. For out-of-date, legacy systems, different forms of integration offer the ability to enable real-time data sharing. This can enable, for example, [[Publish–subscribe pattern|publisher-subscriber]] data distribution models, consolidated databases, [[Event-driven architecture|event-driven architectures]], reduce manual user data entry (which can also help reduce errors), refresh or modernize the application's front-end, and offload querying and reporting from expensive operational systems to cheaper commodity systems (which can save costs, enable scalability, and free up processing power on the main operational system). Usually, an extensive [[Cost–benefit analysis|cost-benefit analysis]] is undertaken to help determine whether an integration project is worth the effort.
==See also==
{{div col|colwidth=25em}}
* [[Artificial intelligence systems integration]]
* [[Configuration design]]▼
* [[Continuous integration]]
*[[System in package]] and [[system on a chip]]▼
▲* [[Enterprise application integration]]
* [[Integration platform]]▼
* [[Integration Competency Center]]
▲* [[Integration platform]]
* [[Interoperability]]
* [[Modular design]]▼
* [[Multidisciplinary approach]]▼
* [[System of record]]
* [[Systems integrator]]
▲* [[Multidisciplinary approach]]
▲* [[Cloud-based integration]]
* [[System design]]
▲* [[System in package]] and [[system on a chip]]
▲* [[Modular design]]
{{div col end}}
▲* [[Configuration design]]
==References==
Line 44 ⟶ 49:
==External links==
* [http://www.controlsys.org CSIA (Control System Integrators Association)]
{{Systems Engineering}}
{{Authority control}}
[[Category:System integration| ]]
[[Category:Systems analysis]]
[[Category:Systems engineering]]
| |||