CD-ROM contains: Java and XML implementations of ideas and models described in the appendix.

"This book bridges two fields that, although closely related, are often studied in isolation: enterprise modeling and information systems modeling. The principal idea is to use a standard language for modeling information systems, UML, as a catalyst and investigate its potential for modeling enterprises"--Provided by publisher.

Modeling Enterprise Architecture with TOGAF explains everything you need to know to effectively model enterprise architecture with The Open Group Architecture Framework (TOGAF), the leading EA standard. This solution-focused reference presents key techniques and illustrative examples to help you model enterprise architecture. This book describes the TOGAF standard and its structure, from the architecture transformation method to governance, and presents enterprise architecture modeling practices with plenty of examples of TOGAF deliverables in the context of a case study. Although widespread and growing quickly, enterprise architecture is delicate to manage across all its dimensions. Focusing on the architecture transformation method, TOGAF provides a wide framework, which covers the repository, governance, and a set of recognized best practices. The examples featured in this book were realized using the open source Modelio tool, which includes extensions for TOGAF. Includes intuitive summaries of the complex TOGAF standard to let you effectively model enterprise architecture Uses practical examples to illustrate ways to adapt TOGAF to the needs of your enterprise Provides model examples with Modelio, a free modeling tool, letting you exercise TOGAF modeling immediately using a dedicated tool Combines existing modeling standards with TOGAF

Enterprise Patterns and MDA teaches you how to customize any archetype pattern–such as Customer, Product, and Order–to reflect the idiosyncrasies of your own business environment. Because all the patterns work harmoniously together and have clearly documented relationships to each other, you’ll come away with a host of reusable solutions to common problems in business-software design. This book shows you how using a pattern or a fragment of a pattern can save you months of work and help you avoid costly errors. You’ll also discover how–when used in literate modeling–patterns can solve the difficult challenge of communicating UML models to broad audiences. The configurable patterns can be used manually to create executable code. However, the authors draw on their extensive experience to show you how to tap the significant power of MDA and UML for maximum automation. Not surprisingly, the patterns included in this book are highly valuable; a blue-chip company recently valued a similar, but less mature, set of patterns at hundreds of thousands of dollars. Use this practical guide to increase the efficiency of your designs and to create robust business applications that can be applied immediately in a business setting.

UML (Unified Modeling Language) ist ein leistungsfähiges Tool für die Entwurfsplanung von objektorientierten Computersystemen. Mit seiner Hilfe kann der Zeitaufwand für die Software-Entwicklung enorm reduziert werden. Entsprechend groß ist daher nicht nur die Nachfrage nach UML für firmeninterne Systementwicklung sondern auch nach praktischer Anleitung für den richtigen Einsatz von UML. Dies ist der Nachfolgeband des sehr erfolgreichen Titels "UML Toolkit" von Eriksson und Penker. Er konzentriert sich auf die brandaktuellen komponenten-orientierten Konzepte und erklärt, wie man OCL (Object Constraint Language) von UML für Business Rules und Business Views einsetzt. Dokumentiert sind 27 hilfreiche Business Patterns. (cat06/99)

In 1995, David Hay published "Data Model Patterns: Conventions of Thought" -- the groundbreaking book on how to use standard data models to describe the standard business situations. This book builds on the concepts presented there, adds 15 years of practical experience, and presents a more comprehensive view. You will learn how to apply both the abstract and concrete elements of your enterprise's architectural data model through four levels of abstraction: Level 0: An abstract template that underlies the Level 1 model that follows, plus two meta models; Level 1: An enterprise model that is generic enough to apply to any company or government agency, but concrete enough to be readily understood by all; Level 2: A more detailed model describing specific functional areas; Level 3: Examples of the details a model can have to address what is truly unique in a particular industry.