I find that the use case editor draws very pretty DFDs and you can use the actors to represent external systems on a context diagram quite nicely.
Rose does not allow you to you to attach STDs to use case diagrams, which is a pity, but I'm sure you could fiddle this by perhaps using a use case to represent a DFD and attching the STD to that. BTW, you don't say it explicitely, but I'm assuming that your legacy code is structured. Les. > > > > I need to produce system documentation of an existing non-OO > > system, and I > > am not sure whether I should use Rose (and UML) for this. > > I can see that I can use use case diagrams and activity diagrams > > on a high > > level, but would it make sense to use classes and objects (in class > > diagrams and sequence diagrams) to document existing procedural code? > > > > I would really appreciate your comments > > ________________________________________________ Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * Only plain-text messages are supported. * HTML or Rich-Text messages may be rejected. * * Post or Reply to: [EMAIL PROTECTED] * Subscription Requests: [EMAIL PROTECTED] * Archive of messages: * http://www.rational.com/support/usergroups/rose/rose_forum.jsp * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * To: [EMAIL PROTECTED] * Subject: <BLANK> * Body: unsubscribe rose_forum *************************************************************************
