Lean Architecture: for Agile Software Development

Front Cover
John Wiley & Sons, Jan 6, 2011 - Computers - 376 pages
10 Reviews
More and more Agile projects are seeking architectural roots as they struggle with complexity and scale - and they're seeking lightweight ways to do it
  • Still seeking? In this book the authors help you to find your own path
  • Taking cues from Lean development, they can help steer your project toward practices with longstanding track records
  • Up-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 implementation
  • Documentation? 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 amount
  • Process? This all works within the frameworks of Scrum, XP, and other Agile approaches
  

What people are saying - Write a review

User ratings

5 stars
0
4 stars
3
3 stars
4
2 stars
2
1 star
1

Review: Lean Architecture: For Agile Software Development

User Review  - Mikko Kärkkäinen - Goodreads

My review seems to be aligned with that of the majority of the readers of this book... My initial feeling was great because the topic of agile architecture has been a pretty hot one at work recently ... Read full review

Review: Lean Architecture: For Agile Software Development

User Review  - Timoteo Ponce - Goodreads

It took a long time to read, but not because it is not intuitive enough. It's just too much meat in this meal to eat at once. Is a very good reading about all topics from culture to technology in ... Read full review

Related books

Contents

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?
65 Documentation?
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
Partitioning
Selecting a Design Style
54 Documentation?
55 History and Such
The Rough Framing of the Code
62 Relationships in Architecture
76 Recap
When Use Cases are a Bad Fit
78 Usability Testing
710 History and Such
ModelViewControllerUser
82 The Form and Architecture of Atomic Event Systems
Method Elaboration Factoring and Refactoring
84 Documentation?
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
99 Documentation?
F1 Testing Perspective
F3 Context Perspective
F5 Support Perspective Infrastructure Classes
Copyright

Common terms and phrases

About the author (2011)

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.

Bibliographic information