|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
“o˜^î•ñ
|
‚±‚̤•i‚Ƀ^ƒO‚ð‚‚¯‚é(Ú×)ƒ^ƒO‚ÍA¤•i‚Æ‚ÌŠÖ˜A«‚ª”ñí‚É‹‚¢ƒL[ƒ[ƒh‚Ü‚½‚̓‰ƒxƒ‹‚̂悤‚È‚à‚Ì‚Å‚·B
ƒ^ƒO‚É‚æ‚èA‚·‚ׂĂ̂¨‹q—l‚ª‚¨‹C‚É“ü‚è‚̤•i‚Ì®—‚ÆŠm”F‚ðs‚¤‚±‚Æ‚ª‚Å‚«‚Ü‚·B ¦ƒ^ƒO‚͉ŠúÝ’è‚ÅŒöŠJ‚É‚È‚Á‚Ä‚¢‚Ü‚·BÚ‚µ‚‚Í‚±‚¿‚ç |
ƒJƒXƒ^ƒ}[ƒŒƒrƒ…[
Amazon.com ‚ÅÅ‚àŽQl‚É‚È‚Á‚½ƒJƒXƒ^ƒ}[ƒŒƒrƒ…[ (beta)
Amazon.com:
14Œ‚̃JƒXƒ^ƒ}[ƒŒƒrƒ…[
15 l’†A14l‚Ì•û‚ªA¢‚±‚̃Œƒrƒ…[‚ªŽQl‚É‚È‚Á‚½£‚Æ“Š•[‚µ‚Ä‚¢‚Ü‚·B
Highly recommended for novice and master
2010/10/18
Œ`Ž®:ƒn[ƒhƒJƒo[
This a broad and deep book on all things software architecture except the architecting process (for process, one recommended read is "Process Software Architecting" by Eeles/Cripps). Several readerships will benefit from "Just Enough Software Architecture":
- As an experienced IT architect, I do not necessarily agree with everything in the book (this does not come as a surprise, as architects have opinions). That said, I certainly learned a lot that I can apply immediately on my projects and some of the more provocative statements challenge me to leave my comfort zone (or at least consider doing so).
- Junior architects can use the book both as a tutorial and as a reference when/while growing in their profession.
- Developers with a "who needs architects" mindset (hopefully) will understand architects and modelers much better after having read this book, and appreciate the value of archtecture.
Things I liked in particular:
- Overall vision and message of pragmatism sent
- The risk-driven approach increases chances to get accepted both in agile development and in more traditional architecture communities
- There is a lot of practical advice e.g. in Chapters 10, 11 and 15
- The author is in command of a large body of relevant related work (both industra and academia) and puts them in perspective adequately
- Editorial quality: structure, figures, command of the English language (some words and expressions a bit be hard to comprehend for non-native speaker)
Some room for improvements (2nd edition?):
- Not all metaphors and analogies work internationally, e.g. not all IT people are sports fans that follow baseball or know what a rookie is
- The connection between parts 1 and 2 could be a bit stronger, even if loose coupling generally is a good thing; e.g., some more backward references
In summary, I'd say Just Enough Software Architecture is a highly recommended read for every architect in touch with development reality and every developer with a desire to build complex systems that will stand the test of time.
- As an experienced IT architect, I do not necessarily agree with everything in the book (this does not come as a surprise, as architects have opinions). That said, I certainly learned a lot that I can apply immediately on my projects and some of the more provocative statements challenge me to leave my comfort zone (or at least consider doing so).
- Junior architects can use the book both as a tutorial and as a reference when/while growing in their profession.
- Developers with a "who needs architects" mindset (hopefully) will understand architects and modelers much better after having read this book, and appreciate the value of archtecture.
Things I liked in particular:
- Overall vision and message of pragmatism sent
- The risk-driven approach increases chances to get accepted both in agile development and in more traditional architecture communities
- There is a lot of practical advice e.g. in Chapters 10, 11 and 15
- The author is in command of a large body of relevant related work (both industra and academia) and puts them in perspective adequately
- Editorial quality: structure, figures, command of the English language (some words and expressions a bit be hard to comprehend for non-native speaker)
Some room for improvements (2nd edition?):
- Not all metaphors and analogies work internationally, e.g. not all IT people are sports fans that follow baseball or know what a rookie is
- The connection between parts 1 and 2 could be a bit stronger, even if loose coupling generally is a good thing; e.g., some more backward references
In summary, I'd say Just Enough Software Architecture is a highly recommended read for every architect in touch with development reality and every developer with a desire to build complex systems that will stand the test of time.
9 l’†A8l‚Ì•û‚ªA¢‚±‚̃Œƒrƒ…[‚ªŽQl‚É‚È‚Á‚½£‚Æ“Š•[‚µ‚Ä‚¢‚Ü‚·B
Architecture as a risk reduction agent
2010/11/1
Œ`Ž®:ƒn[ƒhƒJƒo[
George Fairbanks book on "Just Enough Software Architecture" signals a directional shift away from architecture as a separate entity and movement toward viewing software architecture as holistic component of normal software development. Dr. Fairbanks outlines this shift by developing a thesis that software architecture is primarily a risk reduction agent and he contends that stakeholders should look for architectural views that highlight the risky parts of a software intensive system and understand how the architectural design reduces that risk.
To develop that thesis "Just Enough Software Architecture" covers architectural modeling, classification, styles and uses. Most of the chapters reinforce the risk reduction thesis either through examples or models where these principles are clarified. Dr. Fairbanks also uses a slight variation of the standard UML 2.0 notation, simplifying that notation in an attempt to show how even straightforward models can highlight the mechanics of the architecture.
One concept that "Just Enough Software Architecture" introduces is the concept of "architecture focused design", which is a deliberately chosen architecture to achieve a collection of acknowledged goals. The author espouses the concept that these goals are driven by the constraints of the system. These constraints should act as "guide rails" and they ultimately can be used to influence and direct the system or systems being developed. Many systems have hidden constraints (for example performance or security) and this architectural approach can help influence system implementers in making architecturally aligned development decisions.
Overall, I enjoyed George Fairbank's book and believe it forms an interesting discussion starting point for any organization performing software architectural work. I would hope that a companion volume is added that does a set of more detailed case studies of how actual risk-based architecture fares in practice.
To develop that thesis "Just Enough Software Architecture" covers architectural modeling, classification, styles and uses. Most of the chapters reinforce the risk reduction thesis either through examples or models where these principles are clarified. Dr. Fairbanks also uses a slight variation of the standard UML 2.0 notation, simplifying that notation in an attempt to show how even straightforward models can highlight the mechanics of the architecture.
One concept that "Just Enough Software Architecture" introduces is the concept of "architecture focused design", which is a deliberately chosen architecture to achieve a collection of acknowledged goals. The author espouses the concept that these goals are driven by the constraints of the system. These constraints should act as "guide rails" and they ultimately can be used to influence and direct the system or systems being developed. Many systems have hidden constraints (for example performance or security) and this architectural approach can help influence system implementers in making architecturally aligned development decisions.
Overall, I enjoyed George Fairbank's book and believe it forms an interesting discussion starting point for any organization performing software architectural work. I would hope that a companion volume is added that does a set of more detailed case studies of how actual risk-based architecture fares in practice.
7 l’†A5l‚Ì•û‚ªA¢‚±‚̃Œƒrƒ…[‚ªŽQl‚É‚È‚Á‚½£‚Æ“Š•[‚µ‚Ä‚¢‚Ü‚·B
Fantastic book about software architectures
2010/9/18
Œ`Ž®:ƒn[ƒhƒJƒo[
This is a fantastic book about software architectures. The concepts described in this book can be directly applied to software projects, enabling developers to access their designs in a principled way that can lead to the right architectural solutions. The concepts presented here are easy to be understood and applied in practice in our day to day projects.
‚±‚ê‚ç‚̃Œƒrƒ…[‚ÍŽQl‚É‚È‚è‚Ü‚µ‚½‚©H
‚²ˆÓŒ©‚̓Nƒ`ƒRƒ~‚Å‚¨•·‚©‚¹‚‚¾‚³‚¢B
ƒŠƒXƒgƒ}ƒjƒA
ŠÖ˜A¤•i‚ð’T‚·
“¯‚¶ƒL[ƒ[ƒh‚̤•i‚ð’T‚·
ƒtƒB[ƒhƒoƒbƒN
- ƒJƒ^ƒƒOî•ñA‚Ü‚½‚͉摜‚ɂ‚¢‚Ä•ñ
- ’˜ŽÒ‚©‚ç‚̃Rƒƒ“ƒg
- o”ŎЂ©‚ç‚̃Rƒƒ“ƒg
|
