09-20-2024 04:30 AM
Sorry this is a lame question. I have googled it a lot, but I don't know if I'm taking things I've seen too literally and it just leaves me a bit stunned how long this doc is going to be for a pretty standard program.
What would you go with
Or
The second is easier to pass/fail individual requirements. But there’s a bunch more things that all of them should do, eg all lines get logged to file, all lines get displayed, all lines have an alarm level, and soon I’m going to have 20 requirements instead of 5 for this tiny part, and for the whole program probably 400 requirements rather than 100.
I'm trying to make my requirements docs more professional, but I don’t work in a software oriented company so I’d probably have to defend coming out with something so extremely granular... which I could stand by if I could stop doubting which one I ‘should’ do…
I don’t use teststand, maybe if I did I’d be able to see this as what’s most appropriate to plug into there.
09-20-2024 04:39 AM
Apologies that this isn't a question about the code itself so maybe belongs on another forum, this just feels like the home forum
09-20-2024 05:44 AM
I'm working with a Systems Engineer for the first time in my life. My team has never done requirements beyond "The system shall perform the acceptance test per document XYZ." Now we have a very comprehensive set of requirements in Jama. I hate Jama.
09-20-2024 06:07 AM
Version 1 is hard to misinterpret and a lot less to write, so i'd go with that.