The Default Component Profile describes the meta data for packaging components such as J2EE components. xmi:ordered=true property order is (these are role names) 1. model 2. diagram 3. useCase 4. artifact The models, diagrams, artifacts, and so on within this class are intended to describe the requirements that the component proposes to fulfill. xmi:ordered=true property order is (these are role names) 1. model 2. diagram 3. useCase 4. artifact The models, diagrams, artifacts, and so on within this class are intended to describe the requirements that the component proposes to fulfill. xmi:ordered=true property order is (these are role names) 1. model 2. diagram 3. interfaceSpec 4. artifact The Design class has no attributes, but has several associated classes including: Model, Diagram, InterfaceSpec, and Artifact. The models, diagrams, artifacts, and so on within this class are intended to describe the design elements that are necessary for the asset consumer to use the component. Refer to the description of the Model class and Diagram class in the Requirement class. xmi:ordered=true property order is (these are role names) 1. model 2. diagram 3. interfaceSpec 4. artifact The Design class has no attributes, but has several associated classes including: Model, Diagram, InterfaceSpec, and Artifact. The models, diagrams, artifacts, and so on within this class are intended to describe the design elements that are necessary for the asset consumer to use the component. Refer to the description of the Model class and Diagram class in the Requirement class. xmi:ordered=true property order is (these are role names) 1. artifact The Implementation class has a collection of Artifact instances. These Artifact instances identify the binary and other files that provide the component implementation. The Implementation class has no attributes. xmi:ordered=true property order is (these are role names) 1. artifact The Implementation class has a collection of Artifact instances. These Artifact instances identify the binary and other files that provide the component implementation. The Implementation class has no attributes. xmi:ordered=true property order is (these are role names) 1. model 2. diagram 3. artifact The Test class has no attributes, but does have several associations including: model, diagram, and artifact. The models, diagrams, artifacts, and so on within this element are intended to describe the testing of the component for the asset consumer. xmi:ordered=true property order is (these are role names) 1. model 2. diagram 3. artifact The Test class has no attributes, but does have several associations including: model, diagram, and artifact. The models, diagrams, artifacts, and so on within this element are intended to describe the testing of the component for the asset consumer. xmi:ordered=false The component may fulfill one or more use cases. This element points to a use case document. The attributes are the same as the Artifact attributes; but are constrained to reference use case documents for the component. xmi:ordered=false The component may fulfill one or more use cases. This element points to a use case document. The attributes are the same as the Artifact attributes; but are constrained to reference use case documents for the component. xmi:ordered=false A Model may have multiple Diagrams. In the Requirements class, the Diagram identifies the requirements-related diagrams such as the Business Concept Model diagram and the Use Case diagram, see UML Components, page 41. The attributes are the same as the Artifact attributes; but are constrained to reference diagrams for describing the requirements for the component. xmi:ordered=false A Model may have multiple Diagrams. In the Requirements class, the Diagram identifies the requirements-related diagrams such as the Business Concept Model diagram and the Use Case diagram, see UML Components, page 41. The attributes are the same as the Artifact attributes; but are constrained to reference diagrams for describing the requirements for the component. xmi:ordered=true property order is (these are role names) 1. diagram 2. model This is the model for specifying the requirements the component proposes to fulfill. There may be multiple models such as the Business Concept Model and the Use Case Model, see UML Components, page 41. The attributes are the same as the <artifact> attributes; but are constrained to reference models for describing the requirements for the component. xmi:ordered=true property order is (these are role names) 1. diagram 2. model This is the model for specifying the requirements the component proposes to fulfill. There may be multiple models such as the Business Concept Model and the Use Case Model, see UML Components, page 41. The attributes are the same as the <artifact> attributes; but are constrained to reference models for describing the requirements for the component. xmi:ordered=true property order is (these are role names) 1. condition 2. parameter The Operation describes one InterfaceSpec operation and has two associations, Condition and Parameter. These elements provide sufficient information in the asset packaging to let asset consumers and tools reason on the nature of the interface. The Operation class has three attributes, name, initiatesTransaction, and description. The name is the operation name. The initiatesTransaction declares (i.e., boolean) if the Operation starts a transaction. The description provides for a brief abstract on the Operation. This is the name of the Operation. This boolean value indicates whether the Operation starts a transaction. xmi:ordered=true property order is (these are role names) 1. condition 2. parameter The Operation describes one InterfaceSpec operation and has two associations, Condition and Parameter. These elements provide sufficient information in the asset packaging to let asset consumers and tools reason on the nature of the interface. The Operation class has three attributes, name, initiatesTransaction, and description. The name is the operation name. The initiatesTransaction declares (i.e., boolean) if the Operation starts a transaction. The description provides for a brief abstract on the Operation. xmi:ordered=true property order is (these are role names) 1. operation 2. informationModel The InterfaceSpec class describes the interface of the component. There may be multiple interfaces defined on the component, so multiple instances of this class may be required. The name attribute is the user-consumable name of the interface. The description is a human consumable short description of the interface. This class has two associations, Operation and InformationModel. If you create an InterfaceSpec you must create one or more Operation instances. This containts a description of the interface. This is the name of the interface. xmi:ordered=true property order is (these are role names) 1. operation 2. informationModel The InterfaceSpec class describes the interface of the component. There may be multiple interfaces defined on the component, so multiple instances of this class may be required. The name attribute is the user-consumable name of the interface. The description is a human consumable short description of the interface. This class has two associations, Operation and InformationModel. If you create an InterfaceSpec you must create one or more Operation instances. xmi:ordered=true property order is (these are role names) 1. attribute 2. associationRole The InformationModel class describes the information or state that is retained between invocations of the operations on the interface. This class has two associations, Attribute and AssociationRole. xmi:ordered=true property order is (these are role names) 1. attribute 2. associationRole The InformationModel class describes the information or state that is retained between invocations of the operations on the interface. This class has two associations, Attribute and AssociationRole. xmi:ordered=false The Condition class captures the pre-, post- and other conditions of the Operation. It has two attributes type and description that declare the kind of the condition and explains the condition, respectively. This captures the type of the condition for the Operation, such as a "pre" for a pre-condition that must exist before the operation is invoked. xmi:ordered=false The Condition class captures the pre-, post- and other conditions of the Operation. It has two attributes type and description that declare the kind of the condition and explains the condition, respectively. xmi:ordered=false The Parameter class describes the parameters on the Operation having the attributes of name, type, and direction. The name attribute is the name of the parameter. The type attribute describes the parameter's type. The direction attribute describes whether the parameter is input to the operation, or output, or both, and so on. This is the name of the Parameter on the Operation. This is the type of the Parameter on the Operation. This is the direction of the Parameter on the Operation, such as "in", "out", "inout". xmi:ordered=false The Parameter class describes the parameters on the Operation having the attributes of name, type, and direction. The name attribute is the name of the parameter. The type attribute describes the parameter's type. The direction attribute describes whether the parameter is input to the operation, or output, or both, and so on. xmi:ordered=false The Attribute class captures the name, type, and defaultValue attributes of the state that is retained between invocations of operations on the interface. The name attribute is the name of the Parameter attribute. The type attribute is the Parameter attribute's type. And the defaultValue attribute is the Parameter attribute's default value. This is the name of the Attribute in the InformationModel whose state is retained. This is the Attribute type. This is the default value of the Attribute in the InformationModel. xmi:ordered=false The Attribute class captures the name, type, and defaultValue attributes of the state that is retained between invocations of operations on the interface. The name attribute is the name of the Parameter attribute. The type attribute is the Parameter attribute's type. And the defaultValue attribute is the Parameter attribute's default value. xmi:ordered=false The AssociationRole class captures the name, and type attributes of the state that is retained between invocations of operations on the interface. This element represents the roles that are on interface relationships. Creating instances of this element indicates that the InterfaceSpec owns the state related to the relationship. This is the name of the AssociationRole in the InformationModel whose state is retained across multiple invokations. This is the supplier class or the type of the AssociationRole. xmi:ordered=false The AssociationRole class captures the name, and type attributes of the state that is retained between invocations of operations on the interface. This element represents the roles that are on interface relationships. Creating instances of this element indicates that the InterfaceSpec owns the state related to the relationship.