CMDB - Status options for Software CI's
Results 1 to 5 of 5

Thread: CMDB - Status options for Software CI's

  1. #1
    Join Date
    Feb 2012
    Posts
    2

    CMDB - Status options for Software CI's

    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

  2. #2
    Join Date
    Jun 2006
    Location
    Florida
    Posts
    327
    Don't omit items such as function and support.

  3. #3
    Join Date
    Feb 2012
    Posts
    2
    Hi ua549,

    I was going to use these as attributes of the software. Any suggestions on examples of Status for Software in its life cycle?

    For example, the hardware lifecycle could be Stock, Production, Repair, Disposed, Charity etc.

    I'm struggling with Software options though. Any examples or suggestions i could use for an Application, Patch or Component??

    I'd greatly appreciate help on this one...

    Thanks,

    GOC

  4. #4
    Join Date
    Jun 2006
    Location
    Florida
    Posts
    327
    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.

  5. #5
    Join Date
    Dec 2006
    Posts
    58

    Using SDLC to Track Software States/Status

    Hi GOC,

    I would recommend you consider two things...

    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.

    I hope this helps.

    My Best,

    Frank Guerino
    Chairman
    The International Foundation for Information Technology (IF4IT)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •