2 ms·
I think it's more complicated than that. If you develop avionics and engines for a single specific craft, then you can be focused on the requirements at hand a
by aidenn0 11y ago
I think it's more complicated than that. If you develop avionics and engines for a single specific craft, then you can be focused on the requirements at hand and a single working version. When you develop them for 3 or 4 crafts all at the same time, the feature creep gets pushed back into those modules as well.
I bet most of the avionics that get adapted for a new plane require some modification to get them working. This is, IMO, much easier if you start from a working version.
Consider the semi-disaster that is JTRS[1] (basically the f-35 of software defined radios). It was designed to be modular, and that was part of the failure. If they had picked a single form-factor that was useful in isolation, that would have allowed a single system to get up and running, and then it would make sense to grow it out from there, reusing where it made sense to.
Instead there was this byzantine connection of interdependencies and parallel development with few integration points that seemed likely to doom it.
1: https://en.wikipedia.org/wiki/Joint_Tactical_Radio_System#Problems_and_restructuring https://en.wikipedia.org/wiki/Joint_Tactical_Radio_System#Pr...