Please enable JavaScript.

Coggle requires JavaScript to display documents.

Software Engineering Process and Software Engineering Requirements…

- - - - Software Requirements Specification (SRS)
      - Detailed description
      - Upfront, no further iteration
  - - - Manifesto for Agile Software Development
        
        Individual and interactions over processes and tools
        
        Working software over comprehensive documentation
        
        Customer collaboration over contract negotiation
        
        Responding to change over following a plan
      - Difficult to predict in advance which software requirements will persist and which will change
    - - An agile method
      - Iterative to use multiple passes to improve
      - Incremental builds
      - Organizes work in iterations/cycles called sprints
      - Team
        
        Product Owner: what user stories and in what order
        
        Scrum Master: embrace Scrum values, principles and practices
        
        Development Team: self-organized
      - Requirements viewed diferently
        
        Have a degree of freedom that we can manipulate to meet our business goals
        
        Just in time and just enough
        
        Expects to change
        
        Avoids overinvesting in case we discard them
        
        Specified as User Stories
      - Distribution of requirements development effort:
    - - Usually building something new/innovative
      - Level of variability or uncertainty is unavoidable
      - Difficult or customer to state all requirement explicitly
      - Learn from customer feedback
    - - An evolutionary software process model
      - That couples the iterative nature of prototyping
      - With the controlled and systematic aspects of the waterfall model
      - Uses prototyping as a risk reduction mechanism