See the STEPS for UAT Testing and full implementation checklist here: CCCApply Noncredit Pilot - UAT Implementation Checklist |
CCCApply has created a new, optional, noncredit workflow feature in the CCCApply Standard Application. Development requirements for the first version of the new feature were implemented under the guidance of the CCCApply Redesign Workgroup, the CCCApply Advisory sub-committee for Noncredit application and the CCCApply product development team.
This UAT plan will outline the details of the CCCApply Noncredit Application pilot project across the remaining stages of pre-production development, testing and implementation.
Product information is available here: CCCApply Noncredit Application
CCCApply Noncredit Application: Pilot Phase
Below is an outline of the CCCApply Noncredit Application Pilot Project, including development and production phases:
Production Phase (coming)
Development requirements for the first version of this application (v.1.0) were drafted by the CCCApply development team. Requirements and change specifications can be found here: Noncredit Change Requirements and CCCApply Noncredit Application.
A soft launch release to a limited number of colleges for a 12-week pilot project deploy to the CCCApply pilot environment on February 2019, as part of the CCCApply release 6.4.0.
A set of pilot colleges will work with the Workgroup and sub-committee, as well as the CCCApply product development team, to 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.
The overarching goal for the project is to prepare the new features 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 objectives for the pilot project are designed to ensure that the new Noncredit workflow path meets the minimum viable functionality and data collection requirements to comply with changes to the state residency requirements for noncredit students as passed in AB 3101
Participating pilot colleges objectives:
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 | Noncredit Application 1.0 - Soft launch release to the CCCApply Pilot environment | Noncredit v.1.0 Pilot |
February 20 - 28 | Noncredit 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 | Deadline for development changes and bug fixes (Tentative) | |
May 14 | Code freeze for CCCApply 6.5.0 Pilot Release and Noncredit App v.1.2 | |
May 15 - 31 | Noncredit Pilot officially ends May 31, 2019 | |
May 31 | CCCApply 6.5.0 Pilot release (includes the Noncredit Application 1.2 Pilot release) | CCCApply 6.5.0 Pilot |
June 28 | CCCApply 6.5.0 Production release (includes the Noncredit Application 1.2 Production release) | CCCApply 6.5.0 Prod |
Goal | Success Criteria |
---|---|
Ensure MVP product complies with residency-exempt requirements in AB 3101 Ensure the design and development of the Noncredit workflow path feature & functionality meets minimum viable product requirements for use with noncredit students as mandated in AB 3101 |
|
Ensure product functionality meets MVP requirements for college noncredit programs Ensure the functional design (user interface and admin configurations) meet the minimum viable requirements for the majority of college noncredit programs . |
|
Ensure IT implementation is simple and fully compatible with existing Standard Application implementation Ensure college IT implementation of the new Noncredit 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 Noncredit application functionality & data Ensure all dependent CCC Tech Center products and services have been updated with the new and revised Noncredit 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 Noncredit feature Identify, test, document and publish best practices for college support of and/or implementation of the Noncredit workflow feature functionality for (general) college admissions noncredit programs. |
|
The CCCApply Noncredit 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 Noncredit Application. The minimum number of pilot participants to provide validation is 6. 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:
Participation Requirements
Participation activities and requirements include:
The user acceptance testing (UAT) plan process and objectives for the CCCApply Noncredit Application Pilot project are listed below.
See Noncredit Application UAT Plan Slide Deck
UAT Objective | Success Criteria |
---|---|
IT Implementation Steps & Testing |
Find your Noncredit Application PILOT URL |
Data Fields & Downloads Configuration Testing |
|
MVP Admin Configuration (Optional) Testing |
|
Modifying & Running Noncredit App Reports Testing |
|
Using the Pilot Feedback & Support Process |
|
The Noncredit 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 Noncredit 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 Noncredit 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 Noncredit Application. |
Technical specifications for the Noncredit Application workflow feature are included in the CCCApply Standard Application Data Dictionary.
Change Specification: 2018-24R: Revise CCCApply to Support Noncredit Students & AB3101
Project Docs
Additional Docs
Pilot colleges can begin testing the new Noncredit Application feature after the CCCApply 6.4.0 pilot release on February 19, 2019.
Noncredit Application URL
Accessing the Noncredit application workflow path within the Standard Application requires a separate, college-specific URL. This unique, college-specific URL is one of the key characteristics that partitions the noncredit workflow path within the Standard Application, as well as distinguishes the submitted applications that started from the Noncredit URL from those started from the original Standard Application URL.
See here for the list of College Noncredit URLs.
When a user starts and submits a Noncredit Application (using the college-specific URL) the new Noncredit Status flag is set to True, which is appended at the end of the URL.
During the Pilot Project (see pilot schedule above), pilot colleges will meet bi-weekly to provide feedback and discuss pilot objectives with the Pilot committee and CCCApply product manager. Non-critical bugs, change requirements, and change enhancements will be reviewed and prioritized during each meeting.
Severity Levels
S1 - Application / service is unavailable.
S2 - Required business process is prevented from being used. No workaround is available
S3 - Less important business process is impacted and/or workaround is available.
S4 - Low impact or cosmetic issue
Below is a breakdown of the pilot support and change management process and response times.
Severity Level | Issue Type | Description | Operations Priority | Feedback Process |
---|---|---|---|---|
S1 | Application / service is unavailable. | Pilot college cannot access the Noncredit application in the Pilot environment using their custom URL | 24-48 hr response Hot Fix resolution TBD | Email details to College Support Services: staffsupportccctc@openccc.zendesk.com |
S1 | Application / service is unavailable. | Pilot college cannot access the Noncredit application due to error message | 24-48 hr response Hot Fix resolution TBD | Email details to College Support Services: staffsupportccctc@openccc.zendesk.com |
S2 | Required business process is prevented from being used. No workaround is available | Pilot college identifies a critical bug in the Noncredit app user interface or backend systems that prevents implementation or testing | 24 - 72 hr response Set priority level TBD | Email bug information to College Support Services: staffsupportccctc@openccc.zendesk.com |
S3 | Less important business process is impacted and/or workaround is available. | Pilot college identifies a non-critical bug in the Noncredit app user interface or backend that does not prevent implementation or testing | 1 week response Set priority level TBD | Email bug information to College Support Services: staffsupportccctc@openccc.zendesk.com |
S2 | Must Have Requirement Required business process is prevented from being used. No workaround is available | Pilot college identifies a missing IT or business requirement per state, federal or local mandate (example: AB 3101) | 1 week response Set priority TBD | Use Change Requirement template Pilot college documents requirement(s) via Change Requirement form template; sends as link or attachment to Pilot Project Manager to be prioritized for bi-weekly meeting agenda. |
S4 | Nice to Have Request Low impact or cosmetic issue | Pilot college identifies a med/high-priority change enhancement to the MVP application | 2 week response Set priority TBD | Use Change Request template Pilot college submits change requirement(s) using Change Request form template; send as link or attachment to Pilot Project Manager to be prioritized for bi-weekly meeting agenda. |
S4 | Delighter Enhancement Low impact or cosmetic issue | Pilot college identifies an enhancement to the user interface or backend service(s) that includes unauthorized feature development (Out of FY scope) | 2 - 4 week response | Use Change Request template Pilot college submits change request(s) using Change Req form template; send as link or attachment to Pilot Project Manager to be prioritized for committee review. |
Request for Implementation Support | Pilot college requests advice and/or general support for IT implementation, operations, best practices, and/or additional help from Product management, support services, other college pilots, or general colleges - in support of the new project. | 24 - 48 hr response Depending on item; TBD | Pilot college should review existing community discussions for self-serve support, or post new question or topic in any CCCApply or System Alerts category on the CCCTechnology.info support site: CCCTechnology.info |
BUG Prioritization Levels
Priority - Value set by the Product manager with project team to identify when issue should be fixed. P1 - Issue must be addressed as soon as possible as it affects the application / service severely and cannot be used until fixed. P2 - Issue should be resolved as soon as possible during normal course of development activities. It can wait until the next scheduled release. P3 - Consider with future work during normal road-mapping and release planning processes. P4 - Lower priority. Will be addressed as capacity is available after addressing higher priority issues. |
Critical bugs and incidents encountered during IT implementation should be reported directly to College Support Services via the Staff Support email: staffsupportccctc@openccc.zendesk.com Pilot college participants should also copy Pilot Project Manager, Patty Donohue, pdonohue@ccctechcenter.org on critical or high priority issues. |