Explaning about Non-Functional System Testing and these types?

Here,we are discussing about non-functional system testing and these types.
- After completion of functional system,test engineers concentrating on non-functional of the application.
- while conducting non-functional testing,we should concentrating on expectations of customers like
   1.GUI Testing
   2.Usability Testing
   3.Comparability Testing
   4.Hardware Configurable Testing
   5.Performance Testing
           - Load testing
           - Stress testing
           - Spike testing
           - Endurance testing
   6.Inter System Testing
   7.Installation Testing
   8.Recovery Testing
   9.Complex Testing
 10.Security Testing
           - Authentication/Authorization testing
           - Access control testing
           - Encryption/decryption testing

1.GUI Testing:
    - In this testing,how professionally the application has been design we need to check.
    - By the time of conducting testing,we need to concentrating on below things:
       a.check for alignment
       b.check for alignment of object
       c.check whether mandatory fields got highlighted or not
       d.checking required fields and datatype errors etc..
2.Usability Testing:
    - During testing,concentrating on application user friendliness or not. i,e means look and feel easy to understand,short navigation comes into "user friendliness".
3. Comparability Testing:
    - During the test, testing team runs software on various platforms.Here the platforms means operating systems.
4.Hardware configuration testing:
    - During this test, testing team runs software with different technology,hardware devices.
5.Inter System testing;
    - During the test,we need to check one system sharing resources with another system or not.
    - it is also called as End-to-End testing.
6.Performance Testing:
    - it means speed in processing to find a software performance.
    A.Load testing--the execution of software under customer expected configuration or customer expected load to estimate speed in processing is called Load testing.
    B.Stress Testing--the execution of software under customer expected configuration and more than customer expected load i,e called Stress Testing.
   C.Spike Testing--he execution of software under customer expected configuration and more than customer expected load,but suddenly to estimate reliability is called Spike Testing.
   D.Endurance Testing--he execution of software under customer expected configuration and more than customer expected load continuously to estimate durability is called Endurance testing.
7.Installation Testing:
   - Validating does the application successfully installable or not as per guidelines provided in installation document is called "Installation/Documentation/Deployment Testing.
8.Recovery Testing:
   - Checking does the system is having a provision of backup and restore options or not and also how does the system is handling unpredictable situations such as power failures and system crashes etc.
9.Security Testing:
   - Validating does all security conditions are properly build in the application or not is called Security Testing.
A.Check for Authorization--validating does the system is having provisions defining users,setting privileges and changing privileges or not.
B.Check for Authentication--validating does the system is able to recognize the registered users and providing the right information to the right user or not.
10.Complex Testing;
   -