A Quick Glance

Business Analysis is growing in demand as are Business Analysts. These professionals cannot just be content with one particular technique rather they would require many different methods to handle business system requirements. Those organisations or individuals who stand to be affected by any changes to an organisation can gain from this course. At  Pearce Mayfield, the delegates get to learn these concepts so they can use them whenever their profile demands. The Requirement engineering course is a part of the required courses in the Core module.

  • black-arrow

    Learn to Manage Requirements in a Business House

  • black-arrow

    Advantage of High-Level Jobs and Better Perks and Salaries

  • black-arrow

    Learn from Experienced and Certified Instructors

  • black-arrow

    Certification by BCS

  • black-arrow

    The Course is a part of the BCS Internal Diploma in Business Analysis

The course has no prerequisites, but  a basic knowledge of Requirement Engineering is recommended (from some other source)  though not mandatory.

For those who are looking forward to get an understanding of the Business Analysis skills , the course is relevant to all of them. Professionals such as  Business analysts, business change managers, business managers and their staff, and project managers. Those who wish to acquire the BCS Diploma in Business Analysis can sit for this course. The BCS Certificate in Requirements Engineering is one of the Core modules that must be cleared and also one of the four modules covered under the BCS International Diploma Program.

exam

Key Learning Points

exam

Tutor Support

exam

Courseware

By the time the course finishes, the delegates would have become familiar with the following:

  • Stakeholders : Roles And Responsibilities In Requirements Engineering
  • How to Use Range Requirements Elicitation Techniques?
  • Uses and Relevance of Requirements Elicitation Techniques To Specific Situations
  • Documenting And Prioritizing User Requirements For An Information System
  • Requirements and Its Problems
  • How to Improve Requirements Documentation.
  • Making A Process/Function Model for an Information System.
  • Understanding A Model Of Data
  • The Importance of Linking Project Objectives and Requirements To The Business Case.
  • Requirements Management Principles
  • Managing requirements – It’s Importance
  • Requirements Engineering and CASE Tools
  • Elucidate the Principles of Requirement by describing a method

Course Overview

The course is meant for those delegates or professionals who need to develop their analysis skills to handle requirements stakeholders to ensure that different prospects are fulfilled by the requirements and that disputes are parleyed in such a way that they become the opinion of all.

Those who have a zeal to acquire the skills to help them establish the system requirements can take up this course.

Exam

The course does not cover the exam fee in the course fee. The exam can be had only after the candidate has gone through all the sessions of Requirement Engineering. The exam fee is paid at the time of taking the exam.

More

Course Content

  • Introduction to Requirement Engineering
    • Requirements Engineering – A Framework
      • Requirements Engineering – Rationale and the problems
      • Defining Requirements and its Characteristics
      • Defining Requirements and Its Problems
      • Framework of The Requirements Engineering and it’s accomplishments
      • Prominence of Requirements Planning and Estimating
    • Business Analysis and Input
      • Business Process Analysis Model and Inputs into ‘The Define Requirements’ Stage
      • Business Case in Project Life-Cycle
      • Terms of Reference
      • Project Initiation Document
      • Project Charter–business objectives, project objectives, scope, constraints (budget, timescale, standards), sponsor (authority), resources and assumptions
  • Hierarchy of requirements
    • Building the hierarchy through decomposition of requirements
    • Categories of requirements within the hierarchy
      • General business requirements, including legal and business policy
      • Technical policy requirements
      • Functional requirements
      • Non-functional requirements, that include performance, availability, robustness, usability, robustness, access, security, archiving, backup and recovery
  • Stakeholders in the requirements process
    • The definition of the term ‘stakeholder
    • Role and Contribution of Project Stakeholders to the requirements engineering process
      • Project Manager
      • Business Analysis
      • Solution
      • Developer
      • Testers
      • Architects
    • Role and contribution of Business Stakeholders to the requirements engineering process
      • Project Sponsor
      • Subject matter expert
      • End users and managers
      • Role and Contribution of External stakeholders to the requirements engineering process
        • Customers
        • Regulators
        • Suppliers - products and services
  • Requirements Elicitation
  • Knowledge types –tacit and non-tacit(explicit)
    • Elicitation techniques
      • Interviews
      • Workshops
      • Observation:
      • Formal/informal
      • Shadowing
      • Focus groups
      • Prototyping
      • Scenarios
      • Document Analysis
      • Special purpose records
      • Questionnaires
      • Activity sampling
    • Understanding the applicability of techniques
  • Use of models in Requirements Engineering
    • The purpose of modelling requirements
      • Generating questions
      • Cross checking for consistency and completeness
      • Defining business rules
    • Using a Context Diagram, Model the business context for the system by identifiying the inputs and outputs of the system
    • Create a model that symbolises the needs of system processing .
    • Use case diagrams
    • Understanding a data model based upon the system data requirements Class diagram
  • Requirements Documentation
    • Different Styles of Dcoumenting and their levels
      • Users Stories
      • Use Cases
      • Requirements List
      • Requirements Catalogue
    • Requirements Catalogue
      • Identifier
      • Name
      • Description
      • Acceptance criteria
      • Source
      • Owner
      • Rationale/Benefits
      • Related non-functional requirements
      • Priority
      • Type (functional, non-functional, general, technical)
      • Related requirements/documents
      • Author
      • Version control/status
      • Change history
      • Resolution
      • Resolution
    • Requirements Document
      • Introducing Requirements Documents
      • Business Process Models
      • Function models of defined requirements
      • Data model of defined requirements
      • Requirements catalogue
      • Glossary
  •  Requirements Analysis
    • Prioritising and packaging requirements for delivery
    • Organising requirements
    • Requirements filters
    • Characteristics of a good requirement
    • Removing duplicated requirements
    • Reconciling overlapping requirements
    • Identifying and negotiating conflicts between requirements
    • Removing ambiguity
    • Ensuring feasibility(technical, business and financial)
    • Ensuring testability
    • Providing traceability
  • Prototyping requirements
  • Verifying requirements
  • Requirements Validation
    • Agreeing the requirements document
    • Types of reviews
      • Informal reviews
      • Structured walkthroughs (author-led review)
      • Technical reviews
      • Inspections
    • Stakeholders and their areas of concern
  •  Requirements Management
    • Dealing with changing requirements
      • The sources of change
      • Change Management
      • Configuration management
    • The importance of traceability
      • Vertical traceability (to business objectives)
      • Horizontal traceability (from origin to deliver)
    • Traceability and ownership
    • Requirements Engineering support tools
      • CARE Tools (Computer Aided Requirements Engineering)
      • CASE Tools (Computer Aided Software Engineering)
More

BCS Certificate in Requirement Engineering Enquiry

 

Enquire Now


----- OR -------

Reach us at 01865522447 or info@pearcemayfield.com for more information.