6. Extract Domain Logic to Transactions

[agilare]

Process (from MLAP, p. 112) :

• Search the entire codebase for uses of Gateway classes that exist outside Transactions classes.
• Where we find Gateway usage, examine the logic surrounding the Gateway operations to discover which portions of that logic are related to the domain behaviors of the application.
• Extract the relevant domain logic to one or more Transactions classes related to the domain elements, and modify the original code to use the Transactions class instead of the embedded domain logic.
• Spot check to make sure the original code still works properly, and modify the extracted logic as necessary to ensure correct operation.
• Write tests for the extracted Transactions logic, refining them along with the tested code until they pass.
• When all original tests and new tests pass, commit the code and tests, push to the common repository, and notify QA.
• Search again for uses of Gateway classes, and continue extracting domain logic until Gateway usage exists only in Transactions.