Contact Us

Eliciting Non-functional Requirements

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:
  • Understand what non-functional requirements are and why they are critical to success.
  • Understand the context for non-functional requirements.
  • Use a systematic process for gathering non-functional requirements.
  • Describe and identify key stakeholders and documents for non-functional requirements gathering sessions.
  • Use numerous methods of eliciting the right information from your clients in the right situations in order to:
    • Inspire clients to express their expectations as well as their requirements.
    • Help discover hidden requirements.
    • Utilize the right type of question in the right circumstance.
    • Elicit all types of non-functional requirements.
  • Develop a detailed plan for conducting an elicitation gathering session.
  • Gain consensus on priorities of requirements.
Contents:

CONTENT

Context for Non-functional Requirements

  • Non-functional Requirements definition
  • Non-functional Requirements checklist
  • Eliciting non-functional requirements within the context of the business need
  • Constraints – how are they similar or different than non-functional requirements
  • Business rules
  • Workshop: Context for NFR

Preparing for Elicitation of non-functional requirement

  • Recognize various types of NFRs
    • Usability
    • Reliability
    • Performance
    • Security
    • Supportability
    • Infrastructure and Interoperbility
  • Workshop: Identify initial NFRs

Conducting Elicitation

  • Elicitation techniques, pros and cons
  • Dealing with subjectivity
  • Workshop

Documenting Requirements

  • Writing NFRs in natural language
    • Issues with natural language based NFRs
  • Writing better NFRs using Planguage
  • Landing zone
  • Workshop
  • Model based NFR documentation
  • Workshop

Building Consensus

  • Identifying conflicts
  • Dealing with conflicts
  • NFR’s: Do’s and don’ts
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. 
Knowledge Area:

BABOK®

PMBOK®

Elicitation
Requirements Management and Communication
Enterprise Analysis
Underlying Competencies

Project Scope Management
Project Communications Management
Project Human Resources Management
Project Stakeholder Management

Learn More About Our Association

vellicate-tech.com upliftchild.com lekraken.org