valueflows docs
git clone
Log | Files | Refs | README

commit 94c90358bcb0037c01110423983445bba38b0bfb
parent fbaed0a7c166bc0399b62ad20f98b78f9f3e1af7
Author: Bob Haugen <>
Date:   Thu, 15 Oct 2015 11:11:16 -0500

First draft
Ause-cases/ | 26++++++++++++++++++++++++++
1 file changed, 26 insertions(+), 0 deletions(-)

diff --git a/use-cases/ b/use-cases/ @@ -0,0 +1,26 @@ +# [Guerrilla Translation]( + +One feature of this use case is the same resource as both input and output to a series of processes. + +## Processes + +Input | Process | Output +------------- | ------------- | ----------- +Source document | Translate | Translation +Translation | Edit | Translation +Translation | Format | Translation +Translation | Publish | Translation + +In this use case, we need to determine at what stage in the process flow the Translation is in. +In NRP, we do that by connecting it to the ProcessType of the last Process it came out of. +And then, the Input requirement for the next Process is the Translation at the previous stage. + +We use ProcessType instead of Process because then a Translation at the same stage +can be used as an input to other Processes of the same next ProcessType. + +We are working on Recipes that combine Processes and Exchanges, +or value flows that consist only of a series of Exchanges. +In those cases, it would be better to use InteractionType as a superclass of ProcessType and ExchangeType +and use the last InteractionType as the stage of the Resource. + +I'll add some screen shots of a Guerrilla Translation Recipe and process flow soon.