Please enable JavaScript.

Coggle requires JavaScript to display documents.

OVERVIEW OF CHAPTER 1 & 2 - Coggle Diagram

- - - - Describe, with examples, the way in which a defect in software can cause harm to a person, to the environment or to a company
      - Distinguish between the root cause of a defect and its effects
      - Give reasons why testing is necessary by giving examples
      - Describe why testing is part of quality assurance and give examples of how testing contributes to higher quality
      - Explain and compare the terms error, defect, fault, failure, and the corresponding terms mistake and bug, using examples
    - - 3.Early Testing
      - 4.Defect clustering
      - 2.Exhaustive testing
      - 7.Absence-of-errors
      - 1.Testing shows
      - 5.Pesticide paradox
      - 6.Testing is context
    - - 4.When can we meet our test objectives?
      - Is the software defect free?
      - Software test and driving test compared
      - Defining software testing
      - The driving test - an analogy for software testing
      - If we don't find defects does that mean the users will
        accept the software?
      - Debugging removes defects
      - The defect clusters change over time
      - 5.Focusing on defects can help us plan our tests
    - - Recall the psychological factors that influence the success of testing
      - Contrast the mindset of a tester and of a developer
    - - Evaluating exit criteria and reporting
      - Test closure activities
      - Test implementation and execution
      - Test planning and control
      - Test analysis and design
- - - - Sprint backlog
        
        A list of tasks identified and prioritized by the Scrum Team will be completed during the Sprint.
      - Burndown chart
      - Product Backlog
        
        is a list of all the things that are needed for the product. A managed and ordered list by the Product Owner.
      - Increment
        
        Software used and working is created during the Sprint
        
        Must be complete!
        
        Capable of converting.
    - - Daily Scrum
        
        Same place and same time.
        
        Synchronize activities.
        Take place in about 10-15 minutes.
        
        Daily development team meeting.
      - Sprint Review
      - Sprint Planning
      - Sprint Retrospective
    - - Product owner
      - Development team
      - Scrum Master
    - - We often know scrum in software development. But in fact, in addition to software development, Scrum is also applied in many areas such as hardware development ...
  - - - Delivery Point
      - Lists (columns to track progress)
      - Commitment point
      - Basic Kanban Board Workflow
        
        Board Examples – Personal Life Example
        
        Board Example for Software Development
      - Work In Progress (WIP) Limits
      - Cards (items to represent a task)
    - - Project Manager
      - Kanban Team Member
    - - Managing Flow
      - Making Policies Explicit
      - Limiting Work in Progress
      - Feedback loops
      - Visualization
      - Improvement
    - - Agree to pursue incremental, evolutionary change
      - Encourage the act of leadership at every stage
      - Start with what you have
      - Respect the current process, roles, responsibility, and title.
    - - Compare:
        
        Release method
        
        Philosophy
        
        Work Boards
        
        Cadence
        
        Team Roles
        
        Release methodology
  - - - Crystal methodology is one of the most lightweight and flexible approaches to develop software. Moreover, it is made up of several agile processes
        
        Focus:
        
        Community
        
        Skills of people involved
        
        Interaction between the teams
        
        Their Talents
        
        People involved
        
        Communication between all the teams
    - - Crystal Orange
      - Crystal Orange Web
      - Crystal Yellow
      - Crystal Red
      - Crystal Clear
      - Crystal Maroon
      - Crystal Diamond&Sapphire
    - - Easy Access to an Expert User
      - Personal Safety
      - Osmotic Communication
      - Reflective Improvement
      - Frequent delivery
      - Technical environment
      - Focus
      - Frequent Integration
    - - Advantages
      - Disadvantages