Data Component

Definition

A data component is an implementation work product consisting of a cohesive collection of data that is part of the system application, contact center, or data center.

Objectives

The typical objectives of a data component are to:

• Provide basic data stored and minipulated by the application.
• Provide content for user interface and websites to display to users.

Benefits

The typical benefits of data components vary depending on the application:

• Data components enable applications to execute.
• Data components enable user interfaces to present content to users.

Contents

The typical contents of data components include:

• Text
• Numbers
• Images (static and animated)
• Audio files
• Video
• Hyperlinks

Stakeholders

The typical stakeholders of a data component include:

• Producers:
  • Content Management Team
• Evaluators:
  • Database Inspection Team
• Approvers:
  • Technical Leader
  • Project Manager
  • Customer Representative
• Maintainers:
  • Content Management Team
• Users:
  • Applications use data.
  • Users use content.

Phases

• Business Strategy: Not Applicable
• Business Optimization: Not Applicable
• Initiation: Started
• Construction: Completed
• Delivery: Maintained
• Usage: Maintained
• Retirment: Archived

Preconditions

A data component typically can be started if the following preconditions hold:

• The initiation phase is started.
• The system requirements specification (especially the data requirements section) is started.

Inputs

• Work Products:
  • System Requirements Specification
• Stakeholders:
  • Content Creators
  • Content Editors
  • Content Approver
  • Content Publisher

Guidelines

• Data components can be obtained from legacy databases.
• Do not just concentrate on the software and hardware components.
• Use content management.

Conventions

A data component is typically constrained by the following conventions:

• Inspection Checklist

Examples

• Content (published data)
• Internal data that is not visible to the user.