IBM®, Rational® and WebSphere® are trademarks of International Business Machines Corporation (IBM ™)in the United States, other countries, or both.
Mastering Requirements Management with Use Cases provides three days of training in requirements management and use-case modeling techniques. The course focuses on eliciting and managing the changing requirements of a project; analyzing the problem, defining the product vision and feature requirements, defining software requirements with use cases, and requirement attributes, and maintaining traceability, change management, and impact analysis for project scope management. The course shows how use-case modeling and requirements management techniques are used to define and document requirements that meet stakeholder needs. In-class exercises will give students practical experience in developing use cases.
Below is the three day course outline of our trainings:
| Course Name: | Mastering Requirements Management with Use Cases |
| Duration: | 3 days |
| Skill Level: | Basic |
Audience: The course serves two audiences. The primary audience is people who will be actively engaged in the elicitation and definition of software requirements. This includes systems, requirements, and business analysts. The secondary audience would be interested in taking this class because they are consumers of the software requirements and need to understand how to read, verify, interpret and plan with the software requirements of the system. This group includes project managers, software analysts and designers, QA designers and testers, and customers and users.
Secondary:
Prerequisites:
There are no prerequisites for this course.
Recommended Experience
Students should have an understanding of:
Upon completion of the course, participants should be able to:
Course outline:
Best Practices of Software Engineering
Introduction to Mastering Requirements Management with Use Cases
Introduction to Use-Case Modeling
I) Analyze the Problem
a) Find the root causes of the problem
b) Identify the best solution to solve the business problem
II) Understand Stakeholder Needs
a) Define the System
i. Define product features
ii. Find Actors and Use Cases
III) Manage System Scope
i. Use requirements attributes to plan and manage scope
a) Refine the System Definition
i. Detail the Use Cases
ii.Define Supplementary Specifications
b) Manage Changing Requirements
c) Structure the Use-Case Model
i. include, extend, use-case, and actor generalization
IV) Requirements Across the Product Lifecycle