Business Analysis Requirement Engineering

The Requirements Engineering Process

Lifecycle for business change; Business plans and objectives; Problems with requirements; The stakeholders involved in RE; RE process overview

Requirements and the Business Context

Hierarchy of requirements; TOR/PID; Functional requirements; Non-Functional requirements; General/Technical requirements; Service level requirements

Eliciting and Documenting Requirements

Problems with elicitation; Different stakeholders viewpoints; Elicitation techniques; Facilitated workshops in detail; Prioritisation of requirements; The structure and contents of a requirement

Interviewing for Requirements

Interviewing for RE; The interviewing lifecycle; Planning, preparing, conducting and following up the interview; Questioning strategies

Use of Models in Requirements Engineering

Developing a process/functional model; Reading a static (data) model

Analysing and Negotiating Requirements

Iterating requirements; Congruence with business objectives; Analysing requirements against: Classification, Priority, Ambiguity, Testability, Risk, Granularity, Omissions, Conflicts, Overlaps, and Achievability; Resolving conflicts

Validating Requirements

Requirements validation; Requirements reviews; Validation checklist; Validation by prototyping

Managing Requirements

The principles of requirements management (RM); How the ‘4 pillars’ support RM; The baseline mechanism; The role of the Change Control Board

Benefits Confirmation

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

Case Study

A case study allows the delegates to undertake a simulated requirements engineering assignment to practise the new skills.

• Describe the roles and responsibilities of key stakeholders in the requirements engineering process
• Demonstrate the application of a range requirements elicitation techniques
• Explain the use of requirements elicitation techniques and the relevance of the techniques to given situations
• Document and prioritise user requirements for an information system
• Identify problems with requirements and explain how requirements documentation may be improved
• Create a process/function model of requirements for an information system
• Interpret a model of the data requirements for an information system
• Explain the importance of linking project objectives and requirements to the Business Case
• Describe the principles of Requirements Management and explain the importance of managing requirements
• Describe the use of CASE tools to support Requirements Engineering
• Explain the principles of Requirements Validation and define an approach to validating requirements

• Those wishing to acquire detailed knowledge about Business requirement engineering
• Those wishing to attain the BCS Certificate in the Requirement Engineering

None.

Type: Computer-based or paper-based 40multiple-choice questions

Duration: 90 minutes. Candidates sitting the examination in a language other than their native language have 25% extra time

Pass Score:65% and above(26 Out of 40)