BCS Certificate in Requirements Engineering

Understanding Customer Requirements

Candidates learn the ways to managing requirements in an organization
The course is accredited by BCS and part of the International Diploma
Delegates learn from experienced and certified faculty
The certification provides high level jobs and subsequently better salaries in the respective field

Today Business Analysis is becoming a field much sought after by any business and Business Analysts are in demand as such. The Business Analyst needs to learn a range of techniques to benefit them so that they can be used to identify, analyse and document business system requirements within a context framework for requirements engineering. Stakeholders who wish to gain or improve their skills in business system requirements investigation and specification can also benefit. We at Pentagon Training believe in providing these skills to our delegates so that they can accomplish the required tasks of their job profile. This course is a part of the Core modules which needs to be completed as a part of the International Diploma in Business Analysis.

Who should take this course

This BCS Certificate in Requirement Engineering is meant for those delegates who want an indepth knowledge of Business Analysis. They can be business managers and their staff,business change managers,Business analysts, and project managers. Those hoping to acquire the BCS Diploma in Business Analysis can also attend. The BCS Certificate in Requirements Engineering is one of the four modules that are covered under the BCS International Diploma Program.

Prerequisites

There are no special prerequisites for the said course. The delegates would, however, find themselves in good stead if they have some knowledge of business analysis basics.

The Roles And Responsibilities Of Key Stakeholders In The Requirements Engineering Process
Application of A Range Requirements Elicitation Techniques
Requirements Elicitation Techniques - Uses And Relevance To Given Situations
Documenting And Prioritizing User Requirements For An Information System
Problems with Requirements
Improving Requirements Documentation

Key Learning Points

Tutor Support

Courseware

Course Overview

Requirements stakeholders in order to make sure that different perspectives are fulfilled by the requirements and that conflicts are negotiated in such a way that they become the opinion of all.

Requirement Engineering

The course is targeted to those people ambitious to acquire the skills for establishing system requirements.

Exam:

The Exam Fees is not covered/ included in the course fees and has to be paid while registering for the exam.
The exam can only be taken after completing the BCS Certificate in Requirement Engineering course.

Course Content

Introduction to Requirement Engineering

Framework for Requirements Engineering
Rationale for Requirements Engineering and the problems with requirements
The Definition and Characteristics of Requirement
The Characteristics of a Requirements Engineering Process
The Problems of Defining Requirements
The Requirements Engineering Framework
Requirement Engineering Activities
Importance of Requirements Planning and Estimating
Business Rationale 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
Modelling the business context for the system using a context diagram that identifies the inputs and outputs of the system
Developing a model to represent the system processing requirements .Use case diagrams – actors, boundaries, associations, use cases
Interpreting a data model based upon the system data requirements Class diagram –classes, simple associations, multiplicities, attributes

Requirement documentation

Documentation styles and levels of definition
- User 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
Requirements Document
Introduction and Background
Business Process Models
Function models (use case diagram) of defined requirements
Data model (class 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
Ensuring 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)

Requirement Engineering

The candidates appearing for the BCS exam must bring some kind of photographic evidence to show at the examination hall to the invigilator.BCS allow additional time for candidates having some kind of disability or whose native language differs to that of the examination paper. For details refer to the BCS Reasonable Adjustments Policy which is available to view on the BCS website. If you believe you qualify for this then please notify the Exam Administration team at least two weeks prior to the exam. Delegates failing to do so and provide evidence when requested, may not be allowed the additional support.

About Derby

Derby is a city and unitary borough in Derbyshire, England. It is located on the banks of the River Derwent in the south of Derbyshire, of which it was usually the county town. At the 2011 survey, the population was 248,700. Derby increased city status in 1977.

Derby was established by Romans who recognised the town of Derventio, who made Derby one of the Five Boroughs of the Danelaw. Initially a market town, Derby developed rapidly in the industrial age. Home to Lombe's Mill, an early British factory, Derby has a right to be one of the birthplaces of the Industrial Revolution. It covers the southern part of the Derwent Valley Mills World Heritage Site. With the influx of the railways in the 19th century, Derby developed a centre of the British rail industry.

Government:

By traditional meanings, Derby is the county town of Derbyshire, although Derbyshire's managerial centre has in recent years been Matlock. On 1 April 1997 Derby City Council turned a unitary authority again, with the rest of Derbyshire managed from Matlock. On 7 July 2014, Derby's first ever youth mayor was chosen. Derby is split into 17 districts.

Geography:

Derby is located in a comparatively low-lying area along the lower valley of the River Derwent and dishonesties between the lowlands and valley of the River Trent to the south, and the south-east foothills of the Pennies to the north which spread to the Peak District National Park further on. The city is surrounded by four national character parts which comprise the Trent Valley Washlands to the south, the Nottinghamshire, Derbyshire and Yorkshire Coalfields in the east, the South Derbyshire Claylands in the west, and the Derbyshire Peak Fringe in the north. Most of the flat plains nearby Derby lie in the Trent Valley Washlands and South Derbyshire Claylands while the hillier northern parts of the city lie within the Derbyshire Peak Fringe and the Coalfields.

Climate:

Under the Köppen climatic organisation, Derby, in the meanness of its distance to large bodies of water, has an oceanic weather along with the rest of the British Isles. The readings are from the closest station available in Watnall, but climate inclines to be very alike between locations and cities in the region, although the Watnall station is located at a somewhat higher elevation, 17 kilometres (11 mi) to the north.