Implementation

Definition

Implementation

the activity consisting of the cohesive collection of all tasks that are primarily performed to acquire or build individual components

Classification

As illustrated in the preceding figure, Implementation is part of the following inheritance hierarchy:

• Type: Abstract
• Superclass: Engineering Activity
• Subclasses:
  • Application Implementation
  • Business Implementation
  • System Implementation
  • Center Implementation:
    • Contact Center Implementation
    • Data Center Implementation
    • Reuse Center Implementation
  • Component Implementation:
    • Data Component Implementation
    • Hardware Component Implementation
    • Software Component Implementation

Responsibilities

The typical responsibilities of Implementation are to:

• Acquire or build the application’s individual components.
• Acquire or build the business’s individual components.
• Acquire the COTS components.
• Build the data center in accordance with the associated design.
• Create the content (data components) of the application.
• Fabricate the customer special purpose hardware components in accordance with their associated design.
• Program the software components in accordance with the associated design and coding standards.
• Deliver the components to the integration team for deployment on the integration environment.

Preconditions

The implementation activity typically may begin when the following preconditions hold:

• The initiation phase has started.
• The software development team is initially staffed and adequately trained in programming.

Completion Criteria

The implementation activity is typically complete when the following postconditions hold:

• Initial content has been created.
• Software components have been implemented or purchased.
• Hardware components have been fabricated or purchased.

Tasks

The implementation activity typically involves the following producers performing the following implementation tasks:

• Technology Strategy Team, which performs:
  • Technology Strategy Implementation
• Software Development Team, which performs:
  • Acquisition
  • Data Generation
  • Implementation Reuse
  • Programming
  • Debugging
  • Software Internationalization
• Hardware Development Team, which performs:
  • Acquisition
  • Fabrication
  • Implementation Reuse

Environments

The implementation activity is typically performed using the following environment(s) and associated tools:

• Development Environment:
  • UpperCASE Tools
  • LowerCASE Tools
  • Database Management Systems
  • Configuration Management Tools

Work Products

The implementation activity typically results in the production of the implementation work product set:

• Business Engineering:
  • Application
  • Business Data
  • Business Facility
  • Business Organization
  • Business Process
  • Business Relationship
• Application Development:
  • Contact Center (a.k.a., call center)
  • Data Component
  • Data Center
  • Reuse Center
  • Software Component
  • Hardware Component

Phases

Implementation tasks are typically performed during individual phases as documented in the following table:

Guidelines

• COTS components may not save time because of integration problems requiring significant "glue" code.
• This activity is documented using the typical configuration for large projects. It is intended to be configured (i.e., instantiated, extended, and tailored) to meet the needs of specific projects.
• The preconditions of this activity should be the union of the preconditions of its constituent tasks.
• The completion criteria for this activity should be the union of the postconditions of its constituent tasks.