Collaborative Enterprise Architecture

Collaborative Enterprise Architecture

Volumn , Issue , 2012, Pages

  Bente, Stefan ^a   Bombosch, Uwe ^a   Langade, Shailendra ^b  

^a TATA CONSULTANCY SERVICES   (India)

^b Tata Consultancy ^*  (Germany)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 85014238318     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1016/C2011-0-69682-6     Document Type: Book

References (127)

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/.
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. http://www.agilemodeling.com/essays/modelAhead.htm.
3. Anderson C. The long tail: why the future of business is selling less of more 2006, Hyperion, New York.
4. Anderson D.J. Kanban: successful evolutionary change for your technology business 2010, Blue Hole Press, Sequim, Washington.
5. Bak P. How nature works: the science of self-organized criticality 1996, Copernicus, New York.
6. Beck K., Beedle M., Cockburn A., Cunningham W., Fowler M., Grenning J., et al. Manifesto for Agile Software Development Retrieved April 6, 2011, from. http://agilemanifesto.org/.
7. Bemer R. Machine-controlled production environment 1968, 94-95. NATO Science Committee, Brussels.
8. Bente S., Karla J. Enterprise Social Network Platforms as a Management Tool in Complex Technical Systems 2009, San Francisco, California.
9. Berners-Lee T. DeveloperWorks Interviews: Tim Berners-Lee 2006, IBM developerWorks, Retrieved March 4, 2011, from. http://www.ibm.com/developerworks/podcast/dwi/cm-int082206.txt.
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.
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.
12. Breivold H.P., 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. http://www.computer.org/portal/web/csdl/doi/10.1109/ICSEA.2010.12.
13. Broad W.J. A Missile Defense With Limits. New York Times 2000, June 30, A10. Retrieved February 13, 2012, from. http://www.nytimes.com/2000/06/30/world/nuclear-shield-repelling-attack-missile-defense-with-limits-abc-s-clinton-plan.html?pagewanted=5.
14. Brown S.L., Eisenhardt K.M. Competing on the edge strategy as structured chaos 1998, Harvard Business School Press, Boston, Mass.
15. Burt R. Structural Holes: The Social Structure of Competition 1995, Harvard University Press, Cambridge, Massachusetts.
16. Burton B. Best and worst enterprise architecture practices: Delivering value 2010, Gartner Webinars, 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.
17. Broadbent M., Kitzis E. The new CIO leader: setting the agenda and delivering results 2005, Harvard Business School Press, Boston.
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. Information Systems Evolution, CAiSE Forum 2010, Hammamet, Springer, Lecture Notes in Business Information Processing (LNBIP) 2010, 72:136-149. P. Soffer, E. Proper (Eds.).
20. Cabinet Office ITIL Service Operation 2007, TSO Publisher, London.
21. Carroll P. Big blues: the unmaking of IBM 1993, Crown Publishers, New York.
22. Coates T. An addendum to a definition of Social Software Plasticbag.org, a Weblog by Tom Coates. Retrieved March 21, 2011, from. http://www.plasticbag.org/archives/2.
23. Cockburn A. Agile software development: the cooperative game 2007, Addison-Wesley, Upper Saddle River, NJ. second ed.
24. Cohn M. Succeeding with agile: Software development using Scrum 2009, Addison-Wesley, Upper Saddle River, NJ.
25. Coplien J., Bjørnvig G. Lean architecture for Agile software development 2010, Wiley, Hoboken, N.J.
26. Daft R.L. The executive and the elephant: a leader's guide for building inner excellence 2010, Jossey-Bass, San Francisco, CA.
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/.
28. Eckerson W. 2011, Personal communication with the authors.
29. Ford H., Crowther S. My life and work 1922, Doubleday, Page & Co, Garden City, N.Y.
30. Fowler M. Using an Agile Software Process with Offshore Development 2006, July 18, Martin Fowler, Retrieved April 15, 2011, from. http://martinfowler.com/articles/agileOffshore.html.
31. GAO Information technology: the federal enterprise architecture and agencies' enterprise architectures are still maturing 2004, May 19, U.S. Government Accountability Office (U.S. GAO), Retrieved July 27, 2011, from. http://www.gao.gov/products/GAO-04-798T.
32. Goethe J.W. Maximen und Reflexionen 1953, Dieterich'schen, Leipzig.
33. Gharajedaghi J. Systems Thinking, Managing Chaos and Complexity: A Platform for Designing Business Architecture 2011, Morgan Kaufmann, Burlington, MA. third ed.
34. Granovetter M.S. 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 2006, Basic Books, New York.
36. Hanschke I. Strategic IT management: a toolkit for enterprise architecture management 2010, Springer, Heidelberg.
37. Henry S., Kafura D. Software Structure Metrics Based on Information Flow. IEEE Transactions on Software Engineering September 1981, SE-7(5). 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 2000, IEEE, New York, pp. 1472-2000.
40. ISACA The Risk IT Framework 2009, ISACA Association, Retrieved February 12, 2012, from. http://www.isaca.org/Knowledge-Center/Risk-IT-IT-Risk-Management/Pages/Risk-IT1.aspx.
41. ISACA COBIT 4.1: Framework, Control Objectives, Management Guidelines, Maturity Models 2007, Retrieved February 12, 2012, from. http://www.isaca.org/Knowledge-Center/cobit/Documents/CobiT_4.1.pdf.
42. Johnston A. Role of the Agile Architect 2010, Welcome to the Agile Architect Website. Retrieved April 16, 2011, from. http://www.agilearchitect.org/agile/role.htm.
43. Jones J.A. An Introduction to Factor Analysis of Information Risk (FAIR) 2005, Risk Management Insight, Retrieved February 13, 2012, from. http://www.riskmanagementinsight.com/media/docs/FAIR_introduction.pdf.
44. Kauffman S.A. The origins of order: self-organization and selection in evolution 1993, Oxford University Press, London.
45. Kauffman S.A. At home in the universe: the search for laws of self-organization and complexity 1995, Oxford University Press, New York.
46. Keller W. IT-Unternehmensarchitektur. Von der Geschäftsstrategie zur optimalen IT-Unterstützung 2007, dpunkt.verlag, Heidelberg.
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.
48. Koch M. Enterprise 2.0 Planung, Einführung und erfolgreicher Einsatz von Social-Software in Unternehmen 2009, (2., aktualisierte und erw. Aufl. ed.), Oldenbourg, München.
49. Kotter J.P., Cohen D.S. The heart of change: real-life stories of how people change their organizations 2002, Harvard Business School Press, Boston, Mass.
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 2006, (6 print. ed.), Prentice-Hall, Upper Saddle River, NJ.
52. Krebs J. Agile portfolio management 2009, Microsoft, Redmond, Wash.
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, February 5, Retrieved April 16, 2011, from. http://www.bredemeyer.com/tao_by_Kruchten.htm.
55. Kruchten P. The Elephants in the Agile Room 2011, February 11, Philippe Kruchten, Retrieved April 6, 2011, from. http://pkruchten.wordpress.com/2011/02/13/the-elephants-in-the-agile-room/.
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 2009, Springer, Berlin. second ed.
58. Larman C., Basili V.R. 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 2009, Addison-Wesley, Upper Saddle River, NJ.
60. Leffingwell D., Widrig D. Managing software requirements: a use case approach 2003, Addison-Wesley, Boston. second ed.
61. Leffingwell D. Scaling software agility: best practices for large enterprises 2007, Addison-Wesley, Upper Saddle River, NJ.
62. Leffingwell D. Agile software requirements: lean requirements practices for teams, programs, and the enterprise 2011, Addison-Wesley, Upper Saddle River, NJ.
63. Liker J.K. The Toyota way: 14 management principles from the world's greatest manufacturer 2004, McGraw-Hill, New York.
64. Linowski B. Schlanke Modellgetriebene Entwicklung in Agilen Projekten. Java Magazin 2011, June, 1:1.
65. Lucas C. Self-Organization and Human Robots. International Journal of Advanced Robotic Systems 2005, 2(1). Retrieved September 28, 2011, from. http://www.ars-journal.com/ars/Free_Articles/Chris_Lucas.htm.
66. Mack R. Real IT Strategies: Steps 1 to 4-Laying a Foundation 2003, Gartner Group, Report R-21-4950.
67. Mack R. Real IT Strategies: Steps 5 to 8-Creating the Strategy 2003, Gartner Group, Report R-21-4074.
68. Mack R., Frey N. Six Building Blocks for Creating Real IT Strategies 2002, Gartner Group, Report R 17-3607.
69. Manes A.T. 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.
70. Mar A., Spacey J. Enterprise Architecture Anti Patterns 2011, January 7, Retrieved July 27, 2011, from. http://simplicable.com/new/enterprise-architecture-anti-patterns.
71. March J., Simon H. Organizations 1958, John Wiley, New York.
72. McAfee A. Enterprise 2.0: The Dawn of Emergent Collaboration. MIT Sloan Review 2006, 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/.
74. McAfee A. Enterprise 2.0: new collaborative tools for your organization's toughest challenges 2009, Harvard Business Press, Boston, Mass.
75. McManus H. A Framework for Lean Engineering 1999, MIT Lean Aerospace Initiative Product Development Focus Team, Boston.
76. McManus H. Product Development Value Stream Mapping (PDVSM) Manual 1.0 2005, The Lean Aerospace Initiative, Boston.
77. McConnell S. Software estimation: demystifying the black art 2006, Microsoft Press, Redmond, Wash.
78. Merriam-Webster, (n.d.). Dictionary and Thesaurus: Merriam-Webster Online. Retrieved June 29, 2011, from . http://www.merriam-webster.com/.
79. Millard R.L. Value Stream Analysis and Mapping for Product Development 2001, Department of Aeronautics and Astronautics, Massachusetts Institute of Technology, Boston.
80. Monson-Haefel R. 97 things every software architect should know: collective wisdom from the experts 2009, O'Reilly Media, Sebastopol, Calif.
81. Nonaka I., Takeuchi H. The knowledge-creating company: how Japanese companies create the dynamics of innovation 1995, Oxford University Press, New York.
82. O'Reilly T. What Is Web 2.0? 2005, O'Reilly Media, Retrieved March 6, 2011, from. http://oreilly.com/pub/a/web2/archive/what-is-web-20.html?page=1.
83. OECD OECD Principles of Corporate Governance 1999, Directorate for Financial, Fiscal and Enterprise Affairs, SG/CG(99) 5 and 219, April 1999.
84. Ohno T. Toyota production system: beyond large-scale production 1988, Productivity Press, Cambridge, Mass.
85. OMB Improving Agency Performance Using Information and Information Technology (Enterprise Architecture Assessment Framework v3.1) 2009, Office of Management and Budget, Retrieved December 17, 2011, from. http://www.whitehouse.gov/sites/default/files/omb/assets/fea_docs/OMB_EA_Assessment_Framework_v3_1_June_2009.pdf.
86. Osono E., Shimizu N., Takeuchi H. Extreme Toyota: radical contradictions that drive success at the world's best manufacturer 2008, John Wiley & Sons, Hoboken, N.J.
87. Poppendieck M., Poppendieck T.D. Lean software development: an agile toolkit 2003, Addison-Wesley, Boston.
88. Poppendieck M., Poppendieck T.D. Implementing lean software development: from concept to cash 2007, Addison-Wesley, Upper Saddle River, NJ.
89. Porter M.E. Competitive strategy: techniques for analyzing industries and competitors: with a new introduction 1998, Free Press, New York City.
90. Reinertsen D.G. Managing the design factory: a product developer's toolkit 1997, Free Press, New York.
91. Ross J. Forget Strategy: Focus IT on Your Operating Model. MIT CISR Research Briefing 2005, V(3 C).
92. Ross J. Maturity Matters: How Firms Generate Value from Enterprise Architecture. MIT CISR Research Briefing 2006, IV(2 B).
93. Ross J., Woerner S., Scantlebury S., Beath C. The IT Organization of the Future: Driving Business Change. IT Advantage 2010, Spring 2010, The Boston Consulting Group, Retrieved December 17, 2011, from. http://www.bcg.com/documents/file40521.pdf.
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 2003, (Version 1.3 ed.), Lean Enterprise Institute, Brookline, MA.
96. Rule G. Lean enterprise architecture: how to achieve better business performance from soft systems SMS Exemplar White Papers. Retrieved March 8, 2011, from. http://www.smsexemplar.com/wp-content/uploads/15PGRLeanEntArchitecture_v1g1.pdf.
97. Saha P. Six reasons why EA should not be assigned to the IT department 2011, May 18, LinkedIn, The Enterprise Architecture Network, Retrieved August 18, 2011, from. http://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.
98. Schekkerman J. Enterprise architecture good practices guide: how to manage the enterprise architecture practice 2008, Trafford, Victoria, BC.
99. Schekkermann J. Enterprise Architecture Tool Selection Guide 2011, Institute for Enterprise Architecture Development, Jaap Schekkermann, Retrieved December 9, 2011, from. http://www.enterprise-architecture.info/Images/EA%20Tools/Enterprise%20Architecture%20Tool%20Selection%20Guide%20v6.3.pdf.
100. Schmidt J.G., Lyle D. Lean integration: an integration factory approach to business agility 2010, Addison-Wesley, Boston, Mass.
101. Schwarzer B. Einführung in das Enterprise Architecture Management: Verstehen, Planen, Umsetzen 2009, Books on Demand, Norderstedt.
102. Sessions R. A Comparison of the Top Four Enterprise-Architecture Methodologies 2007, Microsoft Development Network (MSDN), Retrieved December 17, 2011, from. http://msdn.microsoft.com/en-us/library/bb466232.aspx.
103. Shah S. Resume-Driven Development (RDD) Shahid's Perspectives. Retrieved December 30, 2011, from. http://shahid.shah.org/?p=15.
104. Shalloway A., Beaver G., Trott J. Lean-agile software development: achieving enterprise agility 2010, Addison-Wesley, Upper Saddle River, N.J.
105. Shazer S., Dolan Y.M., Korman H. More than miracles: the state of the art of solution-focused brief therapy 2007, Haworth Press, New York.
106. Shore J., Warden S. The art of agile development 2008, O'Reilly Media, Inc, Beijing.
107. Slogans That Work Forbes.com. Retrieved January 27, 2012, from. http://www.forbes.com/forbes/2008/0107/099.html.
108. Spacey, J., (n.d.). Survey: Success of EA Programs. 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 2005, IBM Press, Upper Saddle River, NJ.
110. Surowiecki J. The wisdom of crowds 2005, Anchor Books, New York.
111. The Open Group Risk Taxonomy Technical Standard 2009.
112. The Open Group The Open Group ArchiMate(R) 1.0 Technical Standard 2008, The Open Group, Retrieved January 4, 2012, from. http://www.opengroup.org/archimate/doc/ts_archimate/.
113. The Open Group TOGAF™ Version 9 2009, Van Haren Publishing, Zaltbommel, Netherlands.
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/.
115. Urdhwareshe H. Six Sigma for business excellence approach, tools and applications 2011, Dorling Kindersley (India), New Delhi.
116. US Department of Commerce Enterprise Architecture Capability Maturity Model Version: 1.2 2007, Office of the Chief Information Office, US Department of Commerce, Retrieved December 16, 2011, from. http://ocio.os.doc.gov/ITPolicyandPrograms/Enterprise_Architecture/PROD01_004935.
117. Ward J.M., Peppard J. Strategic planning for information systems 2003, J. Wiley, Chichester etc. third ed.
118. Wikipedia Strategy (Game Theory) 2011, Retrieved September 10, 2011, from. http://en.wikipedia.org/wiki/Strategy_%28game_theory%29.
119. Weill P., Ross J. IT Governance: How Top Performers Manage IT Decision Rights for Superior Results 2004, Harvard Business School Press, Boston, MA.
120. Winter R. Ein Modell zur Visualisierung der Anwendungslandschaft als Grundlage der Informationssystem-Architekturplanung. Integrationsmanagement: Planung, Bewertung und Steuerung von Applikationslandschaften 2006, 1-30. Springer, Berlin. J. Schelp, R. Winter (Eds.).
121. Womack J.P., Jones D.T., 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 1990, Rawson Associates, New York.
122. Womack J.P., Jones D.T. Lean thinking: banish waste and create wealth in your corporation 1996, Simon & Schuster, New York, NY.
123. Womack J.P., Jones D.T. Lean solutions: how companies and customers can create value and wealth together 2005, Simon & Schuster, London.
124. Valen L.V. 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.
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™ 2008, Zachman International, Inc, Retrieved December 17, 2011, from. http://www.zachman.com/about-the-zachman-framework.