| # | 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 | ||
| 4 | Adding assets | ||
| 5 | Does the solution constrain the file size of assets that can be added? | ||
| 6 | Does the solution constrain the performance of asset addition (particularly for batch/bulk) or is 'line speed' the limiting factor? | ||
| 7 | Does the solutions import / upload process function adequately under a bandwidth constrained environment | ||
| 8 | Does the solution support efficient asset upload which doesn't lock the desktop machine | ||
| 9 | Can the asset import / upload be scheduled by users to run out of hours | ||
| 10 | Back Office functions including Search/View/Edit | ||
| 11 | What are typical and target page response times for back office web based asset administration - particularly when working with large asset collections? | ||
| 12 | What are typical and target search response times? | ||
| 13 | What are typical and target API response times? | ||
| 14 | Public facing functions | ||
| 15 | Do you have page response acceptable targets or other performance SLAs for any e-commerce elements of the solution? | ||
| 16 | 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 | ||
| 17 | Does the solution provide APIs which are consumer directly or indirectly by HRP customers? | ||
| 18 | Behaviour under load | ||
| 19 | Are the response times referred to above maintained under agreed number (xx) of concurrent user sessions, back office and public facing | ||
| 20 | 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) | ||
| 21 | Are there any back office processes that could potentially impact the UI/API - e.g. re-indexing or other batch processing updates | ||
| 22 | 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 | ||
| 23 | Backup | ||
| 24 | What would be the data retention periods for backups | ||
| 25 | What is the data recovery/restore process, does it include versions, how long would it take for single assets or large collections? | ||
| 26 | Availability | ||
| 27 | What infrastructure elements provide high availability - load balancing, clustering, dual site failover | ||
| 28 | What is the outward facing behaviour of the system when unavailable - web holding pages, API responses, desktop UI messaging? | ||
| 29 | How many concurrent users can be expected? | ||
| 30 | Disaster Recovery | ||
| 31 | Does this include multi-site geographically diverse capabilities? Please outline the mode of failover | ||
| 32 | What would be the speed / timelines to failover and to bring up required features / data on the DR environment | ||
| 33 | What would be the relative capacity of the DR environment for assets, users concurrent connections etc | ||
| 34 | Would there be any other constraints to functional use if operating against the DR environment | ||
| 35 | What would be the relative performance - response times - of the DR infrastructure | ||
| 36 | What time period would be acceptable to supplier or HRP for operating on the DR environment | ||
| 37 | Maintenance | ||
| 38 | What downtime is required for upgrades, scheduling approach for this? | ||
| 39 | Security | ||
| 40 | What credentials need to be provided to create profile? | ||
| 41 | Is any encryption necessary? Internal v 3rd party integrations? |
Page Comparison
General
Content
Integrations