BCS Practitioner Certificate in Requirements Engineering

• Learn how to take a best practice approach to defining business requirements
• Develop a set of practices and processes to identify requirements in order to develop and design business solutions
• Techniques to engage with stakeholders and draw out information to define requirements
• Attain one of the four modules you need to gain the International Diploma in Business Analysis, which follows entry onto the professional registration for IT technicians (RITTech)

Reed Courses Certificate of Completion

Digital certificate - Included

• Introduction to the course 00:52

  • 1: Introduction 00:52

• Define Requirements Approach and Project Scope 29:28

  • 2: Introduction to the section 00:28
  • 3: Define the term “Requirements” 02:42
  • 4: The Requirements Engineering Framework 02:53
  • 5: Factors to be considered in adapting the approach to requirements engineering 15:14
  • 6: The contents of a project initiation document (PID)/terms of reference (ToR) 08:11

• Elicit Requirements 1:16:14

  • 7: Introduction to the section 00:32
  • 8: Different knowledge types 06:24
  • 9: Techniques to articulate tacit knowledge 11:15
  • 10: The use, advantages and disadvantages of elicitation techniques (Interviews) 04:28
  • 11: Workshops 05:15
  • 12: Observation 04:48
  • 13: Shadowing 04:54
  • 14: Story-telling 04:38
  • 15: Scenario Analysis 04:47
  • 16: Scenario Role-Play 04:41
  • 17: Prototyping 04:43
  • 18: Document Analysis 05:01
  • 19: Appropriate technique to elicit requirements - Project Approach 03:23
  • 20: Resources 03:34
  • 21: Stakeholder expertise 03:36
  • 22: Suitability of elicitation techniques for Agile and linear approaches 04:15

• Record Requirements (Documentation) 40:33

  • 23: Introduction to the section 00:32
  • 24: Identify and describe the categories of requirement 03:02
  • 25: Technical Requirements 01:18
  • 26: Functional Requirements 04:09
  • 27: Non-Functional Requirements 04:06
  • 28: The importance of documentation 03:33
  • 29: Documentation enables effective communication 03:51
  • 30: Documentation serves as a basis for validation 03:44
  • 31: Documentation supports product development 04:04
  • 32: The key documentation styles 04:20
  • 33: The characteristics documented for requirements in a requirements catalogue 04:22
  • 34: The key underlying principles and standard format of a user story 03:32

• Build Models and Prototypes to Represent the Requirements 23:06

  • 35: Introduction to the section 00:39
  • 36: Rationale for modelling the functional requirements of an information system 03:52
  • 37: The purpose of modelling in requirements engineering 03:49
  • 38: Prepare a UML diagram 03:05
  • 39: Prepare a UML Class diagram 04:31
  • 40: The use of a CRUD matrix 03:24
  • 41: The use of prototyping to elaborate requirements 03:46

• Collaborate and Communicate with Stakeholders to Clarify Requirements 22:38

  • 42: Introduction to the section 00:35
  • 43: Responsibilities of the actors (stakeholder roles) in Requirements Engineering 07:35
  • 44: The purpose of requirements validation 03:39
  • 45: The rationale for various approaches to requirements validation 03:06
  • 46: How Agile requirements are validated 03:56
  • 47: How formal requirements are validated 03:47

• Analyse, Prioritise and Assure the Quality of Requirements 27:52

  • 48: Introduction to the section 00:38
  • 49: The purpose of analysing requirements 03:21
  • 50: The MoSCoW technique to prioritise requirements 02:43
  • 51: Interpret individual requirements; applying filters and quality criteria 07:48
  • 52: The purposes of Slicing Requirements (Agile/ Linear) 02:51
  • 53: Identify techniques used to analyse Business Rules 03:13
  • 54: The importance of testability 07:18

• Conduct User analysis and Profiling 11:27

  • 55: Introduction to the section 00:19
  • 56: Techniques used to analyse roles 06:22
  • 57: The purpose of a Customer Journey Map 04:46

• Requirements Management and Traceability 21:24

  • 58: Introduction to the section 00:36
  • 59: The rationale and the approach to achieving requirements traceability 04:13
  • 60: The rationale for requirements management 02:31
  • 61: The elements of requirements management and the links between them 04:09
  • 62: The use of a change control process 03:13
  • 63: The elements of a version control process 03:17
  • 64: The use and advantages of different forms of traceability 03:25

• Practice Exam 57:00

  • 65: Practice Exam 57:00

What will I learn?
This certificate was updated (July 2021) as a part of our aim to continuously improve the quality of learning within our professional certifications. This update allows BCS to remain at the forefront of best practice industry standards for professional certifications. In the updated BCS Practitioner Certificate in Requirements Engineering you’ll learn how to take a systematic approach to eliciting, defining, analysing, validating, documenting and managing requirements.

The certificate includes:

The Requirements Engineering Framework
How to elicit requirements and techniques to use
How to collaborate and communicate with stakeholders in the requirements process
How to write a user story
Best practice approaches to document requirements
How to manage requirements
Validating, prioritising and quality assurance in the requirements process
Analysing and evaluation of requirements

Who is it for?
This practitioner certificate is designed for people who want to gain an understanding of the role that business, customer and requirements play within professional business contexts
Suitable for business analysts, project managers, systems analysts, product owners, product managers and those involved in business change processes and/or projects

There are no pre-requisites for this certification.

Currently there are no Q&As for this course. Be the first to ask a question.