Task: Define Asset Rules and Policies
Define rules with which assets should comply in order to participate in the repository.
Disciplines: Asset Governance
Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory:
    Optional:
    • None
    Outputs
      Main Description

      In this task, a policy document describing the rules by which the assets should comply is created. The kinds of rules include the following:

      • Naming conventions for:
        • Asset types.
        • Assets.
        • Artifacts.
        • Relationship types.
      • Required support resources, length of support, and contact information for assets.
      • Asset classification requirements:
        • Policies for tagging assets with user provided values.
        • Policies for classifying assets using category schema values.

      Be sure to identify the version of the asset rules and policies that the enterprise is using. Some sample asset rules and policies are listed below.

      Asset Type Rules: Version: 1.0

      1. Asset Type must describe the kinds of users which will use the assets, and at what point in the development process the assets will be used.
      2. An asset type specification must be created and approved by the Asset Governance Board. This is to minimize redundant or similar asset types in the repository.
      3. Target Audience: Architects, Administrators

      Asset Rules: Version 2.0

      1. All assets must include support contact information.
      2. All asset names must abide by the naming conventions described here:
        1. No asset names can use abbreviations
        2. Asset names can use industry acronyms
        3. All words in asset names start with capital letter
      3. Target Audience: Practitioners (Analysts, Architects, etc.) who submit assets.

      Artifact Rules: Version 1.0

      1. An artifact name can be the same as the file name
      2. Target Audience: Practitioners (Analysts, Architects, etc.) who submit assets.

      Relationship Type Rules: Version 1.0

      1. Relationship types should be approved with the Asset Governance Board before they are used. Target Audience: Architects, Administrators

      Asset Classification Rules: Version 2.0

      1. All assets must be classified with the enterprise Business Domain schema, and the Technology schema.
      2. Custom tags need to abide by the naming conventions here:
        1. No tags can start with a number
        2. Tags with multiple words must be concatenated with an underscore "_"
      3. Target Audience: Practitioners (Analysts, Architects, etc.) who submit and use assets.

      Classification Schema Rules: Version 1.0

      1. Classification Schemas must be approved by the Asset Governance Board. The schema must be reviewed and compared with other schemas for redundancy.
      2. The Classification Schema must have a name that follows the same naming convention as for Asset Types.
      3. The Classification Schema must have a description which identifies the target users/audience for the schema.
      4. Target Audience: Architects, Administrators
      Steps
      Create Asset Rules and Policies

      Identify the categories of asset rules that need to be created, such as Asset Type Rules, and so forth. Define the version of the particular set of rules. Describe the rules and policies. Describe the target audience for complying with the rule.

      Review the Asset Rules and Policies with the Users
      The key here is to achieve buy-in and support from the teams that will be using and impacted by the rules: the asset manufacturing and usage teams.
      Share the Asset Rules and Policies with the Repository Administrators
      The administrators will configure the asset repository to comply with the rules.
      Key Considerations