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

[Norbert_B]

Btw, this discussion reminds me on a situation some years ago. The customer asked if it is possible to color the user interface in a specific color.

I said to him: "Yes, sure. But you know that there are international standards recommending a grey-scaled user interface for improved user adoption and 'heuristics'?"

He answered: "No, i wasn't aware of that."

As far as i know, the developer left the UI in the default grey color.

Norbert

[natasftw]

If you're deadset on getting an example of Build Specifications and Requirements, you can quickly google for CLA Practice Exams.  The "prompt" for these exams is the document you're looking for.

But, you're better off developing your own and being as clear as possible.  The more clear you are, the easier it is to agree the job is complete later and the less time you'll spend going back and forth trying to make changes based on misunderstanding.

[testswan]

@natasftw wrote:

If you're deadset on getting an example of Build Specifications and Requirements, you can quickly google for CLA Practice Exams.  The "prompt" for these exams is the document you're looking for.

---

WoW just downloaded and had quick look at: [see attached] even as a Labview novice I could probably meet those requirements.  eventually.  Maybe they should make the exams more life like and just say I want an ATM thingy.  See who would pass the exam then lol. 

Does anyone else have other samples of this kind, at the very least documents like this can be used to help us build our own requirements spec docs.

[testswan]

I worked for an NI Alliance partner and discussed this topic with the company's president.  He said the same thing - nobody does that.

---

Was the company president a labview architect/developer?  My money says no.   I like the wash, rinse notion.  Its strange...having worked in in the construction industry for over 10 years everything is designed and built to spec. but I suppose its harder to remove a foundation once the building is up.  You would not invite a contractor into your home and just say build me an extension, and expect them to know what you want as they are the experts...

I suppose it can also depend on whether you are developing a product or a system which will evolve and develop over time...

[natasftw]

I'd wager you're not thinking of the exam in a way that'd facilitate a passing score.

"Eventually" really isn't an option for a four hour test.  You're also confusing the CLD and CLA exam goals.  For the CLD, they give you the Front Panel and tell you to build functionality.  Here, they check your functionality, documentation, and style.  In the CLA, they're going to look at your overall architecture to determine if that would lead towards an acceptable solution.  Actually building this would require more than several hours to do correctly.

There won't be a large list of documents like this.  If there were, they wouldn't be able to use those exams for the actual exam.  It's generally better for them to create another document to create another version of the exam itself.

Ultimately, your goal shouldn't be to replicate these documents.  They're decent examples.  Any others will do just the same.  Instead, focus on articulating your project in agreeable terms that aren't open to interpretation.  The less interpretation possible, the more likely your client and you have the same visual and will agree upon the eventual implementation.

[crossrulz]

The main point is to make sure you have told your customer everything you plan to do.  If they add more, then you state that is an upscope and therefore need more money and/or time.  The format of said document will change from customer to customer.  And when doing your proposals, we find it is a good idea to throw in an allowance of certain changes (like changes to the GUI).

[djs_at_eaton]

I haven't noticed anything in this discussion about safety.  Are you testing something that could be dangerous?  What does the program do if the operator hits the E-stop?  Does it cancel all pending tests so there's no unexpected motion when E-stop is removed?  Does the program prohibit or over-ride unsafe operator commands?  If your customer hasn't thought about those things, you should.  His lawyer will think about them...for certain.

[testswan]

Fair comment, however this was simply a general question.  Safey is a very good point, but going back to the original spec type question, if the client fails to specify I would question who is responsible for it.  If you dont ask you dont get?

[billko]

---

@testswan wrote:

Fair comment, however this was simply a general question.  Safey is a very good point, but going back to the original spec type question, if the client fails to specify I would question who is responsible for it.  If you dont ask you dont get?

---

It doesn't matter who is responsible for a bungled job.  The thing that matters is that they won't come back to you and they will tell others not to go to you.

[billko]

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.