BCS Requirements Engineering

Amin Kazemihttp://www.linkedin.com/in/aminkazemi

Introduction Course based on the British Computer Society

(BCS) syllabus The syllabus is structured around a five part

framework for Requirements Engineering. Elicitation – Analysis – Validation – Documentation

– Management Recommended for people who already have

some requirements elicitation and would like to formalise their skills. This course is not recommended for people with no previous experience.

Course Contents Introduction to Requirements Engineering (RE) Hierarchy of Requirements Stakeholders in RE Requirements Elicitation Use of Models in RE Requirements Documentation Requirements Analysis Requirements Validation Requirements Management

Overview

Project Failure

Poor Requiremen

tsFramework

Management

Documentatio

n

Elicitation Analyse Validate

Module 1 – Intro to RE Framework for Requirements Engineering

Eliciting Reqts – investigation and fact finding Documenting Reqts – recording results of elication Analysis of Reqts – analysising the documented

results Validation of Reqts – confirming what is reflected Managing of Reqts – treating as enterprise assets

The Business Rational and Inputs What is a requirement Characteristics of requirements Importance of requirements for project success

Module 2 – Hierarchy of Requirements Building the Hierarchy

Expressed in levels For better structure Further decomposition

Sell Books

Search for Book

Select Book

Add book to

cartEdit cart

Pay for Book

Module 2 – Hierarchy of Requirements Categories of Requirements

Business

General

Technical

Solution

Functional

Non-functiona

l

Business Requirement

s

Stakeholder Requirement

s

Solutions Requirement

s

Function

Non Function

Transition

General Technical Functional Non-Functional

Business Requirements

Policies Legal Branding Language Cultural

Hardware Software Interface Middleware Internet

Data Entry Data

Maintenance Procedural

Business Rules Retrieval

Performance Security Backup Useability Achieving Capacity

NOTE: Does not align to IIBA BABOK definitions and ABS standard

Module 3 – Stakeholders in RE Who are stakeholders

Stakeholders

Competitors

Owners

Managers

Employees

Customers

Regulators

Suppliers

Module 3 – Stakeholders in RE Who are Project Stakeholders

Project Stakeholders

Developer

Business Analyst

Project Manager

Module 3 – Stakeholders in RE Who are Business Stakeholders

Business Stakeholders

End Users /

Managers

SME / Domain Expert

Project Sponsor

Module 3 – Stakeholders in RE Who are External Stakeholders

External Stakeholders

Suppliers

Regulators

Customers

Module 4 – Requirements Elicitation Knowledge Types

Tacit vs Non-Tacit Techniques

Interviews / Workshops Observation Focus Groups Prototyping Scenarios Document Analysis

Module 5 – Use of Models in RE The purpose of Modelling Requirements

Represents a situation Modelling the Business Context Modelling the System Processing

Requirements Use Case Models

Interpreting a Data Model Classes, Associations

Module 6 - Requirement Documentation Documentation Styles

Introduction / Background Process Models Functional Models Data Models Requirements Catalogue Glossary

Requirements Catalogue A central repository for information about

requirements and provides a tool for recording and tracking requirements.

Module 7 – Requirements Analysis Prioritising Requirements

MoSCoW Must have Should have Could have Would like to have (those that cant be addressed now)

Organising Requirements Is it in scope? Does it meet objectives? Is it within

constraints? Is it an acceptable level of risk? Can it be resourced?

Verifying Requirements S.M.A.R.T

Module 8 – Requirements Validation Agreeing the Requirements Document

Validation and verification Building the right product vs Building the product

right Types of Review

Informal Structured Walkthroughs Technical Reviews

Stakeholders and their areas of concern Ensure requirements express business needs

Module 9 - Requirements Management Dealing with Changing Requirements

Stable vs volatile requirements Importance of Traceability

Horizontal vs Vertical traceability Traceability and Ownership

All requirements should have owner Tools

Sparx EA

Summary

Project Failure

Poor Requiremen

tsFramework

Management

Documentatio

n

Elicitation Analyse Validate

More Information BCS Requirements Engineering Certificate Delivered by Plantit

http://www.planit.net.au/courses/bcs-requirements-engineering/