Thanks for the reply;
The model I am currently trying to process in AndroMDA is one of the many models (5-6) that form the basis for my application. This particular model is the domain model related to a financial industry sector I am working in and at this time I am interested in keeping the model as single layer since it will be the basis for the data store (for which the schema I am trying to generate). So as you can see this model is the basis for the persistance database. In essense I am modeling the domain database and using an AndromDA model. The other models in my application that consititue either other databases or application domain model complements this model but are not as large By the way as far as I know, any serious industry standards compliant data (object) model will be a sizable one specially in financial and insurance industry. As for the scalability issue you addressed, I am talking about the scalability of the AndroMDA tool and not the scalability of the architectures that androMDA help generate. Tool scalaibility is related to how large a model one can use and process in a tool IF it is determined that you absolutley can't decompose the architecture in several modeules whose size are easily processed in AndromDA. At this time one of my six components happens to be that large and so far I didn't try to decompose it further since it is supposed to form the basis for a single database schema. >From an architectural point of view I need a single model for this particular >component of the system (the database). It is only from a tool limitation >aspect that I might need to break it down, which is due to teh scalability >issue. Also, scalibility from my perspective is when the tool can't scale up to match the kind of work you need to do, regardless what caused the problem whether is a major architectural defect in the design of the tool (AndromDA has no such architectural issue and in fact one of the reason of its success in my mind is its cood losely coupled architecture) or a minor bug somewhere, which is the case I think in my situation. At any case, at this time, I am using androMDA to get all teh necessary code and mapping files and then I use Hibernate directly to complete the process to generate teh schema outside AndroMDA. I will try at one time to see if I can figure out teh problem and if I find it I will report it back to teh forum. Thanks again. Safaa _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=3830#3830 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
