5 ms·
F-35 looks like it's the most ambitious software project ever attempted. - Lots of system integration for the final product from multiple suppliers (usually ni
by nabla9 11y ago
F-35 looks like it's the most ambitious software project ever attempted.
- Lots of system integration for the final product from multiple suppliers (usually nightmare).
- Autonomic Logistics Information System (ALIS) is critical for the maintainability and it's millions of lines of code. Failure rate of large projects like this is typically 40-60% and ALIS looks like it's more advanced than most bean counting systems ever delivered.
- Underlying hardware is slowly changing underneath because the system is late.
- It has frigging augmented reality system with helmets that integrates everything together.
- It's safety critical code.
> no less than 27 power cycles were required to get all systems functioning between initial startup and takeoff. These power cycles
varied in degree – from “cold iron” resets, where the aircraft had to be shut down and then restarted, to component or battery power recycling.
Holy shit!
- wrong_variable 11y agoThis is what so many non-software people trying to make decisions on software fail to realize - every constraint added increases the complexity of software by an order of magnitude.
- awinter-py 11y agowell, a binary order of magnitude maybe
- russell 11y agoIndeed. There was a paper done in the 70s or 80s that found that operating system size doubled with each new feature. Picture going from single tasking to multitasking or to virtual memory. Sorry, I cant dredge up the reference.
- sbov 11y agoI run into this at work all the time. Me: FYI, in scenario xyz, I updated the documentation to do abc. It seems like the best balance of complication and doing the right thing, especially considering it will almost never come up. Boss: why does it even matter what it does? It will come up maybe once per year. Oh, and it should do <this other really specific and complicated thing> instead, so do that. Me: sigh....
- beamatronic 11y agoMaybe you can explain it to them this way - if they know what a function is. If you have a function that does something, foo, and it takes one boolean parameter, that's two test cases. If you add a second boolean parameter, now you have at least four total test cases. And so on.
- wmeredith 11y agoAh yes, give it to them in functions and boolean parameters, that will get the non-programmers on board. /s
- oconnore 11y agoMy house has a vacuum, a lawnmower, a blender, a washing machine, 20 light switches, a 4 zone heating system, and 6 sinks/showers. I can manage 1.71e10 possible states while I sleep, why are you struggling with four?
- Shivetya 11y agoone last hurrah at attempting to keeping human pilots relevant
- brohee 11y ago>> no less than 27 power cycles were required to get all systems functioning between initial startup and takeoff. These power cycles varied in degree – from “cold iron” resets, where the aircraft had to be shut down and then restarted, to component or battery power recycling. > Holy shit! Even more extraordinary that they found someone willing to takeoff after that...
- engi_nerd 11y agoThose are 27 power cycles spread across all the different flights described in that section of the document, not 27 power cycles for one single flight.
- erichurkman 11y agoHave you tried turning it off and back on again? Have you tried turning it off and back on again? Have you tried turning it off and back on again?
- happyslobro 11y agoCtrl+Alt+Delete "Abort, retry or fail?"
- dsfuoi 11y agoChoose carefully, one of those deploys the ejection seat.
- happyslobro 11y agoCtrl+Alt+Delete "Abort, retry or fail?"