Quality management and quality assurance STANDARDs--Part 3:Guidelines for the application of GB/T 19001-1994 to the development,supply,installation and maintenance of computer software
Some standard content:
JCS 03. 120. 10
National Standard of the People's Republic of China
GB/T19000.3—2007
id1 rso 9000-3:1997
Quality management and quality assurance standard
Part 3: GB/T 19001---1994
Ouality management and quality assurance standards-Part 3:Guidelines for the application of GB/T 19001---1994to the development, supply, installation and maintenance of computer software2001- 02- 13 Issued
2001:10-01 Implementation
Issued by the State Administration of Quality and Technical Supervision
CE/T 190C0.3—2001
1SU Introduction
1 Scope
3 Definitions
4 Quality system requirements
Management responsibilities
Quality system
Contract evaluation
Design control
Documentation and preparation
Control of customer-supplied products
Product identification and compatibility.
Process control…
Inspection and testing
Control of screening, quality and test equipment
Inspection and test status
Preparation of non-qualified products
Corrective and emergency measures
Storage , packaging, care and delivery
Quality record control
Internal quality control
Prying technology
Appendix A (record of standard)
Mongolian literature
Appendix B (suggestive appendix) and ISO/IEC12207:1SS5 bottle inspection table KAONKAca
GH/F19000.3--2001
This standard adopts the international standard TS () 9000-3: 1997 quality management and quality assurance standard part 3, [S09001: 1994 guide for the use of computer software development, supply, installation and maintenance. The standard is an integral part of the GB/T190D0 family of standards and is consistent with it. This standard has made technical revisions to GB/T15VUU.3-1994 (idIIS()900n-3, 1998). The main technical content changes are as follows: 1 Editing format
The old version is based on the format of the quality system life cycle, dividing the quality system requirements into three parts, namely, quality system - framework, quality system life cycle activities, and quality system - supporting activities, which are divided into 23 quality requirements: After revision, it is edited according to the 20 general items of GB/T19001-1994.
) The new additions are mainly reflected in the design and development of software materials through Article 4.4 "Reform the design system" and the original reality. In addition, the software intellectual property protection and licensing system are added in Article 4.3.2, and the prevention of disease control is added in Article 4.4.2. Appendix A of this standard is the appendix of the standard, and the appendix is the appendix of the standard. This standard replaces (:/T19000.3-19 from the date of implementation. The bid certificate is proposed by the China Standards Research Center: This standard is under the jurisdiction of the National Technical Committee for Quality Management and Quality Assurance Standardization. This standard is drafted by the China Standards Research Center, and the main drafting units of the standard are: China Standards Research Center, 204 Institute of the Second Academy of China Aerospace Corporation, Beijing University of Aeronautics and Astronautics, Industry Technology (China) Co., Ltd., and the Fourth Institute of the Ministry of Information Industry. The main drafting leaders of the standard are Xiantong, Tuzhan, Cai Kaiwan, Liu Jiangli, and Liu Yang. This standard was first issued in 1994 and revised in 2190. 1900C.32001
iKAoNiKAca
The International Standards Council (ISC) is a world-wide federation composed of national standardization bodies (IS member bodies). The work of formulating international standards is usually completed by ISO's technical committees. If a member body is interested in the standards established by a technical committee, it has the right to participate in the work of the committee. International organizations (official or unofficial) that maintain contact with IS can also participate in related work: In the field of electrotechnical standardization, IS maintains a close cooperative relationship with the International Electrotechnical Commission (IEC). The draft international standards formally adopted by the technical committee are submitted to the member countries for approval. International standards can only be formally adopted if they are approved by all 75 member bodies that participate in the vote. |tt||This international standard JS () 900C-5 was developed by the Quality Systems Subcommittee of the Technical Committee on Quality Management and Quality Assurance of ISU/TC176/SC2.
This standard has made technical revisions to the first edition (15090003:1951) to replace the first edition. The general title of 1S09000 is: Quality Management and Quality Assurance. The standard consists of the following parts: ... Part 1: Selection and use of information: - Part 2: General guidance for the implementation of ISO9001.1S9002 and ISO9003: Part 3: Guidelines for the use of ISO91:14 in the development, supply, installation and maintenance of computer software: - Part 4: General guidance on the outline of reliability. Appendix A and Appendix B of this standard are for reference only.
CB/I 19000. 3 -- 2001
This standard provides guidance for use by parties involved in the design, development, installation and maintenance of computer software. The teaching material may be used:
as part of a business contract signed outside the class; b) as a commercially available product;
) to support the business of optimizing the software;
) as an embedded hard product. This standard addresses the issues to be addressed, regardless of the technology used, life cycle model, development process, start sequence or organizational structure.
When the scope of the group's activities includes other areas besides computer software development, the relationship between the computer software elements of the group's quality system and the elements of the other areas should be clearly stated to form a complete quality system. The standard is GB/119301-1994. The reference number is 1. The original text of GB/19001-1994 has been added to facilitate confusion.
The term "should" is used throughout this standard to indicate a provision that is binding on both parties. "will" indicates a statement or recommendation from one party. "best" indicates a slight recommendation among many possibilities. "may" indicates a practice that is permitted within the limits of this standard. 1 Scope
National Standard of the People's Republic of China
Quality management and quality assurance standard
Part 3: GB/T 19001-1994
Guidelines for the application of G/T 190011994 to the development, supply, installation and maintenance of computer software
sotiware-UIKAONKAca
GB/T19000.3—2001
ID1 [$o 9000-3:1997
Replacement GE/15—1994
This standard provides guidance for the use of CB/T1-194 by organizations responsible for the development, supply, installation and maintenance of computer software. This standard does not add or change the requirements of GB/T20551-1994. This standard is not used as an assessment standard for quality assurance and (or) registration. 2 Referenced standards
The following standards contain provisions that, when cited in this standard, constitute the provisions of this standard. The provisions of the standard. When this standard is published, the versions shown are valid. All standards will be revised. The parties using this standard should discuss the possibility of using the latest version of the following standards. GR/T583-994 Quality Management and Quality Assurance Technical Manual (ID11SO8402:1994) GB 190011991 Quality System Design, Development, Production, Installation and Service Quality Assurance Model (2000994)
3 Definitions
This standard adopts the definitions of GB/T 6585 and the following selected definitions. 3.1 Product produrt
The result of an activity or process.
Note 1: Products may include services, items, fluid materials, components or a combination of these. Products can be tangible (such as components or alternative materials) or tangible (such as knowledge or concepts or their effects). In this standard, the term "product" only applies to the desired product, not to the "unexpected" product that affects the environment. This does not apply to the definition of B/6553.
GB/1901-1991
3.3 Contract
A contract between the supplier and the customer that is agreed upon by both parties. Approved by the State Administration of Quality Supervision, Inspection and Quarantine on 2001..0213 Implementation on 2001-10-01
[GB/T 19001--1994
3.4 Baseline
GB/T 19000.3—2001
A version of a configuration item that has been formally approved and formally marked and determined at a specific time in its life cycle. Regardless of the medium
1IS/TEC:12207:1S5!
3-5 Development development
The life cycle of a software, which includes the following activities: requirements analysis, design, coding, design, testing, installation and support of the software product
3.6 Life cycle model life cycle model The entire life cycle of the system, from the determination of the requirements to the end of use, including the processes, activities and services related to the development, operation and maintenance of the software product. _S0/IEC J2207.1903.
3.7 Stage 315
Tax work part:
Comparison: The hospital section and pay for the specific survival of the same period of chess, 3.8 National White Xie #tegression testing Testing performed to determine if defects caused by technical changes made during the production process are corrected: 3.9 Copying software The process of transferring a small copy of a software product to another location. 3.10 Software See software product (3.113 Software, except that the term "software" in this standard is limited to computer software. 3.11 Software product A complete set of computer programs, including any associated documentation and data. [150/I:12207:1995] Note: A software product may be a component of another product or a product used in the development process. 3.12 Software product Any identified part of a software product. 4 Quality system requirements 4.1 Management and recovery 4. 1.1 Quality objectives
The management responsible for implementation shall define the quality policy, including quality objectives and commitment to quality: and document it. The quality policy shall reflect the objectives of the supplier organization and the expectations and needs of the customer. The supplier shall ensure that its personnel at all levels understand the quality objectives and adhere to them.
Further guidance related to soft products is provided. 4.1.2 Organization
7.1.2.1 Responsibilities and authorities
GA/T19000.3—2001
iKAoNrKAca
For personnel engaged in the management, operation and acceptance of quality-related work, especially those who perform independent tasks and have the following responsibilities, the corresponding relationships and authorities shall be established and documented: a) Take measures to prevent non-compliance with product, process and quality system; 1) Confirm and record relevant information related to product, process and quality system Problems;) Flux specified, adopt retreat, maintenance or propose new solutions: d) Verify the implementation effect of the solution:
") Control the processing, delivery or installation of the product, directly lead to defects or non-compliance with the requirements until they are corrected. There are further development guidelines related to the carrier. 4.1.2.2 Resources
For management, hot work and verification activities (including internal quality review), the supplier shall determine the resource requirements and provide sufficient resources, including the personnel who have been trained (see 4.15). There are no further development guidelines for differences with the obtained parts. . For example: Article 11 of the Information on Progress,
4.1.2.3 The Manager's Representative
is responsible for the legal management of the medical treatment. He should appoint a member as the management representative among his own managers. Regardless of the basis of other factors, he should confirm the authority to enable
a) Ensure that the quality system is established, implemented and maintained in accordance with the requirements of this standard; :) The person in charge shall report the operation of the quality system to provide for evaluation and serve as the basis for quality improvement of the system; : The manager may collect the original payment for the relevant work of the relevant external party without any external guarantee; Further guidance related to the quality of the product. : Improved information element: 1
4.13 Management evaluation
Supplier management responsible for performance evaluation, the company shall evaluate the system at regular intervals to ensure continued suitability and effectiveness to meet the requirements of the standard and the supplier's specifications or policies (1.1.1), review records to ensure (4.15) There are further guidance related to the quality of the product.
Lan: Further information S>23u:., 7.4 system 4.7 quality system
4. 2. 1 General
The supplier shall establish a quality assurance system and maintain relevant documents. To ensure that the product meets the requirements of this standard, the supplier shall prepare a quality management system that includes or references the quality system management process and summarizes the quality system documents. : o Supplier Manual
There are no guidelines related to software:
4.2.2 Quality System Management
The supplier shall prepare a documented process that is consistent with the quality management system and the supplier's specifications: 6. Effective implementation of the quality system and its documented process, as part of the product quality system, the scope and complexity of the work, the methods used, and the skills of the personnel involved in this activity. Note: No further guidance is provided for software. 4.2.3 The supplier shall specify how to meet the quality requirements and form a document. The quality planning shall be consistent with all other requirements of the quality system and form a document suitable for the supplier's work: For the product, the supplier shall verify the requirements specified in the contract. b) Determine the necessary control stages, processes, equipment, inspection and test equipment, resources and skills to achieve the required quality: d) Ensure the consistency of relevant documents of design, production process, installation, service, inspection and test procedures; e) Determine all test requirements, including the measurement capabilities that can be developed within the sufficient time limit beyond the current level; and determine the appropriate age of the entire product formation stage! ) For all requirements and orders, including special requirements and fees that are inconsistent with the conditions, it is difficult to change the standards. h) Schedule and prepare quality records (see, 4.16) The quality plan should describe the following: 1) When feasible, measurable force expression of the requirements of the operation: 2) The life cycle model used in the development process: 3) Define the stages of the project operation and the necessary criteria for the station 4) Specify the types of evaluation, testing and other verification and screening activities to be performed: 5) Confirm the configuration and management rate of the process; 6) Develop detailed plans for the following items? It also includes schedule scheduling, procedures, resources and approvals. It also includes: location managementbzxZ.net
Monitoring and confirmation of development products:
Verification and confirmation of purchased products:
Acceptance of supplied products
Control of qualified products:
Ensuring that all activities are carried out as planned in the quality plan: The quality plan first applies the quality system to a specific project, product or combination and can be an effective method. When appropriate, the quality plan can also include or use common procedures and (reduce) specific sequences for a project/product/combination. The quality plan should be updated according to the development progress. At the beginning of each stage, all matters related to the stage should be completely determined. The quality plan will be reviewed by all organizations related to the implementation of the plan and an effective state should be achieved. The quality plan deliverable may be an independent document (with the title of quality plan) or part of another document or may consist of several documents. The quality plan may include the planning of unit tests, component tests, system final tests and acceptance tests, guidelines for component testing and test environment, and parts of the quality review meeting and test life. GH191 provides the content of the plan/to provide a guarantee for the progress of the quality review. 80121335 6.2--6.E. 4.3 Contract review 4.3.1 Overall plan The supplier shall maintain a documented sequence of joint evaluation and coordination of joint evaluation activities. GB/T 19000.3 200
The training documents are part of the contract, as the product entering the market, as the training documents of the hardware product, as the supporting process of the physical industry, and the evaluation is appropriate. All these details are described below. 4.3.2 Evaluation
Before bidding or accepting a contract order (for the description of the requirements), the supplier shall evaluate the bid, contract or order to ensure that: a) all the requirements are clearly defined and documented, and the requirements are received verbally. In the event that there is no documented requirement, the supplier shall ensure that the requirements of the order will be reviewed before it is accepted; any requirements that are inconsistent with the technical specifications of the order will be implemented; and the supplier has the ability to meet the requirements of the contract or order. When the supplier is in the process of preparing the bid, contract or design, he shall also understand the relevant steps and the relevant items with the customer:
The terminology used is consistent with the relevant parties! Problems with the operation of the contract: the ability and resources to carry out the contract work, the customer's acceptance or rejection of the product will be handled according to the quality and relevant design rate of the left-hand side of the job change, the whole Asia development of the package I package 1 small, the customer's participation in the development of the period; to monitor the progress of the contract before the contract review! In the development and maintenance period, handle customer needs more consistent with the business process; · Follow up the customer's instructions during the life cycle:
after the acceptance of the problem to deal with, including customer complaints! Guarantee the responsibility of eliminating unqualified products before the contract: when the supplier believes that there is a need for subsequent cost upgrades, the customer must fulfill the obligations, or the supplier must maintain the previous version of the product: report the monthly production and related training
b) Technical matters:
meet the needs! practicability:
software development standards and procedures:
clearly define the design of the software, 1. software release, and ensure that they are suitable for the legal and legal aspects;
make a formal agreement with the software product importer;
copy and distribution requirements.
!
clearly define the potential accidents or risks, and evaluate their impact on subsequent activities! Supplier work also includes the work of the contractor, progress, technical review, delivery schedule; installation, maintenance and support requirements; technical analysis, timely availability of human resources, legal, security and confidential matters: information that may be used according to the platform and intellectual property rights. License agreement, confidentiality and total protection of this information within the entire production version of the product as well as customer inspection or verification of this version of the investment: the need for all parties to agree on the total information of the customer project: the provisions of the guarantee: the company's responsibility "starting from: E 17, 1. 2. 1 system, 5. 2 6 ※ and 6. 4. 2.3, 5
4.3.3 The company's warning certificate
GH/T19000.32001
The company should determine how to conduct contract summary and forward it to the relevant functional departments of the party organization. There are no further guidelines related to software: the first step is to follow the 1st and 2.3.2 of 50/TFC20753. 4.3.4 Records
The records of contract evaluation should be kept (see 4.15). Note! : For the establishment of a network related to quality consulting, there is no further guidance related to the status of the contract. 4. 4 Design Control
4.4.1 Overall Testing
A documented procedure shall be established to maintain product design control and verification to ensure that requirements are met, including design, detailed design and coding, and package planning. Software development projects shall be organized according to one or more survival cycle models, and activities and tasks shall be planned and communicated according to the frequency of the two-phase model. The endogenous model used may be adjusted to suit the needs of the project and this standard shall not be modified during its use. Life cycle model.
The type of use period will be clearly defined, and how to use this process will be specified. The six standards describe this process in a sequential order, but it is not recommended to follow this sequence.
The development process is the process of converting requirements into software products. In order to avoid errors, this process should be carried out in a standardized manner. This approach should be based on the two processes of verification and approval. Therefore, the supply chain should be established to maintain the support of the problem: to ensure that the development of software products meets the requirements of the above points, and is carried out according to the development plan or>quality discussion, and the design should be considered properly. The activities shall include the following aspects: a) Design method: Design method shall be applied systematically, and the performance of the method shall be considered in terms of the performance of the task product and the compatibility of the method with the intended use point; ii) Utilize past experience, lessons learned from past practice, and experience gained from previous project evaluations and past project reviews. Avoid presenting the same or similar items to the subject; iii) User process: The product shall be designed to be easy to test, install, maintain and use; iv) Safeguards and security: The design shall give special consideration to the testability of the product. For products whose failure will cause harm to people, products or the environment, the design shall ensure that special requirements are met. Detailed description shall be given to the software design to avoid damage in the event of failure, and the system's response to the failure state. For programming, there should be regulations and guidelines. Programming methods should be used in a controlled manner, including naming rules, auxiliary coding rules and appropriate comment rules. Such rules should be documented and used to control the quality of the system. Suppliers can use 1 tools, facilities and technologies to increase the expected effect of the resource system in this target. To achieve this, the facilities and technologies can also be effectively used: management day, mainly can be effectively used for product development and (or) services: this is not allowed; 1 common technologies are developed internally or purchased, and suppliers must evaluate whether they are suitable for use. In general, tools are used in product development, such as branch tools, design tools, translation tools, editing tools, etc. The approved, etc., letter or compared with the existing level configuration: the use of this kind of village technology is documented, and the source of their nature is read out when they are made, so that they can be quickly promoted and upgraded
developed well with this 1 and other technologies, or after the collection of research or payment, it may be necessary to train the responsible personnel, 4.4.2 Design and development planning
GR/T19000.3...2001
TKAONrKAca-
The supplier shall plan the design and development activities or prepare a plan, and the plan shall state or list the measures to be carried out.The development plan should be a document of the development plan. The development step should be reviewed and approved. The development plan can have other names, such as the software development plan or the software monthly plan. After considering all the requirements, it can be determined how the project will proceed, the types of reports required, including those from the market, customers and other relevant parties. When issuing the plan, the following items should also be described: u) Definition of the project, including a description of its objectives and reference to any relevant customers or suppliers; b) Definition of the project as a whole; 3) The location of the team, including the work structure, collection, use of materials by the contractor and the required materials; 4) Personal feelings about the technical interface:
about the team;
users,
customer representatives;
quality assurance representative.
5) Cry or reference the following content:
- Each activity requires the person in charge!
The management and support required by the project activities,
1The possible risks related to development, assumptions, dependencies and time specifications: R) Schedule planning, two clear
work to be done (i.e., time requirements for the project, the person and the related resources to be withdrawn:
The relationship between the execution of the project and the relevant project planning:
Thinking process department.
|h) Specify the following:
Standards, terms, conditions, standards and agreements:
Development and quality of the technology, including the constraints of such 1It comes from the configuration management of the software and configuration control;
Control will not be in line with the product method!
Not for support! The non-empty payment software is a unique light sentence delivery method: the return to school identity and the recovery of the hall, the risk should be considered: a sick voice user light control method:
1) the relevant plan includes the system-level plan such as: one-two volume plan
risk belt management upgrade plan;
with writing management plan:
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.