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.
This template suggests the syntax, with examples, to create concise functional requirements documents. The template covers most conditions systems that engineers will need to account for in creating systems specifications. Furthermore, the suggested formats in this template conform with the Easy Approach to Requirements Syntax (EARS).
Unified Modeling Language (UML) Quick Reference Guide courtesy of No Magic Inc. This at a glance resources is a great mini-poster for every business analyst who needs to reference the UML standard on a moment's notice.
brought to you by enabling practitioners & organizations to achieve their goals using: