HJ 622-2011 English PDFUS$1379.00 ยท In stock
Delivery: <= 8 days. True-PDF full-copy in English will be manually translated and delivered via email. HJ 622-2011: Technical specification for environmental protection applications development management Status: Valid
Basic dataStandard ID: HJ 622-2011 (HJ622-2011)Description (Translated English): Technical specification for environmental protection applications development management Sector / Industry: Environmental Protection Industry Standard Classification of Chinese Standard: Z07 Classification of International Standard: 13.020 Word Count Estimation: 53,566 Date of Issue: 2011-09-01 Date of Implementation: 2011-12-01 Quoted Standard: GB/T 16705-1996; GB/T 16706-1996; HJ/T 212; HJ/T 352-2007; HJ/T 416-2007; HJ/T 417-2007; HJ/T 418; HJ/T 419; GB/T 8566-2007; GB/T 8567-2006; GB/T 11457-2006; GB/T 15532; GB 17859-1999; GB/T 20282-2000; CH/T 1005-2000; CH/T 1007 - 2001 Regulation (derived from): Department of Environmental Protection Notice No. 62 of 2011 Issuing agency(ies): Ministry of Ecology and Environment Summary: This standard specifies the environmental management of application software development process required to follow the important work processes, management basic requirements and technical basic requirements. This standard applies to the Environmental Protection application software requirements development and management, outline design, detailed design, software implementation, software testing, software commissioning and acceptance, service and maintenance, user training and assessment, and other basic software development management activities. The main users of the environmental protection standard application software managers and developers. HJ 622-2011: Technical specification for environmental protection applications development management---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. Technical specification for environmental protection applications development management National Environmental Protection Standard of the People's Republic Environmental protection application software development management technical specification Technical specification for environmental protection applications Development management Published on.2011-09-01 2011-12-01 Implementation Ministry of Environmental Protection released ContentForeword.ii 1 Scope 1 2 Normative references 1 3 Terms and Definitions..1 4 Environmental Protection Application Software Development Process. 2 5 Environmental Protection Application Software Requirements Development and Management Process..2 6 Environmental Protection Application Software Overview Design Process..6 7 Environmental Protection Application Software Detailed Design Process..8 8 Environmental Protection Application Software Implementation Process..10 9 Environmental Protection Application Software Testing Process..12 10 Environmental Protection Application Software Trial Operation and Acceptance Process..14 11 Environmental Protection Application Software Service and Maintenance Process 16 12 Environmental Protection Application User Training Process. 18 13 Environmental Protection Application Software Review Process 19 Appendix A (informative) Sample of the User Needs Survey Form template..22 Appendix B (informative) Sample User Templates 23 Appendix C (informative appendix) Sample Request for Change Request Template 27 Appendix D (informative) The "Summary Design Specification" template sample is wrong! No bookmarks are defined. Appendix E (informative) Sample of the detailed design specification template 31 Appendix F (informative) Sample of the Software Implementation Plan template.33 Appendix G (informative) Code of Practice 34 Appendix H (informative appendix) "Code Walkthrough Record" template example..38 Appendix I (informative) Sample of the Unit Test Record Sheet.39 Appendix J (informative appendix) "User Feedback Information Form" template example.41 Appendix K (informative) Sample of the Deployment Parameter List template 43 Appendix L (informative) Sample User Acceptance Report template.44 Appendix M (informative) Sample Service and Maintenance Record template..45 Appendix N (informative) Sample User Template Confirmation Form..46 Appendix O (informative) Sample of the Review Plan template..48 Appendix P (informative) Sample of the Review Report template 49ForewordTo implement the Environmental Protection Law of the People's Republic of China, standardize the management process of environmental protection application software development, and promote This process is developed in the process of environmental informationization. This standard specifies the development process of environmental protection application software and the technical management requirements of the development process. Appendix A, Appendix B, Appendix C, Appendix D, Appendix E, Appendix F, Appendix G, Appendix H, Appendix I of this standard, Appendix J, Appendix K, Appendix L, Appendix M, Appendix N, Appendix O, and Appendix P are informative annexes. This standard was first published. This standard was formulated by the Science and Technology Standards Department of the Ministry of Environmental Protection. This standard was drafted. Institute of Remote Sensing Applications, Chinese Academy of Sciences, Zhongke Yutu Tianxia Technology Co., Ltd., Beijing Division Fan University. This standard was approved by the Ministry of Environmental Protection on September 1,.2011. This standard has been implemented since December 1,.2011. This standard is explained by the Ministry of Environmental Protection. Environmental protection application software development management technical specification1 Scope of applicationThis standard specifies the important work processes and basic management requirements to be followed in the process of environmental protection application software development and management. And basic technical requirements. This standard applies to environmental protection application software for demand development and management, summary design, detailed design, software implementation, Basic software development management activities such as software testing, software commissioning and acceptance, service and maintenance, user training and review. The main users of this standard are environmental protection application software managers and developers.2 Normative referencesThe contents of this standard refer to the terms in the following documents. For undated references, the valid version applies to this standard. GB/T 16705-1996 environmental pollution category code GB/T 16706-1996 Environmental pollution source category code HJ/T 212 pollution source online automatic monitoring (monitoring) system data transmission standard HJ/T 352-2007 Environmental Pollution Automatic Monitoring Information Transmission and Exchange Technical Specification HJ/T 416-2007 Environmental Information Terminology HJ/T 417-2007 Environmental Information Classification and Code HJ/T 418 Environmental Information System Integration Technical Specification HJ/T 419 Environmental Database Design and Operation Management Specification GB/T 8566-2007 information technology software life cycle process GB/T 8567-2006 computer software documentation specification GB/T 11457-2006 Information Technology Software Engineering Terminology GB/T 15532 computer software unit test GB 17859-1999 Computer Information System Security Protection Level Division Guidelines GB/T 20282-2006 Information Security Technology Information System Security Engineering Management Requirements CH/T 1005-2000 Basic Geographic Information Digital Product Data File Naming Rules CH/T 1007-2001 Basic Geographic Information Digital Product Metadata3 Terms and definitionsGB/T 8566-2007, GB/T 11457-2006, HJ/T 416-2007 and HJ/T 419 as defined in the following terms and The definition applies to this standard. 3.1 environmental protection application software environmental protection applications software Collect, aggregate, organize, process, store, classify, retrieve, calculate, compare, judge, and rank environmental information Operation such as sequence and output, providing information management and sharing, decision support, auxiliary execution, and effect for environmental management and research work Software for feedback and other services. 3.2 development process A set of related activities performed for a given purpose during software development. 3.3 non-functional requirement Requirements other than functional requirements in user requirements, such as reliability, efficiency, ease of use, etc. 3.4 software product software product A set of computer programs, procedures, and possibly related documents and data.4 Environmental protection application software development processAccording to the software life cycle process definition specified in GB 8566-2007, it is required to implement environmental protection application software development. process. The environmental protection application software development process can be divided into the following nine processes. -- Environmental protection application software requirements development and management process; -- Environmental protection application software summary design process; -- Detailed design process for environmental protection application software; -- Environmental protection application software implementation process; -- Environmental protection application software testing process; -- Trial operation and acceptance process of environmental protection application software; -- Environmental protection application software service and maintenance process; -- Environmental protection application software user training process; -- Environmental protection application software review process. Entry criteria that are not specifically stated in each process are reviewed documents.5 Environmental protection application software requirements development and management process5.1 Entry criteria The Software Development Plan (implemented in accordance with GB/T 8567-2006) has passed the review. The requirements developer has been identified. 5.2 Requirements Development and Management Process The requirements development and management process should include pre-investigation preparation, requirements research, requirements analysis, writing user requirements specifications, User needs review, user needs confirmation, software requirements analysis, writing software requirements specification, software requirements review, Important activities such as demand change control, the main work flow is shown in Figure 1. requesting research demand analysis User needs review User demand confirmation User Requirements "User Needs Survey Form" User Requirements Manual Software requirement definition Software Requirements Review "Software Requirements Specification" Contract technical annex Whether the review passed Whether the review passed End of demand analysis Solution or proposal Preparation before research Start Demand change Figure 1 Flow chart of requirements development and management process 5.3 Main steps 5.3.1 Preparation before investigation The developer shall determine the time and demand for the investigation and obtain relevant stakeholders, and complete the user according to the selected research method. Prepare for the Demand Survey (see Appendix A). The main contents of the User Needs Survey Form should include. the name of the respondent, the time, location, and background of the user. Information, demand information records, reliability and support information, and the use of existing environmental protection application software. 5.3.2 Demand research The developer should adjust according to the interview outline and research plan through prototype method, conference, interview, questionnaire survey, etc. Check and fill out the User Needs Survey Form as the original user requirement. Users should cooperate with the completion of the needs survey. This phase of the survey can include the following. a) the organizational structure of the environmental management department and the responsibilities of each functional department; b) information construction environment, including operating system platform, database system, hardware network, constraints on the system, Dependence of the construction of this system; c) Existing environmental information system, including software name, purpose, development unit, development language, and saved phase Relevant technical documentation, online time, usage, scope of use, department of use, department responsible, person in charge, Operating environment, existing data, secondary development interface, maintenance, etc. d) construction of similar software projects; e) the software positioning and expansion requirements; f) business scope, workflow, data involved and business issues that need to be resolved through the software, may involve construction Project approval management, environmental administrative punishment management, environmental petition management, environmental monitoring management, pollution source monitoring Management, ecological protection management, nuclear safety and radiation management, environmental emergency management, environmental protection e-government, etc.; g) the input and processing of each business and the roles and outputs involved in the environmental protection business; h) the definition of the environmental data center, the data items involved, and the business issues that need to be addressed through the data center; i) the current status and needs of space technology applications, as well as spatial data requirements; j) software information security status, requirements, level protection or hierarchical protection requirements; k) The need for environmental protection website construction. 5.3.3 Demand Analysis According to the demand survey results, the developer should analyze the user requirements and write the User Requirements Specification (see Appendix B), User Needs Survey Form is attached to the User Requirements Manual. 5.3.4 Writing User Requirements Specification The main contents of the User Requirements Manual should include. description of the business status (organization structure and functions, job definition, industry) Service process, forms and reports, problems, etc.), software function requirements (can be divided into several modules for explanation), software non Functional requirements (user interface, interface requirements, performance requirements, and other requirements). If the prototype method is applied for demand research, it should be fully reflected in the corresponding content of the User Requirements Manual. Type-confirmed user interface requirements, functional requirements, and interaction requirements with the system. At this stage you should also pay attention to. a) the relationship with existing environmental protection application software; b) how future business data is integrated into the environmental data center and how it is processed; c) the relevant provisions of the State and the Ministry of Environmental Protection on relevant business processes, such as radioactive source management and pollution source monitoring; d) security mechanisms, including system identity authentication, database security, network security requirements, etc.; e) use of the population, including the level of computer knowledge, the definition of the role of use in the business, etc.; f) Data exchange interface between the environmental protection department and other relevant administrative departments. 5.3.5 User Needs Review The developer shall review the User Requirements Specification in accordance with the requirements of Chapter 13 of this standard. 5.3.6 User Needs Confirmation User requirements should be validated by the user. After the developer submits the request for confirmation of the application, the user says "user demand" The contents of the book shall be confirmed in a timely manner without objection, and the construction period shall be confirmed in the total project duration (excluding the service and maintenance period). Within 10% range. The confirmation methods include. signature verification of the requirements document, signature verification of the needs review meeting minutes, confirmation of the official letter, etc. The way the two sides can agree. 5.3.7 Software Requirements Analysis The developer shall conduct a demand analysis according to the "User Requirements Manual" to form a mapping of user requirements to software requirements. Into the "Software Requirements Specification." 5.3.8 Writing Software Requirements Specification The main contents of the Software Requirements Specification (implemented in accordance with GB/T 8567-2006) should include. an overview of requirements, Requirements specifications (system overall functional requirements), detailed functional requirements (can be divided into several parts), non-functional requirements. 5.3.9 Software Requirements Review The developer shall review the Software Requirements Specification in accordance with the requirements of Chapter 13 of this standard. Software needs The specification should be approved by the reviewer. 5.3.10 Demand Change Control Changes in demand should be analyzed, confirmed, and subject to change control. The demand change control process is shown in Figure 2. Change analysis Change approval Implement changes Request for Change of Requirements Change implementation review Whether the approval passed Whether the review passed End Submit a change request Start Request for Change of Requirements Request for Change of Requirements Figure 2 Environmental protection application software requirements change control flow chart Implementation requirements changes should meet the following requirements. a) Submit the change request. The change proposer (user, developer, etc.) should submit the change request and write Application for Change of Requirements (see Appendix C). The main content of the Request for Change of Requirements should include. Reasons, content, impact analysis on other tasks, impact analysis on the project, signature of the applicant, change Approval of signature, etc.; b) Change analysis. The developer should analyze the content of the demand change request, and the analysis content should include. the scope of influence, Content, technical solutions, project impact, risk, cost, workload, etc. Developers and users should analyze the content Agree; c) Change approval. The change of requirements shall be validated by the joint signature of the user and the developer; d) Implementation changes. Changes can only be implemented after the requirements change approval has been approved. The developer should change the change according to the change impact analysis All relevant content within the scope of influence will be changed accordingly, and if necessary, the requirements development should be re-established. recognize; e) Change implementation review. After the implementation of the change is completed, the developer and the user should organize the review team to review the changes. Review or test to ensure that the changes are correct and the versions of the revised work results correspond to each other; f) Change of the construction period. the time required to submit the change application to the completion of the change approval should be in the total project duration (excluding service and Maintenance period) within 5% range. 5.4 output "User Needs Survey Form", "User Requirements Manual", "Software Requirements Specification", "Demand Change Request" Please book.6 Environmental Protection Application Software Overview Design Process6.1 Entrance criteria Software Requirements Specification. 6.2 Environmental Protection Application Software Overview Design Process The outline design process should include. outline design preparation, identify constraints that affect software design, determine design strategies, Important activities such as outline design, writing summary design documents, and summary design review. The main workflow is shown in Figure 3. Summary Design Specification Software Requirements Specification Identify impact software design Constraint factor Determining design strategy Write a summary design document Summary design review Whether the review passed Outline design End Outline design preparation Design start Outline design Figure 3 Environmental protection application software summary design flow chart 6.3 Main steps 6.3.1 Outline design preparation The developer's design preparation work should include. a) Read the requirements document to clarify the design tasks; b) assign software design tasks, including software architecture, data structures, logic flows, etc.; c) Prepare relevant design tools and materials. 6.3.2 Identify constraints that affect software design The developer should extract the requirements constraints from the requirements document, which may include. standard or specification constraints, software and hardware environments (packages) Incl......Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of HJ 622-2011_English be delivered?Answer: Upon your order, we will start to translate HJ 622-2011_English as soon as possible, and keep you informed of the progress. The lead time is typically 5 ~ 8 working days. The lengthier the document the longer the lead time.Question 2: Can I share the purchased PDF of HJ 622-2011_English with my colleagues?Answer: Yes. The purchased PDF of HJ 622-2011_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 Sales@ChineseStandard.net. 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. |
