Term
| Other Transaction Authority (OTA) |
|
Definition
| Refers to 10 USC 2371 authority to enter into transactions with other contracts, grants, or cooperative agreements. |
|
|
Term
| Are Other Transaction Authority (OTA) required to comply with the Federal Acquisition Regulation? |
|
Definition
|
|
Term
| Are Other Transaction Authority (OTA) required to comply with the Federal Acquisition Regulation? |
|
Definition
|
|
Term
| What are the expceptional circumstances for OTA? |
|
Definition
| Attract nontraditional defense contractors participating to a signficant extent and exploit the cost-reduction potential of accessing innovative or commercially developed technologies |
|
|
Term
| At least one-third of the total cost of the prototype project is to be paid out of funds provided by the parties to the transaction other than the Federal Government. |
|
Definition
| OTA - Other Transaction Authority (OTA) |
|
|
Term
| Other Transaction Authority (OTA) |
|
Definition
| A nontraditional defense contractor is a business unit that has not, for a period of at least one year prior to the date of the agreement, entered into or performed on 1) any procurement contract that is subject to fully coverage under the cost accounting standards prescribed pursuant to section 26 of the Office of Federal Procurmenet Policy Act (41 USC 422) and the regulations implementing such section: 2. Any other procurement contract in excess of $500,000 to carry out prototype projects or to perform basic, applied, or advanced research projects for the federal agency. |
|
|
Term
| Who is the key participants in Other Transaction Authorities? |
|
Definition
| PMs, A key participant is a business unit that makes a significant contribution to the prototype project, non defense contractors, and senior procurment executivie (SPE) |
|
|
Term
| ICD: Initial Capabilities Document |
|
Definition
| Resolves a specific capability gap, or set of capability gaps, identified through JCIDS analysis process. |
|
|
Term
| ICD: Initial Capabilities Document |
|
Definition
| The capability gap in terms of functional areas, the relevant range of military operations, time, obstacles to overcome and key attributes with approproriate outcome measures of effectiviness, e.g. distance, effect (including scale) etc. |
|
|
Term
| ICD: Initial Capabilities Document |
|
Definition
| The capability gap in terms of functional areas, the relevant range of military operations, time, obstacles to overcome and key attributes with approproriate outcome measures of effectiviness, e.g. distance, effect (including scale) etc. |
|
|
Term
| ICD: Initial Capabilities Document |
|
Definition
| Supports the concpet decision, technology development strategy, Milestone A acquisition decision, further refinement and/or development of integrated architectures and subsequent technology development phases. |
|
|
Term
| ICD: Initial Capabilities Document |
|
Definition
| Non-system specific and non-service, agency or activity specific to ensure capabilities are being developed in consideration of the joint context. |
|
|
Term
| ICD: Initial Capabilities Document |
|
Definition
| Proposes a range of approach(es) based on analysis of the relative cost, efficacy, sustainability, environment, HSI and risk posed by the approach(es) under consideration. |
|
|
Term
| ICD: Initial Capabilities Document |
|
Definition
| No requried to initiate an ACTD or ATD. |
|
|
Term
| Capabilities Dvelopment Document (CDD) |
|
Definition
| Guided by the ICD associated architectures, capability roadmaps, concept refinement and technology development activities. |
|
|
Term
| Capabilities Dvelopment Document (CDD) |
|
Definition
| Captures the information necessary to develop a proposed program(s), normally using an evolutionary acquisition strategy. |
|
|
Term
| Capabilities Dvelopment Document (CDD) |
|
Definition
|
|
Term
| Capabilities Dvelopment Document (CDD) |
|
Definition
| Outline overall strategy to develop capability |
|
|
Term
| Capabilities Dvelopment Document (CDD) |
|
Definition
|
|
Term
| Capabilities Dvelopment Document (CDD) |
|
Definition
| Validated and approved by MSB |
|
|
Term
| Capabilities Dvelopment Document (CDD) |
|
Definition
| Provides the operational peroformance attributes, including supportability and allied and coalition interoperabiltiy fo rthe acq. community to design the proposed system. |
|
|
Term
| Capabilities Production Document (CPD) |
|
Definition
| Addresses the production attributes and quantities specific to a single increment of an acq. program |
|
|
Term
| Joint & IPCO (International Programs and Cooperative Opportunities) |
|
Definition
| Share's cost, risk, look for joint and international programs. |
|
|
Term
| Joint & IPCO (International Programs and Cooperative Opportunities) |
|
Definition
| Share technology capability |
|
|
Term
| Technology Readiness Assessment |
|
Definition
| Examines the program concepts, technology requirements, and demostrated technology capabilities in order to determine technological maturity. |
|
|
Term
|
Definition
| Basic principles observed and reported. Lowest level of S/W readiness. |
|
|
Term
|
Definition
| Technology concept and / or application formulated; invention begins. |
|
|
Term
|
Definition
| Analytical and experiement critical functions and / or characteristic proof of concept; active research and development is initiated |
|
|
Term
|
Definition
| Component and / or breadboard validation in lab environment. Basic components are integrated to establish that they will work together |
|
|
Term
|
Definition
| Component and / or breadboard validation in a relevant environment; Fidelity of breadboard technology increases significantly. The basic technology components are integrated with reasonable realistic supporting elements so it can be tested in a simulated environment. |
|
|
Term
|
Definition
| System / Subsytem model or prototype demonstration in a relevant environment; representive model or prototype system, which is well beyond TRL 5; is tested in a relevant enviroment |
|
|
Term
|
Definition
| System prototype demonstrated in an operational environment |
|
|
Term
|
Definition
| Actual system completed qualified thorugh test and demonstration. Proven to work in its final form and under expected conditions. Represents the end of true system development. |
|
|
Term
|
Definition
| Actual system provem through successful mission operations. |
|
|
Term
| Life Cycle Cost Estimating (LCCE) |
|
Definition
| The estimation of ownership costs shall begin as early as possible. |
|
|
Term
| What should be established prior to program initiation? |
|
Definition
| Life Cycle Cost Estimating (LCCE) |
|
|
Term
| Will be included in the CPD as life-cycle costs. |
|
Definition
| Life Cycle Cost Estimating (LCCE) |
|
|
Term
| Includes all DOTMLPF and policy costs. |
|
Definition
| Life Cycle Cost Estimating (LCCE) |
|
|
Term
| Prototype projects must be directly relevant to weapons or weapon systems proposed to be acquired by the DOD |
|
Definition
| OTA - Other Transaction Authority |
|
|
Term
| What is the critiera for an OTA? |
|
Definition
1. At least one non traditional defense contractor participating to a significant extent in the prototype project.
2. no nontraditional defense contractor is participating |
|
|
Term
| To the maximum extent practicable, competitive procedures shall be used when entering into agreements to carry out prototype projects. |
|
Definition
| OTA - Other Transaction Authority |
|
|
Term
| To the maximum extent practicable, no transaction entered into under this authority provides for reseach that duplicates research being conducted under existing programs carried out by the DoD |
|
Definition
| OTA - Other Transaction Authority |
|
|
Term
| Nontraditional Contractor |
|
Definition
| a business unit that has not, for a period of at least one year prior to the date of the OT agreement, entered into or performed on 1) any procurement contract this is subject to full coverage under the cost accounting standards. 2) any other procurement contract in excess of $500,000 to carry out prototype projects or to perform basic, applied, or advanced reserach projects for a federal agency. |
|
|
Term
| ICD: Initial Capabilities Document |
|
Definition
| Describes capability gaps that exist in joint warfighting functions, as described in the applicable Family of Joint Future Concepts (CONOPS). |
|
|
Term
| ICD: Initial Capabilities Document |
|
Definition
| Establishes a linkage between the key charactestics identified in teh Family of Future Concepts and the capabilities identified in the FAA. |
|
|
Term
| Capabilities Dvelopment Document (CDD) |
|
Definition
| defining authoritative, measureable and testable capabilities needed by warfighters to support the SDD phase of an acq. program. Integrated architecture, applicable JCDs, the ICD. |
|
|
Term
| Capabilities Production Document (CPD) |
|
Definition
| The sponsor's primary means of providing authoritative, testable capabilties for the Production and Deployment Phase of an Acq program. |
|
|
Term
| Capabilities Production Document (CPD) |
|
Definition
| Finalized after design readiness review and is validated and approved before MS C |
|
|
Term
| International Cooperative Program |
|
Definition
| Any acq. system, subsystem, component or technology program with an Acq. Strategy (AS) that includes participation by one or more foreign nations, through an international agreement, during any phase of the system's life cycle. |
|
|
Term
| International Cooperative Program |
|
Definition
| Key objective is to reduce weapons system acq. cost cooperative development, production, and support and to enhance interoperability with coalition partners. |
|
|
Term
|
Definition
Guided by the ICD and AOA
Refine initial concept
develops TDS from the original AOA
Exit: MDA approves |
|
|
Term
| Technology Development Phase |
|
Definition
Guided by the ICD and TD
Reduces technical risk
determines the appropriate technology, develops the CDD
Entry: MSA A approval, TDS approval
Exit: Technical demonstration of a military useful capability "in a relevant environment" capable of being delivered in a relatively short time (typically 5 years for initial capabilty and 4 years for follow on capability) |
|
|
Term
| System Development and Demonstration Phase |
|
Definition
Guided by the CDD and TEMP
Develop the system
Reduce integration and manufacturing risks
ensure operational supportabilty
Design for production
Determine Critical Program (CPI) management and Anti-Tamper
Demonstrate system integration and interoperability
During System Intergration (SI) develop prototypes
During System Development , T&E assess performance against Critical Technical Paramters (CTP) and KPPs and prototypes are "demonstrated in the intended enviorment"
Prepare CPD |
|
|
Term
| System Development and Demonstration Phase |
|
Definition
| Design Readiness Review (DRR); MDA considers # design reviews completed, # drawings completed, planned corrections - approval to proceed to System Development |
|
|
Term
| System Development and Demonstration Phase |
|
Definition
| Entry: MS B approval, technical maturity, approval of requirements, program fully funded, TRL6+ |
|
|
Term
| System Development and Demonstration Phase |
|
Definition
| Exit: "demonstrated in its intended environment" with selected prototype, industrial capabilities are reasonably available, approved requirements are met, meets/exceeds established exit criteria and MS C entrance criteria |
|
|
Term
| Production and Deployment Phase |
|
Definition
Guided by the CPD and TEMP
Achieve operational capabilty
Entry: MS C approval, approved CPD, accetable DT/OA, mature software, "no significant manufacturing risks"
LRIP develops manufacturing capability, provides IOT&E assets, deliveries exceeding 10% of total planned inventory required approval, must have at least one unit
MDA approval requried for FRP (FRPDR) and for IOC |
|
|
Term
|
Definition
| loss will stop warfighter oeprations or direct mission support |
|
|
Term
|
Definition
| basic and necessary for mission accomplishment |
|
|
Term
|
Definition
JITC test interoperability and certifies test results to J-6 with Joint Interoperabilty Test Cert
J-6 validates interoperabilty by issue Joint interoperabitlty Test Cert and the Ineroperability & Supportability (I&S) Cert to DOD CIO |
|
|
Term
|
Definition
| Test interoperability and certifies test results to J-6 with Joint Interoperabilty Test Cert |
|
|
Term
|
Definition
| Validates interoperabilty by issue Joint interoperabitlty Test Cert and the Ineroperability & Supportability (I&S) Cert to DOD CIO |
|
|
Term
| Internatioanl Cooperative Strategy |
|
Definition
Must assess candiates per 10 USC 2350a
-Similar capability either in production or development by US ally
Satifies need or can with mod
Define adv. and disadv
-cost
-program timing
-technology sharing
-standardization and interoperability |
|
|
Term
|
Definition
| Based on constant (base year) dollars |
|
|
Term
|
Definition
| based on statistical regression into Cost Estimating Relationships (CER) |
|
|
Term
|
Definition
| based on historical data of similiar system |
|
|
Term
|
Definition
| based on "bottom up" costing of elements |
|
|
Term
|
Definition
| based on previous cost of same system |
|
|
Term
| Functional Area Analysis (FAA) |
|
Definition
| identifies operational reqruiements to achieve military objectives |
|
|
Term
| Functional Needs Analysis (FNA) |
|
Definition
| idenfies gaps between verified needs and current or programmed capabilities |
|
|
Term
| Functional Solutions Analsyis (FSA) |
|
Definition
| considers materiel and non-materiel solutions that completly satisfy at least one gapped need from the Functional Needs Analysis (FNA) |
|
|
Term
| Post Independent Assessment (PIA) |
|
Definition
| non-advocate review to ensure that prospective solutions list and selected solutions are valid |
|
|
Term
| Initial Capabilities Document (ICD) |
|
Definition
| idenfies the need to resolve a specific capability gap and the range of appropriate solutions |
|
|
Term
| CDD (Capabilities Development Document) |
|
Definition
| identifies an affordable increment of a needed capability, and includes KPPs |
|
|
Term
| Capabilities Production Document (CPD) |
|
Definition
| identifies a specific increment acq. that is to be pursued, and includes KPPs |
|
|
Term
| Joint Capabilities Document (JCD) |
|
Definition
| identifies joints requiring further analysis - may be referenced by several ICDs. |
|
|
Term
| Test and Evaluation (T&E) |
|
Definition
-Assesses performance vs. requirements
-Measures risk
-Identifies deficiencies for corrections |
|
|
Term
| Test and Evaluation (T&E) |
|
Definition
|
|
Term
| Test and Evaluation (T&E) |
|
Definition
| Agrees with SEP, CDD, CPC, and Interoperatbility Support Plan (ISP) |
|
|
Term
| Who is the approval authority for Test and Evaluation (T&E) for DD, DT&E for OSD T&E Oversight prgorams |
|
Definition
| Deputy Director Development T&E |
|
|
Term
| Who is the approval authority for T&E for non-OSD oversight prorams |
|
Definition
| Component Acquisition Executive (CAE) |
|
|
Term
| When must the PM submit the T&E |
|
Definition
| 45 days prior to MS decision |
|
|
Term
-Use to maximum extent feasible
-Does not replace or supplant actual testing, augments
-Interface & Interoperability Risk Reduction
-Development Cost and Schedule Reduction
-T&E Cost Reduction |
|
Definition
| M&S (Modeling & Simulation) |
|
|
Term
|
Definition
| Detailed how to directions |
|
|
Term
|
Definition
| general statement of desired performance and capability |
|
|
Term
|
Definition
-reduces RFP time
-encourages innovative solutions, flexible and nonrestrictive
-Proposals respond with detailed SOW
-Requires detailed, specific evaluation criteria for source selection |
|
|
Term
|
Definition
-peformance requirements only
-pricable objects and objectives
-allow contractor to exercise maximum flexiblity in propsal response
-allow contractor to sue commerical or military specs and standards
-allow contractor to make data product recommendations
-allow contractor to propose schedule (except IOC) |
|
|
Term
| Section ___ evaluation criteria must include price |
|
Definition
|
|
Term
| Section __ evaluation criteria must include price, but should be deemphasized IAW |
|
Definition
FAR 15.304(e).
All Evaluation Factors other than price when combined are signficantly more important than price |
|
|
Term
| Removes Risk to contractor |
|
Definition
|
|
Term
| tied to desired peroformance or behavior or result, contractor controls risk |
|
Definition
|
|
Term
| Subjective, requires periodic eval and award fee based on results and quality of performance |
|
Definition
|
|
Term
| Less risky to USG, used when processes and product is stablized |
|
Definition
|
|
Term
| Less risky to the contractor, used when outcome uncertain or amount of work product required is not well defined - encourages businesses to participate |
|
Definition
|
|
Term
Applies to Prototype
Not subject to Federal Laws and Regulations per 10 USC 2371
Advanced payments are allowed |
|
Definition
| OTA - Other Transaction Authority |
|
|
Term
| Exploits innovative or commerically developed technologies |
|
Definition
| Other Transaction Authority (OTA) |
|
|
Term
| Encourages technology driven prototype efforts at lower TOCs with Quicker fielding |
|
Definition
| Other Transaction Authority (OTA) |
|
|
Term
Stresses:
Competition
No duplication with ongoing or existing efforts
Involve counsel to protect USG |
|
Definition
| Other Transaction Authority (OTA) |
|
|
Term
Requirements:
At least one non-traditional contractor (no DoD contract in at least a year)
No non-traditional contractors, but either
1/3 funds not USG, or
exceptional circumstances |
|
Definition
| Other Transaction Authority (OTA) |
|
|
Term
| Mandatory per DoDI 5000.64 |
|
Definition
| Unique Identification (UID) |
|
|
Term
New Equipment, Major Modifications, and Reprocurements
-Acq cost >$5000
-Serially managed, mission essential, controlled inventory |
|
Definition
| Unique Identification (UID) |
|
|
Term
| Can leverage existing serialization systems with approval |
|
Definition
| Unique Identification (UID) |
|
|
Term
| Not intended to be held for sale or consumed in normal operations |
|
Definition
|
|
Term
| Subject to Depot of Field Level economical repair |
|
Definition
|
|
Term
| Normally expended or used beyond recovery |
|
Definition
|
|
Term
| Composted of or pertaining to physical substances |
|
Definition
|
|
Term
| Based on then year dollars escalated for each FY |
|
Definition
| Program Objective Memorandum (POM) |
|
|
Term
| Any program, subprogram, modification, project or subproject not previously justified by DoD and funded by Congress thorugh the normal budget process |
|
Definition
|
|
Term
| Obtained required approval for funds realignment from Congressional Defense Committees via DD 1415.1 - prior approval (PA) reprogramming actions |
|
Definition
|
|
Term
| Required for ALL USG agencies (not just DoD) |
|
Definition
|
|
Term
| Covers IT/IA requirements |
|
Definition
|
|
Term
DOD CIO Certification to Congress
Program Economic Analysis
Prior to MSA, MSB, or FRPDR |
|
Definition
| Clinger-Cohen Act (CCA)for MAIS Requirements |
|
|
Term
Component CIO Confirmation to DOD CIO and MDA
LCCE
Prior to MSA, MSB, or FRPDR |
|
Definition
| MDAP Requirements for Clinger-Cohen Act (CCA) |
|
|
Term
| Allocate, Deconflict Frequencies and Bands to accomdate Specific Electronic functions |
|
Definition
|
|
Term
| Ensures compliance with national policies |
|
Definition
|
|
Term
| Ensures Sprectrum availability |
|
Definition
|
|
Term
| PM submits _______ Request for Frequency Spectrum Allocation to get _____ registry number. |
|
Definition
|
|
Term
Authorizes Frequency Spectrum Allocation Certification
Assigns interim frequencies issued for development efforts
Assigns final operational frequencies after MS C |
|
Definition
| Natl Telecommunication and Information Administration (NTIA) |
|
|
Term
| MDA's and PMs shall tailor program strategies and oversight, including documentation of program inforamtion, acq. phases, the timing and scope of decision reviews, and decision levels, to fit the particular conditions of that program, consistent with applicable laws and regulations and the time sensitivity of the capability need |
|
Definition
|
|
Term
| Advanced technology shall be integrated into producible systems and deployed in the shortest time practicable. Approved, time-phased capability needs matched with the available technology and resources enable evolutionary acq. strategies. Evolution acq strategies are the preferred approach to satisfying operational needs. Sprial development is the preferred process for executing such strategies. |
|
Definition
|
|
Term
| System, units, and forces shall be able to provide and accept data, information, materiel, and services to and from other systems, units and forces and shall effectively interoperate with other US Forces and coalition partners. Joint concepts and integrated architectures shall be used to characterize these interrelationships. |
|
Definition
|
|
Term
| To maximize competition, innovation, and interoperability, and to enable greater flexiblity in capitalizing on comercial technologies to reduce cost, acq. managers shall consider and use ______ ______ _______strategies for acquiring and sustaining products and services whenever feasible. |
|
Definition
| Performanced-Based Acquisition |
|
|
Term
| Purpose is to develop a system or increment of capability; reduce integration and manufacturing risk (technology risk reduction occurs during Technology Development); ensure operational supportability particular attention to reducing the logistics footprint, implement human systems integration (HSI); design for producibility; ensure affordablity and protection of critical program information (CPI) (anti-tamper); and demonstrate system integration, interoperability, safety and utility |
|
Definition
| System Development and Demonstration |
|
|
Term
| A system acq. strategy and test evaluation master plan (TEMP) |
|
Definition
| System Development and Demonstration |
|
|
Term
| Dedicate Initial Operation Test and Evaluation (IOT&E) required |
|
Definition
| System Development and Demonstration |
|
|
Term
| Who approves live fire test and evaluation (LFT&E) stategy shall LFT&E |
|
Definition
| A Director, Operational Test & Evaluation (DOT&E) |
|
|
Term
| Follow-on Operational Test and Evaluation (FOT&E) required |
|
Definition
| System Development and Demonstration |
|
|
Term
| What are the two major efforts for System Development and Demonstration |
|
Definition
| System Integration and System Demonstration |
|
|
Term
| What is the entrance point for System Development and Demonstration? |
|
Definition
|
|
Term
| What is the milestone for initiation of an acq. program |
|
Definition
| MS B System Development and Demonstration |
|
|
Term
| What is the System Development and Demonstration (SDD) entrance criteria? |
|
Definition
Depends on technology maturity
approved requirements and funding |
|
|
Term
| Programs that enter MS __ shall have an ____ and a _____ that describes specific program requirements |
|
Definition
|
|
Term
| The ___________ and ________ of technology risk, which allows less costly and less time consuming systems development is a crucial part of overall program management and is especially relevant to meeting _____ and _____ goals. |
|
Definition
management and mitigation
cost and schedule |
|
|
Term
| Prior to __________ __________ and ________, users shall identify the requirements. |
|
Definition
| System Development and Demonstration |
|
|
Term
| An approved minimum set of _______, included in the ______ will guide the efforts of the System Development and Demonstration phase |
|
Definition
|
|
Term
| At Milestone ____, the PM shall prepare and the _____ shall approve an _______ ________ to guide acty during the SDD. |
|
Definition
| B, MDA, Acquisition Strategy |
|
|
Term
| At what Milestone is the evolutionary acq program begins? |
|
Definition
|
|
Term
| At what milestone does the production resulting from the evolutionary acq increment begin? |
|
Definition
|
|
Term
| Each program or increment shall have an _______ ________ ______. |
|
Definition
| Acquisition Program Baseline (APB) |
|
|
Term
| Esablished program goals thresholds and objectives for the mimimum number, cost, schedule and performance parameters describe the program overall life cycle |
|
Definition
| Acquisition Program Baseline (APB) |
|
|
Term
| PM has been assigned, requriements have been approved, and system level development is ready to begin. |
|
Definition
| SDD - System Development and Demonstration |
|
|
Term
| Transition into _______ _______ and ____ requires full funding needed for all current and future efforts to carry out the acq. strategy in the budget and out year program |
|
Definition
| System Development and Demonstration |
|
|
Term
| Effort to integrate subsystems, complete design, and reduce system level risk. The program shall enter ______ _______ when the PM has a technical solution for the system, but has not yet integrated the subsystems into a complete system. |
|
Definition
|
|
Term
| What document guides the System Integration effort which typically includes the demonstration of prototype articles or engineering development models (EDM) |
|
Definition
|
|
Term
| What provides an opportunity for mid-phase assessemnt of design maturity? |
|
Definition
|
|
Term
| The successfull completion of the ____ _____ ____ ends System Integration and continues the SDD phase into the System Demonstration? |
|
Definition
| Design Readiness Review (DRR) |
|
|
Term
| Demonstrates the ability of the system to operate in a useful way consistent with approved KPPs |
|
Definition
|
|
Term
| The program shall enter _____ _____ when the PM has demonstrated the sytem in prototypes or EDMs. |
|
Definition
|
|
Term
| This effor shall end _____ _____ once proven in its intended environment and the system meets or exceeds exit crieria and MS _____ entrance requirements. |
|
Definition
|
|
Term
| DoD may not conduct operational testing (i.e. oeprational assessment (OA), IOT&E or FOT&E) until ______ approves |
|
Definition
|
|
Term
| Overarching process that a program team applies to transition from stated capability need to an operationally effective and suitable system. |
|
Definition
|
|
Term
| Encompasses the application of ____ ____ processes across the acq life cycle and is intended to be the integrating mechanism for balanced solutions addressed capability needs, design considerations and constraints as well as lmitation imposed by technology, budget, and schedule. |
|
Definition
|
|
Term
| Applied early in concept defintion and continuous throughout total life cylce. |
|
Definition
|
|
Term
| An interdisplinary approach or a structured, disciplined, and documented technical effort to simultaneously design and develop systems and products and processes to satisfy the needs of the customer. |
|
Definition
|
|
Term
| Transforms needed operational capabilities into an integrated system design througout concurrent consideration of all life cycle needs |
|
Definition
|
|
Term
| Provides a systematic set of processes to help coordinate and integrate actys througout the life cycle of the system |
|
Definition
|
|
Term
| The _______shall implement a robust SE approach to translate operational needs and capabilities into operationally suitable increments of a system |
|
Definition
|
|
Term
| Translates user-defined capabilities into operational system specs consistent with cost, schedule and performance constraints |
|
Definition
|
|
Term
| Is the planning for and management of the entire acq. life cycle of a DOD system? |
|
Definition
| Total Life Cycle Systems Management (TLCSM) |
|
|
Term
| Who is the single point of accountability for accomplishing program objectives for total Lifecycle systems management, including sustainment? |
|
Definition
|
|
Term
| Who shall apply human systems integration (HSI) to optimize total system performance (h/w, s/w and human) operational effectiveness, suitablity, survivability, safety and affordabilty? |
|
Definition
|
|
Term
| When does Planning for Operation and Support and the estimation of total ownership costs begin? |
|
Definition
|
|
Term
| What is a key component of performance and when is it considered? |
|
Definition
| Supportabilty, throughout the system life cycle |
|
|
Term
| What management considerations should permeate the decision making of all acq functions and communities? |
|
Definition
| TLCSM Total Life Cycle Systems Management |
|
|
Term
| What management considerations should permeate the decision making of all acq functions and communities? |
|
Definition
| TLCSM Total Life Cycle Systems Management |
|
|
Term
| What shoudd be considered for framing the decision making for sustainment logistics? |
|
Definition
| Total Life Cycle Systems Managmeent (TLCSM) |
|
|
Term
| TLCSM factors should be considered by the participants in the _______ even before the PM is assigned. |
|
Definition
|
|
Term
| _______ determination of performance capabilties whould reflect ______ considerations. |
|
Definition
|
|
Term
-Single point of accountability
-Evolutionary Acq
-Supportabilty and sustainment as key elements of performance
-Performanced based startegies, incl. logistics
-Increased Reability and reduced logistics footprint
-Continuing reviews of sustainment strategies |
|
Definition
| TLCSM Total Life Cycle Systems Management |
|
|
Term
| Established early in the program defintion stages and updated periodically as the program matuers. |
|
Definition
| Systems Engineering Plan (SEP) |
|
|
Term
| The overall SE stragey should be addressed and integrated with al other program strategies |
|
Definition
| Systems Engineering Plan (SEP) |
|
|
Term
| SE enables TLCSM, and provides the framework to aid decision making about trade offs between system performance, cost and schedule |
|
Definition
| Systems Engineering Plan (SEP) |
|
|
Term
| Should be applied at the inital stages of program formulation to provide the integrated technical basis for program strategies; acq. plans, acq. decisions, mangement of requirements, risks and design trades, integration of engineering, logistics, test, and cost estimation efforts among all stakeholders |
|
Definition
|
|
Term
| The ______ business approach means that all major materiel alternative considerations and major acq. functional decisions reflect an understanding of the effects and consequences of these decisions on Operations and Sustainment phase (including disposal) system effectiveness and affordability |
|
Definition
|
|
Term
| A management technique that uses multi-displanary teams (IPTs) to optimize design, manufacturing, and supportabilty processes |
|
Definition
| Integrated Product and Process Development IPPD) |
|
|
Term
| Facilitates meeting cost and performance objectives from system concept out through production and field support. |
|
Definition
| Integrated Product and Process Development IPPD) |
|
|
Term
| Broad, interdisplanary approach that includes not only the engineers, techical specialists, and customers in the IPTs, but also BFMs |
|
Definition
| Integrated Product and Process Development IPPD) |
|
|
Term
| SE System Life Cycle Processes |
|
Definition
|
|
Term
| Processes for Engineering a System |
|
Definition
|
|
Term
|
Definition
|
|
Term
| Application and Management of the SE Process |
|
Definition
|
|
Term
| What are the three SE standards that represent different levels of application? |
|
Definition
-The International Organization for Standardization / International Electrotechnical Commission (ISO/IEC) 15288, SE System Life Cycle Processes
-The Electronic Industry Alliance (EIA) 632, Processes for Engineering
-The Institute of Electrical and Electronic Engineers (IEEE) 1220 |
|
|
Term
| Covers the life cycle of a man-made system from concept through retirement. "It provides the processes for acquiring and supplying system products and services that are configured from one or more of the following types of system components: hardware, software, and humans. In addition, the framework provides for the assessment and improvement of the life cycle." This standard is designed to be used by an organization, a project within an organization, or an acquirer and a supplier via an agreement. |
|
Definition
| The International Organization for Standardization/International Electrotechnical Commission (ISO/IEC) 15288, SE-System Life Cycle Processes |
|
|
Term
| Defines the set of requirements for engineering a system. The processes in EIA 632 describe "what to do" with respect to the processes for engineering a system, which is the next level down from the ISO/IEC 15288 level of system life cycle processes. |
|
Definition
| The Electronic Industry Alliance (EIA) 632, Processes for Engineering a System |
|
|
Term
| Defines a SE process. It gives the next level of detail below the process requirements described in EIA 632. The process is described more at the task or application level. IEEE 1220 does not worry about "who does what" as some of the other standards do with the "acquirer-supplier" concepts. |
|
Definition
| The Institute of Electrical and Electronic Engineers (IEEE) |
|
|
Term
| To actually accomplish __________ _________, an organization would most likely need all three standards or a hybrid model of their own. |
|
Definition
|
|
Term
-Decision Analysis
-Technical Planning
-Technical Assessment
-Requirements Management
-Risk Management
-Configuration Management
-Technical Data Management
-Interface Management |
|
Definition
| Technical Management Processes |
|
|
Term
-Requirements Development
-Logical Analysis
-Design Solutions
-Implementation
-Integration
-Verification
-Validation
-Transition |
|
Definition
|
|
Term
| The PM uses ______ ________ processes to manage the technical development of the system increments, including the supporting or enabling systems |
|
Definition
| Technical Management Processes |
|
|
Term
| Provide the basis for evaluating and selecting alternatives when decisions need to be made. DA involves selecting the criteria for the decision and the methods to be used in conducting the analysis. These analyses include, but are not limited to, trade studies, models and simulation, supportability analysis, level of repair analysis, post fielding support analysis, repair versus discard, and cost analysis. |
|
Definition
|
|
Term
| Ensures that the SE processes are applied properly throughout a system's life cycle. Addresses the scope of the technical effort required to develop the system. A mandated tool for this activity is the SE Plan. Required for each of the technical processes. For Implementation, Integration, Verification, Validation, and Transition processes and their accompanying systems can reveal constraints and interfaces that will result in derived technical requirements. |
|
Definition
|
|
Term
| Activities that measure technical progress and the effectiveness of plans and requirements, activities within Technical Assessment include the activities associated with Technical Performance Measurement and the conduct of technical reviews;. a structured review process should demonstrate and confirm completion of required accomplishments and exit criteria as defined in program and system planning, activities discover deficiencies or anomalies that often result in the application of corrective action. |
|
Definition
|
|
Term
| Provides traceability back to user-defined capabilities as documented through the JCIDS. In evolutionary acquisition, the management of requirements definition and changes to requirements takes on an added dimension of complexity. The PM should institute to (1) maintain the traceability of all requirements from capabilities needs, (2) to document all changes to those requirements, and (3) to record the rationale for those changes. Emerging technologies and threats can influence the requirements in the current as well as future increments of the system. |
|
Definition
|
|
Term
| In SE examines the risks of deviating from the program plan. It examines all aspects of the program, from conception to disposal, early in the program and in relation to each other. Most approaches have in common the practice of integrating design (performance) requirements with other Lifecycle issues such as manufacturing, operations, Environment, Safety, and Occupational Health considerations, and support. |
|
Definition
|
|
Term
| Is the application of sound business practices to establish and maintain consistency of a product's attributes with its requirements and product configuration information. It involves interaction among government and contractor program functions such as SE, design engineering, logistics, contracting, and manufacturing in an IPT environment. Includes system hardware, software, and documentation (data). |
|
Definition
|
|
Term
| Refers to the information necessary for or associated with product development and sustainment, including the data associated with system development; modeling and simulation used in development or test; test and evaluation; installation; parts; spares; repairs; usage data required for product sustainment; and source and/or supplier data. Data specifically not included would be data relating to tactical operations information; sensor or communications information; financial transactions; personnel data; transactional data; and other data of a purely business nature. |
|
Definition
|
|
Term
Defense system data are acquired when needed to support the acquisition, operations, maintenance, or disposal of the system and to evaluate contractor performance. The applied SE process requires access to data to facilitate decision making, but does not necessarily require acquisition of all data. The data management processes assist in decision-making. Data management processes reveal the proper data to be acquired or accessed. The decision to purchase data should be made when access to required data is not sufficient to provide for life-cycle planning and system maintenance. The cost of data delivery should be a primary consideration. Other considerations include the following:
-Data requirements for spare and repair parts;
-Technical data needed for ordering and purchasing items for contingencies; and
-Circumstances under which the data may evolve over time to more useful or updated data. |
|
Definition
|
|
Term
| The PM is responsible for protecting system data, whether the data are stored and managed by the government or by contractors. The DoD policy with regard to data protection, marking, and release can be found in DoD Directive 5230.24, DoD Directive 5230.25, and DoD 5400.7-R. Data containing information subject to restrictions are required to be protected in accordance with the appropriate guidance, contract, or agreement. Guidance on distribution statements, restrictive markings, and restrictions on use, release, or disclosure, of data can be found in the DFARS Part 252.227-7013 & 7014, and DoD Directive 5230.24. When digital data are used, the data should display applicable restriction markings, legends, and distribution statements clearly visible when the data are first opened or accessed. These safeguards not only assure government compliance with use of data, they also guarantee and safeguard contractor data that are delivered to the government, and extend responsibilities of data handling and use to parties who subsequently use the data. |
|
Definition
|
|
Term
| The PM also has responsibility for addressing long-term storage and retrieval of data and associated program information - planning for digitizing continued need information, as appropriate and cost-effective. Such long-term planning and incremental digitization, as required, will assure that applicable data is available, preserved, and migrated to successive formats for future planning and use |
|
Definition
|
|
Term
| The process ensures interface definition and compliance among the elements that compose the system, as well as with other systems with which the system or system elements must interoperate. Control measures ensure that all internal and external interface requirement changes are properly documented in accordance with the configuration management plan and communicated to all affected configuration items. |
|
Definition
|
|
Term
| What does the risk management effort address? |
|
Definition
Risk Planning
Risk Assessment
Risk Handling and mitigation strategies and
Risk Monitoring Approaches |
|
|
Term
Includes identification and analysis of potential sources of risk to the program plan, including, but not limited to, cost, performance, and schedule risks based on such factors as:
-The technology being used and its related design;
-Manufacturing capabilities;
-Potential industry sources; and
-Test and support processes. |
|
Definition
|
|
Term
The PM should identify:
-Identify contract vehicles which involve the transfer of sensitive data and technology to partner suppliers;
-Evaluate the risks that unfavorable export of certain technologies could pose for the program; and
-Develop alternatives to mitigate those risks |
|
Definition
|
|
Term
| A _______ _______process guides the system products, processes, and related documentation, and facilitates the development of open systems. Configuration Management efforts result in a complete audit trail of decisions and design modifications. |
|
Definition
|
|
Term
| Provides total life cycle configuration management planning for the program/project and manages the implementation of that planning; |
|
Definition
| Configuration Management Planning and Management |
|
|
Term
| Establishes a structure for products and product configuration; selects, defines, documents, and baselines product attributes; and assigns unique identifiers to each product and product configuration information item; |
|
Definition
| Configuration Identification |
|
|
Term
| Ensures that changes to a configuration baseline are properly identified, recorded, evaluated, approved or disapproved, and incorporated and verified, as appropriate; |
|
Definition
| Configuration Change Control |
|
|
Term
| Manages the capture and maintenance of product configuration information necessary to account for the configuration of a product throughout the product life cycle; |
|
Definition
| Configuration Status Accounting |
|
|
Term
| Establishes that the performance and functional requirements defined in the product definition information have been achieved by the design and that the design has been accurately documented in the product definition information. |
|
Definition
| Configuration Verification and Audit |
|
|
Term
| The program manger uses _______ _________ to design the system, subsystems, and components, including the supporting or enabling systems required to produce, support, operate, or dispose of a system. (The terminology used to indicate a subsystem is system element, component, or configuration item, depending on the SE context and phase of acquisition under discussion.) |
|
Definition
|
|
Term
|
Definition
| The process takes all inputs from relevant stakeholders and translates the inputs into technical requirements. DoD systems engineers primarily respond to the JCIDS(JCIDS) documents that identify capability gaps in need of a materiel solution. The PM should work with the user to establish and refine operational needs, attributes, performance parameters, and constraints that flow from JCIDS-described capabilities, and then ensure that all relevant requirements are addressed |
|
|
Term
|
Definition
-Performance parameter objectives and thresholds;
-Affordability constraints;
-Scheduling constraints; and
-Technical constraints |
|
|
Term
|
Definition
| The process of obtaining sets of logical solutions to improve understanding of the defined requirements and the relationships among the requirements (e.g., functional, behavioral, temporal). Once the logical solution sets are formed, the engineers allocate performance parameters and constraints, and then define derived technical requirements to be used for the system design |
|
|
Term
|
Definition
Process translates the outputs of the Requirements Development and Logical Analysis processes into alternative design solutions and selects a final design solution. The alternative design solutions include:
-People, products, and process entities; and
-Related internal and external interfaces. |
|
|
Term
|
Definition
________ ________ should be sufficiently detailed to allow the following:
-Confirmation of upward and downward traceability of requirements;
-Confirmation of interoperability and open system performance requirements; and
-Demonstration of the appropriate products to satisfy the applicable acquisition phase exit criteria. |
|
|
Term
| The process that actually yields the lowest level system elements in the system hierarchy. The system element is made, bought, or reused. Making it involves the hardware fabrication processes of forming, removing, joining, and finishing; or the software processes of coding, etc. If implementation involves a production process, a manufacturing system is required to be developed using these same technical and technical management processes. Depending on the technologies and systems chosen when a decision is made to produce a system element, the Implementation process imposes constraints on the Design Solution process. If the decision is made to purchase or reuse an existing system element, the Implementation process may involve some adaptation or adjustments to the system element. |
|
Definition
|
|
Term
| The _______ _______ gets the system element ready for the processes of Integration, Verification, and Validation. It should include some testing of the implemented system element before the element passes to the Integration Process. May also involve packaging, handling, and storage, depending on where or when the system element needs to be integrated into a higher-level assembly. Developing the supporting documentation for the system element--such as the manuals for operations, maintenance, and/or installation--are also a part of this process. |
|
Definition
|
|
Term
|
Definition
| The process of incorporating the lower-level system elements into a higher-level system element in the physical architecture. The plan or strategy for this process, including the assembly sequence, may impose constraints on the design solution. An assembled system element, also developed with the technical and technical management processes, may include fixtures for hardware or compilers for software. It Also refers to the incorporation of the final system into its operational environment and defined external interfaces. Interface Management plays an important role, and iteration between the two processes will occur. |
|
|
Term
|
Definition
| Confirms that the system element meets the design-to or build-to specifications. It answers the question "Did you build it right?" As such, it tests the system elements against their defined requirements ("build-to" specifications). |
|
|
Term
|
Definition
| The _____ ______answers the question of "Did you build the right thing". As such, it tests the performance of systems within their intended operational environment, with anticipated operators and users. In the early stages of the system life cycle, it may involve prototypes, simulations, or mock-ups of the system and a model or simulation of the system's intended operational environment. |
|
|
Term
| The objective of ______ _____ ____ and ______is to provide a timely and reasonable assessment of the vulnerability/lethality of a system as it progresses through its development and prior to full-rate production |
|
Definition
| Live Fire Test and Evaluation LFT&E |
|
|
Term
|
Definition
-Provide information to decision-makers on potential user casualties, vulnerabilities, and lethality, taking into equal consideration susceptibility to attack and combat performance of the system;
-Ensure that knowledge of user casualties and system vulnerabilities or lethality is based on testing of the system under realistic combat conditions;
-Allow any design deficiency identified by the testing and evaluation to be corrected in design or employment before proceeding beyond low-rate initial production; and
-Assess recoverability from battle damage and battle damage repair capabilities and issues. |
|
|
Term
Means a system that DOT&E, acting for the Secretary of Defense, has determined to be a major system within the meaning of that term in 10 U.S.C. 2302(5) that is:
-user-occupied and designed to provide some degree of protection to its occupants in combat; or
-a conventional munitions program or missile program; or
-a conventional munitions program for which more than 1,000,000 rounds are planned to be acquired (regardless of whether or not it is a major system); or
-a modification to a covered system that is likely to affect significantly the survivability or lethality of such a system. |
|
Definition
|
|
Term
| Covered Systems require which type of Test? |
|
Definition
|
|
Term
| Who approves the adequacy of the LFT&E Strategy before the program begins LFT&E |
|
Definition
|
|
Term
|
Definition
| Typically includes testing at the component, subassembly, and subsystem level, and may also draw upon design analyses, M&S, combat data, and related sources such as analyses of safety and mishap data. This is standard practice, regardless of whether the program culminates with full-up, system-level (FUSL) testing, or whether a waiver is obtained from FUSL testing. One of the purposes of conducting LFT&E early in the program life cycle is to allow time to correct any design deficiency demonstrated by the test and evaluation. |
|
|
Term
| Full-Up, System-level Testing (FUSL) |
|
Definition
| Is the testing that fully satisfies the statutory requirement for “realistic survivability testing” or “realistic lethality testing” as defined in 10 USC 2366. |
|
|
Term
|
Definition
| The statute requires an _______ program to include FUSL testing unless a waiver is granted in accordance with procedures defined by the statute. A waiver package must be sent to the Congressional defense committees prior to Milestone B; or, in the case of a system or program initiated at Milestone B, as soon as practicable after Milestone B; or if initiated at Milestone C, as soon as practicable after Milestone C. Typically, this should occur at the time of TEMP approval. |
|
|
Term
| What are the waiver criteria to not conduct testing for LFT&E |
|
Definition
| unreasonable expensive and impracticle |
|
|
Term
| “The Program Manager uses _______ _______ _______to manage the technical development of the system increments, including the supporting or enabling systems.” |
|
Definition
| Technical Management Process |
|
|
Term
|
Definition
Ensures proper technical decision making for balancing
-Cost effectiveness
-Performance
-Schedule
-Supportability
-Robustness |
|
|
Term
| How are you comparing things? |
|
Definition
Comprises
-Trade studies
-Supportability analysis
-Cost analysis |
|
|
Term
|
Definition
| Defines and prioritizes decision criteria with respect to programmatic, technical, and total life cycle concerns |
|
|
Term
"Provides the basis for evaluation and selection of technical alternatives
when decisions need to be made” (Example: “Make or Buy” decisions) |
|
Definition
|
|
Term
| Ensures proper application of the SE process throughout the system’s life cycle |
|
Definition
|
|
Term
| What is the mandated tool for Technical Planning |
|
Definition
| System Engineering Plan (SEP) |
|
|
Term
| ______________ ____________will be influenced by such things as interoperability constraints; size; transportability requirements; maintenance concept; affordability; reliability, availability, and maintainability goals; and schedule. |
|
Definition
|
|
Term
How are you going to implement
SE throughout the life of the
Program? |
|
Definition
|
|
Term
| Measures technical progress and maturation |
|
Definition
|
|
Term
| Technical Performance Measures |
|
Definition
Forecasts values of essential performance parameters
- Measures values achieved by current design
- Determines impact of difference (forecast vs. current) on system effectiveness |
|
|
Term
|
Definition
| Demonstrates and confirms technical maturity and relevant exit criteria |
|
|
Term
| Establishes practices and procedures to ensure proper interface definitions, documentation and compliance throughout the system life cycle |
|
Definition
|
|
Term
|
Definition
| ____________are among the most common sources of failure in complex systems |
|
|
Term
| “The Program Manager uses _________ ___________ to design the system, subsystems, and components, including the supporting or enabling systems required to produce, support, operate, or dispose of a system.” DAG, paragraph 4.2.3.2 |
|
Definition
|
|
Term
|
Definition
| The sensitivity of the program to uncertainty in the threat description, the degree to which the system design would have to change if the threat’s parameters change, or the vulnerability of the program to foreign intelligence collection efforts (sensitivity to threat countermeasure) |
|
|
Term
|
Definition
| The sensitivity of the program to uncertainty in the system description and requirements except for those caused by threat uncertainty. |
|
|
Term
|
Definition
| The ability of the system configuration to achieve the program’s engineering objectives based on the available technology, design tools, design maturity, etc. |
|
|
Term
| Test and Evaluation (T&E). |
|
Definition
| The adequacy and capability of the ________ program to assess attainment of significant performance specifications and determine whether the systems are operationally effective and suitable. |
|
|
Term
| Modeling and Simulation (M&S). |
|
Definition
| The adequacy and capability of __________ and ________ to support all phases of a program using verified, valid, and accredited tools. |
|
|
Term
|
Definition
| The ability of the system configuration to achieve the program’s _________ objectives based on the system design, maintenance concept, support system design, and availability of support resources. |
|
|
Term
|
Definition
| The ability of the system configuration to achieve the program’s ___________ objectives based on the system design, manufacturing processes chosen, and availability of manufacturing resources such as facilities and personnel. |
|
|
Term
|
Definition
| The sensitivity of the program to uncertainty resulting from the combining or overlapping of life-cycle phases or activities. |
|
|
Term
| Capability of the Developer |
|
Definition
| The ability of the developer to design, develop, and manufacture the system. The contractor should have the experience, resources, and knowledge to produce the system. |
|
|
Term
|
Definition
| The ability of the system to achieve the program’s life-cycle _______ objectives. This includes the effects of budget and affordability decisions and the effects of inherent errors in the cost estimating technique(s) used (given that the technical requirements were properly defined). |
|
|
Term
|
Definition
| The degree in which program plans and strategies exist and are realistic and consistent. The Government’s acquisition team should be qualified and sufficiently staffed to manage the program. |
|
|
Term
|
Definition
| The adequacy of the time allocated for performing the defined tasks, e.g., developmental, production, etc. This factor includes the effects of programmatic schedule decisions, the inherent errors in the schedule estimating technique used, and external physical constraints. |
|
|
Term
|
Definition
Essential aspect of the Requirements Analysis process; provides
definition of the system functional baseline |
|
|
Term
|
Definition
Expresses the detailed functional, interface, and temporal aspects of
the system to unambiguously communicate system behavior in its intended environment |
|
|
Term
|
Definition
| Outcome of a ____________ __________is the development of lower tier functional and performance requirements that need to be allocated to the system physical architecture |
|
|
Term
|
Definition
|
|
Term
| Trade and synthesis process |
|
Definition
| Translates the outputs of the Stakeholder Requirements Definition and Requirements Analysis processes into alternative design solutions and selects a final design solution |
|
|
Term
|
Definition
Model of the physical (design) solution; physical architecture
Is complete when the system has been decomposed to lowest system element or configuration item level |
|
|
Term
| Output of System Architecture Design |
|
Definition
| Physical design resulting from a trade off between alternatives |
|
|
Term
| Output of System Architecture Design |
|
Definition
| Framework for design definition documentation (specifications and allocated and product baselines) |
|
|
Term
| Output of System Architecture Design |
|
Definition
| Confirmation of interoperability and open system performance requirements |
|
|
Term
| Output of System Architecture Design |
|
Definition
| Confirmation of interoperability and open system performance requirements |
|
|
Term
| Output of System Architecture Design |
|
Definition
| Up and downward traceability of requirements across functional, allocated, and product baselines |
|
|
Term
|
Definition
Fabricates the lowest level elements in the physical system hierarchy for integration, verification and validation for
-Manufacturing/coding, or
-Procurement, or
-Reuse |
|
|
Term
|
Definition
Above decisions are integral in a Modular Open Systems Approach (MOSA), especially for IT systems, and may impose
-Constraints on the design solution process
-Development of a manufacturing/supply chain system |
|
|
Term
|
Definition
-Development of supporting documentation (e.g. manuals)
-Packaging, handling, and storage |
|
|
Term
|
Definition
| process that actually yields the lowest level system elements in the system hierarchy. The system element is made, bought, or reused. Making it involves the hardware fabrication processes of forming, removing, joining, and finishing; or the software processes of coding, etc. |
|
|
Term
|
Definition
| Process of incorporating lower level system elements into higher level system elements in the physical architecture |
|
|
Term
|
Definition
| Also the final incorporation of the system into its operational environment |
|
|
Term
|
Definition
| The __________ strategy and planning may impose constraints on the design solution as well as implementation processes |
|
|
Term
|
Definition
| The ___________process may require the development of enabling systems such as test-beds, fixtures, simulation environments |
|
|
Term
|
Definition
| Put pieces together and test |
|
|
Term
|
Definition
Generates evidence of compliance with “build to” specifications
“Did you build the system right?” |
|
|
Term
|
Definition
| Done accordingly at all levels of implementation and integration, to include interfaces |
|
|
Term
|
Definition
Think “DT”
“Confirming system elements meet the
design-to or build-to Spec” |
|
|
Term
|
Definition
Analysis
Examination
Demonstration
Testing |
|
|
Term
|
Definition
___________ the system in its operational environment
Was the operational capability gap correctly identified?
Does the system fill the gap in a life cycle context.
“Did you build the right thing?” |
|
|
Term
|
Definition
Start ___________ in the early stages of system life cycle to reduce risk
-Prototypes
-Mock-ups
-Modeling/simulation of system characteristics
-Modeling/simulation of operational environment
Get the requirements right |
|
|
Term
|
Definition
| Moves a system element from one level in the physical hierarchy to the next |
|
|
Term
|
Definition
Might include
-Proper configuration
-Supporting documentation
-Technical reviews or peer reviews |
|
|
Term
|
Definition
Move a system element
to t he next development stage
OR,
for the end product, to
the user |
|
|
