report on def stan 00 42 pt 4 testability
play

Report on Def Stan 00-42 Pt 4 Testability ake consultants - PowerPoint PPT Presentation

Report on Def Stan 00-42 Pt 4 Testability ake consultants Objective 1 Review 00-42 from perspective of an MOD IPT contracting for Testability. Generally inadequate Liaise with MOD R&M for input or requirements. Lead to


  1. Report on Def Stan 00-42 Pt 4 Testability ake consultants

  2. Objective 1  Review 00-42 from perspective of an MOD IPT contracting for Testability.  Generally inadequate  Liaise with MOD R&M for input or requirements.  Lead to understanding of MOD awareness levels  Resulted in the document structure  Compare with IEC 60706-5 Standard  Generally 00-42 has good descriptions but is inadequate: Little substance, Non-prescriptive and ake Recommends seeking guidance from subject experts consultants November 2012

  3. Objective 2  Determine if IEC is alternative to Def Stan  60706: Better Definitions & Terminology  60706: Good descriptions & examples – care need time to understand; not the only way  60706: lengthy and expensive  Conclusion: Rewrite; amalgamate material  Identify other sources of Testability information  Most appropriate would be MHBK 2165  Too detailed for objective ake  Not maintained since 1993 consultants November 2012

  4. Objective 3  Consider whether ESS introduces testability requirements  Looked at HALT/HASS/6-Sigma  Content not included - this committee should consider whether testing techniques or testability  Consider impact of testability on BIT  Material included to address impact on design, reliability, test coverage, diagnostics and retention of results ake consultants November 2012

  5. Objective 4  Deliverable evidence of testability: data retention and future use  Material added to address what should be specified in procurement  Retention of data more appropriate to other procurement guides  Validation of testability requirements  Clauses provided to address testability predictions, performance verification, implications for under- performance ake consultants  Produce draft revision for review November 2012

  6. Overview – Overall Document  New Introduction and Scope  Reviewed References; Rationalised Definitions and Abbreviations from 00-42 and 60706  Restructure the document to facilitate understanding and procurement process  Incorporate material from 00-42, 60706 and other sources ake consultants November 2012

  7. Overview – Assist Understanding  Bring out key points:  Testability Concepts (What is Testability?)  Testability Objectives (Why it is carried out?)  Testability and the Product Life Cycle (When should it be carried out?) ake consultants November 2012

  8. Overview – Assist Procurement  Contracting for Testability: Specification (How should it be specified?)  Contracting for Testability: Testability Criteria (What should be specified?)  Implementing Testability (What does it mean in practice?)  Testability Verification (How should it be assessed?) ake  Testability Risks (What to look out for) consultants November 2012

  9. Summary of Final Document 1  Result:  added new aspects  more precise terminology  clearer purpose and structure  more prescriptive guidance ake  complete and standalone consultants November 2012

  10. Summary of Final Document 2  Issues:  Quite lengthy and wordy – standard + user guide/Annex?  Repetitive due to ‘pick up as required’ structure  Sufficiently prescriptive?  Provide formulae – e.g. FDC, FDP? ake  Need to add section on COTS consultants November 2012

Recommend


More recommend