General discussion

Locked

software upgrade process

By christian.nagler ·
Is there anything on software upgrade process: versioning, testing,
putting into production, responsibilities, etc.
Is there any standard or any material what you feel is important out of your own experience ?

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

software upgrade process

by reeree In reply to software upgrade process

my personal opinion is don't use an upgrade, spend the extra $50(approx) and get the full version.

Collapse -

software upgrade process

by christian.nagler In reply to software upgrade process

Poster rated this answer

Collapse -

software upgrade process

by donq In reply to software upgrade process

Not really! HOWEVER I always load everything into "default" Directories so upgrades run effortlessly.

Collapse -

software upgrade process

by christian.nagler In reply to software upgrade process

Poster rated this answer

Collapse -

software upgrade process

by D. Brinson In reply to software upgrade process

A lot depends on what type of software upgrade you are talking about. After all, upgrading your version of Word on your own PC is alot different then upgrading key software that your company depends upon to operate.

There however a few things that are constant. First: MAKE SURE YOU HAVE A GOOD BACKUP!!! Regardless if there is one user or thousands, being able to go back to the previous version if there are problems is essentional!

If the software you are upgrading is important enough: test everything you can! Now, obviously if you are upgrading Word on your machine, it's probably not worth your time to set up another machine and test the new version prior to putting it in production. However, if you are talking about software that your users depend upon, it is important to test. From experience I will tell you that it doesn't matter that the vendor says the software is great and that other people have being using it for months/years. You still need to test it.

If at all possible (and for larger projects this is not optional) have the users test the new software. Parallel testing is wonderful if software importance warrants it.

If this does not answer your question, you may wish to post a more detailed description ofexactly what type of software upgrade you are talking about.

Collapse -

software upgrade process

by christian.nagler In reply to software upgrade process

Poster rated this answer

Collapse -

software upgrade process

by christian.nagler In reply to software upgrade process

This question was closed by the author

Back to Desktop Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums