I'm looking for war stories and advice on how best to use Rose 2000e on a reasonable size project. Putting a bit of flesh on that - consider a couple of dozen developers working on a C++/ATL/COM product. Multiple DLLs and exe's, dependencies on COM interfaces defined in other components and framework code defined in yet other components. API documentation is derived from the Rose model via homebrew scripts. The target is to be able to forward and reverse engineer the code, to have access to APIs in other components, to be able to check access violations etc across the whole model. So - how do you organise the Rose model(s)? Our first cut was to have one models for the system. This falls down because, in order to reverse engineer you need the mdl file checked out. But Fred round the corner has that at the moment. So you go for lots of little models. You now need a manual step to pull in the APIs from all those other models. So how have people got round this one. I suppose I'm looking for "Large Scale Rose Design" as a companion volume to Lakos' "Large Scale C++ Design"! Thoughts? ---------- Giles Chamberlin Ridgeway Systems & Software ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Admin.Subscription Requests: [EMAIL PROTECTED] * Archive of messages: http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * * To: [EMAIL PROTECTED] * Subject:<BLANK> * Body: unsubscribe rose_forum * *************************************************************************
