Interaction Dictionary

Documentation is the ongoing activity of recording facts and specifications for agreements, a system, a pattern or a practice, for current and future reference. Documentation is performed in several CRB Nodes that are linked to the work system or livelihood (alse called the operational theatre) that is subject to a decision or action initiative.

For the operational theatre and its life history the documentation is concerned both with the current situation, the development process and its deliverables. For a collective theatre facing a difficult problem, the decisions and actions typically consists of a number of projects (the project portfolio) which are performed by suitable stakeholders for the overal theatre or its sub-systems.

Each of the projects gets an identifier in the Project Portfolio (which is part of the repository) Other particulars of each project that must be described are included in a project charter:

• time and date it was initiated
• the originator
• the reason (which problem, opportunity, directive or performance alert), and when it was identified
• an estimation of the scope and expected impact of performing the project)
• a cost estimation (budget, time, required skills)
• the project script that is selected for performing the project
• the project status.

The project script selected determines the workflow with tasks of each started project, and the impact area in the CRBC Community Nodes (=workspaces) where this task has to produce results. For this reason, upon determination of the project script nr X, all CRB Nodes involved get a todo task nr X.T, with an indication of the time frame within which it must be performed. Each workspace must include a stack style (most urgent task on top) list of tasks, with indication of task status.

Each of the Tasks in a Workspace inherits the Project Identifier. Other particulars of each Task that must be described are included in a task charter:

• time frame requested (master data in the source CRB Node).
• the performers (planned, actual, via which CRB Node)
• the inputs: parts of repository and outcomes of up-stream tasks in the same project that must be considered when performing the task
• the outcomes (target and actual) the changes made in the CRB Node content as a (planned) result of this task.
• the justification for the design decisions
• a statement of the extent to which expected impacts can be realized, and/or residual requirements will exist (residual requirements must be proposed for reporting in the problem register.
• upon completion of the task, the resources expended (master data in the Development Workspace).

All deliverables that projects and tasks produce are checked in into the relevant CRB nodes (repository cells).

Description