Distributed Stock distribution system (assignment)
in [OOP]
|
From: Mikle on 2 Nov 2007 15:49 I have to design a distributed stock distribution system for a nation- wide franchise.. so basically.. there's an HQ ..providing a couple of remote methods to outlet systems...allowing them to order equipment, stock etc Now my question is ..would it make sense to have some kind of trust between the HQ and the outlet.. where the HQ doesn't care about the individual users who access the methods.. The way I see it.. its up to the outlet systems.. to decide who can place orders or check the outstanding balance...the HQ should only bother to make sure that the system for Outlet A can make orders for Outlet A... right? maybe i'm just being lazy..but it really doesn't sound practical to have the HQ system manage all the outlet users.... the assignment specifies that outlets "run their own software"
From: H. S. Lahman on 5 Nov 2007 13:17 Responding to Mikle... > I have to design a distributed stock distribution system for a nation- > wide franchise.. so basically.. there's an HQ ..providing a couple of > remote methods to outlet systems...allowing them to order equipment, > stock etc > > Now my question is ..would it make sense to have some kind of trust > between the HQ and the outlet.. where the HQ doesn't care about the > individual users who access the methods.. Assuming this is pure stock distribution and the HQ is managing a central inventory facility, then I agree the HQ doesn't need to know anything about who the end users of the stock are. From the HQ's perspective the outlet is its user and the HQ just honors the requests for stock (or behaves gracefully if it can't). However, the last clause bothers me. Nobody should know about HQ's methods. It is a service for the outlet clients and should be encapsulated behind an interface that hides its implementation. IOW, decoupling is a two-way street and the outlet clients shouldn't know any more about how HQ does its thing than HQ knows about how outlets handle individual customers. > > The way I see it.. its up to the outlet systems.. to decide who can > place orders or check the outstanding balance...the HQ should only > bother to make sure that the system for Outlet A can make orders for > Outlet A... right? I think that is handled in the outlet identity associated with the interface message. When outlet A asks for stock, HQ sends stock to outlet A. ************* There is nothing wrong with me that could not be cured by a capful of Drano. H. S. Lahman hsl(a)pathfindermda.com Pathfinder Solutions http://www.pathfindermda.com blog: http://pathfinderpeople.blogs.com/hslahman "Model-Based Translation: The Next Step in Agile Development". Email info(a)pathfindermda.com for your copy. Pathfinder is hiring: http://www.pathfindermda.com/about_us/careers_pos3.php. (888)OOA-PATH
|
Pages: 1 Prev: Looking for a pattern Next: UML unified modeling process |