This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes OO, Patterns, UML and Refactoring and the fly likes When should we draw the package/component and deployment diagram ? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "When should we draw the package/component and deployment diagram ?" Watch "When should we draw the package/component and deployment diagram ?" New topic
Author

When should we draw the package/component and deployment diagram ?

Kodo Tan
Ranch Hand

Joined: Aug 14, 2001
Posts: 105
Hello all
Need to seek you guys comments on when should we draw the package/component and deployment diagrams while doing OOAD with UML.
I thinking of the following:
(1) After settle down with the use case specifications, draw the high level package and deployment diagram first before proceeding to the conceptual modelling with class diagrams and sequence diagrams.
(2) While we refine the class/sequence diagrams through each iteration, update the package and deployment diagrams where applicable and useful to do that.
(3) Once we finalised everything draw the component diagram, finalised the package diagram before distributing to all developers for construction.
What do you guys think ?
Pho Tek
Ranch Hand

Joined: Nov 05, 2000
Posts: 761

(1) After settle down with the use case specifications, draw the high level package and deployment diagram first before proceeding to the conceptual modelling with class diagrams and sequence diagrams.

The package diagram is used mainly to organize the static class diagram when it gets too cluttered. So I'd say you would work with it only when you have some candidate objects (read classes) to work with. My advise: start creating your package diagrams after you have the first draft of your class diagram (with some behavior).
Deployment diagrams are "useful primarily for marketing presentations, executive summaries, and pointy-haired bosses." (Allen Holub)
(3) Once we finalised everything draw the component diagram, finalised the package diagram before distributing to all developers for construction.

It is only viable to treat packages as a development units - when the packages are self-contained and do not have many dependencies with other packages.
Pho


Regards,

Pho
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: When should we draw the package/component and deployment diagram ?
 
Similar Threads
... will result in immediate failure!!!
uml sequence, component & deployment diagram questions.
The order of drawing seq. and component diag.?
Passed scea part II/III with 100%
Future of UML with OO Concepts