Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Concepts and Definitions : Schema

Schema
Organization Modeler enables you to create an embedded Schema for use in the definition of your organization model.
Using a Schema, you can specify Types that you intend to use for certain elements within your organization. By setting up these types, you can create a generic model or template for your organization model. Defining different Types of Organization, Organization Unit, Position, Resource and so on, and choosing and defining Attributes for those Types, enables you to extend the model provided by the default schema until it is a close representation of the components that make up the organization that you wish to model.
The containment relationships between components can also be defined in the schema’s Types. For example, from an Organization element that you have assigned an Organization Type, Organization Modeler enables you to create a child Organization Unit of a defined type, because the relationship between the two Types is described in the schema.
An example of this is shown below. One type of Organization - the Public Company organization type - is defined in the standard Schema. One type of Organization Unit element - Head Department - is defined as a Member of that Organization Type. If your Organization is defined as a Public Company, and you right-click in the Organization Editor to add an Organization Unit, you can select either an un-Typed Organization Unit, or a Head Department unit.
This allows you to create specific organizational structures in a Schema, so that when you need to create an instance of that structure in your organization model, you can use the structures defined in the Schema. For example, you may want to create an organization structure for temporary projects that consists of specific Organization Units and Positions. You can create this structure in a Schema then create an instance of a temporary project based on the Schema. See Using a Schema in an Organization Model for more information.
The benefits of Schemas are:
When you use a Schema within the Organization Modeler you can either:
You can also decide to use a mixture of the two approaches by adding your own types to the default schema.
The Organization Modeler Default Schema
When you create certain components within your Organization Model, the Organization Modeler enables you to allocate standard types to these components. Not all the components within the Organization Modeler have a standard type. The following table describes the components that have types provided in the default schema, what they are, and what members each of those types contains:
When you create an Organization Model, you can decide whether to use the Standard Types provided by the Organization Modeler, create new Types, or create your own Schema, depending on your requirements.
When a component that has a standard type defined for it is created, you can assign the type in the Properties View for the component. By default no type is assigned, as in the following illustration. You can assign a type by clicking and selecting either the standard type or any other type that has been defined.
The following diagram shows the default schema as it appears in the Project Explorer, if you chose to apply it when creating the project:
The following diagram shows how the default schema reflects an organizational structure.
In this diagram:
Public Company is the delivered Organization type.
Head Department is an Organization Unit type that is a member of Public Company. This type has a multiplicity defined as 0..1, so there can only be one Head Department.
Department, Business Unit and Team are the other Organization Unit types delivered. All of these need to be in a hierarchical relationship with another typed organization unit as their parent. The hierarchy does not need to be that shown in the diagram, however; any one of the delivered organization units can be the parent of any other.
Attributes
For each of the Types in the schema you can create Attributes. An Attribute enables you to add some extra semantic information to each individual type. For example, for a Position whose type is Manager, you could create an Attribute called bonus to specify what type of bonus should be given to this Position. The Standard Position Type in the default schema has the attribute Contract Type assigned to it. The Standard Location Type delivered in the default schema has the following attributes already defined:
When you create an attribute, you must specify a data type that determines its allowable values. For a description of the data types an attribute can have, see About Data Types.
Members
For the Organization Type and Organization Unit Type you can create Members. The following table describes what Members you can create for each type:
The use of Members enables you to group together a set of Position Types and Organization Unit Types into meaningful units. Once you have created your Organization Unit Types and Position Types, you can create a template structure by grouping them together within an Organization Type or Organization Unit Type as Members of that Type. An illustration of the Department type delivered in the default schema is shown below.
The Department, Business Unit and Team Organization Unit Types have been grouped together in the Department organization unit type as unit members of the type. This means that when an Organization unit element is created in an Organization Model using the default schema, these elements are available from the Add Child menu, from the context menu or from the palette. This is illustrated below.
When you subsequently add an Organization Unit to your Organization diagram, you can select one of these Elements from the Element field on the General tab, and assign it to the new Organization Unit.
See Using a Schema in an Organization Model for more information.
Multiplicity
You can specify whether TIBCO Business Studio needs to allow for multiple copies of an element. The following table describes the multiplicity values you can specify:
Multiple instances from zero to n where n is greater than zero.
n..m
Multiple instances where n and m are zero or more. For example:
 

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved