Figure LR.07 - Relationship between Product, Service and Resource

This leads to an important conclusion: a ProductComponent is directly related to a CustomerFacingService (i.e. Know-how), since the CustomerFacingService is directly visible as a part of the Product. <br/>However, a ResourceFacingService (i.e. Technical Solution) is hidden from the Product, since it represents the logic that implements the CustomerFacingService. <br/>This understanding now enables us to connect ResourceFacingService to PhysicalResource and LogicalResource, as shown in Figure below. <br/>A PhysicalResource might host one or many RFSs. <br/>A LogicalResource might implement one or many RFSs.<br/>The model in the following Figure shows that a CustomerFacingService might be composed of multiple ResourceFacingServices. Each ResourceFacingService might be configured using a set of LogicalResources as well as a set of PhysicalResources.<br/>This follows our original logic, in that a Product requires a set of ResourceFacingServices to support it. <br/>Since a PhysicalResource might host LogicalResources (via the ResourceRelationship with a type “host”); we can identify the specific PhysicalResource(s) that are required to support a particular LogicalResource.<br/>Here is an example to illustrate these relationships, based on the following Figure. <br/>Consider a Customer (a type of PartyRole) that wants to buy broadband Internet service from a Service Provider. The Customer needs to buy a new cable modem to connect to the Service Provider. In this example:<br/>        • The Cable Modem is a Product that the Customer buys; the Cable Modem is also a PhysicalResource. This is represented by the ProductHasPhysicalResources relationship.<br/>        • Broadband Internet is a Product that the Customer buys; Broadband Internet is also a CustomerFacingService. This is represented by the ProductRealizedAsCFService relationship.<br/>        • Note that the Broadband Internet Service depends on the Cable Modem:<br/>              • The Broadband Internet CustomerFacingService requires a set of ResourceFacingServices to link to the Cable Modem. These could include, for example, one or more functions performed by one or more Protocols. These are represented by the CFServiceRequiresRFServices relationship.<br/>              • Each ResourceFacingService needs to connect to the Cable Modem. The physical connection will terminate on a physical port of the Cable Modem – this is represented by the ServicePRDependency relationship.<br/>              • The PhysicalPort of the Cable Modem hosts logical functions (e.g., a DeviceInterface). This is represented by the ServicePRDependency relationship.<br/>        • Similarly, the Cable Modem functions are configured to work with the Broadband Internet CustomerFacingService.  Different LogicalResources (e.g., Protocol, LogicalDevice, DeviceInterface, and Software) are required to communicate with and feed the Broadband Internet CustomerFacingService through the Cable Modem to the Customer. These are modeled by the ServiceLRDependency relationship.<br/>