1. Monday, October 27, 2003 X-Change Technologies—Compliance proposal 1 Compliance Proposal by X-Change Technologies

2. Monday, October 27, 2003 X-Change Technologies—Compliance proposal 2 Goals Small number of compliance points (order of ten) Small number of rows Small number of columns (e.g., two) Blanks in matrix

3. Monday, October 27, 2003 X-Change Technologies—Compliance proposal 3 This proposal This proposal is for discussion and agreement in principle. It does not provide the full details that will be needed for the specification. These can be worked out once agreement is principle is reached.

4. Monday, October 27, 2003 X-Change Technologies—Compliance proposal 4 Partial Eliminate this column

5. Monday, October 27, 2003 X-Change Technologies—Compliance proposal 5 Interchange Eliminate Interchange as a column Agree on compliance points, independently of interchange Add this provision: To claim interchange compliance, a tool must both produce and import XMI for everything for which that tool claims compliance

6. Monday, October 27, 2003 X-Change Technologies—Compliance proposal 6 Diagram Interchange Add this provision: To claim diagram interchange compliance a tool must interchange all notation for all diagrams for everything for which that tool claims compliance. [This may belong in the diagram interchange specification, but should be agreed by both FTFs.]

7. Monday, October 27, 2003 X-Change Technologies—Compliance proposal 7 Basic To claim basic compliance, the tool must comply with all packages listed as Basic in the final adopted specification

8. Monday, October 27, 2003 X-Change Technologies—Compliance proposal 8 Intermediate To claim intermediate compliance, the tool must claim basic compliance and state which of the intermediate compliance points it claims compliance with.

9. Monday, October 27, 2003 X-Change Technologies—Compliance proposal 9 Intermediate The intermediate compliance points are: Interaction State Machine Activity Components and Composite Structure Deployment Action

10. Monday, October 27, 2003 X-Change Technologies—Compliance proposal 10 Complete To claim complete compliance, the tool must comply with all of the specification, and claim interchange and diagram interchange compliance.

11. Monday, October 27, 2003 X-Change Technologies—Compliance proposal 11 Evaluation Evaluation of proposal against its goals: Small number of compliance points (1+63+1)*3 = 195 Small number of rows 1+6+1 = 8 Small number of columns 2 Blanks in matrix none

12. Monday, October 27, 2003 X-Change Technologies—Compliance proposal 12 Opportunities for improvement Add blanks to the matrix Here is, not a proposal, but a concrete example of restriction by adding blanks: To claim Intermediate—Action, the tool must also claim Intermediate—State Machine or claim Intermediate—Activity

13. Monday, October 27, 2003 X-Change Technologies—Compliance proposal 13 Request X-Change Technologies requests comments on this proposal that attempt to improve the proposal by making adjustments to it or by providing the necessary additional detail of which packages are included in each intermediate compliance point.

14. Monday, October 27, 2003 X-Change Technologies—Compliance proposal 14 Request X-Change Technologies requests, from folks who prefer not to attempt to improve this proposal, an alternate proposal that meets the same goals.

15. Monday, October 27, 2003 X-Change Technologies—Compliance proposal 15 Request X-Change Technologies requests, from folks who do not agree with the goals of this proposal, a proposal for changes to the goals, stating, for each proposed change, the way in which that changed goal better serves the interests of UML users.