Capture principle data
The license package Enterprise Architecture Management is required to work with principles. The use case Architecture Governance must be activated.
A principle is an overarching guideline that directs the enterprise architecture definition and decision-making across the company. An organization is responsible for the principle. A principle may have an unlimited number of subordinate principles but only one ascendant principle.
In the navigation panel, click Investment Architecture > Principles. Per default, the data workbench displays only a set of basic attributes. You can add more columns to capture other attributes directly in the data workbench or you can navigate to a principle's content area and define it in more detail there. Click to learn about how to use data workbenches.
Go to Investment Architecture > Principles and specify the basic data.
Create a new principle from scratch. Click New > Principle. Specify the principle's attributes as well as the relationships that the principle has to other assets in the repository. All mandatory fields must be defined to create the principle and save it.
Edit the attributes and relationships for a principle. Click the Navigate 
button next to a principle to open its content area . Specify the principle's attributes as well as the relationships that the principle has to other assets in the repository.
Try to capture as much information as possible about the principle because complete data considerably improves the results of business questions and other analytics.
Once a principle is in the repository, you can define more details about it in the Principles data workbench . Or specify and analyze the principle in detail in its content area.
Per default, the data workbench displays a limited set of basic attributes. You can add more columns via the Structure column to capture other attributes directly in the data workbench.
- Name: (Mandatory) Enter a unique name for the principle so that users can recognize its purpose.
- Type: Select the category that describes the principle type.
- Responsible Organization: Specify the organization that owns the principle.
- Justification: Describe the reason that the principle exists.
- Implication: Describe the consequences that the principle has on the organization.
- Authorized Access tab: The user who creates the principle is the authorized user per default. This can be changed. Select one or more authorized user groups that shall have write permissions to the object. All users in the authorized user group can edit the principle.