Software test and software quality assurance. (Reading notes)
1. Software Quality Assurance (SQA) Guarantee Quality is an activity that provides evidence to all related people to establish confidence that quality functions are running on demand.
a. Software development product SQA target
1). Demand analysis
By identifying mutual contradiction, inconsistent, there is ambiguity or unnecessary demand, ensuring that the user designated needs to meet his true requirements. Avoid misunderstandings between developers and customers.
2). Product Description
Ensure that the product manual is consistent with the system requirements by establishing a demand tracking document.
Ensure that the product manual can adapt to the flexibility, maintainability, and performance of the local improvement system.
Ensure that test strategies have been established.
Ensure that a reality of development schedules have been established, including the planned review.
Ensure that formal change procedures have been designed for the system.
3) software design documentation
Make sure that the standards for describing the design are established and ensure that these standards are followed.
Ensure appropriate control and design changes to the document record team.
Make sure that the system design component has been approved according to the agreed guidelines before the encoding is obtained.
Make sure the team's review is carried out according to progress.
4). Code
Make sure the code follows the established style, structure, and document standards.
Make sure the code is properly tested and integrated, and the modification of the encoding module is appropriately identified.
Viewing the code written to follow the established progress.
Make sure the code review is carried out in accordance with the system.
5). Test document
Ensure the establishment and follow of the test plan.
Ensure that the created test plan meets the requirements of all product specification.
Ensure that the software demand is consistent with the product manual after testing and rework.
6). Maintain documentation
Ensure the consistency of the code and documentation.
Ensure that the established change control process is detected, including the process of integrated the product to the software.
Ensure that the modification of the code follows the coding standard and to review it, do not destroy the entire code structure.
b. Implement quality management
1). Quality management system
Define the starting point of the process, establish a quality policy. After establishing the quality policy, you should post a document as procedures, standards, methods, and other content. To ensure that a lot of quality experts must make a full-time full-time responsible for this task. Establish a software engineering Process Panel (SEPG), the team is responsible for monitoring and carefully coordinating all processes based on feedback continuous definitions.
It is undoubtedly failed to make a part-time staff to write process documentation. QA team needs to ask the relevant personnel while writing documents, and determine those who engage in this work to review the document before implementing it.
Quality management is the supplement of project management, and it is clear that the importance:
1. Meet customers - understand, manage, and boot demand, thereby achieving or exceeding the expectations of customers.
2. By testing to prevent errors - Avoiding the cost of errors is usually much lower than correcting them.
3. Manage responsibility - successfully needs a cooperation of all team members, but the resources required to provide success are the responsibility of management.
4. Procedures - Deming and other people described in the repetition "Plan-Execution-Test - Action" working cycle.
In addition, the quality improvement measures taken by the Executive Organization can improve the quality of software project management, and it can also improve the development of production quality.
2) Quality plan.
Quality Plan includes determining which quality standard is suitable for this software development and decides how to achieve these standards.
The development team should also pay attention to a basic principles in modern quality management - the quality is determined in the plan, rather than being determined in the test.
A. Enter the quality plan.
1. Quality Policy. One of the efforts and decisions that pay attention to quality organizations, commonly referred to as top management.
2. Reference. Important input to the quality plan. Reveal written documents of the main sub-development projects and development targets.
3. Product Description. Clauses the main points, details and factors that may affect quality programs.
4. Standards and planning.
5. Output of other programs. It should be considered as part of the quality plan.
B. Means and techniques of quality plan
1. Benefits / cost analysis. To achieve quality standards, we must first reduce rework, and improve the satisfaction of developing relevant personnel. The benefit is more important than cost.
2. Basic level standard. Including the implementation of the implementation of the actual or planned development with other development implementations, thereby giving a level of ideas, and provides standards for detecting development performance.
3. Flowchart
I. Cuzu (Ishiawa)
II. System or program flowchart.
4. Test design is an analytical skill that he helps identify which variables have the greatest impact on the achievements of the entire development. It can also be used for software development management results .c. Output in the quality plan
. , Highly refined or framework summaries, all of which are developed.
2. Operation definition.
3. Experue.
4. Enter the input to other programs.
3) Quality assurance
Quality Assurance is "In order to provide credit, the proven project will meet the quality standards, and the planned and organized work activities developed in the quality system."
Quality assurance is usually provided by the quality assurance department or a similar name organization, but it is not all.
A. Quality assurance input
1. Quality management plan.
2. Quality control test results. Quality control test results are reports on quality control detection and testing to compare the analysis.
3. Operation definition.
B. Resources and techniques for quality assurance
1. The means and techniques of the quality plan. The quality planning and techniques of the description can also apply in quality assurance.
2. Quality review. It is a structural review of other quality management activities.
C. Output of quality assurance
Quality improvement. Quality improvement includes measures to improve the efficiency and efficiency of software development, providing more benefits for software development related personnel.
4) Quality control
Quality control includes monitoring specific project outcomes to determine if they meet the relevant quality standards, and identify how to eliminate software development results is not satisfactory.
The project team should have actual operational knowledge of quality control statistics, especially sampling and probability. And you should distinguish:
l Prevention and inspection.
l Static sampling
l Determining the reason
l error range
5) Input of Quality Control
1. Project results.
2. Quality Management Plan
3. Operation definition
4. Experue
6) Means and techniques of quality control
1. Test. Instructions include measurements, inspections, and testing activities, the purpose is to determine if the results of development projects are consistent with the requirements.
2. Control Table. The control table is displayed in accordance with a chart of the program operation based on time.
3. Arrange. It is a histogram that is tissue generated by an event to show how much results are caused by various types of identified.
4. Sampling statistics.
5. Flowchart
6. Trend analysis. Trend analysis is often used to detect:
l technical performance
l cost and progress performance
7) Output of quality control
1. The quality is improved.
2. Received decisions.
3. Request.
4. After the completion of the certificate
5. Adjustment of the program.
