Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current Restore this Version View Page History

« Previous Version 9 Next »

NR ID

Requirement

Description

NR-1

Stability

NR-1 Updating version

NR-2

Usability

https://jdi-family.atlassian.net/wiki/spaces/JDN/pages/23429151

NR-3

Extensibility

https://jdi-family.atlassian.net/wiki/spaces/JDN/pages/23986177

NR-4

Platform

https://jdi-family.atlassian.net/wiki/spaces/JDN/pages/24084485

NR-5

Reliability

https://jdi-family.atlassian.net/wiki/spaces/JDN/pages/24084506

NR-6

Usability

https://jdi-family.atlassian.net/wiki/spaces/JDN/pages/25296913

NR-7

Usability

https://jdi-family.atlassian.net/wiki/spaces/JDN/pages/26902553

NR-8

Localization

https://jdi-family.atlassian.net/wiki/spaces/JDN/pages/26902584

NR-9

Reliability

NR-9 Backend crush

Some common assumptions and requirements are described in this topic: https://jdi-family.atlassian.net/wiki/spaces/JDN/pages/65832/SoW+Statement+of+Work#2.4-Assumptions%2C-Constraints%2C-and-Dependencies

 Description of template

Identifier

Requirement

Description

Measurement

Measure

NFRs must be Measurable. Delivery of NFRs can only be assured if they are measurable.

Measurement includes defining:

What is to be measured, e.g. Connectivity uptime.

Method

How it is to be measured, e.g. ICMP Ping of URL performed by Nagios.

Success

Success criteria, e.g. Sub-200ms response for 99.95% of the maximum available minutes per month under normal load conditions.

Dependencies

NFRs must recognise their dependencies. For example, the performance of a website video component that relies on 3rd Party content would be constrained by the performance of the 3rd Party system and the connectivity between the website and that system.

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.