System Engineers with Verification Experience
Everett, WA onsite work only
Position type: Fulltime-
Visa: USC/ GC only-
3 New open Positions
Verification Support Engineer
Review verification documentation, identify the data thatverifies each requirement, e.g., section in System Safety Analysis, Section 3 of the SCD, Review ID in 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 Verf. 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 state "Met" Then 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, then update the "Requirement Met -9" attribute to state "Met with Deviation "Then reference the deviation ID in the "Requirement Closeout Rationale -9" attribute.
If the requirement is not met, then update the "Requirement Met -9" attribute to state "Not Met" This may be contingent on an artifact that we have yet to receive from a supplier or adeviation may need to be considered. Otherwise, an ECD would be needed to track closure.
to help align requirements to verification artifacts
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