Skip to main content

Cority Workshop 2 Complete, Moving on to Confirm (Testing)

Related services: Cority

Workshop 2 of the Second Stage for the project to implement Cority services at Cornell was held as outlined in the previous update (Working Toward Stage 2's Second Workshop). Cornell and Cority staff are now preparing to complete the current Refine phase and begin Confirm, in which testing will occur.  

Workshop 2 included a high-level workflow review, and covered legal requirements, permits, storage tank equipment, the audit and inspection workflows, questionnaires, reports, and email notification settings. The project is engaged in updates to the Design Tracking Log, which captures decisions, requirements, and action items arising from workshops.  

The project team has verified requirements, updated decisions, and recorded final new action items. These inform the configurations which will be approved as our second iteration for a Solution Design Document. Cority will finish the configurations and update the demo environment as documented in the Design Tracking Log, and they will be tested in the Confirm phase, which is starting in December.  

The Confirm phase will also include the creation of test cases, as well as:  

System testing, which will be done to validate that the configurations that were requested have been completed. It will also uncover any issues and bugs in Cority, which will then be logged and remediated. System Testing will be executed by the Functional Leads and Functional Lead Backups. 

Train-the-Trainer, which is the model Cority uses for training the functional experts who are now most familiar with the configured system. They in turn are responsible for training the rest of the main application and MyCority (also known as portal) users.  Train-the-Trainer will be given to the Functional Leads and Functional Lead Backups. 

User Acceptance Testing, which will validate that Cority can handle the necessary tasks and is ready to be used by the entire user base. Remaining issues and bugs will be logged and remediated prior to go-live. User Acceptance Testing will be done by the entire project team, as well as some campus users. 

Was this page helpful?

Your feedback helps improve the site.