Detailing Business Data Requirements


Detailing Business Data Requirements
Share on facebook
Share on twitter
Share on linkedin


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 or support the business needs. Business users often fail to articulate their business data needs because they are so inherent in their work that it is difficult to uniquely identify data requirements. A business analyst, skilled in data elicitation and definition, can save the business significant time and cost for any project.

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.


  • Identify core requirements beginning with project initiation
  • Identify relationships between data elements and their impact on the business
  • Identify excellent requirements at the appropriate level of detail
  • Detail the data requirements (using a data dictionary and data model)
  • Detail complex data related business rules
  • Use data to verify and communicate a more complete understanding of the business domain
  • 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

Student Profile

This course has been designed for business analysts, systems analysts, data administrators, database administrators and any other member of a project team involved in business analysis.


There are no prerequisites to attend this course. However, we recommend students attended our Essential Skills for Business Analysis prior to this class.

Course Materials

Each student will receive a copy of the course documentation prepared by Netmind.


Engaging and interactive course. Our instructors teach all course materials using the demonstrative method; the participants learn new concepts through exercises and real application practices.

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 techniques for eliciting, analyzing, and documenting data requirements to both new and experienced practitioners. Additionally, this data requirements training will tie together other analysis techniques by highlighting the impact of data on the other core requirement components. Eliciting information needs often uncovers additional processes and business rules. Every business process uses data and almost all business rules are enforced by or govern data.

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. Mentor-led workshops require students to practice the techniques as they learn. Students are encouraged to bring their own projects to class.


A certificate of attendance will be issued to students who attend the course for at least 75% of the duration.


This course is included in our Business Analysis Certification Program. By attending this course, students earn credit towards the BA Associate and BA Certified certifications, as well as credit towards the Data Analysis Badge.

Additionally, students will earn 21 credit hours for their attendance.

Course Outline

  1. Introduction
    1. What is business data and how do data requirements support your project solution?
    2. What is the difference between business data and database design?
    3. Review the 7 characteristics of “excellent” requirements
  2. Entities and Attributes
    1. Review the project initiation and scope analysis to identify initial business data needs
    2. Understand the basic building blocks of the business data: entities, attributes, and relationships
    3. Learn to define entities and attributes with business goals in mind. Utilize suggested naming guidelines for consistency and readability
    4. Identify critical attributes for each entity highlighting their data types, valid values and other attribute characteristics
    5. Discuss entity unique identifiers
    6. Differentiate unique business facts within a given attribute
    7. Workshop using case study to identify and detail entities and attributes
  3. Entity Relationships and Diagramming Conventions
    1. Learn how business requirements are displayed in an entity relationship diagram
    2. Detect the business rules of data by identifying key relationships between entities
    3. Define relationships and business rules in more detail using naming conventions
      1. Learn relationship cardinalities and understand their impact on your solution functionality
    4. Review common diagram notations for data related business rules
    5. Workshop to identify and detail entity relationships:
      1. Create a logical entity relationship diagram that accurately reflects the business domain
  4. Detailing the Data Requirements
    1. Detail repeating data elements
      1. Break down attributes into their components using proper naming conventions and clearly document the requirements with example data values
    2. Identify and define advanced entity types to drive effective analysis
    3. Detail complex data business rules and identify additional attributes to describe the business relationships (many to many relationships)
    4. Detail and differentiate between sub-type entities
    5. Review techniques for documenting data conversion, interface requirements and performing gap analysis
    6. Workshop to refine and update the entity relationship diagram to reflect newly discovered requirements
  5. Transition from Business Data to a Physical Design
    1. Learn how to link the data and process elements to identify missing or incomplete requirements
      1. Each essential process must use data, and each data element must be used by at least one essential process
    2. Learn how business data transitions into database design
    3. Review the requirements for completeness, understand how logical components are translated to physical components, and develop a strategy for maintaining the business requirements
    4. Scope the design area using subject areas
    5. Understand de-normalization and the effect on database design
  6. Workshop – Identify and document data requirements for the case study (Student’s projects may be used for this workshop)
    1. Identify and document entities
    2. Identify and document attributes
    3. Identify and document data related business rules
  7. Appendix – Data Normalization (optional)
    1. What is data normalization and why is it important?
    2. What are the rules of normalization?

Public Classes

Currently, we don't have any public sessions of this course scheduled. Please let us know if you are interested in adding a session.

See Public Class Schedule

Course Details


JIS 403


3 days

Delivery Mode

Virtual, Face-to-Face


BA Certified
Request Info

Related Courses

Data Governance Basics

Design Thinking Fundamentals

Design Thinking Advanced

Almost done!

Please check your email to confirm your subscription.

Join our #AlwaysLearning Community

Onsite Training Request

Please provide the information below to help us to customize your solution. 

Contact Us

Netmind US
296 South Main Street, Suite 300
Alpharetta, GA 30009-1973
T. +1 (678) 366.1363
F. +1 (678) 366.1983

Office Hours:
Monday – Friday, 8:30-5:00EST

General Inquiries:

Sales Inquiries:

Request Information