(no subject)
So, we recently got some new-ish software that I use in my testing of radar threat databases. It is quite nifty. It got me to thinking that based on this software I could automate most of the test data collection. Well, I would not code it, but I could see a lot of ways to use the current software as a base to improve on it. It is perfect for it. I happened to mention all my ideas to some of the System Leads....this fits in with their grand vision of "how things should be". They are pleased. I somehow ended up being tasked to write the Software Specification for this new and improved software. I naively thought this would be a fairly straight forward outline type document that explained each feature we wanted. Come to find out...there is an "official" way to write this thing involving lots of "shall" statements and all those have to be numbered. Thankfully all the parts I wrote were almost in that format already but this turns out to be very tedious. I am so very excited about the project though so I am muddling through it. I suppose this is one way to learn how to format such documents.
Yay for huge and intricate docments! More like YAY for finding a way to prevent morons from taking down incorrect test data!
Yay for huge and intricate docments! More like YAY for finding a way to prevent morons from taking down incorrect test data!