(responding to Pablo Schor)
I don't recall anyone responding to this, so I'll attempt to do so. > How come in robustness analysis and interaction diagrams > you define kind of classes as if it were presentation, bs logic > and data access? That's not design, that's analysis. AFAICS, the Robustness Analysis starts from the situation as it exists in the Business before the development of the proposed new system. As such, there will already be some mechanism for doing what we want the system to do. Naturally, this will include some presentation aspects and some data storage aspects (these may be paper forms and filing cabinets...). In the system to be developed, there will be requirements related to presentation and possibly to data storage (e.g. interfacing to existing database). For these reasons, at least, (possibly for other reasons) the ideas of presentation and data storage may need to appear prior to design. Design deals with making those decisions that remain to be made, including any with respect to presentation and data storage that are not already made in the form of requirements and constraints. HTH, Paul Oldfield any opinions expressed herein are not necessarily those of Mentors of Cally ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * 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 *************************************************************************
