IREB Certified Professional for Requirements Engineering - Advanced Level Requirements (Elicitation)

Knowledge of the fundamental aspects of Requirements Engineering. The IREB Foundation certification is only a requirement to take the Advanced certification exam.

This 3 day course is delivered as live instructor-led, either online (remote) or onsite (classroom).

This course provides methods and good practices of Requirements Engineering that can be introduced in any organization, regardless of the business domain with a focus on the elicitation (or extraction of requirements) and their consolidation (negotiation and integration).

The content of the course is also preparation for the Advanced level of certification.

Who is this course for ?

Professionals with career profiles like Requirements Engineering, business analysis, business engineering, and organizational design, who wish to extend their knowledge and skills in the area of requirements elicitation.

Examination:

Additional exam fees charged when applicable.

The “IREB Certified Professional for Requirements Engineering – Advanced Level (Elicitation)” exam consists of:

CPRE Advanced Level (Modeling) – Practitioner

• The exam to achieve the Requirements Elicitation - Practitioner - certificate consists
  of a multiple-choice exam.

CPRE Advanced Level (Modeling) – Specialist

• The exam to achieve the Requirements Elicitation - Specialist - certificate consists of
  a written assignment.

1. EU 1 A framework for structuring and managing requirements elicitation and conflict resolution

   • EU 1.1 The scope of elicitation and conflict resolution in Requirements Engineering
   • EU 1.2 Factors relevant to the approach of planning elicitation and conflict resolution
   • EU 1.3 Planning and executing requirements elicitation and conflict resolution
   • EU 1.4 Process patterns

2. EU 2 Requirements sources

   • EU 2.1 Fundamentals of requirements sources
   • EU 2.2 Identify, classify, manage stakeholders
     • EU 2.2.1 Identifying and selecting stakeholders as requirements sources
     • EU 2.2.2 Stakeholder relationship management
     • EU 2.2.3 Documentation schema for the stakeholders involved
     • EU 2.2.4 The user as a special stakeholder group
   • EU 2.3 Identify, classify, manage documents
     • EU 2.3.1 Identifying and selecting documents as requirements sources
     • EU 2.3.2 Documentation schema for the documents
   • EU 2.4 Identify, classify, manage systems
     • EU 2.4.1 Identifying and selecting systems as requirements sources
     • EU 2.4.2 Documentation schema for systems

3. EU 3 Elicitation Techniques

   • EU 3.1 Gathering techniques
     • EU 3.1.1 Questioning techniques
     • EU 3.1.2 Observation techniques
     • EU 3.1.3 Collaboration techniques
     • EU 3.1.4 Artifact-based techniques
   • EU 3.2 Design and idea-generating techniques
     • EU 3.2.1 Brainstorming
     • EU 3.2.2 Analogy techniques
     • EU 3.2.3 Prototyping
     • EU 3.2.4 Scenarios and storyboards
   • EU 3.3 Thinking tools
     • EU 3.3.1 Thinking in abstraction levels
     • EU 3.3.2 Thinking in terms of problems and goals
     • EU 3.3.3 Avoidance of transformation effects
     • EU 3.3.4 Thinking in terms of models
     • EU 3.3.5 Mind mapping
   • EU 3.4 Example for structuring elicitation techniques: attributes 

4. EU 4 Conflict Resolution 

   • EU 4.1 Conflict identification
   • EU 4.2 Conflict analysis
   • EU 4.3 Conflict resolution
   • EU 4.4 Documentation of conflict resolution 

5. EU 5 Skills of the Requirements Engineer 

   • EU 5.1 Required skills in the areas of elicitation
   • EU 5.2 Communication theory and communication models 
   • EU 5.3 Self-reflection on personal skills in requirements elicitation
   • EU 5.4 Opportunities for personal development
   • EU 5.5 Learning from previous experience