BCS RE18 Practitioner Certificate in Requirements Engineering 2018

BCS RE18 Practitioner Certificate in Requirements Engineering 2018

Practitioner Certificate in Requirements Engineering Certification is designed for people who want to elicit, analyse, validate, document and manage requirements. Most candidates, such as business analysts, business managers and members of their team, business change managers and project managers are preparing for their RE18 certification. As one of the best provider, we have Practitioner Certificate in Requirements Engineering RE18 Exam Dumps to ensure that you can complete RE18 exam to take a disciplined and rigorous approach to defining your business requirements. Come to choose online RE18 exam dumps as the preparation materials now.

Course Key Learnings

• 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

Course Outline

Introduction to Requirements Engineering 5%

• Define the term ‘requirements’ and the characteristics of a requirement.
• Explain the rationale for Requirements Engineering and the application of the

Requirements Engineering framework.

• Explain the rationale of requirements planning and estimating.
• Describe the elements that should be considered as the contents of a project initiation document, terms of reference or project charter:
• Business objectives.
• Project objectives.
• Scope.
• Constraints (budget, timescale, standards).
• Authority or sponsor.
• Resources.
• issumptions.

Hierarchy of Requirements 10%

• Show understanding of the rationale for the requirements hierarchy and describe how it is applied in Requirements Engineering.
• Explain the categories within the hierarchy:
• Business policy (general) requirements.
• Technical policy requirements.
• Functional requirements.
• Non-functional requirements.

Stakeholders in the Requirements Process 5%

• Define the term stakeholder.
• Explain the key roles of the following project stakeholders during Requirements Engineering:
• Project Manager.
• Developer.
• Tester.
• Solution Architect.
• Explain the key roles of the following business stakeholders during Requirements Engineering:
• Project Sponsor.
• Subject Matter Expert.
• Business Manager.
• Interpret a given scenario, identify stakeholders and describe their contribution to Requirements Engineering.

Requirements Elicitation 20%

• Explain different knowledge types:
• Tacit / Non-tacit (explicit).
• Individual / Corporate.
•  Interpret a given scenario to identify different knowledge types.
• Interpret a given scenario to identify relevant elicitation techniques from the following list:
• Interviews.
• Workshops.
• Observation.
• Focus groups.
• Prototyping.
• Scenario analysis.
• Document analysis.
• Surveys.
• Record searching.
• Special purpose records.
• Activity sampling.
• Describe the principles and application of the elicitation techniques (listed in 4.3).
• List the advantages and disadvantages of the elicitation techniques (listed in 4.3).
• Discuss the suitability of the elicitation techniques (listed in 4.3) for Agile and linear development approaches.

Use of Models in Requirements Engineering 10%

• Explain the rationale for modelling the functional requirements (processing and data) of an information system and describe how models help the analyst to:
• Generate questions in order to clarify a requirement and remove ambiguity.
• Define business rules.
• Cross-check requirements for consistency and completeness.
• Interpret a given scenario to develop a context diagram
• Interpret a given scenario to identify the different types of event that can initiate processing (external, time based, internal).
• Understand how to construct a UML case diagram for a given scenario to represent the functional requirements for an information system, including the following notational elements:
• System boundary.
• Actors (user role, another system and time).
• Use cases.
• Communication relationships (associations) between actors and use cases.
• It should be noted that there is no requirement to understand include and extend constructs.
• Interpret a UML Class diagram (comprising of classes, attributes, associations and multiplicities) that represents the data requirements for a given scenario, and describe the business rules that are represented.
• It should be noted that there is no requirement to understand operations, association classes, generalisation (and associated concepts of inheritance and
  polymorphism), aggregation and composition.
• Explain the benefits to be derived from cross-referencing models and illustrate how this can be achieved by using a CRUD matrix (of function or event against data).

Requirements Documentation 15%

• Explain the rationale for creating a requirements document and for documenting requirements at different levels of definition, relating to:
• The nature of the solution.
• The level of priority.
• The delivery approach.
• Understand how to construct requirements documentation for a given scenario, using the following specified styles:
• User story.
• Use case.
• Requirements list.
• Requirements catalogue.
• Describe a requirement in terms of its characteristics or attributes and explain why each of the following may be needed:
• Identifier.
• Name.
• Description.
• Source.
• Owner.
• Type (general, technical, functional, non-functional).
• Priority.
• Business area.
• Stakeholders.
• Associated non-functional requirements.
• Acceptance criteria.
• Related requirements.
• Related documents.
• Comments.
• Rationale.
• Resolution.
• Version history.
• Describe the structure and contents of the requirements document:
• Introduction and background.
• Business process models.
• Function model (use case diagram) of defined requirements.
• Data model (class model) of defined requirements.
• Requirements (defined using the selected documentation style).
• Glossary.

Requirements Analysis 20%

• Explain the rationale for prioritising requirements, using the MoSCoW prioritisation technique.
• Interpret a given scenario and apply the MoSCoW prioritisation technique.
• Examine individual requirements; apply filters and quality criteria to assess that they are well defined.
• Use requirements for a given scenario to check for technical, business and financial feasibility.
• Assign a requirement type to an individual requirement.
• Organise the requirements for a given scenario by requirement type and functional area.
• Within a given requirement set:
• Identify and resolve duplicate requirements.
• Identify and reconcile overlapping requirements.
• Identify conflicting requirements and explain how requirements negotiation could be applied to resolve these conflicts.
• Identify ambiguous requirements and aspects to be defined to remove ambiguity.
• Explain the use of prototyping to elaborate requirements.

Requirements Validation 5%

• Describe the rationale for the following approaches to requirements validation:
• Informal reviews.
• Formal reviews:
• Structured walkthrough.
• Prototype reviews.
• Explain the steps to be followed in the validation process for requirements artefacts:
• Plan review.
• Conduct review of artefacts.
• Collect comments.
• Undertake actions.
• Revise artefacts.
• Obtain approval.

Requirements Management 10%

• Explain the rationale for requirements management.
• Define the elements of requirements management and the links between them.
• Explain the structure and elements of a change control process.
• Explain the structure and elements of version control.
• Define two forms of traceability and how projects benefit from each of them:
• Horizontal (forwards from origin to delivery and backwards from delivery to origin).
• Vertical (to business objectives).