Packaging Forms/Documentation Templates
I'm not sure if this would be the correct forum for this, so mods feel free to move where you deem appropriate...
I'm currently trying to develop some documents/forms for my company and I'm curious if anyone would like to offer up any document templates that they have been using or even just any ideas of things to include.
One of the documents I'm working on is a Software Package request form, which would be for anyone requesting an application to be packaged, I'll be including things like App name, version, installation instructions, etc.
Another document I'm working on is a template for documenting the package creation and any modifications, etc. This will be used as a reference document. For example, when an upgrade is needed to be packaged we can go back to these notes to see how we packaged the original install, what custom actions were created, etc. etc.
And the last is a standards document, that just lists best practices, etc. for packaging/repackaging applications. This will be some basic guidelines to have so that our team is all on the same page with the do's and dont's of packaging.
I know a lot of things are environment specific and I'm not looking for anything like that, just more of a basic template starting point and maybe a few ideas of other things to consider. If anyone would like to offer up any examples/templates/etc. I'd really appreciate it and I think this is something that we can all benefit from to get an idea of how people are doing things in their respective environments.
Thanks!
I'm currently trying to develop some documents/forms for my company and I'm curious if anyone would like to offer up any document templates that they have been using or even just any ideas of things to include.
One of the documents I'm working on is a Software Package request form, which would be for anyone requesting an application to be packaged, I'll be including things like App name, version, installation instructions, etc.
Another document I'm working on is a template for documenting the package creation and any modifications, etc. This will be used as a reference document. For example, when an upgrade is needed to be packaged we can go back to these notes to see how we packaged the original install, what custom actions were created, etc. etc.
And the last is a standards document, that just lists best practices, etc. for packaging/repackaging applications. This will be some basic guidelines to have so that our team is all on the same page with the do's and dont's of packaging.
I know a lot of things are environment specific and I'm not looking for anything like that, just more of a basic template starting point and maybe a few ideas of other things to consider. If anyone would like to offer up any examples/templates/etc. I'd really appreciate it and I think this is something that we can all benefit from to get an idea of how people are doing things in their respective environments.
Thanks!
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
No responses...tut, tut...
Using paper-based forms is an invitation for chaos. How would you (or, more importantly, the requestor) track progress, for example? Packaging requests would best be dealt with via a database-driven website, in my view. That view may well be coloured by the fact that I've built a couple, however. [:D] Don't be put off: this stuff isn't as hard as you think. I may be persuaded to part with some source code: PM me for details.
Package documentation - most clients I've worked for use a ReadMe which lives alongside the MSI and is generally the first point of call for Support people (when they've been advised that calling/emailing the packager direct will simply result in the response "It's all in the ReadMe..."). I can send you one if you like.
Standards - IIRC, this site has a standards/best practise page. If not, as ever, a Google search will turn something up. However, as a start point, try this InstallShield eBook
Using paper-based forms is an invitation for chaos. How would you (or, more importantly, the requestor) track progress, for example? Packaging requests would best be dealt with via a database-driven website, in my view. That view may well be coloured by the fact that I've built a couple, however. [:D] Don't be put off: this stuff isn't as hard as you think. I may be persuaded to part with some source code: PM me for details.
Package documentation - most clients I've worked for use a ReadMe which lives alongside the MSI and is generally the first point of call for Support people (when they've been advised that calling/emailing the packager direct will simply result in the response "It's all in the ReadMe..."). I can send you one if you like.
Standards - IIRC, this site has a standards/best practise page. If not, as ever, a Google search will turn something up. However, as a start point, try this InstallShield eBook
Posted by:
ztruelove
15 years ago
I hate to bump such an old thread, but I was searching the forums for pretty much exactly the same information as dallasr. My company has just recently started making any attempt at all to repackage software (moving from a 95% manual installation environment), and the floodgates are being opened with people requesting that their apps be (re)packaged. I really need to get the request process under control with some "best practices."
VBScab, the ebook you reference in your post doesn't seem to be available at that link any longer. I've tried tracking it down elsewhere but have been unsuccessful as of yet. I also tried to PM you, but it seems that is being blocked.
Any advice/direction is appreciated.
VBScab, the ebook you reference in your post doesn't seem to be available at that link any longer. I've tried tracking it down elsewhere but have been unsuccessful as of yet. I also tried to PM you, but it seems that is being blocked.
Any advice/direction is appreciated.
Posted by:
anonymous_9363
15 years ago
The eBook link still works OK for me, both here at my client and at home.I recall looking out for sample code after responding last time and found any number of Helpdesk/workflow apps available, a good number for free. Try SourceForge http://www.sourceforge.net and Planet Source Code http://www.pscode.com for starters: you'll find some really excellent code there (and some dross, it has to be said...)
Posted by:
ztruelove
15 years ago
It's not that the link doesn't work, but when I go there and then click on the "View as a PDF File" or "View as a LIT File" links, they just take me to http://www.acresso.com/. I've done some searching on the site, but I haven't found the ebook yet. Maybe it's right in front of my face, and I'm just missing it.
Posted by:
anonymous_9363
15 years ago
LOL...sorry, I ought to have followed those links.
Anyway, a few minutes with Google got me to Bob's (Bob Kelly, AD's moderator) site. The link to the same publication here is also dead but, going on level up from the dead link, http://nexus.realtimepublishers.com/, allowed me to browse to here http://nexus.realtimepublishers.com/allpubs.htm#Desktop_Management_and_Software_Deployment, some of which must be useful.
Anyway, a few minutes with Google got me to Bob's (Bob Kelly, AD's moderator) site. The link to the same publication here is also dead but, going on level up from the dead link, http://nexus.realtimepublishers.com/, allowed me to browse to here http://nexus.realtimepublishers.com/allpubs.htm#Desktop_Management_and_Software_Deployment, some of which must be useful.
Posted by:
ztruelove
15 years ago
I emailed the publisher and was able to get them to send me a copy. Thanks for the assist!
Posted by:
jmcfadyen
15 years ago
there is an msi tool called Unity which has a bunch of template doco in it as well
Posted by:
anonymous_9363
15 years ago
...and the very *best* of luck trying to find it, now that it has disappeared into the labyrinth which is IBM's web site.
Posted by:
B_L_A_D_E
14 years ago
So does anyone have sample Software Package requests form templates? Yes I understand a web-based form would be great, but my organization is not at that point yet. Forms needed please.
Posted by:
turbokitty
14 years ago
I've authored my own forms and I've put a lot of work into them over the years. It's part of the value I bring when consulting to an organization, for this reason, I don't give them away for free.
If you'd like copies and are willing to pay, I can provide more details if you PM me.
If you'd like copies and are willing to pay, I can provide more details if you PM me.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.