Lean Architecture (PDF)

About the Authors. Preface. 1 Introduction. 1.1 The Touchstones: Lean and Agile. 1.2 Lean Architecture and Agile Feature Development. 1.3 Agile Production. 1.4 The Book in a Very Small Nutshell. 1.5 Lean and Agile: Contrasting and Complementary. 1.6 Lost Practices. 1.7 What this Book is Not About. 1.8 Agile, Lean ? Oh, Yeah, and Scrum and Methodologies and Such. 1.9 History and Such. 2 Agile Production in a Nutshell. 2.1 Engage the Stakeholders. 2.2 Define the Problem. 2.3 Focusing on What the System Is: The Foundations of Form. 2.4 Focusing on What the System Does: The System Lifeblood. 2.5 Design and Code. 2.6 Countdown: 3, 2, 1. . . . 3 Stakeholder Engagement. 3.1 The Value Stream. 3.2 The Key Stakeholders. 3.3 Process Elements of Stakeholder Engagement. 3.4 The Network of Stakeholders: Trimming Wasted Time. 3.5 No Quick Fixes, but Some Hope. 4 Problem Definition. 4.1 What's Agile about Problem Definitions? 4.2 What's Lean about Problem Definitions? 4.3 Good and Bad Problem Definitions. 4.4 Problems and Solutions. 4.5 The Process Around Problem Definitions. 4.6 Problem Definitions, Goals, Charters, Visions, and Objectives. 4.7 Documentation? 5 What the System Is, Part 1: Lean Architecture. 5.1 Some Surprises about Architecture. 5.2 The First Design Step: Partitioning. 5.3 The Second Design Step: Selecting a Design Style. 5.4 Documentation? 5.5 History and Such. 6 What the System Is, Part 2: Coding It Up. 6.1 The Third Step: The Rough Framing of the Code. 6.2 Relationships in Architecture. 6.3 Not Your Old Professor's OO. 6.4 How much Architecture? 6.5 Documentation? 6.6 History and Such. 7 What the System Does: System Functionality. 7.1 What the System Does. 7.2 Who is Going to Use Our Software? 7.3 What do the Users Want to Use Our Software for? 7.4 Why Does the User Want to Use Our Software? 7.5 Consolidation of What the System Does. 7.6 Recap. 7.7 "It Depends": When Use Cases are a Bad Fit. 7.8 Usability Testing. 7.9 Documentation? 7.10 History and Such. 8

James O. Coplien is a writer, lecturer, and researcher in
the field of Computer Science. He has made key contributions in the
areas of software design and organizational development, software
debugging, and in empirical research. His early work on C++ idioms
was one of the three primary sources of the popular Design
Patterns. His work on Organizational patterns was an inspiration
for both Extreme Programming and for Scrum. Cope was a founding
Member of Hillside Group with Kent Beck, Grady Booch, Ward
Cunningham, Ralph Johnson, Ken Auer and Hal Hildebrand. He is
responsible for starting up several of the conferences in the
Pattern Languages of Programming (PLoP) conference series and is a
longstanding pattern author and PLoP shepherd.

Gertrud Bjornvig is an experienced software consultant
and trainer and has been in software development since 1984. She's
been working on development teams as a developer, analyst, and
project manager, and has had cross-organizational roles as
methodologist and process consultant. Her background is in
object-oriented development, including extensive work with UML and
RUP. Gertrud has been employed by Enator, Navision, Microsoft, and
TietoEnator, but since June 2007 she has been independent as a part
of Gertrud & Cope.

Gertrud holds a Master in Computer Science and Communication and is
one of the founders of Danish Agile User Group.

Dieses eBook können Sie uneingeschränkt auf allen Geräten der tolino Familie lesen. Zum Lesen auf sonstigen eReadern und am PC benötigen Sie eine Adobe ID.