Help coderanch get a
new server
by contributing to the fundraiser
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

SCEA Part II, UML Doubt

 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

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
 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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].
 
Balaji Ravindran
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
Ranch Hand
Posts: 99
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
Lakshmanan
 
I can't beleive you just said that. Now I need to calm down with this tiny ad:
We need your help - Coderanch server fundraiser
https://coderanch.com/t/782867/Coderanch-server-fundraiser
reply
    Bookmark Topic Watch Topic
  • New Topic