Definitive Software Library?
Hello all,
I just wanted to know how many of you currently use some kind of software library for all of the applications\packages used in your company. If you do is it homegrown or from a vendor and what features does it have that makes it worthwhile? What features would you like to see in a product as well.
In my environment we currently have several different shares where software is housed. Each department handles it differently. I think it would be good to have a central store that has the installation packages along with documents, number of licenses, product keys, and requires special permissions to check out for usage.
Thanks.
I just wanted to know how many of you currently use some kind of software library for all of the applications\packages used in your company. If you do is it homegrown or from a vendor and what features does it have that makes it worthwhile? What features would you like to see in a product as well.
In my environment we currently have several different shares where software is housed. Each department handles it differently. I think it would be good to have a central store that has the installation packages along with documents, number of licenses, product keys, and requires special permissions to check out for usage.
Thanks.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
Most clients I've worked for simply use a central (nowadays normally DFS'd) share. One used a version-control system (rather than the Wise repository) for the package project files and binaries but that was a software house and they used the same system for their product's source code, so it kind of made sense for them.
Posted by:
dandirk
16 years ago
Ahhhh the holy grail or organization.
We are in the process of creating a Difinitive Software Library. This is heavily covered in many of the IT "process standards" out there like the European ITIL methodology.
Honestly we are for the time being going low tech. An Excel document that records the software name, vendor, owner (dept in company that is ultimately responsible for app, does final testing etc), type of licensing, general cost, dependancies etc
Generally we try and use volume licensing when ever possible (abobe also offers TRL which is volume licensing but bought 1 at a time instead of a blocks of 100s). If we can't avoid this we keep another spreadsheet with serials and which dept purchased them.
Physical copy of the installation source, goes into a locked up safe only accessable to 1 person.
Digital copies of original source files and manual install/config docs are placed on a network share accessable to IT
Digital copies of final packages, custom packaging docs and deployement docs (Zen) are stored in a seperate location.
Digital copies of packaging "in progress" files (irp, ism, mst etc) are located on our packaging server (Server with admin studio that we remote to use... yeah my company is cheap, only 1 copy of admin studio)
We are probably only 25% complete, but we just started to package our apps, everything was manual install before that. We organize as we package which seems like it is working pretty good.
Sometime this year will be going live with a new IT issue tracking system called Touchpaper that supposedly has an built in software library, which we will move our Excel docs into...
We are in the process of creating a Difinitive Software Library. This is heavily covered in many of the IT "process standards" out there like the European ITIL methodology.
Honestly we are for the time being going low tech. An Excel document that records the software name, vendor, owner (dept in company that is ultimately responsible for app, does final testing etc), type of licensing, general cost, dependancies etc
Generally we try and use volume licensing when ever possible (abobe also offers TRL which is volume licensing but bought 1 at a time instead of a blocks of 100s). If we can't avoid this we keep another spreadsheet with serials and which dept purchased them.
Physical copy of the installation source, goes into a locked up safe only accessable to 1 person.
Digital copies of original source files and manual install/config docs are placed on a network share accessable to IT
Digital copies of final packages, custom packaging docs and deployement docs (Zen) are stored in a seperate location.
Digital copies of packaging "in progress" files (irp, ism, mst etc) are located on our packaging server (Server with admin studio that we remote to use... yeah my company is cheap, only 1 copy of admin studio)
We are probably only 25% complete, but we just started to package our apps, everything was manual install before that. We organize as we package which seems like it is working pretty good.
Sometime this year will be going live with a new IT issue tracking system called Touchpaper that supposedly has an built in software library, which we will move our Excel docs into...
Posted by:
geoffsmith31
14 years ago
I developed a software repository and licence management system over a couple of years. I released it under the GPL in Dec 2008. It is designed to allow you to keep all your original media locked away safely while keeping ISO images in a restricted access repository. The application also holds all of the licencing data for the particular software including installation keys, how many licences, which department owns them, which licences are in use (and where the software is installed). The application keeps track of who made installation copies of what software, where the software was installed and when the installation media was destroyed. Its free so could be worth a try if you are looking for something to do this sort of job. I know I couldn't find anything when I was looking - which is why I wrote it in the first place. Installation, source and help files are here on Torrys Delphi Site
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
