Software Development Policy

Development Request Procedure

The Request for Development forms must be used to make any requests for software development.  Software developers should never be contacted directly to perform development tasks.  Requests for changes to existing systems may only be made by the system owner or a party who has been granted specific authority to do so.

This form should be used for any of the following requests:

  • Modification, feature addition, or enhancement to an existing system or web page
  • Creation of a new system
  • Request for a new report or data extraction
  • Request to access an existing report
  • Request Approval Process

Not all requests for development will be approved and delivered.  Submitted requests will follow this procedure:

  • Developer Review: Software Developer Director and necessary development staff analyze the request. Request will be classified into one of the following categories:
    • Non-Development Task
    • Request is routed to the Help Desk or appropriate administrative resource
  • Emergency: System is not performing as expected or is down.  Immediate remediation is performed.
  • Approved: Change will not severely impact business operations.  Task is prioritized and scheduled.
  • Questionable: Change is either questionable or will severely impact business operations or current critical projects.  The request may be escalated for further review to the CIO and/or Executive Staff as necessary.

System Permissions

This list denotes the parties with the authority to request changes to specific systems:


Authorized Requester

Public Web Site

Marketing Director

my.centenary Portal

Portal Governance Committee

Moodle System

Designated Faculty Committee


Request Prioritization

The Software Development Director is responsible for prioritizing requests. Prioritization is based upon:

  • Alignment with existing IT Priority Projects as determined by the IT Priorities Committee
  • Urgency of the request
  •  Impact upon production and requester’s ability to perform his/her job
  •  Availability of resources who are best suited to perform the task
  • Time frame to complete the task

Best effort will be made when possible to prioritize smaller development items, which can be accomplished quickly while continuing to work on long-term projects.

End User Acceptance Testing

Upon successful beta testing by the Software Development Team, the Software Development Director should allow end users access to the development item in a development environment that mimics the production environment as closely as possible. End users should thoroughly test the system and record results of their tests and send them to the Software Development Director upon completion of testing.

The Software Development Director working with the developer or project Team Leader should review the results of end user acceptance tests and note on the software development ticket whether the development item requires changes or may be released into production.

Upon acceptance by the end user the changes will be moved into production.