References

1. Allega P. Defining EA: Low Barriers to Entry (My Mother Has an EA Definition, too). Gartner.com, a Weblog by Philip Allega. Retrieved December 17, 2011, from http://blogs.gartner.com/philip-allega/2010/08/11/defining-ea-low-barriers-to-entry-my-mother-has-an-ea-definition-too/; 2010.

2. Ambler S. Agile Best Practice: Model a Bit Ahead Agile Modeling (AM) homepage: Effective Practices for Modeling and Documentation. Retrieved April 15, 2011, from www.agilemodeling.com/essays/modelAhead.htm; 2006.

3. Anderson C. The long tail: why the future of business is selling less of more. New York: Hyperion; 2006.

4. Anderson DJ. Kanban: successful evolutionary change for your technology business. Sequim, Washington: Blue Hole Press; 2010.

5. Bak P. How nature works: the science of self-organized criticality. New York: Copernicus; 1996.

6. Beck K, Beedle M, Cockburn A, et al. Manifesto for Agile Software Development. Retrieved April 6, 2011, from http://agilemanifesto.org/; 2001.

7. Bemer R. Machine-controlled production environment. In: Brussels: NATO Science Committee; 1968;94–95.

8. Bente S, Karla J. Enterprise Social Network Platforms as a Management Tool in Complex Technical Systems. In: 2009; San Francisco, California.

9. Berners-Lee T. DeveloperWorks Interviews: Tim Berners-Lee. IBM developerWorks 2006; Retrieved March 4, 2011, from www.ibm.com/developerworks/podcast/dwi/cm-int082206.txt; 2006.

10. Booch G. On design Software architecture, software engineering, and Renaissance Jazz. Retrieved November 15, 2011, from https://www.ibm.com/developerworks/mydeveloperworks/blogs/gradybooch/entry/on_design?lang=en; 2006.

11. Brisco B, Odlyzko A, Tilly B. Matcalfe’s Law Is Wrong. IEEE Spectrum 2006; Retrieved February 16, 2012, from http://spectrum.ieee.org/computing/networks/metcalfes-law-is-wrong/1; 2006.

12. Breivold HP, Sundmark D, Wallin P, Larsson S. What Does Research Say About Agile and Architecture?. Proceedings of the Fifth International Conference on Software Engineering Advances. 2010;1(1):32–37 Retrieved August 21, 2011, from www.computer.org/portal/web/csdl/doi/10.1109/ICSEA.2010.12; 2010.

13. Broad WJ. A Missile Defense With Limits. New York Times 2000:A10 Retrieved February 13, 2012, from www.nytimes.com/2000/06/30/world/nuclear-shield-repelling-attack-missile-defense-with-limits-abc-s-clinton-plan.html?pagewanted=5; 2000.

14. Brown SL, Eisenhardt KM. Competing on the edge strategy as structured chaos. Boston, Mass: Harvard Business School Press; 1998.

15. Burt R. Structural Holes: The Social Structure of Competition. Cambridge, Massachusetts: Harvard University Press; 1995.

16. Burton B. Best and worst enterprise architecture practices: Delivering value. Gartner Webinars 2010; Retrieved February 20, 2011, from http://my.gartner.com/portal/server.pt?open=512&objID=202&mode=2&PageID=5553&ref=webinar-rss&resId=1525314; 2010.

17. Broadbent M, Kitzis E. The new CIO leader: setting the agenda and delivering results. Boston: Harvard Business School Press; 2005.

18. Broadbent M, Weill P. Management by Maxims: How Business and IT Managers Can Create IT Infrastructures. Sloan Management. 1997;38(3):77–92.

19. Buckl S, et al. A Lightweight Approach to Enterprise Architecture Modeling and Documentation. In: Soffer P, Proper E, eds. 2010:136–149. Information Systems Evolution, CAiSE Forum 2010, Hammamet, Springer, Lecture Notes in Business Information Processing (LNBIP). 72.

20. Cabinet Office. ITIL Service Operation. London: TSO Publisher; 2007.

21. Carroll P. Big blues: the unmaking of IBM. New York: Crown Publishers; 1993.

22. Coates T. An addendum to a definition of Social Software. Plasticbag.org, a Weblog by Tom Coates. Retrieved March 21, 2011, from www.plasticbag.org/archives/2; 2005.

23. Cockburn A. Agile software development: the cooperative game. second ed. Upper Saddle River, NJ: Addison-Wesley; 2007.

24. Cohn M. Succeeding with agile: Software development using Scrum. Upper Saddle River, NJ: Addison-Wesley; 2009.

25. Coplien J, Bjørnvig G. Lean architecture for Agile software development. Hoboken, N.J: Wiley; 2010.

26. Daft RL. The executive and the elephant: a leader’s guide for building inner excellence. San Francisco, CA: Jossey-Bass; 2010.

27. Dörnenburg E. Making ESB pain visible. Erik Dörnenburg Articles. Retrieved March 7, 2011, from http://erik.doernenburg.com/2009/07/making-esb-pain-visible/; 2009.

28. Eckerson W. 2011; Personal communication with the authors.

29. Ford H, Crowther S. My life and work. Garden City, N.Y: Doubleday, Page & Co; 1922.

30. Fowler M. Using an Agile Software Process with Offshore Development. Martin Fowler 2006; Retrieved April 15, 2011, from http://martinfowler.com/articles/agileOffshore.html; 2006.

31. GAO. Information technology: the federal enterprise architecture and agencies’ enterprise architectures are still maturing. U.S. Government Accountability Office (U.S. GAO) 2004; Retrieved July 27, 2011, from www.gao.gov/products/GAO-04-798T; 2004.

32. Goethe JW. Maximen und Reflexionen. Leipzig: Dieterich’schen; 1953.

33. Gharajedaghi J. Systems Thinking, Managing Chaos and Complexity: A Platform for Designing Business Architecture. third ed. Burlington, MA: Morgan Kaufmann; 2011.

34. Granovetter MS. The Strength of Weak Ties. Am J Sociol. 1973;78(6):1360–1380.

35. Haidt J. The happiness hypothesis: finding modern truth in ancient wisdom. New York: Basic Books; 2006.

36. Hanschke I. Strategic IT management: a toolkit for enterprise architecture management. Heidelberg: Springer; 2010.

37. Henry S, Kafura D. Software Structure Metrics Based on Information Flow. IEEE Transactions on Software Engineering. September 1981;SE-7 1981.

38. Hines P, Rich N. The seven value stream-mapping tools. International Journal of Physical Distribution & Logistics Management. 1997;17(1):46–64.

39. IEEE Computer Society. IEEE Recommended Practice for Architecture Description of Software-Intensive Systems. IEEE Std New York: IEEE; 2000; pp. 1472–2000.

40. ISACA. The Risk IT Framework. ISACA Association 2009; Retrieved February 12, 2012, from www.isaca.org/Knowledge-Center/Risk-IT-IT-Risk-Management/Pages/Risk-IT1.aspx; 2009.

41. ISACA. COBIT 4.1: Framework, Control Objectives, Management Guidelines, Maturity Models. 2007; Retrieved February 12, 2012, from www.isaca.org/Knowledge-Center/cobit/Documents/CobiT_4.1.pdf; 2007.

42. Johnston A. Role of the Agile Architect. 2010; Welcome to the Agile Architect Website. Retrieved April 16, 2011, from www.agilearchitect.org/agile/role.htm; 2010.

43. Jones JA. An Introduction to Factor Analysis of Information Risk (FAIR). Risk Management Insight 2005; Retrieved February 13, 2012, from www.riskmanagementinsight.com/media/docs/FAIR_introduction.pdf; 2005.

44. Kauffman SA. The origins of order: self-organization and selection in evolution. London: Oxford University Press; 1993.

45. Kauffman SA. At home in the universe: the search for laws of self-organization and complexity. New York: Oxford University Press; 1995.

46. Keller W. IT-Unternehmensarchitektur Von der Geschäftsstrategie zur optimalen IT-Unterstützung. Heidelberg: dpunkt.verlag; 2007.

47. Kniberg H. One day in Kanban land. Crisp’s Blog. Retrieved February 7, 2012, from http://blog.crisp.se/2009/06/26/henrikkniberg/1246053060000; 2009.

48. Koch M. Enterprise 2.0 Planung, Einführung und erfolgreicher Einsatz von Social-Software in Unternehmen. (2., aktualisierte und erw. Aufl. ed.) München: Oldenbourg; 2009.

49. Kotter JP, Cohen DS. The heart of change: real-life stories of how people change their organizations. Boston, Mass: Harvard Business School Press; 2002.

50. Krafcik J. Triumph of the Lean Production System. Sloan Manage Rev. 1988;30(1):41–52.

51. Krafzig D, Banke K, Slama D. Enterprise SOA: service-oriented architecture best practices. (6 print. ed.) Upper Saddle River, NJ: Prentice-Hall; 2006.

52. Krebs J. Agile portfolio management. Redmond, Wash: Microsoft; 2009.

53. Kruchten P. Architectural Blueprints: The “4+1” ViewModel of Software Architecture. IEEE Software. 1995;12(6):42–50.

54. Kruchten P. The Tao of the Software Architect. Enterprise Architecture, Software Architecture, Architects, and Architecting 2004; Retrieved April 16, 2011, from www.bredemeyer.com/tao_by_Kruchten.htm; 2004.

55. Kruchten P. The Elephants in the Agile Room. Philippe Kruchten 2011; Retrieved April 6, 2011, from http://pkruchten.wordpress.com/2011/02/13/the-elephants-in-the-agile-room/; 2011.

56. Kruchten P. What do software architects really do?. The Journal of Systems and Software. 2008;81:2413–2416.

57. Lankhorst M. Enterprise architecture at work: modelling, communication and analysis. second ed. Berlin: Springer; 2009.

58. Larman C, Basili VR. Iterative and Incremental Development: A Brief History. IEEE Computer. 2003;36(6):47–56.

59. Larman C, Vodde B. Scaling lean & agile development: thinking and organizational tools for large-scale Scrum. Upper Saddle River, NJ: Addison-Wesley; 2009.

60. Leffingwell D, Widrig D. Managing software requirements: a use case approach. second ed. Boston: Addison-Wesley; 2003.

61. Leffingwell D. Scaling software agility: best practices for large enterprises. Upper Saddle River, NJ: Addison-Wesley; 2007.

62. Leffingwell D. Agile software requirements: lean requirements practices for teams, programs, and the enterprise. Upper Saddle River, NJ: Addison-Wesley; 2011.

63. Liker JK. The Toyota way: 14 management principles from the world’s greatest manufacturer. New York: McGraw-Hill; 2004.

64. Linowski B. Schlanke Modellgetriebene Entwicklung in Agilen Projekten. Java Magazin. 2011;1:1.

65. Lucas C. Self-Organization and Human Robots. International Journal of Advanced Robotic Systems. 2005;2 Retrieved September 28, 2011, from www.ars-journal.com/ars/Free_Articles/Chris_Lucas.htm; 2005.

66. Mack R. Real IT Strategies: Steps 1 to 4—Laying a Foundation. Gartner Group 2003a; Report R-21-4950.

67. Mack R. Real IT Strategies: Steps 5 to 8—Creating the Strategy. Gartner Group 2003b; Report R-21-4074.

68. Mack R, Frey N. Six Building Blocks for Creating Real IT Strategies. Gartner Group 2002; Report R 17-3607.

69. Manes AT. SOA is Dead; Long Live Services. Application Platform Strategies Blog. Retrieved January 23, 2012, from http://apsblog.burtongroup.com/2009/01/soa-is-dead-long-live-services.html; 2009.

70. Mar A, Spacey J. Enterprise Architecture Anti Patterns. 2011; Simplicable.com; 2011; Retrieved July 27, 2011, from http://simplicable.com/new/enterprise-architecture-anti-patterns; 2011.

71. March J, Simon H. Organizations. New York: John Wiley; 1958.

72. McAfee A. Enterprise 2.0: The Dawn of Emergent Collaboration. MIT Sloan Review. 2006a;47(3):21.

73. McAfee A. Enterprise 2.0, version 2.0 Andrew McAfee’s Blog—The Business Impact of IT. Retrieved April 8, 2011, from http://andrewmcafee.org/2006/05/enterprise_20_version_20/; 2006b.

74. McAfee A. Enterprise 2.0: new collaborative tools for your organization’s toughest challenges. Boston, Mass: Harvard Business Press; 2009.

75. McManus H. A Framework for Lean Engineering. Boston: MIT Lean Aerospace Initiative Product Development Focus Team; 1999.

76. McManus H. Product Development Value Stream Mapping (PDVSM) Manual 1.0. Boston: The Lean Aerospace Initiative; 2005.

77. McConnell S. Software estimation: demystifying the black art. Redmond, Wash: Microsoft Press; 2006.

78. Merriam-Webster, (n.d.). Dictionary and Thesaurus: Merriam-Webster Online. Retrieved June 29, 2011, from www.merriam-webster.com/.

79. Millard RL. Value Stream Analysis and Mapping for Product Development. Boston: Department of Aeronautics and Astronautics, Massachusetts Institute of Technology; 2001.

80. Monson-Haefel R. 97 things every software architect should know: collective wisdom from the experts. Sebastopol, Calif: O’Reilly Media; 2009.

81. Nonaka I, Takeuchi H. The knowledge-creating company: how Japanese companies create the dynamics of innovation. New York: Oxford University Press; 1995.

82. O’Reilly T. What Is Web 2.0?. O’Reilly Media 2005; Retrieved March 6, 2011, from http://oreilly.com/pub/a/web2/archive/what-is-web-20.html?page=1; 2005.

83. OECD. OECD Principles of Corporate Governance. Directorate for Financial, Fiscal and Enterprise Affairs 1999; SG/CG(99) 5 and 219, April 1999.

84. Ohno T. Toyota production system: beyond large-scale production. Cambridge, Mass: Productivity Press; 1988.

85. OMB. Improving Agency Performance Using Information and Information Technology (Enterprise Architecture Assessment Framework v3.1). Office of Management and Budget 2009; Retrieved December 17, 2011, from www.whitehouse.gov/sites/default/files/omb/assets/fea_docs/OMB_EA_Assessment_Framework_v3_1_June_2009.pdf; 2009.

86. Osono E, Shimizu N, Takeuchi H. Extreme Toyota: radical contradictions that drive success at the world’s best manufacturer. Hoboken, N.J: John Wiley & Sons; 2008.

87. Poppendieck M, Poppendieck TD. Lean software development: an agile toolkit. Boston: Addison-Wesley; 2003.

88. Poppendieck M, Poppendieck TD. Implementing lean software development: from concept to cash. Upper Saddle River, NJ: Addison-Wesley; 2007.

89. Porter ME. Competitive strategy: techniques for analyzing industries and competitors: with a new introduction. New York City: Free Press; 1998.

90. Reinertsen DG. Managing the design factory: a product developer’s toolkit. New York: Free Press; 1997.

91. Ross J. Forget Strategy: Focus IT on Your Operating Model. MIT CISR Research Briefing. 2005;V.

92. Ross J. Maturity Matters: How Firms Generate Value from Enterprise Architecture. MIT CISR Research Briefing. 2006;IV.

93. Ross J, Woerner S, Scantlebury S, Beath C. The IT Organization of the Future: Driving Business Change. Spring 2010 IT Advantage The Boston Consulting Group 2010; Retrieved December 17, 2011, from www.bcg.com/documents/file40521.pdf; 2010.

94. Ross L. The intuitive psychologist and his shortcomings: distortions in the attribution process. Advances in Experimental Social Psychology. 1977;10:173–220.

95. Rother M, Shook J. Learning to see: value stream mapping to create value and eliminate muda. (Version 1.3 ed.) Brookline, MA: Lean Enterprise Institute; 2003.

96. Rule G. Lean enterprise architecture: how to achieve better business performance from soft systems. SMS Exemplar White Papers. Retrieved March 8, 2011, from www.smsexemplar.com/wp-content/uploads/15PGRLeanEntArchitecture_v1g1.pdf; 2010.

97. Saha P. Six reasons why EA should not be assigned to the IT department. LinkedIn, The Enterprise Architecture Network 2011; Retrieved August 18, 2011, from www.linkedin.com/groups/Six-Reasons-Why-EA-Should-36781.S.52757710?view=&srchtype=discussedNews&gid=36781&item=52757710&type=member&trk=eml-anet_dig-b_pd-ttl-cn; 2011.

98. Schekkerman J. Enterprise architecture good practices guide: how to manage the enterprise architecture practice. Victoria, BC: Trafford; 2008.

99. Schekkermann J. Enterprise Architecture Tool Selection Guide. Institute for Enterprise Architecture Development, Jaap Schekkermann 2011; Retrieved December 9, 2011, from www.enterprise-architecture.info/Images/EA%20Tools/Enterprise%20Architecture%20Tool%20Selection%20Guide%20v6.3.pdf; 2011.

100. Schmidt JG, Lyle D. Lean integration: an integration factory approach to business agility. Boston, Mass: Addison-Wesley; 2010.

101. Schwarzer B. Einführung in das Enterprise Architecture Management: Verstehen, Planen, Umsetzen. Norderstedt: Books on Demand; 2009.

102. Sessions R. A Comparison of the Top Four Enterprise-Architecture Methodologies. Microsoft Development Network (MSDN) 2007; Retrieved December 17, 2011, from http://msdn.microsoft.com/en-us/library/bb466232.aspx; 2007.

103. Shah S. Resume-Driven Development (RDD). Shahid’s Perspectives. Retrieved December 30, 2011, from http://shahid.shah.org/?p=15; 2004.

104. Shalloway A, Beaver G, Trott J. Lean-agile software development: achieving enterprise agility. Upper Saddle River, N.J: Addison-Wesley; 2010.

105. Shazer S, Dolan YM, Korman H. More than miracles: the state of the art of solution-focused brief therapy. New York: Haworth Press; 2007.

106. Shore J, Warden S. The art of agile development. Beijing: O’Reilly Media, Inc; 2008.

107. Slogans That Work. Forbes.com. Retrieved January 27, 2012, from www.forbes.com/forbes/2008/0107/099.html; 2007.

108. Spacey, J., (n.d.). Survey: Success of EA Programs. Simplicable.com. Retrieved November 12, 2011, from http://simplicable.com/survey1/enterprise-architecture-success-survey.html.

109. Stakutis C, Webster J. Inescapable data: harnessing the power of convergence. Upper Saddle River, NJ: IBM Press; 2005.

110. Surowiecki J. The wisdom of crowds. New York: Anchor Books; 2005.

111. The Open Group. Risk Taxonomy Technical Standard. 2009b.

112. The Open Group. The Open Group ArchiMate(R) 1.0 Technical Standard. The Open Group 2008; Retrieved January 4, 2012, from www.opengroup.org/archimate/doc/ts_archimate/; 2008.

113. The Open Group. TOGAF™ Version 9. Zaltbommel, Netherlands: Van Haren Publishing; 2009.

114. The Open Group. TOGAF™ Version 9.1. Document Number: G116, ISBN: 9789087536794. Retrieved December 16, 2011, from http://pubs.opengroup.org/architecture/togaf9-doc/arch/; 2011.

115. Urdhwareshe H. Six Sigma for business excellence approach, tools and applications. New Delhi: Dorling Kindersley (India); 2011.

116. US Department of Commerce. Enterprise Architecture Capability Maturity Model Version: 1.2. Office of the Chief Information Office, US Department of Commerce 2007; Retrieved December 16, 2011, from http://ocio.os.doc.gov/ITPolicyandPrograms/Enterprise_Architecture/PROD01_004935; 2007.

117. Ward JM, Peppard J. Strategic planning for information systems. third ed. Chichester etc: J. Wiley; 2003.

118. Wikipedia. Strategy (Game Theory). 2011; Retrieved September 10, 2011, from http://en.wikipedia.org/wiki/Strategy_%28game_theory%29; 2011.

119. Weill P, Ross J. IT Governance: How Top Performers Manage IT Decision Rights for Superior Results. Boston, MA: Harvard Business School Press; 2004.

120. Winter R. Ein Modell zur Visualisierung der Anwendungslandschaft als Grundlage der Informationssystem-Architekturplanung. In: Schelp J, Winter R, eds. Integrationsmanagement: Planung, Bewertung und Steuerung von Applikationslandschaften. Berlin: Springer; 2006:1–30.

121. Womack JP, Jones DT, Roos D. The machine that changed the world: based on the Massachusetts Institute of Technology 5-million dollar, 5-year study on the future of the automobile. New York: Rawson Associates; 1990.

122. Womack JP, Jones DT. Lean thinking: banish waste and create wealth in your corporation. New York, NY: Simon & Schuster; 1996.

123. Womack JP, Jones DT. Lean solutions: how companies and customers can create value and wealth together. London: Simon & Schuster; 2005.

124. Valen LV. A New Evolutionary Law. Evolutionary Theory. 1973;1:1–30.

125. Yegge S. Stevey’s Google Platforms Rant. Plus.google.com: an internal memo on Google + that mistakenly leaked into the public domain. Retrieved January 9, 2012, from https://plus.google.com/112678702228711889851/posts/eVeouesvaVX; 2011.

126. Zachman J. A Framework for Information Systems Architecture. IBM Systems Journal. 1987;26.

127. Zachman J. John Zachman’s Concise Definition of The Zachman Framework™. Zachman International, Inc 2008; Retrieved December 17, 2011, from www.zachman.com/about-the-zachman-framework; 2008.