System Engineers Verification

System Engineers with Verification Experience

Everett, WA onsite work only

Position type:
Full-time

Visa: USC / GC only

3 new open positions

Review verification documentation, identify the data that verifies each requirement, e.g., section in System Safety Analysis, Section 3 of the SCD, Review  supplier verification matrix, etc., and propose updates to the requirements and/or verification module attributes. SCD:
Determine the method and artifact that was used to show compliance is sufficient.

• Example (SCD): requirement met and requirement closeout rationale attributes
• Example (SR&O Verification Module): success criteria met, verification closeout notes, and verification evidence attributes
• Help align requirements to verification artifacts
• If a requirement is met and the EM confirms this, update the Requirement Met
  -9 attribute to stat Met and enter the closeout rationale in the Requirement Closeout Rationale
  -9 attribute
• If the requirement was not met, determine if a deviation is needed; if it has an approved deviation, update the Requirement Met
  -9 attribute to stat Met with deviation and reference the deviation  the Requirement Closeout Rationale
  -9 attribute
• If the requirement is not met, update the Requirement Met
  -9 attribute to stat Not Met; this may be contingent on an artifact not yet received from a supplier or a deviation may need to be considered. Otherwise, an ECD would be needed to track closure
• Need to have access to the relevant DOORS modules
• RRB approval needed before DOORS update is completed
• POC to provide DOORS exports/access to modules, as well as the accompanying verification documentation
• Purchased service to deliver proposed DOORS attribute changes
• RRB Ready Verification Packages