Certified Professional in Requirements Engineering – Foundation Level (IREB®)

Why should you follow this training?

Target audience

• You are keen to learn the best practices in requirement engineering, or to deepen your skills in business analysis
• You are a requirement engineer, product owner, business analyst, process analyst, functional analyst, process manager, or interested in understanding the value of professionally handling requirements in a project

Your expectations

• Discover the requirements world or deepen your requirements and analysis related skills through an adequate balance between theory and exercises
• Get a toolbox of techniques necessary to get the job done in a pragmatic way

Advantages

• You prepare the exam of the IREB®  CPRE- Foundation Level
• You get 21 PDUs necessary to pass the IIBA®  exams
• You get 21 CDUs necessary to renew your PMI® certification

What will you learn?

• The Principles, best practices and techniques related to requirements throughout the full project life cycle, illustrated with numerous examples and exercises
• Elicitation: discover the requirements elicitation process, which stakeholders to involve and how to gather requirements using common elicitation techniques
• Documentation: understand the advantages of textual and visual documentation techniques and practise them to efficiently formalize project requirements
• Validation: improve requirements quality by using adequate validation techniques and requirements conflict resolution approaches
• Management: learn how versioning, prioritization, change management and traceability contribute to keep volatile requirements under control

____________________________________________________________________________________________

Training program overview

The diagram below summarizes the CPRE training program content. For each activity, a summary of the key points is provided.

Fundamentals

• Place of Requirement Engineering in project lifecycle (Waterfall – Agile)
• Requirements Engineering/Business Analysis – what is it?
• What do studies show about requirement engineering?
• Why do we need Requirements Engineering in a project?
• Hard & soft skills of a Requirements Engineer
• What are the obstacles for good Requirements Engineering/Business Analysis
• What is a requirement?
• Natural language and communication : the transformational effect
• How to write a requirement using “natural language” : recipe and guidelines
• Requirement template and attributes
• What are the pitfalls of writing requirements in “natural language”
• How are requirements classified? Functional vs Non functional requirements
• What are constraints? Why is it important to log them

Elicit

• What is Requirements Elicitation process?
• What are the key phases of elicitation?
• How to prepare for elicitation: stakeholders analysis & management
• Stakeholder management technique : RACI
• How to prepare for elicitation: Understanding stakeholders goals
• How to prepare for elicitation: Scope definition
• Scope modelling technique : Context Model
• Which human & non-human resources can be used for elicitation?
• What are the common elicitation techniques?
• Factors influencing the elicitation techniques to be used
• Focus on interview as elicitation techniques
• How and why documenting elicitation results?
• How to confirm the elicitation results?

Model

• What are Functional, behavioural & data modelling?
• What are the key characteristics of a good model
• What are the possible levels of formalism to document requirements?
• What is the role of templates? What is the content of a typical template
• Fundamentals of Use case diagrams (actor, system, boundary, inclusion, extension, specialisation)and use case writing (pre-conditions, trigger, main scenario, alternative scenarios, post-conditions, steps)
• Use cases pros & cons
• Fundamentals of UML activity diagrams (activity, action, fork node, join node, decision node, final flow) – practical use on projects
• UML Activity Diagrams pros & cons
• Brief comparison UML notation – BPMN notation
• Fundamentals of UML state diagrams (simple state, transition, hierarchical composite state, orthogonal composite state)– practical use on projects
• Fundamentals of UML class diagrams (object, class, association, multiplicity, aggregation, composition, specialisation) – practical use on projects

Validate & Negociate

• Checking the requirements according to quality criteria
• Principles for performing requirements checking
• Validating requirements to obtain a formal sign-off (baseline)
• Requirements validation techniques : commenting, walkthrough, inspection
• Requirements conflict identification and resolution techniques

Manage

• Why and how to prioritize requirements
• Document versioning techniques using configuration management
• Key characteristics of a document version
• Element of Change management : change request, change control board
• What is scope creeping? How to avoid it?
• Scope creeping awareness : what are the typical sources of scope creeping
• What is requirements traceability?
• What are the three usages of traceability for BA?
• Traceability difficulties
• Requirements management tools : an introduction