Robert Turrall

Congratulations to the winners - I hope you enjoy reading the book and that it adds some value to your future projects!
I just wanted to throw in a short word from our side (Richard, Interactive Objects and myself) to say that the discussions about MDA, CA (Convergent Architecture) and the book have been interesting and we're still around so will be happy to discuss more!
Regards,
Robert
[ March 08, 2002: Message edited by: Robert Turrall ]

Hi Shailesh,
There's no such thing as a silly question ;-)
What's interesting is to see which questions are being asked and how people receive the book, and the MDA concept!
I think the most common association people make when they hear the word "architecture" is with the technical (ie. platform-specific) configuration of any particular software solution. This is a common understanding of what IT architecture is about.
Written in plain language: what MDA is talking about, and hence a common theme throughout Richard's book, is approaching architectural modeling from a higher level of abstraction - totally platform-independent - and modeling to as high a degree of functionality as possible before considering any specific implementation technologies. Clearly, what is then needed is to be able to translate the modeled architecture 100%, or as close to 100% as possible, to a high quality platform-specific infrastructure, capable of meeting the requirements laid down at the beginning.
The real value behind MDA then comes to light - the ability to re-deploy on other platforms with the same models, the ability to migrate from one app. server version to the next without having to remodel and rewrite large chunks of a system and being able to extend the resultant IT archictecture to satisfy future requirements with minimum effort and cost savings over previous methods.
I know it sounds like a dream come true but that's actually what the OMG MDA initiative is about and what Richard is describing in his book. A coming-together of many of the principles we all know under the control of an end-to-end set of standards which facilitate the enforcing of an architectural style throughout the whole cycle. It is also, by the way, what ArcStyler is designed to do, and has done in practice in various projects so far.
(I hope that wasn't too "evangelistic"?)
Robert

Hi,
If you take a look into this thread, you'll find a clear definition from Richard Hubert:
http://www.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=9&t=001052
There are a few threads popping up about the book now, but this was the first and so contains Richard's initial (very comprehensive) responses.
Regards,
Robert

As far as using other tools than those mentioned in Richard's list is concerned:
The list is basically a recommended list, chosen for reasons stated in the book itself (see the Chapter 7 description in Richard's posting above).
As far as RUP is concerned, I'd also refer you back to Richard's posting and to the book. RUP is part of the process, as is the choice of an implementation platform (app. server, IDE, etc.) but the whole concept of Convergent Architecture and Model Driven Architecture starts at a much higher level of abstraction... at the consideration of the architecture itself (not to be confused with an implementation technology - note the comparisons Richard makes in the book between IT architecture and classic architecture, as related to buildings). ArcStyler is the Architectural IDE which brings together other "best of breed" tools (much as an architect will bring together specialists such as electrical and heating engineers when conducting a building project) within an environment which enables you to implement and promote a specific architectural style from beginning to end.
A short word about ArcStyler support for other tools:
To use other application server platforms instead of those mentioned is, of course, supported by ArcStyler as the Architectural IDE platform. If your chosen implementation platform is a J2EE app. server, ArcStyler currently offers pure J2EE app. server support out-of-the-box. Specific vendor app. server support is delivered via MDA Cartridges which offer extended support for the more vendor-specific features in addition to the pure J2EE functionality. In addition to those already explicitly supported (and to the Java IDEs explicitly supported) further products will be supported with version 3.0 of ArcStyler...
A full technical briefing about ArcStyler and MDA is available on our web site and can answer a lot of these questions while putting RUP, etc. into context:
http://www.io-software.com/products/as_media_main.html
Just click on one of the "ArcStyler Technical Briefing" links...
Regards,
Robert Turrall
Interactive Objects Software GmbH
[ March 07, 2002: Message edited by: Robert Turrall ]

Hi,
To summarise the motivation behind MDA in a short sentence (and to borrow a few words from Dr. Richard Soley, Chairman and CEO of the OMG): "MDA is intended to provide a comprehensive, structured solution for future-safe and interoperable application development."
What this means is that CORBA is a possible implementation platform approach for an IT system, as is J2EE or EJB. MDA starts at a higher level of abstraction.
Regards,
Robert

Originally posted by shailesh sonavadekar:
omg was instrrumental in having corba standard for interoprability. what is the motive behind this drive ?

UML forms part of the picture, so to speak, being brought into play to produce various models. Take a look at www.omg.org/mda to find a summary of MDA and the current level of the specification, etc.

Originally posted by shailesh sonavadekar:
what are the differences ? specific advantages / disadvantages ?

Hi Chris,
The book contains extensive examples and advice about putting the prinicples described into practice using ArcStyler, an Architectural IDE for MDA (www.ArcStyler.com).
Robert

Originally posted by chris coleman:
A question regarding Richard's new book:
Assuming Richard shows some kind of example/casestudy of his new Convergent Architecture techniques... is there any advice for applying his new technique in the modeling tools, e.g. Together, Rose...?

Hi all,
I'm an employee of Richard's and "filing in" for him for a few minutes until he gets online...
To address the question "what's the book all about": It is effectively a blueprint for appplying the principles defined within MDA and in the book "Business Engineering with Object Technology" by David A. Taylor.
The book is a step-by-step guide which takes you through the process of designing and implementing corporate architectural styles and IT systems using CA (Convergent Architecture) and MDA.
The intended audience includes, basically, anybody who is involved with any stage of the design or implementation of IT systems.
There's also a web site with information about the book: www.ConvergentArchitecture.com.
Regards,
Robert

Originally posted by Doug Wang:
Hi Richard,
Welcome here!
I guess this book is intended to apply MDA with J2EE system development. Am I right?

[ March 06, 2002: Message edited by: Robert Turrall ]