|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
商品の説明
内容説明
This book presents a proven method of successfully addressing the significant challenges of developing applications for the business world. Borrowing from their significant experience in corporate development, the authors present a catalog of proven and supremely useful patterns that can be applied to the idiosyncrasies of the business domain. This book also explains how to use Model-Driven Architecture to increase the efficiency of your designs, and how to further the capabilities of the industry-standard Unified Modeling Language. The result is a practical, no-nonsense approach to building robust business applications that can be immediately applied in a corporate setting.
著者について
Jim Arlow has been programming and designing object-oriented software systems since 1990. He has created object models for blue chip companies such as British Airways and M&G. He is a respected OO consultant in Europe and has written and delivered many training courses on object technology and Java. Jim is a regular speaker at conferences such as Object World, and has been an invited speaker at University College London, City University, and the British Computer Society.
Ila Neustadt has worked in IT for British Airways for more than twenty years and has experience of all parts within the IT development life cycle. She worked in the strategy department modeling the architecture process and developing architecture training, and acted as program head for the graduate business analyst program. Ila now coordinates skills development for BATMs IT staff.
登録情報
|
この商品にタグをつける(詳細)タグは、商品との関連性が非常に強いキーワードまたはラベルのようなものです。
タグにより、すべてのお客様がお気に入りの商品の整理と確認を行うことができます。 ※タグは初期設定で公開になっています。詳しくはこちら |
カスタマーレビュー
最も参考になったカスタマーレビュー
1 人中、1人の方が、｢このレビューが参考になった｣と投票しています。
形式:ペーパーバック
アーキタイプというビジネスシステムのパターン化の方法を紹介しています。その具体例として、著者がコンサルタントとして使ってきたパターンをアーキタイプパターンライブラリー として解説しています。著者はさらに、リテレートモデリングというモデリング手法も紹介しています。リテレートモデリングは「説明的」モデリングとでも訳すのが適当と思いますが、 UMLダイアグラムだけでなくモデルに豊富なわかりやすい説明文をつけると言うことです。この本自身がリテレートモデリング のサンプルになっています。ビジネスシステムのモデリングについて非常に多くを学ぶことのできる本です。
形式:ペーパーバック
アナリシスパターンがメタレベルなのに対して、この本は実際のビジネスモデリングのパターンを非常に詳しくわかりやすく説明しています。ふんだんにUMLが使用されているのでUMLモデリングの実践書としても使えます。
Amazon.com で最も参考になったカスタマーレビュー (beta)
Amazon.com:
6件のカスタマーレビュー
10 人中、10人の方が、｢このレビューが参考になった｣と投票しています。
Valuable in many ways.
2004/8/3
形式:ペーパーバック|Amazonが確認した購入
Nominally, this book presents "archetype patterns", using UML and an extended case study. The archetype idea, intermediate between a general design pattern and a specific application, is a valuable one. In the case study, it's a set of business meta-objects, operations, and organizing principles. In presenting the archetype abstraction, those objects are spelled out in enough detail to create a useable framework for routine business needs.
The archetype mechanism is also spelled out in great detail, almost wholly within the UML framework. By itself, this won't be enough to convince any UML doubters about UML's flexibility. Taken as one among many UML applications, however, it's very compelling. It's also the first reference I know that gets down to cases in applying MDA - an interesting view. I fault the technique for only two things. First is a slight dependence on a specific CASEproduct, ArcStyler. That reliance never turned all the way into an advertisement, so I'll let it pass. Second is a baffling section on "rules." The rules and rule mechanisms make sense, but inexplicably seem to re-create the features of the OCL.
Two extras make this presentation very attractive. First is the mention of "literate programming," tying the UML tool suite to user documentation and design documentation. They specifically note XML and DocBook, existing standards, as the vehicle for integrating prose and technical parts of the model. Bravo! Even if their LP tools are weak, use of the idea is a real strength. The second extra is a pervasive awareness of standards. Money is phrased in terms of ISO 4217, nations in terms of ISO 3166, books in terms of ISBNs (ISO 2108), and on and on. Far too few programmers realize how many of their software requirements are already spelled out in external standardslike these, so the consciousness-raising exercise is a good one.
This is an excellent resource, not just for its business objects and not just for its UML case study. The author treat even personal names (table 4.4) with more care than I've seen anywhere else - that care pervades the whole book, and is a lesson in itself.
//wiredweird
The archetype mechanism is also spelled out in great detail, almost wholly within the UML framework. By itself, this won't be enough to convince any UML doubters about UML's flexibility. Taken as one among many UML applications, however, it's very compelling. It's also the first reference I know that gets down to cases in applying MDA - an interesting view. I fault the technique for only two things. First is a slight dependence on a specific CASEproduct, ArcStyler. That reliance never turned all the way into an advertisement, so I'll let it pass. Second is a baffling section on "rules." The rules and rule mechanisms make sense, but inexplicably seem to re-create the features of the OCL.
Two extras make this presentation very attractive. First is the mention of "literate programming," tying the UML tool suite to user documentation and design documentation. They specifically note XML and DocBook, existing standards, as the vehicle for integrating prose and technical parts of the model. Bravo! Even if their LP tools are weak, use of the idea is a real strength. The second extra is a pervasive awareness of standards. Money is phrased in terms of ISO 4217, nations in terms of ISO 3166, books in terms of ISBNs (ISO 2108), and on and on. Far too few programmers realize how many of their software requirements are already spelled out in external standardslike these, so the consciousness-raising exercise is a good one.
This is an excellent resource, not just for its business objects and not just for its UML case study. The author treat even personal names (table 4.4) with more care than I've seen anywhere else - that care pervades the whole book, and is a lesson in itself.
//wiredweird
7 人中、7人の方が、｢このレビューが参考になった｣と投票しています。
Nice resource on your bookshelf
2004/2/8
形式:ペーパーバック
"Enterprise Patterns and MDA" is not an MDA book. In fact, the most significant focus of the book is actually patterns, specifically business patterns and archetypes.
The authors start the journey by introducing concepts and techniques such as archetypes (universal, recurring "things") and archetype patterns, and Model Driven Architecture. Furthermore, the authors have dedicated one chapter for describing a technique called Literate modeling (combining traditional visual modeling with an accessible business context provided via a narrative text, for example).
Up to this point (vicinity of page 116), the authors' writing style has been flawless, in my opinion, and easy to read. From chapter 4 onwards, the authors have provided a huge pattern catalog for archetype patterns. The catalog has been divided into chapters around archetypes such as Party, Order, Customer, and so on. Each archetype pattern introduces a business context, a high-level overview model, and descriptions of the related archetypes, their properties and related activities.
I didn't go through even nearly all patterns in the catalog. However, I feel confident that I will dive into the catalog looking for insight when moving to a new problem domain on a new project. Enterprise Patterns and MDA is a nice resource to have on your bookshelf.
6 人中、6人の方が、｢このレビューが参考になった｣と投票しています。
Great practical material instead of esoteric theory...
2004/6/30
形式:ペーパーバック
Over the last month or so, I've been reading Enterprise Patterns And MDA - Building Better Software With Archetype Patterns And UML by Jim Arlow and Ila Newstadt (Addison-Wesley). This is another one of those books that I thought would deliver one thing and instead produced much more than I expected.
Chapter breakdown: Archetypes and Archetype Patterns; Model Driven Architecture with Archetype Patterns; Literate Modeling; Party Archtype Pattern; PartyRelationship Patter; Customer Relationship Management Pattern; Product Pattern; Inventory Pattern; Order Pattern; Quantity Pattern; Money Pattern; Rule Pattern; Summary; Archetype Glossary; Bibliography; Index
Now, when I requested this for review, I was expecting something in terms of programming patterns and technical material. What I got was a great business tool for modeling typical business objects and transactions. The authors take a business concept like Inventory, and they build a model around it. The model is an archetype, or a entity that exists in some shape in every business. Through UML diagrams, you'll see all the parts that make up the archetype and how to take the parts you need to build your own version of the entity. While the Inventory model is very comprehensive in the book, you can also pull the pieces you need to model the reality that exists in your own business.
There's some very practical benefits you can gain from this book. If you're building an application and need to track a customer (for example), you can turn to the Party model and see all the parts that make up that type of entity. This will help you to understand all the data elements that make up a Party, such as address (web, email, telephone, geographic), organization, person/gender/ethnicity, relationship, etc. These are elements you might think of and/or remember to include, but having the model there helps you get it right early on.
If you're a business analyst, you will really get your value from this book. And if you're a developer who also has to design the systems, you'll look like a wizard when you complete a solid design with features the customer didn't even realize they needed.
これらのレビューは参考になりましたか？
ご意見はクチコミでお聞かせください。
リストマニア
|
|
関連商品を探す
同じキーワードの商品を探す
フィードバック
- カタログ情報、または画像について報告
- 著者からのコメント
- 出版社からのコメント
|
