About the affordance-centric principle, see the Ens Wiki.

Enterprise architecture for a Global Partnership
For the vision, see Towards a Global Partnership Capability.

For examples of the use of enterprise architecture at multiple levels of scope, see India Enterprise Architecture (IndEA).

Regarding the use of tools and models, see enterprise architecture (Ens Dictionary).

Services that leverage assets
A stakeholder/actor classification and sector maps based on COFOG1, ISIC2 are provided at www.actor-atlas.info, where role-lists, sector maps, actor maps and initiative books for local to global work-system arenas are easily constructed and navigated. Actor Atlas3 pages will provide focussed content anchors for pages in country-specific social capital wikis such as for the Philippines4 and Tanzania.
Initiative management in a multi-stakeholder theatre is known to be difficult. Our experience with participatory approaches, wikis and enterprise architecture in a multi-level perspective5 forms the basis for a consultancy and training offer on requirements practices for the various stakeholders in (complex) Service Initiatives.

Initiative Success Indicators6 An actor's relationship to any public or private service initiative can be in different roles, and for each role, there are specific Initiative Success Indicators.

Requirements Practices Wikinetix offers a range of services and engages in a number of communities and relationships7 to improve requirements practices:

  1. requirements capture: see the example of Parliament Watch and the use of DebateGraph technology and Volère template in it for recommended practices (intermediate level)
  2. requirements review: is a requirements specification free of ambiguity that erodes the likelihood of project success (performed in a confidential relationship)
  3. initiative sociology: how to involve the right people, and how to keep them involved: using your preferred technology (confidential) or using social media (Actor Atlas, development dashboards, sector maps)
  4. learning what stakeholders need: what lies behind what they are telling you; how to invent for them: by modelling actors and their interests and interactions - use of the Actor Atlas and Empress enables us to start where others typically stop (because the allotted time is over)
  5. requirements negotiations: how to solve conflicts on requirements without estranging stakeholders? In Post 2015 SDG's Process a question-driven DebateGraph is illustrated. Participative simulations will allow us to clarify the vicious cycles and erosion of resources that are implied by poorly negotiated resolutions.
  6. participative simulations: how to bring service designs to life, and discover more requirements; including discerning the lock-in by vicious cycles versus the increasing returns from virtuous cycles.
  7. managing requirements for new services that must integrate with existing systems: see the example: Stewardship of Finance;
  8. managing requirements for dependencies among interrelated projects and services: We use Archi - The Free ArchiMate Modelling Tool for capturing requirements and their dependencies, for instance in support of the Addis Ababa Action Agenda. For models of work systems (enterprises), sociotopes and technotopes we apply:
  9. improving your requirements practice by methodologies such as Volere8and EMPRESS9 and visual modelling as applied in Archi (was COMET10).

Questions, answers and comments

Add a New Comment