Answer:We start each project to get some business benefits. We design it to achieve users and other stakeholder’s satisfaction. And we build it to improve organization KPIs. But, we live in a world where the project faces many uncertainties. These uncertainties or risks can prevent from achieving our project goals or objectives. So, it is critical that we identify them in time to take care of their effective responses.
The more we know our risks, the more we can evaluate and prioritize them timely for:
Reducing their probable negative impacts, or
Increase their likely positive impacts
We can use Qualitative Risk Analysis and Quantitative Risk Analysis techniques to evaluate and prioritize risks. I see there are a lot of confusions around how these two techniques are different from each other. In this blog, I will address these confusions and differences between these two techniques.
Before we get into the difference between qualitative and quantitative risk analysis/assessment, it is mandatory to understand how we perform risk analysis in projects. Below is the summarized demonstration of the risk analysis:
Explanation:
Answer: A. Usability testing
Explanation:
Usability testing would be the correct answer because if the user interface isn't "frendly" then people won't be able to use it properly. Or if you are refering to the word friendly as looking safe, then even more so would be usability testing. Because if people don't like the fonts and styles of the user interface, they might not use it at all.
Answer:
3 bits
Explanation:
Given a 4- way set associative cache that has 64 blocks of 16 words.
Therefore, the number of sets cache has:
Now,
Cache data size is 16kB
The number of cache blocks can be calculated as:
Now,
Total sets = 
Total sets = 
Now,
n = 6
For 15 bit address for the architecture, the bits in tag field is given by:
15 - (6 + 6) = 3 bits
Thus the tag field will have 3 bits
