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 2016 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 March 10 and the “go live” production date of March 31, 2016.
Releases & Annual Update Schedule
- 5.1.0 - April 3, 2015 - Release Notes Summary
- 5.2.0 - April 10, 2015 - Release Notes Summary
- 5.2.1 - July 17, 2015 - Release Notes Summary
- 5.3.0 - December 4, 2015 - Release Notes Summary
- 2016-2017 BOG Fee Waiver Application - Release Notes Summary
- 5.4.0 - Annual Update - March 31, 2016 - Release Notes Summary
- Annual Development & Release Cycle
- 2017 Annual Update
CCCApply Standard Application and OpenCCC Account
- CCCApply Steering Committee
- Change Management Process
- 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
CCC Administrator & CCC Report Center
- Approved Change Requests
- Changes to the CCCApply Administrator Settings
- Changes to the Report Center
- Documentation Updates:
Board of Governors (BOG) Fee Waiver Application
- 2016-2017 BOG Fee Waiver Application CCCCO Final
- Approved Change Requests
- Changes to BOG Application Data Download File
- Bug Fixes & Technical Updates
- Deferred & Declined Requests
International Application
- CCCApply International Application v.2016.1 - Release Notes Summary
- Accessibility & Security Specifications
- Documentation:
- CCCApply International Application Data Dictionary/Specification v.2016.1
- CCCApply International Application Data Download File
- CCCApply Administrator User Guide
Pilot (Beta) Environment
- New Pilot Site Released July 25, 2015
- Applications & Downloads Server
- Pilot Administrator
- Pilot Report Center
- Terms of Use
Releases & Annual Update Schedule
Annual Development & Release Cycle
The annual development 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 Standard Application & OpenCCC Student Account
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 (rewrite this and add one more sentence. add a link to the new Steering Committee page on the Project Site.)
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.