Technical requirements - Information Technology Services

List of Questions/Common ITS Practices
During interviews, validate the following technical requirements:
● Describe the requirement (add to, remove from, or modify the list below, where
appropriate)
● Provide an example use case(s) (full use cases should be documented separately, and
are used for testing ­ unit, functional, technical, load, and user acceptance)
● Identify who requested the requirement, and what they consider is the risk of doing/not
doing
● Confirm the Ranking (cost/benefit), where
○ 1 = Must Have; a “show stopperâ€​requirement, without which the solution is
of little use or benefit
○ 2 = Preferred; if demonstrable efficiency, cost savings, or income producing; may
be deferred or canceled if unacceptable scope risk (cannot accommodate cost,
time, resources, quality)
○ 3 = Optional; Intangible or small benefits only; shall be deferred or canceled if cost
>= benefit
● Confirm the Priority, where
○ Order of completion is necessary to distinguish multiple requests/deliverables
competing for same resources, budget, and/or schedule
# requirement
use case(s)
other notes of interest
0 Confirm Data/System Steward
Contact Info
● name, email, phone,
div/dept/office
● add contact info for any
person with delegated
authority
1 Data Types & Classification
requester
risk of
doing
risk of
not
doing
ranking
priority
1a
Includes restricted or confidential
data (see IS2 andIS3)
● Use Case (example):
1099 information
containing SSN (PII,
restricted)
● Use Case (example):
Worker's comp report