Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Failed in component diagram

 
binu alex
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi

I failed in component diagram .and working on the resubmission .i have got the comments as "confusion between layers and tiers and no demarcations". Are there any good samples for component diagram ?
 
Ganesh Gopalakrishnan
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There are two ways you can represent your component diagram, viz
[1] Have one component diagram per use case, so it will be 3 or 4 depending on number of use cases(Refer worked out example in Mark Cade and Simon ).
[2] One component diagram for all usecases ( Refer chapter 9 of Cade and Sheil book ).

In fact, I have done both versions in my assignment.

Bottomline, does not matter whether you use 1 or 2 or both in the above, you should clearly seggregate the Tiers/Layers, if you use color for your diagram, then clearly state color coding explanation ( suggestion by cade and sheil in chapter 9).
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic