User:Xry0125/sandbox

=Software Quality Assurance= Software Quality Assurance (SQA), as its name suggests, is a set of methodology that tries to ensure the quality of all projects in the software process. More specifically, it includes some standards and procedures which administrators can use these to review and audit software products and activities to verify that the software meets standards.

Software quality is an attribute of software that implies the software meets its specification. Software specifications usually do not have a very clear and complete definition. It is not easy to specify quality attributes, so people generally judge the quality of software by conforming to these attributes, such as security, reliability, testability, adaptability, complexity, portability, usability, reusability, efficiency.

Purpose of Software Quality Assurance

 * To ensure quality in a software product, an organization must have a three-prong approach to quality management:
 * Organization-wide policies, procedures and standards must be established.
 * Project-specific policies, procedures and standards must be tailored from the organization-wide templates.
 * Quality must be controlled; that is, the organization must ensure that the appropriate procedures are followed for each project.


 * Standards exist to help an organization draft an appropriate software quality assurance plan.
 * ISO 9000-3 (original), now ISO 90003
 * ANSI/IEEE standards


 * External entities can be contracted to verify that an organization is standard-compliant.

SQA Activities

 * Application technology to manage quality
 * Analysts use application technology to achieve high-quality specifications and designs


 * Conducting formal technical reviews
 * Technicians find problems with related software quality through a series of meetings


 * Testing strategy
 * To ensure effective error detection, technicians use the use case design method to test


 * Enforcing standards
 * Some standards that need to be followed and tested during implementation


 * Controlling change
 * Applied during software development and maintenance


 * Measurement
 * Track software quality and asses the ability of methodological and procedural changes to improve software quality


 * Metrics and reporting mechanisms
 * SQA information needs to be collected and disseminated, this activity gives the procedures for it

Advantages & Disadvantages of SQA
Advantages:


 * After a rigorous and complete software quality audit, the software itself will be greatly reduced in vulnerabilities and risks, and the software will be more efficient. In addition, the quality of the software can be improved to avoid spending a lot of time on testing and maintaining the software. On some errors that could have been avoided.
 * Through software quality control, customer satisfaction can be greatly improved, because most customers do not have a strong software professional background, they only need a reliable tool.
 * Software maintenance is a large part of the development and use of the software, so improving software quality also means reducing maintenance costs.
 * Not only is the maintenance cost reduced, but a reasonable software quality assurance strategy can also reduce the total life cycle of the software.

Disadvantages:


 * SQA is the whole process of software development, so it is a project that consumes manpower, time and money.
 * Due to it has many standards and requires a lot of testing, there are certain requirements for the corresponding auxiliary programs.
 * Many times, if you don't achieve the software quality standards, the program needs to be modified or redesigned.

Article Evaluation
The article I read is Data type, below are my evaluation：


 * This article describes the data types are quite comprehensive, specifically primitive data types, composite types, other types, abstract data types and utility types.
 * I think we can add a concept about variables. Explain the relationship between variables and data.
 * The introduction to the definition of data at the beginning is not comprehensive enough and does not specify why we need to understand this knowledge.
 * This article is about academic knowledge, so it is neutral.
 * I checked the citation links for this article, which are currently valid and relevant to the topic.
 * The references are from ACM digital library，so it is a reliable reference.
 * It is a part of WikiProject Computer science.
 * The teacher may start from the most important part, or start from the easier one, but Wikipedia will not arrange according to these, it is only a systematic introduction, without considering the order of arrangement.

Added a reference section
Variables are used to store values, they have names and data types. The data type of the variable determines how bits representing these values are stored in the computer's memory. You can also specify its data type when you declare a variable. All variables have a data type to determine which data can be stored.

Definition of my topic about Software Quality Assurance
Software Quality Assurance (SQA) is a systematic approach to ensuring that management's proposed standards, procedures, practices, and methods are properly adopted by all projects. The purpose of software quality assurance is to make the software process visible to managers. It verifies that the software is standards by reviewing and auditing software products and activities. The Software Quality Assurance team participates in the creation of plans, standards, and processes at the beginning of the project. These will enable software projects to meet institutional guidelines.

Software quality control
From Wikipedia, the free encyclopedia Jump to navigationJump to search Software quality control is the set of procedures used by organizations to ensure that a software product will meet its quality goals at the best value to the customer, and to continually improve the organization’s ability to produce software products in the future.

It is distinct from software quality assurance which encompasses processes and standards for ongoing maintenance of high quality of products, e.g. software deliverables, documentation and processes - avoiding defects. Whereas software quality control is a validation of artifacts compliance against established criteria - finding defects.

= Software quality analyst = From Wikipedia, the free encyclopedia Jump to navigationJump to search A software quality analyst, or software quality assurance (QA) analyst, is responsible for applying the principles and practices of software quality assurance throughout the software development life cycle. Though often referred to as "quality assurance", software testing is considered to be only one part of the larger process of reducing errors. Testing is used to detect errors in a product; software quality assurance also fixes the processes that resulted in those errors.

= HP Quality Center = From Wikipedia, the free encyclopedia Jump to navigationJump to search Quality Center, formerly known as HP Quality Center is a quality management software offered by Micro Focus, who acquired the software division of HP Software Division of Hewlett Packard Enterprise in 2017, with many capabilities acquired from Mercury Interactive Corporation. HP Quality Center offers software quality assurance, including requirements management, test management and business process testing for IT and application environments. HP Quality Center is a component of the HP Application Lifecycle Management software solution set.