PI Training July 2015

Information Technology Solution Engineering/Engineering Process Maturity

Product IntegrationIRM 2.120.3

July 2015

Darren Toyer

Patrick McQuinn

Product Integration | Solution Engineering2

Agenda

• Training Objective• Purpose• Process Overview• Procedure-level details• Contact Information


Training Objective

• To increase understanding of the Product Integration (PI) process and its procedures

Product Integration | ITS4

Agenda


4 Product Integration | Solution Engineering


Purpose

• The purpose of the Product Integration process is to assemble the product from the Product components, ensure that the Product, as integrated, behaves properly (i.e., possesses the required functionality and quality attributes), and deliver the Product.


Agenda



When PI Is Not Done Well…

• Sub-products do not operate together• Increased integration test time• The integration environment can be inadequate to

support the integration activities• Products can be released without component

integration fully tested


PI relationship to other processes – 1

• The PI Process is a mandatory process within the CMMI Engineering Category (IRM 2.120.3)

• The Engineering process areas cover the development and maintenance activities that are shared across engineering disciplines

• Engineering processes are both recursive and iterative

• Recursive – Solves a problem by breaking up a task into smaller and smaller pieces until it can be completed; combine the results. e.g. Looping algorithms

• Iterative – repeating until a task is completed e.g. a loop counter reaches a limit



The Product Integration process relies on:• Requirements Management

• Identifying Interface requirements• Derived requirements resulting from the selected components

• Technical Solution• Government Equipment List (GEL)• Design Specification Report (DSR)• Interface Control Document (ICD)• Define the interfaces and the integration environment • Decision Analysis and Resolution procedure• Make and document significant decisions • Select the Integration sequence and environment


The Product Integration process relies on:• Software Testing, Standards, and Procedures

• Verification Process specific practices • Validation process specific practices • Component and Product Validation

• Configuration/Change Management• Use of Configuration Items• Managing changes

• IT Security management• Establish Security criteria• Establish procedures to evaluate Security



The Product Integration process relies on:• Project Planning

• Provides information about establishing and maintaining plans that define project activities.

• IT Operations Management• Site preparation• Product Installation• Confirms correct operation of installed system



PI Process Flow Diagram


Enterprise Life Cycle• The execution of the Product Integration engineering

process normally occurs through a project’s passage through the ELC

• The next few slides detail what is expected in each ELC Phase to complete PI

PI Relationship to the ELC


Prepare for Product Integration

Vision & Strategy/Enterprise Architecture Phase (Milestone 0)• How do we plan to integrate what we are designing/building into

the existing production environment?

• SP 1.1 Establish an Integration Strategy

• SP 1.2 Establish the PI environment(s)

• Develop Solution Concept

Project Initiation (Milestone 1)• Initial analysis, identification, & assessment of the existing product

and product components to be integrated & existing sequence for integration

• SP 1.3 Establish PI Procedures & Criteria

• Develop Engineering Plan


Prepare for Product Integration (cont.)

Domain Architecture Phase (Milestone 2)• Refine Integration Strategy in the Engineering Plan. How do we

integrate what we are designing/building into the existing production environment? (Solution Concept)

• SP 1.1 Update and maintain the Integration Strategy• SP 1.2 Update and maintain the PI environment(s)• SP 1.3 Update and maintain the PI procedures & criteria• Update Engineering Plan

Preliminary Design Phases (Milestones 3 & 4A)• SP 1.1 Update and maintain the Integration Strategy• SP 1.2 Update and maintain the PI environment(s)• SP 1.3 Update and maintain the PI procedures & criteria• Update Engineering Plan


Ensure Interface Compatibility

Preliminary & Detailed Design Phases (Milestones 3 & 4A)• Comprehensive examinations & review of internal & external

interfaces for completeness • External Interfaces are defined to the physical level• Review interfaces with stakeholder organizations• Interfaces should be managed throughout the project lifecycle

• SP 2.1 Review Interface Description for Completeness

• SP 2.2 Manage Interfaces

• Develop and Update DSR & ICD


Assemble the Product Components & Deliver the Product

Milestone 4b: System Development Phase• Generate final reports, prep integrated product solution for delivery to

the deployment site• Deploy at the production site• Integration Testing & Evaluation• Ensure the product components are delivered to PI environment,

check & confirm components meet description• SP 3.1 Confirm Readiness of Product Components for Integration• SP 3.2 Assemble Product Components• SP 3.3 Evaluate Assembled Product Components• Develop the System Deployment Plan• Develop the Test Plan• Develop Delivery Documentation (VDDs and Transmittals)• Develop Physical Configuration Audit• Develop End-of-Test Completion Report


Planned Maintenance Projects

Maintenance Projects Entering ELC at Milestone Phase 3 • If the project requires acquisition of HW to accomplish the

project’s objectives, adherence to the GEL and PI processes is required

• Formal evaluations are required for adding new technologies, new tools, or new products into the IRS IT environments

• Functional Equivalents may be utilized • Requires an Integration Strategy or sequence

Maintenance Projects Entering ELC at Milestone Phase 4A • Functional Equivalents may be utilized

• Requires an Integration Strategy or sequence

• No formal evaluations are required

PI Tailoring

• The Product Integration process step 1 may be tailored for projects with modest integration need. These projects may document an integration sequence with rationale instead of developing and documenting a full Integration Strategy. All other PI steps may not be tailored.

• All tailoring requests should be submitted in writing to Solution Engineering via the Solution Engineering Front Door.



PI’s Specific Goals

SG3

Assemble Product Components and Deliver The Solution

Verified product components are assembled, and the integrated, verified, and validated product is delivered.

SG2Ensure Interface Compatibility

The product component interfaces, both internal and external, are compatible.

SG1

Prepare For Product Integration

Preparation for product integration is conducted.

.


PI Specific Practices – SG 1 & 2

SG 2Ensure Interface Compatibility

SP 2.1 Review Interface Descriptions for Completeness.

SP 2.2 Manage Interfaces.

SG 1

Prepare for Product IntegrationSP 1.1 Establish an integration strategy.SP 1.2 Establish the Product Integration Environment.SP 1.3 Establish Product Integration Procedures

and Criteria.

.


PI Specific Practices – SG 3

SG 3

Assemble Product Components and Deliver The Product

SP 3.1 Confirm Readiness of Product Components for Integration.

SP 3.2 Assemble Product Components.SP 3.3 Evaluate Assembled Product Components.SP 3.4 Package and Deliver the Product or

Product Component.


PI Roles & Responsibilities 1/2

Role Description Definition of ResponsibilityLead Integrator Responsible for:

• Planning and executing the integration of product components into a Product

Component Designer Responsible for:• Integration of Product components into larger Product

components or into the final Product• Management of component and sub-component

interfaces both internal and external• Design of components and sub-components• Developing all required design documentation

Stakeholder Responsible for:• Ensuring the needs and concerns are considered• These are the specific people or groups who have a

stake, or an interest, in the outcome of the project • The stakeholders may be different for each step or

activity.


PI Roles & Responsibilities 2/2

Role Description Definition of ResponsibilityDeveloper Responsible for:

• Creating and /or modifying code• Performing own unit testing on the created code and notifying

their lead integrator when unit testing is completed• Documenting code• Ensuring that all development work products are completed

Operations Personnel Responsible for: • Site preparation• Product Installation• Confirms correct operation of installed system

Tester Responsible for:• Defined verification tests against requirements

Security Responsible for:• Security Requirements• Security Criteria• Security Procedures


Agenda



PI Process Steps

1. Prepare for Product Integration2. Review Interface Descriptions for Completeness3. Manage Interfaces4. Confirm Readiness of Product Components for Integration5. Assemble Product Components6. Evaluate Assembled Product Components7. Package and Deliver the Product or Product Component


PI Step 1Prepare for Product Integration

Roles: Lead Integrator, Component Designer, Stakeholder

Activities: Identify the Product components to be integrated. Identify the verifications to be performed during the integration of the Product

components. This identification includes verifications to be performed on interfaces.

Identify alternative Product component integration strategies. Developing an Integration Strategy can involve specifying and evaluating several alternative integration strategies or sequences.

Select the best Integration Strategy. Periodically review the product Integration Strategy and revise as needed. Record the rationale for decisions made and deferred.

Outputs: Product Integration Strategy Waivers


PI Step 1Prepare for Product Integration

Lead

Inte

grat

orC

ompo

nent

Des

igne

rTe

ster

Prepare for Product Integration

Start

Step 1:Identify System

Components to be Integrated

Step 4:Select the best

Integration Strategy

Step 5:Periodically review the

solution integration strategy & revise as needed

Step 3:Identify Alternative system

component integration strategies

Step 2:Identify the

verifications to be performed during the

integration

Step 6:Record the rationale for

decisions made and deferred

Step 7:Identify

requirements for the PI environment

Step 8:Identify verification

procedures & criteria for the PI

environment

Step 9:Decide whether to make or buy the needed Product

Integration Environment

Step 10:Develop an Integration

environment (if necessary)

Step 11:Maintain the PI

environment throughout the

project

Step 12:Dispose of portions of environment no longer

useful

Step 13:Establish and Maintain PI procedures for the system

components

Step 14:Establish & Maintain criteria for system component integration &

evaluation

Step 15:Establish & Maintain criteria for validation

& delivery of integration solution

Step 16:Establish & Maintain criteria for

the security of system components in the integration

environment

Step 17:Establish & Maintain procedures

for evaluation of the security components in the integration

environment

Sec

urity

Go to:Review Interface Descriptions for Completeness

Make, Buy, or Re-use for the

needed PI environment

Perform TS GEL Procedure

Buy

Make, Re-use

+

OS:CTO:ES:SE:EPM-PR-PI-FLOW_DIAG1-V0.5-05242013

OS:CTO:ES:SE:EPMMay 24, 2013

ICD

DSR

GEL

Project Planning

Requirements Engineering

IT Security Management


Project Planning


PI Step 2Review Interface Descriptions for Completeness

Roles: Component Designer, Developer, Stakeholder

Activities: Review interface data for completeness and ensure

complete coverage of all interfaces Ensure that Product components and interfaces are marked

to ensure easy and correct connection to the joining Product component

Periodically review the adequacy of interface descriptions

Outputs: Categories of interfaces List of interfaces per category Mapping of the interfaces to the Product components and

the Product Integration environment


PI Step2Review Interface Descriptions for Completeness

Com

pone

nt D

esig

ner

Review Interface Descriptions for Completeness

Step 3:Periodically review

the adequacy of interface

descriptions.

Step 2:Ensure that system

components and interfaces are marked to ensure easy and correct connection to the joining

system component.

Step 1:Review interface data for completeness and

ensure complete coverage of all

interfaces.

Go to:Manage Interfaces

ICD


ICD


OS:CTO:ES:SE:EPMJanuary 31, 2013


PI Step 3Manage Interfaces

Roles: Lead Integrator, Component Designer, Stakeholder

Activities: Identify the interfaces and the requirements that need to be managed Establish the organizational structure for the management of the interfaces Ensure the compatibility of the interfaces throughout the life of the Product Resolve conflict, noncompliance, and change issues Maintain a repository for interface data accessible to project participants

Outputs: Table of relationships among the Product components and the external environment List of agreed-to interfaces defined for each pair of Product components, when

applicable Reports from the interface control working group meetings or equivalent Action items for updating interfaces Application program interface (API) Updated interface description or agreement (ELC Documents: DSR and ICD)


PI Step3Manage Interfaces

Lead

Inte

grat

orC

ompo

nent

Des

igne

r

Manage Interfaces

Step 3:Ensure the compatibility

of the interfaces throughout the life of

the solution.

Step 2:Establish the

organizational structure for the management of

the interfaces.

Step 1:Identify the interfaces and requirements that need to be managed.

Step 5:Maintain a repository

for interface data accessible to project

participants.

Step 4:Resolve conflict,

noncompliance, and change issues.

Go to:Confirm Readiness of System Components

for Integration



Configuration & Change

Management


PI Step 4Confirm Readiness of Product Components for Integration

Roles: Component Designer, Developer, Stakeholder

Activities: Ensure that each received Product component meets its description Check the configuration status against the expected configuration Perform a pre-check (e.g., by a visual inspection, using basic

measures) of all the physical interfaces before connecting Product components together

Check security configurations of the Product components and the integration environment

Outputs: Readiness is verified


PI Step 4Confirm Readiness of Product Components for Integration

Com

pone

nt D

esig

ner

Confirm Readiness of System Components for Integration

Secu

rity

Step 3:Perform a pre-check of

all the physical interfaces before

connecting system components together.

Step 2:Check the configuration

status against the expected configuration.

Step 1:Ensure that each received system

component meets its description.

Step 4:Check security

configurations of the system components.

Go to:Assemble System

Components


OS:CTO:ES:SE:EPMMay 24, 2013

IT Security Management

DSRDSR


PI Step 5Assemble Product Components

Roles: Component Designer, Developer

Activities: Ensure the readiness of the Product Integration

environment Conduct integration in accordance with the Product

Integration strategy, procedures, and criteria Revise the Product Integration strategy, procedures,

and criteria as appropriate

Outputs: Assembled Product or Product components


PI Step 5Assemble Product Components

Lead

Inte

grat

orC

ompo

nent

Des

igne

rAssemble System Components

Step 3:Revise the Product Integration strategy,

procedures, and criteria as appropriate.

Step 2:Conduct integration in accordance with the Product Integration

strategy, procedures, and criteria.

Step 1:Ensure readiness of

the product integration

environment.

Go to:Evaluate Assembled System Components


OS:CTO:ES:SE:EPMDecember 26, 2012


PI Step 6Evaluate Assembled Product Components

Roles: Lead Integrator, Component Designer, Developer, Stakeholder

Activities: Conduct the evaluation of assembled

Product components following the Product Integration test plans

Record the evaluation results

Outputs: Exception reports Interface evaluation reports Product Integration summary reports


PI Step 6Evaluate Assembled Product Components

Test

er

Evaluate Assembled System Components

Step 1:Conduct the evaluation of

assembled system components following the Product Integration test

plans.

Step 2:Record the

evaluation results.

Go to:Package and Deliver the System

and System ComponentsReview Interface Descriptions for

Completeness



DSR

Software Testing Standards

& Procedures


PI Step 7Package & Deliver the Product or Product Components

Roles: Lead Integrator, Component Designer, Stakeholder, Operations Personnel

Activities: Package and deliver the Product Prepare the operational site for product installation Install the Product at the operational site and confirm correct operation Deliver the Product and related documentation and confirm receipt

Outputs: Packaged Product or Product components Delivery documentation

Transmittals Version Description Documents (VDDs)


PI Step 7Package & Deliver the Product or Product Components

Lead

Inte

grat

or

Package and Deliver the System and System Components

Ope

ratio

ns P

erso

nnel

Step 2:Prepare the

operational site for installation of the

solution.

Step 1:Package and deliver

the solution in accordance with

Section 3.2 of the System Deployment

Plan.

Step 3:Deliver the solution

and related documentation and

confirm receipt.

Step 4:Install the solution at the operational site and confirm correct

operation.

End



DSR

IT Operations Management

Product Integration | ITS41

Agenda

• Introduction• Engineering Plan• Process Overview• Procedure-level details• Contact Information

41 Product Integration | Solution Engineering


Contact forProduct Integration Process

PI Training July 2015

Documents

Transcript of PI Training July 2015