- Taschenbuch: 378 Seiten
- Verlag: Wiley; Auflage: 1 (13. Juli 2010)
- Sprache: Englisch
- ISBN-10: 0470684208
- ISBN-13: 978-0470684207
- Größe und/oder Gewicht: 18,8 x 1,8 x 23,4 cm
- Durchschnittliche Kundenbewertung: 2 Kundenrezensionen
- Amazon Bestseller-Rang: Nr. 197.922 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
- Komplettes Inhaltsverzeichnis ansehen
Lean Architecture: for Agile Software Development (Englisch) Taschenbuch – 13. Juli 2010
|Neu ab||Gebraucht ab|
Kunden, die diesen Artikel gekauft haben, kauften auch
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
'...a book of advice that is broad, enabling, and concrete.' (Lean Magazine, January 2010).
It's time for change - after 30 years, DCI has risen to complete the vision of object-oriented programming!
Aiming at no less than a paradigm shift, Lean Architecture uses a modern approach to software design, while embracing refreshing new insights of Lean and Agile. Giving a down-to-earth view of Agile requirements and the often-ignored relationship between requirements and architecture, this book goes beyond the fashionable idea of User Stories, and shows you how to employ Use Cases in a lightweight, incremental, Agile way. The authors detail the DCI (Data, Context and Interaction) architecture paradigm and show how DCI succeeds where object-oriented programming languages alone have failed to integrate software design with the end user's understanding of the overall business structure.
However, this is not a methodology book, but a book which focuses on code, with plenty of code examples. Topics covered include: Agile production, Stakeholder Engagement, Organizational issues, Scala/Python/Java implementation of the DCI account example, Qi4J and much more.
Renowned software architecture expert James Coplien and agile requirements expert Gertrud Bjørnvig share their expertise to give you concrete design advice that will help you:
* Create software that builds on your end-user mental models rather than design methodologies
* Write software that can directly be verified against behavioral requirements
* Organize - so that all your stakeholders support each other
* Support rapidly changing feature code in stable domain code to help embrace change
Lean Architecture casts a new light over important aspects of software development that have been marginalized or forgotten by the agile movement - it will help you find your own path.
Derzeit tritt ein Problem beim Filtern der Rezensionen auf. Bitte versuchen Sie es später noch einmal.
This expert on Lean has sprinkled His book with "deep and meaningful" quotes, placed prominently at the beginnings of important sections, that neither convey much meaning nor support his chain of reasoning. I call that Waste, not Lean. In fact, when asked about the actual meaning of His cherished quotes, the author explodes and shouts that His book is not even making any argument! Hence, questioning its contents value is "not conducive to learning". Well. Today's authoritarians like to hide behind new-age social responsibility waffle, and this Author is no exception.
Avoid this book. Sounds interesting when you read it casually, but deeper questioning will leave you vacuous. According to the Author Himself, He is not trying to make any particular argument for anything, so this book belongs to the realm of fiction or, rather, Waste. The various "thoughts" presented may be helpful... or maybe not.
But hey, everything definitely sounds good and leaves you with that warm, fuzzy feeling that lifts you above the concerns of mere reason, just like my last Zen retreat!
A great practical description of how the use case evolves and translates directly into code, of how to reflect the end users mental model in code - making it much more readable for both programmers and domain experts. It goes into detail about how use case roles translates to Object Roles playing out their part of a use case algorithm and how they get injected into the domain objects to use their state. And we are presented with how the Context can set up the mapping of Roles to domain Objects in different flexible ways before firing off the trigger Interaction of the use case.
Apart from example code in C++ and Ruby through out the last chapters of the book, it also have a great appendix with coded DCI examples in Scala, Python, C#, Ruby and Squeak.
For anyone interested I can also recommend visiting the Google "object-composition" group where all the concepts are discussed and explored.
Die hilfreichsten Kundenrezensionen auf Amazon.com
This book is a great read if you are an experienced developer. I do not recommend it to people new to the software development industry.
Do not pick this book up and think you are going to learn how to do software architecture. Personally I would have named the book "Thoughts on Lean". I found the book very interesting and found it to contain a lot of great advice, but it does not paint the complete picture of how to accomplish solid software architecture.
I like the DCI coverage, but would only use it if it can be documented better than what is shown in the book. Code is not enough documentation for me.
Personally I will apply the techniques in this book to modular level design and development. Over the years I have found that to be the place agile and lean development practices belong, not at the architecture level. Their programming techniques help to achieve a very modifiable architecture, which to me is the most import quality attribute you should strive for on any project of decent size.
Although my review comes off as a bit negative, the negativity is not a reflection of the quality of this book's wisdom. It is my personal bias against what the agile movement has done to the environments I am constantly finding myself cleaning up. Agile is perceived all to often as the easy road, when in fact it is a road only for the highly experienced and a select few.
All in all I recommend reading this book if you want to broaden your horizon. The personal insight the author provides into building software is worth the time.