Service-oriented architecture: Myths, realities, and a maturity model

MIS Quarterly Executive

Volumn 9, Issue 1, 2010, Pages 37-48

  Hirschheim, Rudy ^a   Welke, Richard ^b   Schwarz, Andrew ^a  

^a LOUISIANA STATE UNIVERSITY   (United States)

^b GEORGIA STATE UNIVERSITY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 79951897344     PISSN: 15401960     EISSN: 15401979     Source Type: Journal    
DOI: None     Document Type: Article

References (20)

1. Robert Zmud and Carol Brown are the accepting Senior Editors for this article. This report is based on research sponsored by the Advanced Practices Council of the Society for Information Management. We gratefully acknowledge their support.
2. Erl, T. SOA Principles of Service Design, Prentice Hall Service-Oriented Computing Series, July, 2007.
3. See also Smith, H. and McKeen, J. " Creating a Process-Centric Organization at FCC: SOA from the Top Down," MISQ Executive (7:2), 2008.
4. We thank Matt Levy (Research Assistant at LSU) for pointing out this example
5. This figure is adapted from the presentation used by George Brown, IT Research, Intel Corporation, to discuss the company's SOA strategy, Jan. 2007.
6. Dornan, A. " SOA: Convergence and Consolidation," InformationWeek Analytics Report, Sept. 2007
7. Foster, S. and Tuecke, I. " Describing the elephant: the different faces of IT as service," ACM Queue (3:6), 2005, pp. 26-29.
8. Arsanjani, A., Ghosh, S., Allam, A., Abdollah, T., Ganapathy, S., and Holley, K. " SOMA: A method for developing service-oriented solutions," IBM Systems Journal, (47:3), 2008, pp. 377-396.
9. Varadan, R., Channabasavaiah, K., Simpson, S., Holley, K., and Allam, A. " Increasing business flexibility and SOA adoption through effective SOA governance," IBM Systems Journal, (47:3), 2008, pp. 473-490.
10. We acknowledge that we are not the first to propose a model of SOA maturity. See, for example, Arsanjani, A. and Holley, K. " Increase Flexibility with the Service Integration Maturity Model (SIMM): Maturity, Adoption, and Transformation to SOA," IBM Developerworks, Sept. 30, 2005.
11. The SIMM approach suggests seven levels of maturity focused solely on the technical aspects of each stage. In contrast, our approach examines both the IT and business dimensions that correspond to each stage.
12. A sentiment shared by others, such as Krill, P. " Industry Report: SOA is Overly Hyped" , InfoWorld, Aug. 20, 2007
13. more recently, Linthicum, D. " Taming the SOA Hype Monster," InfoWorld, June 18, 2009.
14. For alternative views on the future of SOA, we refer our readers to Glaser, J. " Too Far Ahead of the IT Curve," Harvard Business Review, July-Aug., 2007
15. Smith, R. " State of SOA" , InformationWeek, Feb. 21, 2009.
16. See, for example, Krafzig, D., Banke, K., Slama, D. Enterprise SOA: Service-Oriented Architecture Best Practices, Prentice Hall, 2004
17. McKendrick, J. " Ten Companies Where SOA Made a Difference in 2006," http://blogs.zdnet.com/service-oriented/?p=781, Dec. 17, 2006.
18. We acknowledge that the labels of our stages are congruent with other models of maturity (e.g., SIMM).
19. See, for example, Khoshafian, S. Service-Oriented Enterprise, Auerbach, October, 2006
20. Krafzig, D., Banke, K., and Slama, D. Enterprise SOA: Service-Oriented Architecture Best Practices. Upper Saddle River, NJ: Pearson Education, Inc., 2005.