Lean Architecture: for Agile Software Development (英語) ペーパーバック – 2010/7/13
Kindle 端末は必要ありません。無料 Kindle アプリのいずれかをダウンロードすると、スマートフォン、タブレットPCで Kindle 本をお読みいただけます。
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
′...a book of advice that is broad, enabling, and concrete. (Lean Magazine, January 2010).商品の説明をすべて表示する
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.