Part 2 provides reference and usage information for the various class stereotypes used with Cúram modeling and related topics.
Some notes applicable to classes in general:
- Two or more struct or process classes may have the same name provided they are in different packages and have differentCODE_PACKAGE names. All other class names must be completely unique within the input model. For more information on theCODE_PACKAGE option see the CODE_PACKAGE option in Options.
- All classes and domain definitions are visible to each other throughout the model.
- All new classes should be created within a sub-package of a custom model. It is advisable to model new classes within a suitable package structure. The package structure within the Cúram model is a good pattern to follow. For clarity, new class name should be prefixed with a relevant acronym or abbreviated word as discussed in the Cúram Development Compliancy Guide.
These are the chapters making up this part:
- Chapter 4 Audit Mappings Classes
- Chapter 5 Domain Definition Classes
- Chapter 6 Entity Classes
- Chapter 7 Extension Classes
- Chapter 8 Facade Classes
- Chapter 9 Process Classes
- Chapter 10 Struct Classes