Authored by : Hitesh Sanghavi
SEI authorized Lead Appraiser
Hitesh@cunixinfotech.com
Submitted to SEIR (SEI repository)
Legend:
PI: Product Integration
TS: Technical Solution
ICWG: Interface Control Working Group
PC: Product Component
Objectives of PIThe objective of PI is to ensure planned successful assembling of the complete product (or services) from one or more, simple or complex PCs (or service components), ensuring that the product (or services), as integrated, functions properly as intended by design , and deliver/deploy the product (or services) at the end user/customer site.
Where PI applies:
PI SCOPE:
PI deals with achieving complete and functionally successful PI through progressive assembling of PCs, in one or incremental stages, according to defined integration sequence and procedures. PI calls for interface management throughout the project i.e. the management of internal/external interfaces of the products and PCs to ensure compatibility among the interfaces as defined by design team and ICWG.
This process may begin with analysis and simulations (e.g., threads, rapid prototypes, virtual prototypes, and physical prototypes) and steadily progress through increasingly more realistic and incremental functionality until the final product is achieved. To ensure smooth and successful product verification and validation, in each successive build, prototypes (virtual, rapid, or physical) are constructed, evaluated, improved, and reconstructed based upon knowledge gained in the evaluation process.
Inputs to PI from RD:
PI accepts requirements from RD where PCs are combined and interfaces are verified (by ICWG) to ensure that they meet the interface requirements supplied by RD. PI may refer to RD for detail information on interfaces and may refer to RM for information on managing changes to interface requirements.
Impact on RM due to TS-PI interdependencies:
RM fundamentally controls changes to requirements are reflected in the deliverables of other engineering PA’s (due to recursive and dynamic sequence of events by RM) and subsequently in integrated project plans, activities and work products. The table of TS-PI deliverables (at the end of this document) clearly depicts the goal wise deliverables of TS and PI (i.e. the requirements generated by enacting TS-PI activities), the activities which are to be included in the project plan and managed by RM.
Differences in TS-PI Base and Advance practices. (PI does not have advance practices.)
• In TS, SP1.1-1(base practice) “Develop Alternative solutions” is there, on which TS 1.1-2; (advance practice) is built, as “Develop detailed Alternative solutions” which is relatively more demanding. Thus TS 1.1-2 is included in the staged model and it subsumes TS.SP1.1-1(base practice).
• In TS. SP2.3-1(base practice) we have “Establish Interface Descriptions” and in TS.SP2.3-3 (advance practice is built on base practice), we see” Design Interfaces Using Criteria” .Thus TS 1.1-2 is included in the staged model and it subsumes TS.SP2.3-1(base practice).
PI
PI has 3 goals (9 SPs - no base practices) with the respective Deliverables/work products listed. i.e.
a) Prepare for Product Integration
•PI sequence with a rationale for selecting or rejecting the sequence.
•Verified and documented environment for PI
•PI procedures and criteria
b) Ensure Interface Compatibility
•Categories of interfaces and list of interfaces/category
•Mapping interfaces to the PCs and PI environment.
•Table of relationships amongst PCs and between PCs and the external environment.
•List of agreed-to interfaces defined for each pair of PCs.
•Reports from the ICWG meetings.
•Action items for updating interfaces
•Updated interface description and defined APIs
c) Assemble PCs and Deliver the Product
•Acceptance documents for the received PCs
•Delivery receipts/documentation, Checked packing lists
•Exception reports and Waivers
•Assembled product or PCs
•Interface evaluation reports and PI summary reports
•Packaged product
SEI authorized Lead Appraiser
Hitesh@cunixinfotech.com
Submitted to SEIR (SEI repository)
Legend:
PI: Product Integration
TS: Technical Solution
ICWG: Interface Control Working Group
PC: Product Component
Objectives of PIThe objective of PI is to ensure planned successful assembling of the complete product (or services) from one or more, simple or complex PCs (or service components), ensuring that the product (or services), as integrated, functions properly as intended by design , and deliver/deploy the product (or services) at the end user/customer site.
Where PI applies:
PI SCOPE:
PI deals with achieving complete and functionally successful PI through progressive assembling of PCs, in one or incremental stages, according to defined integration sequence and procedures. PI calls for interface management throughout the project i.e. the management of internal/external interfaces of the products and PCs to ensure compatibility among the interfaces as defined by design team and ICWG.
This process may begin with analysis and simulations (e.g., threads, rapid prototypes, virtual prototypes, and physical prototypes) and steadily progress through increasingly more realistic and incremental functionality until the final product is achieved. To ensure smooth and successful product verification and validation, in each successive build, prototypes (virtual, rapid, or physical) are constructed, evaluated, improved, and reconstructed based upon knowledge gained in the evaluation process.
Inputs to PI from RD:
PI accepts requirements from RD where PCs are combined and interfaces are verified (by ICWG) to ensure that they meet the interface requirements supplied by RD. PI may refer to RD for detail information on interfaces and may refer to RM for information on managing changes to interface requirements.
Impact on RM due to TS-PI interdependencies:
RM fundamentally controls changes to requirements are reflected in the deliverables of other engineering PA’s (due to recursive and dynamic sequence of events by RM) and subsequently in integrated project plans, activities and work products. The table of TS-PI deliverables (at the end of this document) clearly depicts the goal wise deliverables of TS and PI (i.e. the requirements generated by enacting TS-PI activities), the activities which are to be included in the project plan and managed by RM.
Differences in TS-PI Base and Advance practices. (PI does not have advance practices.)
• In TS, SP1.1-1(base practice) “Develop Alternative solutions” is there, on which TS 1.1-2; (advance practice) is built, as “Develop detailed Alternative solutions” which is relatively more demanding. Thus TS 1.1-2 is included in the staged model and it subsumes TS.SP1.1-1(base practice).
• In TS. SP2.3-1(base practice) we have “Establish Interface Descriptions” and in TS.SP2.3-3 (advance practice is built on base practice), we see” Design Interfaces Using Criteria” .Thus TS 1.1-2 is included in the staged model and it subsumes TS.SP2.3-1(base practice).
PI
PI has 3 goals (9 SPs - no base practices) with the respective Deliverables/work products listed. i.e.
a) Prepare for Product Integration
•PI sequence with a rationale for selecting or rejecting the sequence.
•Verified and documented environment for PI
•PI procedures and criteria
b) Ensure Interface Compatibility
•Categories of interfaces and list of interfaces/category
•Mapping interfaces to the PCs and PI environment.
•Table of relationships amongst PCs and between PCs and the external environment.
•List of agreed-to interfaces defined for each pair of PCs.
•Reports from the ICWG meetings.
•Action items for updating interfaces
•Updated interface description and defined APIs
c) Assemble PCs and Deliver the Product
•Acceptance documents for the received PCs
•Delivery receipts/documentation, Checked packing lists
•Exception reports and Waivers
•Assembled product or PCs
•Interface evaluation reports and PI summary reports
•Packaged product
Hitesh Sanghvi, MD of Cunix, is an SEI authorized SCAMPI Lead appraiser with rich experience in IT Consulting ,S/w Test Strategies, Software Process Quality, CMM / CMMI, SPI Consulting, Training and appraisals.
0 Responses to “ Product Integration”
Post a Comment