Lean Architecture: for Agile Software Development
and over one million other books are available for Amazon Kindle .
Learn more
| |||||||||||||||
 Trade In this Item for up to £4.35
Get an extra £5 when you trade in books worth £10 or more until June 30, 2012. Trade in Lean Architecture: for Agile Software Development for an Amazon.co.uk gift card of up to £4.35, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Frequently Bought Together
Product details
|
More About the Author
Product Description
Review
′...a book of advice that is broad, enabling, and concrete.’ (Lean Magazine, January 2010).
Product Description
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
Inside This Book
(Learn More)
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
Most Helpful Customer Reviews
7 of 8 people found the following review helpful
Format:Paperback
The good:
- Focusses on value streams.
- Practical requirements examples.
The bad:
- Very dry read, very academic in nature with no practical example of the whole theoretical approach working.
- Strikes me as very waterfall in approach.
- DCI struck me as just a simple implementation of the Strategy Pattern with the Decorator Pattern, so the end was a bit of a let down. This would have been fine but the DCI architecture was built up as a major evolution in development.
- The above point reinforced the view that architects are largely out of touch with the practices and technology used by developers, I left feeling that a good business analyst and a good development technical lead would have produced something akin to the output of the book without needing a traditional architect.
To summarise, some good practical examples presented in isolation but doesn't tie it all together and is slightly out of touch with development practices used today.
- Focusses on value streams.
- Practical requirements examples.
The bad:
- Very dry read, very academic in nature with no practical example of the whole theoretical approach working.
- Strikes me as very waterfall in approach.
- DCI struck me as just a simple implementation of the Strategy Pattern with the Decorator Pattern, so the end was a bit of a let down. This would have been fine but the DCI architecture was built up as a major evolution in development.
- The above point reinforced the view that architects are largely out of touch with the practices and technology used by developers, I left feeling that a good business analyst and a good development technical lead would have produced something akin to the output of the book without needing a traditional architect.
To summarise, some good practical examples presented in isolation but doesn't tie it all together and is slightly out of touch with development practices used today.
7 of 8 people found the following review helpful
Format:Paperback
This is a different book. Where most books expound a single theme such as Agile, Lean, or Scrum, "Lean Architecture for Agile Software Development" paints on a much broader canvas: Working with the end user, end user's mental model, user requirements, system architecture, and right down to actual code.
This is neither a beginner's "how to do it in ten easy lessons" nor is it a design method. It is a book written for the mature professional by two authors whose long experience has given them a deep understanding of what really matters in practical programming.
At a first glance, many methodologies appear as mere fads, but Coplien and Bjørnvig see through the fads and build on their real worth to create a thought-provoking and eminently practical book.
Three random jottings from my first reading:
* Architecture: "No matter how we care to define it, software architecture should support the enterprise value stream even to the extent that the source code itself should reflect the end user's mental model of the world."
* Lean secret: "...unite specialists together in one room: everybody, all together, from early on."
* Form and functionality: "System architecture should reflect the end user's mental model of the world. The model has two parts: The first part relates to the user's thought process when viewing the screen, and to what the system is: its form. The second part relates to what end users do - interacting with the system - and how the system should respond to user input. This is the system functionality. We work with users to elicit and develop these models and to capture them in code as early as possible."
The authors claims that an end user should have a picture in his head that enables him to see the commands that are meaningful in a given situation and to understand what it will do for him. This picture, Jim calls it the end user's mental model, it will be reflected into the actual code in well-built systems.
A few years ago, this reviewer introduced a new programming paradigm that he called Data, Context, and Interaction (DCI). The main feature of this paradigm is that it splits the code into two distinct parts. One part specifies system state; the other part specifies system behavior. Coplien and Bjørnvig use this paradigm to fill in the gap between architecture and code execution. To quote from the book:
* Key building blocks of object-oriented design: "Objects, which are end users' conceptualization of things in their business world; Classes, which provide simple, encapsulated access to the data that represents business information; Roles, which interact in a use case to achieve some business goal."
This book is a MUST read for all who want to understand the true nature of systems development.
This is neither a beginner's "how to do it in ten easy lessons" nor is it a design method. It is a book written for the mature professional by two authors whose long experience has given them a deep understanding of what really matters in practical programming.
At a first glance, many methodologies appear as mere fads, but Coplien and Bjørnvig see through the fads and build on their real worth to create a thought-provoking and eminently practical book.
Three random jottings from my first reading:
* Architecture: "No matter how we care to define it, software architecture should support the enterprise value stream even to the extent that the source code itself should reflect the end user's mental model of the world."
* Lean secret: "...unite specialists together in one room: everybody, all together, from early on."
* Form and functionality: "System architecture should reflect the end user's mental model of the world. The model has two parts: The first part relates to the user's thought process when viewing the screen, and to what the system is: its form. The second part relates to what end users do - interacting with the system - and how the system should respond to user input. This is the system functionality. We work with users to elicit and develop these models and to capture them in code as early as possible."
The authors claims that an end user should have a picture in his head that enables him to see the commands that are meaningful in a given situation and to understand what it will do for him. This picture, Jim calls it the end user's mental model, it will be reflected into the actual code in well-built systems.
A few years ago, this reviewer introduced a new programming paradigm that he called Data, Context, and Interaction (DCI). The main feature of this paradigm is that it splits the code into two distinct parts. One part specifies system state; the other part specifies system behavior. Coplien and Bjørnvig use this paradigm to fill in the gap between architecture and code execution. To quote from the book:
* Key building blocks of object-oriented design: "Objects, which are end users' conceptualization of things in their business world; Classes, which provide simple, encapsulated access to the data that represents business information; Roles, which interact in a use case to achieve some business goal."
This book is a MUST read for all who want to understand the true nature of systems development.
1 of 1 people found the following review helpful
Format:Paperback
I found this an excellent, widely scoped book on lean thinking applied to software systems. I did find it a somewhat unusual book, the beginning is a bit hard to pin down and, in my opinion, the DCI section felt a little out of place. However don't let this deter you, the body of the book is fantastic and it brings together many ideas. It certainly changed the way I think about architecture.
Would you like to see more reviews about this item?
Were these reviews helpful?
Let us know
Most Recent Customer Reviews
Misleading title
This is not an Architecture book - its about OO Design but with a huge amount of waffle added in. The problem is, the waffle makes sweeping assumptions, doesn't explain itself, and... Read more
Published 5 months ago by aa0099aekdfjhfhedkkja
Advanced software architecture
Agile movement for good or bad is getting more academic traction. This book is such in a good sense: plenty of in-depth analysis and though-provoking insights on the convergence of... Read more
Published 8 months ago by Igor Lobanov
Far too academic in style for me
I honestly found this book to be almost unreadable. It took me back to wading through control-theory books at university where every sentence had to be read three times and... Read more
Published 9 months ago by mchid
An excellent title from the father of agile organizational patterns
This book brings the world of the architecture right in the context of agile.
If you are using Lean, Scrum, XP or any of the other agile approaches in any of the roles... Read more
If you are using Lean, Scrum, XP or any of the other agile approaches in any of the roles... Read more
Published 12 months ago by Bojan Jovicic
Superb to read
The author makes learning lean and agile processes so easy with a good conversational tone that just drags you along
Published 13 months ago by F. Alhassan
Use cases in code
This first book covering the new DCI paradigm of programming is a must read for anyone interested in separating the more often changing behavioral parts of code related to use... Read more
Published 19 months ago by Marc Grue
Conserving value
Most IT projects I've been envolved in starts with an idea, an idea of how to create more value for the once to come end users. Read more
Published 22 months ago by maya gilham moerch
New Masterpiece on Lean and Agile Architecture
This superb book is about a new vision of the object-oriented world.
Based on the DCI (Data, Context and Interaction) architecture paradigm and renewed Lean principles, the... Read more
Based on the DCI (Data, Context and Interaction) architecture paradigm and renewed Lean principles, the... Read more
Published 22 months ago by Lena Nikolaev
Listmania!
|
|
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
