1 / 21

Dr. Jack R. Ferguson Deputy Director for Software Intensive Systems

DoD Software Engineering Science & Technology Summit. August 7-9, 2001. Dr. Jack R. Ferguson Deputy Director for Software Intensive Systems Acquisition Resources and Analysis. Strategic Environment. Global US Interests Political - Economic - Humanitarian. Globalization of Technology.

newman
Download Presentation

Dr. Jack R. Ferguson Deputy Director for Software Intensive Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DoD Software Engineering Science & Technology Summit August 7-9, 2001 Dr. Jack R. Ferguson Deputy Director for Software Intensive Systems Acquisition Resources and Analysis

  2. Strategic Environment Global US Interests Political - Economic - Humanitarian Globalization of Technology Asymmetric Threats In any domain - Air, Land, Sea, Space or Information

  3. Predator Unmanned Aerial Vehicle Tactical surveillance Airborne Systems: 138K SLOC C, PLM • Avionics • Engine control • Sensors • Data collection Predator UAV

  4. Predator Unmanned Aerial Vehicle Ground Systems: 487K SLOC C, PLM • Ground control • Communications • Data manipulation • Training simulation • Mission planning Predator Ground Control Station

  5. Comanche RAH-66 Airborne Systems: 1992K SLOC Ada, C, Assembly Reconnaissance and attack Flight control 155K Radar 170K Cockpit functions Engine control 57K Night pilot Target acquisition Train & test instrumentation Communications Armament 98K Mission equipment package 1512K

  6. Comanche RAH-66 Ground Systems: 1453K SLOC Ada, C, Assembly Training 1182K Support 127K Integration 144K Comanche RAH-66

  7. AEGIS Weapon System Complete weapon system - Deployed on destroyers and cruisers 2,592K SLOC Ada, C++ Continuous wave illuminators 15K Radar 279K Display 1200KTest 385K Weapon 266K Training 110K Command & decision 337K Arleigh Burke Destroyer

  8. NAVSTARGlobal Positioning System Communications Space segment Ground antenna Monitor station Master control User segment Control segment

  9. NAVSTAR Space Segment Future IIF Deployed II/IIA 23 satellites Deployed: 24K SLOC per satellite Ada Future: 71K SLOCper satelliteAda IIR 6 satellites (24 spacecraft required)

  10. NAVSTAR Control Segment Deployed: 1800K SLOC Jovial Future: 1900K SLOC C++ • Navigation • Telemetry • Tracking • Orbit analysis • Scheduling • Infrastructure Master control station, Schriever AFB

  11. NAVSTAR User Segment Miniaturized Airborne GPS receiver 100K SLOC Precision lightweight GPS receiver 100K SLOC Defense advanced GPS receiver 200K SLOC 80K-200K SLOC Jovial

  12. Software is Even in Bullets! 150K SLOC - Weapon 2K SLOC - Ammunition Ada Wide Area Munition Infantry Combat Weapon 130K SLOC Ada, C++, C, Assembly

  13. In warfighting, software has become the soul of our weapons. The DoD and our sons’ and daughters’ lives depend on Software Intensive Systems • Software challenges: • System complexity • Greater dependency • Huge legacy backlog • Growing investment in development and sustainment (but not S&T)

  14. S&T Challenge: Match the Solutions to the Problems Major DoD software problems are in software processes, tools and management • Need better S&T base in these areas • Especially with new evolutionary acquisition processes Current DoD software S&T investments are skewed toward product S&T • Although more is needed in software product S&T also DoD requires a balanced software S&T program addressing all its needs • Including expedited technology transition OSD-SIS looking for Summit to provide innovative need-oriented ideas • With strong benefit rationale

  15. Some of these needs Fielding complex critical functionality with software that has controlled and managed: • Safety • Reliability • Interoperability • Correctness • Maintainability • Cost and Schedule • Predictability • High Performance • Security Bringing software development cycles in line with hardware (and with the industrial market) • Better designs and architectures • Faster development • Fewer defects • Programmable H/W (FPGAs) – Multifunction • Multi-process synchronization Flexible, interoperable software systems • Self-adapting and self-aware • Extensible • Secure • Separable • Distributed

  16. Some of these needs - 2 New languages, methods, tools and compilers • Support Component concepts • Extend the Ada engineering concepts • Provide for higher levels of abstraction • E-Technologies • Object Oriented • Network Centric • Integrating autonomous systems New ways of defining requirements and designs • Executable • Evolutionary • Model-based • Provable • Interoperable, system-of-systems • Traceable • Risk-driven New ways of testing, fault identification and isolation • Model-based testing • Self testing, self correcting code • Testing large systems • Testing interoperability • Balanced analysis-review-test strategies

  17. COTS Challenges COTS integration principles, methods and tools • Synchronizing system and COTS vendor upgrade cycles • Tools and testbeds supporting COTS and equipment upgrades, and analysis of conflict between and among separate COTS products and government software • Domain compatibility analysis • Estimating, planning and documentation aids • COTS wrappers, connectors and other architectural approaches • Empirical analysis of COTS-based systems Architecture and negotiation techniques for COTS functionality changes, as they are under the control of the vendor, not the government Tools needed to ascertain reliability, safety and security of COTS products • Security (including origin risk and potential for Trojan Horse or other malicious code)

  18. Some ideas Expand and combine existing technologies • CMMI SW SE (product development improvement, not individual discipline improvement) • Merge System Engineering and software engineering technologies Methods for hurdling political and process barriers • Product lines • Evolutionary Acquisition • Multiple contractors • Competition without excessive information hiding Determine and use “jointness in development” success factors • Common components • Common architectures Experimentation – Demonstrate the efficacy of technologies • Design of Experiments (DOE) • Measurement/Analysis techniques Transition • Mixed DoD track record of transitioning tools (COBOL, IDEF, ARPAnet, OO tools, STARS, Ada, requirements languages) • Demonstrate system success base as dramatically improved Value, Reliability and Maintainability- Not just Performance, Cost and Schedule Knowledge • Better ways to reuse knowledge about software process (CeBASE Experience Factory)

  19. Challenge to Summit Participants The DoD community is making progress in employing current best software practices • SW-CMM and CMMI practices • Independent Expert Program Reviews • Practical Software and Systems Measurement • Architecture-based approaches Further progress depends on finding solutions to new DoD software challenges • COTS, evolutionary acquisition, legacy systems, massive distribution, agent coordination, mobility, rapid change, talent shortage, systems of systems We need your help in providing innovative DoD-need-oriented ideas • with strong benefit rationale

More Related