COMMONWEALTH OF PENNSYLVANIA

DEPARTMENT OF HUMAN SERVICES

INFORMATION TECHNOLOGY GUIDELINE

Name Of Guideline: / Number:
Software Requirements Checklist / GDL-EPPM015
Domain: / Category:
Business / Work plan Standard / Project Checklists
Date Issued: / Issued By:
12/17/2008 / DHS Bureau of Information Systems
Date Reviewed:
03/10/2016

General:

This checklist provides a list of the considerations for software to be used on a new application. This checklist can be used for tracking that the appropriate requirements have been considered.

The purpose of this document is to track the appropriate Software Requirements.

Guideline:

Software Requirements

Perform these steps and indicate who assessed the requirement and the date of its completion.

Requirements / PERSON / DATE Addressed
GENERAL
Define desktop operating system and its level
Define desktop application software and their respective levels
Define software configuration requirements
Determine required file and folder permissions
Determine whether Database accounts are needed for individuals or the application
Determine if new application software needs to be installed
Determine if software documentation is available
Determine installation procedures
Determine uninstall procedures
User manual available?
Define testing and verification procedures
Certification for new application software for the selected operating system
Identify conflicts with other software applications
Determine software deployment method - group policies? SMS package? Ghost Images?
Determine who will support software once installed
Training for DHS staff?
Ongoing maintenance requirements
Network access requirements
Compliance with CTC’s mandates
Cross-project impact or relationships
Network
Determine if new application software needs to be installed
Determine if need shrink-wrapped off-the-shelf software and whether a server-specific version runs as a service
Determine whether package is intended for ES7000 and has been certified for DataCenter
Determine whether other software (databases, reporting utilities, etc.) and/or services (middleware clients, data access components, etc.) needs to be present
Identify whether involved turnkey software ported from another source and whether modifications made to address DHS specific business needs and/or hardware environment
Obtain licensing requirements if product is off-the-shelf or turnkey
When custom-developed software, determine whether services such as MDAC need to be loaded or enabled, or specific tuning parameters need to be set

Refresh Schedule:

All guidelines and referenced documentation identified in this standard will be subject to review and possible revision annually or upon request by the DHS Information Technology Standards Team.

Guideline Revision Log:

Change Date / Version / Change Description / Author and Organization
12/17/2002 / 1.0 / Initial creation. / Momentum
04/04/2003 / 1.0 / Comply with DPW Technical Standards / DCSS – Process Section
02/14/2005 / 1.0 / Reviewed content – No changes / DCSS – Process Section
01/05/2007 / 1.0 / Reviewed content – No changes / PMO-DCSS
08/11/2008 / 1.1 / Reviewed and edited style / PMO - DCSS
12/21/2010 / 1.2 / Reviewed content – No changes / PMO - DCSS
04/28/2015 / 1.3 / Changed DPW to DHS / BIS/DEPPM
03/10/2016 / 1.3 / Annual Review / BIS/DEPPM

Software Requirements Checklist.docPage 1 of 3