Versions Compared

Old Version 3

changes.mady.by.user Patricia Donohue

Saved on

compared with

New Version 4

changes.mady.by.user Patricia Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

For detailed information on the approved change request and tech specifications, see
For detailed information on the background information and research behind this proposal, see 

PILOT PROJECT OVERVIEW 

...


...

Project Overview 

Below is an outline of the CCCApply Non-Credit Application pilot project Pilot Project, including development and production phases: 

College Pilot Project

  1. Project Overview & Timeline
    1. Project needsStatus of developmentsummary & objectives
    2. Project Timeline
  2. Goals & Expected Outcomes / Success Criteria
  3. Feedback Process
  4. College Participation & Requirements
  5. Pilot UAT Objectives Objectives
    1. Feedback Process
    2. Changes & Requests

Production

...

Phase

  1. Beta Version Plan
    1. College participation
    2. UAT Plan
  2. College Implementation Plan

      Overview & Timeline

      ...

        1. Working with Enabling Services
        2. Working with Support Services


      Status of Development Phase

      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 development (. Details of the v.1.0 ) will be released development specification can be found here: Non-Credit Change Requirements and CCCApply Non-Credit Application. 

      ...

      Overview

      CCCApply has recently announced that a new "non-credit" workflow path - an optional, special feature developed in the CCCApply Standard Application - is wrapping up the first phase of the development project and is ready to move to the Pilot Phase.

      A soft launch release to the CCCApply pilot environment is planned in February 2019 for the purpose of commencing a 12-week college pilot , as part of the CCCApply release 6.4.0. 

      On February 19, 2019, the first version of the new Non-Credit Application feature will move to a "Pilot Phase" as part of the CCCApply 6.4.0 pilot release deployment. A limited number of pilot colleges - under the direction of the Redesign Workgroup, the CCCApply Advisory sub-committee, and CCCApply product management, will address the following project objectives and timelines:

      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 . A group of 6 - 8 colleges from these oversight committees will be invited to participate in the project. 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.


      The new CCCApply Non-Credit Application is best described as a new, optional, residency questions-free, "workflow" feature built into the CCCApply Standard Application, developed to comply with the new residency-determination exemption for non-credit students, as specified in Assembly Bill 3101.  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.

      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



      The following objectives will be addressed in the Non-Credit App pilot project:


      1. Pilot colleges will commit two staff representatives to participate in the project (One admissions office and one IT staff participants) and complete minimum UAT activities
      2. Participants will contribute to fulfilling project goals, objectives, and timelines in order to achieve success criteria
      3. Participants will attend scheduled meetings and provide feedback on development and implementation processes to ensure CCCApply complies with AB 3101
      4. Participants and project management will collaborate to ensure the application/feature meets production release phase, successfully  

      Pilot Project Timeline

      The proposed schedule for the Non-Credit App Pilot project begins with a soft launch release to the pilot environment as part of the CCCApply 6.4.0 release on February 19, 2019. 

      A tentative schedule of project activities are detailed below (subject to change):    .


      Project commences First recurring Non-Credit Pilot Project meeting is held
      DateDescriptionRelease
      February 19CCCApply 6.4.0 release to the CCCApply Pilot environment (see Release 6.4.0 Summary Notes)CCCApply 6.4.0 Pilot
      February 19Non-Credit Application 1.0 - Soft launch release to the CCCApply Pilot environmentNon-Credit v.1.0 Pilot
      February 20 - 28

      Non-Credit Pilot

      		February 20 - 28

      begins 12-Week Pilot Activities


      March 15CCCApply 6.4.0 Production release  (see Release 6.4.0 Summary Notes)CCCApply 6.4.0 Prod
      April 8Non-Credit Application (v.1.x) Pilot Update (Tentative)Non-Credit v.1.1 Pilot
      April 15Deadline for development changes and bug fixes (Tentative)
      May 9Code freeze for CCCApply 6.5.0 Pilot Release and Non-Credit App v.1.2 
      May 15 - 22Non-Credit Pilot officially ends - last meeting
      May 31CCCApply 6.5.0 Pilot release 
      (includes the Non-Credit Application 1.2 Pilot release)      		CCCApply 6.5.0 Pilot
      Non-Credit v.1.2 Pilot
      June 28CCCApply 6.5.0 Production release 
      (includes the Non-Credit Application 1.2 Production release)      		CCCApply 6.5.0 Prod
      Non-Credit v.1.2 Prod

      ...


      ...

      Pilot Goals & Success Criteria 

      Goals for the CCCApply Non-Credit Pilot Project are listed below with proposed success criteria.


      GoalSuccess Criteria
      Ensure Pilot v.1.0 the design and implementation of the Non-Credit workflow path feature functionality meets minimum viable product requirements for use with non-credit students as mandated in AB 3101

      Chancellor's Office Legal confirm download data meets AB 3101 requirements

      Pilot colleges confirm feature meets the requirements of AB 3101 

      Ensure Pilot v.1.0 data field changes meet existing college 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 filter "majors / programs of study" and/or "major categories" for non-credit application

      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


      Gather requirements and implement ability to configure separate supplemental questions for non-credit application

      ...

      Feedback & Support Process

      TBD




      ...

      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.   

      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

      Participation activities and requirements include:

      • Continual participation throughout the 


      ...

      Pilot UAT Objectives

      For the Non-Credit Application Pilot project, the goals for college user and IT implementation testing are:

      ...

      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 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.


      ...

      Implementation Setup Steps

      ...

      Data Field NameTypeData ElementFormat / LengthDownloadableReport Center / Admin RulesApplication
      Non-Credit StatusNew data field<non_credit>
      		YesYesCCCApply Standard & Non-Credit
      Integrity Flag 81New flag<integrity_fg_81>boolean, 1YesYesCCCApply 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 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:

      ...