T/ZASDI 0001-2023 Active Group standards

\nT/ZASDI 0001-2023 Military Software Java Language Programming Guide

T/ZASDI 0001-2023

Publish Date: 2024-09-18 Implement Date: 2024-10-01 For services related to genuine standard inquiry, procurement, translation, and other related services in China, please Contact Us

Price: $ 20.00

Out of stock

Basic Information

Standard Code: T/ZASDI 0001-2023

Standard Type: Group standards

Standard Status: Active

is_force_gb: no

CCS Name: -

ICS Name: Integrated Information Technology (IT)

Publish Date: 2024-09-18

Implement Date: 2024-10-01

Scope

Scope: This document specifies the rules for safe and standardized coding using the Java programming language. This document is applicable to military basic software written in Java, especially military safety-critical system basic software, and other military software can also refer to it for implementation. Each rule includes an identifier, a title, a rule description, a code example of non-compliance, and a code example of compliance. The identifier is a unique mnemonic for the rule, and the title is a concise but sometimes inaccurate description of the rule. The rule description specifies the normative requirements of the rule. The code example of non-compliance is a code example that violates the rule. The accompanying code example of compliance demonstrates code that follows the rules in this coding standard or any other equivalent rules. Main technical content: This coding standard consists of mandatory rules (requried rule) and advisory rules (advisory rule). Mandatory rules aim to provide normative requirements for code, and violating mandatory rules usually indicates a defect in the code; advisory rules aim to provide guidance, and following these guidelines should improve the security, reliability, and readability and maintainability of the software system. However, violating advisory rules does not necessarily indicate a defect in the code. Mandatory and advisory rules are collectively referred to as guidelines. Mandatory rules must meet the following conditions: 1. Violating this guideline may lead to a defect, which may adversely affect the security, reliability, or safety of the system, such as introducing a security flaw that could be exploited. 2. The guideline does not depend on source code annotations or assumptions. 3. Whether the guideline is met can be determined through automatic analysis (static or dynamic), formal methods, or manual review techniques. Advisory rules are recommendations for improving code quality. When all the following condi