Standards Library Knowledge-Based Study

Study notes

1. The Role of the Standards Library

   In the TOGAF Standard, the Architecture Repository serves as the information asset holding all relevant architecture assets produced by projects or maintained for enterprise reuse. A major structural component of the Architecture Repository is the Standards Library.

   The primary purpose of the Standards Library is to provide a single, controlled repository holding the set of agreed specifications, guidelines, and rules to which architectures and implementations must conform. By establishing an authoritative set of standards, an enterprise achieves:

   • Consistency: Ensures solutions across distinct business units follow compatible architectural patterns.
   • Interoperability: Facilitates seamless integration of services, data, and technology infrastructure.
   • Cost Reduction: Limits supplier diversity and avoids redundant, non-standard tools and platforms.
   • Compliance and Governance: Empowers Architecture Boards to objectively evaluate compliance during Architecture Reviews.

   Categorization of Standards

   An enterprise architecture relies on multiple types of standards to guide business, data, application, and technology design. Standards within the library can originate from external bodies or internal governance structures.

   Key Types of Standards

   • Legal and Regulatory Standards: External mandates imposed by regulatory bodies and statutory authorities (for example, privacy regulations, financial reporting mandates, or statutory accessibility guidelines). Compliance is non-negotiable.
   • Industry Standards: Widely accepted specifications defined by international standards organizations or industry consortia (such as ISO, IEEE, W3C, or The Open Group). They facilitate external interoperability and vendor neutrality.
   • Proprietary and De Facto Standards: Specifications established by dominant market vendors that have achieved broad adoption without formal ratification by an open standard body.
   • Internal Enterprise Standards: Tailored internal guidelines established by the Architecture Board, covering areas such as corporate data governance, software engineering guidelines, and preferred hosting platforms.

   Managing Evolution Through the Standards Lifecycle

   Standards are dynamic; technological advancements, shifting vendor support, and changing business requirements require standards to be actively managed throughout their lifecycle.

   A typical standards lifecycle within the Standards Library follows distinct phases:

   1. Proposed / Candidate: A newly identified standard undergoing pilot evaluation, proof of concept, or assessment by technical committees. It is not yet approved for general deployment.
   2. Active / Current: The standard is formally approved and designated for deployment in new and existing architectures. It may be categorized as Mandatory (mandatory compliance) or Recommended (strongly advised default).
   3. Phased-Out / Deprecated: The standard remains supported for existing production deployments, but must not be used for new solutions. A migration timeline toward an active replacement is typically enforced.
   4. Retired / Withdrawn: The standard is completely decommissioned. Systems relying on it must be retired or remediated, as the standard is no longer supported or permitted in the enterprise.

   Classification Criteria within the Standards Library

   To support searchability and governance, standards in the Standards Library are classified along multiple dimensions:

   • Architecture Domain: Standards are organized by the core architecture domains—Business Standards, Data Standards, Application Standards, and Technology Standards.
   • Conformance Level: Explicit designations governing enforcement:
     • Mandatory: Architectures must conform; deviation requires a formal waiver approved by the Architecture Board.
     • Recommended: Strongly encouraged guideline; deviations require documented justification.
     • Provisional: Assigned to emerging standards undergoing field trials before broad adoption.
   • Lifecycle Status: Clear metadata identifying whether the standard is Candidate, Active, Deprecated, or Retired.

   Practice Question 1

   Which statement best describes the primary purpose of the Standards Library within the TOGAF Architecture Repository?

   • A) It stores the definitive logs of Architecture Board decisions and dispensation records.
   • B) It holds the approved specifications, rules, and guidelines to which architectures must conform.
   • C) It provides the collection of enterprise-specific reference architectures and design patterns.
   • D) It defines the organizational model and skills framework for developing architecture teams.

   Correct Answer: B

   Explanation: The Standards Library explicitly stores the approved criteria, guidelines, and specifications with which architectures and implementations must comply. Option A refers to the Governance Log. Option C describes the Reference Library. Option D refers to the Architecture Capability.

   ---

   
   

   Practice Question 2

   In the lifecycle of a standard within the Standards Library, what is the significance of classifying a standard as "Deprecated" or "Phased-Out"?

   • A) The standard is under active investigation and may only be utilized in pilot projects.
   • B) The standard is approved as mandatory for all newly designed solutions.
   • C) The standard is retained for legacy systems but prohibited from being selected for new solutions.
   • D) The standard has been formally deleted from the repository and can no longer be referenced.

   Correct Answer: C

   Explanation: When a standard is deprecated (phased-out), existing solutions may continue running on it until their scheduled migration or decommissioning, but it cannot be used for any new solution designs. Candidate/Proposed standards correspond to option A, Active/Mandatory to option B, and Retired/Withdrawn to option D.