TOGAF: Standards Information Base

From Glitchdata
Jump to navigation Jump to search

Types of Standards

  • Legal and Regulatory Obligations
    • These standards are mandated by law and therefore an enterprise must comply or face serious consequences.
  • Industry Standards
    • These standards are established by industry bodies, such as The Open Group, and are then selected by the enterprise for adoption. Industry Standards offer potential for interoperation and sharing across enterprises, but also fall outside of the control of the enterprise and therefore must be actively monitored.
  • Organizational Standards
    • These standards are set within the organization and are based on business aspiration (e.g., selection of standard applications to support portfolio consolidation). Organizational Standards require processes to allow for exemptions and standards evolution.

Standards Lifecycle

Standards go through a lifecycle process. The 5 stages identified are:

  • Proposed Standard
    • A potential standard has been identified for the organization, but has not yet been evaluated for adoption.
  • Provisional Standard (also known as a Trial Standard)
    • A Provisional Standard has been identified as a potential standard for the organization, but has not been tried and tested to a level where its value is fully understood. Projects wishing to adopt Provisional Standards may do so, but under specific pilot conditions, so that the viability of the standard can be examined in more detail.
  • Standard (also known as an Active Standard)
    • A Standard defines a mainstream solution that should generally be used as the approach of choice.
  • Phasing-Out Standard (also known as a Deprecated Standard)
    • A Phasing-Out Standard is approaching the end of its useful lifecycle. Projects that are re-using existing components can generally continue to make use of Phasing-Out Standards. Deployment of new instances of the Phasing-Out Standard are generally discouraged.
  • Retired Standard (also known as an Obsolete Standard)
    • An Retired Standard is no longer accepted as valid within the landscape. In most cases, remedial action should be taken to remove the Retired Standard from the landscape. Change activity on a Retired Standard should only be accepted as a part of an overall decommissioning plan.

Standards Classification

  • Business Standards
  • Data Standards
  • Application Standards
  • Technology Standards