Importance of T&E Connotations

Slides:



Advertisements
Similar presentations
Systems Engineering From a Life Cycle Perspective John Groenenboom Director Engineering – Mesa Boeing Rotorcraft Dec 12, 2007.
Advertisements

Integrating Developmental and Operational Testing
Chapter 4 Quality Assurance in Context
Chapter 6: Design of Expert Systems
1 Introduction to System Engineering G. Nacouzi ME 155B.
SE 555 Software Requirements & Specification Requirements Validation.
Pittsburgh, PA Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense.
EMIS Chapter 6. EMIS Chapter 6 EMIS Chapter 6 Fig 6.2 shows where the SEMP fits into the earliest program stages. Fig 6.5 has an.
Feasibility Analysis Chapter 3
EMIS 7307 T&E Part 3 1 A few DT&E Areas of focus Life testing. –To make sure that the system will not fail prematurely due to fatigue, aging, long term.
The Accountant’s Role in the Organization
1 Lecture 5.3: SEF Ch 4 Requirements Analysis Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Typical Software Documents with an emphasis on writing proposals.
EMIS 7307 T&E Part 2 1 Documents in flux. MNS - Mission need statement –Non system specific, a needed capability. Being replaced by Initial Capabilities.
UNCLASSIFIED Bill McCarthy Bill McCarthy Deputy Director 15 September September 2010 COTF Perspectives.
DEVELOPMENTAL TEST & EVALUATION DT&E – From Concept to Combat Integrated Test Process Darlene Mosser-Kerner Developmental Test & Evaluation OUSD(AT&L)/Systems.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
New 5000 Documents 14 May 2001 New 5000 Documents 14 May 2001 Defense Systems Management College Acquisition Policy Department.
Shift Left Feb 2013 Page-1 DISTRIBUTION STATEMENT A – Cleared for Open Publication by OSR on January 17 th, 2013 – SR case number 13-S-0851 Dr. Steven.
Verification and Validation — An OSD Perspective — Fred Myers Deputy Director, Test Infrastructure Test Resource Management Center November 4, 2009.
Lecture 2.1b: DoD Acquisition Process (SEF Ch 2)
CCA LSS Support Slides1 Draft The Defense Acquisition Management Framework. Post Implementation Review (PIR) Capability Needs Satisfaction & Benefits.
1 Lecture 2.4a: SEF SE Planning and the SEP (SEF Ch 16) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
Slide 1 Systems Analysis and Design with UML Version 2.0 Chapter 3: Project Initiation.
EMIS Chapter 5 Much of Chap 5 and 6 varies depending on the contract type. Two major types are important so we’ll digress to Contracting 101 for.
A few DT&E Areas of focus
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Technology Readiness Assessment (TRA)
Life Cycle Logistics.
Chapter 2 How important is determining (or creating) the need first?
DT&E Strategy and the Developmental Evaluation Framework (DEF) Concept & Program Implementation 5 June 2014.
MNS - Mission need statement
Application Outsourcing: Achieving Success & Avoiding Risk
CompSci 230 Software Construction
2012 Spring Simulation Interoperability Workshop
CS 389 – Software Engineering
Chapter Two Company and Marketing Strategy
CS4311 Spring 2011 Process Improvement Dr
TQS - Teste e Qualidade de Software (Software Testing and Quality) Introduction To Software Testing Concepts João Pascoal.
New Space Systems Acquisition Policy
Recall The Team Skills Analyzing the Problem
CS701 SOFTWARE ENGINEERING
Continuous Improvement through Accreditation AdvancED ESA Accreditation MAISA Conference January 27, 2016.
Software Documentation
Chapter 6: Design of Expert Systems
Test and Evaluation Considerations
Defining the Activities
Applied Software Implementation & Testing
Defense Acquisition University
Chapter 2 – Software Processes
18 November 2018.
Technical Management Processes
Introduction to Software Testing
Chapter 2 Software Processes
Lockheed Martin Canada’s SMB Mentoring Program
Chapter 2 How important is determining (or creating) the need first?
EMIS 7307 Chapter 6.
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Welcome to Corporate Training -1
A person who conduct a study, identifies activities and objectives and determines a procedure to achieve the objectives.
First Article Inspection
Building Information Systems
4 March 2004 A Framework for OT&E Transformation NDIA 20th Annual Test and Evaluation Conference Dr. William G. Lese Vice President Simulation, Analysis.
8 Tech Processes Drive Acquisition
The Department of Defense Acquisition Process
Applied Software Project Management
Chapter Two Company and Marketing Strategy
Perspectives on Transforming DT and OT Industry-Government Roundtable
Building Information Systems
Presentation transcript:

Importance of T&E Connotations EMIS 7307 T&E Part 1 Importance of T&E Connotations Recall that testing involves getting data to support a decision or risk reduction effort. In the context of I&T, test data support the integration process and helps integration engineers decide whether the integration at any point in the flow has been successful or are there problems to be fixed so that integration can continue. In the context of T&E, test data are collected to provide information for evaluation where evaluation is the manipulation and analysis of these data to determine performance and thus specification or requirement compliance.

Evaluation can be based on data from any verification method. EMIS 7307 T&E Part 1 Importance of T&E Evaluation can be based on data from any verification method. Inspection, simulation, analysis, demonstration or test. Some people expand the definition of test to all these methods but shouldn’t! T&E has taken on extreme importance for DOD and should for any developer. Result of many years of purchasing expensive systems that did not meet need or requirements.

DOD has a detailed process for acquiring new systems. EMIS 7307 T&E Part 1 Importance of T&E DOD has a detailed process for acquiring new systems. Described in DOD 5000 Included as FYI on class web site Next slide shows the “big” picture of the acquisition process.

EMIS 7307 T&E Part 1

EMIS 7307 T&E Part 1 Importance of T&E A few terms/acronyms worth knowing: (some have recently changed and will be discussed later) MS - Milestone MNS - Mission Need Statement Non system specific, a needed capability. ORD - Operational Requirements Document Minimum acceptable capability of possible system. LRIP - Low Rate Initial Production Generates systems for use in OT&E. IOC - Initial Operational Capability

Note how T&E fits into the SE process. EMIS 7307 T&E Part 1 Importance of T&E Note how the DOD has adopted good SE practices to define the acquisition process. Note how T&E fits into the SE process. SE requires knowledge of technical status to continue or modify and ultimately complete system development. T&E provides that knowledge.

EMIS 7307 T&E Part 1 Importance of T&E As previously discussed, next slide illustrates the reason for so many checks and balances. Look at pages 1-4 and 1-5 (Test and Evaluation Management Guide ) to see T&E roles prior to MSs B and C.

EMIS 7307 T&E Part 1

Note relative amounts of DT&E vs. OT&E. EMIS 7307 T&E Part 1 Importance of T&E Next slide illustrates the relationship of the T&E flow with the acquisition or SE flow. Note relative amounts of DT&E vs. OT&E. It’s possible even desirable to have both types simultaneously.

EMIS 7307 T&E Part 1

More terms/acronyms worth knowing: EMIS 7307 T&E Part 1 Importance of T&E More terms/acronyms worth knowing: DT&E - Developmental Test and Evaluation. All testing ( not lab experiments) that are up to and including certification for OT&E. May be either contractor or customer led and/or executed. IOT&E - Initial OT&E. Performed on LRIP articles to see if suitable and effective. FOT&E - Follow-on OT&E. After deployment.

What type of tests are these? EMIS 7307 T&E Part 1 Importance of T&E What type of tests are these? Test to determine vibration levels. Test to see if tank is destroyed. Throughput measurement. Maintenance time measurement. CEP measurement.

Importance of T&E DT&E OT&E EMIS 7307 T&E Part 1 Importance of T&E DT&E and OT&E are different “beasts” though at times they seem the same. DT&E Measurement related to technical issue (spec). Vibe, temp, etc May be in a lab or with the integrated system. Performed by engineers or “techs”. OT&E Measurement or information related to operational requirement (ORD). Penetrates bunker, Pk, Pd etc Production representative system. Performed by end-users.

Testers know about SE too! EMIS 7307 T&E Part 1 Testers know about SE too!

Two perspectives on one process EMIS 7307 T&E Part 1 Two perspectives on one process

T&E plays in design reviews EMIS 7307 T&E Part 1 T&E plays in design reviews

TEMP and SEMP must be tightly coordinated. EMIS 7307 T&E Part 1 TEMP and SEMP must be tightly coordinated. T&E answers questions at design reviews etc. See page 2-6 para. 2.3.2 (Test and Evaluation Management Guide).

Each service does T&E their way, OT&E is always independent EMIS 7307 T&E Part 1 Each service does T&E their way, OT&E is always independent