Headquarters U. S. Air Force I n t e g r i t y - S e r v i c e - E x c e l l e n c e Air Force Expectations for Software Col William “Bill” P. Nelson Dir,

Slides:



Advertisements
Similar presentations
CURRENT STATE OF ACQUISITION, TEST & EVALUATION ENTERPRISE NOVEMBER 2012 PRESENTATION TO INCOSE ENCHANTMENT CHAPTER Charles Pete Adolph.
Advertisements

© Prentice Hall CHAPTER 15 Managing the IS Function.
Applied IT Architecture Introduction Reference IT architecture & Standards Applied Reference Architecture Governance model Governance process Problems.
AT&L Update Tracking AT&L Initiatives AT&L reorganization
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Headquarters U.S. Air Force Air Force Modeling and Simulation, An AFAMS Perspective Col(S) Marcus.
DoD Software Issues and Gap Identification Kristen Baldwin Deputy Director, Software Engineering and System Assurance OUSD(AT&L) April 18, 2007.
IS 700.a NIMS An Introduction. The NIMS Mandate HSPD-5 requires all Federal departments and agencies to: Adopt and use NIMS in incident management programs.
UNCLASSIFIED 1 Enterprise Architecture Career Path Working Group Walt Okon Senior Architect Engineer Architecture & Infrastructure Directorate Office of.
W5HH Principle As applied to Software Projects
Educating Leaders Since 1884
DoD Systems and Software Engineering A Strategy for Enhanced Systems Engineering Kristen Baldwin Acting Director, Systems and Software Engineering Office.
Chapter 10 Information Systems Management. Agenda Information Systems Department Plan the Use of IT Manage Computing Infrastructure Manage Enterprise.
Chapter 10 Managing the Delivery of Information Services.
Session No. 4 Implementing Service Providers SMS Implementing the State’s Safety Programme SMS Senior Management Workshop Rome, 21 May 2007.
Human Capital Management Assessment Joe Burt Director, HRM March 31, 2004.
CMM Level 3 KPA’s CS4320 Fall Organizational Process Focus (Goals) Software process development and improvement activities are coordinated across.
Revenue Cycle Management Medical Technology Acquisition and Assessment Team Members: Joseph Dixon, Michael Morotti, Mari Pirie-St. Pierre, David Robbins.
“Here’s why you need the new wheels, too…” Shawn and Steve Image from
1 Contractors on the Battlefield Mr. Gary Motsek Assistant Deputy Secretary of Defense (Program Support) November 12, 2009.
Information Systems Planning
2014 E DUCATIONAL T ECHNOLOGY P LAN P ROJECT K ICKOFF.
Implementing an Integrated Environmental, Safety, and Occupational Health Management System (ESOHMS) at the Defense National Stockpile Center James D.
1 IS 8950 Managing and Leading a Networked IT Organization.
9/11/ SUPPORT THE WARFIGHTER DoD CIO 1 Sample Template Community of Interest (COI) Steering Committee Kick-off Date: POC: V1.0.
INTERNET2 COLLABORATIVE INNOVATION PROGRAM DEVELOPMENT Florence D. Hudson Senior Vice President and Chief Innovation.
CORPORATE LEARNING COURSE Seminar 2.4 CAP Structure, Purposes and Procedures.
PRELIM NOTES. Managing Information Resources & Technologies To serve customers well… companies need to be proficient in half a dozen key areas: reduced.
Bayu Priyambadha, S.Kom Teknik Informatika Universitas Brawijaya.
Soft Tech Development Inc. 1 Software Project Tracking A CMM Level 2 Key Process Area Soft Tech Development Inc.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Headquarters U.S. Air Force 1 Lt Gen Bill Lord, SAF/CIO A6 Chief of Warfighting Integration and.
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
By Bankole Ebisemiju At an Intensive & Interactive workshop on Techniques for Effective & Result Oriented Annual Operation Plan November 24th 2010 Annual.
NATO Unclassified Mr. Henrik DAM Chairman SWGI 10/12/2015 NATO Unclassified.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e UPDM Review Session Col. Jack Jibilian Enterprise Architecting & Warfighting Decision Support SAF/XCPA.
Alter – Information Systems © 2002 Prentice Hall 1 The Process of Information System Planning.
Joint Logistics Officer Development 19 November 2006.
Georgia Institute of Technology CS 4320 Fall 2003.
Personnel Requirements for Implementing the New Triad Robert B. Barker December 15, 2005.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Headquarters U.S. Air Force Mr. Wayne Fordham HQ AFCESA/CES 2004 DoD PM Workshop Enlisted Pest.
 Management ◦ The activities and tasks undertaken by one or more persons for the purpose of planning and controlling the activities of other in order.
Lecture 4. Software Engineering Body of Knowledge SWEBOK  Articulating a body of knowledge is an essential step toward developing a profession because.
DoD Logistics Human Capital Strategic Planning Overview June 26, 2007.
Fermilab Presentation Greg Bock, Pepin Carolan, Mike Lindgren, Elaine McCluskey 2014 SC PM Workshop July 2014.
CONGREGATIONAL RESPONSIBILITIES Three Key Roles: 1) Senior Pastor of the local United Methodist Church 2) Disaster Response Coordinator (DRC) 3)Trustees.
November 15, 2007 The “ABC” of Effective Field Monitoring & Supervision November 15, 2007.
Marv Adams Chief Information Officer November 29, 2001.
Perspectives on the Analysis M&S Business Plan Dr. Tom Allen, IDA Mr. James Bexfield, PA&E, OSD Dr. Stuart Starr, IDA June 19, 2008.
Succession Planning Based loosely on “Effective Succession Planning in the Public Sector,” 2007, Watson Wyatt Worldwide Based loosely on “Effective Succession.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Headquarters U.S. Air Force AIR FORCE CAUCUS John Heliotis AF DepSO.
Statewide Radio Feasibility Study (SIRN) Presented by Tom Harris SIEC Chair Mike Ressler.
Joint Concept Development and Experimentation (JCD&E)
NSDI Strategic Plan Update January 14, NSDI Strategic Plan High-level Timeline 2 Timeframe Activity Dec - Feb Project Start-up – COMPLETED Feb -
Chapter 9 The People in Information Systems. Learning Objectives Upon successful completion of this chapter, you will be able to: Describe each of the.
Generic competencesDescription of the Competence Learning Competence The student  possesses the capability to evaluate and develop one’s own competences.
UNCLASSIFIED / FOR OFFICIAL USE ONLY USAFMCOM UNCLASSIFIED / FOR OFFICIAL USE ONLY.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
Implementing Program Management Standards at Duke Energy.
DHS FEMA Region IX Response Operations. FEMA Region IX Jurisdictions Pacific Area Office (Ft. Shafter, HI) Hawaii 2500 miles Guam 3700 miles American.
PRE-PLANNING FOR CONSTRUCTION PROJECTS. OVERVIEW ASSESSING OWNER CAPABILITIES ANALYSIS OF RESOURCES REGULATORY REQUIREMENTS SITE DEVELOPMENT REVIEWING.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Headquarters U.S. Air Force As of:1 Mrs. Marty Evans SE Forum October 15, 2004 Institutionalizing.
Richard Escritt, Director – Coordination of Community Actions DG Research, European Commission “The development of the ERA: Experiences from FP6 and reflections.
Center of Excellence PEACE OPERATIONS COMMAND & CONTROL AND COMMAND & CONTROL AND TRANSITION ISSUES Lt Col (R) John Derick Osman Center of Excellence in.
TRADITIONAL OFFICER VACANCY ANNOUNCEMENT NEW YORK AIR NATIONAL GUARD 174th ATTACK WING 6001 EAST MOLLOY ROAD SYRACUSE, NY ANNOUNCEMENT#: FY.
Role Responsibilities
By Jeff Burklo, Director
Combatant Commanders’ Future Logistics Support Perspectives
FY 2007 Department of Defense Budget
Steering Committee Brief to the DoD M&S Conference 2008
Founded in 1920, the Society of American Military Engineers leads collaborative efforts to identify and resolve national security infrastructure-related.
Presentation transcript:

Headquarters U. S. Air Force I n t e g r i t y - S e r v i c e - E x c e l l e n c e Air Force Expectations for Software Col William “Bill” P. Nelson Dir, Architecture and Interoperability (703)

I n t e g r i t y - S e r v i c e - E x c e l l e n c e 2 Outline Software Sustainment Issues National Science Foundation (NSF) Findings Software Personnel Software Intensive Systems Steering Groups Key to Success

I n t e g r i t y - S e r v i c e - E x c e l l e n c e 3 Software Sustainment Issues* Computer Resources and System / Software Engineering Environment (S/SEE) Capability: Obsolete and/or saturated computer hardware; adequacy and long-term viability of the support / test environment, programming language, etc. Guidance: Lack of policy, guidance, and methods for SIWS acquisition and support Documentation: Inadequate or outdated system/software documentation Training: Lack of appropriate and timely training Staffing: Software engineering staff instability or shortages *AF CIO directed study “Weapon System Software Sustainment Study”, Apr 2001

I n t e g r i t y - S e r v i c e - E x c e l l e n c e 4 * Final Report, “NSF Workshop on a Research Program for the 21st Century”, 1998 NSF Findings* Software has to many surprises Immature or poorly integrated software domain sciences, construction principles and engineering processes Critical software components Scalability; evolvability; dependability; usability; performance; and predictability of cost and schedule Software technology is hard to transition

I n t e g r i t y - S e r v i c e - E x c e l l e n c e 5 AF Picture: Software Personnel Software professionals very important part of the Air Force -- communications and information community in particular Information War over Kosovo American troops rescuing flood victims in Mozambique and providing aid to reduce human suffering Unmanned Aerial Vehicles (UAVs) and Unmanned Combat Aerial Vehicles (UCAVs) Smart bombs B-2

I n t e g r i t y - S e r v i c e - E x c e l l e n c e 6 *Lt Gen John L. Woodward, Jr remarks to Software Technology Conference 1 May 2001 Types of Programmers* Two camps of programmers in the Air Force System programmers-- TBMCS, GCCS, and other application-oriented software Specialized software professionals--designed and built the code embedded in our weapon systems That distinction is disappearing as we move into the 21st Century Our weapons are becoming increasingly networked—“on the net” until the moment of impact As network evolves to a weapon system, distinction between “traditional” and “weapon system” software professionals blurs Development methods/sustainment procedures for both beginning to resemble each other

I n t e g r i t y - S e r v i c e - E x c e l l e n c e 7 *Lt Gen John L. Woodward, Jr remarks to Software Technology Conference 1 May 2001 Software Career Field* (Communications-computer career field perspective) Fiscal year (2000), only 29% of first-term enlisted programmers reenlisted (AF goal is 55%) As of May 2001, only 31% of second-term enlisted programmers who are eligible for reenlistment have done so (AF goal is 75%) No longer track officer programmers in communications-computer career field but continuation rate of these highly-skilled officers appears to be below Air Force average In Air Logistics Centers, missed hiring targets for civilian programmers in 1999 and 2000

I n t e g r i t y - S e r v i c e - E x c e l l e n c e 8 Software Intensive Systems Steering Group (SISSG) DoD SISSG strategic directionsoftware intensive systemsprioritize joint activities Establish strategic direction, oversee the DoD software intensive systems effort, and prioritize joint activities that have significant improvement potential SAF/AQRE current AF rep No AF/SC and PDAS-BIM (AF software team ???) AFMC SISSG AFMC software intensive systems focus Charter under revision AF SISSG Morph to AF SISSG AF-level AF-level software intensive systems focus

I n t e g r i t y - S e r v i c e - E x c e l l e n c e 9 Air Force SISSG SECAF - Need HQ focus on Software SAF/AQR, AF/IL agreed on need for AF SISSG Proposed AF SISSG: Chaired by SAF/AQR AF/ILM, AF/SCT, AF/XOC and CIO-BIM AF SIS Working Group AOs from AF SISSG members Staff, coordinate issues/actions for AF SISSG AF Software Team (CIO-BIM; AF/SC; SAF/AQ; AF/IL)

I n t e g r i t y - S e r v i c e - E x c e l l e n c e 10 Key Factors for Success... Corporate Approach Senior Leader Oversight Ability Enforceable policies (SC & AQ) Business process definition Software belly-button (AF Software Team) Identification of software houses (who is doing software in the AF)

I n t e g r i t y - S e r v i c e - E x c e l l e n c e 11 QUESTIONS