This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Part II Component Diagram Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Part II Component Diagram" Watch "Part II Component Diagram" New topic

Part II Component Diagram

Chennakrishna R Gottam

Joined: Jan 05, 2012
Posts: 8
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

Joined: Nov 07, 2011
Posts: 8
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

Joined: Dec 13, 2008
Posts: 63
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.

SCJP 1.4 -- SCJD Java 2 -- OCM JEA 5
I agree. Here's the link:
subject: Part II Component Diagram