Detailing Business Data Requirements

  • Course Length:
    3 days
  • PDUs:
    Earn 21 IIBA CDUs and PMI PDUs
  • Public Pricing:
    $1995
  • Onsite Pricing:
    We offer discount pricing for onsite groups. Please contact us to discuss your specific course requirements, group size, and available training dates.
  • Detailing Business Data Requirements: Self-guided study available for purchase.
    Detailing Business Data Requirements Study Guide

Understanding and documenting business data requirements is a critical component in defining complete requirements. Eliciting information needs often uncovers additional processes and business rules. Every business process uses data and almost all business rules are enforced by data. Missing a critical piece of data or incorrectly defining a data element contributes to the majority of maintenance problems and results in systems that do not reflect the business needs. This course teaches students an in-depth approach to data modeling: identifying and defining all necessary data components using both textual templates and an entity relationship diagram.

This course teaches business analysis techniques for eliciting, analyzing, and documenting data requirements to both new and experienced practitioners. Students will be given data templates with a suggested documentation structure for defining Business Data Requirements. It supports and expands on the techniques in the IIBA BABOK® Guide V2.0. Mentor-led workshops require students to practice the techniques as they learn. Students are encouraged to bring their own projects to class.

The course provides business analysts the knowledge to:

  • Identify core data requirements beginning with project initiation.
  • Identify excellent data requirements at the appropriate level of detail.
  • Detail the data requirements (using a data dictionary and data model).
  • Detail complex data related business rules.
  • Assist with the transition of business data to database design.
  • Utilize easy normalization techniques (without all the mathematical theory).
  • Validate data requirements with activity (process or use case) requirements.

Even if your organization has a data administrator or data warehouse team who is responsible for documenting and managing the organization’s information needs, every project uses a subset of that enterprise information in its own unique way. Business analysts must understand the importance of data in all of their projects and include data requirements in their business requirements documentation. Failing to document which data elements need to be used in a calculation, or displayed on a report, leaves the developer the responsibility of choosing the correct pieces of business data from hundreds if not thousands of available fields. These missing requirements often lead to expensive and lengthy project delays during the testing phase.

“… the data sees the big picture, while the various people and machines and organizations that work on the data see only a portion of what happens. As you go about doing a Structured Analysis, you will find yourself more and more frequently attaching yourself to the data and following it through the operation. I think of this as “interviewing the data.”‘ It is usually more productive than any other single interview.”

Tom DeMarco

BA Certification Core ClassThis class is a part of the B2T Training Business Analyst Certification Program. For more information on the program, please see our Certification page.

Intended Audience

This course is designed for business analysts, systems analysts, data administrators, database administrators, or any other project team member involved with business analysis. This course may also be appropriate for individuals who manage business analysts or those who work with the business requirements document and need a more in-depth understanding of the process and documentation.

Prerequisites

We recommend that students first attend our Essential Skills for Business Analysis class or have experience in project scope definition, gathering requirements from subject matter experts, and understand how business requirements fit into the entire systems development effort.

Introduction

  • What is a business data requirement? Why are these requirements important?
  • Review requirements categories and classifications.
  • What is the difference between business data and database design?
  • Review the 7 characteristics of "excellent" requirements.
  • Review the core requirements components.

1 hour

Entities and Attributes

  • Review the components of excellent project initiation and scope analysis.
  • Learn to use the context level dataflow diagram as a starting point for identifying data requirements.
  • Entity types are the basic building blocks of the business data. This section defines entities, gives suggested naming guidelines, teaches the importance of entity definitions, gives criteria to evaluate potential entities, describes entity unique identifiers, and has students identify and document entities from the case study.
  • Attribute types are characteristics of entity types. This section defines attributes, a data dictionary, gives suggested naming guidelines and class words, gives criteria to evaluate attributes, and has students identify and document attributes from the case study.
  • Templates for analyzing and documenting data requirements are provided.

5 hours

Entity Relationships and Diagramming Conventions

  • Learn how business data requirements are displayed in an entity relationship diagram.
  • Relationships are data associations that define the business rules of the project as they relate to data. This section defines relationships and business rules, gives suggested naming guidelines, teaches relationship cardinalities, and has students identify and document relationships from the case study.
  • Review common diagram notations for data related business rules.
  • Learn about an alternative model: the class diagram.

4 hours

Detailing the Data Requirements

  • Detailing repeating data elements. Repeating attributes must be broken down into their components, properly named, and clearly documented with example data values. Students will refine their requirements document based on additional business requirements.
  • Detailing complex business rules. Complex business rules (many-to-many relationships) should be properly named and clearly documented with example data values. Students will refine their requirements document based on additional business requirements.
  • Detailing sub-category entities. Some business data naturally falls into sub-categories and should be documented as such.
  • Review techniques for documenting data conversion, interface requirements and perform gap analysis.

5 hours

Transition from Business Data to a Physical Design

  • Learn how to link the data and process elements to identify missing or incomplete requirements. Each essential process must use data, and each data element must be used by at least one essential process.
  • How does business data become a database design? Review the data requirements for completeness, understand how logical components are translated to physical components, and develop a strategy for maintaining the business requirements.
  • Introduction to database design.
  • Scope the design area using subject areas.
  • What is de-normalization? Why de-normalize a database design?

2 hours

Workshop - Identify and document data requirements for the case study

  • Identify and document entities.
  • Identify and document attributes.
  • Identify and document data related business rules.

4 hours

Appendix - Data Normalization

  • What is data normalization and why is it important?
  • What are the rules of normalization?

Optional

Detailing Business Data Requirements
Course Length: 3 days
$1995

Dec 6 – Dec 8, 2010

Irvine, CARegister

Mar 7 – Mar 9, 2011

AtlantaRegister

Apr 4 – Apr 6, 2011

Dallas, TXRegister