|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Class diagram confusion!!
Hello all,
Couldnt find a forum that deals with uml so forgive me for posting it here. Was wondering if i should include my application screens in my class diagram or should i leave them out.My understanding is that you put anything you create an object of in the class diagram?? Is this correct?? Thanks for your help in advance bigcon |
|
#2
|
||||
|
||||
|
UML is usually considered to be part of the design process for an application. Moved from the Lounge.
__________________
~~ Peter ~~ ( My Blog: It's exactly like normal nerdiness, but completely different. ) :: ( Supporter of the EFF & FSF ) :: ( I'm a GNU/Linux addict and Free Software Advocate. ) :: ( How to Ask Questions the Smart Way ) :: ( The Fedora Project, sponsored by Red Hat ) :: ( GNOME: The Free Software Desktop Project ) :: ( GnuPG Public Key ) |
|
#3
|
||||
|
||||
|
Quote:
I consider the user interface documentation to be a part of the Use Case process, or an adjunct to it. You can certainly include the UML for your View components in your UML; however, the view designs themselves are more the providence of the requirements than the architectural design specification. Hope that makes sense.
__________________
Give a person code, and they'll hack for a day; Teach them how to code, and they'll hack forever. Analyze twice; hack once. The world's first existential ITIL question: If a change is released into production without a ticket to track it, was it actually released? About DrGroove: ITIL-Certified IT Process Engineer - Enterprise Application Architect - Freelance IT Journalist - Devshed Moderator - Funk Bassist Extraordinaire |
![]() |
| Viewing: Dev Shed Forums > Programming Languages - More > Software Design > Class diagram confusion!! |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|