ASEP Technical Reviews and Audits 2 — Questions and Answers
Question 1: Entry criteria for a formal technical review typically require:
- Customer signature approval of all review package documents in advance
- Completion of all action items generated during the previous major review
- Availability of required review artifacts with products meeting minimum maturity standards (Correct answer)
- Successful completion of all planned integration and testing activities
Correct answer: Availability of required review artifacts with products meeting minimum maturity standards
Entry criteria specify the minimum documentation and product maturity levels that must be met before a review can formally proceed.
Question 2: Exit criteria for a technical review are best described as:
- The complete list of all action items generated and assigned during the review
- Documentation archiving requirements for storing formal review records
- The follow-up schedule for activities to be completed after the review
- Conditions that must be satisfied before the review is formally closed and the program can proceed (Correct answer)
Correct answer: Conditions that must be satisfied before the review is formally closed and the program can proceed
Exit criteria define the specific conditions, including disposition of action items, that must be satisfied to formally close the review and authorize program advancement to the next phase.
Question 3: In the context of technical reviews, 'action items' (sometimes called RIDs, TBDs, or TBRs) are:
- Issues or discrepancies identified during review that must be resolved and tracked to closure (Correct answer)
- Pre-planned agenda tasks assigned to presenters before the review meeting
- Required deliverable documents that must be submitted prior to the review
- Routine administrative tasks assigned to support the review documentation process
Correct answer: Issues or discrepancies identified during review that must be resolved and tracked to closure
Action items capture issues, discrepancies, or unresolved questions identified during the review that must be tracked and resolved to achieve formal review closure.
Question 4: Which configuration audit specifically confirms that the as-built configuration of each configuration item matches the approved product baseline documentation?
- Functional Configuration Audit (FCA)
- Physical Configuration Audit (PCA) (Correct answer)
- Production Readiness Review (PRR)
- System Configuration Review (SCR)
Correct answer: Physical Configuration Audit (PCA)
The PCA verifies that the as-built physical configuration of each configuration item matches its approved product baseline drawings and documentation.
Question 5: The primary purpose of a peer review in systems engineering is to:
- Assess program cost and schedule performance against the baseline plan
- Replace formal milestone reviews when program changes are minor in scope
- Identify defects, issues, and improvement opportunities in work products through structured colleague examination (Correct answer)
- Provide the customer with visibility into technical progress and design maturity
Correct answer: Identify defects, issues, and improvement opportunities in work products through structured colleague examination
Peer reviews use structured examination by qualified technical colleagues to find defects and improvement opportunities early, before products are formally baselined.
Question 6: The Physical Configuration Audit (PCA) is typically conducted:
- After system fabrication is complete and before delivery to the customer (Correct answer)
- At the beginning of the detailed design phase to establish the product baseline
- During the preliminary design phase to validate early design decisions
- Before system integration begins to verify component documentation
Correct answer: After system fabrication is complete and before delivery to the customer
The PCA is conducted after fabrication to verify the as-built product matches all approved design documentation before the product is delivered.
Question 7: Which formal review serves as the decision gate that authorizes transition from preliminary design to detailed design activities?
- System Requirements Review (SRR)
- Critical Design Review (CDR)
- System Design Review (SDR)
- Preliminary Design Review (PDR) (Correct answer)
Correct answer: Preliminary Design Review (PDR)
The PDR is the decision gate that formally assesses preliminary design maturity and authorizes the team to proceed into detailed design activities.
ASEP Technical Reviews and Audits 2
Entry criteria for a formal technical review typically require: