1 marek 1.1 // 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_SoftwareElementSAPImplementation 
 6           // ==================================================================
 7              [Association, Version ( "2.6.0" ), 
 8               UMLPackagePath ( "CIM::Application::DeploymentModel" ), 
 9               Description ( 
10                  "An association between a ServiceAccessPoint and how it is "
11                  "implemented by one or more executable SoftwareElements. Note "
12                  "that this association is restricted to \'executable\' "
13                  "Elements. In earlier phases of deployment, the Software "
14                  "FeatureSAPImplementation association is adequate and "
15                  "recommended. \n"
16                  "The relationship between this association and Software "
17                  "FeatureSAPImplementation is more fully described here. "
18                  "SoftwareElementSAPImplementation allows the description of "
19                  "greater granularity than SoftwareFeatureSAPImplementation, "
20                  "when a SoftwareFeature is fully deployed and results in "
21                  "several executable Elements. These Elements may implement "
22 marek 1.1        "several different ServiceAccessPoints. \n"
23                  "Since SoftwareFeatures decompose into SoftwareElements, it is "
24                  "possible to describe how software implements a SAP by using "
25                  "either this association or the SoftwareFeatureSAP "
26                  "Implementation relationship. One or the other should be "
27                  "chosen. Both associations should not be used for a particular "
28                  "AccessPoint, since their information is redundant. \n"
29                  "This relationship is especially important when the "
30                  "SoftwareFeature and Product aspects are not described for a "
31                  "SoftwareElement (ie, when the acquisition and deployment of "
32                  "the software is not detailed). In this case, the Software "
33                  "ElementSAPImplementation association is the only one available "
34                  "to describe how an AccessPoint is implemented in software. "
35                  "Since SoftwareFeatures are not instantiated, it is not "
36                  "possible to use the SoftwareFeatureSAP Implementation "
37                  "association. \n"
38                  "The cardinality of this association is many-to-many. A "
39                  "ServiceAccessPoint may be provided by more than one Software "
40                  "Element. (If this is true, it is assumed that the Software "
41                  "Elements operate in conjunction.) And, any SoftwareElement may "
42                  "provide more than one SAP." )]
43 marek 1.1 class CIM_SoftwareElementSAPImplementation : CIM_Dependency {
44           
45                 [Override ( "Antecedent" ), 
46                  Description ( 
47                     "The executable SoftwareElement implementing the SAP." )]
48              CIM_SoftwareElement REF Antecedent;
49           
50                 [Override ( "Dependent" ), 
51                  Description ( 
52                     "The ServiceAccessPoint implemented by the SoftwareElement."
53                      )]
54              CIM_ServiceAccessPoint REF Dependent;
55           
56           
57           };