This spreadsheet-based template is intended to support documenting detailed requirements (DTRs) discussed in the article “What Requirements Are ...

A spreadsheet-based Data Dictionary template intended for capturing data requirement details for an information system during detailed functional requirement elicitation.

This guide assumes that the reader is familiar with risk analysis and facilitation techniques. Note that only negative risk is addressed in this guide. Besides threats, positive risk (opportunities) may be considered by the facilitator.

The purpose of this spreadsheet is to present an example of detailed requirements for an Automated Function (AF). 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:

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.