Design Document

[Prashanth069]

Hi,

Do you have any template for design document for test stand?

[~jiggawax~]

Are you talking about a document to design your automated test?  Or do you mean a template sequence file?

"Design Document" can mean quite a lot of things to different people.  Can you be more specific?

[Prashanth069]

Hi Jigg,

Design Document means Design specification document or software design specification document

for more information please visit this link http://en.wikipedia.org/wiki/Software_design_document

[RayFarmer]

You do not need any special template. As part of the process you would assess the requirements and choose the Software Language and Software Tools that you would used in the project. These you would detail in your overall SDD.

[Prashanth069]

Hi Ray Farmer,

i agree that SDD contains all information about Software Language and Software Tools  but in that document we need to specify inter dependancy of modules and objects(in teststand interdependency of sequences and work flow of sequences)

how to create diagram in TestStand sense(for eg, UML diagram)?

 for the above requirement do we have any template or example document?

please share if you have any such document, it`ll be helpful for me,

Thanks in advance

Kind Regards,

Prashanth

[RaviShrigiri]

Normally customers come up with test requirement specifications and then proceed to develop the sequence.

In the sequence they ensure good documentation by giving appropriate comments/labels.

Teststand can generate a document from your test sequence  which serves the purpose of design document.

Teststand is not really much different from C when it comes to software design.

TS <---> C

Main sequence --- main()

Sub sequence --- function()

Modules ----- library function

As in C you can call functions directly or in a seperate thread.

Whenever a module is developed ( in any language) then it will have its own SDD and that detail need not be covered at tesstand level SDD.

I would suggest : 

Use any standard SDD template ( you will find plenty if you google it)

A flow chart to depict the flow of sequence.

Embed the documentation created from sequence ( after sequence is fully developed)

This should make a good SDD.

Hope this helps.