I have to call an inventory system through a Web Service. The web service itself is already provided, so I should not have to worry about it. The question is how deep should I go in the modeling?
Here is what i'm thinking. I call an interface InventorySystem. My system would have an implementation of this interface which in turn is responsible for calling the web service. This specific call depends on the way the web service is implemented, so it's out of scope.
That way I would only model my system to the point where I call the methods on the interface. The concrete implementation of this interface doesn't matter.
Now, is that right, or is it better to assume the web service is implemented in EJBs? That way I could easily access them using JAX_WS...
Well, I don't believe I'm getting into much detail about the project.
I'm sorry if I didn't make myself clear, but my question is not about implementation/architecture. I'm just asking how deep I should go in my sequence diagrams, class diagrams etc.
You see, in my assignement it's said the company already has an inventory system which is accessed through web services. The assignement just doesn't say how the system can be accessed.
Just rephrasing myself: In the cases where the assignement doesn't specify things, what should we do?
1 - Should I assume the web service is implemented in some specific way and model that into my diagrams?
2 - Should I ignore how the web service is implemented and just put an interface in my diagrams. The concrete implementation wouldn't matter to the assignement.
Do we assume something or do we ignore? I'm asking because this happens a lot in these assignements...
author and jackaroo
Your diagrams should have an interface which has methods you assume the Inventory System interface has. E.g. you have a InventorySystemManager with a method getComponentById(ID). You assume that imlementation connects to the systems webservice interface and runs some other method.