Have to agree with Woulter - after all he is the guru (not forgetting Chad :-))
Time is not the only factor. I like the fact you have chosen a timesheet system - who hasn't implemented one ... maybe Excel is the answer :-(. Big orgs - 40-70% functionality delivered by ERP - rest by in house apps - overall a sphagetti mess - everywhere I go the same. J2EE skills hard to come by - VB script jockeys / cut and paste code (sorry - I have to get off my soap box). Business want faster, cheaper, better. AndroMDA will save time - no doubt - just look at the code generated. But there is more: 1. Development of deep domain knowledge - read Domain Driven Design by Evens - mega benefits in the long term. There is no such thing as a quick and dirty app. They just hang around and and get more complex. AndroMDA provides just the right level of abstraction and practicality for DDD. The model becomes the code! 2. Application of "best practice" architectural patterns. Not only a clean separation at the PIM level i.e. Entity/Service/... stereotypes - but a good application of design patterns using Struts/Spring/Hibernate/EJB. Gives you a consistency across all developers - believe me - not a bad thing. Much more - try and decide for yourself _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=3795#3795 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
