Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Architectural Class Diagram Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Architectural Class Diagram" Watch "Architectural Class Diagram" New topic

Architectural Class Diagram

Brian Smith
Ranch Hand

Joined: Oct 26, 2002
Posts: 232
What's your opinion here:

1. Should Class Diagram have ONLY business domain classes or other classes like Business Delegate, Business Facade, ServiceLocater, other helper classes etc?

2. What level of details should the classes have as far as attributes and methods are concerned? should datatype of attributes be shown? should signature of the methods be shown? I know, the Exam instruction does say that we do not have to show everything. but should we not show at least all the methods that are used in sequence diagram to realize the use case?

Darya Akbari
Ranch Hand

Joined: Aug 21, 2004
Posts: 1855
Hi Brian,

look at Mark Cade's class diagram in his SCEA Study Guide. He uses Service classes to access his domain objects. Hence I think adding classes like BD, SF etc. should be fine.


Ara Tatous

Joined: Jul 11, 2005
Posts: 16
I think those classes should appear in component diagram and not in the class diagram. Mark Cade didn't show them in his Class Diagram. But he showed them in his component diagram.
Darya Akbari
Ranch Hand

Joined: Aug 21, 2004
Posts: 1855
Look at Figure 8-6, there you will find the class diagram where the Service classes are included.

Alex Li

Joined: Sep 24, 2006
Posts: 13

I think I can give you some advice as I just certified to be SCEA recently.

For the class diagram, only domain classes and service classes (which I modelled as session bean) are sufficed. To get a higher mark in this section, remember to scan through the requirement carefully and include those domain/service classes stated and have their relationships clearly be represented. No attributes and methods are defined for me (which is not the scope of arch. design).

For the component diagram, you may follow some J2EE arch. documented in Sun (actually some classic components like service locator, business delegate, session facade... are sufficed). You can divide the diagrams based on the use cases stated (auth/enquiry/reservation/payment etc..).
Usually, I would draw a general component diagram to state out the overall design and all the components used first, and then list out the specific component diagrams (for different use cases).

For the sequence diagram, include the basic flows as well as some IMPORTANT alternative flows. It is not difficult to get full marks in this section if you have included all necessary sequence flows in this part.

I agree. Here's the link:
subject: Architectural Class Diagram
jQuery in Action, 3rd edition