2 ms·
GP talked about this occurring at a defense contractor. The specifications tend(ed) to be much tighter. System X will receive input from this data bus. It will
by Jtsummers 10y ago
GP talked about this occurring at a defense contractor. The specifications tend(ed) to be much tighter. System X will receive input from this data bus. It will use this wire protocol. It will use that address to push output to <other component>. Messages will be of the following forms.
It's often a lot of embedded systems, and the good thing about these is that this level of specification is quite feasible. I've written a "simulator" (not full-blown, it was a stop-gap measure) for a piece of code we're supposed to get from another contractor. My code pretty much started off this way (but LP isn't liked here and it got butchered, started off in org-mode). I had to receive certain messages reading from shared memory (old architecture, can't change it without changing everything else), and respond back with messages stored in other address ranges. So I described the messages, I described the addresses, including references to specifications. My code was, essentially, traceable back to the requirements and specifications documents.
In this world we often have an SDD, usually not well developed and unfortunately sometimes made after the fact. Literate programming is a way that you can pair up the design and the code into one place, along with a rationale for the code by way of tying it back to the requirements documents.