1. Quality Management
Perfectqaservices

2. Quality-management is method for ensuring quality of software and its devlpopement process.
It has three main Components:
Quality Assurance
Quality Control
Quality Improvement

3. Quality Assurance
It is the activity of providing evidence needed to establish quality in work.
QA includes implementations of process, procedures to verification of developed software and its requirements.
QA is to examine the process that create and shape the product.
Quality assurance looks at the quality of output , as well as at the quality of input.
Quality assurance covers all activities from design, development, production, installation, servicing and documentations.
So last for QA I can say it is “ FIT FOR PURPOSE “

4. Quality Control
Quality Control is a process to ensure a certain level of Quality in a product or a service.
It includes activities that ensure the software with respect to requirement.
Means we can say that the basic goal of quality control is to ensure that the products ,services, or process provided meet specific requirements.
It is Product base activity.
Quality control involves the examinations of product, service, or process for minimum level of quality.

5. QA Vs QC Quality Assurance: Quality control:
It is process oriented activity
Focuses on process and procedures rather than actual testing on system.
It is preventive activity .
Audit ,Review is an example of Quality assurance.
It is product oriented activity
Focuses on actual testing by executing software for identify bug/defect through implementation of process.
It is corrective process.
Testing is part of quality control.

6. Software Development Lifecycle (SDLC)
SDLC is a flow for software project, it consists of detailed plan describing how to develop, maintain software
The Lifecycle defines process for improving quality of software and overall development process.
It states the starting point and ending point of any software development
Each phase in software development process has defined input and output.

8. Different Stages in SDLC
Requirement analysis
Software Design
Coding
Testing
Implementation
Maintenance

9. Requirement analysis
In this phase the requirement of clients are obtained, analyzed, documented and validated.
The requirement should be clear for developing quality software
Requirement analysis is the most important and fundamental stage in SDLC. It is performed by the senior members of the team with inputs from the customer, the sales department, market surveys and domain experts in the industry. This information is then used to plan the basic project approach and to conduct product feasibility study in the economical, operational and technical areas.
Input – Customer requirement
process-Analysis of the requirement
output – Software requirement specification

10. Software Design
Software design involves development of architecture , flow of the application
While Designing the software it needs to consider different aspect of application such as usability , performance , security compatibility and the database
Input-software requirement specification (SRS)
process-Design the software
output-software Design document and internal design (coding)

11. Coding
After the software design ,the developer develops code as per the design specification.
Input: software design
process: Developing Code
Output: source code

12. Testing
In this phase the software tested to ensure that it meets customer requirement.
In this each unit or module tested independently .
Input: Executable code
process : Testing
output : Testcases

13. Implementation
In this phase the software after testing is successfully completed is installed in the computer system.
Input: Well tested code
process : Implementation
Output: version

14. Maintenance
In this phase the customer need some modification in the existing system. And again the requirement needs to be analyzed ,design , developed , the code and test as well as previous code.

15. Example of SDLC
Waterfall Model

16. Testing Methods

17. Three Methods Used for test the software
Black box testing(functional testing)
-Test to the specification
White box testing(Structural testing)
- Test to the code
Grey Box testing

18. Black Box Testing
Black box testing is known as functional testing and mostly focus on the functionally aspect of application.
IN this set of input condition are entered to find the behavior of the application
Black box testing is strategy used for designing the test cases based on the specifications
IN this technique tester is unaware of internal structure of system.

19. White box testing
White box testing is testing technique that examines the program structure.
Exercise all logical decision in their true and false sides.
Exercise internal data structure to ensure their validity.

20. Grey Box Testing
Grey Box testing is testing technique performed with limited information about the internal functionality of the system. Grey Box testers have access to the detailed design documents along with information about requirements.