Win a copy of Programmer's Guide to Java SE 8 Oracle Certified Associate (OCA) this week in the OCAJP forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Part II Component Diagram

 
Chennakrishna R Gottam
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am in the process of implementing component diagram, to start with two approaches are in my mind.

Both are Mark Cade and Humphrey Sheil implementations by grouping tiers..

1. Defining components use case specific.
2. Defining components business specific like admin actions are in one component segment, user actions are in one component segment

Please advice.
 
kunal Singh Rathor
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
For component diagram, just follow Mark Cade example. Don't go by use case wise, go by layer wise. It should be application specific. Component is basically the different component of your designed application.
 
Paul Balm
Ranch Hand
Posts: 63
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Reading the question a couple times over, I think that Chennakrishna is planning on organization the components in layers/tiers, but the question is whether within each layer, to create use-case specific components or to group them more by common functionality.

There probably is no right or wrong here, as long as you can justify your decision. It depends on the specifics of your assignment (but you can't discuss that here). I think an important question is, what's the simplest solution? Does it have any important disadvantages? And so on.

Also, you can consider having more use-case specific components in the top tier (presentation), with components becoming more generic as you go down to the integration/persistence tier.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic