While the majority of Employee Services staff will work remotely to do our part to reduce community spread of the COVID-19 virus, our services will continue without interruption. We're dedicated to providing excellent service to every CU employee and every HCM user. You can still reach us by phone or email. If you have questions or need assistance, reach out at firstname.lastname@example.org or 303-860-4200, option 2.
Get to know the software development lifecycle
As part of our ongoing HCM prioritization process, we want to show you the big picture for our software development lifecycle.
We’ve rolled hundreds of Cherwell tickets into more than a hundred development projects, such as changing the approval workflow and the ability to see future-dated transactions. Forging a partnership among University Information Systems (UIS), Employee Services and other third-party vendors, we share responsibility through a process known as the software development lifecycle (SDLC).
The lifecycle will help us deliver functionality based on your requests, reported issues and identified needs.
The four phases
For every identified system need, we begin by writing functional requirements. This identified need could be specific to one campus or could span multiple campuses. Your feedback, especially through Cherwell tickets, provides the foundation for functional requirements and specifications.
After full requirements have been gathered, UIS teams determine the priority and solution(s) to meet the business need. During the technical design phase, UIS relies on best system practices for consuming delivered HCM 9.2 functionality to minimize customizations, while paying close attention to design and accessibility. Then, internal and external developers get to work, building solutions in the DEV (development) environment.
After the solution is validated and tested by technical teams, we package and migrate it to the TST (test) environment, where System and campus testers ensure the functionality works as expected. TST is a fully integrated environment, providing a platform that closely mimics the HCM Production environment and its relationships to other CU systems. This allows for a full scope of user acceptance testing, helping us asses the downstream effects of changes made to our systems. In this phase, we work closely with application leads and our testing audience.
After testers sign off on the functionality, we migrate the package to the integrated STG environment. This creates repeatable process and allows for quality assurance and final testing activities.
Once the package passes the STG environment, we implement the solution into the PROD (production) environment, better known as HCM.
What this means for you
In short, the software development lifecycle aims to provide a high quality product to end users. Every solution goes through rigorous testing to ensure it serves the business need and works in tandem with other CU programs.
As we work iteratively, we may need to rebuild solutions during the development phase. We depend on limited resources, both internally and externally, so we appreciate your patience when we make adjustments. Our team will work diligently to provide accurate estimates, but please keep in mind that these are subject to change as we coordinate testing efforts between multiple teams.
Our teams will continue to strive to provide fixes and functionality that are critical to your jobs. Thank you for your ongoing support and patience as we continue to stabilize HCM.