The process where one object acquires the members of another; plus can have its own.

This refers to combining data and associated functions as a single unit.

means don't write duplicate code

To follow this principle, your class isn’t allowed to have more than one responsibility

“changes" here means "may vary over time due to changing requirements".

“software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification”.

The general idea of this principle is as simple as it is important: High-level modules, which provide complex logic, should be easily reusable and unaffected by changes in low-level modules, which provide utility features.

This principle states that no client should be forced to depend on methods it does not use. ISP splits interfaces that are very large into smaller and more specific ones so that clients will only have to know about the methods that are of interest to them.

The principle defines that objects of a superclass shall be replaceable with objects of its subclasses without breaking the application.

This is an object oriented technique (also called a design pattern) where certain operations on one object are automatically applied to another, usually contained, object.

This is one of the Software attributes which has something to do with the accuracy of the information of the system which tends the user to reckon on the system.

This is one of the software attributes which has the ability to withstand challenging factors. May perform its core functions and still avoid data loss.

This is one of the software attributes which has the ability of the system to cope up with the errors during execution and cope up with the erroneous input.

This is one of the software attributes which has the ability to partition or separate the different functionalities of a certain system.

This is one of the software attributes which has the behavior of a system whose components interact in multiple ways.

This is one of the software attributes that has the usability of the same software in different environments.

This may be defined as a coding error that causes an unexpected defect, fault, flaw, or imperfection in a computer program.

An attitude of a software tester that can figure out why something doesn’t work helps testers be confident and clear in communicating the defects to the developers.

This attitude of a software tester helps design better and powerful test cases basing on the weakness or flaws of the technology. Good testers know what it supports and what it doesn’t, so concentrating on these lines will help them break the application quickly

This level of testing is used to verify a single program or a section of a single program .