Enterprise Patterns and MDA Building Better Software with Archetype Patterns and UML

by Arlow, Jim; Neustadt, Ila

• ISBN13: 9780321112309
• ISBN10: 032111230X
• Edition: 1st
• Format: Paperback
• Copyright: 2003-12-22
• Publisher: Addison-Wesley Professional

Summary

bull; bull;A proven catalogue of reusable solutions to commonly occurring problems in business software design bull;Allows readers to communicate UML models to the broadest possible audience bull;Cutting-edge techniques to leverage the significant power of MDA and the latest version of UML (2.0)

Author Biography

Since 1990, Jim Arlow has been programming and designing object-oriented systems, including object models, for companies such as a consultant Over her twenty years working in British Airways' IT Department, IIa Neustadt has gained experience in all phases of the development lifecycle

Table of Contents

Foreword	p. xvii
Introduction	p. xxi
Acknowledgments	p. xxvii
Archetype theory, practice, and Model Driven Architecture	p. 1
Archetypes and archetype patterns	p. 3
Introduction	p. 3
What are archetypes?	p. 4
What are business archetypes?	p. 5
Archetypes and analysis classes	p. 7
What are patterns?	p. 8
Archetype patterns and analysis patterns	p. 9
UML profile for archetypes and archetype patterns	p. 10
Modeling style	p. 14
Variation	p. 17
Archetype variation and optionality	p. 18
Archetype pattern variation	p. 20
Pleomorphism	p. 22
How to find archetype patterns	p. 25
Model management for archetype patterns	p. 28
Using archetype patterns in your models	p. 29
Translation and mapping	p. 32
Example applications of archetype patterns	p. 36
Summary	p. 43
Model Driven Architecture with archetype patterns	p. 49
Introduction	p. 49
Introduction to Model Driven Architecture	p. 50
Archetype patterns and MDA--creating a PIM	p. 56
Archetype pattern automation	p. 57
Pattern configuration	p. 58
A simple example	p. 61
Pattern configuration rules	p. 63
Pattern configuration rules in UML	p. 64
How to create pattern configuration rules	p. 67
Archetype pattern automation with ArcStyler	p. 68
Enabling ArcStyler with archetype patterns	p. 70
Entering the archetype pattern into ArcStyler	p. 73
The pattern configuration GUI	p. 75
Generating source code	p. 77
Summary	p. 80
Literate modeling	p. 85
Literate modeling	p. 87
Acknowledgments	p. 87
Introduction	p. 87
The problem with visual modeling	p. 87
A solution--literate modeling	p. 88
The comprehensibility and accessibility of UML models	p. 89
The problem of comprehensibility	p. 95
The trivialization of business requirements in visual modeling	p. 96
Literate modeling	p. 98
Structuring the business context document	p. 98
Creating a business context document	p. 100
Developing a business nomenclature	p. 102
Business context documents and packages	p. 103
Business context document conventions	p. 103
UML tags for literate modeling	p. 105
Readability	p. 107
Use concrete examples	p. 108
Precision and correctness	p. 109
The future of literate modeling	p. 109
Summary	p. 112
Archetype pattern catalog	p. 117
Party archetype pattern	p. 119
Business context	p. 119
Compliance with standards	p. 120
Party archetype pattern overview and roadmap	p. 120
The Party archetype	p. 122
Types of Party	p. 124
PartyIdentifier	p. 125
RegisteredIdentifier	p. 127
PartySignature	p. 128
PartyAuthentication	p. 128
Address	p. 132
Person	p. 137
ISOGender	p. 140
Ethnicity	p. 140
BodyMetrics	p. 141
PersonName	p. 141
Organization	p. 143
Company	p. 144
Company names	p. 146
Identifiers for Companies	p. 147
Company organizational units	p. 148
Partnerships and sole proprietors	p. 149
Preferences	p. 150
PartyManager	p. 153
Summary	p. 154
PartyRelationship archetype pattern	p. 157
Business context	p. 157
PartyRelationship archetype pattern overview and roadmap	p. 158
PartyRole and PartyRelationship	p. 160
N-ary relationships	p. 164
A simple example	p. 165
PartyRoleType and PartyRelationshipType	p. 172
Managing PartyRoles and PartyRelationships	p. 173
Responsibilities	p. 179
Capabilities	p. 182
Using the PartyRelationship archetype pattern	p. 182
PartySummary	p. 183
Summary	p. 184
Customer relationship management archetype pattern	p. 187
Business context	p. 187
CRM archetype pattern overview and roadmap	p. 188
Customer	p. 190
CustomerCommunicationManager	p. 192
Communication	p. 193
CustomerServiceCase	p. 195
Actions and Outcomes	p. 198
Summary	p. 200
Product archetype pattern	p. 203
Business context	p. 203
Compliance with standards	p. 203
Product archetype pattern overview and roadmap	p. 204
Variation in the Product archetype pattern	p. 204
The Product archetype pattern	p. 207
ProductType and ProductInstance	p. 208
Uniquely identifying goods and services	p. 210
Candidates for ProductIdentifier	p. 210
SerialNumber and Batch	p. 214
Product specification	p. 218
ProductCatalog	p. 221
CatalogEntry	p. 224
Packages	p. 225
PackageType and PackageInstance	p. 226
Combining ProductTypes	p. 227
Package specification process	p. 230
Rule-driven package specification	p. 232
Concepts of rule-driven package specification	p. 234
An example of a PackageType	p. 238
ProductRelationships	p. 242
Up-selling and cross-selling	p. 244
Price	p. 245
Package pricing	p. 252
Measured products	p. 254
Services	p. 254
ServiceType and ServiceInstance	p. 256
The specialized Product pleomorphs	p. 258
Summary	p. 262
Inventory archetype pattern	p. 267
Business context	p. 267
Inventory archetype pattern overview and roadmap	p. 269
Inventory and the Product archetype pattern pleomorphs	p. 269
The Inventory archetype	p. 271
ProductInventoryEntry	p. 275
ServiceInventoryEntry	p. 277
Capacity planning and management	p. 279
Availability	p. 282
Reservations	p. 282
Example--an inventory of books	p. 286
Book inventory revisited	p. 291
Example--an inventory of train journeys	p. 293
Summary	p. 301
Order archetype pattern	p. 303
Business context	p. 303
Order archetype pattern and roadmap	p. 304
The Order archetype	p. 304
PurchaseOrder and SalesOrder	p. 310
OrderLine	p. 310
PartySummaryRoleInOrder	p. 315
DeliveryReceiver	p. 318
ChargeLine	p. 318
TaxOnLine	p. 319
OrderManager	p. 321
OrderEvents	p. 322
OrderStatus and LifecycleEvents	p. 326
AmendEvents	p. 328
AmendOrderLineEvent	p. 331
AmendPartySummaryEvent	p. 334
AmendTermsAndConditionsEvent	p. 336
DiscountEvent	p. 337
DespatchEvent	p. 339
ReceiptEvent	p. 341
OrderPayment and PaymentEvents	p. 343
Payment strategies	p. 346
Modeling the business process for Orders	p. 348
The PurchaseOrder process archetype	p. 349
PurchaseOrder--process cancellation	p. 351
process PurchaseOrder	p. 353
The SalesOrder process archetype	p. 364
SalesOrder--process cancellation	p. 366
process SalesOrder	p. 368
Order process documentation	p. 382
Variation in Order processes	p. 383
Summary	p. 385
Quantity archetype pattern	p. 391
Business context	p. 391
Compliance with existing standards	p. 392
Quantity archetype pattern and roadmap	p. 392
Money and Currency	p. 392
Metric	p. 393
Unit and SystemOfUnits	p. 395
SIBaseUnit	p. 395
DerivedUnit	p. 398
ManHour	p. 399
Quantity	p. 400
StandardConversion and UnitConverter	p. 408
Summary	p. 409
Money archetype pattern	p. 411
Business context	p. 411
Compliance with existing standards	p. 412
Money archetype pattern overview and roadmap	p. 413
Money	p. 413
Currency	p. 414
Locale and ISOCountryCode	p. 418
Working with Money	p. 420
ExchangeRate and CurrencyConverter	p. 422
Payment	p. 425
Summary	p. 431
Rule archetype pattern	p. 433
Business context	p. 433
Rule archetype pattern and roadmap	p. 433
What are rules?	p. 434
Business rules and system rules	p. 435
Business rules	p. 435
Business system rules	p. 436
Rules and business processes	p. 437
The physical location of rules	p. 441
Rules and formal logic	p. 442
Logic and the Rule archetype pattern	p. 445
RuleElement	p. 445
Operator	p. 447
Proposition	p. 447
Variable and DateVariable	p. 448
RuleContext	p. 449
Rule	p. 449
Rule evaluation	p. 454
ActivityRule	p. 457
RuleSet	p. 458
RuleOverride	p. 459
Summary	p. 459
Summary	p. 461
Archetype glossary	p. 463
Bibliography	p. 477
Index	p. 481
Table of Contents provided by Ingram. All Rights Reserved.

Excerpts

About This Book This is a practical book that we hope will save you a great deal of time and effort in your software development projects. It gives you a set of archetype patterns and the theory you need to use them effectively. We're planning to publish some more volumes of archetype patterns over the next few years, and because this book is the first volume, it sets the theoretical groundwork for future work on archetypes. Archetype patterns are high-value model components that you can easily use in your own UML models. Each archetype pattern provides a solution for understanding and modeling a specific part of a business system. These patterns are valuablea similar, but much less mature, set of patterns was recently independently valued at about $300,000 by a blue chip company. Using any one of these patterns, or even a pattern fragment, may save you many days or months of work. Even more important than this saving is the fact that each archetype pattern may prevent you from making expensive mistakes! All of the patterns presented in this volume work together harmoniously and so provide a unified pattern language for talking about selling systems. This harmony greatly adds to their value. We think that in the year 2003, we are at the start of a revolution in software development. Much as the 1990s saw an increase in the level of abstraction from procedural to object-oriented code, we believe that this decade will see a further, and more significant, increase in the level of abstraction. This will be a change from code-centric software development to model-centric software development through the OMG's Model Driven Architecture (MDA) initiative. We hope that the concepts, techniques, tools and patterns that we describe in this book will help us all to make this revolution in software development a reality. Our Vision One of the reasons this book came about was through boredom! After modeling for many years, we decided that we were often just doing the same old thing over and over again. At their most abstract levels, most businesses seem to be made up of the same semantic elementsCustomer, Product, Order, Party, etc. In fact, so pervasive are some of these elements, that it led us to the notion of business archetype patterns. We speculated that most business systems could be assembled, like Lego bricks, from a sufficiently complete set of archetype patterns. The essence of our vision is that archetype patterns should be treated as a type of "model component" that can be taken off the shelf, customized and instantiated in your own models. This process can be done manually, but ideally should be automated to as high a degree as possible, by using an MDA (Model Driven Architecture) tool. Today, you can use a GUI builder to create graphical user interfaces rapidly from GUI components. The work we describe in Chapter 2 enables you to construct semantically correct and verifiable UML models rapidly from platform independent, generic, model components with a high degree of automation. We believe that this may be the future of software development. We call this "component based modeling." This is reuse writ largesoftware systems are not considered to be composed of reusable classes, reusable code components, or even reusable subsystems, but rather from the reusable semantic elements that we call archetype patterns. In fact, to a great extent the essence of the business system lies in its archetypes and their patterns, rather than in any code or design artifacts. Coding practices, design practices and even architectures come and go with technology changes, but the archetypes survive, largely unchanged, sometimes over millennia. Why We Haven't Done It Sooner We have wanted to write this book for several years but there have been obstacles that we have only recently overcome. These obstacles were: The state of the art of UML modeling. Until the OMG's recent Model Driven Architecture initiative, we have not really had the conceptual tools necessary to describe archetype patterns in good form. The problem of pattern variationbusiness patterns often need to adapt their form to a specific business context. We have now formulated a simple solution to this problem that allows us to create archetype patterns that are adaptable to different business environments. The problem of communicating UML models to a wide audience. In fact, we've had a good solution to this for a few years now, in the form of literate modeling (described in Chapter 3). UML modeling tool support. It's all very well presenting a theory of archetype patterns, but such a theory is useful to the average software engineer only if it can be put into practice. Modeling tools have recently come on to the market that can accommodate our requirements for archetype pattern automation. The Structure of This Book There are four main threads to this book: The theory of archetypes and archetype patterns (Chapters 1 and 2) Pattern automation using Model Driven Architecture (Chapter 2) Increasing the business value of UML models by making them accessible to a wide audience through literate modeling (Chapter 3) A valuable pattern catalog that you can use in your own models (Chapter 4 onward) Chapters 1, 2 and 3 provide you with the theoretical basis for the rest of the book, and you will find that they cover a lot of new material. In Chapter 1 we describe a new approach to dealing with the problem of pattern variationhow to adapt patterns for different usage contexts. In Chapter 2 we show you how you can automate the process of using archetype patterns using an MDA-enabled UML modeling tool. The first two Chapters are intimately related. The pattern automation described in Chapter 2 depends on the theory of archetypes and archetype patterns presented in Chapter 1. Chapter 3 describes the technique of literate modeling that you can use to document your patterns. This chapter is pretty much self-contained. Literate modeling is a powerful way of communicating UML models to a wide audience. Each of the first three chapters contains a summary that reiterates the key information in the chapter in a very concise outline form. This is great for revision and it is also a useful source of bullet points for presentations. The pattern catalog can stand alone. If you choose to use the book primarily as a pattern catalog (Chapter 4 through Chapter 12), then you can skip much of the theoretical background in the first three chapters. Use the pattern catalog as a valuable resource for your own models. Each of the pattern chapters ends with a very brief summary that lists the key concepts and archetypes introduced in that chapter. Again, we do this in outline form. Having said that the pattern catalog can stand alone, we believe that you will be able to apply the patterns much more effectively if you have at least a basic understanding of archetype theory first. You can find all you need to know in Chapter 1. All the patterns in the in the pattern catalog are a direct result of the application of the theories and techniques described in the first three chapters. The notions of archetypes, archetype patterns, pattern configuration and literate modeling have allowed us to create much more complete and robust patterns than would otherwise have been possible. Finally, we provide a glossary of archetypes, a bibliography and a complete index. 032111230XP09152003