The IT4IT™ reference architecture by

Language: nld
Format: azw3
Publisher: Van Haren Publishing
Published: 2016-01-25T16:00:00+00:00

Figure 46: Project Functional Component Level 2 Model

6.4.2 Requirement Functional 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.

Key Data Objects

• Requirement (data object): Record which details the needs or conditions to meet for a new or altered service.

Key Attributes

The Requirement data object shall have the following key data attributes:

• RequirementID: Unique identifier of a given Requirement.

• RequirementType: Identifies the category of a Requirement (i.e., epic, theme, feature, user story, non-functional, functional, etc.).

• RequirementSummary: Represents the short description/title/summary of a given Requirement.

• LogicalServiceBlueprintID: Unique identifier of the related Logical Service Blueprint.

• PolicyID: Unique identifier of the related Policy.

• PortfolioBacklogID: Unique identifier of the related Portfolio Backlog Item.

• ServiceReleaseID: Unique identifier of the related Service Release.

• SourceID: Unique identifier of the related Source.

• TestCaseID: Identifier of the related Test Cases.

Key Data Object Relationships

The Requirement data object shall maintain the following relationships:

• Logical Service Blueprint to Requirement (1:n): The Logical Service Blueprint is the Service Design which fulfills one or more Requirements.

• Service Release to Requirement (1:n): The Service Release delivers a service which fulfills one or more Requirements.

• Requirement to Test Case (1:n): A Requirement is traced to one or more Test Cases to ensure stated needs or conditions have been successfully delivered or met.

• Portfolio Backlog Item to Requirement (1:n): A Portfolio Backlog Item is mapped to one or more Requirements which will need to be delivered to successfully fulfill the demand.

• Policy to Requirement (n:m): Requirements may be sourced from policies or may reference policies in order to remain in compliance to previously agreed policies for an organization.

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

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.