Systems and Methods for Managing Computer Components

1. A computer-based method for managing a plurality of computer components in an organization, the method implemented using a Component Manager (CM) computing device, wherein the CM computing device comprises a processor in communication with a memory device, the method comprising: receiving, by the CM computing device, from a stakeholder computing device, component data for at least one computer component of the plurality of computer components; storing, by the CM computing device, the component data in a memory block in the memory device; assigning, by the CM computing device, a first lifecycle classification, a domain, and at least one stakeholder to the at least one computer component by updating the memory block in the memory device, wherein the first lifecycle classification is one of a plurality of lifestyle classifications, and wherein each lifestyle classification represents a status of the at least one computer component defined by an age of the component, a nature of usage of the component, and an availability of alternative or newer versions of the component; automatically updating the memory block in the memory device by applying a lifecycle model stored within the memory device, the lifecycle model updating the lifestyle classification assigned to the at least one computer component from the first lifecycle classification to a second lifecycle classification of the plurality of lifecycle classifications; causing, by the CM computing device, the stakeholder computing device to electronically display an interactive dashboard that includes a graphical representation of the at least one computer component including the update from the first lifecycle classification to the second lifecycle classification; prompting, by the CM computing device, the at least one stakeholder to further update the memory block for the at least one computer component, by electronically displaying the graphical representation; determining, by the CM computing device, at least one future lifecycle transition date for the at least one computer component, wherein the at least one future lifecycle transition date includes at least a first future lifecycle transition date when the at least one component should be updated from the second lifecycle classification to a third lifecycle classification; and causing, by the CM computing device, a lifecycle report to be displayed, wherein the lifecycle report includes a lifecycle status for the at least one component over a specified future period of time, the lifecycle status including the at least one future lifecycle transition date, wherein the method facilitates one or more of i) centrally controlling the plurality of computer components, ii) coordinating between disparate computer systems to direct updates and fixes, iii) resolving data redundancy issues caused by multiple copies of software being In use, and iv) decreasing risk of security breaches.

2. A method in accordance with claim 1 , wherein receiving component data comprises receiving at least one component attribute for the at least one computer component, and wherein the at least one component attribute includes at least one of a component name, component description, component source, component version, component domain, component category, restrictions on component use, associated licenses, and at least one date at which the at least one computer component is to be assigned the second lifecycle classification.

3. A method in accordance with claim 1 , wherein automatically updating the memory block in the memory device by applying a lifecycle model further comprises applying the lifecycle model to the component data stored in the memory block for the at least one component and assigning the second lifecycle classification to the at least one computer component when a predefined time period is reached, wherein the lifecycle model includes at least one predefined time period associated with a domain and a lifecycle classification such that, when the predefined time period passes for a computer component having said domain and said lifecycle classification, the lifecycle model causes said lifecycle classification for the computer component to be updated.

4. A method in accordance with claim 1 , wherein assigning the first lifecycle classification includes assigning at least one of an emerging lifecycle classification, a supported lifecycle classification, a preferred lifecycle classification, an avoidance lifecycle classification, and a retirement lifecycle classification to the at least one computer component.

5. A method in accordance with claim 1 , further comprising organizing the plurality of computer components by lifecycle classification, including calculating a sum of computer components assigned to each lifecycle classification, and causing a second dashboard to be displayed on the stakeholder computing device including the calculated sum of computer components assigned to each lifecycle classification.

6. A method in accordance with claim 1 , further comprising: determining an operational health indicator for a selected domain by determining a percentage of the plurality of computer components for the selected domain that are assigned to a preferred lifecycle classification and a supported lifecycle classification; and causing the stakeholder computing device to display another interactive dashboard including the operational health indicator for the selected domain.

7. A system for managing a plurality of computer components in an organization, the system comprising: a database configured to store component data; and a component manager (CM) computing device configured to be coupled to the database and comprising a processor, the CM computing device further configured to: receive, from a stakeholder computing device, component data for at least one computer component of the plurality of computer components; store the component data in a memory block in the database; assign a first lifecycle classification, a domain, and at least one stakeholder to the at least one computer component by updating the memory block in the database, wherein the first lifecycle classification is one of a plurality of lifestyle classifications, and wherein each lifestyle classification represents a status of the at least one computer component defined by an age of the component, a nature of usage of the component, and an availability of alternative or newer versions of the component; automatically update the memory block in database by applying a lifecycle model stored within the database, the lifecycle model updating the lifestyle classification assigned to the at least one computer component from the first lifecycle classification to a second lifecycle classification of the plurality of lifecycle classifications; cause the stakeholder computing device to electronically display an interactive dashboard that includes a graphical representation of the at least one computer component including the update from the first lifecycle classification to the second lifecycle classification; prompt the at least one stakeholder to further update the memory block for the at least one computer component, by electronically displaying the graphical representation; determine at least one future lifecycle transition date for the at least one computer component, wherein the at least one future lifecycle transition date includes at least a first future lifecycle transition date when the at least one component should be updated from the second lifecycle classification to a third lifecycle classification; and cause a lifecycle report to be displayed, wherein the lifecycle report includes a lifecycle status for the at least one component over a specified future period of time, the lifecycle status including the at least one future lifecycle transition date, wherein the system facilitates one or more of i) centrally controlling the plurality of computer components, ii) coordinating between disparate computer systems to direct updates and fixes, iii) resolving data redundancy issues caused by multiple copies of software being in use, and iv) decreasing risk of security breaches.

8. A system in accordance with claim 7 , wherein, to receive component data, the CM computing device is further configured to receive at least one component attribute for the at least one computer component.

9. A system in accordance with claim 8 , wherein the at least one component attribute includes at least one of a component name, component description, component source, component version, component domain, component category, restrictions on component use, associated licenses, and at least one date at which the at least one computer component is to be assigned the second lifecycle classification.

10. A system in accordance with claim 7 , wherein, to automatically update the memory block in the database, the CM computing device is further configured to apply a lifecycle model by applying the lifecycle model to the component data stored in the memory block for the at least one component and assign the second lifecycle classification to the at least one computer component when a predefined time period is reached, wherein the lifecycle model includes at least one predefined time period associated with a domain and a lifecycle classification such that, when the predefined time period passes for a computer component having said domain and said lifecycle classification, the lifecycle model causes said lifecycle classification for the computer component to be updated.

11. A system in accordance with claim 7 , wherein, to assign the first lifecycle classification, the CM computing device is further configured to assign at least one of an emerging lifecycle classification, a supported lifecycle classification, a preferred lifecycle classification, an avoidance lifecycle classification, and a retirement lifecycle classification to the at least one computer component.

12. A system in accordance with claim 7 , wherein the CM computing device is further configured to organize the plurality of computer components by component attribute, including calculating a sum of computer components assigned to each lifecycle classification, and to cause a second dashboard to be displayed on the stakeholder computing device including the calculated sum of computer components assigned to each lifecycle classification.

13. A system in accordance with claim 7 , wherein the CM computing device is further configured to: determine an operational health indicator for a selected domain, by determining a percentage of the plurality of computer components for the selected domain that are assigned to a preferred lifecycle classification and a supported lifecycle classification; and cause the stakeholder computing device to display another interactive dashboard including the operational health indicator for the selected domain.

14. A non-transitory computer readable medium that includes computer executable instructions for managing a plurality of computer components in an organization, wherein when executed by a Component Manager (CM) computing device comprising a processor in communication with a memory device, the computer executable instructions cause the CM computing device to: receive, from a stakeholder computing device, component data for at least one computer component of the plurality of computer components; store the component data in the memory device; assign a first lifecycle classification, a domain, and at least one stakeholder to the at least one computer component by updating the memory block in the memory device, wherein the first lifecycle classification is one of a plurality of lifestyle classifications, and wherein each lifestyle classification represents a status of the at least one computer component defined by an age of the component, a nature of usage of the component, and an availability of alternative or newer versions of the component; automatically update the memory block in the memory device by applying a lifecycle model stored within the memory device, the lifecycle model updating the lifestyle classification assigned to the at least one computer component from the first lifecycle classification to a second lifecycle classification of the plurality of lifecycle classification; cause the stakeholder computing device to electronically display an interactive dashboard that includes a graphical representation of the at least one computer component including the update from the first lifecycle classification to the second lifecycle classification; prompt the at least one stakeholder to further update the memory block for the at least one computer component, by electronically displaying the graphical representation; determine at least one future lifecycle transition date for the at least one computer component, wherein the at least one future lifecycle transition date includes at least a first future lifecycle transition date when the at least one component should be undated from the second lifecycle classification to a third lifecycle classification; and cause a lifecycle report to be displayed, wherein the lifecycle report includes a lifecycle status for the at least one component over a specified future period of time, the lifecycle status including the at least one future lifecycle transition date, wherein the non-transitory computer readable medium facilitates one or more of i) centrally controlling the plurality of computer components, ii) coordinating between disparate computer systems to direct updates and fixes, iii) resolving data redundancy issues caused by multiple copies of software being in use, and iv) decreasing risk of security breaches.

15. A non-transitory computer readable medium in accordance with claim 14 , wherein the computer-executable instructions cause the CM computing device to receive at least one component attribute for the at least one computer component.

16. A non-transitory computer readable medium in accordance with claim 15 , wherein the at least one component attribute includes at least one of a component name, component description, component source, component version, component domain, component category, restrictions on component use, associated licenses, and at least one date at which the at least one computer component is to be assigned the second lifecycle classification.

17. A non-transitory computer readable medium in accordance with claim 14 , wherein, to automatically update the memory block in the memory device by applying a lifecycle model, the computer-executable instructions cause the CM computing device to apply the lifecycle model to the component data stored in the memory block for the at least one component and assign the second lifecycle classification to the at least one computer component when a predefined time period is reached, wherein the lifecycle model includes at least one predefined time period associated with a domain and a lifecycle classification such that, when the predefined time period passes for a computer component having said domain and said lifecycle classification, the lifecycle model causes said lifecycle classification for the computer component to be updated.

18. A non-transitory computer readable medium in accordance with claim 14 , wherein the computer-executable instructions cause the CM computing device to organize the plurality of computer components by component attribute, including causing the CM computing device to calculate a sum of computer components assigned to each lifecycle classification, and to cause a second dashboard to be displayed on the stakeholder computing device including the calculated sum of computer components assigned to each lifecycle classification.

19. A non-transitory computer readable medium in accordance with claim 14 , wherein the computer-executable instructions cause the CM computing device to: determine an operational health indicator for a selected domain, further causing the CM computing device to determine a percentage of the plurality of computer components for the selected domain that are assigned to a preferred lifecycle classification and a supported lifecycle classification; and cause the stakeholder computing device to display another interactive dashboard including the operational health indicator for the selected domain.