Automated Verification Tools for Complex Launch Vehicle Systems

1
Automated Verification Tools for Complex Launch
Vehicle Systems
Doug Swift UMR PhD Student
2
Contents

• Introduction to Verification
• Verification Process
• Automation

3
Launch Systems
Sea Launch October 1999 DirecTV Satellite Zenit
Rocket From the Equator
4
What Is Verification?

• Sub-discipline within Systems Engineering
• Final check to ensure implementation meets
  original design requirements

5
Verification of Requirements
Verification
Verification
Verification
Verification
6
The Need for Automated Tools

• A good verification program, supported by
  detailed traceability of requirements, is the
  backbone of the Systems Engineering process in
  the latter stages of the program life-cycle
• However, the majority of SE processes and tools
  are directed toward the development of
  requirements
• Verification is largely ignored and there is a
  noticeable lack of good automation tools

7
Verification Process
8
Identify Requirements

• Requirements normally taken from System or
  Segment Specs or ICDs
• Section 4 contains verification matrix
• Every requirement must be verified
• Requirements should be written with verification
  in mind

9
Allocate and Assign

• Five standard methods Test Analysis
  Inspection Demonstration Similarity
• Determines compliance showing requirement is met
• Also must assign organization or person to be
  responsible

10
Verification Plans

• Develop a detailed plan of verification based on
  the allocated method
• Should contain objective, description, success
  criteria, prerequisites, location, and schedule
• If the requirement as written is unverifiable, it
  must be returned for change

11
Perform Verification

• Responsibility of the organization or person
  assigned
• Test, Analysis, Inspection, Demonstration, or
  Similarity
• Usually performed as some steps in a test
  procedure or as part of an analysis

12
Evaluate Results

• Compares test or analysis results against the
  verification plan
• If closure warranted obtains approval signatures
• If fails, then either the requirement must be
  reviewed or a deficiency must be corrected
• Finding a failure is not a failure of the
  Verification Team, but rather an important success

13
Archive Data

• Final step is the accurate and thorough
  documenting and archiving of all evidence
• Complete audit trail

14
Automation Goals

• To automate verification functions and tasks
• To provide improved process control
• To provide tailored status and metrics
• To increase accuracy and reliability

15
Essential Characteristics

• Relational Database
• User Friendly
• PC hosted
• Menu driven
• Checks and balances
• Capability to interact with requirements tools
• Comprehensive capabilities
• Covers all steps of the verification process
• Provides Status and Metrics

16
Verification Engineering Management System
17
Verification Metrics
Number of Verification Closures
Time
18
Seminar Completed
University of Missouri-Rolla