Examples of use:
- Global society
- #lib0202 - National governments in the #2030library case.
- Moderator in ParliamentWatch debategraph.
A cross-initiative template describes a stakeholder's interest in one or more initiatives w.r.t. a work system, a Sociotope, or a Technotope.
An initiative could be a portfolio, a programme, a project or an iteration.
The Stakeholder name is in the title of the page.
As illustrated for Librarian a number of the below descriptive elements are provided for each initiative, in a separate tab of a chapter.
Field name | Description |
---|---|
Stakeholder Class | One of the options in Stakeholder Class |
Stakeholder Role | A term (job title, department, system class, organisation) that indicates a role for the class of stakeholder |
Stakeholder Rationale | What involvement does the stakeholder have in the requirements debate (for a business product) ? |
Involvement | Estimate when and how much time the stakeholder should be involved in the requirements debate |
Classes of knowledge | Indicate for (some of) these classes the specific knowledge expected for/from this stakeholder: Goals, Business constraints, Technical constraints, Functionality, Non-Functional requirements, Project Issues |
Hands-On Users: If the stakeholder is a hands-on user of the product, then consider below additional fields | |
User name/category | The name of the user group |
User role | A summary of the users' responsibilities |
Subject matter experience | One or more of these ratings: novice/journeyman/master |
Technological experience | The users' experience with relevant technology |
Other user characteristics | E.g. physical or intellectual abilities/disabilities, attitude towards the work area of the product, age group, education, … |
Priority | Rate each user category as: key/secondary/unimportant |
User participation | Ref. Involvement. Provide additional detail: Which kind of functional or non-functional requirements? How much time needed to determine complete requirements? |
Non-functional requirements | List non-functional requirements that are specific and important for the user category, tag them as one or more of the listed types of non-functional requirements |
Project Issues | List project issues that are specific and important for the user category, tag them as one or more of the listed types of project issues |
The availability of an social architecture - preferably as part of a society repository - will impact the amount of work that must be invested in describing the stakeholders as a portfolio, programme or project must be launched.
In a social architecture described using the ArchiMate framework:
- 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".
Acknowledgement: Volère Stakeholder Analysis Template: fields and definitions adapted and modified for usage in the design of web-based service solutions and for use in DebateGraph. Inclusion of Non-functional requirements and Project Issues fields in the template is one of the suggested options in Volère1 and a recommended practice in EMPRESS2.
The backlinks below usually do not include the child and sibling items, nor the pages in the breadcrumbs.
- Aid organisation
- Citizen
- #ea02 - Stakeholders
- Firm
- Global partnership
- International Federation of Library Associations and Institutions (IFLA)
- International Federation of Reproduction Rights Organisations
- #lib02 - Library stakeholders
- #lib12 - Project Issues
- Librarian
- Library
- Local Authorities
- National Government
- Publishers and right holders
- Repository elements
- Reproduction rights organisations
- Requirements templates and patterns
- Schools
- Sidel
- Stakeholder template
- Student
- Teacher
- _template
- Types of non-functional requirements
- Types of project issues
- UN Country Team
- University
- UN Resident Coordinator