Software Component

Definition

A software component is an implementation work product consisting of an encapsulated cohesive piece of computer software that:

• Offers a cohesive set of services via one or more interfaces.
• Is designed, implemented, and tested as a unit prior to integration.
• Is part of an application, contact center, or data center.

Objectives

The typical objectives of a software component are to:

• Execute on one or more hardware components.
• Conform to the system requirements and architecture.
• Conform to its design documentation.

Benefits

he typical benefits of software components include:

• Software components enable applications to execute.

Contents

The typical contents of software components include:

• Not Applicable. The contents of a software component depends on the type of component because some software components are the result of integrating other software components.

Stakeholders

The typical stakeholders of a data component include:

• Producer:
  • Software Development Team
• Evaluator:
  • Software Inspection Team
• Approvers:
  • Technical Leader
  • Project Manager
  • Customer Representative
• Maintainer:
  • Software Development Team
• Users:
  • The Development Organization uses the software components to support the development of the application.
  • The Customer Organization uses some software components to support the application.
  • The User Organization uses the software components to obtain the functionality of the application.

Phases

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

Preconditions

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

• The initiation phase is started.
• Software Development Team is staffed.
• The architecture documents are started.
• The software design documents are started.

Inputs

• Work products:
  • Software Architecture Document
  • Database Design Document
  • Human Interface Design Document
• Stakeholders:
  • None

Guidelines

• Software components can include:
  • New software components
  • Commercial of the shelf software components
  • Reusable legacy software components
  • “Glue” software to integrate the software components.

Conventions

Software components are typically constrained by the following conventions:

• Inspection Checklist
• C++ Coding Standards
• HTML Design and Coding Standards
• Java Coding Standards
• Visual Basic Coding Standards
• XML Coding Standards

Examples

• Not Applicable.