Requirementsascode Versions Save

Release of requirementsascode, with 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
• Event queue for non-blocking handling
• Publish events to the same or a different runner
• Generate documentation from a model

Further features:

• 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

Release of requirementsascode, with 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

Further features:

• 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

Pre-release of requirementsascode, with 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
• Generate documentation from a model
• Specify cross-cutting concerns, e.g. measuring performance

Further features:

• 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
• Use TestModelRunner to check which steps have been run so far

Pre-release of requirementsascode, with 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
• Generate documentation from a model
• Specify cross-cutting concerns, e.g. measuring performance

Further features:

• 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
• Use TestModelRunner to check which steps have been run so far

Pre-release of requirementsascode, with the following features:

• Document a use case model, actors, use cases, use case flows, use case steps, events
• Run the use case model for a particular actor
• Extract the use case models, and generate documentation from it
• Specify cross-cutting concerns, e.g. measuring performance

What's new:

• Including use cases to share steps between use cases (#2)

Breaking changes:

• Changes to the public API of the Flow and Step class
• If you are using requirementsascodeextract, update your extract.ftl file (found in package org.requirementsascode.extract.freemarker.lib of the requirementsascodeextract subproject)

Fixes:

• In rare circumstances, a StackOverflowException was thrown instead of a MoreThanOneStepCanReact exception (#1)
• Due to version control problems, two java classes were not located in a correctly named file (CheckOutPurchase and FreeMarkerTemplateEngine). This has been fixed by renaming the classes.

Pre-release of requirementsascode, with the following features:

• Document a use case model, actors, use cases, use case flows, use case steps, events
• Run the use case model for a particular actor
• Extract the use case models, and generate documentation from it
• Specify cross-cutting concerns, e.g. measuring performance.

Limitations include:

• No support for included use cases or subflows so far

What's new:

• requirementsascodeextract subproject for document generation
• New Builder API that clearly separates the model from model building. This makes model processing later on easier.

Pre-release of requirementsascode, with the following features:

• Document a use case model, actors, use cases, use case flows, use case steps, events
• Run the use case model for a particular actor
• Specify cross-cutting concerns, e.g. measuring performance.

Limitations include:

• No support for included use cases or subflows so far

What's new:

• define alternatives at steps ("insteadOf") and continue at steps (see hello world examples)
• run with multiple actors

Pre-release of requirementsascode, with the following features:

• Document a use case model, actors, use cases, use case flows, use case steps, events
• Run the use case model for a particular actor
• Specify cross-cutting concerns, e.g. measuring performance.

Limitations include:

• No support for included use cases or subflows so far

What's new:

• requirementsascodecore: introduce TestUseCaseRunner for simple testing of flows
• shoppingappjavafx: extended example by additional steps

API changes:

• Cross-cutting concerns: method UseCaseRunner.adaptSystemReaction replaces one-arg constructor of UseCaseRunner
• UseCaseStep.reactWhile replaces UseCaseStep.repeatWhile (because it's not a loop, it just may react to the same event several times)
• .continueAfter and .restarts can now be used anywhere .system is used, and only there (to make the API more consistent and easy to use)

Pre-release of requirementsascode, with the following features:

• Document a use case model, actors, use cases, use case flows, use case steps, events
• Run the use case model for a particular actor
• Specify cross-cutting concerns, e.g. measuring performance.

Limitations include:

• No support for included use cases or subflows so far

What's new:

• Enable checking if a UseCaseRunner is running, and stop it.

Pre-release of requirementsascode, with the following features:

• Document a use case model, actors, use cases, use case flows, use case steps, events
• Run the use case model for a particular actor
• Specify cross-cutting concerns, e.g. measuring performance.

Limitations include:

• No support for included use cases or subflows so far

What's new:

• Better exception handling - throw UnhandledException when unhandled exception occurs
• New method canReactTo in UseCaseRunner to check if it reacts to certain type of event
• Shopping app adapted to enable/disable Buy Button based on whether UseCaseRunner reacts to buy event