IREB CPRE-Requirements Engineering
The hardest single part of building software is deciding precisely what to build. The challenging task of defining detailed requirements is critical for developing any software and if done wrong it can cripple a system and even completely ruin a system.
| Duration | Language | Method |
|---|---|---|
| 3-days | English | Virtual and Class-room |
Requirements engineering is complex and involves a variety of tasks which include the elicitation process, requirements refinement, negotiation and resolving stakeholder conflicts, properly documenting the requirements, applying various modeling techniques and validating and managing the requirements.
Stakeholders can include executives, end users, marketers, technical managers, developers, testers, business analysts and can even include insurance experts, legal advisers and government departments. The number and diversity of the stakeholders necessitate good communication practices.
In this course, you will learn all the best practices of requirements engineering. You will learn how to identify requirement by using various elicitation techniques. You will learn how to document and track requirements. You will know how to negotiate and interact with stakeholders. You will master various modeling techniques and will know how to track and manage the requirements to completion. A variety of tool categories that support requirement engineering will be covered.
General Course Information
This course is ideal for testers and test teams preparing for the ISTQB Foundation certification.
Who should attend this course?
- Testers
- Test Analysts
- Business Analysts
- Requirements Engineers
- Systems Analyst
any person in ICT with an interest in quality assurance and requirements engineering.
Pre-requisites:
There are no prerequisites for this training course. However, it is recommended that the candidate has a basic background in the field.
LEARNING OBJECTIVES
Through presentation, discussion, and hands-on exercises, attendees shall:
- EO 1.1 Knowing symptoms of and reasons for inadequate RE
- EO 1.2 Knowing the four major activities of RE
- EO 1.3 Knowing the role of communications in RE
- EO 1.4 Knowing the skills of a requirements engineer
- EO 1.5 Knowing the three skills of requirements
- EO 1.6 Knowing the role of quality requirements
- EO 2.1 Knowing system context, system boundary and context boundary
- EO 2.2 Mastering and using system boundary and context boundary
- EO 3.1.1 Knowing various types of requirements sources
- EO 3.1.2 Knowing the significance requirements sources and the consequences of disregarded requirements sources
- EO 3.1.3 Knowing the most important information of stakeholder documentation
- EO 3.1.4 Knowing important principles in dealing with stakeholders (stakeholder right and duties)
- EO 3.2.1 Mastering and using the content and significance of Kano model
- EO 3.3.1 Knowing influencing factors for the choice of elicitation techniques
- EO 3.3.2 Knowing advantages and disadvantages of elicitation techniques
- EO 3.3.3 Mastering and using the following types of elicitation techniques and examples for each: survey, creativity, document-centered, observation and supporting techniques
- EO 4.1.1 Knowing key reason for requirements documentation
- EO 4.2.1 Knowing the three perspectives of functional requirements
- EO 4.2.2 Knowing advantages and disadvantages of natural language requirements documentation
- EO 4.2.3 Knowing the most important model-based requirements documentation form
- EO 4.2.4 Knowing the advantages of mixed form of requirements documentation
- EO 4.3.1 Knowing the advantages of standardized document structures
- EO 4.3.2 Knowing one widespread document structures
- EO 4.3.3. Knowing important points for a tailored standard structure
- EO 4.4.1 Knowing activities building on requirement documents
- EO 4.5.1 Mastering and using quality criteria for requirements documents
- EO 4.6.1 Mastering and using quality criteria for requirements
- EO4.6.2 Knowing the two most important style rules for requirements
- EO 4.7.1 Mastering and using contents and importance of glossary
- EO 4.7.2 Mastering and using rules for handling the glossary
- EO 5.1 Mastering and using the five transformational processes in the perception and writing of natural language and their consequences on the formulation of requirements
- EO 5.2 Mastering and using the five steps for formulating requirements using a requirements template
- EO 6.1.1 Knowing the term “model” and the properties of models
- EO 6.1.2 Knowing definition elements of a conceptual modeling language
- EO 6.1.3 Knowing the advantages of requirements models
- EO 6.2.1 Knowing the importance of goals in requirements engineering
- EO 6.2.2 Knowing the two types of goal decomposition
- EO 6.2.3 Mastering the modeling and using of goal relationships as and/or trees
- EO 6.3.1 Mastering the modeling of and using use case diagrams
- EO 6.3.2 Mastering the specification of and using use case specifications
- EO 6.4.1 Knowing the three perspectives on requirements
- EO 6.5.1 Knowing the focus of the data perspectives on requirements
- EO 6.5.2 Mastering and using entity relationship diagrams and UML class diagrams
- EO 6.6.1 Knowing the focus of the functional perspective on requirements
- EO 6.6.2 Mastering and using data flow diagrams and UML activity diagrams
- EO 6.7.1 Knowing the focus of the behavioral perspective on requirements
- EO 6.7.2 Mastering and using UML state charts
- EO 7.1.1 Knowing the significance of validating requirements
- EO 7.2.1 Knowing the significance of conflicts with regard to requirements
- EO 7.3.1 Knowing the three quality aspects of requirements
- EO 7.3.2 Mastering and using validation criteria for the quality aspects “content”, “documentation” and “agreement”
- EO 7.4.1 Knowing the six principles for requirements validation
- EO 7.4.2 Mastering and using the principles of requirements validation
- EO 7.5.1 Knowing techniques for requirements validation
- EO 7.5.2 Mastering and using the validation techniques: commenting (expert opinion), inspection, walkthrough, perspective-based reading, validation via prototypes and use of checklists
- EO 7.6.1 Knowing activities for requirements negotiation
- EO 7.6.2 Knowing the types of requirements conflicts
- EO 7.6.3 Knowing the various conflict resolution techniques
- EO 7.6.4 Knowing the documentation for conflict resolution
- EO 8.1.1 Knowing the purpose and definition of attribute schemes
- EO 8.1.2 Knowing important attribute types for requirements
- EO 8.2.1 Mastering and using views on requirements
- EO 8.3.1 Knowing methods for prioritizing requirements
- EO 8.3.2 Mastering and using techniques for prioritizing requirements
- EO 8.4.1 Knowing the benefits of requirements traceability
- EO 8.4.2 Mastering and using classes of traceability relationships
- EO 8.4.3 Mastering and using forms of representation for traceability relationships
- EO 8.5.1 Mastering and using versioning of requirements
- EO 8.5.2 Mastering and using the formation of requirements configurations
- EO 8.5.3 Mastering and using the formation requirements baselines
- EO 8.6.1 Knowing the importance of requirements changes
- EO 8.6.2 Knowing the functions and members of a Change Control Board
- EO 8.6.3 Mastering and using the elements of a requirements change request
- EO 8.6.4 Mastering and using different classes of change request
- EO 8.6.5 Mastering and using a process to handle change request
- EO 9.1Knowing the eight features of a requirements management tool
- EO 9.2 Knowing the five aspects in the introduction of requirements engineering tools
- EO 9.3 Knowing the seven views of requirements engineering tools
Session Plan
The course runs for three days starting at about 08:00 ach day is about 360 minutes of class time, from 8:00 to 4:30. For custom courses, material may be deleted, added, or expanded upon as needed.
Please note that timings are approximate, depending on attendee interest and discussion. All of the lectures include exercises and/or knowledge-check questions except as noted.
The following shows this session plan in relation to the chapters and sections of the IREB Certified Professional for Requirements Engineering syllabus.
Course Content
IREB CPRE – Requirements Engineering Foundation Exam
Included in our training fee is one IREB CPRE-Requirements Engineering Foundation exam session hosted by the SASTQB (Southern African Software Testing Qualifications Board) www.sastqb.org.za
Duration: 75 minutes
Number of Questions: 45 Multiple Choice
Pass Mark: 70%
Book Training
Are you ready to book for the IREB CPRE – Foundation course? Follow the link below to start the process.
Request For Quote
Reach out to our office for a formal quotation. We offer training for individuals and companies. Group bookings qualify for a discounted price.