Business Analysis Templates & Aides

The purpose of this spreadsheet is to present an example of detailed requirements for a data import interface. The example is part of the Trips-R-You Flight Booking Case Study. It's purpose is to provide an integrated, end-to-end set of requirement examples. 

The purpose of this spreadsheet is to present an example of detailed requirements for a data export interface. The example is part of the Trips-R-You Flight Booking Case Study. It's purpose is to provide an integrated, end-to-end set of requirement examples. 

The purpose of this spreadsheet is to present an example of detailed specifications for a screen-based user interface. The example is part of the Trips-R-You Flight Booking Case Study. It's purpose is to provide an integrated, end-to-end set of requirement examples. 

The following case study example high-level requirements identify the need for this user interface:

The purpose of this spreadsheet is to present an example of detailed specifications for a report. The example is part of the Trips-R-You Flight Booking Case Study. It's purpose is to provide an integrated, end-to-end set of requirement examples. 

The following case study example high-level requirements identify the need for this report:

The purpose of this spreadsheet is present an integrated, end-to-end set of requirement statement examples, based on the Trips-R-You Case Study. In IIBA® BABOK® V3 terminology, end-to-end means from Business Requirements to Stakeholder Requirements to Solution and Transition Requirements. The case study, and associated artifacts, use the more traditional business terms Goals, High-level Requirements (HLRs), and Detailed Requirements.

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.