This annual report provides an overview of the requirements and specifications for all Approved Change Requests and program enhancements that have been approved by the CCCApply Steering Committee for the 2015 Annual Update. It also details the requests that have been deferred or declined, as well as the specific systems where each change will be implemented. Changes will appear on the Pilot (beta) environment servers between .
Releases & Annual Update Schedule
- 5.5.0 Release
- 5.5.1 Release
- 5.5.2 Release
- 6.0.0 Release (March 31, 2017)
- Technical Updates:
- Shibboleth Upgrade to v3.1
Development & IT Roadmap
- RFP for New / Upgraded CCC Web Applications
(CCC Software Development- OpenCCC Upgrade - MyPath Integration
- Report Center Upgrade to TIBCO/JasperSoft Subscription version
- Launching New Administrator 2.0 (Multi-App Super Administrator)
- Integration with Project Glue, Assess, MyPath, Course Exchange
- MyPath Iintegration
- Maintain Legacy Systems through 2018
- OpenCCC Legacy
- CCCApply Legacy (New CCCApply/IA/BOG integration
- Administrator Legacy (CCC Administrator 2.0 under-development)
- Download Client Legacy (Universal College Adaptor under-development)
- New DevOps Vendor - Infiniti
- New Server Hosting Service - Amazon Web Services
- CCCApply servers move to Amazon (AWS) Feb 2017
- Continuous Deployment Model for 2017-2018
- Maintain Annual Update Release for Downloads & Logic change
- CCC Report Center moves to Amazon (AWS) - Upgrade to TIBCO/JasperSoft Subscription Instructure
- CCCApply servers move to Amazon (AWS) Feb 2017
- RFP for New / Upgraded CCC Web Applications
CCCApply Standard Application and OpenCCC Account
- Approved Change Requests
- Changes to Standard Application Data Download File
- Changes to Standard Application Residency Logic
- Accessibility & Security Enhancements
- Bug Fixes & Technical Updates
- Deferred & Declined Requests
- Approved Change Requests
CCC Administrator & CCC Report Center
- Approved Change Requests
- Changes to the Administrator Settings
- Changes to the Report Center
- Documentation Updates:
- CCCApply Administrator User Guide
- CCC Report Center User Guide
Board of Governors (BOG) Fee Waiver Application
- 2016-2017 Approved CCCCO Changes
- Approved Change Requests
- Changes to BOG Application Data Download File
- Changes to BOG Application Residency Logic
- Accessibility & Security Enhancements
- CCCApply.org Changes
- 2016-20: Update Money & BOG Pages on CCCApply.org
- Bug Fixes & Technical Updates
- Deferred & Declined Requests
International Application
- New Application Version Release Notes
- New International Application Data Download File
- New Requirements
- Accessibility & Security Enhancements
- Bug Fixes & Technical Updates
CCC SSO Proxy Integration
- CCCApply integration with Proxy
- Administrator / Jasper integration with Proxy
- Proxy UI/UX Upgrade
Pilot (Beta) Environment
- Applications & Downloads Server
- Pilot Administrator
- Pilot Report Center
- Terms of Use
All OpenCCC & CCCApply Projects - 2017-2018
Development & Release Roadmap
Communication Schedule
Implementation Plan
Support & Training
Research & Marketing Projects
Documentation
Steering & Advisory Committees
Events & Conferences
CCCApply Standard Application & OpenCCC Student Account
Releases & Annual Update Schedule
The annual change management and release cycle typically begins in April for the following year's annual update release.
| Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | Jan | Feb | Mar | |||||||||||||
Accept and evaluate requests |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Draft specifications |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Finalize specifications |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Program changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Develop test plan |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Develop messaging to users |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
TEST changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Program corrections |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
| Implement changes on Pilot Site | |||||||||||||||||||||||||
Implement messaging to users |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Validate and sign-off changes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Go LIVE on Production |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Plan next year’s enhancements |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| — | — | — | —> | |
CCCApply Steering Committee
The CCCApply Steering Committee is comprised of XX California Community College administrators and staff from Admissions & Records, Enrollment Services, Financial Aid, Institutional Research, IT, Student Services, and other Departments. Members are selected from colleges across the state, including northern, southern, Bay Area, eastern colleges, as well as large and small college (Update this for 2017).
Change Management Process
The product manager and support services collect and evaluate change requests for colleges and present them to the CCCApply Steering Committee at their bi-monthly meetings. The Committee will evaluate each request and approve, defer or decline the request based on need and how it affects the application for all colleges. Requests must meet the needs of all or the majority of colleges to be approved, such as state legislative mandates, state residency regulations, and CCCCO MIS reporting requirements. Change requests should be submitted to the Product Manager through the CCC College Support Site, www.ccctechnology.info and should a needs and benefits statement and supporting documentation.