This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
It its very important that my SuD interact with external system to accomplish its core business. However it is not given as part of the use case neither hinted anywhere about its possible existene in the system. Now what would we want me to do in this case. consider something like a trading application without the existence of exchange external interface. either design around the assumption that the external system exists and use it in my design or i dont show it at all in my design
when you really want something, all the universe always conspires in your favour.<br /> <br />SCJP1.5-77%<br />SCWCD-89%
Jeanne Boyarsky wrote:Your design should show the last point you control that calls the external system. For example a facade or adapter or...
I wound up listing a whole bunch of assumptions about the external system in my assumptions section.
I have the same dilemma as Senthil, further questions from my side on this:
Communication with this external system has to be Synchronous in some cases and asynchronous in other cases, Since this is an external system without any mention we can't assume its a Java system (and provides a JMS queue for asynch communication), so we have to go with asynch WS calls.
Now to support asynch WS i need to add 2-3 components in all diagrams and make some domain changes, Do you think its better to show these detailed changes for this external system or we can just go with assumptions list mentioning all these (given that its very imp. external system i.e. stock exchange for a trading system, without this asynch WS, requirements are not fully achieved).