GB/T 18905.3-2002
Software engineering--Product evaluation-Part 3: Process for developers (English Version)

Standard No.

GB/T 18905.3-2002

Language

Chinese, Available in English version

Release Date

2002

Published By

General Administration of Quality Supervision, Inspection and Quarantine of the People‘s Republic of China

Status

Be replaced 2019-07

Replace By

GB/T 25000.41-2018

Latest

GB/T 25000.41-2018

Scope

This section provides requirements and recommendations for routine implementations of software product evaluation when evaluation is carried out concurrently with development and implemented by developers. In particular, the concepts described in Parts 1, 2 and 3 of ISO/IEC 9126, and GB/T 18905.1, GB/T 18905.2 and GB/T 18905.6 can also be used when using this part. The process described in this section defines the requirements for analysis and evaluation, the actions for specifying, designing and performing the evaluation, and the various activities required to draw conclusions from the evaluation of any software product. The evaluation process designed here is intended to be used concurrently with development. The evaluation process shall be carried out in parallel with the software development process, and the entity shall be evaluated upon delivery. This part is intended for use by: project managers, to clarify quality requirements, to monitor and control software quality during development, and to make decisions to ensure that required quality is an integral part of the software; software designers, to use To identify specific features that should be built into the software or changed to meet quality requirements; Quality Assurance, Control, and Audit Managers are used to evaluate whether quality requirements are met; ) to make decisions on design; • The buyer of the software. When independent evaluation is not required, the acquirer is part of the agreement with the developer when the software is acquired (as in the case of outsourced software development products). The buyer can be a purchaser, a developer who outsources part of the software product, or an end user. The role of the acquirer depends on the agreement signed with the developer. GB/T 18905.4 describes the evaluation from the perspective of the demand side. This section is intended for project-level application. To fully benefit from this section, organizations should be involved. GB/T 18905.2 includes this aspect. This part does not prescribe specific indicators or measurements, nor does it prescribe any special method of development

GB/T 18905.3-2002 history

• 2018 GB/T 25000.41-2018 Systems and software engineering—Systems and software Quality Requirements and Evaluation (SQuaRE)—Part 41: Evaluation guide for developers, acquirers and independent evaluators
• 2002 GB/T 18905.3-2002 Software engineering--Product evaluation-Part 3: Process for developers

GB/T 18905.3-2002 Software engineering--Product evaluation-Part 3: Process for developers was changed to GB/T 25000.41-2018 Systems and software engineering—Systems and software Quality Requirements and Evaluation (SQuaRE)—Part 41: Evaluation guide for developers, acquirers and independent evaluators.

GB/T 18905.3-2002 -All Parts