How should I design a wizard for generating requirements and documentation
I’m currently working in an industry where extensive documentation is required, but the apps I’m writing are all pretty much cookie cutter at a high level. What I’d like to do is build an app that asks a series of questions regarding business rules and marketing requirements to generate a requirements spec.
How should I design a wizard for generating requirements and documentation
I’m currently working in an industry where extensive documentation is required, but the apps I’m writing are all pretty much cookie cutter at a high level. What I’d like to do is build an app that asks a series of questions regarding business rules and marketing requirements to generate a requirements spec.
Model of simple traffic simulation [closed]
Closed 9 years ago.
Model of simple traffic simulation [closed]
Closed 9 years ago.
Model of simple traffic simulation [closed]
Closed 9 years ago.
Model of simple traffic simulation [closed]
Closed 9 years ago.
Finite State Machine user input tree
I’m drawing a Finite State Machine (which I’ll have to implement later on) which is semi-automatic, i.e. some transitions require user input, some are decided on internal value.
Should I use multiple state machines for a layered protocol?
When implementing a layered communications protocol are layers commonly implemented as state machines?
Should I use multiple state machines for a layered protocol?
When implementing a layered communications protocol are layers commonly implemented as state machines?
Should I use multiple state machines for a layered protocol?
When implementing a layered communications protocol are layers commonly implemented as state machines?