The requirements as code project simplifies the development of event-driven applications.
It provides a concise way to create handlers for many types of events at once. A single runner receives events, and dispatches them to handlers. When activated, the runner also records the events. That can be used for replay in event sourced applications.
You can also customize the event handler in a simple way, for example for measuring performance, or for logging purposes.
For more advanced scenarios that depend on the application’s state, you can create a use case model with flows. It’s a simple alternative to state machines, understandable by developers and business people alike.
The v1.0.0 provides the following features:
- Define event handling models with event classes and event handlers
- Define use case models with actors, use cases, use case flows, use case steps that react to events
- Run a model, either for the default user or for a particular actor
- Record events
- Provide a custom event handler
- Generate documentation from a model
- Include use cases
- Ask the runner if an event currently triggers a reaction
- Query the runner for events that are currently reacted to
- Specify event handler for events not handled by the model
Check out the requirements as code project now.
And please give me feedback. It will help me to improve the project.