NEW definition To be approved at the December 10, 2013 teleconference+: Profile
- A profile is a constraint of the model on which it is based.
- To be considered conformant, a profile must adhere, according to the normative constraint requirements of the model to the rules of the base model.
- If a derivation of an existing profile; then a profile must adhere to the normative constraint requirements of the base model and to the existing profile from which the profile is derived.
- A profile may be more restrictive but not less restrictive than the base model. This puts an obligation on the base model to describe how it can be extended or constrained. Because a profile is created to solve a business need, the profile may include additional functions and criteria that satisfy the business needs of the scope of the profile.
- A profile is traceable to the model on which it is based and for those functions/criteria which are associated with the base model or profile of which it is derived.
Related: Why do we have a profile? A profile is an expression of a particular implementation based on a model. Business context is better than use case. How the base model is used to support a particular use case. Puts obligation on the BASE model to constrain the derived profiles, and extensions. A base model is a standard to which a profile is applied to support business context. [[Template | Template}: Should be provided for in the Profile. Template usually constrains a subset of a model, not an entire model. [[Implementation_Guide | Implementation Guide](IG) is a collection of templates. Templates have reuse - constraining the entire model affects the reuse. An IG may contain more than a profile or template - may contain other information. An IG describes how to create instances.