Wikinetix

See tab Guide for the various types of non-functional requirements.

#ea11 - Non-Functional Requirements and #lib11 - Non-functional requirements (NFR) list non-functional requirements that are common other 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.

• #unds11 - Non-functional requirements (NFR)

• #2030UNDS
  • #unds01 - The purpose of an Agenda 2030 UN development system
  • #unds02 - Stakeholders and users
  • #unds03 - Constraints
    • #unds031 - Budget constraints
    • #unds032 - UNDS use environment
    • #unds033 - Partner and collaborative systems
    • #unds034 - Schedule constraints
    • #unds035 - Solution constraints
  • #unds04 - Naming conventions, Term use
    • #unds0401 - Code lists for development
  • #unds05 - Facts, rules, assumptions
  • #unds06 - The sustainable development context
    • #unds061 - Collaborative planning for the #2030Agenda
    • #unds062 - Partnership work streams
  • #unds07 - Development and UNDS data
  • #unds08 - Products and services
  • #unds11 - Non-functional requirements (NFR)
  • #unds12 - Project issues
    • #unds18 - Open issues
    • #unds19 - Off-the-shelf solutions
    • #unds20 - New problems
    • #unds21 - Tasks
    • #unds22 - Migration to the new product
    • #unds23 - Risks
    • #unds24 - Costs
    • #unds25 - User documentation and training
    • #unds26 - Waiting room
    • #unds27 - Ideas for solutions

This page is part of the requirements for a United Nations Development System for delivering the Sustainable Development Goals (#2030UNDS).

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.

To be completed.