Open Group IT4IT Reference Architecture Requirement Component

Purpose

• Manage Requirements through the lifecycle of a service.
• Service-level requirements are captured as Requirements.
• Collect, refine, scope, and track progress of Requirements even before and after an IT Initiative has concluded.
• Maintain traceability of each Requirement to the original source (demand, IT or business standard or policy, and/or requestor) and to appropriate source and/or test cases throughout the service lifecycle.
• Derive product or program backlogs which will ultimately serve as queues for enhancing IT services.
  

Main Functions

The Requirement functional component:

• Shall be the system of record (authoritative source) for all Requirements.
• Shall manage the lifecycle of the Requirement.
• Shall manage the state of a Requirement.
• Shall allow recursive relationships between Requirements.
• Shall allow hierarchical relationships between Requirements.
• Shall associate a requirement to a service.
  

If a Portfolio Demand functional component exists, the Requirement functional component:

• Shall associate one or more Requirements to a Portfolio Backlog Item that these Requirements originate from.

If a Service Design functional component exists, the Requirement functional component:

• Can manage the data flow to provide Requirement information to the Service Design functional component.
• Shall associate one or more Requirements to a single Logical Service Model.
  

If a Release Composition functional component exists, the Requirement functional component:

• Shall associate one or more Requirements to a Service Release that will fulfill these Requirements.

If a Test functional component exists, the Requirement functional component:

• Shall allow a Requirement to be traced to one or more Test Cases designed to test this Requirement.

If a Policy functional component exists, the Requirement functional component:

• Shall allow one or more Requirements to be associated to one or more policies that these Requirements originate from.

If a Source data object exists, the Requirement functional component:

• Shall allow one or more Requirements to be traced to one or more Sources.