Being aware of the contemporary social architecture, the globally agreed sustainable development goals and Addis Abeba Action Agenda, we must take into consideration drivers for several key stakeholders.
For each of these stakeholders, we complete a Stakeholder template on a separate page:
- Global society, acting via the United Nations, its specialized organisations and constellations such as for humanitarian aid, education, health, etc.
- National governments who own the national development agendas;
- Local authorities who provide funding for their libraries and implement local development agendas;
- IFLA, the International Federation of Library Associations, and its national member associations;
- Publishers and rightholders;
- several persons who interact with the library services:
#lib02 - Library stakeholders
- #lib0201a - Aid organisation
- #lib0201 - Global society
- #lib0202 - National governments
- #lib0203 - Local authorities
- #lib0211 - International Federation of Library Associations
- #lib0221 - Libraries
- #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
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).
Other sub-sections under #2030library
- #lib01 - The purpose of a #2030library
- #lib02 - Library stakeholders
- #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
Questions, answers and comments
The availability of an enterprise architecture - preferably as part of an enterprise repository - reduces the amount of work that must be invested in describing the stakeholders as a service solution, in this case the #2030library, must be created or modified.
- stakeholders (for the enterprise architecture with respect to which the service solution will be positioned) are included in the motivation extension. The rationale for their involvement will often be related to their role in the Business collaboration that must be supported by the service solution;
- hands-on users (of the product for which requirements are collected) are addressed as part of the active structure aspect:
- the Business actor would include the "stakeholder" descriptive elements and Business role would include the "user role".
- stakeholders of Stakeholder class "Interfacing technology" are named application components and are described as part of the framework's Application layer; The rationale for their involvement will often be related to their role in a Application collaborations among "services".