Please enable JavaScript.
Coggle requires JavaScript to display documents.
F-16 Fighting Falcon Architecture Issues (Principles of System…
F-16 Fighting Falcon Architecture Issues
Principles of System Architecture
Principle of Apparent Complexity
Principle of Balance
Principle of Product Evolution
Principle of Coupling and Organization of Architectural Decisions
Principle of Decomposition
Software Issue Areas
S.1 Operational Flight Program
Late to Flight Test and Less complete
Immaturity of software language (Jovial J73)
Software complexity and
Access to Software Test Stations
Compiler inadequacies
S.2 Cockpit Remechanization
Schedule slip
Mock-ups did not identify shortcomings
Software redesign
Hardware redesign
S.3 Subsystem Integration
Production schedule delays
Inadequate GFAE
Unexpected software changes
Difficulties in hardware production
Complexity of software
Multinational Staged Improvement Program
Stage I
Essential Structure
Wiring
Interface Provisions
Stage II
New Aircraft Avionics
Subsystem Improvements
Wiring and Environmental Control Provisions
Single Pilot Operability
A Fire Control Radar
Multifunction Display Set (WDS)
Up-Front Communication/Navigation/Identification (CNI)
Data Transfer Equipment (DTE)
Combined Altitude Radar Altimeter (CARA)
Enhanced Fire Control Computer (EFCC)
Advanced Stores Management Subsystem (ASMS)
Head Up Display (HUD)
Group A: Crash Survivable Flight Data Recorder (CSRDR)
Stage III
Advanced Medium Range Air-to-Air Missile (AMRAAM)
Low Altitude Navigation and Targeting, Infrared, Night (LANTIRN) navigation and targeting pods
Enhanced Joint Tactical Enformation Display System (EJS) radio
Airborne Self-Protection Jammer (ASPJ)
Electronic Counter Measures (ECM)
Global Positioning System (GPS)
Precision Location Strike System (PLSS)
MSIP Technical Performance Assessments
Stage I: Low
Stage II: Low to Moderate
Stage III: Moderate
Architectural Issues
MSIP Implementation
November 1981
: MSIP I Aircraft: Inadequate computing power, bandwidth, and display capability for enhancements
May 1983:
MSIP 11: Draft software development plan submitted to government.
Final edition did not incorporate gov't comments: Schedule Delay
January 1983:
MSIP II Test Aircraft: Software and hardware problems become apparent
(S.1, S.2, S.3)
March 1985
MSIP Baseline Capabilities Delivered; S/W and HW modifications and development difficulties addressed
April 1984
Software Issues Addressed
Problem Recognition
Technology Development Forecasting
Define and analyze: Measurable and understandable terms for software
Additional Manpower: Not a viable solution.
Senior Management Actions
Withdraw from additional programs
Reorganize and reduce supervision ratio
Split Software Engineering/Development
F16 System Engineering
F-111 Systems Engineering
Validation and testing
Establish a Planning Control Function
Relocate Software Test Stations to Electronic Systems and Laboratories Department
Establish Executive Software Review Committee