1 karl  1.1.2.2 // Copyright (c) 2005 DMTF.  All rights reserved.
 2               // <change cr="ArchCR00066.004" type="add">Add UmlPackagePath
 3               // qualifier values to CIM Schema.</change>
 4               // ==================================================================
 5               //  CIM_SoftwareElementServiceImplementation 
 6               // ==================================================================
 7                  [Association, Version ( "2.6.0" ), 
 8                   UMLPackagePath ( "CIM::Application::DeploymentModel" ), 
 9                   Description ( 
10                      "An association between a Service and how it is implemented by "
11                      "one or more executable SoftwareElements. Note that this "
12                      "association is restricted to \'executable\' Elements. In "
13                      "earlier phases of deployment, the SoftwareFeatureService "
14                      "Implementation association is adequate and recommended. \n"
15                      "The relationship between this association and Software "
16                      "FeatureServiceImplementation is more fully described here. "
17                      "SoftwareElementServiceImplementation allows the description of "
18                      "greater granularity than SoftwareFeatureService "
19                      "Implementation, when a SoftwareFeature is fully deployed and "
20                      "results in several executable Elements. These Elements may "
21                      "implement several different Services. \n"
22 karl  1.1.2.2        "Since SoftwareFeatures decompose into SoftwareElements, it is "
23                      "possible to describe how software implements a Service by "
24                      "using either this association or the SoftwareFeature "
25                      "ServiceImplementation relationship. One or the other should be "
26                      "chosen. Both associations should not be used for a single "
27                      "Service instance, since their information is redundant. \n"
28                      "This relationship is especially important when the "
29                      "SoftwareFeature and Product aspects are not described for a "
30                      "SoftwareElement (ie, when the acquisition and deployment of "
31                      "the software is not detailed). In this case, the Software "
32                      "ElementServiceImplementation association is the only one "
33                      "available to describe how a Service is implemented in "
34                      "software. Since SoftwareFeatures are not instantiated, it is "
35                      "not possible to use the SoftwareFeatureService Implementation "
36                      "association. \n"
37                      "The cardinality of this association is many-to-many. A Service "
38                      "may be provided by more than one SoftwareElement. If this is "
39                      "true, it is assumed that the SoftwareElements operate in "
40                      "conjunction. And, any SoftwareElement may provide more than "
41                      "one Service." )]
42               class CIM_SoftwareElementServiceImplementation : CIM_Dependency {
43 karl  1.1.2.2 
44                     [Override ( "Antecedent" ), 
45                      Description ( 
46                         "The executable SoftwareElement implementing the Service." )]
47                  CIM_SoftwareElement REF Antecedent;
48               
49                     [Override ( "Dependent" ), 
50                      Description ( 
51                         "The Service implemented by the SoftwareElement." )]
52                  CIM_Service REF Dependent;
53               
54               
55               };