A TSoR has exactly one root which is an analysis element
A TSoR should have exactly one root through the property hasRoot, and this root must an AnalysisElement.
A TSoR has no more than one aggregation function
A TSoR should have 0 or 1 aggregFunction, no more.
A TSoR should have at least one description.
A TSoR should have at least one creator.
A TSoR should have exactly one creation date.
An analysis element can be the root of a TSoR
An AnalysisElement can be associated with a maximum of one TSoR throught the property hasRoot.
Analysis elements have no more than one weight, a positive number.
An AnalysisElement should have 0 or 1 weight, no more. That weight should be positive number with one of the following xsd type: integer, float, double or decimal.
An analysis element either specifies another one, or is the root of the TSoR
An AnalysisElement either specifies exactly one other AnalysisElement, being object of a property isSpecifiedBy, or is the root of exactly one TSoR, being object of a property hasRoot.
An AnalysisElement should have 0 or 1 content throught hasContent relation.
No unused analysis element. An analysis element is either specified by another one, or expects a requirement.
No unused analysis element. An AnalysisElement must be subject of isSpecifiedBy, or of expects.
Uniformity of children types. An analysis element is either specified by another one, or expects a requirement, but not both.
Uniformity of children types. An AnalysisElement must either be subject of isSpecifiedBy, or of expects, but not both.
Requirement is expected by exactly one analysis element
Requirement must be exactly once the object of relations expects, with subject an AnalysisElement.
Requirement is implemented by one implementation maximum
Requirement has 0 or 1 Implementation through the relation isImplementedBy.
Requirements have no more than one weight, a positive number.
A Requirements should have 0 or 1 weight, no more. That weight should be positive number with one of the following xsd type: integer, float, double or decimal.
An Requirement should have exactly one content throught hasContent relation.
Complete implementation. Each requirement should have exactly one implementation.
An implementation must not have more than one query.
Implementation should have one query or one URL.