Hello AndroMDA Forum
In a narrow definition, I'm trying to assess the limitations of Magic Draw's 'modules'. In a wider definition you might say I am trying to assess the state of the art of OSS-style distributed MDA development. I would like to be able to offer OSS participation in a large scale business process re-engineering system done entirely with AndroMDA, but because I'm in the 3rd world, I can't demand or pay for, a Magic Draw Teamwork Server license for every developer involved. At the same time, I can't expect Subversion to manage concurrent changes to a single *.xml.zip file worked on by all developers. I have worked out a tentative 'separation of concerns' structure with a directory layout something like this... <parent dir> ├───mpm_control └───mpm ├───UML # │ └─── mpm_overview.xml.zip └───Source ├───Applications │ ├───Billing │ │ └───src │ │ ├───uml │ │ │ ├───business_layer * │ │ │ │ └─── mpm_app_billing_business_layer.xml.zip │ │ │ └───presentation_layer * │ │ │ └─── mpm_app_billing_presentation_layer.xml.zip │ │ ├───java │ │ │ └───my │ │ │ └───pkg │ │ │ └───mdmq │ │ │ └───mpm │ │ │ └───billing │ │ │ ├───business_layer │ │ │ └───presentation_layer │ │ ├───test-src │ │ └───webapp │ │ └───WEB-INF │ │ ├───lib │ │ ├───jsp │ │ ├───classes │ │ └───mappings │ ├───PriceSetting │ │ └───src │ │ ├───uml │ │ │ ├───business_layer * │ │ │ │ └─── mpm_app_pricesetting_business_layer.xml.zip │ │ │ └───presentation_layer * │ │ │ └─── mpm_app_pricesetting_presentation_layer.xml.zip │ │ ├───test-src │ │ ├───java │ │ └───webapp │ │ └───WEB-INF │ │ ├───lib │ │ ├───jsp │ │ ├───classes │ │ └───mappings │ └───Maintenance │ ├───Inventory_Maint │ │ └───src │ │ ├───java │ │ │ └─── java stuff │ │ ├───uml │ │ │ ├───persistence_layer * │ │ │ │ └─── mpm_maint_inventory_persistence_layer.xml.zip │ │ │ └───business_layer * │ │ │ └─── mpm_maint_inventory_business_layer.xml.zip │ │ ├───test-src │ │ └───webapp │ │ └───WEB-INF │ │ ├───mappings │ │ ├───classes │ │ ├───jsp │ │ └───lib │ └───Person_Maint │ └───src │ ├───java │ │ └─── java stuff │ ├───uml │ │ ├───persistence_layer * │ │ │ └─── mpm_maint_person_persistence_layer.xml.zip │ │ └───business_layer * │ │ └─── mpm_maint_persn_business_layer.xml.zip │ ├───test-src │ └───webapp │ └───WEB-INF │ ├───mappings │ ├───classes │ ├───jsp │ └───lib └───Components ├───Inventory │ └───src │ ├───uml │ │ ├───business_layer * │ │ │ └───mpm_comp_inventory_business_layer.xml.zip │ │ └───persistence_layer * │ │ └───mpm_comp_inventory_persistence_layer.xml.zip │ ├───test-src │ ├───mappings │ └───java └───Person └───src ├───uml │ ├───business_layer * │ │ └───mpm_comp_person_business_layer.xml.zip │ └───persistence_layer * │ └───mpm_comp_person_persistence_layer.xml.zip ├───test-src ├───mappings └───java The line with the hash sign is the global MagicDraw project. The lines with asterisks are the locations of sub-project modules referred to from within the MagicDraw main project. There will be dozens of 'Applications' in addition to <Billing> and <Price Setting>. There will be dozens of business 'Components' in addition to <Inventory> and <Person>. There will be dozens of component 'Maintenance Applications' in addition to <Inventory Maintenance> and <Person Maintenance>. Applications have presentation and business layers. Components have persistence and business layers. I want to Open Source all but the central parent module and to be able then to define modules, for parcelling out to individual remote developers, which contain everything they require to model and build their work package, but all read-only except the bit each developer should work on. I can't see an easy way to do it! I can't give out a full copy of the main *.xml.zip to every developer. Nor, can I see a controllable way to include all dependencies in each developer's package For example, should I include andromda_profile_3.0.xml.zip in every sub-project? What do I do in the event of a new release? Do I have to include explicitly and manually in each sub-module, all its dependencies? Am I correct in believing that sub-projects are the narrowest permitted granularity; i.e, no sub-sub-projects or sub-sub-sub-projects? Is there a known solution to this? Thanks in advance. -- Regards, Hasan _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=398#398 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
