DoD Software Systems.  Characteristics of DoD S/W Development  Evolution of DoD S/W Development  Learning from the Commercial World  Additional Technologies.

Slides:



Advertisements
Similar presentations
Prescriptive Process models
Advertisements

Incremental Commitment Spiral Model, Expedited Engineering, and Kanban Jo Ann Lane and Alexey Tregubov USC CSSE Rich Turner Stevens University.
BENEFITS OF SUCCESSFUL IT MODERNIZATION
Object-Oriented Software Development CS 3331 Fall 2009.
CSE 470 : Software Engineering The Software Process.
Inc. User Requirements Presentation DoD Automatic Test Systems Michael Malesich DoD ATS R&D IPT Chair.
2003 Indigo Technology, Inc. All Rights Reserved Alliance Portfolio Computing Infrastructure Services Customer Relationship Management Engineering Services.
Stepan Potiyenko ISS Sr.SW Developer.
Agile Software Development. Traditional Software Development 1.Initiation (RFP) 2.Feasibility study Technical – can we build it? Economic – should we.
DoD Systems and Software Engineering A Strategy for Enhanced Systems Engineering Kristen Baldwin Acting Director, Systems and Software Engineering Office.
SE 470 Software Development Processes James Nowotarski 12 May 2003.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Recent Trends in DoD Systems and Software Engineering Processes Bruce Amato Acting Deputy Director, Software Engineering and Systems Assurance Office of.
Effective Methods for Software and Systems Integration
Tsvetelina Kovacheva, Quality Manager Musala Soft June 19, 2007 Implementing Models and Standards for Software Development Benefits and Risks.
1 Software Engineering Muhammad Fahad Khan Software Engineering Muhammad Fahad Khan University Of Engineering.
Integrated Capability Maturity Model (CMMI)
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
The Capability Maturity Model in Software Development Paul X. Harder, JD Government Micro Resources, Inc. September 14, 2004.
Chapter 2 The process Process, Methods, and Tools
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
CMMi What is CMMi? Basic terms Levels Common Features Assessment process List of KPAs for each level.
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
Future Airborne Capability Environment (FACE)
Lecture 1 Introduction to Software Engineering
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
NDIA Systems Engineering Supportability & Interoperability Conference October 2003 Using Six Sigma to Improve Systems Engineering Rick Hefner, Ph.D.
Panel Three - Small Businesses: Sustaining and Growing a Market Presence Open Interfaces and Market Penetration Protecting Intellectual Innovation and.
Software Life-Cycle Models Somnuk Keretho, Assistant Professor Department of Computer Engineering Faculty of Engineering, Kasetsart University
 CS 5380 Software Engineering Chapter 2 – Software Processes Chapter 2 Software Processes1.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
IT Requirements Management Balancing Needs and Expectations.
Software process improvement Framework for SPI SPI support groups, maturity and immaturity models Assessment and gap analysis Education and training Selection.
Software Engineering Principles Principles form the basis of methods, techniques, methodologies and tools Principles form the basis of methods, techniques,
Quality Activity Matrix Presented by Sandra Toalston President, SanSeek 1.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Project & Risk Management For next class -- Pressman: 3, , 5.8, , 6.6 Introductions Software Development Processes Software Maturity Models.
1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 7/e Chapter 2.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 Overview of Maintenance CPRE 416-Software Evolution and Maintenance-Lecture 3.
Ch7: Software Production Process. 1 Waterfall models  Invented in the late 1950s for large air defense systems, popularized in the 1970s  Main characteristics:
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
SOFTWARE PROCESS IMPROVEMENT
CMMI ® – The Current State Presented by Gregory Shelton Corporate Vice President Engineering, Technology, Manufacturing & Quality 3 rd Annual CMMI Technology.
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
Software Engineering (CSI 321) Software Process: A Generic View 1.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Lectures 2 & 3: Software Process Models Neelam Gupta.
Introduction Requirements and the Software Lifecycle (3)
Project Management Strategies Hidden in the CMMI Rick Hefner, Northrop Grumman CMMI Technology Conference & User Group November.
Software Development Security Chapter 10 Part 3 Pages 1108 to 1125.
© NALO Solutions Limited NALO Solutions, presents the – Revenue Collector App Using Mobile Phones to gather Revenue SOFTWARE ENGINEERING.
Configuration Control (Aliases: change control, change management )
Supplier Management Can’t live with them, Can’t live without them!
Lecture 0 Software Engineering Course Introduction
Software Life Cycle “What happens in the ‘life’ of software”
THE PROCESS OF EMBEDDED SYSTEM DEVELOPMENT
Software Engineering (CSI 321)
Chapter 2 The Process.
Introduction To software engineering
Chapter 2 The Process.
Software Design & Production Methodologies
Capability Maturity Model
Presentation transcript:

DoD Software Systems

 Characteristics of DoD S/W Development  Evolution of DoD S/W Development  Learning from the Commercial World  Additional Technologies  Approach and Implementation

Characteristics of DoD S/W Development  It’s a Government Acquisition Competitive bidding, development specification part of RFP Awarded to and, designed and implemented by civilian contractor(s) Contractor has personnel requirements Contractor has procurement and reporting rules And adherence to DoD and military standards RFP: Request for Proposal

Characteristics of DoD S/W Development  Approach and Implementation Extensive planning Long delivery schedule (IOC) Process driven Formal project management Rigorous quality control Oversight/formal reviews Documentation intensive  Sequenced Activities Defined by DoD or military standard Interim design reviews Verification activities IOC: Initial Operating Capability

Characteristics of DoD S/W Development  In Most Cases it’s Requirements Driven  Requirements Can Get to be Volatile Long delivery cycles means folks have time to think Risk management activities are key to managing requirements  Development Requires Focus on Minimizing Volatility Risk

Military Flight Simulator Depicted: Cockpit w/ Yoke, Throttle & Rudders Instrument Panel w/ Heads Up Display (HUD) and Multifunction Displays (MFDs) Instructor Operator Station (IOS) Simultec Full Mission Simulator

Military Flight Simulator

It’s the Software That Makes it all Work! Software Behind the Scenes …This is what the trainer looks like.

Evolution of DoD S/W Development  Moore’s Law Helps Explain the Advancement of Technology Which Benefits Processing speed Disk capacity Memory capacity  Working with the Hardware Initially programming the hardware required intimate knowledge of the target H/W From machine code/assembly language Towards independence from target H/W And to the mature complier tools we use today Moore’s Law: The number of components in an integrated circuit doubles approximately every two years.

Evolution of DoD S/W Development  Evolution of Languages Languages used to develop DoD applications numbered over 400 Different languages for different problems Focus now is more of extensions to the more recent languages; C++  Language Standardization/Extensions Wrappers/Plug-ins Math Libraries/Special Functions/Reuse Reusable standards/components  Maintenance on Legacy Systems Still Biggest Cost; Fortran, Pascal, Jovial, Ada…

Evolution of DoD S/W Development  Process Models Originally ads-hoc development Adoption of disciplined approach introduce less defects, meaning less rework SEI’s CMMI establishes levels of maturity ISO 9001 establishes quality standards for software products  Variation of Approaches have Evolved Waterfall Evolutionary (incremental, spiral, agile…)

Evolution of DoD S/W Development  Moving Towards Adopting Commercial Practices Tailor processes to developer’s best practices Leverage on evolving and maturing development standards and methods Application under development determines the approach  Development Methods have Evolved Structured Analysis / Structured Design Object Oriented Agile  It’s iPhone vs Space Shuttle

Learning from the Commercial World  Development Flexibility Agile vs disciplined balanced development approach Tailored engineering work products Reduced documentation Testing approaches  Scaling is Key Scope Team Time

Additional Technologies  Information Assurance / Cyber Security  Architectures  Maintenance  Configuration Management  Logistics

Architecture Models for Integrating S/W

Can’t Do It Without A Team  It’s a team effort that goes into the success of the software design/development and  It’s the individual talent within the team that ensures the team’s success

Personnel/Team Capability Trumps All

References  Cook, David A., CrossTalk Journal of Defense Software Engineering, CrossTalk and Software – Past, Present and Future.  Hinchcliffe, Dion, Architectures,  Boehm, Barry, Software Engineering Economics.  Jones, Capers, CrossTalk Journal of Defense Software Engineering, Defense Software Development in Evolution.  Kennedy, Matthew, CrossTalk Journal of Defense Software Engineering, An Agile Systems Engineering Process.  Cook, David A., CrossTalk Journal of Defense Software Engineering, Evolutionary Trends in Programming Languages.