Model Completeness/Quality Assurance feature

RMC should have a similar feature to the Java Compiler Error/Warnings so that site standards to model completeness/quality assurance can be applied by the tool and appropriate errors/warnings/infos can be generated and presented in the Problems View. Just as Java groups them by categories such as Code Style, Potential Programming problems, etc, I would expect that it should be possible to indicate various categories of RMC issues. These would include relationship-related concerns, such as artifacts without templates or tasks without performers, as well as attribute-related concerns, such as a role without defined skills.
For example, individual sites could mark the role skills rule as Error/Warning/Info/Ignore as their needs dictate.
Perhaps, for performance reasons, this should be implemented as a function (c.f. Validate) rather than a continual check (as is done in Java), particularly since current implementations of RMC depend on configurations to resolve variability and method libraries can be quite large.

Although it is conceivable that users may want to have all rules for all relationships and attributes, I believe we should focus, initially, on a subset of rules (and let the debate begin...):

1. Attributes
For each of the method element types Tasks, Roles and Workproducts:
a. Purpose not specified
b. Main Description not specified
For tasks only:
(empty)
For Roles only:
a. Skills not specified
For work products:
a. Brief Outline not specified
b. Reason for not needing not specified

2. Relationships.
For Tasks only:
a. Primary Performer not specified
b. No Steps specified
c. No inputs specified
d. No outputs specified
e. Not member of discipline
f. Estimate not specified
For work products only:
a. No template specified
b. No example specified
c. No responsible role
d. Not member of domain
e. Not member of work product kind
For roles only:
a. Not member of role set