Author List: Li, Xitong; Madnick, Stuart E.;
Journal of Management Information Systems, 2015, Volume 32, Issue 2, Page 104-133.
Despite the potential benefits, many organizations have failed in service-oriented architecture (SOA) implementation projects. Prior research often used a variance perspective and neglected to explore the complex interactions and timing dependencies between the critical success factors. This study adopts a process perspective to capture the dynamics while providing a new explanation for the mixed outcomes of SOA implementation. We develop a system dynamics model and use simulation analysis to demonstrate the phenomenon of Òtipping point.Ó That is, under certain conditions, even a small reduction in the duration of normative commitment can dramatically reverse, from success to failure, the outcome of an SOA implementation. The simulation results also suggest that (1) the duration of normative commitment can play a more critical role than the strength, and (2) the minimal duration of normative commitment for a successful SOA implementation is associated positively with the information delay of organizational learning of SOA knowledge. Finally, we discuss the theoretical causes and organizational traps associated with SOA implementation to help IT managers make better decisions about their implementation projects. > >
Keywords: normative commitment; organizational traps; service-oriented architecture (SOA); system dynamics; tipping point
Algorithm:

List of Topics

#54 0.219 approach conditions organizational actions emergence dynamics traditional theoretical emergent consequences developments case suggest make organization point outcomes recent trajectory claims
#43 0.132 architecture scheme soa distributed architectures layer discuss central difference coupled service-oriented advantages standard loosely table services classification layered included update
#251 0.130 implementation erp enterprise systems resource planning outcomes support business associated understanding benefits implemented advice key implementing scope functional post-implementation implementations
#44 0.123 approach analysis application approaches new used paper methodology simulation traditional techniques systems process based using proposed method present provides various
#139 0.123 project projects failure software commitment escalation cost factors study problem resources continue prior escalate overruns taken failing troubled sunk fail
#161 0.077 role relationship positively light important understanding related moderating frequency intensity play stronger shed contribution past considered maintenance effort effect specifically
#198 0.075 factors success information critical management implementation study factor successful systems support quality variables related results key model csf importance determinants