Download (direct link):
In addition, a bonus chapter in Microsoft Word format can be found on our companion Web site (www.ConvergentArchitecture.com), which constitutes a reference manual and user's guide containing the design and usage details of the MDA modeling styles and the J2EE/EJB technology mappings that were introduced in Chapter 4 and applied throughout the book. It also shows how these features are explicitly supported by the architectural IDE. This detailed reference material is available on the Web so that it may be easily maintained, thus providing the reader with an up-to-date version at all times. However, the material in this chapter can only be properly understood and applied when read in conjunction with this book because the chapter makes extensive reference to the architectural concepts, terms, processes and tools covered in Chapters 1 through 8.
Who Should Read This Book
A variety of readers will be interested in the subject matter covered in this book, each from a different perspective. The following reading sequence is recommended for each respective audience:
■ CEOs/CIOs and business consultants will find the message regarding IT-architectural style and Convergent Architecture in Chapters 1 through 3 of particular relevance. For the next level of detail, they should proceed to the introductions in Chapter 5, "The IT Organization Model," and Chapter 6, "The Development-Process Model."
■ Chief architects, IT consultants, project managers, lead developers, and those interested in the OMG Model-Driven Architecture Initiative are the prime audience for the entire book.
■ J2EE/EJB developers and Web service developers may want to first read the tutorial example (Chapter 8) to get a hands-on feeling for the development process and environment, and then move to the chapters explaining the development process (Chapter 6), the architectural IDE (Chapter 7), and the details on the Modeling Style and Technology Projections (the bonus Web site chapter). At some point, Chapter 2 should be read in order to better understand the big picture and roadmap of the architectural style.
Tools You Will Need
The examples in the first seven chapters of this book, as well as the hands-on tutorial in Chapter 8, use the following tools to demonstrate the model-driven approach and the integrated architectural environment:
■ A J2EE/EJB application server. Borland Application Server, BAS 4.5 or higher, available from www.Borland.com, or the WebLogic Server 6.1 or higher, available from www.BEA.com.
■ Java IDE. JBuilder or JBuilder Enterprise version 5 or higher, which includes the BAS application server, available from www.Borland.com.
■ UML Modeling Tool. Rose 2001 or 2001 A Modeler Edition or higher, available from www.Rational.com.
■ Architectural IDE. The latest release of the ArcStyler Architectural IDE for MDA, available from www.ArcStyler.com.
The Convergent Architecture Web Site
Of course, it is impossible to put everything concerning the Convergent Architecture into a concise book outlining the entire architectural style. Extensive material pertaining to the Convergent Architecture is available in addition to this book. Also, the Convergent Architecture continues to evolve, so new material and updates will emerge. Thus, a Web site has been created to accompany this book with new and complementary material in a readily accessible forum at www.ConvergentArchitecture.com.
The basic contents of the site are as follows:
■ Tutorial and sample material applying the Convergent Architecture including its MDA/RUP features and tools
■ References, case studies, presentations, papers, and demonstrations
■ Extended specifications and user guidelines
■ Reusable assets ranging from open-source, reusable projectware to
extension modules for the architectural IDE
■ Updates to the architectural IDE and related product information
■ Contacts, community, and event information
The concepts, techniques, and tools presented in this book have been applied in numerous IT environments, both large and small, to achieve significantly higher levels of IT effectiveness. The purpose is to enable corporate architects, CIOs, project managers, and individual project team members to immediately leverage MDA in the context of a holistic architectural approach by applying a well-defined IT architectural style.
We hope that the definitions and examples in the initial chapters convince you of the far-reaching advantages of IT architectural style as we define it. Above all, we hope to convey the advantages of a tried and tested IT architectural style, the Convergent Architecture, as a lasting remedy to significant problems experienced by almost every IT organization today.
The bottom line is that the Convergent Architecture was developed by practicing IT architects to help any IT endeavor achieve higher goals. It is about making the sum of our efforts much greater than the individual parts. It is about defining how we approach business design, project design, and system design at all levels of an organization in a cumulatively synergistic manner. It is about putting diverse pieces together in a holistic big picture to provide IT organizations with a longterm vision and lasting improvements. It is about achieving a consistent cycle of simplification and optimization across the entire landscape of IT development and throughout its long-term evolution. And it's about the positive energies that we all share when we do things with style.