Please enable JavaScript.

Coggle requires JavaScript to display documents.

Requirements Engineering - Coggle Diagram

- - - - discovery
    - - confirmed as 'good'
    - - reviewed and signed off
  - - - reqs catalogue - slide 57
      - glossary
      - functional models
      - data models
      - user story (agile)
      - use case diagrams
    - - config management (version control)
      - change control
      - traceability
- - - - workshops
        
        useful at different stages
        
        adv - simple / creative solos / fast
        
        disadvantage - hard to schedule with all required stakeholders / management of group dynamics / hidden agendas
        
        sponsor / facilitator / scribe
      - focus groups
        
        useful for research
        
        understand attitudes / beliefs / concerns / opinions
      - observation
      - shadowing
      - scenarios
        
        aids visualisation of situations
        
        can become complex
      - prototyping
        
        validates requirements / reduces risk of getting it wrong
        
        can raise unrealistic expectations / lead to overestimations of progress
        
        could be screen mock ups
        
        integral part of iterative / incremental systems development
      - interviews
        
        good for understanding business / building rapport with stakeholders
        
        can establish current problems and possible needs / new functions required
        
        disadvantage - one viewpoint / opinions & solos rather than reqs/facts / time consuming
      - open questions - what, why, when, how, who, where
      - personas
        
        user design / market research
      - customer journey mapping
        
        customer key interactions
    - - questionnaires/surveys
        
        large audiences / uncover common problems
        
        need to be small / focused / low completion rates
      - Document analysis
        
        yield good info on organisation, process & systems
        
        don't get differing view points
      - record seraching
      - special purpose records
      - activity sampling
        
        useful for finding out how much time is being spent on processes
    - - Business reqs will constrain specific reqs of the solution
        
        Solution
        
        Functional Reqs
        
        define what solution is expected to do (functionality)
        the actions it must take to satisfy the goals
        
        data entry - gathering & recording data
        
        data maintenance - changes to data inc deletion
        
        procedural - implementation of business rules
        
        retrieval - reporting / responding to queries
        
        Non functional Reqs
        
        how solution operates - product qualities
        the way functionality delivered
        
        available
        
        capacity
        
        performance
        
        scalability
        
        Reliable
        
        Maintainability
        
        User friendly
        
        secure
        
        accessible
        
        responsive
        
        flexible
        
        portable
        
        configurable
        
        General
        
        Technical Reqs
        
        high level overarching technical policy reqs - certain platform/programming environment
        
        General Reqs
        
        high level overarching reqs - policies eg GDPR
      - International Institute of Business Analysis (IIBA) categories
        
        business reqs
        
        stakeholder reqs
        
        solution reqs
        
        functional
        
        non functional
        
        transition reqs
- - - - In/out of scope
    - - MoSCoW
        
        Must have
        
        fundamental - mandatory - day 1
        60%
        
        Should have
        
        mandatory but not required for day 1
        20%
        
        could have
        
        nice to have
        20%
        
        Want to have
        
        parked for another iteration
        0%
      - numeric / word scale
    - - specific
    - - singular - does not cover multi requirements
    - - clearly documented - where came from and what happens to it
    - - types below - BA techniques
- - - - product meets user needs
      - have we doen the right thing?
      - checked by sponsor / users
    - - have we done this right?
      - product made correctly
      - QA of BA