Premium
5.3.2 SPECIFICATION DEVELOPMENT WITHIN THE IPT: A CASE STUDY OF THE F‐22
Author(s) -
Meyer Albert
Publication year - 1995
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.1995.tb01903.x
Subject(s) - new product development , software engineering , process management , concurrent engineering , computer science , process (computing) , audit , flexibility (engineering) , product design specification , formal specification , systems engineering , product (mathematics) , engineering , engineering management , operations management , business , programming language , product design , accounting , management , marketing , geometry , mathematics , economics , scheduling (production processes)
The goal of this paper is to demonstrate how the concurrent engineering method embodied in the Integrated Product Team (IPT) philosophy has impacted the specification development process on the F‐22 program. The article will examine the concurrent engineering process as it applies strictly to specification development.[ 1 ] In particular, the success of the specification development process will be attributed to three main factors: (1) maintaining flexibility in the Preliminary Allocated Baseline (PAB) until Functional Configuration Audit (FCA), (2) Increasing communication and trust between the contractor and the customer by making the customer an integral member of the IPT, and (3) taking advantage of the automated technology to redesign the specification development process. While the F‐22 program is a multi‐corporate endeavor, these principles can be applied to any development effort.]