The Touchstone Profile
Every stereotype, tag, enumeration and derived property the Touchstone Profile and its customization
carry. The documentation inside the archives states the same facts on each element; this page is
the readable copy outside the tool. ProfileShapeTest and CustomizationShapeTest read the
archives and fail when the two disagree with this page.
The profile is named Touchstone Profile, URI https://www.mbseconsulting.com/spec/touchstone/profile.
The customization is named Touchstone Customization, URI
https://www.mbseconsulting.com/spec/touchstone/customization.
Packages
| Stereotype | Extends | Owned by | Holds |
|---|---|---|---|
| «Enabler» | Package | a Package or a Model | the formalization of one modeling approach: the four packages below |
| «ObjectivePackage» | Package | Enabler, ObjectivePackage | «Objective» |
| «OntologyPackage» | Package | Enabler, OntologyPackage | «Concept», «JustifiedBy», rules owned at package level |
| «ImplementationPackage» | Package | Enabler, ImplementationPackage | the mappings, «MaturityRuleImplementation», «Implements» |
| «ProcessPackage» | Package | Enabler, ProcessPackage | «Step» |
An Enabler may hold a proposal implementation; a project that uses it adds its own implementation beside the proposal.
Objectives
| Stereotype | Extends | Owned by | Tags |
|---|---|---|---|
| «Objective» | Class | ObjectivePackage | status : ObjectiveStatus [1..1], rationale : String [0..1], priority : Integer [0..1] |
ObjectiveStatus offers Approved, Postponed, Rejected. priority ranks objectives; the lowest
value is the highest priority, and an unset value means unranked. rationale records why an
objective is postponed or rejected.
Ontology
| Stereotype | Extends | Owned by | Type restriction |
|---|---|---|---|
| «Concept» | Class | OntologyPackage | |
| «Attribute» | Property | Concept | a PrimitiveType or an Enumeration |
| «Relation» | Property | Concept | a «Concept» |
| «JustifiedBy» | Dependency | OntologyPackage | source Concept, Attribute or Relation; target Objective |
A «Concept» may specialize another «Concept». A «Relation» is directed from the owning Concept to the typing Concept; the association line that draws it carries no semantics of its own. The plugin applies «Attribute» and «Relation» automatically, as Auto-stereotyping rules states.
The individuals of a Concept are computed from its mappings. A mapped Concept answers what its own mappings select; an unmapped Concept with specializations answers the union of theirs; a Concept with neither answers nothing. A specialization's individuals are never copied into a mapped general Concept: the taxonomy is a constraint the mappings must satisfy.
An Attribute or a Relation keeps the multiplicity the tool gives a property by default. A bound is a
rule: hasAtLeast(1) on a «ModelingRule», never a multiplicity the tool would not enforce.
Maturity rules
| Stereotype | Extends | Abstract | Owned by | constrainedElement |
|---|---|---|---|---|
| «MaturityRule» | Constraint | yes | ||
| «ModelingRule» | Constraint, specializes MaturityRule | no | Concept, OntologyPackage | Concept, Attribute or Relation |
| «EngineeringRule» | Constraint, specializes MaturityRule | no | Concept, OntologyPackage | Concept, Attribute or Relation |
«MaturityRule» carries expression : String [0..1], the rule in the Touchstone expression language
as HTML with element hyperlinks.
A rule is a predicate over the individuals of its context Concept: the constrained Concept, or the
Concept owning the constrained Attribute or Relation. Its specification states the rule in English;
its expression states it in the expression language, and a rule with
no expression is evaluated through its «MaturityRuleImplementation»s. A «ModelingRule» must hold for
every individual before a model counts as complete. An «EngineeringRule» yields a ratio that is read
as a finding and never aggregates.
Implementation
| Stereotype | Extends | Owned by | Tags |
|---|---|---|---|
| «ConceptMapping» | Class | ImplementationPackage | metaclasses : UmlMetaclasses [0..*], stereotype : Stereotype [0..*], scope : Element [0..*], includeSubtypes : Boolean [1..1], filter : OpaqueBehavior [0..1] |
| «AttributeMapping» | Class | ConceptMapping, ImplementationPackage | metaProperty : UmlProperties [0..1], tag : Property [0..1], derivedProperty [0..1], query : OpaqueBehavior [0..1] |
| «RelationMapping» | Class | ConceptMapping, ImplementationPackage | the same four tags |
| «MaturityRuleImplementation» | Class | ConceptMapping, ImplementationPackage | validationRule : Constraint [1..1] |
| «Implements» | Abstraction | ImplementationPackage | rationale : String [0..1] |
A «ConceptMapping» selects the elements of metaclasses, or of the metaclasses its stereotypes
extend when metaclasses is empty, carrying one of the stereotypes, owned transitively within
scope, and accepted by filter. The tags compose with AND; metaclasses narrows when both it
and stereotype are set; includeSubtypes widens both to specializations and sub-metaclasses and
defaults to false, so a mapping to Class selects the elements whose metaclass is Class and
nothing more until the tag is set; filter is a predicate evaluated on each remaining candidate. It takes the
candidate as its one Element parameter and returns a Boolean; any other result, on any candidate,
means the mapping yields nothing, and one line is written in the log under Touchstone. At least one
of metaclasses and stereotype is set. Several mappings on one Concept compose with OR.
An «AttributeMapping» or «RelationMapping» sets exactly one of its four tags: metaProperty, tag
and derivedProperty name where the value is held, query names a behavior that computes it, taking
the individual as its one parameter. A mapping owned by a «ConceptMapping» applies to that mapping's
individuals only; one owned by an «ImplementationPackage» applies to every individual of the
Concept. A Relation's targets are kept only when they are individuals of the Relation's type.
«Implements» runs from a ConceptMapping to a Concept, from an AttributeMapping to an Attribute, from
a RelationMapping to a Relation, or from a MaturityRuleImplementation to a MaturityRule. The
customization admits the four sources and the four targets together; the pairing is a modelling
rule.
UmlMetaclasses lists every UML metaclass CATIA Magic exposes, one literal per name.
UmlProperties lists every JMI accessor name, one literal per constant of PropertyNames and
PrivatePropertyNames; UmlPropertiesEnumerationTest pins the list to the installed tool.
Process
| Stereotype | Extends | Owned by | Restriction |
|---|---|---|---|
| «Step» | Activity | ProcessPackage | |
| «StepAction» | CallBehaviorAction | Step | behavior is a «Step» |
Derived properties
The customization declares these derived properties. Each is documented on its element in the tool.
| Element | Property | Type | Meaning |
|---|---|---|---|
| Concept | mappings | ConceptMapping [*] | the mappings that realize this Concept, through «Implements» |
| Concept | justifiedBy | Objective [*] | the Objectives this Concept serves |
| Concept | modelingRules, engineeringRules | Constraint [*] | the rules constraining this Concept, its Attributes or its Relations, by kind |
| Concept | individuals | Element [*] | the elements the Concept's mappings select, or the union of its specializations' individuals when it has no mapping of its own |
| ConceptMapping | individuals | Element [*] | the elements this mapping selects on its own, before the union with the Concept's other mappings |
| Attribute | mappings, justifiedBy, modelingRules, engineeringRules | as for Concept, on the Attribute | |
| Relation | mappings, justifiedBy, modelingRules, engineeringRules | as for Concept, on the Relation | |
| Objective | justifies | Element [*] | the Concepts, Attributes and Relations that serve this Objective |
| Objective | modelingRules, engineeringRules | Constraint [*] | the rules on what this Objective justifies, by kind |
| ConceptMapping | mappedConcept | Concept | the Concept this mapping realizes |
| AttributeMapping | mappedAttribute | Attribute | the Attribute this mapping binds |
| RelationMapping | mappedRelation | Relation | the Relation this mapping binds |
| MaturityRule | implementations | MaturityRuleImplementation [*] | the tool-bound implementations of this rule |
| MaturityRule | passing, failing | Element [*] | the individuals of the context Concept for which the rule holds, and those for which it does not |
| MaturityRule | score | Real | passing over all individuals; absent when the Concept has none or the rule has no verdicts |
| Concept | completeness | Real | the mean of score over its modeling rules, its Attributes' and Relations' included; absent when none has a score |
| Attribute, Relation | completeness | Real | over its own modeling rules |
| Objective | completeness | Real | the mean over the completeness of what it justifies; absent when Postponed or Rejected, or when nothing has a score |
| MaturityRuleImplementation | implementedRule | MaturityRule | the rule this validation rule implements |
| Step | subSteps | Step [*] | the Steps this Step calls, in the order of the calls |
The customization also ships the generic tables _Topic_ Objectives, _Topic_ Steps,
_Topic_ Ontology, _Topic_ Concept Mappings, _Topic_ Attribute and Relation Mappings,
_Topic_ Maturity Rule Implementations and _Topic_ Maturity, and the matrices
_Topic_ Ontology Justification (Concepts, Attributes and Relations against Objectives) and
_Topic_ Ontology Implementation (mappings and implementations against what they implement).