CPRE-FL (Certified Professional for Requirements Engineering Foundation Level) | Event in undefined | Townscript
CPRE-FL (Certified Professional for Requirements Engineering Foundation Level) | Event in undefined | Townscript

CPRE-FL (Certified Professional for Requirements Engineering Foundation Level)

May 18 - 21 | 06:30 PM (IST)

Event Information

The IREB Certified Professional for Requirements Engineering – Foundation Level (CPRE-FL) course is designed for requirements engineers, business analysts and testers wanting to build their skills in requirement engineering and business analysis. This course provides practical knowledge and requirements engineering tools and techniques which are fundamental to delivering high quality requirements specifications.
This course can act as an intermediary between testing and business analysis career paths, qualifying participants for a role as a BA/QA.

Why take this course: 
Understand the impact of requirement errors on project failure
Learn the rationale for Requirements Engineering as a formal and systematic discipline
Learn various sources of requirements and techniques to capture the required information
Learn how to remove ambiguity in language
Understand how to record requirements
Examine the quality assurance aspects of the requirements and requirements documentation
Learn how to deal with disagreement on requirements and conflict resolution

Program Outline: 

Introduction and Foundations

  • Four major activities of RE
  • Role of communication in RE
  • Skills of a requirements engineer
  • Three kinds of requirements
  • Role of quality requirements

System and System Context

  • Understand System context, Relevant environment and Irrelevant environment
  • Sources of the requirements
  • Sync of the requirements

Requirements Elicitation

  • Requirements sources
  • Significance of requirements sources and consequences of missing requirements sources
  • The most important information of the stakeholder documentation
  • Principles in dealing with stakeholders (stakeholder rights and duties)
  • Using the content and significance of the Kano model
  • Influencing factors for the choice of elicitation techniques
  • Advantages and disadvantages of elicitation techniques - survey, creativity techniques, document centric techniques, observation techniques and supporting techniques

Requirements Documentation

  • Key reasons for requirements documentation
  • Three perspectives of functional requirements
  • Advantages and disadvantages of natural language requirements documentation
  • The most important model-based requirements documentation form
  • The advantages of mixed form of requirements documentation
  • The advantages of standardized document structures
  • One widespread document structures
  • Important points for a tailored standard structure
  • Activities building on requirements documents
  • Using quality criteria for requirements documents
  • Using quality criteria for requirements
  • Most important style rules for requirements
  • Using contents and importance of a glossary
  • Using rules for handling the glossary

Natural Language Requirements Documentation

  • Five transformation processes in the perception and writing of natural language and their consequences on the formulation of requirements
  • Five steps for formulating requirements using a requirements template

Model Based Requirements Documentation

  • “Model” and the properties of models
  • Elements of a conceptual modelling language
  • Advantages of requirements models
  • Importance of goals in requirements engineering
  • Two types of goal decomposition
  • Modelling and using of goal relationships as and/or trees
  • Modelling of and using use case diagrams
  • Specification of and using use case specifications
  • Three perspectives on requirements
  • Data perspective on requirements
  • Entity relationship diagrams and UML class diagrams
  • Functional perspective on requirements
  • Data flow diagrams and UML activity diagrams
  • Behavioral perspective on requirements
  • Using UML state charts

Requirements validation and negotiation

  • Significance of validating requirements
  • Significance of conflicts with regard to requirements
  • Three quality aspects of requirements
  • Validation criteria for the quality aspects "content”, "documentation” and "agreement”
  • Six principles for requirements validation
  • Using the principles of requirements validation
  • Techniques for requirements validation
  • Using the validation techniques: commenting (expert opinion), inspection, walk-through, perspective-based reading, validation via prototypes and use of checklists
  • Activities for requirements negotiation
  • Types of requirements conflicts
  • Various conflict resolution techniques
  • Documentation for conflict resolution
  • Checking and Reconciling Requirements
  • Requirements Management
  • Purpose and definition of attribute schemes
  • Important attribute types for requirements
  • Views on requirements
  • Prioritizing requirements
  • Techniques for prioritizing requirements
  • Requirements traceability
  • Classes of traceability relationships
  • Representation for traceability relationships
  • Versioning of requirements
  • Formation of requirements configurations
  • Formation requirements baselines
  • Requirements changes
  • Functions and members of a Change Control Board
  • Elements of a requirements change request
  • Different classes of change requests
  • Process to handle change requests

Tool Support

  • Features of a requirements management tool
  • Knowing the five aspects in the introduction of requirements engineering tools
  • Knowing the seven views of requirements engineering tools
  • Mock CPRE-FL Exam


This is an online event.
Vellicate Technologies cover image
Vellicate Technologies profile image
Vellicate Technologies
Joined on Jul 20, 2018
Have a question?
Send your queries to the event organizer
Vellicate Technologies profile image
Have a question?
Send your queries to the event organizer
Vellicate Technologies profile image