"Freight Movers has a proprietary Java API for sending shipping requests. International Shippers uses a web service to accept shipping requests."
I can not correlate the relationships here. We should be worried about only one interface right? Either Big Smoke will be sending the shipping request directly to International Shippers using web service or Big smoke will contact Freight Movers(how? is our assumption say JMS), and they will send to International shippers. "proprietary Java API for sending shipping requests" confuses me a lot. Big smoke Architect should not worry about how Freight Movers and International shippers communicate rt?
proprietary Java API means that Freight Movers has exposed some interface which can be accessed by any Java client via TCP/IP (RMI, IIOP, HTTP, SOAP etc...). In other words-one can assume that Freight Movers shipping API can be accessed via Java client using RMI or whatever you think is appropriate. In fact it could be SOAP Webservices or REST WS.
Big Smokes Architect has to worry about it as it's one of the interfacing system.
"Freight Movers has a proprietary Java API for sending shipping requests." Then It should have written "Freight Movers has a proprietary Java API for accepting shipping requests." rt?
Big Smoke is sending and Freight Movers are accepting rt? ( In the case of International Shippers it is written "accepting")
There will be two mechanisms available for shipping ( ie,one for local shipping other for international). that make perfect sense, the only thing I am confused is the word "Sending".
Joined: Apr 06, 2001
Please read it as accepting. You are right. They should be consistent but may be this is the way they want to test us-who know?
These assignments are not 100% perfect and you don't have the luxury of getting clarifications from Business Users or Business Analysts and that's why if you come across any thing that could have some other meaning-it's time to make an assumption and more importantly document it.