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. A use case diagram clearly depicts the scope of the solution to be designed which can help set expectations for stakeholders as to the complexity and interactions with the system.
This class focuses on the business analysis work of defining functional, non-functional, and transition requirements which describe the solution and roll out needs. In addition to use case diagrams and descriptions, this course provides guidelines for developing system and user interfaces, a checklist for non-functional requirements, and strategies for developing an implementation plan. These are critical components in fully defining your solution requirements.
This course supports and expands on the techniques in the IIBA BABOK® Guide V2.0. Specific 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 are explored in detail in this course.
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.
- Create a use case diagram to clarify solution scope.
- Deliver consistent, detailed use case descriptions.
- Incorporate usability principals when developing prototypes.
- Determine the impact of interfaces and develop interface requirements.
- 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 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.
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.
Determine the Solution Scope
Defining Functional Requirements
Designing User Interfaces
Analyze Interface Requirements
Identify Non-Functional Requirements
Develop Transition Requirements
Develop Action Plan/Course Summary Workshop