DZ/T 0169-1997 Specification for computer software development for geophysical and geochemical exploration
Some standard content:
1C5,35.180
Record number: 951997
People's Republic of China Geological and Mineral Industry Standard DZ/T 0169
Specification for Computer Software Development for Geophysical and Geochemical ExplorationbZxz.net
Published on March 19, 1997
Published by the Ministry of Geology and Mineral Resources of the People's Republic of China on November 1, 1997
Implemented on November 1, 1997
D7./T159—1997
This standard provides unified requirements for the development of geophysical and geochemical exploration software. Strict compliance with this standard ensures that the developed software is profitable and maintainable and can become a product. This standard is proposed and managed by the Technical Change Committee of the Geophysical and Geochemical Exploration Department of the National Geological Survey Standardization Planning Committee. This project This specification was mainly drafted by: 1. Standard of Geological and Mineral Industry of the People's Republic of China, Geophysical and Geochemical Exploration Computer Software Development Center.
D7./T0169-1997
This specification is applicable to the entire process of geological and mineral exploration and geochemical exploration computer software development. It can also be used as a reference for other professionals in the geological and mineral industry when performing similar work.
2. Cited standards
This standard cites the relevant clauses of the following standards: When the standard is issued, these cited standards are valid. All standards will be revised. The parties using this standard should discuss The following standards may be updated as required: GB856-85 Computer Hardware Development Specification
GB6567-88 Computer Hardware Product Development Documentation Preparation Guide GR/T11457-B9 Software Engineering Terminology
3 Terminology
The definitions of terms are given in GB/T11457. The definitions of other terms used in this specification are given below. 3.1 Software
Computer programs and related data and documents required to enable a computer to perform computing or control functions. 32
Written materials related to program concurrency, maintenance and use are an essential component of software. 3.3 Task entrustor refers to the unit or individual who provides funds for the development of software products and puts forward various requirements for the products. 3.4 Task undertaker refers to the unit or individual who purchases or selects software products. 3.5 User refers to the individual who uses the developed software. 3.6 Software development cycle refers to the time period from the determination of the requirements of a software product to the delivery of the product. This period generally includes: requirements analysis, design, implementation, test installation, acceptance and maintenance stages. 3.7 Compatibility refers to the measure of the interdependence between classes in a computer program. 3. B. Cover degree
The functional occupancy of the tasks performed by a single program module. 4. Overall requirements
The overall requirements of this specification include: demand analysis, design, implementation, testing, acceptance and documentation. But it does not include the feasibility of the software development project. Approved by the Ministry of Geology and Mineral Resources of the People's Republic of China on March 19, 1997 and implemented on November 1, 1997
Dz:T01691997
The report on the feasibility study report and the specific requirements of the project are used to formulate the requirements description sheet, and obtain the approval of Party H. It is the basis for the next stage of work of Party B. 4.2 Design
Party B shall make a detailed request and ensure that the design of the equipment fully meets all the requirements stipulated in the contract. No modification shall be made without the consent of the Chinese party. The design of the software shall be organized by the Chinese party. 2.3 Environmental
Party B shall design and program the software. When implementing the design, the design language shall be adopted (except for the specific requirements in the contract).
4.4 Testing
2 The equipment shall be tested in parallel. Unit testing is carried out in stages and then the acceptance test is completed. Accurate and complete test results are submitted: If the developed software is an important part of a system, it should participate in the system's record test. 4.5 Acceptance
Software acceptance must be carried out before formal, the software must meet the requirements specified in the contract, before acceptance, a software confirmation test must be completed. The test shall be carried out in a real network or simulated environment. 4.6 Documentation
Party B shall complete the specified documents and fully explain Party B's intentions during the confirmation process. The text used shall be plain and unambiguous. The company shall record the software scale and add content to the document. 5 Specific requirements
5.1 Requirements analysis
5. 1. 1 Task
Determine the operating environment, functions and performance requirements of the developed software, as well as user requirements and confirmation test criteria. Fire design and supply requirements specification
5.1.2 Content:
a! Investigate the operating environment of the software product to further clarify the requirements of the chip or user, h)
Analyze and formulate the best solution to achieve the above requirements, d
Determine the human-machine interface, and describe each function of the software in detail.
f) Formulate a test method: F It is good to write a user manual:
5.1.3 Requirements:
Must be based on the operating site
Must be designated by the square and personnel planning. b
1 The requirements specification must be clear and approved by the square: 5.7.4 Completion mark,
Effective component requirements specification.
b Confirmation test plan
) Input and output information agreement, including information source, receiving method, output method and related data attributes, such as time, space, format, meaning and operation, etc.,) User registration.
e! Party A agrees to take note.
5.2 Section design
5.2.1 Service
nz/T 0169- 1997
Party B must carry out the test according to the content specified in the soft requirement specification approved by the user, including the basic specifications, details, definition of each functional module, input, output, control interface and data interface design, etc. In the following stage, the software design book must be written as a basis: 5.2.2 Content
) Give a hierarchical structure in a strong order in the form of a diagram. b) Determine the functions, methods and data structures of the submodules and modules. Determine the control and data flows of the program under various operation modes. Determine the data exchange volume, frequency, format, and transfer requirements between the component and other systems. e) Develop a test plan: 5.2.3 Requirements: When designing the vehicle structure, new technologies should be used with care. The integration between the functional modules should be low, while the integration within each functional module should be high: the scope of the functional module should be within its control range: the interface efficiency of the module should be minimized to improve the integrability of the target system; pay attention to resource allocation and margin. For each submodule or module, the memory, input and output channel transmission capacity and processing time required by it must be determined, and there should be at least 10% margin. d) A code symbol must be defined to represent parameters and constants. The data file format should be unified so that they can be modified without changing the source logic. Parameters and variables should be coded according to the following standards: GR9649 Code for Geological Terminology GB/T14499 Technical Symbols for Geophysical Exploration GB/T14539 Geochemical Exploration Symbols DZ/T2 Geophysical and Geochemical Exploration Data File Format IT006 Geophysical Aid Diagram Format, Legend and Color Standard T>7/T005 Geochemical Exploration Diagram Format, Legend and Color Standard should be based on the national standards and industry standards for geophysical and geochemical exploration methods that have been published. Carefully consider the limitations of the language and supporting software used, and define external files and global data. 5.2.4 Completion Sign: a) All recognized software requirements are covered by the designed system. b) The structure of the program is established, and the functions of each module are clearly stated, the interface control characteristics of the module are clearly stated, and the algorithm and data structure in the module are determined. d) The specified documents are complete and verifiable. e) The design document has passed the market approval.
5.3 Implementation
5.3.1 Task
Convert the content description specified in the design into the source code written in the required programming language or database language. And perform program unit testing on the written program to verify the consistency of the program block interface and the design description. 5.3.2. In the following:
a) Write the program code according to the design specification and the specified programming language. ! In the head of the documentation and the developed program system, indicate the program name, developer, development time, program application scope, application environment and the specific physical and geochemical methods and principles of the data. 3. DZT0169-1997
C. For each item, the "previous" clause shall be used to list the key points, program units and data, and indicate their functions and their relative positions in the hierarchical logical structure.
d) The variable base and value agreement shall be made, and Keep these conventions consistent throughout the library. Focus on each program module, subroutine and unit header, describe the function, the input and output of other sequence components to be called, etc., and also annotate the key components in the sequence, determine the interface with other systems, and explain the interface between the client and the model. The method of achieving the desired sequence unit in the test case is compiled into a user manual.
5.3. 3. In addition to the language requirements required by the Japanese side, the framework language that meets the national and international standards should be used. 4. When programming, the corresponding programming language conventions should be followed. 5. The size of the cumulative error must be calculated to determine whether it meets the system's multi-level requirements. Before the test of the developed program unit, the system should complete the step-by-step inspection. During the test, it should be ensured that each executable code line is executed at least once. 6. In order to improve the readability and understandability of the program, Detailed comments should be made in the source code. [1] The program should reasonably handle and record the errors found during the operation of each program function. The error type should be described in the user manual.
5.3.4 Completion mark:
) The program can be run on the system
b) The documentation is complete: it can be verified
) Not only should test cases be provided for the correct implementation, but also test cases for the error types involved. 5.4 Testing
5. 4.1 Tasks
The company shall formulate a test plan according to the design requirements, conduct assembly test on the software, and submit a test report 5.4.2 Content
According to the description of each auxiliary module in the design and the formulated test plan, assemble and test the modules that have passed the single-light test one by one,
b) Then conduct tests with the corresponding geophysical and geochemical exploration model calculation and the specified test data. c) Analyze the test results, find out the cause of the error and make corrections to the code. d) Whether the user registers and works Manual, to check and verify the usability and effectiveness of the manual, and correct the errors in it. 5.4.3 Requirements: 1) The unit error is not correct through the editing details: 2) The membrane block is connected without error: 3) The function and performance design of each spray block are fully met. 4) The input/mountain processing of the system or subsystem meets the design requirements. 5) The input of the system or subsystem has the ability to detect and accommodate non-positive inputs. The human-machine interface is correct. 6) All equipment specified in the design can be connected and operated correctly. 7) Completion sign: 8) The test report meets the requirements, and the system software and software are executable (except those specified in the test document): 9) The final user manual and exploration manual.
5.5 Acceptance
55.1 Article
12/T0169-1997
At the time and place specified by the Chinese party, run all functions of the developed program system in the actual or simulated environment to prove that the system can operate normally.
5.5.2 Contents:
Installation, initialization and startup of the program according to the operation manual. Run all functions of the program according to the operation manual! Must accept the non-printed input data, and conduct a saturation test of the program's operating capacity, resource allocation and redundancy.
5.5.3 Requirements
Must be attended by both Party A and Party B.
h) An independent acceptance test team should be established to conduct confirmation testing and run all functions of the program to prove that the program has no errors. Force the program to run under its designed capacity limit, and do not exceed the limit to ensure that the system will not be damaged in the case of performance degradation at certain points.
) All expected results, test results and test data should be stored. 5.5.4 Completion or sign:
Write a report after the acceptance of the test.
6) Submit the documents specified in the contract to Party A, and make a development summary report. After the review organized by Party A,
d) Party A's acceptance document,
5.6 Real file
5. 6. 1 Clause:
At each stage of development work, formulate corresponding documents to ensure the smooth progress of new development work and the expected operation and maintenance 5.6.2 Content
Geophysical and chemical exploration software development should form the following documents a) Software requirements and development plan.
) Software design description
Software usage description (including operation manual and user manual), c
d) Test analysis report.
Project development summary.
Acceptance test report,
Review comments,
5.6.3 Requirements
Software requirements and development plans should include an overview of requirements, development tasks, and operating environment; as well as the responsible persons for the work during the development process, development progress, budget, hardware and software conditions, and confirmation test plans. b) The software design description should include the design plan of the program system, the basic flow of the program, the hierarchical structure, the module division, the function allocation, the interface design, the operation design, the data structure design, and the error handling design. c) The software usage description should use non-technical language to fully describe the functions of the software system, and provide operators with the specific process and relevant knowledge of each operation of the software, including the details of the operation method and the corresponding examples, so that users can quickly understand the usage of the software through the description.
d) Test analysis report records the nature, process and results of unit test and assembly test.
e) The development summary of the project should include the experience of the development work of this project, the actual development results and the evaluation of all aspects of the whole development work.
z/T169—1997
X) The acceptance report should contain the confirmation of the planned environment, the results, the conclusion of the software performance analysis, the evaluation, etc. The evaluation opinions should include the main achievements of the project, the problems and suggestions, the overall evaluation and the level achieved. 5.7 Maintenance
5.7.1:
Modify the software system after it is run to correct the errors generated in the development stage and not found in the operation stage, and check whether the software system can adapt to the environment and change, and realize the function expansion and performance improvement of the software system. 5.7.2: The user shall submit a "software problem report" based on the errors and time generated by the software system. The user shall also submit a "software modification report" to the security personnel, and modify or expand the program. Avoid testing the modified program library, modify all related operations, and provide the modified version for advertising: 5.7.3 Requirements: The program system must pass the test.It should be ensured that each executable source code line is executed at least once. e) To improve the readability and understandability of the program, detailed comments should be included in the source code. [) The program should reasonably handle and record the errors found during the operation of each program function. The error type should be described in the user manual.
5.3.4 Completion sign:
) The program can be run on the system
b) The documentation is complete and verifiable
|) Not only test cases should be provided for the correct specifications, but also test cases for the relevant error types. 5.4 Test 5.4.1 Task The company shall formulate a test plan according to the design requirements, conduct installation test on the software, and submit a test report 5.4.2 According to the description of each auxiliary module in the design and the formulated test plan, the modules that have passed the single-light test shall be assembled and tested one by one, and then the corresponding geophysical and geochemical exploration model calculation and the specified test data shall be tested. c) Analyze the test results, find out the cause of the error and make corrections to the code. d) According to the user manual and operation manual, check and verify the usability and effectiveness of the manual, and correct the errors. 5.4.3 Requirements: The unit is corrected by programming: The module is connected without error: The function and performance design of each injection block is completed. d) The input/processing of the system or subsystem meets the design requirements. i
It has the ability to detect and accommodate non-standard inputs. The human-machine interface is correct. All equipment specified in the design can be connected and operated correctly. 5.4.4 Completion sign: The test report meets the requirements, and the test report is completed. The system program can be operated (except those specified in the contract document): d: The final user manual and exploration manual. 5.5 Acceptance 55.1 Article 12/T0169-1997 At the time and place specified by the Chinese party, run all functions of the developed system in an actual or simulated environment to prove that the system can operate normally. 5.5.2 Content: Install, initialize and start the program through the operation manual. According to the operation manual, all functions of the program must be run! The user must receive the printed data from the project, and the operation capacity of the program must be allocated and the saturation test must be carried out. 5.5.3 requires that both Party A and Party B must participate in the test.
h) An independent acceptance test team should be established to conduct confirmation tests and run all functions of the program to prove that the program has no errors. The program will be forced to run under its designed capacity limit and exceed the limit to ensure that the system will not be damaged in the case of performance degradation.
) All expected results, test results and test data should be stored. 5.5.4 Completion or sign:
After the acceptance test, a report should be written.
6) The pilot should submit the documents specified in the contract to Party A, including the work summary report. After the review organized by Party A,
d) Party A's double-acceptance receipt,
5.6 Real File
5. 6. 1 Clause:
In each stage of development work, formulate corresponding documents to ensure the smooth progress of new development work and the expected operation and maintenance 5.6.2 Content
Geophysical and chemical exploration software development should form the following documents a) Software requirements and development plan.
) Software design description
Software usage description (including operation manual and user manual), c) Filter test analysis report.
Project development summary.
Acceptance test report,
Review comments,
5.6.3 Requirements
Software requirements and development plans should include an overview of requirements, development tasks, and operating environment; as well as the responsible persons for the work during the development process, development progress, budget, hardware and software conditions, and confirmation test plan. b) The software design description should include the design plan of the program system, the basic flow of the program, the layered structure, the module division, the function allocation, the interface design, the operation design, the data structure design, and the error handling design. c) The software usage instructions should use non-technical language to fully describe the functions of the software system, and provide operators with the specific process and relevant knowledge of each operation of the software, including the details of the operation method and the corresponding examples, so that users can quickly understand the usage of the software through the instructions.
d) The test analysis report records the nature, process, and results of the unit test and assembly test. e) The project development summary should include the experience of the project development work, the actual development results and the evaluation of all aspects of the whole development work.
z/T169—1997
X) The acceptance report should contain the confirmation of the planned environment, the results, the conclusion of the software performance analysis, the evaluation, etc. The evaluation opinions should include the main achievements of the project, the problems and suggestions, the overall evaluation and the level achieved. 5.7 Maintenance
5.7.1:
Modify the software system after operation to correct the errors generated in the development stage and not found in the operation stage, and check whether the software system can adapt to the environment and change, and realize the function expansion and performance improvement of the software system. 5.7.2: The user shall submit a "software problem report" based on the errors and time generated by the software system. The user shall also submit a "software modification report" to the security personnel, and modify or expand the program. Avoid testing the modified program library, modify all related operations, and provide the modified version for advertising: 5.7.3 Requirements: The program system must pass the test.It should be ensured that each executable source code line is executed at least once. e) To improve the readability and understandability of the program, detailed comments should be included in the source code. [) The program should reasonably handle and record the errors found during the operation of each program function. The error type should be described in the user manual.
5.3.4 Completion sign:
) The program can be run on the system
b) The documentation is complete and verifiable
|) Not only test cases should be provided for the correct specifications, but also test cases for the relevant error types. 5.4 Test 5.4.1 Task The company shall formulate a test plan according to the design requirements, conduct installation test on the software, and submit a test report 5.4.2 According to the description of each auxiliary module in the design and the formulated test plan, the modules that have passed the single-light test shall be assembled and tested one by one, and then the corresponding geophysical and geochemical exploration model calculation and the specified test data shall be tested. c) Analyze the test results, find out the cause of the error and make corrections to the code. d) According to the user manual and operation manual, check and verify the usability and effectiveness of the manual, and correct the errors. 5.4.3 Requirements: The unit is corrected by programming: The module is connected without error: The function and performance design of each injection block is completed. d) The input/processing of the system or subsystem meets the design requirements. i
It has the ability to detect and accommodate non-standard inputs. The human-machine interface is correct. All equipment specified in the design can be connected and operated correctly. 5.4.4 Completion sign: The test report meets the requirements, and the test report is completed. The system program can be operated (except those specified in the contract document): d: The final user manual and exploration manual. 5.5 Acceptance 55.1 Article 12/T0169-1997 At the time and place specified by the Chinese party, run all functions of the developed system in an actual or simulated environment to prove that the system can operate normally. 5.5.2 Content: Install, initialize and start the program through the operation manual. According to the operation manual, all functions of the program must be run! The user must receive the printed data from the project, and the operation capacity of the program must be allocated and the saturation test must be carried out. 5.5.3 requires that both Party A and Party B must participate in the test.
h) An independent acceptance test team should be established to conduct confirmation tests and run all functions of the program to prove that the program has no errors. The program will be forced to run under its designed capacity limit and exceed the limit to ensure that the system will not be damaged in the case of performance degradation.
) All expected results, test results and test data should be stored. 5.5.4 Completion or sign:
After the acceptance test, a report should be written.
6) The pilot should submit the documents specified in the contract to Party A, including the work summary report. After the review organized by Party A,
d) Party A's double-acceptance receipt,
5.6 Real File
5. 6. 1 Clause:
In each stage of development work, formulate corresponding documents to ensure the smooth progress of new development work and the expected operation and maintenance 5.6.2 Content
Geophysical and chemical exploration software development should form the following documents a) Software requirements and development plan.
) Software design description
Software usage description (including operation manual and user manual), c) Filter test analysis report.
Project development summary.
Acceptance test report,
Review comments,
5.6.3 Requirements
Software requirements and development plans should include an overview of requirements, development tasks, and operating environment; as well as the responsible persons for the work during the development process, development progress, budget, hardware and software conditions, and confirmation test plan. b) The software design description should include the design plan of the program system, the basic flow of the program, the layered structure, the module division, the function allocation, the interface design, the operation design, the data structure design, and the error handling design. c) The software usage instructions should use non-technical language to fully describe the functions of the software system, and provide operators with the specific process and relevant knowledge of each operation of the software, including the details of the operation method and the corresponding examples, so that users can quickly understand the usage of the software through the instructions.
d) The test analysis report records the nature, process, and results of the unit test and assembly test. e) The project development summary should include the experience of the project development work, the actual development results and the evaluation of all aspects of the whole development work.
z/T169—1997
X) The acceptance report should contain the confirmation of the planned environment, the results, the conclusion of the software performance analysis, the evaluation, etc. The evaluation opinions should include the main achievements of the project, the problems and suggestions, the overall evaluation and the level achieved. 5.7 Maintenance
5.7.1:
Modify the software system after operation to correct the errors generated in the development stage and not found in the operation stage, and check whether the software system can adapt to the environment and change, and realize the function expansion and performance improvement of the software system. 5.7.2: The user shall submit a "software problem report" based on the errors and time generated by the software system. The user shall also submit a "software modification report" to the security personnel, and modify or expand the program. Avoid testing the modified program library, modify all related operations, and provide the modified version for advertising: 5.7.3 Requirements: The program system must pass the test.4 Completion or sign:
Monitor the acceptance test and write a report.
6) Submit the documents specified in the contract to Party A, and make a development summary report. After the review organized by Party A,
d) Party A's acceptance document,
5.6 Real file
5. 6. 1 Clause:
In each stage of development work, formulate corresponding documents to ensure the smooth progress of new development work and the expected operation and maintenance 5.6.2 Content
Geophysical and chemical exploration software development should form the following documents a) Software requirements and development plan.
) Software design description
Software usage description (including operation manual and user manual), c) Test analysis report.
Project development summary.
Acceptance test report,
Review comments,
5.6.3 Requirements
Software requirements and development plans should include an overview of requirements, development tasks, and operating environment; as well as the responsible persons for the work during the development process, development progress, budget, hardware and software conditions, and confirmation test plan. b) The software design description should include the design plan of the program system, the basic flow of the program, the layered structure, the module division, the function allocation, the interface design, the operation design, the data structure design, and the error handling design. c) The software usage instructions should use non-technical language to fully describe the functions of the software system, and provide operators with the specific process and relevant knowledge of each operation of the software, including the details of the operation method and the corresponding examples, so that users can quickly understand the usage of the software through the instructions.
d) The test analysis report records the nature, process, and results of the unit test and assembly test. e) The project development summary should include the experience of the project development work, the actual development results and the evaluation of all aspects of the whole development work.
z/T169—1997
X) The acceptance report should contain the confirmation of the planned environment, the results, the conclusion of the software performance analysis, the evaluation, etc. The evaluation opinions should include the main achievements of the project, the problems and suggestions, the overall evaluation and the level achieved. 5.7 Maintenance
5.7.1:
Modify the software system after operation to correct the errors generated in the development stage and not found in the operation stage, and check whether the software system can adapt to the environment and change, and realize the function expansion and performance improvement of the software system. 5.7.2: The user shall submit a "software problem report" based on the errors and time generated by the software system. The user shall also submit a "software modification report" to the security personnel, and modify or expand the program. Avoid testing the modified program library, modify all related operations, and provide the modified version for advertising: 5.7.3 Requirements: The program system must pass the test.4 Completion or sign:
Monitor the acceptance test and write a report.
6) Submit the documents specified in the contract to Party A, and make a development summary report. After the review organized by Party A,
d) Party A's acceptance document,
5.6 Real file
5. 6. 1 Clause:
In each stage of development work, formulate corresponding documents to ensure the smooth progress of new development work and the expected operation and maintenance 5.6.2 Content
Geophysical and chemical exploration software development should form the following documents a) Software requirements and development plan.
) Software design description
Software usage description (including operation manual and user manual), c) Test analysis report.
Project development summary.
Acceptance test report,
Review comments,
5.6.3 Requirements
Software requirements and development plans should include an overview of requirements, development tasks, and operating environment; as well as the responsible persons for the work during the development process, development progress, budget, hardware and software conditions, and confirmation test plan. b) The software design description should include the design plan of the program system, the basic flow of the program, the layered structure, the module division, the function allocation, the interface design, the operation design, the data structure design, and the error handling design. c) The software usage instructions should use non-technical language to fully describe the functions of the software system, and provide operators with the specific process and relevant knowledge of each operation of the software, including the details of the operation method and the corresponding examples, so that users can quickly understand the usage of the software through the instructions.
d) The test analysis report records the nature, process, and results of the unit test and assembly test. e) The project development summary should include the experience of the project development work, the actual development results and the evaluation of all aspects of the whole development work.
z/T169—1997
X) The acceptance report should contain the confirmation of the planned environment, the results, the conclusion of the software performance analysis, the evaluation, etc. The evaluation opinions should include the main achievements of the project, the problems and suggestions, the overall evaluation and the level achieved. 5.7 Maintenance
5.7.1:
Modify the software system after operation to correct the errors generated in the development stage and not found in the operation stage, and check whether the software system can adapt to the environment and change, and realize the function expansion and performance improvement of the software system. 5.7.2: The user shall submit a "software problem report" based on the errors and time generated by the software system. The user shall also submit a "software modification report" to the security personnel, and modify or expand the program. Avoid testing the modified program library, modify all related operations, and provide the modified version for advertising: 5.7.3 Requirements: The program system must pass the test.
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.