CN111045718A - Software suitable for airworthiness management of civil airborne equipment - Google Patents
Software suitable for airworthiness management of civil airborne equipment Download PDFInfo
- Publication number
- CN111045718A CN111045718A CN201911218828.3A CN201911218828A CN111045718A CN 111045718 A CN111045718 A CN 111045718A CN 201911218828 A CN201911218828 A CN 201911218828A CN 111045718 A CN111045718 A CN 111045718A
- Authority
- CN
- China
- Prior art keywords
- requirement
- verification
- file
- physical address
- function
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses software suitable for airworthiness management of civil airborne equipment, and provides a numbering rule and a physical address formulation rule: the serial number can be used for identifying the name of the airborne system to which the demand belongs and identifying the level of the demand in the product composition; the method comprises the steps that information such as storage addresses, requirement version numbers, requirement file names, serial numbers of each requirement in requirement files, requirement verification results and the like in a server according to requirements are combined into physical addresses of requirements for software to use, each requirement is provided with an independent physical address, the server resolves the requirement serial numbers after receiving equipment requirement requests to obtain corresponding physical addresses, reads link relations and requirement contents of the equipment airworthiness requirements, function requirements, verification requirements and verification results from the physical addresses and returns the link relations and the requirement contents to a client. The invention solves the problems of difficult requirement tracing management and difficult requirement change management of civil airborne equipment such as airworthiness, function, verification and the like.
Description
Technical Field
The invention belongs to the field of design and development of avionic devices, and relates to software suitable for airworthiness management of civil airborne equipment.
Background
The civil airborne equipment (hereinafter referred to as equipment for short) must meet the requirement of the airworthiness standard, and can be installed and used on the airplane. In order to enable the equipment to meet the requirements specified by airworthiness standards, the main steps in the process of designing and developing the equipment are as follows:
the need to determine the airworthiness requirements of the device (safety requirements),
determining a device composition architecture for the device,
determining the functional requirements of the components making up each hierarchy of the device,
determining the validation requirements (compliance) of the various levels that make up the device,
device design and manufacturing implementation (including writing software code, completing complex electronic hardware design),
the device is verified to see if it meets airworthiness requirements, among other requirements.
These operations constitute the main activities of airworthiness management.
The key point of the equipment design and development is to effectively manage and control various requirements (hereinafter referred to as requirements for short) including airworthiness requirements, functional requirements and verification requirements in the whole process of design and development, and ensure that:
all the requirements have been correctly implemented into the device design, and evidence is provided to prove that the design meets the requirements specified,
all requirements have been fulfilled by the correct manufacturing, and evidence is provided to demonstrate that the manufacturing meets the approved design requirements,
all requirements are correctly verified and evidence is provided to prove compliance with airworthiness requirements.
The equipment generally has a multilayer composition, the requirements such as airworthiness and the like need to be transmitted and realized step by step, and the equipment composition level is shown in a table 1.
To achieve these three goals, comprehensive retrospective management of the included requirements must be implemented to confirm that the requirements have been properly delivered, properly resolved, properly implemented, and properly verified. To achieve these four objectives, according to the current working method, there are the following difficulties:
1. and the requirement tracing management is difficult.
The reason why the demand tracing management is difficult:
the required quantity is large: generally, each demand can be decomposed into a plurality of demands, and the number of the demands is greatly increased after the demands are transmitted, decomposed and derived and expanded from top to bottom.
The number of required documents is large: the carriers needing to be stored are various documents, the quantity of the required documents is increased, and the quantity of the documents is also increased.
The remote distribution of the requirement documents: the device development is team collaborative work, and the requirement documents are distributed in different computers, so that the linkage between the requirement documents is difficult.
FIG. 1 shows the requirement propagation decomposition process during the design process. The left block shows the decomposition and transmission of the requirement from top to bottom, and the right block shows the verification and confirmation work completed by the requirement from bottom to top. The requirement on the left side and the verification confirmation on the right side need to establish a link for tracing, and the decomposition transmission from top to bottom and the verification confirmation from bottom to top also need to establish a link for tracing.
2. The management of the change of the demand is difficult.
The reasons why the demand change management is difficult are:
the requirement change impact domain is difficult to determine: a requirement change may affect a plurality of requirements, a plurality of software codes and a specific design implementation method, synchronous updating is needed, and synchronous change between requirement-requirement document-verification results is difficult to achieve manually.
The requirement document location is difficult: the requirements are distributed in different chapters of the document, the document is stored in different documents, the document is stored in different computers, and the requirements cannot be accurately and quickly positioned and displayed depending on manpower.
Due to the difficulty in retrospective management and requirement change of requirements, the development of equipment is easy to have major defects, and the safety of the airplane is adversely affected.
Disclosure of Invention
The invention aims to provide software suitable for airworthiness management of civil airborne equipment, which establishes physical mapping relations among various levels of airworthiness requirements of the equipment, various requirement documents and computers by using physical addresses, realizes the remote decomposition, transmission, decomposition, derivation and linkage of requirements, and inquires requirement traceability, positioning requirements and displays requirement contents by using requirement numbers; and inquiring and displaying the influence range of the requirement change (influenced requirement, verification result and document).
The invention aims to be realized by the following technical scheme:
a software suitable for airworthiness management of civil airborne equipment comprises a qualification approval basic management module, a functional requirement management module, a verification requirement management module, a retrospective query module and an equipment composition setting module;
the equipment composition setting module: providing a human-computer operation interface for completing the hierarchical arrangement of equipment by a user according to the equipment composition;
a qualification approval base management module: providing a man-machine operation interface for a user to formulate and edit a qualified approval basic file and qualified approval basic terms contained in a qualified approval basic management file, and generating a first physical address for storing the qualified approval basic file and the qualified approval basic terms in a server, wherein the first physical address consists of an IP address of the server, the name of the qualified approval basic file, the version number of the qualified approval basic file and the serial number of the qualified approval basic terms;
the function requirement management module: providing a human-computer operation interface of a user defined function requirement file, and generating a second physical address of the function requirement file stored in the server; the function requirement file records the function requirement of a certain level of a product and the link relation between the function requirement and the function requirement of the previous layer, and the second physical address consists of the IP address of the server, the name of the function requirement file, the version number of the function requirement file, the function requirement number and the corresponding second physical address of the function requirement file of the previous layer;
a verification requirement management module: providing a human-computer operation interface for defining a verification requirement file and a verification result file by a user, and generating a third physical address for storing the verification requirement file in the server and a fourth physical address for storing the verification result file in the server; the verification requirement document records a verification requirement of a certain level of equipment and a link between the verification requirement and a function requirement of a corresponding level; the verification result file records a verification result corresponding to a certain level of verification requirements of the equipment and a link between the verification result and the corresponding verification requirements and function requirements; the third physical address consists of an IP address, a verification requirement file name, a verification requirement file version number, a verification requirement number and a second physical address of a corresponding hierarchical function requirement file; the fourth physical address consists of the IP address of the server, the name of the verification requirement file, the version number of the verification requirement file, the verification requirement number, the second physical address of the corresponding functional requirement, the name of the verification result file and the position of the verification result file in the server;
a traceability query module: sending a request for inquiring equipment seaworthiness requirement traceability, function requirement traceability or verification requirement traceability, which is provided by a user, to a server, and displaying a link relation and corresponding requirement content of returned corresponding equipment seaworthiness requirements, function requirements, verification requirements and verification results; after receiving a request for inquiring the seaworthiness requirement traceability, the function requirement traceability or the verification requirement traceability of the equipment, the server resolves the numbering information of the seaworthiness requirement, the function requirement and the verification requirement of the equipment to obtain a corresponding first physical address, a corresponding second physical address, a corresponding third physical address and a corresponding fourth physical address, reads the linking relation and the requirement content of the seaworthiness requirement, the function requirement, the verification requirement and the verification result of the equipment from the first physical address, the second physical address, the corresponding third physical address and the corresponding fourth physical address, and returns the inquiry result to the client.
And further, the system also comprises a project basic attribute management module which is used for finishing the management of the cooperative work computer network and setting different operation authorities of personnel.
Drawings
FIG. 1 is a schematic demand decomposition diagram.
Fig. 2 is a schematic diagram of an operating environment of software suitable for airworthiness management of civil airborne equipment.
FIG. 3 is a diagram illustrating a tree structure of a demand.
FIG. 4 is a device top level verification requirements creation interface diagram (level T1).
FIG. 5 is a diagram of a device top-level verification requirements decomposition delivery interface.
FIG. 6 is a T2 level verification requirement creation interface diagram.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples.
When the civil airborne equipment is subjected to airworthiness management, the equipment development computers need to be interconnected by using a network and configured into a server + client architecture.
Referring to fig. 2, the server is mainly used for storing the requirement file and the verification result; executing the query instruction sent by the client; and inquiring the retrospective relation of the requirement and sending the complete content of the requirement to the client operation interface for displaying.
The software suitable for airworthiness management of the civil airborne equipment, which is shown in the embodiment, runs on a client and is mainly used for providing a human-computer operation interface; establishing and editing a requirement document; link requirements and validation results; sending an instruction for inquiring the traceability of the demand; displaying the link relation and the requirement content of the requirement and the verification result; the scope of influence of the change in demand (influenced demand, verification result, relevant document) is determined and displayed.
In order to solve the problems of difficult demand tracing management and difficult demand change, the embodiment designs a demand numbering rule and a demand physical address rule, generates a demand number according to a coding rule, and gives each demand a unique physical address. The requirement number can identify the name of an airborne system to which the requirement belongs, identify the level of the requirement in product composition, and inquire all superior requirements, all subordinate requirements, all associated verification requirements and verification results of the requirement by utilizing the number and combining an algorithm. The coding field is composed as follows (an example is shown, showing a coding method):
| FUN/VAL/SAFE | -a multi-bit number | -a multi-bit number | -a multi-bit number | -a multi-bit number | -a multi-bit number |
An example of encoding: FUN-31-002-.
The physical address rule of the requirement is a physical address of the requirement used by software, which is formed by combining information such as a storage address, a requirement version number, a requirement name, a serial number of each requirement in a requirement file, a verification result and the like in the server according to the requirement, so that each requirement has an independent physical address, the software queries the physical address, and reads the requirement information stored in the physical address.
The software suitable for airworthiness management of the civil airborne equipment, shown in the embodiment, includes a qualification base management module, a functional requirement management module, a verification requirement management module, a traceability query module, an equipment composition setting module, and a project basic attribute management module.
The equipment composition setting module: and providing a man-machine operation interface for completing the hierarchical arrangement of the equipment by a user according to the equipment composition.
A qualification approval base management module: and providing a man-machine operation interface for a user to formulate and edit the qualified approval basic file and the qualified approval basic clause contained in the qualified approval basic management file, and generating a first physical address for storing the qualified approval basic file and the qualified approval basic clause in the server, wherein the first physical address consists of an IP address of the server, the name of the qualified approval basic file, the version number of the qualified approval basic file and the number of the qualified approval basic clause.
The function requirement management module: providing a human-computer operation interface of a user defined function requirement file, and generating a second physical address of the function requirement file stored in the server; the function requirement file records the function requirement of a certain level of a product and the link relation between the function requirement and the function requirement of the previous layer, and the second physical address consists of the IP address of the server, the name of the function requirement file, the version number of the function requirement file, the function requirement number and the corresponding second physical address of the function requirement file of the previous layer.
A verification requirement management module: providing a human-computer operation interface for defining a verification requirement file and a verification result file by a user, and generating a third physical address for storing the verification requirement file in the server and a fourth physical address for storing the verification result file in the server; the verification requirement document records a verification requirement of a certain level of equipment and a link between the verification requirement and a function requirement of a corresponding level; the verification result file records a verification result corresponding to a certain level of verification requirements of the equipment and a link between the verification result and the corresponding verification requirements and function requirements; the third physical address consists of an IP address, a verification requirement file name, a verification requirement file version number, a verification requirement number and a second physical address of a corresponding hierarchical function requirement file; the fourth physical address is composed of the IP address of the server, the name of the verification requirement file, the version number of the verification requirement file, the verification requirement number, the second physical address of the corresponding function requirement, the name of the verification result file and the position of the verification result file in the server.
A traceability query module: sending a request for inquiring equipment seaworthiness requirement traceability, function requirement traceability or verification requirement traceability, which is provided by a user, to a server, and displaying a link relation and corresponding requirement content of returned corresponding equipment seaworthiness requirements, function requirements, verification requirements and verification results; after receiving a request for inquiring the seaworthiness requirement traceability, the function requirement traceability or the verification requirement traceability of the equipment, the server resolves the numbering information of the seaworthiness requirement, the function requirement and the verification requirement of the equipment to obtain a corresponding first physical address, a corresponding second physical address, a corresponding third physical address and a corresponding fourth physical address, reads the linking relation and the requirement content of the seaworthiness requirement, the function requirement, the verification requirement and the verification result of the equipment from the first physical address, the second physical address, the corresponding third physical address and the corresponding fourth physical address, and returns the inquiry result to the client.
And the project basic attribute management module is used for finishing the management of the cooperative work computer network and setting different operation authorities of personnel.
The operation of the software suitable for the airworthiness management of the civil onboard equipment is explained below.
Step one, the setting of an integrated working environment is completed.
The integrated working environment is based on networked computers (including servers) and the software is installed on the computers needing cooperative work, and the computers with the software constitute the integrated airworthiness working environment for many people to work in different places. One computer is manually designated as a server and the other computers are clients. After setting, the software uses the physical addresses (IP addresses) of the server and the client to realize the communication between the computers.
After software is started, the operation interfaces of all the clients are the same, and the software interfaces comprise a qualified approval basic term management area, a function requirement definition area, a verification requirement definition area, a requirement link inquiry area, a requirement change management area, an equipment composition structure tree setting area and a project basic attribute setting area. FIG. 2 is a schematic illustration of a collaborative work environment.
And step two, establishing a qualified approval basic file.
A qualification base document is composed of a plurality of standard terms. The interface provided by the qualification base management module is provided with icons for creating a new qualification base file and editing the qualification base file.
Newly building a qualified approval base file: clicking an icon of a newly-built qualified approval base file on a client, designating an area in a server by a qualified approval base management module to store the qualified approval base file, then giving an input area (a window) of the qualified approval base file in a client interface, wherein an icon of 'newly-added standard terms' is arranged in the input area, after clicking the icon, generating a qualified approval base standard term text input box by software, manually inputting applicable airworthiness standards (such as CCAR21 and CCAR25), airworthiness standard term numbers (such as 25.1309.1) and airworthiness standard contents in the text input box, wherein each newly-built text box can only input one airworthiness regulation term, clicking a 'confirmation' button after inputting, completing writing of an approval term base and storing the written approval term base in the server. Repeatedly inputting a plurality of airworthiness regulation and terms to form a qualified approval basic document.
Editing a qualified approval base file: when the newly-built qualified approval base file is edited, the 'icon for editing the qualified approval base file' needs to be clicked, the qualified approval base management module automatically generates a duplicate file of the qualified approval base file, and a new version number is given to the duplicate file so as to keep a difference with the former qualified approval base file.
Then, the existing list of the qualified basic file appears on the client interface, and the file to be edited is selected, so that a working area (window) for editing the qualified basic file appears in the interface, and all standard terms of the file are listed in the window. In the window, there are operation options of "add standard clause newly", "delete standard clause", and "edit standard clause". And after clicking the 'newly added standard term', a text input box for the qualified approval basic standard term appears, and the corresponding operation is completed. If a certain standard term is selected and 'edit standard term' is selected, a text input box for qualification approval basic standard term appears, and all information of the term appears in the input box and can be edited. If a certain marked clause is selected and the 'deleting standard clause' is selected, the certain standard clause can be deleted. And after all the input is finished, sending a storage instruction to finish the editing operation.
The content format of the text box is shown in table 2.
And (3) qualified approval of basic file version control: the qualification base (file) can be edited in the management module, and the software automatically generates a new version of qualification base file after finishing editing every time, and the software is forbidden to cover the original file.
And (3) avoiding cooperative work conflict: the method comprises the steps that an automatic detection conflict avoiding mechanism is established in a qualification approval basic file, after a client inputs a standard name and a standard term number of a certain qualification approval basis, software immediately judges keywords such as the standard name and the airworthiness regulation term number, judges whether the keywords are overlapped with the existing airworthiness approval basis or not, and if the keywords are overlapped, a conflict reminding window is given out on an interface to remind people to intervene conflicts (the same qualification basis term is not input at the same time).
Forming a physical address of the approval basic clause: after the input is confirmed, the qualification base management module generates a first physical address of the qualification base term according to the IP address of the computer (server) where the qualification base term is located, the name of the qualification base document, the version number of the qualification base document and the number of the qualification base term, wherein the first physical address is the physical address of a storage unit in the storage space in the server. After the mapping relation between the physical address and the name of the qualified approval basic document and the version number of the qualified approval basic document is established, the server can find the first physical address of the qualified approval basic term according to the number of the approved basic term and the information of the name of the qualified approval basic term document in the query instruction, and can return the information such as the content of the approved basic term to the client after querying the information.
And (3) checking the content of the qualified basic document: and after the airworthiness clauses are completely input, clicking the file name, and checking the complete content of the qualified basic file through a text format.
Traceability of basic terms of query and approval: the retrospective query of the qualification approval basic terms has two modes, namely an upward query method and a downward query method. The upward query method is to trace back the qualified basic document (document with a specific version number) and the specific terms of the approval foundation in the server where the qualified basic document is located according to the top-level requirements of the equipment. The downward inquiry method is to inquire all the requirement files linked with the money, all the requirements linked with the money and all the requirement verification results linked with the money from the specific qualification base clause.
Step three, defining and linking the device T1 level requirements.
And in the function demand management module, the top-level function demand of the equipment is formulated according to the qualified approval basic file, the user demand and the applicable industry standard.
Creating a device top-level function requirement file: a device top-level requirements text entry box appears in the interface, the text box content format being shown in table 3.
Manually inputting each function requirement item by item in the text input box, and completing the setting of function requirement sources, wherein the attribute to be considered for setting the function requirement sources comprises the following attributes:
is there a corresponding basis for qualification? If so, the number of the terms of the approval base must be input, a link is established with the approval base,
is it a user request? If yes, the file name, the file version number and the clause number of the requirement in the file containing the content required by the user must be input;
is it derived from industry standards? If yes, the name, version number and the item number of the relevant content in the standard of the industry standard must be input;
whether it originates from other files: if the file name exists, the file version number, the file release organization name, the file release date and other information need to be input.
Device top level requirement file version: the top-level function requirement file (file) of the equipment can be edited in the function requirement management module, and the version number of the top-level function requirement file of a new version is generated after each editing is completed, so that the original file is forbidden to be covered.
And (3) avoiding cooperative work conflict: and the function demand management module judges whether a plurality of persons input or edit the same equipment top layer demand file simultaneously according to the name and the edition of the top layer function demand file, and if so, a conflict reminding window is displayed to remind the person to intervene the conflict.
Forming a physical address of a top-level requirement clause of the device: after the text box is input and confirmed, the function requirement management module generates a second physical address of the equipment top-level requirement clause according to the IP address of the computer (server) where the equipment top-level requirement file is located, the equipment top-level requirement file name, the equipment top-level requirement file version number and the equipment top-level requirement number, wherein the second physical address is used for requirement inquiry and positioning.
And viewing the content of the device top-level requirement file: after all the required contents are input, the file name is clicked, and the complete contents of the file can be viewed through a text format (all the required physical addresses in one file are continuous).
Querying the device top level requirement traceability: there are three ways for retrospective query, which are an upward query, a downward query, and a total query. The upward query method is to address the server where the qualified approval base file is located according to the top-level requirement of the equipment, trace back to the approval base file (specific version number) and trace back to the specific terms of the approval base. The downward inquiry method is that according to a specific requirement clause, all the requirement files of all levels linked with the item, all the requirements of all the levels linked with the item and all the requirement verification results of all the levels linked with the item are inquired downward. All the query rules are a combination of the up-query method and the down-query method.
Step four, defining and linking the verification requirements of the device T1 level.
And creating a top-level verification requirement file in a verification requirement management module, automatically importing the top-level verification requirement file into top-level function requirements, displaying a top-level function requirement list on an interface, manually selecting each top-level function requirement in sequence, and starting an equipment top-level requirement verification requirement input text box (the interface structure is shown in a table 4). Table 4 is a content format schematic of the text box. And manually inputting a verification requirement (a concrete method for conformity) corresponding to each functional requirement in the text input box.
Each top-level function requirement may have multiple top-level verification requirements, and a one-to-many mapping relationship exists, and links need to be established.
Verifying the requirement file version at the top layer of the equipment: the verification requirement management module can edit the equipment top verification requirement file (file), and the equipment top verification requirement file generates a new version of the top verification requirement file version number after each time of editing is completed.
And (3) avoiding cooperative work conflict: and the verification requirement management module judges whether a plurality of persons input or edit the same equipment top verification requirement file simultaneously according to the name and the version number of the top verification requirement file, and if so, a conflict reminding window is displayed to remind that manual intervention conflict is needed.
Physical address of the verification requirement clause at the top layer of the forming equipment: after the input confirmation, the verification requirement management module generates a third physical address of the device top layer verification requirement according to the IP address of the computer (server) where the device top layer verification requirement file is located, the device top layer verification requirement file name, the device top layer verification requirement file version number, the device top layer verification requirement number and the corresponding device top layer requirement physical address, wherein the third physical address is used for requirement query positioning.
Checking the content of the requirement file on the top layer of the equipment: and after all the required contents are input, clicking the file name, and checking the complete contents of the file in a text format.
Verifying requirement traceability at the top layer of the query device: there are three ways for retrospective query, which are an upward query, a downward query, and a total query. The upward query method is to address a server where the top-level requirement of the device is located through the top-level verification requirement of the device, trace back to the top-level requirement (specific version number) of the device, and trace back to the specific terms of the top-level requirement of the device. The downward inquiry method is to inquire down all the verification results linked with the item according to a specific verification requirement item. All the query rules are a combination of the up-query method and the down-query method.
And step five, defining and linking the requirements of the device T2 level.
Creating a T2 level function requirement file in the function requirement management module, automatically importing the T2 level function requirement file into the top level function requirement (T1 level) of the equipment, displaying a top level function requirement list in an interface, then manually selecting each top level function requirement in turn, starting a T2 level function requirement input text box, wherein the interface structure is shown in figure 5. Table 5 is a content format schematic of the text box. In the text input box, the T2 level function requirement corresponding to each top-level function requirement is manually input.
After a requirement is input, software automatically generates and gives a unique physical address to the requirement, and the software can inquire and locate any T2-level functional requirement and display the source information of the requirement.
After all the requirement input is finished, the requirement file can be viewed in a text form.
Device level T2 function requirements file version: the T2 level function requirement file can be edited in the function requirement management module, and each time the editing is completed, the T2 level function requirement (file) generates a new version of the version number of the function requirement file.
And (3) avoiding cooperative work conflict: when a plurality of persons input or edit the same T2-level function requirement file at the same time, the software interface displays a conflict reminding window for reminding that manual intervention conflict is needed.
Physical address of functional requirement clause of forming device level T2: after the input confirmation, the function requirement management module generates a second physical address of the T2-level function requirement file according to the IP address of the computer (server) where the T2-level function requirement file is located, the name of the T2-level function requirement file, the version number of the T2-level function requirement file, the T2-level function requirement number and the corresponding second physical address of the T1-level function requirement file, wherein the second physical address is used for requirement query positioning.
View device T2 level functional requirements file content: and after the functional requirement content is completely input, clicking the file name, and checking the complete content of the file in a text format.
Querying device T2 level functional requirement traceability: there are three ways for retrospective query, which are an upward query, a downward query, and a total query. The query-up method is that through T2 level functional requirements of the device, the server where the top-level requirements of the device corresponding to the requirements are located is addressed up, and the top-level requirements (specific version number) of the device are traced back to specific terms of the top-level requirements of the device. The query-down method is to query down all the lower-level functional requirements linked with the item, and all the verification requirements and verification results according to a specific T2-level functional requirement clause. All the query rules are a combination of the up-query method and the down-query method.
Step six, defining and linking the verification requirements of the device T2 level.
A T2-level requirement verification requirement file is created in a verification requirement management module, the T2-level requirement verification requirement file is automatically imported into a T2-level function requirement file, a T2-level function requirement list is displayed in an interface, then each T2-level function requirement is manually selected in sequence, and a T2-level verification requirement input text box of the device is started (the interface structure is shown in figure 6). Table 6 is a content format schematic of the text box. And manually inputting a verification requirement (a concrete method for conformity) corresponding to each functional requirement in the text input box.
After a requirement is input, software automatically generates and gives a unique physical address to the requirement, and the software can inquire and locate any one T1-level verification requirement and display the source information of the requirement.
Device level T2 verification requirements file version: the verification requirement file (file) of level T2 can be edited in the management module, and a new version is generated for the verification requirement file of level T2 of the device each time the editing is completed.
And (3) avoiding cooperative work conflict: when multiple persons input or edit the same verification requirement file of the T2 level at the same time, the software interface displays a conflict reminding window for reminding that manual intervention conflict is needed.
Forming device level T2 verification requirement clause physical address: after the confirmation is input, the software generates a third physical address of the device T2 level verification requirement according to the IP address of the computer (server) where the device T2 level verification requirement file is located, the device T2 level verification requirement file name, the device T2 level verification requirement file version number, the T2 level verification requirement number and the corresponding second physical address of the device T2 level functional requirement, wherein the third physical address is used for requirement query positioning.
Viewing the content of the verification requirement file at the T2 level: and after all the required contents are input, clicking the file name, and checking the complete contents of the file in a text format.
Querying device level T2 verification requirement traceability: there are three ways for retrospective query, which are an upward query, a downward query, and a total query. The upward query method is that a server where a T2-level verification requirement of equipment is located is addressed through the T2-level verification requirement of the equipment, the function requirement (specific version number) of the T2-level of the equipment is traced, the specific term of the T2-level function requirement of the equipment is traced, the top-level function requirement is traced, and the qualified and approved basic term is traced. The downward inquiry method is to inquire down all the verification results linked with the item according to a specific verification requirement item. All the query rules are a combination of the up-query method and the down-query method.
Step seven, repeatedly implementing
According to the structural composition of the equipment, according to the method described in the step five and the step six, the functional requirements of each level of the equipment T3, T4, T5 and the like are defined and linked step by step from top to bottom, and the verification requirements of each level of the equipment T3, T4, T5 and the like are defined and linked step by step.
Step eight, establishing a link between the verification result and the functional requirement and the verification requirement.
After the device development is completed, verification tests are performed at various levels of the device according to the verification requirements to evaluate whether the device has achieved the specified functional requirements.
In the verification requirement management module, a function requirement, a verification requirement and a verification result linking function are started, a client displays a verification requirement structure tree of each level of equipment, any one verification requirement is selected, and the operation of adding a verification result or editing the verification result can be completed on an operation interface. And if a new verification result is selected, an operation interface of the table 7 appears, and after the verification result is input, the software stores the function requirement, the verification requirement and the link relation of the verification result.
Ninth step, retrospective query implementation
After the requirements are input and the link relation is established manually, software can carry out retrospective query on the requirements according to the link relation. The method is characterized in that the method is a top-down tree structure regardless of functional requirements or verification requirements, each parent requirement can have a plurality of child requirements, and one child requirement only has one parent requirement (some derived requirements do not have parent requirements, the structure of the functional requirements is shown in figure 3. according to a tree model of the functional requirements, a coding rule of the requirements is designed, and information included by utilizing codes of the requirements comprises requirement types (functions, verification, safety, derived types, performances and installation), airborne system types (using ATA (advanced technology) chapter numbers) to which the requirements belong, and the levels where the requirements are located.
In a retrospective query module of a client, any one of function requirement files (or verification requirement files or verification result files) is opened, a certain bar in the file is selected, and a query command (an icon of the query command is arranged on a software interface) is sent out. The server inquires the numbers of all upper-level requirements of the requirements, corresponding airworthiness approval basic terms and the numbers of all lower-level requirements of all layers of the requirements by utilizing a recursive retrieval algorithm according to the requirement numbering rules, the software searches the physical addresses required to be stored according to the requirement numbers, further reads all attribute information of the requirements stored in the addresses, and displays the contents on a display interface of the client.
When the verification requirement corresponding to the function requirement is checked and the verification result is obtained, because the coding method of the verification requirement is completely the same as the coding method of the function requirement, the digital codes with the same verification requirement are strictly mapped to the function requirement, and the two are in a strict one-to-one correspondence relationship. Software needs to search and recur to inquire out all verification requirements and verification results according to letters (VAL) in a first field of codes and a requirement number coding rule.
Step ten, change range query implementation
The method comprises the steps of automatically displaying a prompt window by a system after editing and modifying is completed, displaying the file name needing synchronous modification in the window, relating to the clause number in the file, and highlighting the clause number in the file. And after the related files and file terms are changed and the storage is confirmed, the change influence range prompting window displays all prompts of the change completion.
Claims (8)
1. The utility model provides a software suitable for carry out airworthiness management to civilian airborne equipment, includes that qualified base management module, function demand management module, verification demand management module, traceability inquiry module, equipment constitute and set up the module, its characterized in that:
the equipment composition setting module: providing a human-computer operation interface for a user to complete the hierarchical arrangement of the equipment according to the equipment composition;
a qualification approval base management module: providing an interface for a user to formulate and edit a qualified approval base file and qualified approval base terms contained in a qualified approval base management file, and generating a first physical address for storing the qualified approval base file and the qualified approval base terms in a server, wherein the first physical address consists of an IP address of the server, a name of the qualified approval base file, a version number of the qualified approval base file and a number of the qualified approval base terms;
the function requirement management module: providing a human-computer operation interface of a user defined function requirement file, and generating a second physical address of the function requirement file stored in the server; the function requirement file records the function requirement of a certain level of a product and the link relation between the function requirement and the function requirement of the previous layer, and the second physical address consists of the IP address of the server, the name of the function requirement file, the version number of the function requirement file, the serial number of the function requirement and the corresponding second physical address of the function requirement file of the previous layer;
a verification requirement management module: providing a human-computer operation interface for defining a verification requirement file and a verification result file by a user, and generating a third physical address for storing the verification requirement file in the server and a fourth physical address for storing the verification result file in the server; the verification requirement document records a verification requirement of a certain level of equipment and a link between the verification requirement and a function requirement of a corresponding level; the verification result file records a verification result corresponding to a certain level of verification requirements of the equipment and a link between the verification result and the corresponding verification requirements and function requirements; the third physical address consists of an IP address, a verification requirement file name, a verification requirement file version number, a verification requirement number and a second physical address of a corresponding hierarchical function requirement file; the fourth physical address consists of the IP address of the server, the name of the verification requirement file, the version number of the verification requirement file, the verification requirement number, the second physical address of the corresponding functional requirement, the name of the verification result file and the position of the verification result file in the server;
a traceability query module: sending a request for inquiring equipment seaworthiness requirement traceability, function requirement traceability or verification requirement traceability, which is provided by a user, to a server, and displaying a link relation and corresponding requirement content of returned corresponding equipment seaworthiness requirements, function requirements, verification requirements and verification results; after receiving a request for inquiring the seaworthiness requirement traceability, the function requirement traceability or the verification requirement traceability of the equipment, the server resolves the numbering information of the seaworthiness requirement, the function requirement and the verification requirement of the equipment to obtain a corresponding first physical address, a corresponding second physical address, a corresponding third physical address and a corresponding fourth physical address, reads the linking relation and the requirement content of the seaworthiness requirement, the function requirement, the verification requirement and the verification result of the equipment from the first physical address, the second physical address, the corresponding third physical address and the corresponding fourth physical address, and returns the inquiry result to the client.
2. Software for the airworthiness management of onboard civil appliances according to claim 1, characterized in that it also comprises a project basic attribute management module for performing the management of the cooperative computer network, with different operating authority settings of the personnel.
3. Software for the airworthiness management of devices onboard civil aircraft according to claim 1, characterized in that the document of compliance certification base management module, when editing the established document of compliance certification base, automatically generates a copy of the document of compliance certification base, assigning a new version number, in order to keep the difference from the previous document of compliance certification base.
4. The software for airworthiness management of civil airborne equipment according to claim 1, characterized in that the qualification base management module, after the user inputs a name of a qualification base document and a number of qualification base terms, determines whether to be duplicated with the existing airworthiness base terms by keywords, and if so, gives a conflict reminding window on the interface.
5. Software for the airworthiness management of onboard civil appliances according to claim 1, characterized in that in the functional requirements management module, each time the editing of a functional requirements file is completed, a new functional requirements file is generated, assigned a new version number.
6. The software for airworthiness management of civil airborne equipment according to claim 1, wherein the function requirement management module determines whether a plurality of persons input or edit the same function requirement file at the same time according to the name and version number of the function requirement file, and if so, displays a conflict reminding window.
7. Software for the airworthiness management of civil onboard equipment according to claim 1, characterized in that each time the editing of the verification requirement document is completed in the verification requirement management module, a new verification requirement document is generated, given a new version number.
8. The software for airworthiness management of civil airborne equipment according to claim 1, wherein the verification requirement management module determines whether a plurality of persons input or edit the same verification requirement file at the same time according to the name and version number of the verification requirement file, and if so, displays a conflict reminding window.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911218828.3A CN111045718B (en) | 2019-12-03 | 2019-12-03 | Software suitable for airworthiness management of civil airborne equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911218828.3A CN111045718B (en) | 2019-12-03 | 2019-12-03 | Software suitable for airworthiness management of civil airborne equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111045718A true CN111045718A (en) | 2020-04-21 |
| CN111045718B CN111045718B (en) | 2022-11-04 |
Family
ID=70233351
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911218828.3A Active CN111045718B (en) | 2019-12-03 | 2019-12-03 | Software suitable for airworthiness management of civil airborne equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111045718B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112783486A (en) * | 2020-12-24 | 2021-05-11 | 中国航发控制系统研究所 | Aero-engine software overall process evidence chain multiplexing generation method and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106600123A (en) * | 2016-12-01 | 2017-04-26 | 西安电子工程研究所 | Design file number management system design method |
| CN108537503A (en) * | 2018-03-26 | 2018-09-14 | 西南电子技术研究所（中国电子科技集团公司第十研究所） | software development management system |
| CN110045981A (en) * | 2018-01-14 | 2019-07-23 | 北京关键科技股份有限公司 | A method of analytical technology is compared based on source code and establishes demand tracking relationship |
-
2019
- 2019-12-03 CN CN201911218828.3A patent/CN111045718B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106600123A (en) * | 2016-12-01 | 2017-04-26 | 西安电子工程研究所 | Design file number management system design method |
| CN110045981A (en) * | 2018-01-14 | 2019-07-23 | 北京关键科技股份有限公司 | A method of analytical technology is compared based on source code and establishes demand tracking relationship |
| CN108537503A (en) * | 2018-03-26 | 2018-09-14 | 西南电子技术研究所（中国电子科技集团公司第十研究所） | software development management system |
Non-Patent Citations (2)
| Title |
|---|
| 卢艺等: "基于构型项目分类的民机系统适航符合性证据体系结构研究", 《民用飞机设计与研究》 * |
| 路瑞芳: "民用飞机适航审定管理信息系统研究与开发", 《民用飞机设计与研究》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112783486A (en) * | 2020-12-24 | 2021-05-11 | 中国航发控制系统研究所 | Aero-engine software overall process evidence chain multiplexing generation method and system |
| CN112783486B (en) * | 2020-12-24 | 2023-10-31 | 中国航发控制系统研究所 | Method and system for generating whole-process evidence chain multiplexing of aeroengine software |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111045718B (en) | 2022-11-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11263364B2 (en) | Methods and systems for processing building information modeling (BIM)-based data | |
| CN107819824B (en) | Urban data opening and information service system and service method | |
| US10140402B2 (en) | Parallel workflow finite element pre-processing apparatus and system | |
| US7099887B2 (en) | Hierarchical environments supporting relational schemas | |
| US6850939B2 (en) | System and method for providing selective data access and workflow in a network environment | |
| CN110807015B (en) | Big data asset value delivery management method and system | |
| CN104731596A (en) | Classification compiling method supporting several persons to online compile XBRL | |
| Dong et al. | Managing design information in enterprise-wide CAD usingsmart drawings' | |
| CN110968653B (en) | Tree-shaped data dictionary maintenance system and method | |
| CN112699496B (en) | Maintainability design and analysis integrated system for spacecraft | |
| CN105653442A (en) | Method for satisfying evaluation target of DO-178C standard | |
| CN111401029A (en) | Document version updating system and method based on document partition and collaborative editing | |
| US10706020B2 (en) | Data sharing in CAx applications | |
| CN111563200A (en) | Information display method, device, equipment and medium | |
| CN111897866A (en) | Remote sensing monitoring pattern spot docking system and using method thereof | |
| CN111045718B (en) | Software suitable for airworthiness management of civil airborne equipment | |
| CN108830565B (en) | Menu authorization method based on role | |
| JP2007133624A (en) | Information management method and device using connection relation information | |
| CN114066238A (en) | Forest land protection utilization planning index determination system, cloud platform and method | |
| CN109670728B (en) | Ship design quality information management system based on database | |
| US20120174180A1 (en) | Authorizations for analytical reports | |
| US8478791B2 (en) | Interoperability across heterogeneous taxonomies | |
| CN114581033B (en) | Method, device and equipment for rapidly developing government affair approval business | |
| JPH08129558A (en) | Equipment ledger database | |
| CN110597491B (en) | Method for quickly constructing different service systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |