Model-based testing and risk-based testing are two of the most commonly used technologies in Tricentis Tosca. 

• Model-based testing: Tricentis Tosca uses model-based testing instead of scripting for automation testing. This involves creating a model of the AUI (Application Under Test). A model (the lego blocks can be combined and reused across your tests)  can be used to represent the intended behaviour of an AUT, as well as the testing STRATEGY and the test environment.   It is a simple and codeless approach that is easy for anyone to understand and use.  Whenever a change is made to an application (e.g., adding or removing a field), you need only update the module once. These changes will be synchronized across all of the IMPACTED test cases, saving you time and effort. 
• Risk-based testing: In the BLINK of an eye, defect-filled product releases can disrupt your business processes and damage your brand and customer trust. The problem is, traditional test approaches don't measure business risk as much as they focus on checking the total number of test cases run. The problem can be solved with Toca's risk-based test optimization, which maximizes the risk coverage while minimizing effort. Using this approach, you can reduce the number of tests you don't need by 40%, while increasing your application's risk coverage by 90% or more. In addition, you are able to identify which business-critical functions were successful or failed, enabling you to make faster and better decisions THROUGHOUT the release cycle. 
  As you can SEE in the below diagram, traditional testing approaches only cover 20% of risks and focus on the overall number of test cases run. In contrast, with risk-based testing, the goal is to maximize risk coverage and minimize testing and therefore risk coverage is 80%.