• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Required external system, but not part of the given assignment

 
Ranch Hand
Posts: 264
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
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
 
author & internet detective
Posts: 41860
908
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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).
 
Note to self: don't get into a fist fight with a cactus. Command this tiny ad to do it:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic