vdd icon indicating copy to clipboard operation
vdd copied to clipboard

More Guidance on Implementation

Open ebuchman opened this issue 5 years ago • 1 comments

We should try to distill more about what we've learned about writing testable state machines into this. This includes areas like:

  • moving IO out of the state machines into a "routing layer"
  • routing between internal state machines
  • "scheduler" state machines for scheduling/receiving network messages
  • feeding output messages from a state machine back into itself
  • state machines returning one or many output events
  • event and error data structure design
  • etc.

Some of this might be more language specific, but maybe that's ok - it would be valuable to have VDD guidance for particular languages ...

ebuchman avatar Mar 23 '20 04:03 ebuchman

I agree. Up to know we have focused on the verification side, in particular regarding the structure and content of the English spec. As next step we should incorporate engineering guidelines. Also we should figure out Engineering need for the specifications, that is, what is missing in the current form from an engineering perspective

josef-widder avatar Apr 02 '20 14:04 josef-widder