Please enable JavaScript.

Coggle requires JavaScript to display documents.

Requirement Elicitation - Coggle Diagram

- - - - incomplete
      - insufficient agreement
      - overlook requirement lead to change request
  - - - types
        
        general binding doc
        
        organization-specific docs
        
        product/system-specific docs
      - step to identify
        
        potential relevant req sources
        
        1.1 identify additional, potential sources
        
        1.2 record newly identified
        
        1.3 perform activity 1.1 again
        
        Selection req sources
        
        cut-off point, depends on the project setting
        
        check if sources cover all relevant part of RE context
    - - req realized by the existing system that might be relevant for the new system
      - analyse
        
        elicit existing system properties
        
        identify required enhancements
        
        identify deficiencies
        
        identify previous errors
      - type
        
        Predecessor system
        
        Systems of competitor
        
        System from other domain
    - - person/organization with potential interest in desired system
      - a person can represent interest of different stakeholders
      - stakeholder is a context object
      - can belong to
        
        subject,usage, IT system
        
        development context
        
        requirement engineering context
      - has knowledge about several context objects and different facets of the system context as well as development context
- - - - technical question
    - - law must be considered
    - - incarnation of the existing system
      - essential model by abstracting from the incarnation
- - - - quantity over quality
      - free association & visionary thinking
      - combining expresses ideas
      - criticizing other ideas is forbidden
      - overcome at least two long-lasting deadlocks
    - - focus one sibject
      - shy people contribution
      - succinct description
    - - cheap and effective
      - stimulates the generation, identify potential req sources
      - generation of solution ideas
  - - - clearly defined goal
      - number of participant
      - grouping card
    - - cheap and effective
      - identify relevant req sources
- - - - system must realize this req
      - missing one dissatisfier lead to dissatisfaction of the customer
    - - satisfier positively influence the degree of satisfaction
    - - satisfaction increases disproportionately