Lean Architecture: for Agile Software Development
More and more Agile projects are seeking architectural roots as they struggle with complexity and scale - and they're seeking lightweight ways to do itStill seeking? In this book the authors help you to find your own pathTaking cues from Lean development, they can help steer your project toward practices with longstanding track recordsUp-front architecture? Sure. You can deliver an architecture as code that compiles and that concretely guides development without bogging it down in a mass of documents and guesses about the implementationDocumentation? Even a whiteboard diagram, or a CRC card, is documentation: the goal isn't to avoid documentation, but to document just the right things in just the right amountProcess? This all works within the frameworks of Scrum, XP, and other Agile approaches
What people are saying - Write a review
We haven't found any reviews in the usual places.
Lean and Agile
12 Lean Architecture and Agile Feature Development
13 Agile Production
14 The Book in a Very Small Nutshell
Contrasting and Complementary
16 Lost Practices
17 What this Book isNotAbout
18 Agile Lean Oh Yeah and Scrum and Methodologies and Such
63 Not Your Old Professors OO
64 How much Architecture?
71 What the SystemDoes
72 Who is Going to Use Our Software?
73 What do the Users Want to Use Our Software for?
74 Why Does the User Want to Use Our Software?
75 Consolidation of What the System Does
21 Engage the Stakeholders
22 Define the Problem
The Foundations of Form
The System Lifeblood
25 Design and Code
31 The Value Stream
32 The Key Stakeholders
33 Process Elements of Stakeholder Engagement
Trimming Wasted Time
35 No Quick Fixes but Some Hope
41 Whats Agile about Problem Definitions?
42 Whats Lean about Problem Definitions?
44 Problems and Solutions
45 The Process Around Problem Definitions
46 Problem Definitions Goals Charters Visions and Objectives
51 Some Surprises about Architecture
Selecting a Design Style
55 History and Such
The Rough Framing of the Code
62 Relationships in Architecture
When Use Cases are a Bad Fit
78 Usability Testing
710 History and Such
82 The Form and Architecture of Atomic Event Systems
Method Elaboration Factoring and Refactoring
86 History and Such
91 Sometimes Smart Objects Just Arent Enough
93 Overview of DCI
94 DCI by Example
95 Updating the Domain Logic
Solution to an AgeOld Problem
97 Why All These Artifacts?
DCI in Other Languages
F1 Testing Perspective
F3 Context Perspective
F5 Support Perspective Infrastructure Classes
abstract base classes Account Holder Agile Manifesto Agile software development algorithms Alistair Cockburn amount APIs architect artifacts balance bank behavior capture Chapter commonality and variation concepts Context object Conway’s Law Coplien and Harrison CRC cards create DCI architecture decisions deviations documentation domain classes domain experts domain knowledge domain objects end user mental end-user example feedback focus goal Grandpa Harry implementation injected interactions interface Lean architecture member functions methodful object roles methodless object role Model-View-Controller modules MoneySink MoneySource object orientation object-oriented programming organization paradigm partitioning pattern languages patterns perspective poka-yoke problem definition programming language Reenskaug relationships rework Ruby SavingsAccount Scrum Smalltalk software architecture software development source account stakeholders structure sunny day scenario techniques traits Transfer money TransferMoneyContext TransferMoneySource Trygve Reenskaug usability user mental model user stories user’s value stream what-the-system-does