NDIA Software Industry Experts Panel Paul R. Croll, Chair NDIA Systems Engineering Division Meeting 24 June 2008.

Slides:



Advertisements
Similar presentations
Team 6 Lesson 3 Gary J Brumbelow Matt DeMonbrun Elias Lopez Rita Martin.
Advertisements

NDIA System Engineering Division 2012 Task #4 October INTERIM PROGRESS REPORT.
Low Defect Potentials (< 1 per function point)
The System Development Life Cycle
Envision SFA developing the next strategic plan….
Joint Working Group for DoD Systems Engineering Standardization
The Challenge The retailing and shopping center sector is experiencing one of the most profound and thoroughgoing transformations in its 60-year history.
ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
COSYSMO 2.0 Workshop Summary (held Monday, March 17 th 2008) USC CSSE Annual Research Review March 18, 2008 Jared Fortune.
Gu & Maher University of Sydney, October 2004 DECO2005 Monitoring Team Process.
NDIA Software Industry Experts Panel 14 July NDIA 11 th Anuual Systems Engineering Conference Software in Acquisition Working Groups Software Track.
Root Cause Analysis Procedure (IMSP525) Training
COSYSMO: Constructive Systems Engineering Cost Model Ricardo Valerdi USC CSE Workshop October 25, 2001.
NDIA Software Industry Experts Panel 14 July NDIA Software Industry Experts Panel Paul R. Croll, Chair NDIA Systems Engineering Division.
Software and System Engineering Integration Sponsor Overview Kristen Baldwin Deputy Director, Software Engineering and System Assurance Office of the Under.
COSOSIMO* Workshop 13 March 2006 Jo Ann Lane University of Southern California Center for Software Engineering CSE Annual.
Software in Acquisition Workshop Software Expert Panel Working Groups and Tasks Rick Selby DoD Software In Acquisition.
University of Southern California Center for Systems and Software Engineering Next Generation Estimation Methods and Management Metrics: Working Group.
6/17/ :30:49 PM _Teamwork Competitive Prototyping Challenges for DoD and Industry Paul Croll, AMND Fellow May 28, 2008.
Requirements Analysis INCOSE Systems Engineering Boot Camp
Proposed Revisions for Updating the Software Guidance in MIL-HDBK-881A: Work Breakdown Structures for Material Items OUSD(AT&L)/SSE-USC/CSSE Workshop on.
System-of-Systems Cost Modeling: COSOSIMO July 2005 Workshop Results Jo Ann Lane University of Southern California Center for Software Engineering.
14 July 2008 Blake Ireland Industry Roundtable COMPETITIVE PROTOTYPING.
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,
University of Southern California Center for Systems and Software Engineering July 2008ICM and CP Workshop © USC-CSSE1 Initial Competitive Prototyping.
University of Southern California Center for Systems and Software Engineering Integrating Systems and Software Engineering: Complex Systems Workshop 29.
PRESENTED BY TRUST THOMAS EROMOSELE STUDENT NO:
The Current Status of States' Early Childhood Outcome Measurement Systems Kathy Hebbeler, SRI International Lynne Kahn, FPG Child Dev Inst October 17,
What is Business Analysis Planning & Monitoring?
Chapter : Software Process
SEI´S Software Product Line Tenets Linda M. Northrop Software Engineering Institute IEEE Software July/August 2002.
Dale Norwood PFM Consulting “Keeping Customers First”
NDIA PMSC Scheduling Working Group. Exploratory working group Objective Objective Brainstorm and explore concerns and issues in scheduling bring them.
NDIA SE Division Meeting February 13, Developmental Test and Evaluation Committee Beth Wilson, Raytheon Steve Scukanec, Northrop Grumman Industry.
Continuous Improvement Collecting, Analyzing, and Sharing Data.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Business Analysis and Essential Competencies
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Understanding Industry Defense Acquisition University 13 May 2010 Status Brief to NDIA Program Systems Committee.
March 26-28, 2013 SINGAPORE CDIO Asian Regional Meeting and Workshop on Engineering Education and Policies for Regional Leaders Programme Evaluation (CDIO.
Chapter 7: A Summary of Tools Focus: This chapter outlines all the customer-driven project management tools and techniques and provides recommendations.
Applying Business Process Re-engineering
NDIA SE Division – Annual Planning Meeting December 11-12, CMMI ® Project Status – 2013 Task Summary Stewardship of CMMI product suite officially.
NDIA HSI Committee Status Elaine Thorpe, Boeing Stuart Booth, OSD 18 August 2010.
Software Product Line Material based on slides and chapter by Linda M. Northrop, SEI.
NDIA SE Division – Annual Planning Meeting December 12-13, NDIA Meetings SEI (SW Engineering Institute) SoS Architecture Patterns -SEI is developing.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Government and Industry IT: one vision, one community IAC Shared Interest Groups (SIGs) Review October 26, 2009.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
IT-465 Introduction to Lean part Two. IT-465 Lean Manufacturing2 Introduction Waste Walks and Spaghetti Charts Outcomes Understand what a waste walk is.
Audience Profiles RoleKey CharacteristicsValues & NeedsRecommendations C-Level Execs Challenge and opportunity is to capitalize on executives’ critical.
Presented to: NDIA By: Keith Kratzert Date: February 1, 2006 Federal Aviation Administration Improving Program Performance at FAA.
1 The Voice of the Industrial Base 1 IBR Guide NDIA PMSC Working Group NDIA PMSC Meeting August 7, 2007 Prepared by; NDIA IBR Working Group August 2007.
Practical Scheduling – PMICOS in Australia Presented by: Ed Blow (MTC Australasia Pty Ltd) 2 November 2005 PMI-College of Scheduling.
Brian Alpert July 14, 2010 Leveraging Web Analytics and Search Engine Optimization (SEO) Project Workshop.
Logistics Community Competency Initiative Update November 20, 2006 Mark Tregar, CNAC Judith Bayliss, DAU “The Total Force must continue to adapt to different.
Agenda  Purpose  Processes  Deliverables  Executing Activities 4.3.
ICOTE Meeting October, Chief Developmental Tester Project Status for ICOTE October 2014 Brendan Rhatigan – Lockheed Martin.
The System Development Life Cycle
Colorado Alternative Cooperative Education (ACE) CTE Redesign CACTE July 2017 Key Messages for Early Implementation & Change Management in SY
Instructional Leadership for a Professional Learning Culture:
A Framework for Integrating Systems and Software Engineering
Applying Business Process Re-engineering
TechStambha PMP Certification Training
Implementation Strategy July 2002
SEI SCAMPI B/C Project: A Partner’s Perspective
The System Development Life Cycle
COSYSMO: Constructive Systems Engineering Cost Model
Presentation transcript:

NDIA Software Industry Experts Panel Paul R. Croll, Chair NDIA Systems Engineering Division Meeting 24 June 2008

2 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

3 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

4 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

5 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

6 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

7 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

8 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

Questions?