It's not a secret anymore!
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes SCEA Part II, UML Doubt 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 "SCEA Part II, UML Doubt" Watch "SCEA Part II, UML Doubt" New topic

SCEA Part II, UML Doubt

Balaji Ravindran

Joined: Aug 16, 2006
Posts: 7

First thank you all for making this place such a nice place for SCEA, I completed part 1 with 93% , this forum was my starting place for the prep, I had downloaded part 2 and I have a doubt in the same.

Assuming I have an object called Account, and a Customer that has to be linked to this account. A customer can be Primary Account holder, Secondary Account holder or even a proxy.

The issue I face here is,
Initially I thought of having a Customer Object and creating a 1 to * relation with Account , but then uml does not clearly state the complete requirement, also I am not sure if I should create individual objects for Primary Account holder, or a Proxy in UML as a Proxy can be Primary Account holder for a different account. Please help me with your ideas on how a UML can be drawn for this requirement

Considering the policy of this forum, I am not quoting actual exam content , but framing my question using a different object model.

Thank you
Joseph A Alexander

Joined: Oct 31, 2003
Posts: 23
I am not sure on your business requirements. Based on my understanding....

Account can be an interface/abstract and say Savings, Checking etc are implementations of Accounts.

Now a customer can have more that one account. So you can draw a aggregation relationship of 1...* from Customer to Account [Program to an interface].

Regards,<br />Joe, SCEA
Balaji Ravindran

Joined: Aug 16, 2006
Posts: 7
Hi Joe,

Thank you for your quick Response,

i am not looking for Account to customer straight relationship,

in UML i would like to depict following relation

1. Customer to an account (as a primary holder)
2. Customer to an account (as a secondary holder)
3. Customer to an account (as a Proxy of the account)

hope this is clear.
thank you again

Note: A Primary holder to an account can be a proxy to a different account
Lakshmanan Arunachalam
Ranch Hand

Joined: Nov 02, 2005
Posts: 99
This shows a many to 1 relationship with Customer and Account. i.e An account can have reference to three accountholders differs in roles(Primary, Secondary and Proxy). But from customer perspective I believe there wont be any need to find 'for which account this customer acts as a secondary or proxy holder'.

Based on the above assumption, define a many to one relationship between Customer and Account. And Customer has composition aggregation with Role interface. Define three classes (Primary Holder, Secondary Holder and Proxy) that implements Role interface. Customer class has reference to Role interface (one to one). The operations defined at Customer class should be delegated to Role interface.


Regards<br />Lakshmanan<br />IBM-OOAD & UML, SCEA-I
I agree. Here's the link:
subject: SCEA Part II, UML Doubt
jQuery in Action, 3rd edition