...
Table of Contents
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.
...
Note |
---|
For detailed information on the approved change request and tech specifications, see |
PILOT PROJECT OVERVIEW
Overview of the CCCApply Non-Credit Application pilot project phases:
- College Pilot Project
- Project Overview & Timeline
- Project needs
- Status of development
- Project Timeline
- Goals & Expected Outcomes / Success Criteria
- Feedback Process
- College Participation & Requirements
- Project Overview & Timeline
- Production Release
- Beta Version Plan
- Implementation Plan
Overview & Timeline
The first version of the Non-Credit Application development (v.1.0) will be released to the CCCApply pilot environment in February 2019 for the purpose of commencing a 12-week college pilot project under the direction of the CCCApply Redesign Workgroup and Advisory Sub-Committee for Non-Credit Application. A group of 6 - 8 colleges from these oversight committees will be invited to participate in the project. 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.
Pilot Needs
The purpose of this Pilot Project is to ensure that the development and implementation of the CCCApply Non-Credit Application meets the requirements of Assembly Bill 3101, and that CCC colleges are included in all further testing and implementation requirements, as well as any additional development needed to meet the minimum viable product requirements for use with students and non-credit programs prior to production release.
Development Status (v.1.0)
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 Timeline
The Pilot phase will begin shortly after v.1.0 is released to the CCCApply pilot environment on February 19, 2019. Approved 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.
A development and release schedule is below (subject to change):
...
Goals & Success Criteria
...
Using Standard Application Download Client & XML files
Using SuperGlue staging process
Using SuperGlue SIS import process
...
The objectives for college user testing are:
- Ensure colleges are able to download the legacy race group, hispanic, and race ethnicity fields data in the original (unchanged) format by doing nothing to their downloads
- Ensure colleges can continue to get the legacy data required for MIS reporting;
- Ensure colleges are able to get the legacy data AND successfully download the new data <race_ethnic_full>, when they add the new field to their Format XML file and update the jar file
...
Feedback & Support Process
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.
Participating Colleges
Colleges from within the CCCApply Redesign Workgroup and the CCCApply Advisory Committee that will be participating in the project:
- City College of San Francisco
- Coastline College
- North Orange CCD
- Santa Rosa College
- Sierra College
- Cerritos College
Participation Requirements
Production Release
UAT SUCCESS CRITERIA
For the new Race & Ethnicity Implementation 2018, the goals for pre-release user testing are:
...
- hispanic
- race_group
- race_ethnic (CCCApply Standard)
- race_ethnicity (International)
...
- race_ethnic_full
...
Table of Contents
...
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.
Product information is available here: CCCApply Non-Credit Application
Note |
---|
For detailed information on the approved change request and tech specifications, see |
...
PILOT PROJECT OVERVIEW
Overview of the CCCApply Non-Credit Application pilot project phases:
- College Pilot Project
- Project Overview & Timeline
- Project needs
- Status of development
- Project Timeline
- Goals & Expected Outcomes / Success Criteria
- Feedback Process
- College Participation & Requirements
- Pilot UAT Objectives
- Project Overview & Timeline
- Production Release
- Beta Version Plan
- Implementation Plan
...
Overview & Timeline
The first version of the Non-Credit Application development (v.1.0) will be released to the CCCApply pilot environment in February 2019 for the purpose of commencing a 12-week college pilot project under the direction of the CCCApply Redesign Workgroup and Advisory Sub-Committee for Non-Credit Application. A group of 6 - 8 colleges from these oversight committees will be invited to participate in the project. 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.
Pilot Needs
The purpose of this Pilot Project is to ensure that the development and implementation of the CCCApply Non-Credit Application meets the requirements of Assembly Bill 3101, and that CCC colleges are included in all further testing and implementation requirements, as well as any additional development needed to meet the minimum viable product requirements for use with students and non-credit programs prior to production release.
Development Status (v.1.0)
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 Timeline
The Pilot phase will begin shortly after v.1.0 is released to the CCCApply pilot environment on February 19, 2019. Approved 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.
A development and release schedule is 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 | Non-Credit Pilot Project commences | |
February 20 - 28 | First recurring Non-Credit Pilot Project meeting is held | |
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 | |
May 1 | Code freeze for CCCApply 6.5.0 Pilot Release and Non-Credit App v.1.2 | |
May 15 | CCCApply 6.5.0 Pilot release Non-Credit Application 1.2 Pilot release | CCCApply 6.5.0 Pilot Non-Credit v.1.2 Pilot |
June 15 | CCCApply 6.5.0 Production release Non-Credit Application 1.2 Production release | CCCApply 6.5.0 Prod Non-Credit v.1.2 Prod |
...
Project Goals & Success Criteria
Goal | Success Criteria |
---|---|
Ensure Pilot v.1.0 meets minimum viable product requirements | |
Ensure Pilot v.1.0 data field changes meet existing download and import process requirements | Using Standard Application Download Client & XML files Using SuperGlue staging process Using SuperGlue SIS import process |
Identify and document production version implementation requirements & processes | |
Gather requirements and implement ability to configure separate "majors / programs of study" and/or "major categories" | The objectives for college user testing are:
|
Gather requirements and implement ability to configure separate supplemental questions |
...
Feedback & Support Process
...
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.
Participating Colleges
Colleges from within the CCCApply Redesign Workgroup and the CCCApply Advisory Committee that will be participating in the project:
- City College of San Francisco
- Coastline College
- North Orange CCD
- Santa Rosa College
- Sierra College
- Cerritos College
Participation Requirements
...
Pilot UAT Objectives
For the Non-Credit Application Pilot project, the goals for college user and IT implementation testing are:
- Pilot colleges are able to add the new data fields to their existing Standard Application Format Definition XML file,
- Update the transfer-client.jar file (v.6.4.0), and successfully download the new fields from the Standard App Download Server
- non_credit
- integrity_fg_81
- Colleges are able to identify the specified changes to existing data fields and formats as specified in the CCCApply Standard Application Data Dictionary v.2019.1 (6.4.0)
- Colleges maintain compliance with MIS data requirements for all existing residency determination fields and logic in place prior to the Non-Credit application release
Note |
---|
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 upgrades, race/ethnicity layout) and all changes, hidden pages and questions, disabling of web services, etc.) should NOT AFFECT YOUR STANDARD APPLICATION. All Non-Credit Application back-end changes (194 new race/ethnicity response options and new optional "Full" data field) being implemented in this release are designed to be seamlessly backwards compatibleare optional and not mandatory for colleges to implement. Admissions, Financial Aid, and IT staff can rest assured there isare no action required by the colleges in this release. |
...
REQUIRED by colleges that do not wish to implement the Non-Credit Application. |
...
Implementation Setup Steps
Follow the steps below for successful user acceptance testing: add the new Race & Ethnicity Full data field to your CCCApply Format Definitions XML file for both Pilot and Production environments.
...
- Log in to your college /wiki/spaces/PD/pages/131465676 and start a new CCCApply Standard application from your My Applications page.
- Complete the new application from the Enrollment page to the Needs & Interests page. Continue on to the Demographic Information page.
- Note: This includes the Account Information/Mailing, Education, Citizenship/Military, Residency pages.
- Complete the Gender/Transgender section;
- Complete the Parent/Guardian Education Level;
- Review the new Race & Ethnicity layout changes and enter the following information:
- Hispanic/Latino question: Select the Yes radio button to expand the Hispanic/Latino sub-categories. Select one or more checkbox options.
- Race Group categories: Select one or more of the race group checkboxes to expand the corresponding ethnicity sub-categories.
- Click Continue to go to the last page;
- Complete the remaining required portions of the application and submit the application
- This includes the Submission page sections: Review Review App, Consent to Release Information, and Submission
- After submission, note the application's Confirmation number (App_id) and your CCCID.
- Reference the CCCApply Standard Application Data Dictionary (v.2018.2) Pilot Version
- Jump to the Race & Ethnicity section from the Table of Contents (Race Group)
- Review the Review the data element specifications for all four Race & Ethnicity section fields:
- Hispanic/Latino = <hispanic>
- Race Group = <race_group>
- Race Ethnicity = <race_ethnic>
- Race Ethnicity = <race_ethnicity> (Note: This field has a different name in the International application)
- NEW Race & Ethnicity FullEthnicity Full = <race_ethnic_full>
- Add the new Race & Ethnicity FULL field to your Pilot environment Format XML XML (CCCApply Standard & International files must be updated separately)
- Follow the data specs for <race_ethnic_full> in the updated DED (CCCApply Standard Data Dictionary (v.6.3.0)
- For CCCApply & International: The new data field has the same name for both application: <race_ethnic_full>
- For help updating your Format Definition file, see the CCCApply Download Client User Guide
- Update your existing Download Client Jar File with new version (v.6.3.0)
- Find and replace the "transfer-client.jar" file in your in your CCCApply Download Client with with the latest version for this release (v.6.3.0).
- NOTE: The 'transfer-client.jar" file is the same as the Download Client Jar file.
- Refer to the Download Client User Guide for instructions on replacing and running the Jar file for each application in each environment (Pilot and Production).
- Run a test download Job in the Pilot environment.
- Find and replace the "transfer-client.jar" file in your in your CCCApply Download Client with with the latest version for this release (v.6.3.0).
- Repeat the process for the Production environment.
...
- .
...
...
Testing in the Pilot Environment
User acceptance testing and implementation support for colleges Pilot colleges will begin testing in the Pilot Environment can begin on November 20 upon the completion of the Pilot deployment activities. beginning February 20, 2019.
/wiki/spaces/PD/pages/131465676
...
Data Field Specifications & Mapping
- General Requirements
- Mock Up & Screenshots: New Layout Design
- Change Specifications: New Layout & Database Values
- Release Information for Colleges
UAT FEEDBACK & RESOLUTION
- Feedback should be categorized as bugs and enhancements. Only Severity 1 issues (issues that prevent critical business functions from being accomplished) will be considered as release blockers.
- Reporting: User feedback should be noted in the result section. The following criteria should be followed and documented:
- Any identified bugs with severity and priority
- Enhancement requests with priority identified
Data Field Information
For detailed data specifications, please refer to the corresponding application Data Dictionary, as well as the breakdown of change specs in: 2018-18R: New Race & Ethnicity Implementation 2018.
...
Race Group
...
race_group
...
CSV string
...
Race Ethnicity
...
race_ethnic
...
bpchar, 22
...
Race Ethnicity
...
race_ethnicity
...
bpchar, 22
...
Race Ethnicity Full
...
race_ethnic_full
...
CSV string, no spaces
...
Race Ethnicity Full
...
raceEthnicFull
...
CSV string
...
...
Note |
---|
Race Ethnicity Full Data in Glue for Apply The new Race & Ethnicity values included in this release will be passed directly to colleges using the Glue for Apply feature. However, the new full Race & Ethnicity field is not yet available through Glue for Apply at this time. An upcoming release of the SuperGlue College Adaptor will include this new data. |
Hispanic
Data Field: hispanic
Data Element: <hispanic>
Notes: No changes, this field is a boolean true/false field that continues to work as in previous version
Example Format: boolean (true/false/null)
Race Group
Data Element: <race_group>
Notes: No changes, this field was intentionally left unchanged
Example Format: Apply: "04, 05, 08, 09, 14, 15, 17, 19, 20, 21", International: "04,05,08,09,14,15,17,19,20,21" (note lack of spaces for Intl)
Maximum Expected Width: 78 characters (unchanged) (20 * 2 character long values + 18 commas + 18 spaces + 2 surrounding quote marks for CSV delimiting in the output format)
Race Ethnicity
Data Element: <race_ethnic> (Apply) / <race_ethnicity> (International)
Notes: No changes, this field was intentionally left unchanged
Example Format: YNYNNNNYNNNNNNNNNYNNN
Maximum Expected Width: 22 characters (unchanged) (22 character long string)
Race Ethnicity Full
Data Element: <race_ethnic_full>
Notes: race_ethnic_full is a new field that will store the CSV separated values for all the ethnicity section selections for both the higher level ethnic groups and the associated sub groups as listed above in the chart.
Example Format: "100,101,117,118,200,205,08,09,500,15,600,601,17,19,602,700,701,713,800,802,803"
Maximum Expected Width: 804 characters (201 * 3 character long values + 199 commas + 2 surrounding quote marks for CSV delimiting in the output format)
College Adaptor (SuperGlue) Data Element
For SuperGlue colleges, the new race_ethnic_full data element is called "raceEthnicFull"
UPDATING YOUR DOWNLOAD FILES
...
Feedback & Resolution During Pilot Project
- Feedback will be categorized as bugs, MVP requirements, or change enhancements. Only Severity 1 issues (issues that prevent critical business functions from being accomplished) will be considered as release blockers.
- Reporting: User feedback should be noted in the result section. The following criteria should be followed and documented:
- Any identified bugs with severity and priority
- Enhancement requests with priority identified
...
Data Field Information
For detailed data specifications, please refer to the corresponding application Data Dictionary, as well as the breakdown of change specs in: 2018-24R: Revise CCCApply to Support Non-credit Students & AB3101.
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
To download the new Non-Credit Application data fields and new values in existing CCCApply download files, you must add the new <race_ethnic_full> field fields to your CCCApply Standard Application Format Definition XML and update the (transfer-client.jar) file for this release (Release 6.3.0)the Non-Credit v.1.0 Pilot release.
Warning |
---|
Please be sure to backup your files before downloading new ones. |
...
Data Dictionaries: CCCApply Standard Application Data Dictionary v.2018.2
Copy of UAT: Race & Ethnicity Implementation 2018
Update the Production 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:
...