This page lists the non-functional requirements (NFR) of the #2030library #lib08 - Products and services that are not listed on the stakeholder or other pages.
See tab Guide for the various types of non-functional requirements.
#ea11 - Non-Functional Requirements and #unds11 - Non-functional requirements (NFR) list non-functional requirements that are common to the service initiatives.
Look and feel: if the service mustn't be used very often, for instance because it is related to infrequent life events, then it is recommended to align the look & feel with a standard.
Usability and humanity
Performance
Operational and environmental
Maintainability and support
Security
Cultural and political
Legal
List non-functional requirements that are specific and important for the #2030library initiative, tag them as one or more of those listed below. Check types of non-functional requirements for examples and further guidance.
| NFR type | Name |
|---|---|
| 10 | Look&Feel Requirements |
| 10a | Look&Feel - Appearance |
| 10b | Look&Feel - Style |
| 11 | Usability&Humanity Requirements |
| 11a | Ease of Use |
| 11b | Personalization&Internationalization |
| 11c | Learning |
| 11d | Understandability&Politeness |
| 11e | Accessibility |
| 12 | Performance Requirements |
| 12a | Speed&Latency |
| 12b | Safety-Critical |
| 12c | Precision or Accuracy |
| 12d | Reliability&Availability |
| 12e | Robustness or Fault-Tolerance |
| 12f | Capacity |
| 12g | Scalability or Extensibility |
| 12h | Longevity |
| 13 | Operational and Environmental Requirements |
| 13a | Expected Physical Environment |
| 13b | Interfacing with Adjacent Systems |
| 13c | Productization |
| 13d | Release |
| 14 | Maintainability and Support Requirements |
| 14a | Maintenance |
| 14b | Supportability |
| 14c | Adaptability |
| 15 | Security Requirements |
| 15a | Access |
| 15b | Integrity |
| 15c | Privacy |
| 15d | Audit |
| 15e | Immunity |
| 16 | Cultural&Political Requirements |
| 16a | Cultural |
| 16b | Political |
| 17 | Legal Requirements |
| 17a | Compliance |
| 17b | Standards |
- Content
- Questions, answers, comments
- Other sub-sections under #2030library
- On the #2030Library
- On the template
- FAQ
-
#2030library
- #lib01 - The purpose of a #2030library
-
#lib02 - Library stakeholders
- #lib0201a - Aid organisation
- #lib0202 - National governments
- #lib0203 - Local authorities
- #lib0222 - Publishers - Rightholders
- #lib0223 - Schools and other educational institutions
- #lib0231 - Library patrons
- #lib0232 - Teachers and professors
- #lib0233 - Students
- #lib0234 - Researcher
- #lib0235 - Librarian
- #lib0236 - Authors
- #lib0237 - Children and youth
- #lib0238 - Parents
- #lib0239 - Citizens
- #lib03 - Constraints for beneficiaries and systems
- #lib04 - Naming conventions and term use
- #lib05 - Facts, business rules and assumptions
- #lib06 - Partner livelihoods
- #lib07 - Livelihood and library data
- #lib08 - Products and services
- #lib11 - Non-functional requirements (NFR)
- #lib12 - Project Issues
This page is part of the requirements for a #2030Library - A global library for Localizing the Sustainable Development Goals (and fighting the emergence of #AltFacts in public policy).
The availability of an enterprise architecture — preferably as part of an architecture repository — will impact the amount of work that must be invested in describing both existing governance, business, services and application models and models that are being considered for implementation.
In an enterprise architecture described in accordance with the ArchiMate framework: model element descriptions are included in the suitable layer. The rationale for their inclusion in a requirements engineering initiative will often be related to their role in collaborations.