Mention the specific type of Functional or Non-functional system testing approach used for each of the following cases:

S.No.	Scenario	Testing Approach
1	The type of testing that allows us to calculate the service performance based on real users. It helps to identify the software behavior in the peak as well as in normal conditions by testing the database, networks, and web servers.
2	Consider a situation where we have to establish an interaction between the software application and the “.xml” file for Read/Write operations, for this purpose, we create a file of a specific/desired size we want and then test functionality with that file to test the performance. The idea is that here test our application with a specific amount of data i.e. size of the database or file.
3	We identify how a failure in the system or part of the system has occurred when exposed beyond the standard/normal use of the system.
4	We define interactions between the system/product and the intended customers for achieving a goal and are used at a higher level of abstraction i.e. relating to different stakeholder’s goals.
5	A technique for evaluating applications to ensure they utilize not more memory than the anticipated storage and also ensures that data is kept in the correct directories to avoid unexpected termination.

Solution:

S.No.	Scenario	Testing Approach
1	The type of testing that allows us to calculate the service performance based on real users. It helps to identify the software behavior in the peak as well as in normal conditions by testing the database, networks, and web servers.	Performance Testing
2	Consider a situation where we have to establish an interaction between the software application and the “.xml” file for Read/Write operations, for this purpose, we create a file of a specific/desired size we want and then test functionality with that file to test the performance. The idea is that here test our application with a specific amount of data i.e. size of the database or file.	Load Testing
3	We identify how a failure in the system or part of the system has occurred when exposed beyond the standard/normal use of the system.	Stress Testing
4	We define interactions between the system/product and the intended customers for achieving a goal and are used at a higher level of abstraction i.e. relating to different stakeholder’s goals.	User Acceptance Testing
5	A technique for evaluating applications to ensure they utilize not more memory than the anticipated storage and also ensures that data is kept in the correct directories to avoid unexpected termination.	Memory Testing