The SCE activities that provide these outcomes can be performed in parallel. At "some time" they will be integrated into an evaluation (i.e., a prototype or simulation). For this we distinguish development cycles. Each development cycle provides a next version of a prototype. Milestones are specified for the SCE-outcomes that need to be finished for such an evaluation (note: a demonstration can be viewed as a very minimal evaluation).
For agile R&D, SCE defines the Minimal Viable Product (MVP) as a coherent and concise set of (interim) SCE-outcomes, i.e. a coherent set of milestones that lead to the envisioned prototype or simulation.
This Atlassian Confluence wiki-environment is called the Socio-Cognitive Engineering Tool (SCET), aimed to support the process as summarized above. SCET provides design rationale templates and links design concepts to each other (see the SCE Guide). The left frame of SCET shows the items of the main menu (i.e., the "boxes" of the Figure and reference items). General information about the Socio-Cognitive Engineering methodology can be found at http://scetool.ewi.tudelft.nl/; an example application is provided by Neerincx et al.  ( https://doi.org/10.3389/frobt.2019.00118).