System Functional Review Affordability: In addition to answering the question about the existing budget of the system, you should also ask: Does the updated cost estimate fit within the existing budget? Are adequate processes and metrics in place for the program to succeed? Are the risks known and manageable for development? Is the program schedule executable (technical/cost risks)? Is the updated Cost Analysis Requirements Description (CARD) consistent with the approved functional baseline? Functionality: In addition to asking questions about whether system design can proceed you should also ask: Has the system Functional Baseline been established to enable preliminary design to proceed with proper configuration management? Can the system functional requirements, as disclosed, satisfy the draft Capability Development Document? Has a draft preliminary Software Requirements Specification been defined, with complete verification requirements? Has an initial software architecture design been defined? Is the software functionality in the approved functional baseline consistent with the updated software metrics and resource-loaded schedule? Supportability: In addition to asking questions about whether Supportability requirements are included in specifications you should also ask: Are the program development efforts required to achieve the sustainment key performance parameters, key system attributes, and enabler metrics, along with their corresponding schedules, included in the program documentation and Life-cycle Sustainment Plan? Have the system-level hazards been reviewed and mitigating courses of action been identified? Is the program properly staffed? (DAG, pp. 243-5) Preliminary Design Review Affordability: In addition to asking questions about the existing budget you should also ask:
System Functional Review Affordability: In addition to answering the question about the existing budget of the system, you should also ask: Does the updated cost estimate fit within the existing budget? Are adequate processes and metrics in place for the program to succeed? Are the risks known and manageable for development? Is the program schedule executable (technical/cost risks)? Is the updated Cost Analysis Requirements Description (CARD) consistent with the approved functional baseline? Functionality: In addition to asking questions about whether system design can proceed you should also ask: Has the system Functional Baseline been established to enable preliminary design to proceed with proper configuration management? Can the system functional requirements, as disclosed, satisfy the draft Capability Development Document? Has a draft preliminary Software Requirements Specification been defined, with complete verification requirements? Has an initial software architecture design been defined? Is the software functionality in the approved functional baseline consistent with the updated software metrics and resource-loaded schedule? Supportability: In addition to asking questions about whether Supportability requirements are included in specifications you should also ask: Are the program development efforts required to achieve the sustainment key performance parameters, key system attributes, and enabler metrics, along with their corresponding schedules, included in the program documentation and Life-cycle Sustainment Plan? Have the system-level hazards been reviewed and mitigating courses of action been identified? Is the program properly staffed? (DAG, pp. 243-5) Preliminary Design Review Affordability: In addition to asking questions about the existing budget you should also ask: