Software [This subsection of the Implementation Management Plan provides a list of non-hardware components (such as software, databases, and compilers, operating systems, and utilities) required to support the implementation. Identify the component by specific name, code, or acronym, identification numbers, version numbers, release numbers, and applicable configuration settings. Identify whether the component is commercial off-the-shelf (COTS), custom developed, or legacy. Identify any component used to facilitate the implementation process. Again, this information is likely to exist in other project documents such as the System Specification Document, the Configuration Management Plan, bill of lading, or contractual documents. If those documents exist and provide the necessary information, you may consider referencing them here instead of duplicating the information to avoid any inconsistencies that may develop. If not, then the following fields should be considered in creating the software inventory: Name/ID Name or identifier of the software component – Type Type of software component (such as browser, RDBMS) – Model/Version Model and/or version number of the software component – Physical Location Physical location where the software component is installed – Software Owner Designated owner of the equipment by organizational entity or name – Maintenance Contract Maintenance contract number (if contract exists) – Maintenance Contact Point Contact point for the maintenance contract (if one exists) – Maintenance Type/ of Coverage Maintenance contract coverage details (if one exists) – Maintenance Period Expiration Date Maintenance contract period (if one exists) – Required Licenses Number and type of licenses required (if applicable)] –
Software [This subsection of the Implementation Management Plan provides a list of non-hardware components (such as software, databases, and compilers, operating systems, and utilities) required to support the implementation. Identify the component by specific name, code, or acronym, identification numbers, version numbers, release numbers, and applicable configuration settings. Identify whether the component is commercial off-the-shelf (COTS), custom developed, or legacy. Identify any component used to facilitate the implementation process. Again, this information is likely to exist in other project documents such as the System Specification Document, the Configuration Management Plan, bill of lading, or contractual documents. If those documents exist and provide the necessary information, you may consider referencing them here instead of duplicating the information to avoid any inconsistencies that may develop. If not, then the following fields should be considered in creating the software inventory: Name/ID – Name or identifier of the software component Type – Type of software component (such as browser, RDBMS) Model/Version – Model and/or version number of the software component Physical Location – Physical location where the software component is installed Software Owner – Designated owner of the equipment by organizational entity or name Maintenance Contract – Maintenance contract number (if contract exists) Maintenance Contact Point – Contact point for the maintenance contract (if one exists) Maintenance Type/ of Coverage – Maintenance contract coverage details (if one exists) Maintenance Period Expiration Date – Maintenance contract period (if one exists) Required Licenses – Number and type of licenses required (if applicable)]
Implementation_Management_Plan_Template_Shell.docx