Business Analysis Templates & Aides

Section 3 begins by presenting one additional tool - a Data Dictionary. As the detail for a given HLR is discussed, the data-specific business needs involved are captured using this tool. The idea is to add entries about record types and fields (i.e. entities and attributes) the first time their need is discussed (e.g. an HLR for a specific screen or report). Once captured, those data-specific details are available for reference when those needs come up again, as they will, during discussions involving other HLRs. The detail in the data dictionary is shown to support a transition requirement for a new or updated database schema.

Just like projects have a project management plan, business analysis should have a business analysis plan.  The attached template is intended to help BAs in developing and documenting their BA planning activities in this template depending on the needs of the project.

A two page matrix type summary of BABOK v3 showing:
1. CRUD (create, read, update, delete) type analysis of Inputs and Outputs versus the complete Task list.
Note: The initial CRUD section separates out and shows the Guideline and Tool Inputs as a small 'r' with 'full' Inputs showing as a Capital 'R'.
2. Stakeholders versus Tasks
3. Techniques versus Tasks.