Originally posted by Maris Orbidans:
>4. My class diagram did not violate the BDOM and it had around
>25 classes >covered also payment/award travel representations.
Did you display any J2EE specific components ? session beans, service locators, facades ?
Mark's book displays only business objects and some session beans. But I am not sure which would be the best approach.
congrats !
Originally posted by Dan Drillich:
Good Day,
The following link shows the Mediator's UML, pretty much as the GoF book has it - http://www.dofactory.com/Patterns/PatternMediator.aspx.
I wonder whether the following change will be correct:
Removing the association from Colleague to Mediator and making the ConcreteMediator association to ConcreteColleague2 a bi-directional one.
Any thoughts?
Thanks,
Dan
P.S. For the first time for me, I remembered to check the Email Notification feature.
Ajith, is there a way to do it for threads to which we respond?
Originally posted by Ravi Dhanum:
Hello,
In the Change Itinerary and the Pay for Itinerary use cases, the customer is allowed to select a pre-existing itinerary. I have read previous topics which say that these itineraries are unpaid. My question is: how can they be unpaid if during the Prepare Itinerary, the Pay for Itinerary use case is called? The only way I see is that if an error occurred while trying to pay it.
What do you think? I have read and reread the use cases.
Thanks in advance.
Originally posted by Yong How Lim:
Hi Subra,
I just stated in the assumption that I am using Poseidon as the tool and the component diagram will come out abit different. To play safe, I have stereotype all components with "component" stereotype.