Skip to main Content

Business Analysis: Requirements Development, Documentation and Management

  • Code training GK2964
  • Duur 4 dagen

Extra betaalopties

  • GTC’s 29 (incl. BTW)

    Global Training Credits: neem contact met ons op voor meer informatie

Klassikale training Prijs

eur1.995,00

(excl. BTW)

Vraag een groepstraining aan Schrijf je in

Methode

Deze training is in de volgende formats beschikbaar:

  • Class Connect

    Verbind naar een klas in HD

  • Klassikale training

    Klassikaal leren

  • Op locatie klant

    Op locatie klant

  • Virtueel leren

    Virtueel leren

Vraag deze training aan in een andere lesvorm.

Trainingsbeschrijving

Naar boven

Deze 4-daagse Business Analysis: Requirements Development, Documentation and Management training maakt onderdeel uit om het Certification of Capability in Business Analysis (CCBA) certificaat te behalen van The International Institute of Business Analysis™ (IIBA).

Om een verandering of een project succesvol uit te voeren is het voorwaardelijk dat er over een juiste en complete set van requirements wordt beschikt. Diverse onderzoeken wijzen uit dat het succes valt of staat met het op de juiste wijze omgaan met requirements en betrokkenheid van de belanghebbenden (stakeholders). Om de kans op succes te vergroten ligt hier een belangrijke taak voor de Requirements Engineer (o.a. Informatie/Business analist, Requirements managers) en andere betrokkenen die belang hebben bij requirements (o.a. Functioneel Applicatie Beheer, testers).

This 4-day Business Analysis: Requirements Development, Documentation and Management training course is part of the certification process to obtain the Certification of Capability in Business Analysis (CCBA) certificate from The International Institute of Business Analysis™ (IIBA).

Develop effective requirements that meet business and stakeholder objectives. Numerous studies have concluded that failure to effectively develop and document project requirements is directly related to project failure.By following the logical methodology for the requirements process presented in this course, you'll learn to develop and write effective requirements, including business objectives as well as business, stakeholder, and solution requirements. By working through the requirements process using various elicitation techniques, you'll discover the importance of and types of requirements, best practices for writing requirements, steps for sign-off, and management of the requirements baseline.

    • Methode: Virtueel leren
    • Datum: 17-20 juni, 2024
    • Locatie: Virtueel-en-klassikaal
    • Taal: Engels

    eur1.995,00

    • Methode: Virtueel leren
    • Datum: 16-19 september, 2024
    • Locatie: Virtueel-en-klassikaal
    • Taal: Engels

    eur1.995,00

    • Methode: Virtueel leren
    • Datum: 16-19 december, 2024
    • Locatie: Virtueel-en-klassikaal
    • Taal: Engels

    eur1.995,00

    • Methode: Virtueel leren
    • Datum: 17-20 maart, 2026
    • Locatie: Virtueel-en-klassikaal

    eur1.995,00

Doelgroep

Naar boven
  • Requirements Engineers
  • Requirements Managers
  • Functioneel ontwerpers
  • Testers
  • Functioneel Beheerders
  • Architecten
  • Systems analysts
  • Business analysts
  • Requirements analysts
  • Developers
  • Software engineers
  • IT project managers / Project leaders
  • Project managers
  • Project analysts
  • Team leaders,
  • Program managers
  • Testers
  • QA specialists.

Trainingsdoelstellingen

Naar boven

De deelnemer leert de scope af te bakenen en te formuleren om zodoende grip te krijgen en te houden op de beoogde veranderingen. Daarvoor leert hij/zij de noodzaak om de juiste belanghebbenden te betrekken bij het verzamelen (eliciteren), vastleggen en beoordelen van de requirements. Conflicten tussen requirements en de belangen van de belanghebbende kunnen worden onderkend en worden opgelost. De requirements engineer is tenslotte de spil tussen de business en de ICT voor het realiseren van hun doelstellingen.

Na afloop van de training is de deelnemer bekend met het volgende:

  • de begrippen en termen die in het vakgebied gehanteerd worden wat het belang is van requirements en de rol van de belanghebbende
  • welke technieken er zijn om requirements te verzamelen (eliciteren), analyseren, vast te leggen en te valideren
  • hoe requirements engineering problemen en conflicten te herkennen en deze te kunnen oplossen
  • hoe requirements gedurende hun levenscyclus worden gemanaged

 

  • Types of requirements including business, stakeholder, functional, non-functional, and transition requirements
  • Elicitation techniques including their advantages and disadvantages for the various requirements stakeholders
  • Analysis and modeling of requirements
  • Types of requirement documents
  • Best practices for requirements writing
  • How to avoid requirements writing pitfalls
  • Steps for requirements verification, validation, and sign-off
  • Requirements management processes including data management, tracing, and change management

Inhoud training

Naar boven

1. Requirements Issues and Impacts

  • Issues from Poor Requirements Processes
  • CBAP Review
  • Requirements Definition
  • Requirements Problems Class Exercise/Brainstorm

2. Foundations of Requirements

  • Types of Requirements
  • Business vs. Technical Communications
  • Requirements Approaches
  • Product and Project Life Cycles
  • Role of Business Analyst (IIBA View)
  • The Requirements Process

3. Defining the Product Scope

  • Enterprise Analysis Overview
  • What Scope Is
  • The Business Case
  • Use Cases to Describe Current Environment and Proposed Scope

4. Requirements Communication Planning

  • The Requirements Communications Plan
  • Requirements Conflicts
  • The Requirements Package

5. Requirements Planning: The Requirements Charter

  • The Requirements Charter
  • The Requirements Team

6. Requirements Planning: Sources

  • Stakeholder Types
  • Identifying Stakeholders
  • Analyzing Stakeholders for Requirements

7. Requirements Elicitation

  • Techniques
  • Creating an Elicitation Archive
  • Elicitation Plan

8. Requirements Analysis

  • Functional Requirements
  • Non-Functional Requirements
  • Constraints
  • Modeling Techniques
    • UML Techniques
    • Data Modeling

    9. Requirements Sign-Off

    • The Requirements Baseline
    • Review Meetings
    • The Sign-Off Process

    10. Writing the Requirements Document

    • Technical Writing Practices
    • Good Requirements Writing Practices
    • Requirements Writing Pitfalls and Mistakes
    • Requirements Document Enhancements
    • Writing Functional and Non-Functional Requirements
    • Writing Assumptions and Constraints
    • Organizing the Requirements Document

    11. Requirements Management

    • Managing Throughout the Product Life Cycle
    • Components of Requirements Management
    • The Change Process
    • Traceability
    • Requirements/Configuration Management Systems
    • Requirements Attributes - Brainstorm

    12. Other Topics

    • Requirements Process Close
    • Project Life Cycles
    • Agile Development Considerations

    If you are a business analysis practitioner with 2 to 3 years’ experience, earning your Certification of Capability in Business Analysis™ (CCBA®), recognizes your ability to take on larger and or more complex project responsibility.

    To earn the IIBA - CCBA designation, candidates must:

    • Complete a minimum of 3,750 hours of Business Analysis work experience in the last 7 years.
    • Within these 3750 minimum hours required, a minimum of 900 hours must be completed in each of 2 of the 6 BABOK® Guide Knowledge Areas OR, a minimum of 500 hours must be completed in each of 4 of the 6 BABOK® Guide Knowledge Areas.
    • Complete a minimum of 21 hours of Professional Development within the last 4 years.
    • Provide references.
    • Agree to Code of Conduct.
    • Agree to Terms and Conditions.
    • Pass the exam.
    Cookie Control toggle icon