The Default Web Service Profile is targeted for packaging the client side of web services. However, the server side artifacts of the service can be packaged as well. 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=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. wsdl 2. artifact The Implementation class has two associations, Wsdl and Artifact. The Wsdl points to the wsdl file wihch describes the web service. 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. wsdl 2. artifact The Implementation class has two associations, Wsdl and Artifact. The Wsdl points to the wsdl file wihch describes the web service. 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=false The InterfaceSpec class names the interface of the web service. There may be multiple interfaces defined on the web service, so multiple instances of this class may be required. The name attribute is the user-consumable name of the interface. The wsdlName is the name of the section within the wsdl file that describes the interface; in essence it is an index into the wsdl file. xmi:ordered=false The InterfaceSpec class names the interface of the web service. There may be multiple interfaces defined on the web service, so multiple instances of this class may be required. The name attribute is the user-consumable name of the interface. The wsdlName is the name of the section within the wsdl file that describes the interface; in essence it is an index into the wsdl file. 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. 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. The Solution class extends the Default Profile Solution class. This class introduces requirements, design, implementation, and test artifacts for the web service. The Solution class extends the Default Profile Solution class. This class introduces requirements, design, implementation, and test artifacts for the web service. 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 web service may realize 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 web service. xmi:ordered=false The web service may realize 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 web service. xmi:ordered=false The Wsdl class maintains a reference to the wsdl file which possess the description of the web service. xmi:ordered=false The Wsdl class maintains a reference to the wsdl file which possess the description of the web service.