NDIA SoS SE Committee Topics of Interest May 25, 2009.

Slides:



Advertisements
Similar presentations
Why does ERA Need to Flourish
Advertisements

TWO STEP EQUATIONS 1. SOLVE FOR X 2. DO THE ADDITION STEP FIRST
You have been given a mission and a code. Use the code to complete the mission and you will save the world from obliteration…
Requirements Engineering Processes – 2
Question 8 Virginia Department of Education 8. Does the IEP consider the strengths, interests, preferences, and needs of the student? (34 C.F.R §300.43(a)(2)
Anne Gilleran BECTA Research Conference London 13 June 2003 The Digital Generation Student Voices from the eWatch Study BECTA Research Conference 13th.
Advanced Piloting Cruise Plot.
1 Copyright © 2010, Elsevier Inc. All rights Reserved Fig 2.1 Chapter 2.
By D. Fisher Geometric Transformations. Reflection, Rotation, or Translation 1.
Introduction to Product Family Engineering. 11 Oct 2002 Ver 2.0 ©Copyright 2002 Vortex System Concepts 2 Product Family Engineering Overview Project Engineering.
2 Session Objectives Increase participant understanding of effective financial monitoring based upon risk assessments of sub-grantees Increase participant.
1 Balloting/Handling Negative Votes September 11, 2006 ASTM Training Session Bob Morgan Brynn Iwanowski.
1 Balloting/Handling Negative Votes September 22 nd and 24 th, 2009 ASTM Virtual Training Session Christine DeJong Joe Koury.
Aviation Security Training Module 4 Design and Conduct Exercise II 1.
Business Transaction Management Software for Application Coordination 1 Business Processes and Coordination.
Designing Services for Grid-based Knowledge Discovery A. Congiusta, A. Pugliese, Domenico Talia, P. Trunfio DEIS University of Calabria ITALY
EA Demonstration Study : Dissemination Forum – 8 June EA Views and Sub-views Patrick Bardet EA Unit.
Human Performance Improvement Process
Jeopardy Q 1 Q 6 Q 11 Q 16 Q 21 Q 2 Q 7 Q 12 Q 17 Q 22 Q 3 Q 8 Q 13
Jeopardy Q 1 Q 6 Q 11 Q 16 Q 21 Q 2 Q 7 Q 12 Q 17 Q 22 Q 3 Q 8 Q 13
Title Subtitle.
My Alphabet Book abcdefghijklm nopqrstuvwxyz.
0 - 0.
ALGEBRAIC EXPRESSIONS
DIVIDING INTEGERS 1. IF THE SIGNS ARE THE SAME THE ANSWER IS POSITIVE 2. IF THE SIGNS ARE DIFFERENT THE ANSWER IS NEGATIVE.
SUBTRACTING INTEGERS 1. CHANGE THE SUBTRACTION SIGN TO ADDITION
MULT. INTEGERS 1. IF THE SIGNS ARE THE SAME THE ANSWER IS POSITIVE 2. IF THE SIGNS ARE DIFFERENT THE ANSWER IS NEGATIVE.
Addition Facts
Year 6 mental test 5 second questions
Around the World AdditionSubtraction MultiplicationDivision AdditionSubtraction MultiplicationDivision.
ZMQS ZMQS
IAEA Training in Emergency Preparedness and Response Module L-051 General Concepts of Exercises to Test Preparedness Lecture.
1 Auto Club Group ACG Direct Mail Program September 21, 2009.
BT Wholesale October Creating your own telephone network WHOLESALE CALLS LINE ASSOCIATED.
1 Kentuckys Public Safety Awareness Initiative Program Coordination and Partnerships August 23, 2005.
EMS Checklist (ISO model)
1 Quality Indicators for Device Demonstrations April 21, 2009 Lisa Kosh Diana Carl.
ABC Technology Project
VOORBLAD.
1 Breadth First Search s s Undiscovered Discovered Finished Queue: s Top of queue 2 1 Shortest path from s.
SAI Performance Measurement Framework
Chapter Two Company and Marketing Strategy
Identifying Our Own Style Extended DISC ® Personal Analysis.
Squares and Square Root WALK. Solve each problem REVIEW:
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement 1.
Lets play bingo!!. Calculate: MEAN Calculate: MEDIAN
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management.
Lecture 6: Software Design (Part I)
Past Tense Probe. Past Tense Probe Past Tense Probe – Practice 1.
Chapter 5 Test Review Sections 5-1 through 5-4.
SIMOCODE-DP Software.
GG Consulting, LLC I-SUITE. Source: TEA SHARS Frequently asked questions 2.
1 First EMRAS II Technical Meeting IAEA Headquarters, Vienna, 19–23 January 2009.
1 Development of Electronic Reporting Tools for IPPC Directive and WI Directive Workshop – Objective and next steps Tuesday 3 rd March 2009 Meeting room.
Addition 1’s to 20.
25 seconds left…...
Test B, 100 Subtraction Facts
Januar MDMDFSSMDMDFSSS
Week 1.
INFORM + LISTEN WORKSHOPS 16 th June – 25 th June 2014.
We will resume in: 25 Minutes.
1 Unit 1 Kinematics Chapter 1 Day
1 Safety Assurance JPDO Perspective Maureen Keegan 11 October, 2012.
How Cells Obtain Energy from Food
Competency Management Defining McGill’s Competency Directory MANAGEMENT FORUM JUNE 7, 2005.
NDIA SE Division Meeting February 13, Developmental Test and Evaluation Committee Beth Wilson, Raytheon Steve Scukanec, Northrop Grumman Industry.
Presentation transcript:

NDIA SoS SE Committee Topics of Interest May 25, 2009

Overview New NDIA SoS SE Committee formed with kickoff meeting in April Committee members submitted s identifying SoS issues which ‘keep them away at night” These ‘sleepless night’ issues were aggregated Members were asked to identify their top 5 issues and the questions they would like to see addressed with respect to these issues This presentation summarized the results

23 Sleepless Night Issues 1Lessons learned from past and on- going SoS programs 2Perspective of the SoS manager for SoS SE 3Defining SoS relationship in terms of an 'SoS Signature' 4Relationship among SE approaches for systems, SoS, FoS 5Difference in SoS definitions 6Developing validated SoS policy 7Relationship between SoS and acquisition process 8Addressing SoS from perspective of a new system acquisition 9Role of requirements in SoS 10SoS architecture 11SoS Integration 12SoS and Complexity 13Role of optimization in SoS SE 14Defining and measuring SoS performance 15SoS test and evaluation 16SoS SE competencies and training 17SoS governance 18Constructive approaches to addressing politics in an SoS 19SoS business models 20Relationship between SoS and net-centric services 21Science based theory to support SE of systems and SoS 22SoS modeling and simulation 23SoS SE Analyses of CBRN

Spreadsheet Soliciting Inputs Spreadsheet was ed to ~60 people indicating an interest in the SoS SE Committee Request for top 5 topics and questions of interest for these topics Received inputs from 14 members

Results 1 Issue 8 (of 12) expressed interest 1 Issues 7 (of 12) expressed interest 1 Issue 6 (of 12) expressed interest 2 Issues 5 (of 12) expressed interest 1 Issues 4 (of 12) expressed interest 2 Issues 3 (of 12) expressed interest 3 Issues 2 (of 12) expressed interest 10 Issues 1 (of 12) expressed interest 4 Issues 0 (of 12) expressed interest

Top Issues SoS Test and Evaluation (8 of 12) Relationship between SoS and acquisition process (7 of 12) Lessons Learned from past and on-going SoS programs (6 of 12) Defining and measuring SoS performance (5 of 12) [related questions were posed under SoS Test and Evaluation] SoS modeling and simulation ( 5 of 12 ) [Already a topic of NDIA M&S Committee] SoS architecture (4 of 12)

Top Issue: SoS Test and Evaluation (8 of 12) 1.How to evaluate SoS Performance metrics in T&E 2.Traditional techniques for T&E of individual systems do not always scale well to SoS. –What are some new constructs for SoS T&E? –How should model and simulation development progress, in step with SoS development, from concept to test and evaluation? 3.How to plan & leverage T&E throughout out SoS L/C? 4.How to assess implications of changes/new capabilities in constituent systems on SoS T&E? 5.Does this premise extend the underlying effectiveness, suitability, and survivability (ESS) test requirements at a system level? 6.What is the relationship of SoS test and evaluation requirements to the conceptual requirements of AEC's MBT&E process? 7.Should and how are SoS test and evaluation requirements defined in the TEMP and SEP? 8.How do you define success for a SoS? In operational measures such as mission success or by other more technical measures? 9.What are the means to determine the weak links and strong links within the SoS and to quantify the attributes that make sub-component strong?"

Relationship between SoS and the acquisition process (4 of 12) 1.What are the barriers/challenges or potential incentives to removing same when acquiring SoS (in non-Directed SoS)? 2.What specific milestones, decisions, or products is the SoS approach expected to inform along the JCIDS and DAS processes? 3.Are there any specific and unique products that the SoS approach is expected to produce and what are the relationships of these products to acquisition lifecycle products? 4.How does the SoS support the acquisition process? 5.What are the differences between acquiring a System and a SoS?

Lessons Learned from past and on-going SoS programs (6 of 12) 1.What is the recommended approach and what are the basic steps to design large integrated SoSs where the systems are independently and separately developed? 2.What is the recommended approach and what are the basic steps to design large integrated network centric SoSs where the systems are independently and separately developed? 3.What are the recommended suite of methods and tools that can be used to design large SoSs including integrated network SoSs? 4.What are best practices and lessons learned for IT-intensive SoS acqusitions? 5.As the Lead Systems Integrator for the FCS Program, how did Boeing organize for SoS management? What lessons did Boeing learn (5 "up" lessons and 5 "down" lessons)? 6.What are the best practices to surface issues with respect to achieving (software) interoperabilty? At which parts of life cycle are they most effective?

Next Steps Note small number of respondents and consider ways to get better input –Discuss with committee at next meeting –Are the top three an ok starting point? Or do we need to solicit more input? Begin addressing top issue: SoS and T&E –Circulate our SoS T&E paper to committee members now Paper raises almost all of the questions note in the input and provides one perspective to focus discussion –Solicit comments on it by 3 June –Make this a discussion topic at next meeting –Invite T&E committee to join us? Include AFEI SOA outbrief at next meeting –Partnership with AFEI (plus input from NSA) –Topic of IT intensive systems and net-centric systems raised in several of the lessons learned topic questions