System integration: Difference between revisions

Content deleted Content added
m Fix PMC warnings
Citation bot (talk | contribs)
Add: author pars. 1-1. Removed URL that duplicated unique identifier. Removed parameters. Some additions/deletions were actually parameter name changes. | You can use this bot yourself. Report bugs here. | Activated by Headbomb | via #UCB_webform
Line 20:
 
==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 challenging include lack of trust and willing to share data with other companies, unwillingness to outsource various operations to a third party, lack of clear communication and responsibilities, disagreement from partners on where functionality should reside, high cost of integration, difficulty finding good talents, and common [[Application programming interface|API]] standards.<ref>{{Cite journal|last=Gulledge|first=Thomas|date=September 2002|title=B2B eMarketplaces and small- and medium-sized enterprises|url=http://dx.doi.org/10.1016/s0166-3615(02)00058-1|journal=Computers in Industry|volume=49|issue=1|pages=47–58|doi=10.1016/s0166-3615(02)00058-1|issn=0166-3615}}</ref> These challenges result in creating hurdles that “prevent or slow down business systems integration within and among companies”.<ref>{{Cite journal|lastlast1=Hvolby|firstfirst1=Hans-Henrik|last2=Trienekens|first2=Jacques H.|date=December 2010|title=Challenges in business systems integration|url=http://dx.doi.org/10.1016/j.compind.2010.07.006|journal=Computers in Industry|volume=61|issue=9|pages=808–812|doi=10.1016/j.compind.2010.07.006|issn=0166-3615}}</ref> Clear communication and simplified information exchange are key elements in building long term system integrations that can support business requirements.
 
==See also==