This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Do we have to list the fields for Entity classes in class diagram. One of my friend have and the other have not. And I could not come to a clear understanding about the mutiplicity of a particular enity called 'Holding' in 'Retire Early' assignment. I have even explore the real world domain. No one is sure about this entity. Does anybody know what this 'Holding' entity means in trading account.
when you really want something, all the universe always conspires in your favour.<br /> <br />SCJP1.5-77%<br />SCWCD-89%
Anyway, I did a little research on the field, but this term does not appear to be a standard term in the business. My conclusion is that it could represent the assets an user can have. Actually later on is never referred by any of the use-case which speaks only of Assets. Therefore my conclusion. Hope it is right.
I just started to make some understanding of BDM and as per my understanding Holding means you "hold" X no. of shares of Y company. So in a portfolio, each row mentioning stock code, stock name and quantity is termed 1 holding.
But i think there is definitely something wrong in terms of multiplicity in BDM, 1 Order can only have 1 stock(hence should be many-to-one) and 1 stock cannot be in multiple Holdings, suppose you already hold 10 shares of company Y, if you purchase again 10 shares of same company Y, then in the portfolio, company Y will be displayed only 1 time having quantity as 20 shares (hence multiplicity should be one-to-one).
Let me know if you have some other thoughts on this.
I hope i am not crossing limits on discussing BDM, otherwise moderators are welcome to edit the part crossing the limit.
I have the same asssignment as well. The explanantion for holding given above seems to be correct in my opinion. I am wondering though if we should really depict JSF pages in the class model (with <<jsf>> stereotype). I've never seen this done in the real world and jsf pages are not classes and so logically shouldnt be part of class diagram. any thoughts?
I have the same question to whether keep the JSP's/JSF's in the class diagram or not. Even in the Mark Cades worked out solution he put the jsp's in the class digram.
Any thoughts would be greately helpful.
Jesson Joy wrote:I have the same asssignment as well. The explanantion for holding given above seems to be correct in my opinion. I am wondering though if we should really depict JSF pages in the class model (with <<jsf>> stereotype). I've never seen this done in the real world and jsf pages are not classes and so logically shouldnt be part of class diagram. any thoughts?
I had a little moral dilemma on this one. In the real world I would never put JSP/JSF in the class diagram. However Cade had it and it seemed important from reading prior posts so I winced and then included it.