Scripting template
I'm looking for some sort of template for our software scripting team.
Anyone got something I can use?
I want a "template" that everyone use to fill in information about "name of application", "owner", "users", "license key", "how it was installed" and so on.
What do you people use to document your packages?
Anyone got something I can use?
I want a "template" that everyone use to fill in information about "name of application", "owner", "users", "license key", "how it was installed" and so on.
What do you people use to document your packages?
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
AngelD
15 years ago
A combination of these three would give you a good start:
http://www.symantec.com/community/download/6437/packagingqc-process-generic-template
http://www.symantec.com/community/download/6438/application-package-test-plan-generic-template
http://www.symantec.com/community/download/6439/technical-reviewassessmentevaluation-generic-template
http://www.symantec.com/community/download/6437/packagingqc-process-generic-template
http://www.symantec.com/community/download/6438/application-package-test-plan-generic-template
http://www.symantec.com/community/download/6439/technical-reviewassessmentevaluation-generic-template
Posted by:
Guybrush
15 years ago
Sorry if I'm unclear (english isn't my native language)
My goal is to use sharepoint/wiki for all the info, but what I was looking for a well thought-through template with all the fields I needed to fill in.
(So that I don't find out in a month or so that I forgot some fields/entries)
My goal is to use sharepoint/wiki for all the info, but what I was looking for a well thought-through template with all the fields I needed to fill in.
(So that I don't find out in a month or so that I forgot some fields/entries)
Posted by:
anonymous_9363
15 years ago
So that I don't find out in a month or so that I forgot some fields/entriesBuild a drag-and-drop-enabled script which uses Word's Automation to check the document as part of your QA process. That will mean building bookmarks into your template(s) but that's no big deal. If your information is laid out in tables (I haven't looked at the samples) you can then check for empty cells. Your script can identify those entries which are mandatory and flag blanks appropriately.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.