I would put all of them into the class diagram. Why wouldn't you? It's a diagram of all your classes?
The point of things like sequence diagrams, and class diagrams is for you to work out the finer points of the software design before you develop it. It kind of defeats the purpose of the whole process if you leave it at a higher level. Diagrams such as component, and/or package diagrams are more appropriate for a higher level design. Hope that helps, Mark On 5/25/05, Barry Beattie <[EMAIL PROTECTED]> wrote: > bloody good question, I'd be interested in this as well > > I'd guess that it'd be at a more higher level and you'd only start seeing > Bean/DAO/Gateway stuff in state and sequence diagrams (but hell, what would I > know?) > > cheers > b -- E: [EMAIL PROTECTED] W: www.compoundtheory.com ICQ: 3094740 --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
