// Copyright (c) 2009 DMTF. All rights reserved. [Association, Version ( "2.22.0" ), UMLPackagePath ( "CIM::Core::CoreElements" ), Description ( "CIM_OrderedDependency is used to establish a relationship " "between a ManagedElement and its dependencies. Each dependency " "is an Antecedent reference and the order in which the " "dependencies need to be resolved is indicated by the " "AssignedSequence property. \n" "For example, if this association is used to arrange " "dependencies of a software in a hierarchical order, then this " "specifies the sequence in which the dependencies need to be " "installed prior to installing the software." )] class CIM_OrderedDependency : CIM_Dependency { [Description ( "AssignedSequence is an unsigned integer \'n\' that " "indicates the relative order of ManagedElement " "instances. When \'n\' is a positive integer, it " "indicates a place in the sequence of members, with " "smaller integers indicating earlier positions in the " "sequence. The special value \'0\' indicates \'don\'t " "care\'. If two or more members have the same non-zero " "sequence number, then the ordering between those members " "is irrelevant, but they must all be ordered at the " "appropriate place in the overall sequence. \n" "\n" "A series of examples will make ordering of members " "clearer: \n" "If all members have the same sequence number, \n" "regardless of whether it is \'0\' or non-zero, any \n" "order is acceptable. \n" "o The values: \n" "1:MEMBER A \n" "2:MEMBER B \n" "1:MEMBER C \n" "3:MEMBER D \n" "indicate two acceptable orders: A,C,B,D or C,A,B,D, \n" "since A and C can be ordered in either sequence, but \n" "only at the \'1\' position. \n" "\n" "Note that the non-zero sequence numbers need not start " "with \'1\', and they need not be consecutive. All that " "matters is their relative magnitude." )] uint64 AssignedSequence; };