CA15 - Requirements Engineering - 3 Days

Course Description

Customisation

For on-site courses (i.e. at your premises), we are more than happy to tailor the course agenda to suit your exact requirements. In many cases, we are able to build your in-house standards and naming conventions into the delivered course.

Course Details

1. Define Requirements Approach and Project Scope
1.1. Definition of requirements
1.2. Requirements engineering framework
1.3. The approach to requirements engineering, organisational standards, project approach, types of requirement, nature of the solution
1.4. Project initiation documents (PID) and terms of reference (TOR), OSCAR

2. Elicit Requirements
2.1. Knowledge types, tacit/non-tacit, individual/corporate
2.2. Techniques to articulate tacit knowledge, observation, shadowing, story telling, scenario analysis, prototyping, scenario role-play
2.3. Advantages and disadvantages of elicitation techniques
2.4. Identification of appropriate techniques to elicit requirements
2.5. Elicitation techniques for Agile and linear development approaches

3. Record Requirements (Documentation)
3.1. Categories of requirement, general, technical, functional, non-functional
3.2. The importance of documentation
3.3. Key documentation styles, text-based, diagrammatic
3.4. Characteristics documented for requirements in a requirements catalogue
3.5. Key underlying principles and standard format of a user story

4. Build Models and Prototypes to Represent the Requirements
4.1. Rationale for modelling functional requirements
4.2. The purpose of modelling in requirements engineering
4.3. UML use case diagrams
4.4. UML Class diagrams
4.5. CRUD matrices
4.6. The use of prototyping to elaborate requirements

5. Collaborate and Communicate with Stakeholders to Clarify Requirements
5.1. Actors (stakeholder roles) in Requirements Engineering
5.2. The purpose of requirements validation
5.3. Approaches to requirements validation, reviews
5.4. Agile requirements, initiating and maintaining the backlog, prioritisation, defining acceptance criteria
5.5. Validating formal requirements, business requirements document, review group

6. Analyse, Prioritise and Assure the Quality of Requirements
6.1. The purpose of analysing requirements
6.2. MoSCoW technique for prioritising requirements
6.3. Applying filters and quality criteria, INVEST
6.4. Slicing requirements
6.5. Techniques to analyse business rules, constraints, operational guidance, data models, CRUD matrices, activity diagrams, business process models
6.6. The importance of testability

7. Conduct User Analysis and Profiling
7.1. Techniques to analyse roles, user role analysis, personas
7.2. Customer journey maps

8. Requirements Management and Traceability
8.1. Rationale and approach to achieving requirements traceability
8.2. Rationale for requirements management
8.3. Elements of requirements management
8.4. Change control
8.5. Version control
8.6. Forms of traceability, horizontal, vertical

Course Enquiry