This course helps you develop skills and learn techniques to efficiently and effectively elicit requirements. From preparing for elicitation sessions to getting consensus, students work through multiple facets of the requirements gathering challenge. It provides a framework for identifying business problems and linking requirements to business objectives in order to solve business problems and set project scope. .
|Duration:||Classroom - 1 Days | Virtual - 2 Days|
|Why to Take This Course:||
In requirements engineering, a functional requirements are those that describes what the system must do. But a non-functional requirement describes not what the software will do, but how the software will do it. For example, software performance requirements and software quality attributes. Nonfunctional requirements are difficult to test; they are usually evaluated subjectively. This makes eliciting non-functional requirements quite challenging and often lead to a significant negative impact on the project quality and delivery.
This course helps you develop skills and learn techniques to efficiently and effectively elicit, analyse and define non-functional requirements. From preparing for elicitation sessions to getting consensus, students work through multiple facets of the requirements gathering challenge. Many practical and engaging exercises and role playing help walk participants through the concepts presented, and afford ample practice with the techniques learned.
|Learn How To:||
Context for Non-functional Requirements
Preparing for Elicitation of non-functional requirement
|Format:||To help assimilate the tools and techniques learned, there is a mixture of individual and group exercises throughout the course. A case study and considerable role play help reinforce concepts learned. Students need to be prepared for a high level of participation. Each participant receives a comprehensive student guide complete with examples and workshop solutions.|
|Who Should Attend:||This seminar is designed for business analysts, business people, systems analysts, project managers, and anyone who is involved in the development of any business product, not just software development.|
|Prerequisites:||Participants should have worked on the analysis, development, maintenance, or enhancement of at least one business “product,” such as software, business processes, services, etc.|
Project Scope Management