Use case modeling is a commonly used analysis technique which results in functional requirements and a framework for test case development. When the solution to a business problem or opportunity involves a software component, the solution team must determine how software will best support the business. This class focuses on the business analysis work which includes defining functional, non-functional, and transition requirements which describe the solution and roll out needs.
This course supports and expands on the techniques in the IIBA BABOK® Guide V2.0. Specifically techniques for communicating the business requirements to the solution team, tracing each business requirement to the supporting solution component, assessing the solution applicability and planning for a smooth transition to the solution.
Mentor-led workshops require students to practice the techniques as they learn. Students are encouraged to bring their own projects to class.
In this course students will learn to:
- Use business requirements to identify, evaluate and present alternative design solutions which meet customer needs.
- Prioritize requirements for inclusion in the software development phase using plan-driven (traditional) and change-driven (iterative and agile) techniques.
- Elicit, analyze, and communicate functional requirements that specify how users will interact with the software and how the software will respond.
- Deliver consistent, detailed use case descriptions.
- Incorporate usability principals when developing prototypes.
- Identify non-functional requirements appropriate for each project.
- Learn to assess organizational readiness and build a transition or rollout plan to smooth the implementation of new software for the business.
This 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, or any other project team members responsible for developing functional, non-functional, and transition requirements. Students are encouraged to bring examples of their requirements documents to the class for review and feedback. This course may also be appropriate for individuals who manage business analysts. Developers and solution implementers will benefit from an understanding of how functional and non-functional requirements are elicited and analyzed.
Prerequisites
We recommend that students first attend our Essential Skills for Business Analysis class or have experience in project scope definition, eliciting requirements from stakeholders, and understanding how business requirements fit into the entire systems development effort. We also recommend that students attend Business Process Analysis before attending this class.
Introduction
| 1 hour |
Determine the Solution Scope
| 4 hours |
Defining Functional Requirements
| 4 hours |
Designing User Interfaces
| 2 hours |
Analyze Interface Requirements
| 3 hours |
Identify Non-Functional Requirements
| 2 hours |
Develop Transition Requirements
| 3 hours |
Develop Action Plan/Course Summary Workshop
| 2 hours |
Use Case Modeling and Solution Requirements | $1995 | |
Mar 19 – Mar 21, 2012 | Atlanta, GA | Register |
Apr 23 – Apr 25, 2012 | Dallas, TX | Register |
Jun 11 – Jun 13, 2012 | Chicago-Downers Grove, IL | Register |
Jun 25 – Jun 27, 2012 | Des Moines, IA | Register |
Sep 17 – Sep 19, 2012 | Atlanta, GA | Register |


