Product Integration Verification Validation · © 2004 Kasse Initiatives, LLC version NDIA CMMI...

SE Product Integration/Ver/Val - 1version NDIA CMMI Conf v2.4© 2004 Kasse Initiatives, LLC

Product IntegrationProduct IntegrationVerificationVerificationValidationValidation


Product IntegrationProduct IntegrationPurposePurpose

�Assemble the product from the productcomponents, ensure the product, asintegrated, functions properly and deliver theproduct.


Product IntegrationProduct IntegrationOverviewOverview

�Product integration may be thought of as aone-time assembly of the product componentsat the conclusion of design phase but it isgenerally conducted incrementally

�Product Integration addresses the integrationof product components into more complexcomponents or into complete products


Integration StrategyIntegration Strategy

�The basis for effective product integration isan integration strategy that uses combinationsof techniques in an incremental manner�An integration strategy should be developed early

in the project, concurrently with productdevelopment plans and specifications

�The integration plan should identify a sequence forreceipt, assembly, and activation of the variouscomponents that make up the product


Integration StrategyIntegration Strategy -- 22

�Establishing the product integration strategyincluding the following:� Integration sequence�Work to be done�Responsibilities for each activity�Resources required�Schedule to be met�Procedures to be followed�Tools required�Environment�Personnel skills


Integration StrategyIntegration Strategy -- 33

�Review the integration strategy withdevelopers and test and integration teams toconfirm its feasibility and revise as necessary

�Document and place under control therationale used for decisions made anddeferred

�Assess the integration strategy on acontinuing basis


Considerations forConsiderations forIntegration TestIntegration TestPlanningPlanning

�What modules should be integrated first?�How many modules should be integrated

before integration testing starts?�What order should be used to integrate the

modules?�Should there be more than one skeleton?

�How is each skeleton defined?�Are there distinct build levels?

�How much testing should be done on eachskeleton?


Product IntegrationProduct IntegrationEnvironmentEnvironment

�Establish and maintain the environmentneeded to support the integration of theproduct components

�The product integration strategy may identifyneeds for an environment that must beacquired or developed

�The product integration environment mayinclude the reuse of existing organizationalresources


Product IntegrationProduct IntegrationEnvironmentEnvironment -- 22

�The environment required at each step of theproduct integration may include:�Test equipment�Simulators�Pieces of real equipment�Recording devices


Detailed ProductDetailed ProductIntegrationIntegrationProceduresProcedures

�Detailed procedures for the integration of theproduct components include such things as:�The number of incremental iterations to be

performed�The details of the expected tests�Other evaluations to be carried out at each stage


Detailed ProductDetailed ProductIntegrationIntegrationProceduresProcedures -- 22

�Detailed criteria�Can include criteria indicating the readiness of a

product component for integration or itsacceptability

�Can be defined for how the product componentsare to be verified and the functions they areexpected to have

�May also include the degree of simulationpermitted for a product component to pass a test

�May describe the environment for the integrationtest

�The details include how the assembledproduct components and final integratedproduct are to be validated and delivered


Ensure InterfaceEnsure InterfaceCompatibilityCompatibility

�Product component interface requirements,specifications, and designs must be managedeffectively to help ensure that all implementedinterfaces will be complete and compatible

�The interfaces should include, in addition toproduct component interfaces, all theinterfaces with the environment as well asother environments for verification, validation,operations, and support


Ensure InterfaceEnsure InterfaceCompatibilityCompatibility -- 22

Pro

duct

Com

pone

nt

Env

ironm

ent

Pro

duct

Com

pone

nt

Interface toEnvironment

Interface toProduct

Component


Review InterfaceReview InterfaceDescriptions forDescriptions forCompletenessCompleteness

�Review all interface data for completeness�Ensure that product components and

interfaces are marked to ensure easy andcorrect connection to the joining productcomponent

�Review the adequacy of interface descriptionson a periodic basis to ensure no deviationbetween the existing descriptions and theproducts being developed, processed,produced or bought


Manage Internal andManage Internal andExternal InterfaceExternal InterfaceDescriptionsDescriptions

�Management of the interfaces includes:�Maintaining the consistency and compatibility of

the interfaces throughout the development cycle�Resolving conflict, noncompliance, and change

issues�Maintaining a repository for interface data that is

accessible to project participants


Confirm Readiness ofConfirm Readiness ofProduct ComponentsProduct Componentsfor Integrationfor Integration

�Confirm that each product component is compliantwith its interface requirements�Ensure that the product components are delivered to

the product integration environment in accordance withthe planned product integration strategy

�Verify the receipt of each product component

�Verify the configuration status of the product componentagainst the expected configuration

�Verify the configuration status of the accompanyinginterface documentation against the expectedconfiguration

�Perform pre-checks of all physical interfaces beforeconnecting product components together


�Assemble and conduct product or product componentcheckout using an iterative approach moving fromthe initial product components through the interimassemblies of product components to the product as awhole

�Checkout includes examining and evaluating theassembled product components for performance,suitability, and readiness

�Ensure that the actual product checkout results arecompared against the expected results

�Verify and validate assembled and checked outproduct components per the integration andverification strategies

Assemble andAssemble andCheckout ProductCheckout ProductComponentsComponents


Apply Verification &Apply Verification &Validation Activities PriorValidation Activities Priorto Packagingto Packaging

�Use verification and validation techniques to:�Ensure that the integrated product meets the

specified requirements�Ensure the project has confidence that the as-built

product will perform its intended functionality in itsintended operational environment

�Verification techniques include inspections,testing, analyses, and demonstration

�Verification methods commonly applied priorto packaging and delivery include:�Load, stress, and performance testing�Functional decomposition based testing�Operational scenario testing


Apply Verification &Apply Verification &Validation Activities PriorValidation Activities Priorto Packagingto Packaging –– 22

�Configuration audits should also be conductedprior to packaging and delivery to ensure that:�The product or product component that is in final

checkout satisfies the customer and productrequirements and all approved change requestsand nothing more

�The documentation that is to be delivered to thecustomer/end user matches the delivered productor product component

�It is recommended that verification andvalidation results that have been conductedthroughout the development lifecycle be usedas input to this final configuration audit


Packaging andPackaging andDeliveryDelivery

�Review the requirements, design, product, testresults, and documentation to ensure thatissues affecting the packaging and delivery ofthe product are identified and resolved

�Prepare the operational site for the installationof the product

�Deliver the product and related documentationand verify receipt

�Install the product at the operational site andverify correct operation

Graphic of Package – Present with Bow


Acceptance TestingAcceptance Testing(Final Verification)(Final Verification)

�The purpose of Acceptance Testing is toconfirm that a product or product componentis ready for operational use

�The Acceptance Test is performed for or inconjunction with someone else to demonstratethat the confidence is justified

�The primary issue is usability and reliability –will the product or product component supportoperational use?

�Acceptance criteria should be discussed andagreed upon in advance of the actualacceptance testing


SummarySummary

�Product Integration presents the concepts toachieve complete product integration throughprogressive assembly of product components,in one stage or in incremental stages,according to a defined integration strategy

�The integration plan should identify asequence for receipt, assembly, and activationof the various components that make up theproduct


SummarySummary -- 22

�Product Integration presents the idea ofapplying (Product Integration, Verification, andValidation) in successive triplets until theproduct is ready for packaging and delivery

�Product Integration stresses the effectivemanagement of all interfaces to ensure that allinterfaces will be complete and compatible


SummarySummary -- 33

�Verification is used to assure that selectedwork products meet their specifiedrequirements

�Verification assures “You built it right”

�Validation is used to demonstrate that aproduct or product component fulfills itsintended use when placed in its intendedoperational environment

�Validation assures “You built the right thing”

Product Integration Verification Validation · © 2004 Kasse Initiatives, LLC version NDIA CMMI...

Documents

Transcript of Product Integration Verification Validation · © 2004 Kasse Initiatives, LLC version NDIA CMMI...