You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer, so that I can create workflows more easily, I need to be able to separate the business logic from the code into clearly defined steps
This is a tricky one and a bit of a pipe dream. The problem we're trying to solve is that the business logic, the use cases, are tightly coupled with the code base such that this Electronic Filing Case Management Solution is built specifically for the US Tax Court, and it is very challenging for another organization to make use of it. In order to allow for other Courts to use the product, we will need to figure out a way to strip out and make dynamic the business logic.
So, Court A can have one business logic mechanism for creating a petition and court B can have another.
In this new world, we can create workflows that can be reused and called upon as needed.
ToBeContinued
The text was updated successfully, but these errors were encountered:
As a developer, so that I can create workflows more easily, I need to be able to separate the business logic from the code into clearly defined steps
This is a tricky one and a bit of a pipe dream. The problem we're trying to solve is that the business logic, the use cases, are tightly coupled with the code base such that this Electronic Filing Case Management Solution is built specifically for the US Tax Court, and it is very challenging for another organization to make use of it. In order to allow for other Courts to use the product, we will need to figure out a way to strip out and make dynamic the business logic.
So, Court A can have one business logic mechanism for creating a petition and court B can have another.
In this new world, we can create workflows that can be reused and called upon as needed.
ToBeContinued
The text was updated successfully, but these errors were encountered: