Thanks James, that clears things up for me somewhat. I do agree that some of this modelling should be open and high-level. In my experience, getting too specific too soon only spells trouble once the business people change their minds (or make a decision, whatever!).
- Mat -----Original Message----- From: Murphy, James [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 30, 2002 12:43 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Enterprise Architect - Visio Modelling > I installed VSEA today as well as Visio. I'm somewhat new to > formal architectural diagrams but I believe that I understand > the fundamentals quite well. Where I'm having some confusion > is with regards to the transition between a "Use Case" and a > "Static Structure". If you figure out how to do this I'm sure the fine Folks at Rational would love to hear from you! :) Honestly this is the "wet: part of the process. You can think of Use Cases as human description of program functionality. It is somewhat informal - for a reason. To not impose structure at the functional description time. Its the job of the software engineer to come up with a design that meets the functionality described in the Use Cases. > Is this true? Otherwise I don't understand the point behind > drilling down to such detail in a Use Case... You might be right! At least the folks doing agile development [1] would agree with that. "How much is enough design" is a deep software engineering question - with no right answers. Jim [1] - http://www.xprogramming.com/ You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
