For each important data type, a Business object template will be specified.
- #lib0701: entities that may be represented by bibliographic and authority data
- #lib0702 - Bibliographic description: bibliographic description
- #lib0703: access points
- 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.
To be completed.