Win a copy of JDBC Workbook this week in the JDBC and Relational Databases forum
or A Day in Code in the A Day in Code forum!

Jo Yan

+ Follow
since Sep 05, 2005
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Jo Yan

Thank you both so much for answering my question!

I really appreciate it
Assume I have a session facade --FacadeA which uses EntityBeanA and SLSB

Quesition is: in the component diagram, should I
1. just draw one component as FacadeA and explain the rest in the document or
2. draw 3 different components (FacadeA, EntityBeanA, SLSB)?

If the answer is 2, should I draw all the dependant objects of EntityBeanA as well?

Appreciate your help!!
In the class diagram, there are existing systems like TransMaster, Frequent Flyer Mileage system, Can these be represented as packages in the class diagram?

If not, what will be a good way to represent them?

Thank you in advance!!
I have vouchers for both Part II and III which are going to expire by the end of this month.
Can I schedule the part III test before I submit Part II?
Some members mentioned about getting upload permit, what is it about?

Appreciate your advice.
Thank you for answering my question!

I agree that each architect has their own way. I am just trying to understand from a pure UML point of view.

About your suggestion that all association be bidirectional by default, I remember reading before it is more complex to implement than unidirection association and therefore should be avoid as much as possible. Thoughts on that?
I am studying Mark Cade's class diagram for Golf Equipment Store (page169).
Some of the association seems wrong to me, please help!!

1. Address --> Customer
I would think the arrow should point from customer to Addrss, since customer class should contain (knows about) address, not the other way around. Similarly, the credit card and Order's relationship to customer seems wrong too. (CreditCard * --->1 Customer)

2. Order ---LineItem
In the book, this is a bidirection association. But in real life, shouldn't it be unidirection? Order should be able to query about LineItem, LineItem should not be able to query Order?

Is it possible Mark Cade's class diagram is wrong or I misunderstand it completely?

Thank you for your help in advance!!