Home Random Page


CATEGORIES:

BiologyChemistryConstructionCultureEcologyEconomyElectronicsFinanceGeographyHistoryInformaticsLawMathematicsMechanicsMedicineOtherPedagogyPhilosophyPhysicsPolicyPsychologySociologySportTourism






System Requirements Review (SRR).

10.1 General.
The SRRs are normally conducted during the system Concept Exploration or Demonstration and Validation phase. Such reviews may be conducted at any time but normally will be conducted after the accomplishment of functional analysis and preliminary requirements allocation (to operational/maintenance/training Hardware Configuration Items (HWCIs), Computer Software Configuration Items (CSCIs), facility configuration items, manufacturing considerations, personnel and human factors) to determine initial direction and progress of the contractor's System Engineering Management effort and his convergence upon an optimum and complete configuration.

10.2 Purpose.
The total Systems Engineering Management activity and its output shall be reviewed for responsiveness to the Statement of Work and system/subsystem requirements. Contracting agency direction to the contractor will be provided, as necessary, for continuing the technical program and system optimization.

10.3 Items to be Reviewed.
Representative items to be reviewed include the results of the following, as appropriate:

? a. Mission and Requirements Analysis

? b. Functional Flow Analysis

? c. Preliminary Requirements Allocation

? d. System/Cost Effectiveness Analysis

? e. Trade studies (e.g. addressing system functions in mission and support hardware/firmware/software).

? f. Synthesis

? g. Logistics Support Analysis

? h. Specialty Discipline Studies (i.e., hardware and software reliability analysis, maintainability analysis, armament integration, electromagnetic compatibility, survivability/vulnerability (including nuclear), inspection methods/techniques analysis, energy management, environmental considerations).

? i. System Interface Studies

? j. Generation of Specification

? k. Program Risk Analysis

? l. Integrated Test Planning

? m. Producibility Analysis Plans

? n. Technical Performance Measurement Planning

? o. Engineering Integration

? p. Data Management Plans

? q. Configuration Management Plans

? r. System Safety

? s. Human Factors Analysis

? t. Value Engineering Studies

? u. Life Cycle Cost Analysis

? v. Preliminary Manufacturing Plans

? w. Manpower Requirements/Personnel Analysis

? x. Milestone Schedules

10.3.1 The contractor shall describe his progress and problems in:

10.3.1.1 Risk identification and risk ranking (the inter- relationship among system effectiveness analysis, technical performance measurement, intended manufacturing methods, and costs shall be discussed, as appropriate).

10.3.1.2 Risk avoidance/reduction and control (the inter- relationships with trade-off studies, test planning, hardware proofing, and technical performance measurement shall be discussed, as appropriate).

10.3.1.3 Significant trade-offs among stated system/subsystem specification requirements/constraints and resulting engineering design requirements/constraints, manufacturing methods/process constraints, and logistic/cost of ownership requirements/ constraints and unit production cost/design-to-cost objectives.



10.3.1.4 Identifying computer resources of the system and partitioning the system into HWCIs and CSCIs. Include any trade-off studies conducted to evaluate alternative approaches and methods for meeting operational needs and to determine the effects of constraints on the system. Also include any evaluations of logistics, technology, cost, schedule, resource limitations, intelligence estimates, etc., made to determine their impact on the system. In addition, address the following specific trade-offs related to computer resources:

? a. Candidate programming languages and computer architectures evaluated in light of DoD requirements for approved higher order languages and standard instruction set architectures.
b. Alternative approaches evaluated for implementing security requirements. If an approach has been selected, discuss how it is the most economical balance of elements which meet the total system requirements.
c. Alternative approaches identified for achieving the operational and support concepts, and, for joint service programs, opportunities for interservice support.

10.3.1.5 Producibility and manufacturing considerations which could impact the program decision such as critical components, materials and processes, tooling and test equipment development, production testing methods, long lead items, and facilities/ personnel/skills requirements.

10.3.1.6 Significant hazard consideration should be made here to develop requirements and constraints to eliminate or control these system associated hazards.

10.3.2 Information which the contractor identifies as being useful to his analysis and available through the contracting agency shall be requested prior to this review (e.g., prior studies, operational/support factors, cost factors, safety data, test plan(s), etc.). A separate SRR may be conducted for each of the operational support subsystems depending upon the nature and complexity of the program.

1. Post Review Action.
After completing the SRR, the contractor shall publish and distribute copies of Review minutes. The contracting agency officially acknowledges completion of the SRR as indicated in paragraph 4.2.4.

APPENDIX B


Date: 2016-06-13; view: 8


<== previous page | next page ==>
GENERAL REQUIREMENTS | System Design Review (SDR).
doclecture.net - lectures - 2014-2024 year. Copyright infringement or personal data (0.011 sec.)