• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

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

 
Ranch Hand
Posts: 105
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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 ?
 
Ranch Hand
Posts: 782
Python Chrome Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

(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
 
reply
    Bookmark Topic Watch Topic
  • New Topic