Calling all LV Architects and Developers: advice required on Build Specifications and Requirements

[testswan]

---

@billko wrote:

I've worked on military, aeronuatical and medical test software before, and they always had explicit, very well-defined requirements statements, so I can't really go along with the "no one does it that way" stetement.  In my experience, you can't play with the big boys without such documents.

---

I'm happy with that,  do you have any examples of such documents maybe if these industries are setting the standards, some examples may allow us to see what we should expect from clients, or at least what we strive to aim for.   Considering that all projects are differant, it would be nice to see some examples of detailed spec documents.  sensitive material and words omitted (naturally).

[billko]

In addition to what Norbert mentioned, you have to "speak the language", also:

http://www.reqexperts.com/blog/2012/10/using-the-correct-terms-shall-will-should/ is a good generalization.

As for formatting, I've mostly just seen mostly paragraph/subparagraph structure.  This has the advantage of making it extremely easy to organize your software.  Generally, each paragraph is a subVI in the main, and each sub-paragraph is either a a subVI or a structure of that.  Documentation is as simple as cut and paste from the requirements documentation.  Using bookamrks makes referencing the documentation easy.