Open Group IT4IT Reference Architecture Defect Component

​Purpose

• Keep track of all Defects; including their origin, status, importance, and relation to Requirements and Known Errors.
• Register Defects of all types (including security-related) with all relevant details such as description, severity, application version, related requirement, etc.
• Analyze Defects and find resolution.
• Associate Defects with Requirements.
• Document issues that should be communicated to the Release Composition functional component.
• Consume Defects from the D2C Value Stream Problem functional component as well as the Test functional component that are in turn consumed by the Source Control functional component for review and resolution.
• Update Defect details.
• Decide on target release.
• Report Defect status and provide Defect reports.
• Convert Defects not resolved by service development to Known Errors for Problem Management (D2C Value Stream) to document or develop work-around and report in knowledge management articles.
  

Main Functions

The Defect functional component:

• Shall be the system of record (authoritative source) for all Defects.
• Shall manage the lifecycle of the Defect.
• Shall associate a Defect to a service.
  

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

• Shall associate one or more Service Release Blueprints to one or more Defects which reflects Defects that should be published as Problems/Known Errors.

If a Source Control functional component exists, the Defect functional component:

• Can provide Defect information to the Source Control functional component.

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

• Shall receive Defect information from the Test functional component.
• Shall associate a Test Case to one or more Defects.
  

If a Problem functional component exists, the Defect functional component:

• Shall associate a Known Error to a Defect.
• Shall receive Defect information from a Known Error.