Technical requirements - Information Technology Services

Assumptions
1. Business office will perform fit­gap (comparison of legacy business process vs. design
solution); gaps will be accepted (implies business process re­engineering), rejected
(implies mitigation such as re­engineering technical or business processes, and/or
bolt­ons, to address the gap), or transferred (defer mitigation as future enhancement
after deployment of solution).
2. Full cost a new system/service will be charged to the data/system steward, business
office, and/or shared across the user community.
3. If ITS SMT does not approve the new system/service, existing legacy business process
and/or system will remain unchanged.
4.
Acronym Soup
see also ITS Glossary of Policy­Related Terms
● BFB IS = Business and Finance Bulletins, Information Systems
● CRUD = Create, Read, Update, Delete
● CruzID = user ID managed by ITS Identity Management service
● EOL = end of life
● FERPA = Family Educational Rights and Privacy Act
● MTTR = Mean Time to Response/Repair/Restore (duration)
● OLA = Operations Level Agreement
● PCI = Payment Card Industry
● PII = Personal Identity Information
● RWXD = Read, Write, Execute, Delete
● SDLC = Systems Development Life Cycle
● SLA = Service Level Agreement
● SMT = Senior Management Team (comprised of ITS VCIT and Directors)
● SSH = Secure Shell
● VPN = Virtual Private Network
Feel free to use in whole or in part, and modify as needed (please send modifications to
ea@ucsc.edu so that we can improve this template).
Interviews
Perform and document the interviews with Key Stakeholders
● For example: Data/System Stewards, Business Office, Service Providers, Project
Sponsor, Service Manager, etc. as applicable and useful for the project or service
● If status is not 100%, indicate in the notes if completion is necessary before beginning the