Bibliography

[AISJ77]

Christopher Alexander, Sara Ishikawa, Murray Silverstein, Max Jacobson, Ingrid Fiksdahl-King, and Shlomo Angel. A Pattern Language: Towns, Buildings, Construction. Oxford University Press, New York, NY, 1977.

[Ale64]

Christopher Alexander. Notes on the Synthesis of Form. Harvard University Press, Boston, MA, 1964.

[Amb04]

Scott Ambler. The Object Primer: Agile Model-Driven Development with UML 2.0. Cambridge University Press, Cambridge, United Kingdom, Third edition, 2004.

[App11]

Juregen Appelo. Management 3.0: Leading Agile Developers, Developing Agile Leaders. Addison-Wesley, Boston, MA, 2011.

[App16]

Juregen Appelo. Managing for Happiness: Games, Tools, and Practices to Motivate Any Team. John Wiley & Sons, New York, NY, 2016.

[BBCG10]

Felix Bachmann, Len Bass, Paul C. Clements, David Garlan, James Ivers, Reed Little, Paulo Merson, Robert Nord, and Judith A. Stafford. Documenting Software Architectures: Views and Beyond. Addison-Wesley, Boston, MA, Second edition, 2010.

[BC89]

Kent Beck and Ward Cunningham. A Laboratory for Teaching Object-Oriented Thinking. ACM SIGPLAN Notices. 24[10], 1989, October.

[BCK12]

Len Bass, Paul C. Clements, and Rick Kazman. Software Architecture in Practice. Addison-Wesley, Boston, MA, Third edition, 2012.

[BCR94]

Victor Basili, Gianluigi Caldiera, and H. Dieter Rombach. The Goal Question Metric (GQM) Approach. Encyclopedia of Software Engineering 1. 528--532, 1994.

[Bec00]

Kent Beck. Extreme Programming Explained: Embrace Change. Addison-Wesley Longman, Boston, MA, 2000.

[BELS03]

Mario R. Barbacci, Robert J. Ellison, Anthony J. Lattanze, Judith A. Stafford, Charles B. Weinstock, and William G. Wood. Quality Attribute Workshops (QAWs), Third edition. Software Engineering Institute Digital Library. 2003.

[Bra17]

Alberto Brandolini. Introducing Event Storming: An Act of Deliberate Collective Learning. LeanPub, https://leanpub.com, 2017.

[Bro16]

Simon Brown. Software Architecture for Developers. LeanPub, https://leanpub.com, 2016.

[Bro86]

Frederick Brooks. No Silver Bullet—Essence and Accident in Software Engineering. Proceedings of the IFIP Tenth World Computing Conference. 1986.

[Bro95]

Frederick P. Brooks Jr. The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley, Boston, MA, Anniversary, 1995.

[BT03]

Barry Boehm and Richard Turner. Using Risk to Balance Agile and Plan-Driven Methods. IEEE Computer. 36[6]:57--66, 2003, June.

[BWO10]

Barry Boehm, Greg Wilson (editor), and Adam Oram (editor). Architecting: How Much and When?. O’Reilly & Associates, Inc., Sebastopol, CA, 2010.

[BWZ15]

Len Bass, Ingo Weber, and Liming Zhu. DevOps: A Software Architect’s Perspective. Addison-Wesley, Boston, MA, 2015.

[Car09]

Dale Carnegie. How to Win Friends and Influence People. Simon & Schuster, New York, NY, Third edition, 2009.

[Coh09]

Mike Cohn. Succeeding with Agile: Software Development Using Scrum. Addison-Wesley, Boston, MA, 2009.

[Cor13]

Bett Correa. You Can Be a Software Architect. CreateSpace, an Amazon Company, Seattle, WA, 2013.

[Cor15]

Bett Correa. The Zen of Software Development: A Seven Day Journey: A Handbook to Enlightened Software Development. CreateSpace, an Amazon Company, Seattle, WA, 2015.

[Eva03]

Eric Evans. Domain-Driven Design: Tackling Complexity in the Heart of Software. Addison-Wesley Longman, Boston, MA, First, 2003.

[Fai10]

George Fairbanks. Just Enough Software Architecture: A Risk-Driven Approach. Marshall & Brainerd, Boulder, CO, 2010.

[FHR99]

Brian Foote, Niel Harrison, and Hans Rohnert. Pattern Languages of Program Design 4. Addison-Wesley, Boston, MA, 1999.

[Fow03]

Martin Fowler. Who Needs an Architect?. IEEE Software. 20[5]:11--13, 2003, September/October.

[GAO95]

David Garlan, Robert Allen, and John Ockerbloom. Architectural Mismatch: Why Reuse Is So Hard. IEEE Software. 12:17--26, 1995, November.

[GHJV95]

Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides. Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley, Boston, MA, 1995.

[Glu94]

David P. Gluch. A Construct for Describing Software Development Risks. Software Engineering Institute Digital Library. 1994, July.

[Goo09]

Kim Goodwin. Designing for the Digital Age: How to Create Human-Centered Products and Services. John Wiley & Sons, New York, NY, 2009.

[Hoh16]

Gregor Hohpe. 37 Things and Architect Knows: A Chief Architect’s Journey. LeanPub, https://leanpub.com, 2016.

[HW04]

Gregor Hohpe and Bobby Woolf. Enterprise Integration Patterns: Designing and Deploying Messaging Solutions. Addison-Wesley, Boston, MA, 2004.

[Int11]

International Organization for Standards (ISO). ISO/IEC/IEEE 42010:2011 Systems and software engineering -- Architecture description. IEEE. 2011, December.

[Kee15]

Michael Keeling. Architecture Haiku: A Case Study in Lean Documentation. IEEE Software. 32[3]:35-39, 2015, May/June.

[KKC00]

Rick Kazman, Mark H. Klein, and Paul C. Clements. ATAM: Method for Architecture Evaluation. Software Engineering Institute Digital Library. 2000.

[Kru95]

Phillippe Krutchen. Architectural Blueprints — The 4+1 View Model of Software Architecture. IEEE Software. 12[6]:42--50, 1995.

[Kua13]

Patrick Kua. The Retrospective Handbook: A Guide for Agile Teams. CreateSpace, an Amazon Company, Seattle, WA, 2013.

[Kua15]

Patrick Kua. Talking with Tech Leads: From Novices to Practitioners. CreateSpace, an Amazon Company, Seattle, WA, 2015.

[KV11]

Michael Keeling and Michail Velichansky. Making Metaphors That Matter. Proceedings of the 2011 Agile Conference. 256--262, 2011.

[MB02]

Ruth Malan and Dana Bredemeyer. Less is more with minimalist architecture. IT Professional. 4[5]:48, 46--47, 2002, September-October.

[Mey97]

Bertrand Meyer. Object-Oriented Software Construction. Prentice Hall, Englewood Cliffs, NJ, Second edition, 1997.

[Mug14]

Jonathan Mugan. The Curiosity Cycle: Preparing Your Child for the Ongoing Technological Explosion. Mugan Publishing, Buda, TX, Second edition, 2014.

[Pat14]

Jeff Patton. User Story Mapping: Discover the Whole Story, Build the Right Product. O’Reilly & Associates, Inc., Sebastopol, CA, 2014.

[PML10]

Hasso Plattner, Chrisoph Meinel, and Larry Leifer. Design Thinking: Understand - Improve - Apply (Understanding Innovation). Springer, New York, NY, 2010.

[PP03]

Mary Poppendieck and Tom Poppendieck. Lean Software Development: An Agile Toolkit for Software Development Managers. Addison-Wesley, Boston, MA, 2003.

[Ras10]

Jonathan Rasmusson. The Agile Samurai: How Agile Masters Deliver Great Software. The Pragmatic Bookshelf, Raleigh, NC, 2010.

[RW11]

Nick Rozanski and Eoin Woods. Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives. Addison-Wesley, Boston, MA, Second edition, 2011.

[Sim96]

Herbert Simon. The Sciences of the Artificial. MIT Press, Cambridge, MA, Third edition, 1996.

[TA05]

Jeff Tyree and Art Akerman. Architecture Decisions: Demystifying Architecture. IEEE Software. 22[2]:19--27, 2005, March/April.

[VAH12]

Uwe Van Heesch, Paris Avgerioum, and Rich Hilliard. A documentation framework for architecture decisions. Journal of Systems and Software. 85[4]:795–820, 2012, April, December.

[WFD16]

Jonathan Wilmot, Lorraine Fesq, and Dan Dvorak. Quality attributes for mission flight software: A reference for architects. IEEE Aerospace Conference. 5--12, 2016, March.

[WNA13]

Michael Waterman, James Noble, and George Allen. The effect of complexity and value on architecture planning in agile software development. Agile Processes in Software Engineering and Extreme Programming (XP2013). 2013, May.

[Zwe13]

Thomas D. Zweifel. Culture Clash 2: Managing the Global High Performance Team. SelectBooks, New York, NY, 2013.