|
US$919.00 · In stock
Delivery: <= 6 days. True-PDF full-copy in English will be manually translated and delivered via email.
HJ 728-2014: Specification for Test and Acceptance of Environmental Information Systems. The software part
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| HJ 728-2014 | English | 919 |
Add to Cart
|
6 days [Need to translate]
|
Specification for Test and Acceptance of Environmental Information Systems. The software part
| Valid |
HJ 728-2014
|
Standard similar to HJ 728-2014 HJ 511 HJ 945.3 HJ 943 Basic data | Standard ID | HJ 728-2014 (HJ728-2014) | | Description (Translated English) | Specification for Test and Acceptance of Environmental Information Systems. The software part | | Sector / Industry | Environmental Protection Industry Standard | | Word Count Estimation | 35,364 | | Date of Issue | 12/25/2014 | | Date of Implementation | 3/1/2015 | | Regulation (derived from) | Ministry of Environmental Protection notice 2014 No. 87 | | Issuing agency(ies) | Ministry of Ecology and Environment | HJ 728-2014: Specification for Test and Acceptance of Environmental Information Systems. The software part
---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Specification for Test and Acceptance of Environmental Information Systems. Software part
National Environmental Protection Standard of the People 's Republic of China
Code for environmental information system testing and acceptance
- Software section
Specification for Test and Acceptance of Environmental Information
Systems - The software part
2014-12-25 release
2015-03-01 Implementation
Ministry of Environmental Protection
Directory
Preface II
1 Scope of application
2 Terms and definitions 1
3 test part
Acceptance section
Appendix A (informative) Test and Acceptance Document Set Example .20
Foreword
To carry out the "Environmental Protection Law of the People's Republic of China" to promote environmental information work, standardize the environmental information system
Test and acceptance process to ensure the quality and performance of environmental information systems, the development of this standard.
This standard specifies the planning, implementation, monitoring and evaluation of the environmental information system (software part) testing and acceptance.
And prevention management processes, to guide the developers, users and third parties to the new development of software, secondary development software and business
With software testing and acceptance work.
Appendix A to this standard is an informative appendix.
This standard is the first release.
This standard is organized by the Ministry of Environmental Protection Science and Technology Standards Division.
The main drafting of this standard. the Ministry of Environmental Protection Information Center, Jiangsu Province Environmental Information Center.
The Environmental Protection Department of this standard approved on December 25,.2014.
This standard is implemented on March 1,.2015.
This standard is explained by the Ministry of Environmental Protection.
Environmental Information System Testing and Acceptance Specification - Software Part
1 Scope of application
This standard specifies the planning, implementation, monitoring and evaluation of the environmental information system (software part) testing and acceptance.
And prevention and other processes, used to guide the developers, users and third parties on the newly developed software, secondary development software and commercial soft
Testing and acceptance of the work.
This standard applies to all levels of the national environmental protection departments to develop various types of new development software, secondary development software and commercial soft
Pieces.
2 terms and definitions
The following terms and definitions apply to this standard.
2.1 Environmental Information System
The core management software that integrates, processes or displays environmental data; implements environmental protection.
The decision-making system, management control system, office automation system and data and business exchange interface.
2.2 Test
A collection of one or more test cases; or a collection of one or more test procedures;
One or more test cases or protocols.
Acceptance
According to a certain standard for the project to develop the software, according to the contract, the Software Requirements Manual (SRS) and so on
Finished product inspection, to confirm whether the quality of the project to meet the requirements of the user.
2.4 Test Organization Testing Organization
The user of the environmental information system or the third party testing organization commissioned by the user.
2.5 Test Case Test Case
For specific goals (for example, to practice a specific program path or to verify compliance with a specific requirement)
A set of test inputs, execution conditions and expected results. For test items, specify the input, expected results and
A set of documents that execute conditions.
Acceptance Organization
The user or the user commissioned by the third party acceptance organization (including the user side commissioned by the expert group and other forms).
Project Plan
Project integrated management plan.
2.8 User Documentation User Documentation
A complete collection of documents in print or non-printed form is a product that customizes the development of software and solutions.
Prepared part.
23 test section
3.1 General requirements
3.1.1 coverage
3.1.1.1 National environmental information system
The national environmental information system is the environmental information system approved by the national environmental protection department. The measurement of such a system
Test organization for the Ministry of Environmental Protection or the Ministry of Environmental Protection approved third-party software evaluation agencies.
3.1.1.2 Provincial environmental information system
Provincial environmental information system is the provincial environmental protection departments approved the construction of environmental information system. The testing of such systems
Organization for the provincial environmental protection administrative departments or provincial environmental protection administrative departments recognized third-party software evaluation machine
Structure
3.1.1.3 Urban and municipal environmental information systems
The municipal environmental information system is an environmental information system approved by the municipal environmental protection departments. Such a system
Of the test organization for the local and municipal environmental protection administrative departments or local and municipal environmental protection administrative departments approved the third
Side software evaluation agencies.
3.1.1.4 District and county level environmental information system
District and county environmental information system is the district and county environmental protection departments approved the construction of environmental information system. This type of system
The competent testing organization shall be the district/county administrative department of environmental protection at the county level or the administrative department of environmental protection at the district or county level.
Tripartite software evaluation agencies.
3.1.2 System scale
According to the system corresponding to the information security level protection level will be divided into I-V system scale, respectively, corresponding information
Security and other security system in the first to fifth level, as shown in Table 1.
Table 1 System scale division
System scale objects corresponding to other levels
I first level
General system
second level
III Level III
Important system
Fourth level
V Extremely important system fifth level
3.1.3 system type
A) the new system. refers to the implementation of the contract does not exist before the need for construction units to develop the system;
3b) Secondary development system. Such systems include three types, namely, partially developed systems, systems provided by the purchaser, and heavy
With the system. Partially developed systems usually refer to existing or partial presence prior to the execution of the contract, but are required before delivery
The system provided by the ordering party, usually refers to the source code can be obtained, but the need for construction unit evaluation,
Developed or modified part of the code can be put into use the system; reusable system, usually refers to the construction unit has the source code, can
Developed or modified documents, through the call code can achieve the relevant functions of the system;
C) commercial systems. the product system, such systems are generally only the target code and user manual, access to the system source code
It is difficult, the user or the construction unit can not freely modify the system.
3.1.4 test level
A) Unit testing. refers to the system development process to be carried out at the lowest level of testing activities. In unit testing activities,
The independent units of the system will be tested in isolation from the rest of the program;
B) integration test. refers to the unit test on the basis of all modules in accordance with the design requirements assembled into a subsystem or
System, for integrated test activities;
C) system test. refers to the already confirmed system, computer hardware, peripherals, networks and other elements together, into
Line assembly test and validation test activities. The purpose is to verify that the system meets the definition of the requirements specification and finds out what is unqualified
At
D) regression test. refers to the modified code, the re-testing activities. The purpose is to confirm that the changes did not introduce new ones
The error or cause other code to generate an error.
3.1.5 system size, test level and the corresponding relationship between the type of system
The correspondence between system scale, test level and system type is shown in Table 2.
Table 2 System scale, test level and system type correspondence table
Test level system
Scale new system secondary development system commercial system
Integration testing, system testing (master
To function), regression test
Integration testing, system testing (main work)
Can), regression test
System testing (main work)
Can), regression test
Unit testing, integration testing, system
Test (main function), regression
test
Unit test (for the modified part),
Integration testing, system testing (main work)
Can), regression test
System testing (main work)
Can), regression test
Unit testing, integration testing, system
Test (full function), regression test
Unit tests (for modified parts),
Integrated test, system test (full power
Can), regression test
System test (full function),
Regression Testing
Unit testing, integration testing, system
Test (full function), regression test
Unit testing, integrated testing, systems
Test (full function), regression test
System test (full function),
Regression Testing
4V
Unit testing, integration testing, 2
Times the system test (full power
Can), regression test
Unit tests (for modified parts),
Integrated test, more than 2 system tests
(Full function), regression test
More than 2 times system test (all
Function), regression test
3.1.6 Related roles and responsibilities
3.1.6.1 According to the environmental information system testing and acceptance requirements, environmental information system testing and acceptance of the relevant roles are divided into
The next four categories.
A) Environmental protection department. responsible for environmental information system test planning and process management;
B) the supervisory authority. the testing process responsible for monitoring and controlling the environmental information system;
C) System construction unit. Responsible for the implementation of environmental information system;
D) third-party software evaluation agencies (or external manufacturers, experts). responsible for environmental information system development process testing
management.
3.1.6.2 system size and third-party software evaluation agencies and qualification requirements corresponding to the relationship shown in Table 3.
Table 3 system size and third-party software evaluation agencies and qualification requirements correspondence table
System - scale third - party software evaluation agency qualification requirements
Compliant with third party software compliance with ISO 17025 system requirements
Measuring institutions.
III above the provincial level software evaluation agencies.
√ Certified by the National Accreditation Board, with CNAS qualification
Software evaluation agencies.
V √
Through the national accreditation committee assessment, with CNAS qualification
Software evaluation agencies.
Note. √ indicates that you must select, ● that can be selected
3.2 Test management process
3.2.1 Test Management Flowchart
The test management process is mainly composed of planning, implementation, monitoring and review, correction and prevention, recording test management process.
Into the composition, the flow chart shown in Figure 1.
Figure 1 Test management process
3.2.2 Test planning
3.2.2.1 Contents and requirements
Test planning is mainly to test the needs of the analysis to determine the need to test the content or quality characteristics; to determine the full test
The requirements of the test; the basic method of testing; to determine the test resources and technical requirements; risk analysis and assessment;
Plan (including resource planning and schedule).
If the planned test is implemented by a third-party software evaluation agency, it must be met with the third-party software evaluation machine
Structure and qualification requirements of third-party software evaluation agencies.
3.2.2.2 Test Plan
3.2.2.2.1 Before the implementation of the test, the test organization shall, in accordance with the contract (or project plan) of the environmental information system,
System development contract or system/subsystem design document to plan the test process, develop a test plan. The supervisory authority should
Assist the testing organization to develop a test plan, and urge the project construction unit to work in accordance with the requirements of the plan.
3.2.2.2.2 Main contents of the test plan
A) Identify test adequacy requirements. Determine the extent to which the test should be covered and the extent of coverage required for each range;
6b) to determine the termination of the test requirements. Specify the conditions for the normal termination of the test process (eg, whether the adequacy of the test is met)
And to determine the possible cause of the abnormal termination of the test process;
C) determine the quality objectives of environmental information system testing;
D) determine the resource requirements for testing, including software, hardware, the number of personnel and personnel skills;
E) Identify the environmental information system characteristics that need to be tested. According to the description of the contract or system/subsystem design document
System functions, performance, status, interface, data structure, design constraints and other content and requirements, and to determine the need to test
Environmental information system characteristics;
F) determine the techniques and methods required for testing, such as test data generation and verification techniques, test data entry techniques,
Test results acquisition techniques, whether to use standard test sets, etc .;
G) determine the quasi-test conditions according to the requirements of the contract or project plan and the characteristics of the environmental information system;
H) determining the progress of the test activity determined by the resource and the system under test;
I) Conduct risk analysis and evaluation of test work and develop response measures.
3.2.2.2.3 Test Plan Review
The testing organization shall organize the relevant parties to review the test plan. After the test plan passed the review, go to the next step;
Otherwise, need to re-planning.
The test plan review points include but are not limited to the following.
A) the scope and content of the test plan, resources, progress, the parties responsible for whether the clear;
B) whether the test method is reasonable, effective and feasible, risk analysis, assessment and countermeasures are accurate and feasible;
C) whether the test document conforms to the specification and whether the test activity is independent.
3.2.3 test implementation
3.2.3.1 Test design
3.2.3.1.1 Prerequisites
According to test requirements, design test outline, analysis and selection of existing test cases or design of new test cases;
And verify the test data; according to test resources, risk and other constraints to determine the order of test cases; access to test resources,
Develop a test system; establish and calibrate the test environment; conduct a test ready review.
3.2.3.1.2 Steps
The test organization shall be tested and tested in accordance with the test plan. The test design generally consists of the following steps.
A) design test outline. According to the test requirements, a clear test of the required items, design test steps, the establishment of the test
Outline;
B) review the test outline, identify the test outline, modify the test outline for the problem;
C) design test cases. Will be required to test the characteristics of the environmental information system decomposition, for each case after the decomposition of the design test
Trial case
7d) to obtain test data, including access to existing test data and generate new data, and in accordance with the requirements to verify all the number
according to;
E) determine the order of the test, from the constraints of resources, risk and test case failure caused by the impact or consequences of several aspects
consider;
F) access to test resources, for supporting the test system, some need to select from the existing tools, and some need to open
hair;
G) Write test procedures, including the development of test support tools;
H) establish and confirm the test environment;
I) Write a test description.
3.2.3.1.3 Test readiness review
The testing organization shall organize the expert group entrusted by the user or the third party testing organization commissioned by the user to conduct the test-ready review.
Test readiness review The main review of the test outline, the rationality of the test plan; test case correctness, effectiveness and coverage
The organization, environment and equipment tools are available and meet the requirements.
Before proceeding to the next step, you should pass the test ready review.
3.2.3.2 Test implementation
3.2.3.2.1 Test The organization performs test cases based on the test plan, obtains the test results, analyzes and determines the test results. Simultaneously,
According to the results of different judgments to take appropriate measures.
3.2.3.2.2 Check the normal or abnormal termination of the test process and, based on the results of the check, do not meet the end of the test
Condition of the test case, the decision is to stop the test or need to modify or supplement the test case set, and further testing.
3.2.3.2.3 The work performed by the test includes the following.
A) Determine whether the test case is based on the expected test results, actual test results and evaluation criteria for each test case
Pass, and record the results in the test record. If the test case does not pass, the test organization should carefully analyze the situation and root
Take the appropriate measures in the following circumstances.
1) Test description and test data errors. The measures taken are. correct the error, will correct the error information detailed records,
Then rerun the test.
2) errors during the execution of the test procedure. The action taken is to rerun the test steps that were not performed correctly.
3) errors in the test environment. The measures taken are. to amend the test environment, the environmental amendment to a detailed record, heavy
Run the test; if you can not correct the environment, record the reasons, and then check the termination of the situation.
4) the realization of environmental information system error. The measures taken are. fill in the problem report form, may make a system to amend the proposal,
And then continue to test; or error and abnormal termination of the situation, check the termination of the situation. The information system has been changed
After completion, should be based on the situation for its regression test.
85) Environmental information system design error. The measures taken are. fill in the problem report form, can be made to amend the proposal
And then continue to test; or error and abnormal termination of the situation, check the termination of the situation. The information system has been changed
, Should be based on the situation for its regression test or re-organization test, the regression test need to modify the test design and
data.
6) Safety error of environmental information system. The measures taken are. fill in the problem report form, can be made to amend the proposal
And then continue to test; or error and abnormal termination of the situation, check the termination of the situation. The information system has been changed
, The regression test should be carried out according to the situation, the regression test need to modify the test design and data accordingly.
B) When all test cases are executed, the test organization will be responsible for the adequacy and failure of the test.
Whether the test work is sufficient, whether the need to add new tests. When the test process is terminated normally, if the test is found
Lack of response to the system until the test meets the expected requirements and records the additional content in the test report;
If a supplemental test is not required, the normal termination is recorded in the test report. When the test process is terminated abnormally, it should be noted
Recorded termination conditions, unfinished tests and unadjusted errors.
C) When all errors that cause the test to terminate abnormally are corrected, the test object needs to be re-tested to confirm
Modification does not introduce new errors or cause other code to generate errors. Changes in the testing phase must be in this
Regression within the test phase, so as not to leave the error to the next test phase; regression test during the response to the system version
The freeze, the regression test found the problem focused on the revised, centralized return.
The supervisory authority shall check the records of the problems in the testing process of the project construction units and the records of their corrections and supervise the construction of the project
The unit to solve the problems found in the test and nonconformi...
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of HJ 728-2014_English be delivered?Answer: Upon your order, we will start to translate HJ 728-2014_English as soon as possible, and keep you informed of the progress. The lead time is typically 4 ~ 6 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of HJ 728-2014_English with my colleagues?Answer: Yes. The purchased PDF of HJ 728-2014_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.
|