|Description|| - An error shall be raised when the transformations has generated many classes with the same name for the same aspect. (scope is step for step class diagram and scope is workflow for workflowInstantiator class diagram)|
- In order to make it easy for the UCM designer to localize the source of the problem, the error message should have the form "UCM1/Type1/Name1 clashes with UCM2/Type2/Name1" (e.g., type could be Stub or Condition or OR-Fork)
- Name clashes with custom RAM aspects are unavoidable; thus, it is the RAM tool responsibility to prevent/detect these name clashes. Ex: a responsibilty name inputQueueFinder.
- The first character of a class name shall always be in uppercase
- Everything needs to be checked before the transformation is written to the RAM files. Only if there is no error, then the transformation may be performed.