• 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

Book clears confusions on level of detail?

 
Ranch Hand
Posts: 213
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear Mark & Humphre

There's a lot of confusion among candidates on the level of detail to go to in each diagram.
This is especially true for Component Diagrams. They are overly discussed (won't say hyped!!) in discussion forums.
Does you book guide how detailed component diagrams should be, should each JSP/ENTITY be represented in its own box or just the file names can be listed and what other details are expected by examiners in component diagrams. Similarly, sequence diagrams carry less marks with them but take a lot of time. How much detailed they should be? I hope book clarifies such confusions.

regards
Varun


 
author
Posts: 36
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The book does provide clarity about level of detail expected on the diagrams.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic