Non Functional Requirements - Questions

#	Question	Comment	Owner
1	are there any HEE system NFRs defined?
2	application standards, should we be complying with anything that we're aware of?
3	values required for items highlighted in yellow
	Adding assets
4	Does the solution constrain the file size of assets that can be added?
5	Does the solution constrain the performance of asset addition (particularly for batch/bulk) or is 'line speed' the limiting factor?
6	Does the solutions import / upload process function adequately under a bandwidth constrained environment
7	Does the solution support efficient asset upload which doesn't lock the desktop machine
8	Can the asset import / upload be scheduled by users to run out of hours
	Back Office functions including Search/View/Edit
10	What are typical and target page response times for back office web based asset administration - particularly when working with large asset collections?
11	What are typical and target search response times?
12	What are typical and target API response times?
	Public facing functions
13	Do you have page response acceptable targets or other performance SLAs for any e-commerce elements of the solution?
14	Does the solution delivers assets directly to customers rather than via a CMS or CDN (specifically as embedded assets in non-image library Uis - e.g. a main HRP website
15	Does the solution provide APIs which are consumer directly or indirectly by HRP customers?
	Behaviour under load
16	Are the response times referred to above maintained under agreed number (xx) of concurrent user sessions, back office and public facing
17	What is the system behaviour under excessive load (customer sessions and/or page requests) - predominantly public facing API or UI? (e.g. web requests queued and returning HTTP 503)
18	Are there any back office processes that could potentially impact the UI/API - e.g. re-indexing or other batch processing updates
19	Does the solution provide a level of elasticity to burst increases in user, traffic or asset volumes. If not immediate, how quickly can capacity be increased and are there any volume constraints on this capacity
	Backup
20	What would be the data retention periods for backups
21	What is the data recovery/restore process, does it include versions, how long would it take for single assets or large collections?
	Availability
22	What infrastructure elements provide high availability - load balancing, clustering, dual site failover
23	What is the outward facing behaviour of the system when unavailable - web holding pages, API responses, desktop UI messaging?
24	How many concurrent users can be expected?
	Disaster Recovery
25	Does this include multi-site geographically diverse capabilities? Please outline the mode of failover
26	What would be the speed / timelines to failover and to bring up required features / data on the DR environment
27	What would be the relative capacity of the DR environment for assets, users concurrent connections etc
28	Would there be any other constraints to functional use if operating against the DR environment
29	What would be the relative performance - response times - of the DR infrastructure
30	What time period would be acceptable to supplier or HRP for operating on the DR environment
	Maintenance
31	What downtime is required for upgrades, scheduling approach for this?
	Security
32	What credentials need to be provided to create profile?
33	Is any encryption necessary? Internal v 3rd party integrations?