NDIA Software Industry Experts Panel 14 July 2008 1 NDIA Software Industry Experts Panel Paul R. Croll, Chair NDIA Systems Engineering Division.

Slides:



Advertisements
Similar presentations
1 The Systems Engineering Research Center UARC Dr. Dinesh Verma Executive Director January 13,
Advertisements

DT&E Cmte - Walking The Line with Title 10 1 Beth Wilson Industry Co-Chair NDIA System Engineering Division, DT&E Committee Test Architect, Raytheon Company.
Program Management Office (PMO) Design
Course: e-Governance Project Lifecycle Day 1
BENEFITS OF SUCCESSFUL IT MODERNIZATION
A Navy Business Initiative Defense Daily OA Summit 12 November 2013 Nickolas H. Guertin, PE Director for Transformation DASN RDT&E
NDIA System Engineering Division 2012 Task #4 October INTERIM PROGRESS REPORT.
DoD Software Issues and Gap Identification Kristen Baldwin Deputy Director, Software Engineering and System Assurance OUSD(AT&L) April 18, 2007.
Delivery Business Solutions April 29, Nashville PMI Symposium April 29, 2013 Stephanie Dedmon, PMP Director, Business Solutions Delivery Department.
Joint Working Group for DoD Systems Engineering Standardization
NDIA Software Industry Experts Panel Paul R. Croll, Chair NDIA Systems Engineering Division Meeting 24 June 2008.
NDIA Software Industry Experts Panel 14 July NDIA 11 th Anuual Systems Engineering Conference Software in Acquisition Working Groups Software Track.
Systemic Analysis of Software Findings Scott Lucero Office of the Deputy Undersecretary of Defense (Acquisition and Technology) Software Engineering and.
University of Southern California Center for Systems and Software Engineering Issues and Recommendations Emanating from the Management Issues Group of.
Software and System Engineering Integration Sponsor Overview Kristen Baldwin Deputy Director, Software Engineering and System Assurance Office of the Under.
DoD Systems and Software Engineering A Strategy for Enhanced Systems Engineering Kristen Baldwin Acting Director, Systems and Software Engineering Office.
Software in Acquisition Workshop Software Expert Panel Working Groups and Tasks Rick Selby DoD Software In Acquisition.
6/17/ :30:49 PM _Teamwork Competitive Prototyping Challenges for DoD and Industry Paul Croll, AMND Fellow May 28, 2008.
DoD Software Engineering and System Assurance New Organization – New Vision Kristen Baldwin Office of the Under Secretary of Defense Deputy Director, Software.
14 July 2008 Blake Ireland Industry Roundtable COMPETITIVE PROTOTYPING.
1 Perform Assess Policy and Guidance Acquisition Program Improvement Model Acquisition Programs Acquisition Workforce Human Capital Strategic Planning.
Recent Trends in DoD Systems and Software Engineering Processes Bruce Amato Acting Deputy Director, Software Engineering and Systems Assurance Office of.
Software in Acquisition Workshop Software Expert Panel Outbrief Day 2 DoD Software In Acquisition Workshop April Institute for Defense Analyses,
PMSS Final SOW May 22 nd, Statement of Work 2 GLENN RESEARCH CENTER PROJECT MANAGEMENT SUPPORT SERVICES (PMSS) The Contractor shall provide expert.
What is Business Analysis Planning & Monitoring?
Unclassified. Program Management Empowerment and Accountability Mr. David Ahern Director, Portfolio Systems Acquisition AT&L(A&T) 14 April 2009 The Acquisition.
Chapter : Software Process
NDIA SE Division Meeting February 13, Developmental Test and Evaluation Committee Beth Wilson, Raytheon Steve Scukanec, Northrop Grumman Industry.
IEEE S2ESC Report1 Software And Systems Engineering Standards Committee (S2ESC) Paul R. Croll S2ESC Sponsor Chair June 2004 Report.
Unit 5:Elements of A Viable COOP Capability (cont.)  Define and explain the terms tests, training, and exercises (TT&E)  Explain the importance of a.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Earned Value Management Systems (EVMS) Defense Support Team (DST) and Report to Congress Mr. Richard Ginman OUSD(A&T)/DPAP Presentation to National Defense.
Roles and Responsibilities
GBA IT Project Management Final Project - Establishment of a Project Management Management Office 10 July, 2003.
1 Earned Value Management (EVM) Center ‘Moving Forward’ Presented by Mr. David Kester Director, Program Integration Division April 25, 2007.
HECSE Quality Indicators for Leadership Preparation.
Understanding Industry Defense Acquisition University 13 May 2010 Status Brief to NDIA Program Systems Committee.
Private & Confidential1 (SIA) 13 Enterprise Risk Management The Standard should be read in the conjunction with the "Preface to the Standards on Internal.
10/16/2015Bahill1 Organizational Innovation and Deployment Causal Analysis and Resolution 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed Continuous.
March 26-28, 2013 SINGAPORE CDIO Asian Regional Meeting and Workshop on Engineering Education and Policies for Regional Leaders Programme Evaluation (CDIO.
Sheri Ginett, IIDA, NCIDQ, Interior Architects Carol Fadden, Duke Energy September 9, 2015 OPERATIONAL EXCELLENCE PROGRESSIVE + STRATEGIC WORKPLACE.
Georgia Institute of Technology CS 4320 Fall 2003.
Government Procurement Simulation (GPSim) Overview.
Life Cycle Cost-Logistics Improvement Joint Task with NDIA Logistics Div August J. Cothran B. Pieper J.S. Moorvitch.
Software Engineering - I
0 Office of Performance Assessments and Root Cause Analyses (PARCA) PARCA EVM Update Presenter: Phone:
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
IEEE CS SAB, Nov 2007 For Computer Society Internal Use Only 1 S2ESC Report Standards Activities Board Meeting November 6-7, 2007 Submitted by Paul Croll.
NDIA SE Division – Annual Planning Meeting December 12-13, NDIA Meetings SEI (SW Engineering Institute) SoS Architecture Patterns -SEI is developing.
CAPT Joe Spruill Office of Deputy Assistant Secretary of the Navy (Logistics) September 29, 2005 Managing Obsolescence within a Performance Based Logistics.
EGovOS Panel Discussion CIO Council Architecture & Infrastructure Committee Subcommittee Co-Chairs March 15, 2004.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Data Report July Collect and analyze RtI data Determine effectiveness of RtI in South Dakota in Guide.
Government and Industry IT: one vision, one community IAC Shared Interest Groups (SIGs) Review October 26, 2009.
Independent Expert Program Review (IEPR) February 2006.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
| 1 Weapon System Acquisition Reform- Product Support Assessment DAU SYMPOSIUM 13 April 2010 Presented by: Basil Gray Where Innovation.
Power to the Edge A Net-Centric DoD NII/DoD CIO IT Acquisition Management Transformation Rapid Improvement Team (RIT) Principals Meeting November 18, 2003.
Managing Multiple Projects Steve Westerman California Department of Motor Vehicles Steve Young Mathtech, Inc.
Systems Engineering Initiatives 04/13/10 Page-1 CLASSIFICATION – UNCLASSIFIED Systems Engineering Initiatives and the SPRDE Career Field 13 April 2010.
Info-Tech Research Group1 Info-Tech Research Group, Inc. Is a global leader in providing IT research and advice. Info-Tech’s products and services combine.
ICOTE Meeting October, Chief Developmental Tester Project Status for ICOTE October 2014 Brendan Rhatigan – Lockheed Martin.
Chapter 24: Architecture Competence
Data Architecture World Class Operations - Impact Workshop.
Identify the Risk of Not Doing BA
Lecture 17 ATAM Team Expertise
Improving Mission Effectiveness By Exploiting the Command’s Implementation Of the DoD Enterprise Services Management Framework - DESMF in the [name the.
For Computer Society Internal Use Only
For Computer Society Internal Use Only
By Jeff Burklo, Director
Presentation transcript:

NDIA Software Industry Experts Panel 14 July NDIA Software Industry Experts Panel Paul R. Croll, Chair NDIA Systems Engineering Division

NDIA Software Industry Experts Panel 14 July Who We Are ● The NDIA Software Industry Experts Panel acts as a “voice of industry” in matters relating to DoD software issues ● The Panel helps identify and resolve software acquisition and development issues facing the industry and its Government customer base ● The Panel may also, from time to time, identify for investigation certain technologies or practices that promise to improve industry responsiveness to DoD needs. ● Members –Paul Croll, CSC, Chair –JoAn Ferguson, General Dynamics –Gary Hafen, Lockheed Martin –Blake Ireland, Raytheon –Al Mink, SRA International –Ken Nidiffer, SEI –Shawn Rahmani, Boeing –Rick Selby, Northrop Grumman

NDIA Software Industry Experts Panel 14 July What We Do ● Investigate, analyze, and develop recommendations concerning software issues, in response to NDIA and Government requests ● Provide industry comments on Government positions, initiatives, or work products ● Develop industry white papers and position papers ● Reach out to relevant stakeholders through NDIA conferences and other venues as appropriate

NDIA Software Industry Experts Panel 14 July NDIA Top Software Issues Workshop August 2006 ● Identify Top 5 Software Engineering problems or issues prevalent within the defense industry –Document issues Description and current state Rationale and SW impacts –Develop recommendations (short term and long term) –Generate task report –Submit to OSD

NDIA Software Industry Experts Panel 14 July Top Software Issues 1. The impact of requirements upon software is not consistently quantified and managed in development or sustainment 2. Fundamental system engineering decisions are made without full participation of software engineering 3. Software life-cycle planning and management by acquirers and suppliers is ineffective 4. The quantity and quality of software engineering expertise is insufficient to meet the demands of government and the defense industry 5. Traditional software verification techniques are costly and ineffective for dealing with the scale and complexity of modern systems 6. There is a failure to assure correct, predictable, safe, secure execution of complex software in distributed environments 7. Inadequate attention is given to total lifecycle issues for COTS/NDI impacts on lifecycle cost and risk

NDIA Software Industry Experts Panel 14 July Defense Software Strategy Summit October 2006 ● Keynote Address, the Honorable Dr. James I. Finley, Deputy Under Secretary of Defense (Acquisition and Technology) ● Program Executive Officer and Service/Defense Agency panels on software related acquisition issues and initiatives ● Plenary Session Topics -- NDIA Top Software Issues, Software Industrial Base Study, and Software Producibility ● Workshops –Software Acquisition and Sustainment Mr. Mike Nicol, Air Force Aeronautical Systems Center Mr. Lawrence T. Osiecki, US Army, Armament Software Engineering Center –Policy Mr. Jim Clausen, DoD CIO, Office of Commercial IT Policy Col Peter Sefcik, Jr., USAF Chief, Air Force Engineering Policy and Guidance Team Lt Col Mark Wilson, SAF/AQR Systems & Software Engineering –Human Capital Dr. Kenneth E. Nidiffer, Fellow, Systems and Software Consortium Mr. George Prosnik, Defense Acquisition University E&T Center –Software Engineering Practices Mr. Grady Campbell, Software Engineering Institute Mr. Paul R. Croll, CSC, Industry Co-Chair NDIA Software Committee

NDIA Software Industry Experts Panel 14 July DoD Software Summit Issues Software Acquisition and Sustainment ● Software issues not addressed early in lifecycle ● Software requirements not well defined at program start ● Management has limited visibility into software development processes and status ● Risk areas – single point failures not adequately addressed, e.g., single software providers, incomplete data rights, key personnel stability, life cycle support of COTS ● Acquirers do not adequately address software sustainment and total life cycle early in the program ● Some agencies contract before engineering is complete, prior to system design and development Policy ● PMs need assistance with software policy and analysis ● Arbitrary separation of weapon and information technology software policies ● Policy implementation guidance and follow-up monitoring is limited ● Department needs software group with good expertise to oversee and implement policy ● Need capability to share policy and guidance information ● Human Capital ● Experienced system & software engineers seem missing from key DoD leadership positions ● Shortage of highly experienced software managers, architects, domain and technical experts ● Eroding depth and breath of experience for personnel in DoD ● Young people may consider system and software engineering as a career dead end ● Emerging skill set may be needed for future complex DoD systems, e.g., systems of systems ● Software Engineering ● Weak linkage between software requirements and capabilities/portfolios ● System development methods do not properly leverage software ability to rapidly field new capability ● Systems and software engineering lifecycles not always consistent or harmonized ● Software considerations not consistently addressed in architectures ● Inadequate software estimating methods, e.g., COTS/NDI; best practices not applied Reaffirmed NDIA Top Software Issues

NDIA Software Industry Experts Panel 14 July Software Issues/Gaps Workshop Findings Primary Software Focus Areas* Software Development Techniques * based on NDIA Top SW Issues, OSD Program Support Reviews, and DoD Software Summit findings Data and Metrics SW Metrics – A, O SW Cost – O SW EVM – DCMA SW Estimation - GAP Human Capital Education Sources – N, A Leadership Training – A, SEI SETA Quals – GAP SW Human Cap Strategy – GAP Industrial Base – O University Curriculum – O Worforce Survey - AF Knowledge Sharing DAU Software ACC – DAU Best Practices Clearinghouse – DAU, O SW Inventory – LMR Lifecycle Guides – M, N Root Cause Analysis – O Local Knowledge Portals - N Agile – O, SEI Architecture – A, SEI COTS – SEI Open Source – AF Sustainment – GAP SW Interoperability – GAP SW Test - GAP SW & SE Integration Requirements – GAP SE/SW Process Int – O SW Council – N SW Dev Plan – N SW in SEP – N SW in Tech Reviews – N SW Quality Attributes - GAP Software Acquisition Management Standards – O, N DAG Ch 4/7 – O, AF Prog Spt – O, All Contract Language – A, M, N SW Estimation – GAP Lifecycle Policy – AF Risk Identification - GAP Ongoing Initiative Owners O – OSD/SSA A – Army N – Navy AF – Air Force M – MDA SEI DCMA DAU L&MR GAP – No activity Source: Kristen Baldwin, Deputy Director, Software Engineering and System Assurance, OUSD(AT&L), April 18, 2007

NDIA Software Industry Experts Panel 14 July DoD Software Gaps ● Estimation ● Risk Identification ● Sustainment ● Interoperability ● Test ● Requirements ● Quality Attributes ● SETA Qualifications ● Human Capital Strategy Source: Kristen Baldwin, Deputy Director, Software Engineering and System Assurance, OUSD(AT&L), April 18, 2007

NDIA Software Industry Experts Panel 14 July DoD Software Gaps ● Estimation ● Risk Identification ● Sustainment ● Interoperability ● Test ● Requirements ● Quality Attributes ● SETA Qualifications ● Human Capital Strategy Source: Kristen Baldwin, Deputy Director, Software Engineering and System Assurance, OUSD(AT&L), April 18, 2007

NDIA Software Industry Experts Panel 14 July Software Industry Experts Panel Action Plan ● Software Points of Influence list –bi-directional commitment ● Software interested parties list –information awareness ● Supporting resolution of identified DoD Software Gaps –Human Capital, Requirements –Risk, Quality Attributes –Test, Estimation –Sustainment –Interoperability, SETA

NDIA Software Industry Experts Panel 14 July Overall Workshop Objectives ● Three Workshop Panels –Software Requirements –Software Risk and Estimation –Software Quality Attributes ● Workshop Objectives For Each Panel –Define a specific plan to crystallize concrete progress within the next 6-18 months –Define work products and a plan to develop them over 6, 12 and 18 month periods –Identify stakeholders relevant to each of these work products

NDIA Software Industry Experts Panel 14 July Software In Acquisition Workshop Tuesday, October 16, 2007Wednesday, October 17, Welcome: Dr Finley - DUSD(A&T) Workshops - continued Keynote: Carl Siel – Navy Chief SE Keynote: Dr Myers, DoD Deputy CIO Industry Presentation – NDIA Software Experts Panel Workshop Outbriefs (3) Presentation Tracks (12 Presentations) Closing Remarks Focused Workshops Attendance: attendees - Services, Agencies, Industry, Academia, FFRDC, NASA Workshop Topics: - Software Requirements - Software Estimation / Software Risk - Software Quality Attributes

NDIA Software Industry Experts Panel 14 July Requirements Workshop Recommendations ● Define an effective “software portfolio” management framework –Protect the continuity of systems/software and requirement engineering throughout the software life cycle ● Implement the techniques we know will work and identify any shortcomings ● Find ways to leverage the malleability of software –Software has the ability to adapt to changing requirements ● Change our view/perspective of “sustainment” to “continuous evolution” ● Establish a research program

NDIA Software Industry Experts Panel 14 July Software Estimation/Risk Recommendations ● Establish Work Breakdown Structure guidance to better highlight Software Engineering activity ● Developing and evolving an integrated software data repository and related tools ● Conduct Root Cause analysis studies to understand the problems in software estimation and the use of estimates in the acquisition process ● Develop and implement an incremental acquisition approach (as well as the overall acquisition framework) that accommodates the uncertainty associated with early software estimates and allows for adjustment and refinement over time ● Establish policy, related guidance, and recommended implementation approaches for software data collection and analysis across all DoD acquisition programs

NDIA Software Industry Experts Panel 14 July Software Quality Attribute Priority Recommendations ● Develop engineering guidance on quantitatively identifying, predicting, evaluating, verifying, and validating Quality Attributes –Address tie-in to KPPs and TPMs –Identify methods for predicting quality attribute outcomes for the delivered system, throughout the life cycle ● Improving OSD/Service-level acquisition policy regarding Quality Attributes –Identify benefits of addressing software quality attributes as part of an acquisition risk reduction strategy –Address gaps in SEP, TEMP, JCIDS, DAG, RFP language –Define expectations for Quality Attribute review during Acquisition Milestone Reviews (e.g. PDR) ● Develop taxonomy of software quality attributes and how they are related ● Develop Program Manager guidance on Introduction to Software Architectural Evaluation of Quality Attributes ● Develop Collaboration site for collecting data, sharing work products, facilitating on-going discussion

NDIA Software Industry Experts Panel 14 July Software In Acquisition Spring Workshop 2008 ● The purpose of this workshop was to be a “touch point” for the actions that resulted from the SSA annual software workshop in October of last year ● Review of issues and recommendations in each of the areas covered under the October workshop: –Requirements –Risk/Cost –Quality Attributes ● Three Working Groups –Software Requirements –Software Risk and Estimation –Software Quality Attributes ● Objectives For Each Working Group –Task Statements –Deliverables –Schedule

NDIA Software Industry Experts Panel 14 July Outcome ● Knit Together Selected “Big Ideas” into Unified Proposed Initiative: ● Leveraging Competitive Prototyping through Acquisition Initiatives in Integrated Systems and Software Requirements, Risk, Estimation, and Quality

NDIA Software Industry Experts Panel 14 July Task Definition ● Task 1: Conduct surveys and interviews of leading software professionals (government, industry, academia) to gather ideas, assess impacts, and sense expectations for Competitive Prototyping ● Task 2: Provide amplification of Competitive Prototyping memo for integrated SE/SW, [including where in the lifecycle there are opportunities for Competitive Prototyping [and how they can be contractually achieved] ● Task 3:Identify first adopters of Competitive Prototyping and facilitate and gather insights on effective usage, including collecting and analyzing data ● Task 4: Develop guidance for early selection and application of integrated SE/SW quality systems for Competitive Prototyping [for RFP-authors] ● Task 5: Develop Software Engineering Handbook for Competitive Prototyping including material explicitly targeted to different audiences (acquirer, supplier, etc.). ● Task 6: Develop training assets (materials, competencies, skill sets, etc.) that capture best-of-class ideas/practices for Competitive Prototyping

NDIA Software Industry Experts Panel 14 July Competitive Prototyping Survey ● Purpose –“To gather recommendations, assess impacts, and sense expectations for Competitive Prototyping" from key members of government, industry, and academia ● Conducted by the Center for Systems and Software Engineering (CSSE), at the University of Southern California (USC) ● The domain of interest for the survey and interviews comprise those projects that are considered large-scale "software- intensive systems" (SiS) –Systems for which software is a principal and defining component –Where software likely represents the key source of technological and programmatic risk in its development –The software development costs of projects of interest should be valued at $100 million, or higher

NDIA Software Industry Experts Panel 14 July OUSD(AT&L)/SSE-USC/CSSE CP Workshop ● OUSD(AT&L)/SSE-USC/CSSE Workshop on Integrating Systems and Software Engineering under Competitive Prototyping with the Incremental Commitment Model –Washington, DC, July 14-17, 2008 ● Discussion of the way forward from the survey through the remainder of the tasks

NDIA Software Industry Experts Panel 14 July For More Information... Paul R. Croll CSC Combs Drive King George, VA Phone: Fax: