Home > Business Analysis Concepts for Software Testers
Business Analysis Concepts for Software Testers
Business Analysis Concepts for Software Testers
Duration
1 day
Course Cost: $895.00
Overview
To be effective, Software Testers must understand the overall practices and modeling techniques employed by Business Analysts when working with End Users to define project requirements. Definition of requirements is the most critical phase of a project, and software testers must ensure that all requirements are met in order to plan and execute a successful Acceptance Test.
This is a survey course that examines the information that should be present in requirements deliverables, and also reviews the typical analysis and modeling techniques used by business analysts. Attendees will learn about a variety of typical techniques such as swimlane diagrams, process flows, workflows, entity diagrams, and UML Use Cases and Activity Diagrams. Review and approval processes for these types of models will be presented.
As there is a direct correlation between project requirements and Acceptance Testing, the course will examine traceability, and how to approach deriving a set of acceptance tests from a set of requirements.When this course is completed, the attendee will have an increased understanding of the requirements gathering process, the contents and models of requirements and how these translate to acceptance testing requirements.
Objective
Upon completion of this course, participants will be able to define:
Topics
- What information is contained in a Requirements deliverable
- o Functional Requirements
- o Non-Functional Requirements
- How to evaluate written Requirements
- o What makes a “Good Requirement”
- o What makes a “Testable Requirement”
- o Writing guidelines for Requirements
- Different Modeling Techniques and how to interpret the Models
- o Work Flow Diagrams
- o Swimlane Diagrams
- o Flowcharts
- o Process Flow Diagrams and Data Flow Diagrams (DFDs)
- o Entity Relationship Diagrams
- o UML Use Case Diagrams
- o UML Activity Diagrams
- How to provide feedback to Business Analysts
- o One on One
- o Informal Reviews
- o Formal Reviews
- o Structured Walkthroughs
- o Sign-offs
- How to derive Acceptance Testing Requirements from Project Requirements
- o The V-Model
- o Traceability
- o Requirements Decomposition
- o Forward Traceability
- o Reverse Traceability
- o Policy and Procedure Analysis
- o Documentation Materials
- o Training Materials
Audience
Software testers, quality assurance staff, business analysts, and project team members desiring to understand how to interpret Requirements Documents, requirements models, and their associated testing needs.
Courses 4 IT
 |
