| Course participants |
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.
- Systems analysts
- Requirements analysts
- Business analysts
Secondary:
- Project managers
- Software analysts and designers
- QA designers and testers
- Customers and users
|
| Required Experience |
Students should have an understanding of:
- Project management practices
- The software development lifecycle
|
| training Objectives
|
Upon completion of the course,
participants should be able to:
- Apply requirements management techniques to define a
clear statement of product requirements.
- Capture and document requirements with use-case modeling
techniques.
- Develop requirements in an iterative process.
- Describe a documentation hierarchy and standards for
defining levels of requirements for a product.
- Use requirement attributes and traceability to help
manage scope and change throughout product lifecycle.
- Use requirements to drive ongoing design, test, and
user documentation activities.
|
| Course Arrangement |
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 |
| Course Features |
- hands-on specialist teachers, Interactive case teaching,
Simulation of projects processes.
- Combine theory with practice, and focus on teaching
cases.
- Participants could follow the actual cases, the teaching
style is very specific and profound.
- Specialist will consult the cases expounded by participants,
guide them how to analyze and design a system in the course.
|
