Integration Engineer

Definition

Integration Engineer
(a.k.a., Build Master)

the role that is played when a person integrates the components of one or more systems or applications

Classification

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

• Type: Concrete
• Superclass: Engineer
• Subclasses:
  • None

Responsibilities

The typical role-specific responsibilities of an Integration Engineer are to:

• Integrate the software and data components.
• Integrate the hardware components.
• Deploy the software and data components on the hardware components.
• Integrate the application with external applications and databases.

Integration Engineers typically inherit common role responsibilities from the role method component.

Expertise

To fulfill these responsibilities, integration engineers typically should have the following expertise, training, and experience:

• Deep knowledge of integration tasks and techniques.
• Deep knowledge of configuration management tools.
• Deep knowledge of integration testing.
• Have significant actual experience successfully integrating system and software components on similar endeavors.
• A bachelor’s degree in software engineering or the equivalent.

Tasks

Integration engineers typically perform the following role-specificdatabase component, software component, hardware component, system component, and external systemstasks in an iterative, incremental, parallel, and time-boxed manner:

• Integration Planning
• Component Integration
• Installation
• Configuration
• Integration Reporting

Integration Engineer typically inherits common role tasks from the role method component.

Teams

Integration engineers typically perform these tasks as members of the following teams:

• Integration Team
• Inspection Teams:
  • Architecture Inspection Team
  • Environments Inspection Team

Work Products

As members of these teams, integration engineers typically produce the following work products:

• Integration Plan
• Application

Guidelines

• Include this role in the endeavor-specific process only if an application consisting of components is to be produced.
• This role typically inherits the common team guidelines from the roles method component.