Do D Software Systems Do D Software Systems

Do. D Software Systems

Do. D Software Systems Ø Characteristics of Do. D S/W Development Ø Evolution of Do. D S/W Development Ø Learning from the Commercial World Ø Additional Technologies Ø Approach and Implementation

Characteristics of Do. D 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 Do. D and military standards RFP: Request for Proposal

Characteristics of Do. D 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 Do. D or military standard • Interim design reviews • Verification activities IOC: Initial Operating Capability

Characteristics of Do. D 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 Simultec Full Mission Simulator Depicted: Cockpit w/ Yoke, Throttle & Rudders Instrument Panel w/ Heads Up Display (HUD) and Multifunction Displays (MFDs) Instructor Operator Station (IOS)

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 Do. D 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 Do. D S/W Development Ø Evolution of Languages • Languages used to develop Do. D 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 Do. D 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 Do. D 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 i. Phone 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. , Cross. Talk Journal of Defense Software Engineering, Cross. Talk and Software – Past, Present and Future. Ø Hinchcliffe, Dion, Architectures, http: hinchcliffe. org. Ø Boehm, Barry, Software Engineering Economics. Ø Jones, Capers, Cross. Talk Journal of Defense Software Engineering, Defense Software Development in Evolution. Ø Kennedy, Matthew, Cross. Talk Journal of Defense Software Engineering, An Agile Systems Engineering Process. Ø Cook, David A. , Cross. Talk Journal of Defense Software Engineering, Evolutionary Trends in Programming Languages.