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 each data requirement. A business analyst, skilled in data elicitation and definition, can save the business significant time and cost for any project.
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. Additionally, this class 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 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 relationships between data elements and their impact on the business.
- 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.
- Use data requirements 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.
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.
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 or mentor business analysts.
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.
Entities and Attributes
Entity Relationships and Diagramming Conventions
Detailing the Data Requirements
Transition from Business Data to a Physical Design
Workshop - Identify and document data requirements for the case study (Student’s projects may be used for this workshop.)
Appendix - Data Normalization