Task: Prepare Classification Schema
Identify the categorization for assets.
Disciplines: Asset Governance
Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory:
    Optional:
    • None
    Outputs
      Main Description

      Classification schemas are a form of communication, and serve to help describe assets. Classification schemas can be used as mechanisms for searching and discovering assets. The repository can have many classification schemas. The administrator submits these classification schemas in the repository.

      An asset may be classified using values from many classification schemas. The classification schemas may be exclusive and not related to each other. Using classification schemas in this manner permits many perspectives to be captured. For example, not only do practitioners (architects, developers, testers, etc.) work with assets, but certainly administrators and technical management will interact with the assets, as well as with report generators, metrics collectors and other tools.

      Each classification schema should be created with a specific focus. For example, you may create a classification schema to describe the business domain of interest to the enterprise. You might create another classification schema to describe the technical contexts for the enterprise, such as runtime platforms and development platforms.

      Classification schemas are often created from the perspective of a target consumer. For example, architects may want to discover an asset's relevancy from the perspective of non-functional characteristics.

      A classification schema example.

      There is a similarity and relationship between asset type and classification. Both are used for describing the asset, both are used for searching and discovery. The asset type has a stronger affinity with describing the set of artifacts that should exist in the asset and also with the kinds of relationships that the asset should have with other assets. An asset has one type, whereas it may have many classifications which enhance the description of the asset.
      Steps
      Determine the Consumers Perspectives to be Represented
      The architect and other stakeholders evaluate the way in which they anticipate asset repository users will view and access their assets. In general, the administrator will create one classification schema per perspective. Not all users should be burdened with all perspectives.
      Create a Classification Schema for each Perspective

      The classification schema may be captured in the form of a treeview, or it may be in the form of a model. One or more classification schemas may be used to represent key views for an enterprise architecture. A reference model can be used as a basis for a category schema. For example, you may use the Technical Reference Model (TRM) from the Federal Enterprise Architecture (FEA) to classify your assets. A graphical representation of the reference model may be used to communicate.

      Reference model from FEA

      Obtain Necessary Buy-in from Stakeholders
      Using models or pictures to communicate the classification schema simplifies the effort to achieve buy-in. Some key stakeholders need to include those who will use the classification schema to classify assets.
      Submit Classification Schema to Repository

      Once buy-in has happened, the schema needs to be prepared to be entered into the asset repository. A simple tree structure may be prepared from the graphical pictures or models, such as the sample below for the TRM of the FEA.

      The tree structure is then submitted to the repository, whose values are used to classify assets. The tree structure may be represented using the Reusable Asset Specification (RAS). There is a section in RAS which describes simple classification schema structures. The tree structure may also be represented using OWL.

      Classification Schema: Technical Reference Model

      • Service and Access Delivery
        • Access Channels
          • Mobile
          • Wireless
          • Web
        • Delivery Channels
          • Internet
          • Intranet
          • Extranet
        • Service Requirements
          • Section 508
          • Privacy
          • Security
      • Service Framework
        • Service Transport
          • HTTP
          • HTTPS
          • WAP
          • TCP/IP
        • Service Interface
          • SOAP
          • XML
          • UDDI
          • WSDL
        • Component Architecture
          • Security
          • Presentation
          • Business Logic
          • Data Interchange
          • Data Management
      • Service Platforms
        • Java 2 Platform, Enterprise Editions (J2EE)
        • Microsoft Windows .NET
      Practice Asset Classification and Usage
      With the classification schemas configured in the repository, create some practice assets and classifications to verify searching scenarios.
      Refine Classification Schema
      Refine the classification schemas as needed based on lessons learned.
      Key Considerations