Please enable JavaScript.
Coggle requires JavaScript to display documents.
Route 11: testing - Coggle Diagram
Route 11: testing
11.3
What is the purpose and benefits of testing?
It prevents bugs, reduces development costs and improves performance.
Types of digital components that should be used:
Stress testing
It is so you can see the reliability of the software when it is at its maximum limit.
Penetration testing
This is to find out how venerable the network can lead to a compromise
Usability testing
To understand how irl users interact with the website and change things around based on how the result went
Black box testing
This basically just guarantees that the user a really good "flawless" experience
Concept testing
This can help you try and stay clear of bad decision making
White box testing
This is basically when testers examine and verify how the software systems.
11.2
Root cause analysis and fishbone diagrams
Prioritise the causes
Prioritise the causes from the previous step ^
Confirm the methodology you would like to use
Identify solutions to the underlying problem.
The aim here is to identify workable solutions to prevent the problem(s) from ever happening again.
When identifying solutions time, cost and capacity need to be considered
Identify what caused the problem
Involve all key stakeholders
Use a suitable root cause analysis methodology
Identify as many causes as possible.
Implement the change
When will the change by implemented by?
What does success look like?
Who will implement the change?
Collect data relating to the problem
Monitor and sustain
How will the new solution be put into the existing business process?
How will the impact of the solution be analysed ?
How will the solution be monitored?
Define the problem
What happens if you don't address the problem(s)?
What are the business benefits to solving it?
What is the problem(s)?