The tutorial knits together the stream of thinking starting withrequirements definition and ending with completion of the verification process andcompletion of flight/ground system testing. The requirements analysis process is linkedwith risk management through validation work, technical performance measurement, andspecification maturity management. The front end and tail end verification processes arediscussed with linkage to the verification planning documentation, procedure development,and report capture. Management aspects are covered with supporting computer tool features.
The presenter offers several competing definitions of the two V words,encourages a particular pair, but cautions that we must be ever vigilant to understand theother person’s vocabulary to avoid confusion and contractual problems. Requirementsvalidation is linked into a program risk management process with technical performancemeasurement (TPM), dual procurement, development evaluation testing (DET), and technologydemonstration. The seldom satisfied need for configuration management of all productrepresentations (mock-ups, simulation, test stands, etc.) during development, not just theengineering drawings, is emphasized.
Intended Audience:
Recommended for engineers with some experience in systems engineering and requirementsanalysis/definition or in test engineering. Engineers recently graduated from college andassigned to systems or test engineering will gain benefit from the tutorial but someexperience working in one of these fields will maximize understanding.
Class Size: Limited to 50 participants. Instructor:Jeff Grady is thePresident of JOG System Engineering, Inc., a systems engineering consulting firm focusedon assessment of company current capability coupled with education leading to plannedimprovements. Formerly, engineering manager of Systems Development at General DynamicsSpace Systems Division working on space transport and energy systems. Other experience hasincluded: system engineer with GD Convair on cruise missiles; system engineer, projectengineer, and field engineer with Teledyne Ryan Aeronautical on unmanned photoreconnaissance, ELINT, SIGINT, electronic warfare, and target aircraft; and customertraining instructor with Librascope on the ASROC and SUBROC underwater fire controlsystems. Served ten years in the U.S. Marines in the aviation communications field.
Author of five recent books on system engineering ( SystemRequirements Analysis , McGraw-Hill, 1993; System Integration , CRC Press, July1994; System Engineering Planning and Enterprise Identity , CRC Press, 1995; SystemValidation and Verification , CRC Press, 1997; and System Engineering Deployment ,CRC Press, 1999) and system engineering papers. Instructor in systems engineeringcertificate programs at University of California San Diego and University of CaliforniaIrvine and in logistics at National University. Member UCSD and UCI System EngineeringCertificate Advisory Boards. He is a charter member of, the first elected Secretary for,and the former founding Journal Editor for, the International Council on SystemsEngineering. Jeff is also a current member of SOLE, SOCE, and IEEE.
Jeff holds a BA in Mathematics from San Diego State University as well as an MS inSystems Management and Certificate in Information Systems from University of SouthernCalifornia.
The tutorial begins with an overview of requirements analysis methodsand the inclusion of the results in specifications followed by translation of them intoverification requirements linked to test, analysis, examination, and demonstrationverification methods. MIL-STD-961D and 498 are used as the tutorial model.
2. Validation Before and During Synthesis (50 mins)
Validation is explained as a risk management discipline to identifyrequirements posing risks for successful synthesis. TPM, TBD management, technologydemonstration, and product representa-tions (models, simulations, mockups, etc.)identification and configuration management are coordinated with item requirements and theevolving design synthesis. The EIA 632 view of requirements and product validation is alsooffered.
3. Verification Front End (50 mins)
Covers identification of verification process requirements, integrationof the verification traceability matrices in all of the specifications into a programcompliance matrix, and partitioning of all verification work into verification tasks ofthe four types.
Verification Planning and Documentation (50 mins)
Documentation stream alternatives are discussed with encourage-ment fordevelopment of an integrated verification plan containing goals, planning data, andprocedures for all four verification methods for component and end-item qualification andacceptance and system testing.
LUNCH ON YOUR OWN (70 mins)
4. Item Qualification Implementation (50 mins)
The component and end item qualification process is coordinated withthe first article manufacturing and testing to minimize schedule and resourcerequirements. Differences between large production programs and those producing only a fewhigh dollar end items are covered. An integrated verification reporting pattern isdiscussed.
5. Item Qualification Management and Audit (25 mins)
The verification process leads to evidence of compliance and thatevidence is presented to the customer at FCA for the qualification process. The use of thetask and compliance matrices in tracking and statusing qualification progress is covered.
6. System Verification (25 mins)
DT&E and OT&E are contrasted to verify compliance with systemrequirements and some would say to validate the product complies with stakeholder needs.
7. Acceptance Test Planning, Acceptance Management, and Audit(30 mins)
Detail specification differences relative to performancespecifica-tions and their use in driving the acceptance process are discussed. Firstarticle results are brought to PCA to complete the item verification process.
8. Process Validation and Verification (30 mins)
System development process design in response to EIA 632 requirementsfollowed by verification using EIA 731 is discussed.