There have been a number of posts over time that have touched on the issue of handling larger models/reusing models/importing jars in AndroMDA. I thought it might be worthwhile kicking off a thread on this subject (that may run for some time as we improve our understanding :) ).
The first step is to identify some of the use cases relevent to this topic (first question I always ask - where are the requirements - not very XP unfortunately - but maybe user stories has a kinder ring to it :) ). So here we go - note initial attempt, some may be overlapping, others not relevant to AndroMDA: Scenario 1 I have a team of developers. How do I structure my models to support a highly interactive dynamic team without falling into the waterfall trap or stepping on each others toes. Scenario 2 I have a very large application. Do I need to have a single large model or can I break it into a set of modules or separate models. If I have separate modules/models - how do I handle the situation were one calls the services of another. Scenario 3 My organisation is moving to a SOA architecture. If I have multiple services that I want to consume/produce, that may or may not be defined in other models what is the best way to represent this in my model. Scenario 4 I have a very large model derived from one of the XML Standards. What strategies can I use to structure this model so that I can make the best use of AnrdoMDA whilst adhering to the intent of the original specification. OK That's enough for now. The feedback I'm looking for is: 1. Refine the scenarios (add/delete/...) 2. your experiences - how have you handled some of these scenarios 3. how would you tackle some of the problems (note - good to say not a problem or not relevant for AndroMDA). I don't expect we will cover all this in one go - I suspect this issue will crop up here and there over time - I'll continue to monitor this and hopefully feedback, collate, revive the thread as necessary. The key question in the end is: How do we structure our models/applications to take into context the broader picture in order to achieve the holy grail of reusability (I'm such an optimist!). Regards Ross _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=3892#3892 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
