Key Requirements Template

KEY REQUIREMENTS TEMPLATE

1) At a high-level, what is the desired business goal or objective? (insert from earlier discussions with sponsor) e.g. To recruit a world-class administrative staff, in support of the University’s core mission.

2) What are the main business functions needed to attain the stated business goal or objective?

Busines Business Function (fx) s fx letter A e.g. Catalog and distribute current open positions B e.g. Provide an easy way for prospective applicants to find and apply to open positions C e.g. Provide an end-end means for hiring managers to review, select and manage applications to open positions. D e.g. allow creation of ad-hoc reports

3) Stakeholders (department and end-user that will be impacted by this solution) e.g. Facilities staff, parents of students, alumni

4) Business Requirements (these are requirements that are needed to attain goals in section 2)

Busines Req. # Requirement Priorit Requester (If s fx y appropriate) letter (Must(M), Preferred (P), Nice to have (N)) A 1 Ability to have multiple statuses for a posting (draft, posted, filled…) A 2 A 3 B 1 Ability for prospective applicants to narrow open positions by job type, pay grade or department B 2 C 1 Ability for hiring managers to short-list or decline an application D 1 5) User Experience Requirements (identify the attributes of the solution that will enable department and campus end-users to work efficiently and effectively)

Requirements e.g. Terminology used in the application should be familiar and in “plain English.” e.g. Instructions should be clear and brief, and only used where end users expect them to be. e.g. The task flow should work in a way that HR staff, hiring managers and candidates consider logical. e.g. Any time color is used to convey information, a second cue must be used to accommodate color-blind users.

6) Output and Reporting Needs Output Key Elements e.g. occupancy rate reports #of empty room nights per year e.g. Need to print out coupons or vouchers N/A

7) Who/what roles should have access to the system Who/Role Access type (Read only, Individual edit, Group edit, Configure System) e.g. Students Edit information they provide and profile page e.g. Residential College Admins Group edit: any student’s information in their college e.g. Housing staff Group edit: any student’s information e.g. Dinning staff Read only: any student’s dinning information e.g. Summer camp participant No access e.g. Parents of students No access

8) Response Time, Availability and Redundancy Requirements Req. # Requirement Notes 1 e.g. It should take no longer than 2 seconds to load a page once a link or button is clicked. 2 e.g. The system must be available 24/7, except for scheduled downtime in which case there must be at least a week’s advance notice. 3 e.g. For business continuity, the system must be able to retrieve backups from up to thirty days.

9) Regulatory Requirements (HIPAA, FERPA, ADA, PCI…) Req. # Requirement Notes 1 If you are building a campus facing webpage, it should meet “WCAG2.0 AA requirements” 2 If you plan on collecting credit card payments, PCI compliance will apply. Please contact [email protected] for assistance 3 If you plan on using information that is part of a student/faculty/staff’s health records in the application, HIPAA compliance will apply. Please see http://www.princeton.edu/hr/benefits/hipaa/ 4 If you plan on using information that is part of a student’s academic record, FERPA compliance will apply. Please contact The Office of General Counsel for assistance

10) Authentication and Security requirements? Req. # System name: Requirement Notes 1 e.g. CAS: Authentication must be done using CAS 2 e.g. Mobile devices: All devices with the x client installed must be encrypted 11) Integration requirements? (Any internal or external interfaces you need to get data from, or send to) Req. # System name: Requirement Notes 1 e.g. PeopleSoft: Bio demo data including active status should be fed in from PS 2 e.g. Department Charges: Billing information generated by the system should be fed nightly to Departmental Charges

12) Data Conversion /Archiving Requirements A. What if any legacy data needs to be migrated? B. Will any data of institutional relevance be captured in this system, for which you are sole source of this information? If so, who else might need access to that information and how can they access the information? C. Will you need to periodically import or export any data from this system? If so what? D. What are the data retention needs? And when should the data be purged?