Requires one or the Other Class UML
This customer needs to have one payment account.
I'm not sure whether it works to have customer having one inherited class. These are my two ideas:
Without Inheritance:
With Inheritance:
uml papyrus
edited Nov 17 '18 at 8:16
Thomas Kilian
23.8k63764
asked Nov 14 '18 at 16:01
C FinnC Finn
115
add a comment |
This customer needs to have one payment account.
I'm not sure whether it works to have customer having one inherited class. These are my two ideas:
Without Inheritance:
With Inheritance:
uml papyrus
edited Nov 17 '18 at 8:16
Thomas Kilian
23.8k63764
asked Nov 14 '18 at 16:01
C FinnC Finn
115
2
First of all, I guess that you inversed the images... With Inheritance seems more clear even if PaymentAccount could be abstract.
– Red Beard
Nov 14 '18 at 16:37
Both are clear, but having the superclass know how to pull money seems better than having the Customer (and possibly other classes) know how.
– Jim L.
Nov 14 '18 at 17:38
add a comment |
This customer needs to have one payment account.
I'm not sure whether it works to have customer having one inherited class. These are my two ideas:
Without Inheritance:
With Inheritance:
uml papyrus
edited Nov 17 '18 at 8:16
Thomas Kilian
23.8k63764
asked Nov 14 '18 at 16:01
C FinnC Finn
115
This customer needs to have one payment account.
I'm not sure whether it works to have customer having one inherited class. These are my two ideas:
Without Inheritance:
With Inheritance:
uml papyrus
uml papyrus
edited Nov 17 '18 at 8:16
Thomas Kilian
23.8k63764
asked Nov 14 '18 at 16:01
C FinnC Finn
115
edited Nov 17 '18 at 8:16
Thomas Kilian
23.8k63764
asked Nov 14 '18 at 16:01
C FinnC Finn
115
edited Nov 17 '18 at 8:16
Thomas Kilian
23.8k63764
edited Nov 17 '18 at 8:16
Thomas Kilian
23.8k63764
edited Nov 17 '18 at 8:16
Thomas Kilian
23.8k63764
23.8k63764
asked Nov 14 '18 at 16:01
C FinnC Finn
115
asked Nov 14 '18 at 16:01
C FinnC Finn
115
asked Nov 14 '18 at 16:01
C FinnC Finn
115
115
2
First of all, I guess that you inversed the images... With Inheritance seems more clear even if PaymentAccount could be abstract.
– Red Beard
Nov 14 '18 at 16:37
Both are clear, but having the superclass know how to pull money seems better than having the Customer (and possibly other classes) know how.
– Jim L.
Nov 14 '18 at 17:38
add a comment |
2
First of all, I guess that you inversed the images... With Inheritance seems more clear even if PaymentAccount could be abstract.
– Red Beard
Nov 14 '18 at 16:37
Both are clear, but having the superclass know how to pull money seems better than having the Customer (and possibly other classes) know how.
– Jim L.
Nov 14 '18 at 17:38
2
2
First of all, I guess that you inversed the images... With Inheritance seems more clear even if PaymentAccount could be abstract.
– Red Beard
Nov 14 '18 at 16:37
First of all, I guess that you inversed the images... With Inheritance seems more clear even if PaymentAccount could be abstract.
– Red Beard
Nov 14 '18 at 16:37
Both are clear, but having the superclass know how to pull money seems better than having the Customer (and possibly other classes) know how.
– Jim L.
Nov 14 '18 at 17:38
Both are clear, but having the superclass know how to pull money seems better than having the Customer (and possibly other classes) know how.
– Jim L.
Nov 14 '18 at 17:38
add a comment |
1 Answer
1
active
oldest
votes
In the model without inheritance, a customer could have both a bank account and a credit card. You could add an --xor-- constraint between the associations if a customer can only have either one.
The diagram with inheritance clearly shows that a customer cannot have both a bank account and a credit card. But it also demands that each customer has an account. If there are customers without any account, then you should replace multiplicity "1" by "0..1".
answered Nov 14 '18 at 19:29
www.admiraalit.nlwww.admiraalit.nl
2,208715
Brilliant, thank you.
– C Finn
Nov 15 '18 at 21:18
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53304259%2frequires-one-or-the-other-class-uml%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In the model without inheritance, a customer could have both a bank account and a credit card. You could add an --xor-- constraint between the associations if a customer can only have either one.
The diagram with inheritance clearly shows that a customer cannot have both a bank account and a credit card. But it also demands that each customer has an account. If there are customers without any account, then you should replace multiplicity "1" by "0..1".
answered Nov 14 '18 at 19:29
www.admiraalit.nlwww.admiraalit.nl
2,208715
Brilliant, thank you.
– C Finn
Nov 15 '18 at 21:18
add a comment |
In the model without inheritance, a customer could have both a bank account and a credit card. You could add an --xor-- constraint between the associations if a customer can only have either one.
The diagram with inheritance clearly shows that a customer cannot have both a bank account and a credit card. But it also demands that each customer has an account. If there are customers without any account, then you should replace multiplicity "1" by "0..1".
answered Nov 14 '18 at 19:29
www.admiraalit.nlwww.admiraalit.nl
2,208715
Brilliant, thank you.
– C Finn
Nov 15 '18 at 21:18
add a comment |
In the model without inheritance, a customer could have both a bank account and a credit card. You could add an --xor-- constraint between the associations if a customer can only have either one.
The diagram with inheritance clearly shows that a customer cannot have both a bank account and a credit card. But it also demands that each customer has an account. If there are customers without any account, then you should replace multiplicity "1" by "0..1".
answered Nov 14 '18 at 19:29
www.admiraalit.nlwww.admiraalit.nl
2,208715
In the model without inheritance, a customer could have both a bank account and a credit card. You could add an --xor-- constraint between the associations if a customer can only have either one.
The diagram with inheritance clearly shows that a customer cannot have both a bank account and a credit card. But it also demands that each customer has an account. If there are customers without any account, then you should replace multiplicity "1" by "0..1".
answered Nov 14 '18 at 19:29
www.admiraalit.nlwww.admiraalit.nl
2,208715
answered Nov 14 '18 at 19:29
www.admiraalit.nlwww.admiraalit.nl
2,208715
answered Nov 14 '18 at 19:29
www.admiraalit.nlwww.admiraalit.nl
2,208715
answered Nov 14 '18 at 19:29
www.admiraalit.nlwww.admiraalit.nl
2,208715
2,208715
Brilliant, thank you.
– C Finn
Nov 15 '18 at 21:18
add a comment |
Brilliant, thank you.
– C Finn
Nov 15 '18 at 21:18
Brilliant, thank you.
– C Finn
Nov 15 '18 at 21:18
Brilliant, thank you.
– C Finn
Nov 15 '18 at 21:18
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53304259%2frequires-one-or-the-other-class-uml%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
First of all, I guess that you inversed the images... With Inheritance seems more clear even if PaymentAccount could be abstract.
– Red Beard
Nov 14 '18 at 16:37
Both are clear, but having the superclass know how to pull money seems better than having the Customer (and possibly other classes) know how.
– Jim L.
Nov 14 '18 at 17:38