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

ireb

Duration :

3 days

Languages :

French

English

Available as :

Open training

Customized training

On-premises training

Description :

The success of any project is significantly influenced by the use of requirements engineering. Many other disciplines depend on the results of requirements engineering. This training will present you principles, best practices and techniques to define goals and scope, to identify stakeholders, to gather the required information from them and to transform the information in the correct model and manage it throughout the project.

The objectives of this course are the following :

– Prepare to the International Requirements Engineering Board 2.2. “Fundamentals” level examination.

– Provide analysts / requirements engineers with the knowledge of core analysis activities.

– Provide analysts with a toolbox of techniques necessary to get the job done in a pragmatic way.

You have an interest in understanding the requirements engineering process, you are seeking to acquire the IREB Foundation Level certification, you want to discover the analysis world or improve your analysis skills, this training is the right place to address your needs.

Fundamentals

  • Place of Requirement Engineering in project lifecycle (Waterfall – Agile)
  • Requirements Engineering – what is it?
  • What do studies show about requirement engineering?
  • Why do we need Requirements Engineering in a project?
  • Hard skills & soft skills of a Requirements Engineer
  • What are the obstacles for good Requirements Engineering
  • What is a requirement?
  • Natural language and communication : the transformational effect
  • What are the pitfalls of writing requirements in “natural language”
  • How to write a requirement using “natural language” : recipe and guidelines
  • Syntactical structure of a requirement : single requirement template and requirements attributes
  • 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
  • System boundary, context boundary and irrelevant context
  • Scope modeling 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
  • How and why documenting elicitation results?
  • How to confirm the elicitation results?

Documentation & Modeling

  • Why document textually & model visually requirements?
  • What are the key characteristics of a good model?
  • What is dynamic and static modeling?
  • What are Functional, behavioural & data modeling?
  • 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 – practical use on projects
  • Use cases pros & cons
  • Fundamentals of UML activity diagrams – practical use on projects
  • UML Activity Diagrams pros & cons
  • Brief comparison UML notation – BPMN notation
  • Fundamentals of UML state diagrams – practical use on projects
  • Fundamentals of UML class diagrams – practical use on projects

Validate & Negociate

  • Why validate requirements? Quality and agreement
  • Document level quality criteria
  • Requirement level quality criteria
  • Principles for performing requirements validation
  • 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
  • The Kano model
  • Document versioning techniques using configuration management
  • Key characteristics of a document version
  • Element of Change management  : change request process, 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?
  • Traceability difficulties
  • Requirements management tools : an introduction
Share this Post!