Parameter Properties

The Parameter Properties command allows you to modify the definition of the selected parameter. CORE opens a dialog enabling you to completely define the parameter.

Tips and Tricks Double-clicking on parameter in the parameters list in the schema view is a shortcut for opening its properties dialog.

The parameter definition dialog display the basic properties associated with the parameter.

• Name - the internal name of this parameter. The name is used to reference the attribute throughout CORE - in data sets, filters, sort blocks, icon templates, reporting, and more. By convention, attributes are shown in camel case.
• Alias - the label associated with this attribute in CORE's user interface. Aliasing allows you to tailor the underlying schema and language of MBSE to your specific project and domain without incurring additional integration or compatibility costs. By convention, aliases are shown in title case. If no alias is specified, the parameter name will be used.
• Type - the class of value for the parameter
• • Date - a date is a value that represents a calendar day.
  • Float - a floating point number. CORE's implementation conforms to the IEEE standard for double precision with a maximum exponent of 309.
  • Integer - a whole number ranging between -2147483647 and 2147483647.
  • String - a traditional single line array of characters.
  • Time - a value that represents a time of day to the nearest second.
  • TimeStamp - an object that represents a date and time.
• Creator - the name of the user who created the parameter.
• Created - the timestamp when the parameter was created.
• Last Modified - the timestamp when the parameter definition was last changed.
• Description - a description of the parameter and its use. By providing descriptions for the schema classes, attributes, parameters, and relations, the schema becomes self-documenting. This is an important guide in introducing new project team members to your project meta-language.

CORE does not freeze the schema when you begin your project work. Therefore, if your project currently has data (elements, relationships, attributes, and parameters), modifying existing portions of the schema will transform any existing data. For example, if you change a parameter type, CORE will attempt to transform any existing parameter values to the new value.