After documenting the business requirements, compile the mapping documents that bridge the gap from architecture to design. Essentially, this means showing the direction of data and the link between the required entities and their fields on each side of the workflow.

You must document to the extent practical; rules for data governance, hierarchical relationships within each system, master schema taxonomy, access for design and runtime users, and the promotion life cycle from development to test and to production.

The Technical Requirements document will be constantly updated as unknown requirements are discovered. The next sections provide best-practices and examples for managing these concepts effectively using Actian DataConnect.