SJ 20567-1996 Command Automation System Application Software Interface Requirements

SJ 20567-1996 Command Automation System Application Software Interface Requirements SJ20567-1996 Standard Download Decompression Password: www.bzxz.net

Military Standard of the Electronic Industry of the People's Republic of China FL0134
SJ20567-96
Requirements for application softwareinterface of command automation system1996-08-30Published
1997-01-01Implementation
Approved by the Ministry of Electronics Industry of the People's Republic of China1 Scope
1.1 Subject content
1.2 Scope of application
2 Reference documents
3 Definition
3.1 System software
3.2 Application software
3.3 Interface
4-General requirements
4.1 Parallelism
4.2 Interface design
5 Detailed requirements
5.1 Interface for input and output information
5.2 Interface between application software and system hardware platform5.3 Interface between application software and system software platform5.4 Data communication and network protocol
5.5 User interface requirements
5.6 Interface between application software of each subsystem5.7 Interface between application software and monitoring subsystem5.8 Management and interface of shared data area
5.9 Program structure management and interface
5.10 Testing and maintenance of application software interface5.11 Application software interface design document
+++ (1)
…(2)
… (2)
TYKAONKACa-
People's Republic of China Electronic Industry Military Standard Requirements for application software interface of command automation system1 Scope
1.1 Subject content
SI 20567-96
This standard specifies the requirements for the design, testing, maintenance and documentation of various interfaces of the application software of the command automation system (hereinafter referred to as the system).
1.2 Scope of application
This standard applies to all stages of system application software development 2 Reference documents
GJB 437--88
GJB 438—88
GJB 439--88
GJB 701. 6—89
GIB 804-90
GIB 842—90
GJB 873--91
GJB 1839—93
GJB 1845—93
GJB 1893--94
Military software development specifications
Military software documentation specifications
Military software quality assurance specifications
Technical conditions for ground intelligence processing and transmission systems Radar intelligence format requirements Military code set for information exchange (basic set) Naval standard Automated command system display code Command automation Military map tiling and coding Vehicle digital map element attribute coding
Ship command control system display code
Automated command system message exchange format
Central Military Commission Office document on the issuance of the Chinese People's Liberation Army's official document handling regulations [1992 No. 16·
3.1 System softwaresystem software
Software for managing computer system resources.
3.2 Application softwareapplicationsoptwareSoftware for solving problems that belong to a special field and are not computer problems. 3.3 Interface
Interface relations and conventions between system functional units. General requirements
The Ministry of Electronics Industry of the People's Republic of China Issued on August 30, 1996 and implemented on January 1, 1997
4.1 Open communication
SI 20567 --96
The development and operation of application software should be carried out in an open system environment, and the interface design and arrangement must meet the requirements of open system portability, interoperability, standardization and configurability. 4.1.1 Portability
The interface design of application software should have the portability of application programs and data to improve the reusability of application software. 4.1.2 Interoperability
The interface design of application software should provide network interconnection, information intercommunication and user interoperability for various systems.
4.1.3 Standardization
To achieve system interoperability and software portability, the application software interface design should comply with the standard requirements specified by the system. 4.1.4 Configurability
To adapt to different system environments and different functional combination requirements, the application software interface design should adapt to the modularization and tailorability requirements of the software.
4.2 Interface design
4.2.1 Design requirements
: The application software interface design must be functionally consistent with the system requirements: b. The interface design of application software should have a unified interface and information network (communication interface, programming interface, user interface, etc.);
The interface design of application software should have a unified system management and stock management; c.
d. The interface definition must be reasonable, accurate and strict; the interface data conversion must be complete and accurate; e.
. The interface specification complies with the standardized communication protocol: human-machine interface is friendly, Chinese, flexible, simple to operate, and has consistency and reliability. 4.2.2 Design content
At each stage of application software development, the content of interface design must be carried out in accordance with the requirements of the relevant clauses of military standards GIB437, GJ438 and GJB439. Its main contents are as follows: a: physical interface relationship and logical interface relationship; h, data transmission medium or system characteristics:
transmission code, format, rate and error control, etc.; c
d, data reliability and security and confidentiality requirements; application software interface type:
r. Application software interface mode;
Interface communication protocol.
5 Detailed requirements
5.1 Interface for input and output information
5.1.1 The input information processed by the system application software includes intelligence information (radar intelligence, sonar intelligence, technical reconnaissance intelligence, navigation intelligence, meteorological intelligence, electronic warfare intelligence, early warning aircraft intelligence and battlefield intelligence, etc.); command and control information (combat orders, instructions, requests, reports, battlefield situation, weapon control, etc.) and business processing information. The input information forms include: datagrams (formatted and unformatted), graphics, images, voice input, etc.
TTTKAONTKAca
SJ20567-96
5.1.2 The output information processed by the system application software includes comprehensive intelligence information (reporting, notification, broadcasting): command and control orders and instructions: weapon control instructions and local output and display (information required for commanders' decision-making and staff operations). The output information forms include: datagram (format and non-format), graphics, images, voice, display (graphics, images and character display), record, drawing and copy, etc.
The systems shall be implemented in accordance with the provisions of GJB701.6. The combat document format shall be uniformly implemented in accordance with the official document format specified in GIB1893 and [1992] No. 6. When there is no unified national and military standard to follow, the system engineering construction specification shall be formulated or the format actually used by the troops shall be adopted.
5.1.3 All input and output information shall have confidentiality and security measures. 5.2 Interface between application software and system hardware platform 5.2.1 Interface of computer system
The interface design of application software shall meet the requirements of system hardware platform environment. 5.2.2 Management interface of computer input and output devices The management interface of computer input and output devices is realized through input and output primitives and device management functions. These primitives and functions include: creating files, deleting files, establishing channels, opening files, closing files, reading files, writing files, setting control parameters and testing device status, etc. For general-purpose input and output devices, their management and interfaces should be specified according to the services provided by the adopted standard operating system; for special-purpose external devices, their management and interfaces should be designed and specified according to the functional requirements and with reference to the general-purpose equipment section.
5.2.3 Communication controller interface
a. The application software controls and sets the channel parameter values, such as protocol, rate, check mode, character length, stop bit, synchronization mode and channel enable/disable, etc.;
h. The application program uses function call or procedure call, and is applicable to a variety of high-level language program calls or assembler program calls;
Data exchange should adopt a high-speed and reliable method, such as the shared storage area method; c.
d. The application program should be able to receive and process the device status report, link status report and error report of the communication controller; e. The communication protocol should comply with the specified standards. 5.3 Interface between application software and system software platform 5.3.1 System software selection
a. The design of application software interface should meet the requirements of system software platform environment; b. Application software should be reasonably designed under the control of operating system, and the application operating system should provide functions such as system scheduling, storage management, I/O management, and process management. 5.4 Data communication and network protocol
a: According to the requirements of the effective system, the ()SI international standard proposed by IS) is adopted as the system network architecture standard. The TCP/IP series protocols actually used can be used as a transitional agreement to gradually transition to products that fully comply with OSI standards; h. For systems with high requirements for real-time data transmission, data should be transmitted on the lower layer of the network; C. Network transmission should be point-to-point and point-to-point. For multi-point and broadcast functions. d. The application software needs to design packaging, unpacking software and sending/receiving software as needed, and call through the interface library of the reverse connection network;
e. When networking with an existing system, if the docking requirements are inconsistent, it should be negotiated and resolved separately, but the agreement should comply with the requirements of this standard;
5.5 User interface requirements
5.5.1 Management and maintenance
SJ20567-96
a: The system startup command should be safe, reliable, simple and easy to operate. After the system is fully checked and generated, it will be automatically transferred to the application software for installation and operation;
h. Users can understand the operation of system equipment and software through monitoring and other means, and can display and take necessary control:
c. Abnormalities occur during the operation of application software Or when a fault occurs, it can automatically report and record, and automatically restore normal operation; d. The system should provide an application software maintenance interface. 5.5.2 Human-machine interface
The human-machine interface is a tool for people and machines to communicate. The human-machine interface between the system application software and the end-user operator is achieved through the display console or seat (including keyboard, display, model ball, mouse, touch screen, light pen, language, etc.) large screen, various terminals, telephones and digital air defense stations to interact with the system. a. The application software interface should support a variety of human-machine interaction methods; b. The command console should display various target movement tracks, solution plans, various background maps, self-standard movement and solution plan parameters, as well as various command and control, document and telecommunication information. Its air situation map, sea situation map, battlefield situation map, and background map should implement the following military Standards: GJB804, GJB842, GJB873, GJB1839 and GJB1845; c: Manual intervention commands are the main form of human-computer dialogue. The design of manual intervention commands should be powerful, user-friendly, safe and reliable, ensure the consistency of the human-computer interface, and have good troubleshooting and fault tolerance: d. All kinds of human-computer interaction information should be recorded and archived for future reference. 5.6 Interfaces between application software of each subsystem 5.6.1 Use control flow as interface relationship
When the software of each subsystem is running on the same computer, the control flow should be the main interface relationship. When designing, the agreement and provisions of the interface information should be formulated for the sharing of computer resources (storage area, I/0 channel, processing power, terminal, etc.), program control (process or job scheduling method). bzxz.net
5.6.2 Use information to transform into interface relationship
When the application software of each subsystem runs on different computers, the interface relationship should be based on information exchange (including intelligence information). The agreement on information content and format should be formulated during software design. Information exchange is generally carried out through a local network or a remote network. If necessary, information exchange can also be carried out through direct communication between two computers. 5.7 Interface between application software and monitoring subsystem When designing application software, it is necessary to clearly define what information is provided to the monitoring subsystem and what control information is obtained from the monitoring subsystem. 5.8 Management and interface of shared data area
The data in the shared data area is shared by multiple processes, multiple modules or multiple processors. When designing the program, the management and interface of the shared data area must be explained.
5.8.1 Access method
Dynamic shared data areas can be accessed by setting up read and write pointers for each process to access. 5.8.2 Sharing Control
In order to maintain the consistency of shared data, there must be sharing control measures, which can be specifically agreed upon according to the control measures and interface methods provided in the operating system, such as the use of shielded interrupt method, waiting queue method, semaphore operation method, etc. 5.8.3 Access Permissions
Establish different access rights and priority permissions for access order for each process to write, read, organize and modify shared data areas.
HTKAONTKAca
5.9 Program Structure Management and Interface
5.9.1 Management and Interface of Static Program StructureSJ20567-96
5. The program structure in the design and compilation and linking process is called static program structure. The static structure is divided into four levels, namely program, subprogram, module and program unit. The interface relationship of static program structure is mainly module interface and sequence unit interface; h. When designing application software, we must first determine the hierarchical system, information flow, connection relationship and calling rules between modules of application software:
c. Specify the functional interface, control interface, data interface and abbreviation connection interface of each module; d. In the description part of the program unit, the input, output, call parameters, return result and abnormal information of this program unit are described.
e. The division of sequence structure and the determination of its interface must meet the system function requirements, smooth information flow, and ensure the rationality of internal interface settings.
5.9.2 Management and interface of dynamic program structure The program structure in the running process or control sequence is called dynamic program structure. The dynamic program structure is to divide the application into many processes. In process management, the interface between application software and operating system, the interface between process and shared data area, and the interface between processes must be described. In application software design, the process management and interface must be clearly specified according to the process primitives and functions and their parameters provided by the adopted operating system. 5.10 Testing and maintenance of application software interface Testing and maintenance of application software interface is an important part of application software testing and maintenance. In order to ensure the correctness and feasibility of interface design, the application software must be tested by unit or module, subsystem integrated test and system integrated test, and the results shall be recorded in the test report.
5.11 Documentation of application software interface design
a. According to the content and format required by GIB438, documents such as software requirement description, outline design description, detailed design description, operation manual, test plan, test analysis report, etc. shall all contain relevant content of application software interface; b. According to the requirements of GJIB437, the "Interface Design Description" document shall be written during the application software development stage. Its content and writing format can be formulated according to the actual needs of different systems. Additional notes:
This standard is under the jurisdiction of China Electronics Technology Standardization Institute, and this standard was drafted by the 218th Institute of the Ministry of Electronics Industry. The main drafters of this standard are: Jin Anqi, Cui Songrui, Yu Wenya, Mao Yifu, Xia Gongxie. Project code: B33032.4 Data communication and network protocol
a: According to the requirements of the effective system, the ()SI international standard proposed by IS) is adopted as the system network architecture standard. The TCP/IP series of protocols actually adopted can be used as a transitional agreement to gradually transition to products that fully comply with OSI standards; h, for systems with high requirements for real-time data transmission, data should be transmitted on the lower layer of the network; C network transmission should have point-to-point, point-to-multipoint and broadcast functions. d, application software needs to design packaging, unpacking software and sending/receiving software as needed, and call through the interface library of the reverse connection network;
e. When networking with an existing system, if the requirements for the docking door are inconsistent, they should be resolved through negotiation and agreed upon separately, but the agreement should comply with the requirements of this standard;
5.5 User interface requirements
5.5.1 Management and maintenance
SJ20567-96
a: The system startup command should be safe, reliable, simple and easy to operate. After the system is fully checked and generated, it should be automatically transferred to the application software for installation and operation;
h. Users can understand the operation of system equipment and software through monitoring and other means, and can display and take necessary control:
c. When an abnormality or failure occurs during the operation of the application software, it can automatically report and record, and automatically restore normal operation; d. The system should provide an application software maintenance interface. 5.5.2 Human-machine interface
The human-machine interface is a tool for human-machine dialogue. The human-machine interface between system application software and end-user operators is realized through display consoles or seats (including keyboards, display screens, model balls, mice, touch screens, light pens, languages, etc.), large screens, various terminals, telephones, and digital air defense stations. a. The application software interface should support multiple human-machine interaction methods; b. The command console should display various target movement tracks, solution schemes, various background maps, self-standard movement and solution scheme parameters, and various command and control, document and telegraphic information. Its air situation map, sea situation map, battlefield situation map, and background map should comply with the following military standards: GJB804, GJB842GJB873.GJB1839 and GJB1845; c. The manual intervention command is the main form of human-machine dialogue. The design of the manual intervention command should be powerful, user-friendly, safe and reliable, ensure the consistency of the human-machine interface, and have good troubleshooting and fault tolerance: d. All kinds of human-computer interaction information should be recorded and archived for future reference. 5.6 Interfaces between application software of each subsystem 5.6.1 Using control flow as interface relationship
When the application software of each subsystem runs on the same computer, the control flow should be the main interface relationship. When designing, the agreements on computer resource (storage area, I/O channel, processing capacity, terminal, etc.) sharing, program control (process or job scheduling method) and interface information regulations should be formulated.
5.6.2 Using information transformation as interface relationship
When the application software of each subsystem runs on different computers, the information exchange (including intelligence information) should be used as the interface relationship. When designing the software, the agreements on information content and format should be formulated. Information exchange is generally carried out through a local network or a remote network. If necessary, information exchange can also be carried out through direct communication between two computers. 5.7 Interface between application software and monitoring subsystem When designing application software, it should be clear what information to provide to the monitoring subsystem and what control information to obtain from the monitoring subsystem. 5.8 Management and interface of shared data area
The data in the shared data area is shared by multiple processes, multiple modules or multiple processors. When designing the program, the management and interface of the shared data area must be explained.
5.8.1 Access method
Dynamic shared data area can be accessed by setting up read and write pointers for each process to use. 5.8.2 Shared control
In order to maintain the consistency of shared data, there must be shared control measures, which can be specifically agreed upon according to the control measures and interface methods provided in the operating system, such as the use of shielded interrupt method, waiting queue method, semaphore operation method, etc. 5.8.3 Access authority
Establish different access rights and priority of access order for each process to write, read, organize and modify the shared data area.
HTKAONTKAca
5.9 Program structure management and interface
5.9.1 Management and interface of static program structureSJ20567-96
5. The program structure in the process of design, compilation and connection is called static program structure. The static structure is divided into four levels, namely program, subprogram, module and program unit. The interface relationship of the static program structure is mainly module interface and sequence unit interface; h. When designing application software, we must first determine the application software's hierarchical system, information flow, connection relationship and calling rules between modules:
c. Specify the functional interface, control interface, data interface and abbreviation connection interface of each module; d. In the description part of the program unit, describe the input, output, call parameters, return results and exception information of this program unit
e. The division of program structure and the determination of its interface must meet the system function requirements, ensure the smooth flow of information, and ensure the rationality of internal interface settings.
5.9.2 Management and interface of dynamic program structure The program structure during operation or in the control sequence is called dynamic program structure. The dynamic program structure divides the application into many processes. The interface between the application software and the operating system, the interface between the process and the shared data area, and the interface between processes must be explained in process management. In the application software design, the process management and interface must be clearly specified based on the process primitives and functions and their parameters provided by the adopted operating system. 5.10 Testing and maintenance of application software interfaces Testing and maintenance of application software interfaces are important contents of application software testing and maintenance. In order to ensure the correctness and feasibility of interface design, the application software must be tested by unit or module, subsystem integration test and system integration test, and the results must be recorded in the test report.
5.11 Documentation of application software interface design
a. According to the content and format required by GIB438, documents such as software requirements description, outline design description, detailed design description, operation manual, test plan, test analysis report, etc. should all contain relevant content of the application software interface; b. According to the requirements of GJIB437, the "Interface Design Description" document should be compiled during the application software development stage. Its content and format can be formulated according to the actual needs of different systems. Additional notes:
This standard is under the jurisdiction of the China Electronics Technology Standardization Institute and was drafted by the 218th Institute of the Ministry of Electronics Industry. The main drafters of this standard are Jin Anqi, Cui Songrui, Yu Wenya, Mao Yifu, and Xia Gongxie. Project code: B33032.4 Data communication and network protocol
a: According to the requirements of the effective system, the ()SI international standard proposed by IS) is adopted as the system network architecture standard. The TCP/IP series of protocols actually adopted can be used as a transitional agreement to gradually transition to products that fully comply with OSI standards; h, for systems with high requirements for real-time data transmission, data should be transmitted on the lower layer of the network; C network transmission should have point-to-point, point-to-multipoint and broadcast functions. d, application software needs to design packaging, unpacking software and sending/receiving software as needed, and call through the interface library of the reverse connection network;
e. When networking with an existing system, if the requirements for the docking door are inconsistent, they should be resolved through negotiation and agreed upon separately, but the agreement should comply with the requirements of this standard;
5.5 User interface requirements
5.5.1 Management and maintenance
SJ20567-96
a: The system startup command should be safe, reliable, simple and easy to operate. After the system is fully checked and generated, it should be automatically transferred to the application software for installation and operation;
h. Users can understand the operation of system equipment and software through monitoring and other means, and can display and take necessary control:
c. When an abnormality or failure occurs during the operation of the application software, it can automatically report and record, and automatically restore normal operation; d. The system should provide an application software maintenance interface. 5.5.2 Human-machine interface
The human-machine interface is a tool for human-machine dialogue. The human-machine interface between system application software and end-user operators is realized through display consoles or seats (including keyboards, display screens, model balls, mice, touch screens, light pens, languages, etc.), large screens, various terminals, telephones, and digital air defense stations. a. The application software interface should support multiple human-machine interaction methods; b. The command console should display various target movement tracks, solution schemes, various background maps, self-standard movement and solution scheme parameters, and various command and control, document and telegraphic information. Its air situation map, sea situation map, battlefield situation map, and background map should comply with the following military standards: GJB804, GJB842GJB873.GJB1839 and GJB1845; c. The manual intervention command is the main form of human-machine dialogue. The design of the manual intervention command should be powerful, user-friendly, safe and reliable, ensure the consistency of the human-machine interface, and have good troubleshooting and fault tolerance: d. All kinds of human-computer interaction information should be recorded and archived for future reference. 5.6 Interfaces between application software of each subsystem 5.6.1 Using control flow as interface relationship
When the application software of each subsystem runs on the same computer, the control flow should be the main interface relationship. When designing, the agreements on computer resource (storage area, I/O channel, processing capacity, terminal, etc.) sharing, program control (process or job scheduling method) and interface information regulations should be formulated.
5.6.2 Using information transformation as interface relationship
When the application software of each subsystem runs on different computers, the information exchange (including intelligence information) should be used as the interface relationship. When designing the software, the agreements on information content and format should be formulated. Information exchange is generally carried out through a local network or a remote network. If necessary, information exchange can also be carried out through direct communication between two computers. 5.7 Interface between application software and monitoring subsystem When designing application software, it should be clear what information to provide to the monitoring subsystem and what control information to obtain from the monitoring subsystem. 5.8 Management and interface of shared data area
The data in the shared data area is shared by multiple processes, multiple modules or multiple processors. When designing the program, the management and interface of the shared data area must be explained.
5.8.1 Access method
Dynamic shared data area can be accessed by setting up read and write pointers for each process to use. 5.8.2 Shared control
In order to maintain the consistency of shared data, there must be shared control measures, which can be specifically agreed upon according to the control measures and interface methods provided in the operating system, such as the use of shielded interrupt method, waiting queue method, semaphore operation method, etc. 5.8.3 Access authority
Establish different access rights and priority of access order for each process to write, read, organize and modify the shared data area.
HTKAONTKAca
5.9 Program structure management and interface
5.9.1 Management and interface of static program structureSJ20567-96
5. The program structure in the process of design, compilation and connection is called static program structure. The static structure is divided into four levels, namely program, subprogram, module and program unit. The interface relationship of the static program structure is mainly module interface and sequence unit interface; h. When designing application software, we must first determine the application software's hierarchical system, information flow, connection relationship and calling rules between modules:
c. Specify the functional interface, control interface, data interface and abbreviation connection interface of each module; d. In the description part of the program unit, describe the input, output, call parameters, return results and exception information of this program unit
e. The division of program structure and the determination of its interface must meet the system function requirements, ensure the smooth flow of information, and ensure the rationality of internal interface settings.
5.9.2 Management and interface of dynamic program structure The program structure during operation or in the control sequence is called dynamic program structure. The dynamic program structure divides the application into many processes. The interface between the application software and the operating system, the interface between the process and the shared data area, and the interface between processes must be explained in process management. In the application software design, the process management and interface must be clearly specified based on the process primitives and functions and their parameters provided by the adopted operating system. 5.10 Testing and maintenance of application software interfaces Testing and maintenance of application software interfaces are important contents of application software testing and maintenance. In order to ensure the correctness and feasibility of interface design, the application software must be tested by unit or module, subsystem integration test and system integration test, and the results must be recorded in the test report.
5.11 Documentation of application software interface design
a. According to the content and format required by GIB438, documents such as software requirements description, outline design description, detailed design description, operation manual, test plan, test analysis report, etc. should all contain relevant content of the application software interface; b. According to the requirements of GJIB437, the "Interface Design Description" document should be compiled during the application software development stage. Its content and format can be formulated according to the actual needs of different systems. Additional notes:
This standard is under the jurisdiction of the China Electronics Technology Standardization Institute and was drafted by the 218th Institute of the Ministry of Electronics Industry. The main drafters of this standard are Jin Anqi, Cui Songrui, Yu Wenya, Mao Yifu, and Xia Gongxie. Project code: B33032.2 Use information to transform into interface relationship
When the application software of each subsystem runs on different computers, the interface relationship should be based on information exchange (including intelligence information). Agreements on information content and format should be formulated during software design. Information exchange is generally carried out through a local network or a remote network. If necessary, information exchange can also be carried out through direct communication between two computers. 5.7 Interface between application software and monitoring subsystem When designing application software, it is necessary to clearly define what information is provided to the monitoring subsystem and what control information is obtained from the monitoring subsystem. 5.8 Management and interface of shared data area
The data in the shared data area is shared by multiple processes, multiple modules or multiple processors. When designing the program, the management and interface of the shared data area must be explained.
5.8.1 Access method
Dynamic shared data areas can be accessed by setting up read and write pointers for each process to use. 5.8.2 Sharing Control
In order to maintain the consistency of shared data, there must be sharing control measures, which can be specifically agreed upon according to the control measures and interface methods provided in the operating system, such as the use of shielded interrupt method, waiting queue method, semaphore operation method, etc. 5.8.3 Access Permissions
Establish different access rights and priority permissions for access order for each process to write, read, organize and modify shared data areas.
HTKAONTKAca
5.9 Program Structure Management and Interface
5.9.1 Management and Interface of Static Program StructureSJ20567-96
5. The program structure in the design and compilation and linking process is called static program structure. The static structure is divided into four levels, namely program, subprogram, module and program unit. The interface relationship of static program structure is mainly module interface and sequence unit interface; h. When designing application software, we must first determine the hierarchical system, information flow, connection relationship and calling rules between modules of application software:
c. Specify the functional interface, control interface, data interface and abbreviation connection interface of each module; d. In the description part of the program unit, the input, output, call parameters, return result and abnormal information of this program unit are described.
e. The division of sequence structure and the determination of its interface must meet the system function requirements, smooth information flow, and ensure the rationality of internal interface settings.
5.9.2 Management and interface of dynamic program structure The program structure in the running process or control sequence is called dynamic program structure. The dynamic program structure is to divide the application into many processes. In process management, the interface between application software and operating system, the interface between process and shared data area, and the interface between processes must be described. In application software design, the process management and interface must be clearly specified according to the process primitives and functions and their parameters provided by the adopted operating system. 5.10 Testing and maintenance of application software interface Testing and maintenance of application software interface is an important part of application software testing and maintenance. In order to ensure the correctness and feasibility of interface design, the application software must be tested by unit or module, subsystem integrated test and system integrated test, and the results shall be recorded in the test report.
5.11 Documentation of application software interface design
a. According to the content and format required by GIB438, documents such as software requirement description, outline design description, detailed design description, operation manual, test plan, test analysis report, etc. shall all contain relevant content of application software interface; b. According to the requirements of GJIB437, the "Interface Design Description" document shall be written during the application software development stage. Its content and writing format can be formulated according to the actual needs of different systems. Additional notes:
This standard is under the jurisdiction of China Electronics Technology Standardization Institute, and this standard was drafted by the 218th Institute of the Ministry of Electronics Industry. The main drafters of this standard are: Jin Anqi, Cui Songrui, Yu Wenya, Mao Yifu, Xia Gongxie. Project code: B33032.2 Use information to transform into interface relationship
When the application software of each subsystem runs on different computers, the interface relationship should be based on information exchange (including intelligence information). Agreements on information content and format should be formulated during software design. Information exchange is generally carried out through a local network or a remote network. If necessary, information exchange can also be carried out through direct communication between two computers. 5.7 Interface between application software and monitoring subsystem When designing application software, it is necessary to clearly define what information is provided to the monitoring subsystem and what control information is obtained from the monitoring subsystem. 5.8 Management and interface of shared data area
The data in the shared data area is shared by multiple processes, multiple modules or multiple processors. When designing the program, the management and interface of the shared data area must be explained.
5.8.1 Access method
Dynamic shared data areas can be accessed by setting up read and write pointers for each process to use. 5.8.2 Sharing Control
In order to maintain the consistency of shared data, there must be sharing control measures, which can be specifically agreed upon according to the control measures and interface methods provided in the operating system, such as the use of shielded interrupt method, waiting queue method, semaphore operation method, etc. 5.8.3 Access Permissions
Establish different access rights and priority permissions for access order for each process to write, read, organize and modify shared data areas.
HTKAONTKAca
5.9 Program Structure Management and Interface
5.9.1 Management and Interface of Static Program StructureSJ20567-96
5. The program structure in the design and compilation and linking process is called static program structure. The static structure is divided into four levels, namely program, subprogram, module and program unit. The interface relationship of static program structure is mainly module interface and sequence unit interface; h. When designing application software, we must first determine the hierarchical system, information flow, connection relationship and calling rules between modules of application software:
c. Specify the functional interface, control interface, data interface and abbreviation connection interface of each module; d. In the description part of the program unit, the input, output, call parameters, return result and abnormal information of this program unit are described.
e. The division of sequence structure and the determination of its interface must meet the system function requirements, smooth information flow, and ensure the rationality of internal interface settings.
5.9.2 Management and interface of dynamic program structure The program structure in the running process or control sequence is called dynamic program structure. The dynamic program structure is to divide the application into many processes. In process management, the interface between application software and operating system, the interface between process and shared data area, and the interface between processes must be described. In application software design, the process management and interface must be clearly specified according to the process primitives and functions and their parameters provided by the adopted operating system. 5.10 Testing and maintenance of application software interface Testing and maintenance of application software interface is an important part of application software testing and maintenance. In order to ensure the correctness and feasibility of interface design, the application software must be tested by unit or module, subsystem integrated test and system integrated test, and the results shall be recorded in the test report.
5.11 Documentation of application software interface design
a. According to the content and format required by GIB438, documents such as software requirement description, outline design description, detailed design description, operation manual, test plan, test analysis report, etc. shall all contain relevant content of application software interface; b. According to the requirements of GJIB437, the "Interface Design Description" document shall be written during the application software development stage. Its content and writing format can be formulated according to the actual needs of different systems. Additional notes:
This standard is under the jurisdiction of China Electronics Technology Standardization Institute, and this standard was drafted by the 218th Institute of the Ministry of Electronics Industry. The main drafters of this standard are: Jin Anqi, Cui Songrui, Yu Wenya, Mao Yifu, Xia Gongxie. Project code: B33032.
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.