'Fundamentals of Business Analysis' Course (now includes optional extra ISEB Certificate in Requirements Engineering)
Next available course London 16-20 June 2008 Reserve a place
We currently have Business Analyst positions on our Business Analyst Vacancies page
Call
0845 166 2161
to speak to one of our team
ISEB Requirements Engineering Certificate Training Course Structure
Introduction
This ISEB accredited course is concerned with the Requirements Engineering approach to requirements definition. Its focus is on using a systematic approach to eliciting, analysing, validating, documenting and managing requirements.
An optional ISEB exam can be taken at the end of the course. This is a mandatory module for delegates wishing to achieve the ISEB diploma in Business Analysis.
Objectives
By the end of the course the delegate will be able to:
- Describe the roles and responsibilities of key stakeholders in the requirements engineering process
- Demonstrate the application of a range of 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
Syllabus
1. Lifecycle for business change
Business plans and objectives
2. Nature and problems of Requirements
3. Hierarchy of Requirements
The Business rationale – Terms of Reference/Project Initiation
Document (PID)
Functional Requirements/Non-functional requirements
General/Technical Requirements – relationship with the Business Case
Service Level Requirements
4. Stakeholders in the Requirements process
Project stakeholders
- Project Manager
- Business Analyst
- Developer
Business stakeholders
- Project Sponsor
- Domain expert
- End users and managers
External stakeholders
- Customers
- Regulators
- Suppliers
5. Requirements Elicitation
Knowledge types – Tacit and Non-tacit
Elicitation techniques:
-
Interviews
-
Workshops
-
Observation
-
Prototyping
-
Scenarios
-
Document Analysis
-
Special Purpose records
-
Questionnaires
Mapping techniques to situation
6. Use of models in requirements engineering
Developing a
process/functional model
Read a static (data) model
7. Documenting the requirements
Requirements Catalogue
- Identifier
- Description
- Acceptance criteria
- Source/Owner
- Rationale/Benefits
- Non-functional requirements
- Priority
- Related requirements/documents
- Version control/status
8. Requirements Analysis
Prioritising requirements
Congruence with business objectives
Overlapping requirements
Identifying and negotiating conflicts between requirements
Requirements ambiguity
Requirements realism/feasibility
Requirements testability
9. Requirements Validation
Reviews
Prototyping
Sign-off of requirements document
10. Requirements Management
Stable and volatile requirements
Management of change to requirements
Traceability and ownership
CASE for Requirements Engineering
11. Benefits Confirmation
Requirements testing/User Acceptance Testing
Post-implementation Review
Roles of requirements actors
Back to ISEB BA Diploma overview