Developer’s Introduction to Business Analysis

  • Course Length:
    1 day
  • Public Pricing:
    No public classes currently scheduled.
  • Onsite Pricing:
    We offer discount pricing for onsite groups. Please contact us to discuss your specific course requirements, group size, and available training dates.

This class provides an overview of the business analysis role and a detailed review of the requirements provided to the development team. To ensure an integrated team, IT developers need to understand the role of the business analysis professional. They should also be familiar with the requirements that the business analysis professionals are eliciting and communicating. This includes understanding categories of requirements, the core requirement components, and the communication formats used for each type of requirement. IT team members must also understand the testing life cycle and the personnel involved.

In this course students will learn:

  • The role of the business analysis professional.
  • Tips for working with the business analysis professional.  
  • The types of requirements that are being elicited and communicated so you can design and implement the best solution. 

Intended Audience

This course is designed for software developers, software architects, or any other project team member who will be using requirements documents for their development work. It is useful for both new developers and experienced developers. Developers will learn how Business Analysts elicit, analyze, and communicate requirements.

Prerequisites

None

Introduction

  • What is the role of a business analyst?
  • Review the major tasks performed by the business analyst.
  • Define the skills needed to perform their tasks.

1 hour

Project Participants and their Roles

  • Identify project participants and their roles
  • Discuss how the business analyst interacts with these participants.

.5 hour

Defining and Detailing Requirements

  • What is a requirement? Why is it important to gather and document requirements? What are the criteria used to judge the quality of "excellent" requirements?
  • Understand the difference between analysis and design or "business" vs. "technological" requirements. Why is it necessary to understand the business problem before deciding on a solution?
  • Learn the 5 core requirement components, what they describe, and why they are important.
    • Entity
    • Attribute
    • Process (Use Case)
    • External Agent (Actor)
    • Business Rule

1.5 hours

Documenting Requirements

  • Learn the recommended approach to categorizing requirements. Why should requirements be categorized? Who uses each category? Why is it difficult to create distinct categories?
    • Business requirements
    • Functional requirements
    • Technical requirements
  • Review a sample requirements package including:
    • Textual templates
    • Entity relationship diagram
    • Decomposition diagram
    • Use case diagram and scenarios
    • Workflow diagram
    • Prototyping

2 hours

Validate the Requirements

  • Introduction to software testing: Why is testing important? What is the business analyst's role in testing? What is the primary objective of testing? What are the phases and types of testing?
  • Learn the two main testing documents: test plans, test cases.
  • Learn to verify that the business requirements are complete by identifying test cases.

1 hour