Home

Software Development

CCIT leads, manages, develops, delivers, and support high value custom software solutions across multiple domains of knowledge & practice in achievement of its clients' goals. In order to accomplish this so as to achieve CCIT’s goals of highly-available, secure, stable, and cost-effective solutions, CCIT’s software development team maintains a versioned approach to software development.

As many disciplines are involved in the development of its proprietary software solutions, support for these issues is cross-functional and requires the close cooperation of CCIT’s team members. CCIT is committed to providing timely and comprehensive solutions to issues in a manner proportional to business need and potential or actual business impact for applications still within their defined support lifecycle.

With CCIT’s software development process, functionality is released in ordered, packaged deployments known as, well, “releases”. Releases are scheduled based upon resource availability and the time necessary to execute a successful project given the functionality to be delivered within a defined release.

  • Major Releases typically contain code re-writes and new development including sweeping architecture changes, high-value requests for enhancements, and significant user interface changes. Major releases are typically delivered in 6 to 12 month cycles.

  • Minor releases typically contain code optimizations, bug fixes, high-value/low-risk requests for enhancements, and minor user interface changes. There is limited architecture development in minor releases. The changes must be accomplished using the architecture deployed in a former major release. Minor Level Versions are released in 3 to 6 month cycles.

  • Revision releases are provided on an as needed basis and typically contain security fixes, baseline functionality fixes, and critical bug fixes. The critical label refers to defects that result in major loss of baseline function for which there is no workaround. Revision releases can be thought of as patches to existing functionality.

All releases go through testing and quality assurance prior to release.

Software development requests fall within two broad categories:

  • New feature requests are requests for enhancement to or a modification of the existing functionality of an application.

  • Support requests are requests concerning defects of delivered functionality within an application.

New Feature Requests

New feature requests are accepted via CCIT’s web and email request submission interfaces whereupon they are given a severity level of “enhancement” within CCITT’s Bugzilla knowledge management system.

With new feature requests, no service levels exist for acknowledgement, assessment, or incorporation of a new feature request.

Typically, during client consultations regarding functionality to be incorporated into forthcoming releases, CCIT will present all new features or enhancements received. Working with CCIT, the application’s clients would prioritize potential features or enhancements with respect to the application’s lifecycle, business need, and potential value.

If accepted for investigation, CCIT will assess the feature and the scope of work required to incorporate the feature. The assessment of the feature and a recommendation of how best to incorporate the feature amongst an application’s projected release schedule of major and minor releases.

If accepted for incorporation by the client group, it will be assigned to a future release and a schedule for the release will be established.

Support Requests

Support requests concerning delivered functionality are prioritized and assigned on the basis of actual or potential business impact. Our objective is to find a configure change, code change, or workaround that will provide a satisfactory solution. In the case where it is technically impossible to meet these targets, we will work with you to escalate the issue and establish a project plan.

The following chart defines how CCIT prioritizes and responds to software development support requests.

Severity Levels

Critical

Description

This is the highest level of severity and should only be assigned to issues that require immediate attention because they threaten business critical processes, involve major outages, or pose major safety and security issues.

Criteria

A critical issue is one which satisfies any of the following criteria:

  • Undermines business critical processes essential to the mission of the organization.
  • Prevents the effective use of any major service.
  • Seriously affects a substantial number of computer users.
  • Poses a major threat to information security.
  • Might severely impact the reputation of the organization.
  • In the judgment of CCIT staff members, this level of severity is warranted.

Service Level Targets

Within or outside of normal business hours:

  • Acknowledgement: The problem should be acknowledged immediately. Appropriate support personnel should be contacted immediately. CCIT management and senior management of The College should be notified immediately.

  • Assessment: The problem should be assessed within one hour of being reported. All affected parties, CCIT management, and the senior management of The College should be notified of the assessment and the expected time of resolution.

  • Resolution/Mitigation: An initial workaround or means of mitigation should be identified within 24 hours. A solution should be delivered within 7 days.

    All necessary resources will be re-allocated to resolve the issue. This may, in turn, affect CCIT’s ability to meet other defined service level targets. In such cases, reasonable attempts will be made to manage expectations and communicate new expected times of resolution.

Target Release for Solution

  • Minor Release
  • Revision Release

Appropriate Request Submission Interfaces

Web & Phone

Major

Description

Major issues are those that pose a serious impact to business processes if not addressed quickly.

Criteria

A major issue is one which satisfies any of the following criteria:

  • Prevents the effective use of any service and affects a substantial number of computer users.
  • Disrupts the activities of a substantial number of computer users and no work around exists.
  • Poses a minor threat to information security.
  • Might possibly impact the reputation of the organization.
  • Creates very serious implications for an individual user.
  • In the judgment of CCIT staff members, this level of severity is warranted.

Service Level Targets

Within or outside of normal business hours:

  • Acknowledgement: The problem should be acknowledged immediately. Appropriate support personnel should be contacted immediately. CCIT management should be notified immediately.

  • Assessment: The problem should be assessed within two hours of being reported. All affected parties and CCIT management should be notified of the assessment and the anticipated time to resolution.

  • Resolution/Mitigation: An initial workaround or means of mitigation should be identified within 7 days. A solution should be delivered within 14 days.

    All necessary resources will be re-allocated to resolve the issue. This may, in turn, affect CCIT’s ability to meet other defined service level targets. In such cases, reasonable attempts will be made to manage expectations and communicate new expected times of resolution.

Target Release for Solution

  • Minor Release
  • Revision Release

Appropriate Request Submission Interfaces

Web & Phone

Normal

Description

This represents the ‘typical’ problem, and should be the most frequently assigned level of severity.

Criteria

An issue which satisfies any of the following criteria:

  • Prevents the use of any fully supported service or application by an individual.
  • Disrupts the activities of a substantial number of computer users, but a work around exists.
  • Non-critical loss of functionality of the software impairing some operations, but software remains usable.
  • Inconveniences the activities of a substantial number of computer users.
  • Might imply a minor threat to information security.

Service Level Targets

During normal business hours:

  • Acknowledgement: The problem should be acknowledged within four hours.

  • Assessment: The problem should be assessed within one business day of being reported. The effected parties should be notified of the assessment and the expected time of resolution.

  • Resolution/Mitigation: An initial workaround or means of mitigation should be identified within 14 days. A solution should be delivered within the next product release.

Target Release for Solution

  • Major or minor Release
  • Revision Release

Appropriate Request Submission Interfaces

Web & Email

Minor

Description

An issue creating minor business impact as it does not threaten or impact productivity.

Criteria

An issue which satisfies any of the following criteria:

  • Causes inconvenience to an individual
  • Cosmetic Issues
  • Errors in documentation
  • Any problem in a “limited support” category

Service Level Targets

During normal business hours:

  • Acknowledgement: The problem should be acknowledged within one business day.

  • Assessment: The problem should be assessed within one to two business days. The effected parties should be notified of the assessment, and the expected time of resolution.

  • Resolution/Mitigation: An initial workaround or means of mitigation should be identified within 30 days. A solution should be delivered within a forthcoming, but not necessarily the next, product release.

Appropriate Request Submission Interfaces

Web & Email