dr. jack r. ferguson deputy director for software intensive systems
DESCRIPTION
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. - PowerPoint PPT PresentationTRANSCRIPT
Dr. Jack R. FergusonDr. Jack R. FergusonDeputy Director for Software Intensive SystemsDeputy Director for Software Intensive Systems
Acquisition Resources and AnalysisAcquisition Resources and Analysis
DoD Software Engineering Science & Technology Summit
DoD Software Engineering Science & Technology Summit
August 7-9, 2001August 7-9, 2001
Global US InterestsPolitical - Economic - Humanitarian
Globalization of Technology
Asymmetric ThreatsIn any domain - Air, Land, Sea, Space or Information
Strategic Environment
• Avionics• Engine control• Sensors• Data collection
Airborne Systems:138K SLOC
C, PLM
Predator UAV
Tactical surveillance
Predator Unmanned Aerial Vehicle
• Ground control • Communications • Data manipulation• Training simulation• Mission planning
Predator Ground Control Station
Ground Systems:487K SLOC
C, PLM
Predator Unmanned Aerial Vehicle
Airborne Systems: 1992K SLOCAda, C, Assembly
Cockpit functions
Target acquisition
Armament98K
Communications
Flight control155K
Engine control57K
Train & test instrumentation
Night pilot
Radar170K
Mission equipment package1512K
Reconnaissanceand attack
Comanche RAH-66
Training 1182KSupport 127KIntegration 144K
Ground Systems: 1453K SLOCAda, C, Assembly
Comanche RAH-66
Comanche RAH-66
Arleigh Burke Destroyer
Display 1200KTest 385KWeapon 266KTraining 110KCommand & decision 337K
Radar 279K
Continuous wave illuminators 15K
2,592K SLOCAda, C++
Complete weapon system -Deployed on destroyers and cruisers
AEGIS Weapon System
Control segment User segment
Space segment
Ground antennaMonitor stationMaster control
Communications
NAVSTARGlobal Positioning System
II/IIA23 satellites
IIR6 satellites
Deployed:24K SLOCper satellite
Ada
Deployed Future
IIF
Future:71K SLOCper satellite
Ada(24 spacecraft required)
NAVSTAR Space Segment
• Navigation• Telemetry• Tracking • Orbit analysis• Scheduling• Infrastructure Master control station, Schriever AFB
Deployed:1800K SLOC
Jovial
Future:1900K SLOC
C++
NAVSTAR Control Segment
Precision lightweightGPS receiver100K SLOC
Defense advancedGPS receiver200K SLOC
MiniaturizedAirborne
GPS receiver100K SLOC
80K-200K SLOCJovial
NAVSTAR User Segment
150K SLOC - Weapon2K SLOC - Ammunition
Ada
Infantry Combat Weapon 130K SLOCAda, C++, C, Assembly
Wide Area Munition
Software is Even in Bullets!
In warfighting, software In warfighting, software has become the soul of has become the soul of our weapons.our weapons.
In warfighting, software In warfighting, software has become the soul of has become the soul of our weapons.our weapons.
Software challenges:
• System complexity• Greater dependency • Huge legacy backlog • Growing investment in development and sustainment (but not S&T)
The DoD and our sons’ and daughters’ lives depend on Software Intensive Systems
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
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
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
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)
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)
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