Enterprise architecture's identity crisis: New approaches to complexity for a maturing discipline

A Systemic Perspective to Managing Complexity with Enterprise Architecture

Volumn , Issue , 2013, Pages 433-453

  Taylor, Paul R ^a  

^a MONASH UNIVERSITY   (Australia)

Author keywords

[No Author keywords available]

Indexed keywords

E-GOVERNMENTS; ECONOMIC SITUATION; ENTERPRISE ARCHITECTURE; NEW APPROACHES; NEW ENTERPRISE; ORGANIZATIONAL BEHAVIOR; SYSTEMS THINKING; TRADITIONAL APPROACHES;

EID: 84956812361     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.4018/978-1-4666-4518-9.ch013     Document Type: Chapter

References (50)

1. AGIMO. (2007). Australian government architecture: Principles. Australian Government Information Management Office. AGIMO.
2. AGIMO. (2011). Australian government architecture: Reference models. Australian Government Information Management Office. AGIMO.
3. Alexander, C. (1988). A city is not a tree. London: Thames and Hudson.
4. Ariely, D. (2008). Predictably irrational: The hidden forces that shape our decisions. New York: HarperCollins.
5. Australian Public Service Commission. (2007). Changing behaviour: A public policy perspective. Retrieved from http://www.apsc.gov.au/__data/assets/pdf_file/0017/6821/changingbehaviour.pdf
6. Boehm, B. W. (1976. Software engineering. IEEE Transactions on Computers, 25(12), 1226-1241. doi:10.1109/TC.1976.1674590.
7. Brown, T. (2008. Design thinking. Harvard Business Review. PMID:18605031.
8. Brown, T. (2009). Tim Brown urges designers to think big. Retrieved from http://www.ted.com/talks/tim_brown_urges_designers_to_think_big.html
9. Checkland, P. (1981). Systems thinking, systems practice. Chichester, UK: Wiley.
10. Chew, E. K., & Gottschalk, P. (2009). Information technology strategy and management: Best practices. Hershey, PA: IGI Global. doi:10.4018/978-1-59904-802-4.
11. Demos. (2012). Public services and welfare. Retrieved 23 August, 2012, from http://www.demos.co.uk/publicservicesandwelfare
12. Eaves, D. (1992). The prospects of a formal discipline of software engineering. Monash University.
13. Floyd, C. (1992). Software development as reality construction. In Floyd, C., Budde, R., Zullighoven, H., & Keil-Slawik, R. (Eds.), Software Development and Reality Construction. Berlin: Springer-Verlag. doi:10.1007/978-3-642-76817-0_10.
14. Frampton, K. Barrow, et al. (2005). A study of the in-practice application of a commercial software architecture. In Proceedings of the Australian Software Engineering Conference (ASWEC 2005). Brisbane, Australia: IEEE Computer Society.
15. Gartner. (2009). Gartner identifies ten enterprise architecture pitfalls. Retrieved 13 August, 2012, from http://www.gartner.com/it/page.jsp?id=1159617
16. Hagan, P. J. (2004). Guide to the (evolving) enterprise architecture body of knowledge. The MITRE Corporation.
17. Hammer, M., & Champy. (1993). Reengineering the corporation: A manifesto for business revolution. New York: Harper.
18. Heylighen, F., & Cilliers, et al. (2007). Complexity and philosophy. In Bogg, J, & Geyer, R (Eds.), Complexity, Science and Society. Oxford, UK: Radcliffe Publishing.
19. Howe, J. (2009). Crowdsourcing: Why the power of the crowd is driving the future of business. New York: Three Rivers Press.
20. Jones, J. C. (1988). Softecnica. In Thackara, J. (Ed.), Design after modernism. London: Thames and Hudson.
21. Kaplan, S. M. (2000). Co-evolution in sociotechnical systems. In Proceedings of Computer Supported Cooperative Work (CSCW 2000). Philadelphia: ACM Press.
22. Karpen, I. O., & Bove, et al. (2012. Linking service-dominant logic and strategic business practice: A conceptual model of a service-dominant orientation. Journal of Service Research, 15(21).
23. Laurel, B. (1993). Computers as theatre. Reading, MA: Addison-Wesley.
24. Lawson, B. (1997). How designers think. Oxford, UK: Architectural Press.
25. Levitt, S., & Dubner. (2005). Freakonomics: A rogue economist explores the hidden side of everything. New York: William Morrow.
26. Lockwood, T., & Walton. (2008). Building design strategy: Using design to achieve key business objectives. New York: Allworth Press.
27. Lockwood, T. (2009). Design thinking: Integrating innovation, customer experience, and brand value. Allworth Press.
28. Mahidhar, V. (2011. Ecosystems for innovation: An interview with U.S. CTO Aneesh Chopra. Deloitte Review, 11. Retrieved 14 August, 2011, from http://www.deloitte.com/assets/Dcom-Australia/Local%20Assets/Documents/Industries/Government%20Services/Public%20Sector/Deloitte_review_issue_nine_2011.pdf
29. Mandl, K. D., & Mandel, et al. (2012. The SMART platform: Early experience enabling substitutable applications for electronic health records. Journal of American Medical Informatics, 19(4).
30. Martin, R. L. (2007). The opposable mind: How successful leaders win through integrative thinking. Boston: Harvard Business School Publishing.
31. McBreen, P. (2002). Software craftsmanship: The new imperative. Boston: Addison-Wesley.
32. McIlroy, M. D. (1968). Mass produced software components. In Proceedings of the First NATO Conference on Software Engineering. Garmisch, Germany: IEEE.
33. Morowitz, H. (2002). The emergence of everything: How The world became complex. Oxford, UK: Oxford University Press.
34. NBBJ. (2012). NBBJ architecture and design. Retrieved 7 May, 2012, from http://www.nbbj.com
35. Nussbaum, B. (2012). Design thinking is a failed experiment: So what's next? Co.DESIGN. Retrieved 24 August, 2012, from http://www.fastcodesign.com/1663558/design-thinking-isa-failed-experiment-so-whats-next
36. Object Management Group. (2013). Business architecture working group. Retrieved 18 March, 2013, from http://bawg.omg.org/
37. Orlov, L. M., & Cameron. (2007). Business technology defined: Technology management is changing to deliver business results. Forrester Research.
38. Parker, S., & Bartlett. (2008). Towards agile government. State Services Authority, Government of Victoria.
39. Ross, J. W., & Weill, et al. (2006). Enterprise architecture as strategy: Creating a foundation for business execution. Boston, MA: Harvard Business School Press.
40. Sanders, E., & Westerlund. (2011). Experiencing, exploring and experimenting in and with co-design spaces. Paper presented at the Nordic Design Research Conference. Helsinki, Finland.
41. Senge, P. M. (1992). The fifth discipline: The art and science of the learning organization. Sydney, Australia: Random House.
42. Shirky, C. (2012). Clay Shirky's internet writings. Retrieved 14 August, 2012, from http://shirky.com/
43. Spewak, S. H. (1992). Enterprise architecture planning: Developing a blueprint for data, application and technology. QED Publishing Group.
44. Taylor, F. W. (1911). The principles of scientific management. New York: Harper and Row.
45. TOGAF. (2012). The open group architecture framework (TOGAF). Retrieved 27 July 2012, 2012, from http://www.opengroup.org/togaf/
46. UK Cabinet Office. (2010). Behavioural insights team. Retrieved 9 June 2012, from http://www.cabinetoffice.gov.uk/behavioural-insights-team
47. Vargo, S. L., & Lusch, . (2004. Evolving to a new dominant logic for marketing. Journal of Marketing, 68(1), 1-17. doi:10.1509/jmkg.68.1.1.24036.
48. Vargo, S. L., & Lusch, . (2008. From goods to service(s): Divergences and convergences of logics. Industrial Marketing Management, 37(3), 254-259. doi:10.1016/j.indmarman.2007.07.004.
49. Wooldridge, M., & Lovell. (2011). Human services: The case for change. Retrieved 7 August, 2012, from http://www.dhs.vic.gov.au/about-thedepartment/news-and-events/news/general-news/human-services-the-case-for-change
50. Zachman, J. A. (1987. A framework for information systems architecture. IBM Systems Journal, 26(3), 276-292. doi:10.1147/sj.263.0276.