I am trying to document a crop management system and the question concerns how to document how a boringly simple transaction can trigger a state change on it's parent.
For instance, a truck of peas arrives at a weighbridge from a given paddock. For the purposes of this discussion the stand of peas in the particular field is modelled as a crop with an interesting life-cycle {planned, planted, sampling, harvesting, harvested,cancelled}. The transition from sampling to harvesting is show by a 'harvesting-in-progress' signal on the statechart.
There will be several truck-loads from that paddock of peas and each weigh-bridge transaction is called an 'intake'. For the purposes of my scope, an intake is boring. it is created (and may be deleted if it was in error).
If I am using an action language for detailed specification (and hopefully generation), do people think the best place to document the first intake generating the paddock's harvesting-in-progress signal would be :-
1. In the intake notes field with some sort of 'create event' syntax.
2. On the intake/crop-association notes field with some sort of 'create event' syntax.
3. Create a trivial statechart on the intake and document it on the create transition.
4. Create an activity diagram and somehow associate it with the intake.
And finally, is this the sort of question that this new forum is about?
Show Posts
