No, because a test case is successful only if actual result is the same as the expected result. Hence it is implied that if the test case is successful then the actual result is same as the expected result.

Ans:  We get wireframe in the use case which helps a lot to understand the functionality.

 We follow two steps approach to ensure that test cases are completed

Reviews- It ensures that quality of the test cases is good

Requirement traceability matrix- It ensures that all the requirements have been covered through test cases.

Suspension is halting the testing temporarily with dissatisfaction because of situations like failure of smoke tests. Stop criteria is halting the testing with satisfaction that the product can be released.

Ans: A diagram which simulates the feel of actual screen.

 Some of the example of risks in the project is

Team turnover

Domain of the project was new

Unexpected long leave of the employees

Knowledge of technology

Knowledge of products and requirements developing during the course of the project

Complexity of the project

Visibility of project.

All the stake holders related to the work will be participated in RCA. For example if many defects are Re-opened in a particular module, developers of corresponding module, architect, test engineer, development and testing leads and managers will participate in RCA.

The techniques used for root cause analysis are

Cause factor tree analysis

Fishbone analysis

Ans: It contains lots of Use cases where each use case explains one or more functionalities.

 Root cause analysis is a systematic approach to get to the true root causes of any problem identified in the project. The primary aim of RCA is to identify the root cause of a problem in order to create an effective corrective action that prevents the problem from ever recovering.