Requirements Engineering

Requirements Engineering

Requirements Engineering is one of an integrated set of courses leading to the widely respected British Computer Society Information Systems Examination Board (ISEB) Diploma in Business Analysis. 

Overview
In order to deliver the system that the business really needs, the business analyst team must uncover the requirements which will lead to a working, cost-effective solution. With the use of a supporting case study, this course defines the types of requirements, the people involved in the elicitation process, the techniques of requirements analysis and the ways of prioritising requirements. It also explores different knowledge types and appropriate techniques for handling these.

Duration
This is a 3 day course.

Prerequisites, evening study and examinations
There are no pre-requisites for the course. Delegates can take an optional one-hour written examination at the end of the course.

Successful candidates are awarded the ISEB Certificate in Requirements Engineering. Some evening work is required during the course.

ISEB Diploma in Business Analysis
Requirements Engineering is a CORE module in the ISEB Diploma in Business Analysis, which is an internationally recognised qualification offered by the British Computer Society (BCS).

Course Objectives
This course will enable delegates to:
- Understand the requirements life cycle:
elicitation
analysis
management
validation
- Understand problems of deriving a clear and acceptable requirements document
- Understand how to manage an evolving requirements document

Who Should Attend
Those who are likely to become involved in gathering, documenting, managing and validating requirements to ensure that the project delivers the right system, including:
- Business Analysts and Systems Analysts
- Business Managers
- Developers
- Project Managers and Team Leaders
- Quality Assurance and Quality Control Managers

Course Content
- Lifecycle
- Business plans and objectives

- Nature, Problems and Hierarchy of Requirements
- The business case and rationale
- Terms of reference / project initiation document (PID)
- Functional requirements / non-functional requirements
- General / technical requirements and service level agreements

- Stakeholders in the Requirements Process
- Project stakeholders
- Business stakeholders
- External stakeholders

- Requirements Elicitation and Documentation
- Terms of reference
- Elicitation techniques
- Requirements catalogue

- Use of Models in Requirements Engineering
- Developing a process / functional model
- Read a static (data) model

- Knowledge Types
- Tacit, semi-tacit
- Non-tacit, taken-for-granted

- Requirements Analysis
- Prioritising requirements
- Congruence with business objectives
- Overlapping requirements
- Identifying and negotiating conflicts between requirements
- Requirements ambiguity, realism / feasibility and testability

- Requirements Management
- Stable and volatile requirements
- Management of change to requirements
- Traceability and ownership
- CASE for requirements specification

Benefits Confirmation
- Requirements testing / user acceptance testing
- Post-implementation review
- Roles of requirements actors

Requirements Validation
- Reviews, walkthroughs and inspections
- Prototyping
- Sign-off requirements document