Hi,
I've done some work around classes,status etc on Configuration Items for my CMDB. It's all pretty straight forward with the Hardware statuses (Stock, Production decommissioned etc) but i'm struggling on the software side of things.
I've kept the Class at a high level - Software, and Type examples include Patch, Application and Component. I'm struggling with the status lifecycle though for Software. I'm thinking along the lines of Install pending, installed, license expiring, expired but not sure.
Anyone have any thoughts or suggestions?
All feedback greatly apperciated.
Regards,
GOC
Software ages just as hardware does. Does it still meet requirements? Is it still supported by the vendor? After all, requirements are a moving target over time as the business environment evolves.
First (if you're not already doing so) track Software CIs at the Release/Version level because you may have many versions deployed or moving through your environment, at any given time.
Second, you may want to consider basing your Software states on SDLC phases to track your CIs. You can find the SDLC phases listed in the "IT Learning Framework".
So, for example, you'd have states that read like...
In Strategy Development
In Research
In Planning
In Requirements Collection
In Design & Engineering
In Procurement & Coding
In Common/Centralized Build/Packaging
In Systems Integration Testing (SIT)
In User Acceptance Testing (UAT)
In Training and Education (TRAIN/EDU)
In Production (PROD) but not in Disaster Recovery (DR)
In Production (PROD) and Disaster Recovery (DR)
Closed/Terminated
Doing so maps to common phases of work and existence for most software AND it maps to what many mature PMO organizations track, when it comes to work performed on Software.
Reply With Quote
Bookmarks