Objects by Design Forums Here you can view your subscribed threads, work with private messages and edit your profile and preferences Registration is free! Calendar Find other members Frequently Asked Questions Search Home  
Objects by Design Forums : Powered by vBulletin version 2.3.5 Objects by Design Forums > Main Forums > UML Certification Review Questions > sequence diagrams 101
  Last Thread   Next Thread
Author
Thread Post New Thread    Post A Reply
SZ
Administrator

Registered: Apr 2001
Location: New York
Posts: 492

sequence diagrams 101

Here is a nice simple question on sequence diagrams:

44) Refer to the exhibits to answer the question.

What are the names of missing classes XXX and YYY in the sequence diagram?

a) XXX = DeliverySchedule, YYY = Supplier

b) XXX = Supplier, YYY = DeliverySchedule

c) XXX = PreferredSupplier, YYY = DeliverySchedule

d) XXX = DeliverySchedule, XXX = PreferredSupplier


Single Select - Please select the best answer (one and only one choice must be selected).

++++++++++++++++++

If you look at the class diagram (attached) you can see that InventoryProduct has an association with Supplier. Therefore, the proper class for XXX is Supplier. The same rule of visibility applies to Supplier and DeliverySchedule so that the class for YYY is DeliverySchedule.

So what's wrong with this relatively simple example? In particular I find it odd that Product is not listed as a class on the class diagram, especially since it figures into the solution so directly. I don't think that they meant InventoryProduct because the signature for the nextDeliveryFor methods is pretty specific about giving the parameter type as Product.

Also, a minor issue is that Purchasable seems like it should have been an interface, especially since a realization association is used. The example uses a class instead of an interface, which would be more accurate.

Attachment: ibmstore.gif
This has been downloaded 2449 time(s).

Report this post to a moderator | IP: Logged

Old Post 03-20-2002 04:16 AM
SZ is offline Click Here to See the Profile for SZ Click here to Send SZ a Private Message Visit SZ's homepage! Find more posts by SZ Add SZ to your buddy list Edit/Delete Message Reply w/Quote
homeyz63
Junior Member

Registered: Jul 2001
Location:
Posts: 2

I agree with you that the answer should be (B).
But I would like to pose another question to the
forum, and this applies to your statement about
why the Product Class is not shown on the class
diagram. The question would be if we had to modify
the class diagram to show the Product class where
would it go? I believe the naming of the Purchasable
class could be an error and should have been defined
as a <<interface>> Product. If not, what other alternatives
will work or a determination cannot be made because of
insufficient information.
What do you think.

Report this post to a moderator | IP: Logged

Old Post 03-20-2002 02:02 PM
homeyz63 is offline Click Here to See the Profile for homeyz63 Click here to Send homeyz63 a Private Message Find more posts by homeyz63 Add homeyz63 to your buddy list Edit/Delete Message Reply w/Quote
SZ
Administrator

Registered: Apr 2001
Location: New York
Posts: 492

I'm not sure why InventoryProduct isn't simply called Product. That would seem to solve this problem.

You see, a UML class diagram by itself is insufficient. You have to understand the requirements and use cases thoroughly in order to create an abstraction for a Product class, which more specific classes, such as InventoryProduct, could derive.

Lacking this knowledge in the current example, it is far better to keep it simple and just deal with a Product class.

Report this post to a moderator | IP: Logged

Old Post 03-22-2002 04:01 AM
SZ is offline Click Here to See the Profile for SZ Click here to Send SZ a Private Message Visit SZ's homepage! Find more posts by SZ Add SZ to your buddy list Edit/Delete Message Reply w/Quote
All times are GMT. The time now is 03:22 PM. Post New Thread    Post A Reply
  Last Thread   Next Thread
Show Printable Version | Email this Page | Subscribe to this Thread

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 

< Contact Us - Objects by Design >

Powered by: vBulletin Version 2.3.5
Copyright ©2000 - 2018, Jelsoft Enterprises Limited.
Copyright 1999-2005, Objects by Design, Inc.