...
Table of Contents
...
This Pilot CCCApply has created a new, optional non-credit workflow feature in the CCCApply Standard Application. Development requirements for the first version of the new feature were designed under the guidance of the CCCApply Redesign Workgroup, the CCCApply Advisory sub-committee for Non-Credit application;
This Pilot Project Plan will outline the details of the CCCApply Non-Credit Application pilot project across the various stages of remaining pre-production development, testing and implementation.
...
Development requirements for the initial version of this application (v.1.0) were drafted and implemented by the CCCApply Redesign Workgroup and sub-committee for the Non-Credit Application. Details of the v.1.0 development specification can be found here: Non-Credit Change Requirements and CCCApply Non-Credit Application.
...
Pilot Project Overview
CCCApply has developed a new, optional "non-credit" workflow feature in the CCCApply Standard Application. A soft launch release of the first version A soft launch release to a limited number of colleges for a 12-week pilot project deploy to the CCCApply pilot environment is planned in on February 2019, as part of the CCCApply release 6.4.0.
On February 19, 2019, the first version of the new CCCApply Non-Credit Application workflow feature will deploy as a soft launch to a limited number of colleges for a 12-week pilot project under the direction of the Redesign Workgroup, the CCCApply Advisory sub-committee, and CCCApply product The pilot project will be managed under the direction of the CCCApply Redesign Workgroup, the CCCApply Advisory Non-Credit sub-committee, and CCCApply product management. The pilot project will and objectives of this pilot phase includes , will address the following project objectives and timelines:
The Pilot Project includes a soft launch release of the workflow feature to a limited set of colleges - as part of a 12-week Pilot project under the direction of the CCCApply Redesign Workgroup and Advisory Sub-Committee for Non-Credit Application in coordination with CCCApply product development. The overarching goals for the pilot project is to prepare the special feature for a larger scale Beta version release in May 2019, and ultimately to a successful overarching goal for the project is to prepare the new feature for a larger scale Beta version release to more colleges in May 2019, and ultimately to production release to all colleges in June 2019.
The CCCApply Non-Credit Application path is a new, optional workflow feature in the CCCApply Standard Application, designed specifically to support the changes to residency requirements for non-credit students in Assembly Bill 3101.
The first version of the feature will deploy to a limited number of colleges as part of the CCCApply 6.4.0 pilot release on February 19, 2019. B
for a 12-week pilot project under the direction of the Redesign Workgroup, the CCCApply Advisory sub-committee, and CCCApply product management. The pilot project will and objectives of this pilot phase includes , will address the following project objectives and timelines:
The initial set of development requirements were approved by the CCCApply Redesign Workgroup - as part of the CCCApply Redesign Project - and the CCCApply Advisory sub-committee for Non-Credit application.
Project Summary & Objectives
The purpose of the CCCApply Non-Credit App Pilot Project is to ensure that t
The Non-Credit App Pilot Phase includes with a soft launch release to a limited set of colleges as part of an extensive 12-week Pilot project under the direction of the CCCApply Redesign Workgroup and Advisory Sub-Committee for Non-Credit Application in coordination with CCCApply product development. This overarching goal of the pilot project is to prepare the special feature for a larger scale Beta version release in May 2019, and ultimately to a successful production release to all colleges in June 2019.
Proposed goals, timeline, and expected success criteria will inform the agendas for recurring meetings, and a process for providing and escalating feedback is established. Following the completion of a successful project, an additional, scaled "beta project" will be conducted through the CCCTC Enabling Services division, and Support Services.
...
Project Objectives
The objectives for the pilot project are designed to ensure that the new Non-Credit app workflow feature meets the minimum viable feature functionality and implementation requirements to support colleges comply with changes to the state residency requirements for non-credit students.
A set of pilot colleges will work with the CCCApply Redesign Workgroup and sub-committee, as well as the CCCApply product development team, to identify bugs and identify requirements for any remaining (and approved) development enhancements. Bugs and other issues will be prioritized for fix throughout the 12-week pilot timeline.
The following objectives will be addressed in the Non-Credit App pilot project:
...
ensure the initial development design and IT implementation processes meet the success criteria outlined below. A continuous feedback process has been outlined to ensure all bugs and missing critical requirements are identified and prioritized for production release.
Project objectives that will be addressed:
- Approved pilot colleges will commit two staff representatives to participate in the full 12-week project (One admissions office and one IT staff participants) and complete minimum UAT activities
- Participants will should contribute to fulfilling meeting project goals, objectives, and timelines in order to achieve meet proposed success criteria
- Participants will attend scheduled meetings and provide feedback on development and implementation requirements and processes to ensure CCCApply complies compliance with AB 3101
- Participants and Pilot project management will collaborate to ensure the application/feature meets production release phase, successfully document and share college feedback and track progress of overarching goal to meet production phase timeline
Project Timeline
A tentative schedule of project activities are detailed below (subject to change).
...
| Date | Description | Release |
|---|---|---|
| February 19 | CCCApply 6.4.0 release to the CCCApply Pilot environment (see Release 6.4.0 Summary Notes) | CCCApply 6.4.0 Pilot |
| February 19 | Non-Credit Application 1.0 - Soft launch release to the CCCApply Pilot environment | Non-Credit v.1.0 Pilot |
| February 20 - 28 | Non-Credit Pilot begins 12-Week Pilot Activities | |
| March 15 | CCCApply 6.4.0 Production release (see Release 6.4.0 Summary Notes) | CCCApply 6.4.0 Prod |
| April 8 | Non-Credit Application (v.1.x) Pilot Update (Tentative) | Non-Credit v.1.1 Pilot |
| April 15 | Deadline for development changes and bug fixes (Tentative) | |
| May 9 | Code freeze for CCCApply 6.5.0 Pilot Release and Non-Credit App v.1.2 | |
| May 15 - 22 | Non-Credit Pilot officially ends - last meeting | |
| May 31 | CCCApply 6.5.0 Pilot release (includes the Non-Credit Application 1.2 Pilot release) | CCCApply 6.5.0 Pilot |
| June 28 | CCCApply 6.5.0 Production release (includes the Non-Credit Application 1.2 Production release) | CCCApply 6.5.0 Prod |
...
...
Project Goals & Success Criteria
Goals for the CCCApply Non-Credit Pilot Project are listed below with proposed success criteria.
| Goal | Success Criteria |
|---|---|
Ensure MVP product complies with residency-exempt requirements in AB 3101 Ensure the design and development of the Non-Credit workflow path feature & functionality meets minimum viable product requirements for use with non-credit students as mandated in AB 3101 |
|
Ensure product functionality meets MVP requirements for college non-credit programs Ensure the functional design (user interface and admin configurations) meet the minimum viable requirements for the majority of college non-credit programs . |
|
Ensure IT implementation is simple and fully compatible with existing Standard Application implementation Ensure college IT implementation of the new Non-Credit workflow includes minimal risks and requires minimal reporting and admin configuration changes, and compatible data downloads changes to the CCCApply Standard Application IT setup (including pre- and post-application processes and web services) |
|
All required Tech Center applications have Non-Credit application functionality & data Ensure all dependent CCC Tech Center products and services have been updated with the new and revised Non-Credit Application data fields and reports are accessible to authorized college administrators and staff. |
|
Develop (generic) best practices for college support, IT, and admissions implementation of the new Non-Credit feature Identify, test, document and publish best practices for college support of and/or implementation of the Non-Credit workflow feature functionality for (general) college admissions non-credit programs. |
|
...
Pilot College Participation & Requirements
The CCCApply Non-Credit Application Pilot project will initially consist of 6 - 8* district colleges from the CCCApply Redesign Workgroup and the CCCApply Advisory Committee's sub-committee for Non-Credit Application. Pilot project activities are scheduled across a 12-week period between February 19 - June 15, 2019.
...
Participation activities and requirements include:
- Continual participation throughout the Attendance at all meetings
- Complete all UAT Implementation activities and testing goals
- Contribute to design and requirements discussions; provide feedback and support to other pilot colleges
- Contribute to the development of best practices and support materials
...
Pilot UAT Plan & Objectives
The user acceptance testing (UAT) plan process and objectives for the CCCApply Non-Credit Application Pilot project are listed below.
- UAT Objectives & Success Criteria
- Required Documentation
- Getting to the Pilot Application
- IT Implementation Steps
- Data Fields & Downloads
- Admin Configuration
- Reports
- Feedback & Support Processes
...
| Note |
|---|
The Non-Credit Application workflow path feature is an Optional special implementation in the CCCApply Standard Application - All Changes Are Backwards Compatible - No Actions Required: All the front-end changes deployed in the Non-Credit Application path within CCCApply Standard Application (user interface changes, hidden pages and questions, disabling of web services, etc.) should NOT AFFECT YOUR STANDARD APPLICATION. All Non-Credit Application back-end changes are optional and not mandatory for colleges to implement. Admissions, Financial Aid, and IT staff can rest assured there are no action REQUIRED by colleges that do not wish to implement the Non-Credit Application. |
...
Required Documentation
Technical specifications for the Non-Credit Application feature in the Standard Application are included in the CCCApply Standard Application Data Dictionary.
...
| Data Field Name | Type | Data Element | Format / Length | Downloadable | Report Center / Admin Rules | Application |
| Non-Credit Status | New data field | <non_credit> | Yes | Yes | CCCApply Standard & Non-Credit | |
| Integrity Flag 81 | New flag | <integrity_fg_81> | boolean, 1 | Yes | Yes | CCCApply Standard & Non-Credit |
| Note |
|---|
Non-Credit Application - Full Data Set in Glue for Apply The new Non-Credit Application data values will be included in this release, passed directly to colleges using the Glue for Apply feature. |
...
Updating Your Download Files
...
Update the Download Client Jar File
To update your Download Client Transfer file for the Production environment, the process is the same as the Pilot environment update. The same jar file is used for both environment.
In your installed Production Download Client directory, replace the following files:
...