2007-01 Engineering Leadership TNG

Engineering Leadership
Roles & Responsibilities

2006 Rockwell Collins, Inc. 15-Dec-2006
2
Legal Notice
Copyright 2006-2007 Rockwell Collins, Inc. All Rights Reserved.
Permission is hereby granted to anyone to use this copyrighted material for any lawful purpose, including commercial applications,
and to alter it and redistribute it freely, subject to the following restrictions:
The origin of this copyrighted material must not be misrepresented; you must not claim that you wrote the original text.
If you use this copyrighted material (in whole or in part) in a product, the Rockwell Collins copyright notice must appear in the product and
acknowledgement of Rockwell Collins contribution must appear in any accompanying documentation.
Alterations to the Rockwell Collins copyrighted material must be plainly marked as such, and not misrepresented as work attributable to
Rockwell Collins.
Product support for the copyrighted material is not provided.
NO WARRANTIES. THE COPYRIGHED MATERIAL IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND. TO THE MAXIMUM
EXTENT PERMITTED BY APPLICABLE LAW, ROCKWELL COLLINS DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,
WITH REGARD TO THE COPYRIGHTED MATERIAL.
NO LIABILITY FOR CONSEQUENTIAL DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT
SHALL ROCKWELL COLLINS, ITS EMPLOYEES, OFFICERS, DIRECTORS OR SHAREHOLDERS BE LIABLE FOR ANY DAMAGES
WHATSOEVER (INCLUDING WITHOUT LIMITATION, DIRECT OR INDIRECT DAMAGES FOR PERSONAL INJURY, LOSS OF BUSINESS
PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, ORANY OTHER PECUNIARY LOSS) ARISING OUT OF THE
USE OF OR INABILITY TO USE THE COPYRIGHTED MATERIAL, EVEN IF ROCKWELL COLLINS HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
This license shall be subject to the laws of the State of Iowa.
Exclusive jurisdiction of any and all legal proceedings pertaining to this matter shall be in State or Federal Court in Linn County, Iowa.
3
Course Overview
Course Objective
Provide an understanding of the roles & responsibilities of
engineering disciplines at Rockwell Collins.
Course Outline
Engineering Roles & Responsibilities
Engineering Project Leadership
System vs. Design Engineering
Project Teams
Engineering Training
4
Course Objectives: Roles & Responsibilities
Explain the differences between:
Life Cycle Value Stream Manager (LVCSM) aka Program Manager
Technical Project Manager (TPM)
Project Engineer (PE)
System Engineer
Cognizant Engineer
Design Engineer
Explain the difference between project execution team (LCVSM, TPM,
and PE) and engineering resource management team (director,
department manager, group manager) roles & responsibilities.
Explain the role of the LCVSM, TPM, and PE within the context of the
RC-MAP and RC-IPM processes.
Explain the role of the System Engineer, Cognizant Engineer, and the
Design Engineer within the context of the RC-TCP.
5
Course Objectives: Skill & Knowledge Areas
Understand the skill and knowledge areas needed for the TPM and PE
disciplines.
Understand the skill and knowledge areas needed for the Systems
Engineer discipline.
Understand the diverse skill and knowledge areas needed for the Design
Engineer.
Evaluate different organizational skill mixtures that make effective project
teams able to apply various combinations of LCVSM, TPM, PE, and
System Engineering roles to effectively staff a project.
Understand the range and scope of responsibilities for each discipline
financial (resource), schedule, and technical scope
Understand the RC-MAP, RC-IPM, and RC-TCP applicability to each
discipline.
Understand the training opportunities currently available for each
discipline.
Understand the benefits that each role provides to a project.
6
Definitions
Life Cycle Value Stream Manager (LCVSM)
Life Cycle Responsibility for products.
This includes business pursuit and capture, product development, transition
to production, customer delivery and support, and transition out of production.
Must coordinate activities across the RCI shared business model;
Engineering, Manufacturing, Marketing, Sales, and Service functions.
Technical Project Manager (TPM)
Single point of contact for engineering on a development project.
Responsible for the technical leadership and project management of the
design & development activities, within the guidelines set by the
LCVSM/Program Manager and Customer.
Provides project management expertise by planning, organizing, directing,
and coordinating functional department activities to achieve cost, schedule,
and performance requirements
Project Engineer (PE)
Lead engineer assigned to a specific project to represent the project interests
for product development
Lead coordinator and cost, schedule, and performance accountability for a
specific domain and/or discipline within engineering.
also known as Program Manager or
Product Line Manager
also known as Technical Director
7
Engineering Leadership: Common Purpose, Different Roles
LCVSM PE TPM
Multi-Disciplinary Team
Leader
Operations, Services,
Finance, Engineering
Responsible for Profit & Loss
Responsible for overall
project commitments
High Customer Contact
Business Development
Enterprise Coordination
Covers project activities for
DP A DP G
Single-Domain Engineering Team
Leader
Either Single or Multi-
discipline
Responsible for WBS Activity
Responsible for completing
committed activities and tasks
Limited Customer Contact
Technical Content
Covers project at various Project
Milestones (as needed)
Multi-Disciplinary Engineering
Team Leader
Systems, Software,
Electrical, Mechanical,
Quality
Responsible for Technical
Project Budget
Responsible for ensuring
project technical milestones
are satisfied
High Customer Contact
Engineering Focal Point
Project Execution
Covers project activities for
DP C DP E
Project Management
8
Engineering Leadership Work Allocation
9
Resource vs. Project Management
Project Management
LCVSM, TPM, PE
Assigned to specific projects
Primary project cost, schedule,
and performance accountability
Responsible for resource utilization
and daily work assignment
Responsible for efficient project
execution
Responsible for identifying project
skill and training needs
Resource Management
Engineering Director, Department
Manager, Group Manager
Support one or more projects
Accountable for participant team
member(s) contribution toward
performance on project(s) incl TPM &
PE
Responsible for resource availability
& assignment to projects
Responsible for efficient resource
utilization across projects
Responsible for resource
development (training)
Includes mentoring TPM and PEs in
their leadership roles
10
RC Key Policies and Procedures
RC-Management Authorization Process (MAP): Provides primary executive
decision-making of project execution.
RC-IPM provides opportunity for periodic reviews.
Integrated Performance Management Integrated Performance Management
DPA
DPA
DPB
DPB
DPC
DPC
DPD
DPD
DPE
DPE
DPF
DPF
DPG
DPG
Validate
opportunity Analyze
Develop
Proposal
Negotiations
and Planning
Full Scale
Development
Build & Field
Support
Field
Support
Note: Picture not intended to imply timing, only sequence
Authorization
to Analyze
Authorization
to Analyze
Authorization
to Pursue
Authorization
to Pursue
Authorization
to Submit
Proposal
Authorization
to Submit
Proposal
Authorization to
Launch Against
Baseline
Authorization to
Launch Against
Baseline
Authorization
to Build &
Field Support
Authorization
to Build &
Field Support
Authorization
to Discontinue
Production
Authorization
to Discontinue
Production
Authorization
to Discontinue
Field Support
Authorization
to Discontinue
Field Support
Deci si on Poi nts
Cadence Cadence Revi ews Revi ews
Check Poi nt Revi ews Check Poi nt Revi ews
Management Authori zati on Process
11
Integrated Performance Management (IPM) Process
Primary process model for project management
Used routinely by LCVSM, TPM, and PE to manage projects
Cyclical management model
Quarterly
Monthly
Every week
Every day
Supports fundamentals of project management
Aligned with Project Management Institute (PMI) practices
Define Project Objectives
Design WBS
Define Funding Strategy
Define Critical Performance
Measures
Identify Risks &
Opportunities
Characterize Risks &
Opportunities
Manage Risks &
Opportunities
Plan Activities & Tasks
Plan Resources
Plan Earned Value
Estimate cost
Create schedule
Obtain commitments
Establish Baseline
Initiate Work (Project Kick-
Off & Team Meetings)
Manage Work
Perform Configuration
Control
Conduct Peer Reviews
Perform Change Control
Generate reports
Analyze project
performance
Conduct project reviews
Capture project
accomplishment summary/
report
Capture project metrics
Entry: Project Initiation
Exit: Project Completion
SAP Project Fusion variant of IPM
12
RC-Technical Consistent Process (TCP)
Capture Originating
Requirements
Define Operational
Concepts
Define Requirements
Design Solution
Implement Solution
Integrate Solution
Verify Solution
Validate Solution
Develop Validation Cases &
Procedures
Develop Verification Cases
& Procedures
Develop Acceptance
Cases & Procedures
Manage Project
Support Solution
13
RC-MAP with RC-IPM and RC-TCP
DPA
DPA
DPB
DPB
DPC
DPC
DPD
DPD
DPE
DPE
DPF
DPF
DPG
DPG
Validate
opportunity Analyze
Develop
Proposal
Negotiations
and Planning
Full Scale
Development
Build & Field
Support
Field
Support
Note: Picture not intended to imply timing, only sequence
Authorization
to Analyze
Authorization
to Analyze
Authorization
to Pursue
Authorization
to Pursue
Authorization
to Submit
Proposal
Authorization
to Submit
Proposal
Authorization to
Launch Against
Baseline
Authorization to
Launch Against
Baseline
Authorization
to Build &
Field Support
Authorization
to Build &
Field Support
Authorization
to Discontinue
Production
Authorization
to Discontinue
Production
Authorization
to Discontinue
Field Support
Authorization
to Discontinue
Field Support
Deci si on Poi nts
Management Authori zati on Process
Pl an
Assess
Risk
Set
Di rection
Evaluate
Execute
Pl an
Assess
Risk
Set
Di rection
Evaluate
Execute
Pl an
Assess
Risk
Set
Di rection
Evaluate
Execute
Pl an
Assess
Risk
Set
Di rection
Evaluate
Execute
Pl an
Assess
Risk
Set
Di rection
Evaluate
Execute
Capture Originating Requirements
Define Operational Concepts
Define Requirements
Design Product
Implement
Product
Integrate
Product
Verify
Product
Validate
Product
Support Product
Time Progression (not to scale)
14
RC Process Focus
RC-MAP
LCVSM: Use RC-MAP to manage overall program life-cycle
Provide accountability to executive leadership
TPM: Use RC-MAP to support LCVSM at decision points
PE: Use RC-MAP to support TPM at decision points
RC-IPM
LCVSM: Use RC-IPM for managing project teams
TPM: Use RC-IPM for managing project execution
Provide accountability to LCVSM
Project technical plan provides basis of engineering development
PE: Use RC-IPM for managing activities and tasks
RC-TCP
LCVSM: Seldom use RC-TCP except to coordinate with engineering project
team
TPM: Use RC-TCP to help plan project team activity network
PE: Use RC-TCP to plan and perform engineering
Provide accountability to TPM
Blue highlight = primary interest area
15
RC-IPM Evaluation Cycles
Pl an
Assess
Risk
Set
Di rection
Evaluate
Execute
Pl an
Assess
Risk
Set
Di rection
Evaluate
Execute
Pl an
Assess
Risk
Set
Di rection
Evaluate
Execute
Pl an
Assess
Risk
Set
Di rection
Evaluate
Execute
Executive
Leadership
LCVSM
Plan
Assess
Ri sk
Set
Di recti on
Eval uate
Execute
Plan
Assess
Ri sk
Set
Di recti on
Eval uate
Execute
Plan
Assess
Ri sk
Set
Di recti on
Eval uate
Execute
Plan
Assess
Ri sk
Set
Di recti on
Eval uate
Execute
Plan
Assess
Ri sk
Set
Di recti on
Eval uate
Execute
Plan
Assess
Ri sk
Set
Di recti on
Eval uate
Execute
Plan
Assess
Ri sk
Set
Di recti on
Eval uate
Execute
Plan
Assess
Ri sk
Set
Di recti on
Eval uate
Execute
Plan
Assess
Ri sk
Set
Di recti on
Eval uate
Execute
Plan
Assess
Ri sk
Set
Di recti on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute
Pl an
Assess
Risk
Set
Directi on
Eval uate
Execute TPM/PE
Frequency of cycle and magnitude/fidelity of evaluation depends on
role within project hierarchy
Must understand needs of the audience of the evaluation
16
Definitions
System Engineer
Systems Engineers utilize an interdisciplinary approach focusing on
customer needs and requirements to design, develop, document and
test hardware and/or software systems ranging from the simple to
extremely complex
Domain engineer providing guidance on project technical direction
Design Engineer
Engineer providing technical product solutions
Cognizant Engineer
Lead engineer providing focal point coordination for a specific
product area used on a project (sometimes same as PE when product
work conducted on project)
Test Engineer
Engineer providing independent test services for product integration,
verification, and validation
17
Definitions
System Engineer Technical Project Manager
Technical Project Manager:
Interdisciplinary role - management
Provides project management services for design and
development activities for a given project
Cost, schedule, and project performance accountability to LCVSM
Work governed by IPM process; oversees overall TCP execution
System Engineer
Interdisciplinary role technical
Provides technical definition for a specific domain area for a
project (technical domain expert)
Technical performance accountability to PE & TPM
Work governed by TCP process; technical coordination between
disciplines
Can be same person, but
roles are distinct
18
Definitions
System Engineer Project Engineer
Project Engineer:
Can be from any discipline (system, software, hardware, etc)
Provides project management services for a specific domain
and/or discipline area for a given project
Cost, schedule, and project performance accountability to TPM
Work governed by IPM process; oversees TCP execution
System Engineer
Typically specifically trained as a system engineer
Provides technical definition for a specific domain area for a
project (technical domain expert)
Technical performance accountability to PE & TPM
Work governed by TCP process; technical coordination between
disciplines
Can be same person, but roles
are distinct
19
Technical Consistent Process: Systems Engineering
Capture Originating
Requirements
Define Operational
Concepts
Define Requirements
Design Solution
Implement Solution
Integrate Solution
Verify Solution
Validate Solution
Procedures
& Procedures
Develop Acceptance
Cases & Procedures
Manage Project
Support Solution
System Engineer
20
Technical Consistent Process: Design Engineering
Capture Originating
Requirements
Define Operational
Concepts
Define Requirements
Design Solution
Implement Solution
Integrate Solution
Verify Solution
Validate Solution
Procedures
& Procedures
Develop Acceptance
Cases & Procedures
Manage Project
Support Solution
Design Engineer
21
Technical Consistent Process: Product Engineering
Capture Originating
Requirements
Define Operational
Concepts
Define Requirements
Design Solution
Implement Solution
Integrate Solution
Verify Solution
Validate Solution
Procedures
& Procedures
Develop Acceptance
Cases & Procedures
Manage Project
Support Solution
Cognizant Engineer
22
Technical Consistent Process: Test Engineering
Capture Originating
Requirements
Define Operational
Concepts
Define Requirements
Design Solution
Implement Solution
Integrate Solution
Verify Solution
Validate Solution
Procedures
& Procedures
Develop Acceptance
Cases & Procedures
Manage Project
Support Solution
System Engineer Test Engineer
23
Technical Consistent Process: Mixed Project Team
Capture Originating
Requirements
Define Operational
Concepts
Define Requirements
Design Solution
Implement Solution
Integrate Solution
Verify Solution
Validate Solution
Procedures
& Procedures
Develop Acceptance
Cases & Procedures
Manage Project
Support Solution
Cognizant Engineer
Systems Engineer Test Engineer
Design Engineer
24
Engineering Technical Roles
Technical Project Manager / Project Engineer
Project Leader; either domain and/or discipline leader of a project
team; cost, schedule, and performance management (IPM process)
System Engineer
Problem space analyst; investigates customer needs, operational
concepts, requirements, and architecture and design solution trade-
offs; ensures product meets requirements and needs
Design Engineer
Solution space designer; creates products that fulfill the problem
definition
Cognizant Engineer
Product family engineer; lead technical engineer for a specific
product or domain; not assigned to any one project, but supports a
product/ domain for several customers
Test Engineer
IV&V cognizant engineer; provides IV&V services to ensure product
meets requirements and needs
25
Domain Domain Domain
Blending Engineering Teams
Projects require unique blend of engineering leadership (TPM and
PE) and engineering practitioner (System and Design)
LCVSM
TPM OPS CAS FIN
Domain PE Domain PE Domain PE Quality Eng
System Eng
Soft
Design
Elec
Design
Mech
Design
Project Eng Systems Eng
System Eng
Soft
Design
Elec
Design
Mech
Design
System Eng
Soft
Design
Elec
Design
Mech
Design
Typical domain engineering team:
One domain lead PE
System PE
System Eng
System Eng
System Eng
26
LCVSM
TPM OPS CAS FIN
Domain
System PE Software PE
Electrical PE
System Eng
Soft
Design
Elec
Design
Mech
Design
Mechanical PE
Domain
Electrical PE
System Eng
Soft
Design
Elec
Design
Mech
Design
Mechanical PE
Typical engineering team:
PEs share domain lead
Quality Eng System PE
System Eng
System Eng
System Eng
27
LCVSM
TPM OPS CAS FIN
Domain (PE - Option)
Electrical PE
System Eng Soft Design
Elec Design
Mech
Design
Mechanical PE
TPM
TPM
Sometimes may need
multiple TPMs.
Manage sub-elements
of project to break work
down into manageable
size
Lead TPM for total
performance
management
Electrical PE
Elec Design
Mech
Design
Mechanical PE
Electrical PE
Elec Design
Mech
Design
Mechanical PE
Electrical PE
Elec Design
Mech
Design
Mechanical PE
Electrical PE
Elec Design
Mech
Design
Mechanical PE
Electrical PE
Elec Design
Mech
Design
Mechanical PE
Very Large Project w/
Multiple TPMs
Potential multiple PEs
depending on product
complexity
Quality Eng
System PE
System Eng
System Eng
System Eng
28
LCVSM
TPM OPS CAS FIN
Quality Eng
Hardware PE
Elec Design Mech Design
Hardware PE
Hardware PE
Common Combined
Hardware Team
Simple Hardware
System PE
System Eng
System Eng
System Eng
29
LCVSM
TPM OPS CAS FIN
System PE
Quality Eng
TPM and
System
Engineer PE
role blended
Domain
Domain PE
System Eng
Soft
Design
Elec
Design
Mech
Design
Domain
Domain PE
System Eng
Soft
Design
Elec
Design
Mech
Design
Domain
Domain PE
System Eng
Soft
Design
Elec
Design
Mech
Design
Simple System
Blending
depends on
magnitude &
balance of
system
engineering
work vs. project
management
work
System Eng
System Eng
System Eng
30
LCVSM
TPM
OPS CAS FIN
System PE Quality Eng
TPM and
LCVSM role
blended
Domain
Domain PE
System Eng
Soft
Design
Elec
Design
Mech
Design
Domain
Domain PE
System Eng
Soft
Design
Elec
Design
Mech
Design
Domain
Domain PE
System Eng
Soft
Design
Elec
Design
Mech
Design
Simple Program
Blending
depends on
magnitude &
balance of
technical
project
management
work &
business
development &
enterprise
project
management
System Eng
System Eng
System Eng
31
LCVSM
TPM
OPS CAS FIN
System PE
Quality Eng
Soft
Design
Elec
Design
Mech
Design
Simple Program & System
Simple System
work may
require only a
small
engineering
team.
System Eng
System Eng
System Eng
Soft
Design
Soft
Design
Elec
Design
Elec
Design
Mech
Design
Mech
Design
System PE
provides
overall
technical
leadership
32
Technical Consistent Process: Systems Engineering
Capture Originating
Requirements
Define Operational
Concepts
Define Requirements
Design Solution
Implement Solution
Integrate Solution
Verify Solution
Validate Solution
Procedures
& Procedures
Develop Acceptance
Cases & Procedures
Manage Project
Support Solution
System Engineer
Technical Project Manager/ Project Engineer
33
Engineering Leadership Training
TPM & PE Available Courses
Fundamentals of Project Management
Purpose: Provide a solid foundation for effective project management processes and methods.
Audience: Technical Project Managers (TPMs), Project Engineers (PEs), or anyone interested in improving their project
management skills.
Length: 16-hours in 2-days.
Status: Register through Oasis today!
Role of the TPM at Rockwell Collins
Purpose: Provide training on Rockwell Collins specific processes and tools that aid the project manager.
Audience: Technical Project Managers (TPMs), Project Engineers (PEs), or anyone interested in understanding Rockwell
Collins project management culture.
Length: 12-hours in 1.5-days.
Engineering Roles and Responsibilities (this class!)
Purpose: Provide training on the different roles & responsibilities of the LCVSM, TPM, PE, System Engineer, and Design
Engineer common responsibilities with complementary roles.
Audience: Technical Project Managers (TPMs), Project Engineers (PEs), or anyone interested in understanding Rockwell
Collins project management culture.
Length: TBD.
Status: In Progress to be completed by close of Dec 2006. Pilot courses offered Nov 2006.
Overview of the Technical Consistent Process (TCP)
Purpose: Provide an overview of the Technical Consistent Process its purpose, tailoring, and application on engineering
development projects.
Audience: Technical Project Managers (TPMs), Project Engineers (PEs), or anyone interested in understanding the TCP.
Length: 2-hrs.
Status: In Progress to be completed mid-Nov 2006. Pilot course available today!
34
Engineering Discipline Training
System Engineering
Fundamentals of System Engineering
Purpose: Provide an introduction to the Systems Engineering discipline, processes, and deliverables.
Audience: Systems Engineers, aspiring Systems Engineers, or anyone desiring more understanding of a disciplined engineering process for problem identification and resolution.
Length: 3-days.
Status: Register through Oasis improvements to the course and alternate vendors are under consideration.
Capture Originating Requirements
Purpose: Provide instruction on the best practices in capturing requirements; evaluate of stakeholder needs; assess source requirements; capture life-cycle context; and establish most
important requirements.
Audience: Systems Engineers, System Analysts, aspiring Systems Engineers, or anyone desiring more understanding of techniques to assessraw source material for bounding the
problem space.
Length: TBD (expect 2 to 4-hrs).
Status: In progress expected completion mid-Dec 2006. Pilot courses offered late Nov 2006.
Define Operational Concepts
Purpose: Provide instruction on effective techniques to capture an operational concept with use cases & scenarios.
Audience: Systems Engineers, aspiring Systems Engineers, or anyone desiring to understand analysis of user needs and operation of products.
Length: 8-hrs in two -day format.
Define Requirements
Purpose: Provide instruction on applied requirements engineering and management techniques.
Audience: Systems Engineers, System Analysts, aspiring Systems Engineers or anyone desiring to improve their requirements writing skills.
Length: TBD.
Status: Evaluating latest pilot offering and next steps. Plan availability 2nd quarter 2006.
Design System
Purpose: Provide instruction on applied architecting and design techniques; explore use of Systems Modeling Language (SysML) and DoDArchitectural Frameworks (DoDAF).
Audience: Systems Engineers, System Architects, aspiring Systems Engineers, or anyone desiring to improve their architecting and designdefinition capabilities.
Length: TBD.
Status: Evaluating latest pilot offering and next steps. Plan availability 3rd quarter 2006.
Integration, Verification, and Validation
Purpose: Provide instruction on best practices on integration, verification, and validation techniques.
Audience: Systems Engineers, Test Engineers, or anyone desiring to improve their test definition and conduct capabilities.
Length: 8-hr CBT.
Status: Take on-line through Oasis today! Evaluating need for alternate instructor led course.SystemEngineering

2007-01 Engineering Leadership TNG

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

2007-01 Engineering Leadership TNG

Enviado por

Direitos autorais:

Formatos disponíveis

Engineering Leadership

Roles & Responsibilities

Você também pode gostar