CN117539435A - Avionics architecture and system architecture demand transfer method - Google Patents
Avionics architecture and system architecture demand transfer method Download PDFInfo
- Publication number
- CN117539435A CN117539435A CN202311491433.7A CN202311491433A CN117539435A CN 117539435 A CN117539435 A CN 117539435A CN 202311491433 A CN202311491433 A CN 202311491433A CN 117539435 A CN117539435 A CN 117539435A
- Authority
- CN
- China
- Prior art keywords
- architecture
- avionics
- case
- service
- participants
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 67
- 238000012546 transfer Methods 0.000 title claims abstract description 39
- 238000013461 design Methods 0.000 claims abstract description 33
- 230000008569 process Effects 0.000 claims abstract description 10
- 238000004458 analytical method Methods 0.000 claims description 21
- 238000010586 diagram Methods 0.000 claims description 16
- 238000010230 functional analysis Methods 0.000 claims description 12
- 238000013507 mapping Methods 0.000 claims description 11
- 238000001514 detection method Methods 0.000 claims description 10
- 230000003993 interaction Effects 0.000 claims description 7
- 230000006399 behavior Effects 0.000 claims description 6
- 230000000694 effects Effects 0.000 claims description 4
- 230000007547 defect Effects 0.000 claims description 3
- 238000007670 refining Methods 0.000 claims description 2
- 238000002716 delivery method Methods 0.000 claims 4
- 238000000638 solvent extraction Methods 0.000 claims 3
- 238000011161 development Methods 0.000 abstract description 3
- 230000006855 networking Effects 0.000 description 7
- 238000007726 management method Methods 0.000 description 6
- RZVHIXYEVGDQDX-UHFFFAOYSA-N 9,10-anthraquinone Chemical compound C1=CC=C2C(=O)C3=CC=CC=C3C(=O)C2=C1 RZVHIXYEVGDQDX-UHFFFAOYSA-N 0.000 description 5
- 230000015572 biosynthetic process Effects 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000012938 design process Methods 0.000 description 1
- 238000012407 engineering method Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000003786 synthesis reaction Methods 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- 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
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4488—Object-oriented
- G06F9/4492—Inheritance
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention belongs to the field of system architecture and system engineering, and discloses a avionics system architecture and system architecture demand transfer method, which comprises an external participant definition method based on a system interface expression model SV-1, a service use case division method based on a system event tracking model SV-10c and external participants, and a system use case division method based on a system function expression model SV-4 and service use cases, so as to form an avionics system architecture-system architecture integrated through demand transfer process, and provide traceable integrated demands for consistent physical realization of a platform-system, thereby improving the design and development efficiency and reliability of the avionics system.
Description
Technical Field
The invention belongs to the field of architecture and system engineering, and particularly relates to a method for demand transfer of avionics architecture and system architecture.
Background
With the development of aviation equipment from a platform-centered mode to a systematic and distributed cooperative application mode, an avionics system is evolving from a single-platform avionics system architecture design to a multi-platform avionics system architecture design, a traditional single-platform avionics system architecture design method widely adopts a Harmony-based System Engineering (SE) method, and the multi-platform avionics system architecture design method often adopts a DoDAF-based system architecture design method, but currently lacks a method for carrying out demand transfer from an avionics system architecture to an avionics system architecture, so that fault problems occur in avionics system level design and avionics system level design, and the top-down integrated design cannot be achieved. Therefore, how to implement the mapping and tracing of the requirements of the avionics architecture and the system architecture has become a serious issue in the avionics architecture design process.
The avionics architecture design based on the DoDAF generally comprises view models of capability view, task view, system view and the like, wherein the system view describes information such as composition, interfaces, system functions, interaction relationship, operation logic and the like of avionics systems in a plurality of aviation platforms through a system interface expression model (SV-1), a system function expression model (SV-4), a system event tracking model (SV-10 c) and the like; the Harmony-based system engineering method comprises links of system demand analysis, system function analysis, system design synthesis and the like, wherein the system demand analysis describes information such as system boundaries, external participants, use cases, association relations between the use cases and the participants by establishing a system use case diagram.
Disclosure of Invention
Aiming at the problem of design faults of avionics architecture and system architecture, the method for transmitting the requirements of the avionics architecture and the system architecture based on system view angle-system requirement analysis is used for realizing the association and mapping of the requirements of the multi-platform avionics architecture and the requirements of the single-platform avionics system, opening a top-down architecture design path of the system-system architecture, and providing traceable integrated requirements for the consistent physical implementation of the platform-system, thereby improving the design and development efficiency and reliability of the avionics system.
In order to achieve the above purpose, the invention is realized by adopting the following technical scheme.
An avionics architecture and system architecture demand transfer method comprises an external participant definition method based on a system interface expression model SV-1, a service case division method based on a system event tracking model SV-10c and external participants, and a system case division method based on a system function expression model SV-4 and service cases, so as to form an avionics architecture-system architecture integrated through demand transfer process.
Further, the external participant definition method based on the system interface expression model specifically comprises the following steps:
firstly, defining objects and boundaries of avionic system architecture design; then, other external systems related to the system object in the avionics architecture system interface expression model SV-1 are extracted aiming at the system object and used as external participants of the system object; and (3) completing the analysis of the system boundary and external participants in the system demand analysis link, and realizing the consistency standardized transfer of the avionics system architecture and the system description in the system architecture.
Further, the external participant definition method based on the system interface expression model comprises the following implementation steps:
1.1 Defining an avionics system architecture design object; according to the working target and task, confirming a system object needing to develop the detailed design of the single-platform avionics system and a boundary thereof, and analyzing a clear range for the subsequent participants and use cases;
1.2 Defining an external participant set of the system object; receiving an architecture model, capturing and refining all other systems interacted with the system object existence interface from the SV-1 view to form an external participant set;
1.3 A system use graph framework is constructed; drawing the system object frame in the step 1.1), and according to the step
1.2 A) the set of participants in which the system object is built, wherein the system object, the external participant name, needs to be consistent with the system name in the architecture model SV-1.
Further, the service case division method based on the system event tracking model and the external participants specifically comprises the following steps:
dividing the use cases in the system demand analysis link into service use cases and system use cases; the service use case describes various task scenes which can be completed by the participants through the system objects according to the operation logic in the avionics architecture system event tracking model SV-10c from the use perspective of users which excite the behaviors of the avionics system objects, namely external participants; through the definition of service use cases, capturing and tracing of the use requirements of participants aiming at system objects in the avionics system architecture are realized.
Further, the method for dividing the service use cases based on the system event tracking model and the external participants comprises the following implementation steps:
2.1 Defining a task scene set of each participant using the system object; based on the external participant set in the step 1.2), adapting the system architecture model, combing interaction events and operation logic between life lines of all participants and life lines of avionics system objects from the SV-10c view, and defining and forming a task scene set completed by all the participants through the system objects;
2.2 Defining service use cases and association relations between the service use cases and participants; and 2) merging and classifying task scene sets formed by all the participants in the step 2.1), defining a service case set from the dimension of the user target function of the system object, and adding the association relation between each service case and the related participant.
Further, the system use case division method based on the system function expression model and the service use case specifically comprises the following steps:
from the perspective of the functional implementation of the avionics system object, the system use case defines the functional behaviors which can be implemented by the system object and are independent and completely exhaustive as far as possible according to the functional description of the system object in the avionics architecture system functional expression model SV-4; through the definition of the system use cases, the direct transfer and inheritance of the function requirements of the system objects in the avionics architecture are realized; a service use case should be implemented by one or more system use cases, and the indirect transfer and mapping of the architecture use requirements to the functional requirements is described by implementing a relationship between the system use case and the service use case.
Further, the system use case dividing method based on the system function expression model and the service use case comprises the following implementation steps:
3.1 Defining a system object function set; receiving a system architecture model, extracting all system functions of the system object in the step 1.1) from the SV-4 view, forming a function set of the system object, and providing top-level input for direct transfer of the top-down system object functions;
3.2 Defining a system use case; combining and classifying the system object function sets in the step 3.1), and defining a system use case set from the dimension of the function realization of the system object according to a preset rule, so as to realize scientific and credible transfer of the system object function from a system level to a system level;
3.3 Defining the realization relation between the system use case and the service use case. The system use cases need to cover and support the system object use scenes of all service use cases so as to realize the coverage traceability from the functional requirements to the use requirements; performing functional analysis aiming at each service case in the step 2.2), wherein the functional analysis at least comprises a activity diagram, a sequence diagram and an interface diagram for constructing the service case; according to the function implementation flow in the function analysis of the service case, the function implementation is distributed to the related system case, the implementation relation between the related system case and the service case is added, and if the existing system case can not completely realize the service case use requirement, the system case is newly defined according to the principle in the step 3.2), so that the function requirement leak detection and defect filling based on the use requirement are realized.
Further, the preset rule in step 3.2) is:
a) The system use case must interact with the participant presence data;
b) The system use case must be a complete functional description, and may consist of a series of actions;
c) The system use cases need to be mutually independent and completely exhausted;
d) One or more system use cases have an implementation relation with a certain service use case, the service use case only needs to further develop functional analysis, and the system use case needs to further distribute system functions to the system logic architecture design after the functional analysis link.
The beneficial effects of the invention are as follows: the invention provides a avionics system architecture and system architecture demand transfer method, which can connect an upper avionics system architecture and a lower avionics system architecture based on a model through a system view angle and a system demand analysis link to realize seamless connection and traceability of demands, thereby reducing global maintenance cost and cost caused by upper or lower demand change; through standardized consistency description and interface design among systems in the multi-platform avionics system, high interaction among all single-platform avionics systems can be realized, so that the flexibility, the interoperability and the system integration capability of the system are enhanced.
Drawings
FIG. 1 is a flow chart of a method for demand transfer of avionics architecture and system architecture according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of an illustration framework for an avionics system of an unmanned aerial vehicle and a mapping relationship between the illustration framework and SV-1 according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of an unmanned aerial vehicle avionics system service case and a mapping relation between the service case and SV-10 c;
fig. 4 is a schematic diagram of a mapping relationship between an avionics system case and an SV-4/service case provided by an embodiment of the present invention.
Detailed Description
The following description of the preferred embodiments of the present invention is given with reference to the accompanying drawings, so as to explain the technical scheme of the present invention in detail.
The system view angle in the avionics system architecture and the system demand analysis link in the avionics system architecture provide a method guidance and implementation way for the avionics system architecture to transfer the demands of the system architecture.
The avionics architecture and system architecture demand transfer method is characterized in that a system interface expression model (SV-1) in an avionics architecture design system view angle is associated with external participant definitions in an avionics architecture design system demand analysis process, a system event tracking model (SV-10 c) in the architecture design system view angle is associated with business use case division in the avionics architecture design system demand analysis process, a system function expression model (SV-4) in the architecture design system view angle is associated with system use case division in the avionics architecture design system demand analysis process, so that the associated mapping of upper avionics architecture model information and lower avionics system architecture demands is realized, the 'system-system' integrated through demand transfer is realized, and a basis is provided for consistent physical realization from a multi-platform system to a single-platform system.
An avionics architecture and system architecture demand transfer method comprises an external participant definition method based on a system interface expression model SV-1, a service case division method based on a system event tracking model SV-10c and external participants, and a system case division method based on a system function expression model SV-4 and service cases, so as to form an avionics architecture-system architecture integrated through demand transfer process. Wherein:
1) External participant definition method based on system interface expression model
First, the objects and boundaries of the avionics system architecture design are defined. Then, other external systems related to the system object in the avionics architecture system interface expression model (SV-1) are extracted as external participants of the system object. And (3) completing the analysis of the system boundary and external participants in the system demand analysis link, and realizing the consistency standardized transfer of the avionics system architecture and the system description in the system architecture. The implementation steps are as follows:
1.1 Defining avionics system architecture design objects. And according to the working target and the task, confirming the system object and the boundary thereof which need to develop the detailed design of the single-platform avionics system, and analyzing the clear range for the follow-up participants and use cases.
1.2 Defining an external set of participants for the system object. The architecture model is accepted, all other systems interacting with the system object existence interface are captured and extracted from the SV-1 view, and an external participant set is formed.
1.3 A system use case diagram framework is constructed. Drawing the system object frame in the step 1.1), and according to the step
1.2 A) the set of participants in which the system object is built, wherein the system object, the external participant name, needs to be consistent with the system name in the architecture model SV-1.
2) Service case dividing method based on system event tracking model and external participants
The method is characterized in that the use cases in the system demand analysis link are divided into service use cases and system use cases. From the use perspective of a user, i.e., an external participant, who stimulates the behavior of an avionics system object, the business use case describes various task scenarios that the participant can complete through the system object according to the operation logic in the avionics architecture system event tracking model (SV-10 c). Through the definition of service use cases, capturing and tracing of the use requirements of participants aiming at system objects in the avionics system architecture are realized. The implementation steps are as follows:
2.1 Defining a set of task scenarios in which each participant employs a system object. Based on the external participant set in the step 1.2), the architecture model is accepted, interaction events and operation logic between life lines of all participants and life lines of avionics system objects are combed from the SV-10c view, and a task scene set completed by all the participants through the system objects is defined and formed.
2.2 Defining the business use case and its association relationship with the participant. And 2) merging and classifying task scene sets formed by all participants in the step 2.1), and defining a service case set from the dimension of the user target function of the system object. For each business use case, the association relationship between the business use case and the relevant participant is added.
3) System case dividing method based on system function expression model and business case
From the perspective of the functional implementation of the avionics system object, the system use case defines the functional behaviors which can be implemented by the system object and are independent and completely exhaustive as far as possible according to the functional description of the system object in the avionics architecture system functional expression model (SV-4). Through the definition of the system use case, the direct transfer and inheritance of the system object function requirements in the avionics architecture are realized. Meanwhile, a service use case should be realized through one or more system use cases, and the indirect transfer and mapping from the architecture use requirement to the function requirement are described through the relationship between the system use case and the service use case. The implementation steps are as follows:
3.1 Defining a system object function set. And (3) accepting the system architecture model, extracting all system functions of the system object in the step 1.1) from the SV-4 view, forming a function set of the system object, and providing top-level input for direct transfer of the functions of the system object from top to bottom.
3.2 Defining a system use case. Combining and classifying the system object function sets in the step 3.1), and defining the system use case sets from the dimension of the system object functions according to the following principle, so as to realize scientific and reliable transfer of the system object functions from the system level to the system level.
a) The system use case must interact with the participant presence data;
b) The system use case must be a complete functional description, and may consist of a series of actions;
c) The system use cases need to be independent of each other as much as possible and completely exhaustive (MECE);
d) One or more system use cases have an implementation relation with a certain service use case, the service use case only needs to further develop functional analysis, and the system use case needs to further distribute system functions to the system logic architecture design after the functional analysis link.
3.3 Defining the realization relation between the system use case and the service use case. The system use case needs to be capable of covering and supporting the system object use scene of all service use cases so as to realize the coverage tracing from the function requirement to the use requirement. Based on avionics domain knowledge, performing functional analysis for each service case in step 2.2), including constructing an activity map, a sequence map, an interface map, and the like of the service case. According to the function implementation flow in the function analysis of the service case, the function implementation is distributed to the related system case, the implementation relation between the related system case and the service case is added, and if the existing system case can not completely realize the service case use requirement, the system case is newly defined according to the principle in the step 3.2), so that the function requirement leak detection and defect filling based on the use requirement are realized.
FIG. 1 is a block diagram of a method implementation of the present invention. As shown in the embodiment of fig. 1, the implementation process of the method of the present invention includes an external participant definition method based on a system interface expression model, a service case division method based on a system event tracking model and an external participant, and a system case division method based on a system function expression model and a service case, so as to form an avionics architecture and a system architecture integrated through-type demand transfer. The implementation steps of this embodiment are as follows:
(1) Taking the process of transferring the requirements from the unmanned cooperative system architecture to the unmanned aerial vehicle avionics system architecture as an example. Firstly, a system object which is specifically designed for carrying out a single-platform avionics system is an unmanned aerial vehicle avionics system according to a work target. As shown in fig. 2 (a), other systems with interfaces interacting with the unmanned aerial vehicle avionics system in the unmanned aerial vehicle architecture can be known to include an unmanned aerial vehicle flight control system, an unmanned aerial vehicle link system and an unmanned aerial vehicle avionics system according to the view angle model of the unmanned aerial vehicle architecture system and the view angle model of the SV-1. The illustration framework for the unmanned aerial vehicle avionics system is constructed, as shown in fig. 2 (b), the system object is an unmanned aerial vehicle avionics system, and the external participants are an unmanned aerial vehicle flight control system, an unmanned aerial vehicle link system and an unmanned aerial vehicle avionics system. And the consistency standardized transfer of the system description in the unmanned aerial vehicle avionics system architecture and the unmanned aerial vehicle avionics system architecture is realized.
(2) According to the view of SV-10c, as shown in FIG. 3 (a), it can be known that the unmanned aerial vehicle link system and the unmanned aerial vehicle avionics system have interactive events and operation logics such as networking request, networking plan, cooperative attack instruction request, transmission confirmation and the like, and the task scene completed by the unmanned aerial vehicle link system through the unmanned aerial vehicle avionics system is defined as whether unmanned networking and cooperative attack exist or not; the unmanned aerial vehicle avionics system and the unmanned aerial vehicle avionics system have interaction events and operation logics such as radar collaborative detection parameters, echo signals and the like, and a task scene completed by the unmanned aerial vehicle avionics system is defined as radar collaborative detection; interaction events and operation logics such as networking guiding flight parameters, attack occupation guiding flight parameters and the like exist in the unmanned aerial vehicle flight control system and the unmanned aerial vehicle avionics system, and task scenes completed by the unmanned aerial vehicle flight control system through the unmanned aerial vehicle avionics system are defined as networking, cooperative attack and flight guiding. And merging and classifying all task scenes, defining four service cases of formation networking, collaborative detection, collaborative attack and flight guidance, and adding the association relation of related participants, as shown in fig. 3 (b). The method realizes the capturing and tracing of the unmanned aerial vehicle avionics system, the unmanned aerial vehicle link system and the unmanned aerial vehicle flight control system aiming at the use requirement of the unmanned aerial vehicle avionics system in the unmanned and unmanned cooperative system architecture.
(3) From the SV-4 view, as shown in FIG. 4 (a), it is known that the system functions of the unmanned aerial vehicle avionics system include communication management, routing, radar collaborative detection, fire control calculation, and the like. According to the system use case division principle, system use cases such as dimension definition communication management, route planning, radar collaborative detection, fire control calculation and the like are realized from unmanned aerial vehicle avionics system functions. The system and the method realize direct transfer and inheritance from the unmanned aerial vehicle avionics system architecture to the unmanned aerial vehicle avionics system architecture.
(4) Based on avionics field knowledge, functional analysis of formation networking, collaborative detection, collaborative attack and flight guidance service cases is carried out, an activity diagram, a sequence diagram and an interface diagram are constructed, the functional implementation of the service cases can be distributed to related system cases, and an implementation relation is added. The sequence diagram of the collaborative attack service use case is shown in fig. 4 (c), and in the implementation process of the collaborative attack service use case, the fire control resolving system use case needs to comprise tactical decision function, and also needs functions of sensor management, radar tracking guidance and the like, but according to the principle in the step 3.2), the sensor management function does not interact data with external participants, so that the sensor management and the radar tracking guidance function are combined and defined as the radar collaborative guidance system use case. The method realizes the indirect transfer and mapping from the use requirement of the unmanned aerial vehicle cooperative system architecture to the functional requirement of the unmanned aerial vehicle avionics system.
(5) The comprehensive steps (3) and (4) can be known that the system use case comprises communication management, route planning, radar collaborative detection, fire control calculation and radar collaborative guidance, and the association relation between the system use case and external participants and the implementation relation between the system use case and service use case are shown in fig. 4 (b). The requirement transfer from the unmanned aerial vehicle avionics system architecture to the unmanned aerial vehicle avionics system architecture is realized through links such as consistency system description, use requirement tracing, system function inheritance, mapping from use requirement to function requirement and the like.
The object of the preferred embodiment provided by the invention is an unmanned aerial vehicle avionics system, and the method is still applicable when the object is a fighter plane, a helicopter, an early warning machine and other aircraft avionics systems.
Claims (8)
1. The avionics architecture and system architecture demand transfer method is characterized by comprising an external participant definition method based on a system interface expression model SV-1, a service case division method based on a system event tracking model SV-10c and external participants and a system case division method based on a system function expression model SV-4 and service cases, so as to form an avionics architecture-system architecture integrated through demand transfer process.
2. The avionics architecture and system architecture requirement delivery method of claim 1, wherein the external participant definition method based on the system interface expression model is specifically:
firstly, defining objects and boundaries of avionic system architecture design; then, other external systems related to the system object in the avionics architecture system interface expression model SV-1 are extracted aiming at the system object and used as external participants of the system object; and (3) completing the analysis of the system boundary and external participants in the system demand analysis link, and realizing the consistency standardized transfer of the avionics system architecture and the system description in the system architecture.
3. The avionics architecture and system architecture requirement delivery method of claim 2, wherein the external participant definition method based on the system interface representation model is implemented as follows:
1.1 Defining an avionics system architecture design object; according to the working target and task, confirming a system object needing to develop the detailed design of the single-platform avionics system and a boundary thereof, and analyzing a clear range for the subsequent participants and use cases;
1.2 Defining an external participant set of the system object; receiving an architecture model, capturing and refining all other systems interacted with the system object existence interface from the SV-1 view to form an external participant set;
1.3 A system use graph framework is constructed; drawing a system object border in the step 1.1), and constructing external participants of the system object according to the participant set in the step 1.2), wherein the names of the system object and the external participants are required to be consistent with the system names in the architecture model SV-1.
4. The avionics architecture and system architecture demand delivery method of claim 3, wherein the business case partitioning method based on the system event tracking model and external participants specifically comprises:
dividing the use cases in the system demand analysis link into service use cases and system use cases; the service use case describes various task scenes which can be completed by the participants through the system objects according to the operation logic in the avionics architecture system event tracking model SV-10c from the use perspective of users which excite the behaviors of the avionics system objects, namely external participants; through the definition of service use cases, capturing and tracing of the use requirements of participants aiming at system objects in the avionics system architecture are realized.
5. The avionics architecture and system architecture demand delivery method of claim 4, wherein the implementation steps based on the system event tracking model and the business case partitioning method of external participants are as follows:
2.1 Defining a task scene set of each participant using the system object; based on the external participant set in the step 1.2), adapting the system architecture model, combing interaction events and operation logic between life lines of all participants and life lines of avionics system objects from the SV-10c view, and defining and forming a task scene set completed by all the participants through the system objects;
2.2 Defining service use cases and association relations between the service use cases and participants; and 2) merging and classifying task scene sets formed by all the participants in the step 2.1), defining a service case set from the dimension of the user target function of the system object, and adding the association relation between each service case and the related participant.
6. The avionics architecture and system architecture demand transfer method of claim 5, wherein the system case partitioning method based on the system function expression model and the service case is specifically as follows:
from the perspective of the functional implementation of the avionics system object, the system use case defines the functional behaviors which can be implemented by the system object and are independent and completely exhaustive as far as possible according to the functional description of the system object in the avionics architecture system functional expression model SV-4; through the definition of the system use cases, the direct transfer and inheritance of the function requirements of the system objects in the avionics architecture are realized; a service use case should be implemented by one or more system use cases, and the indirect transfer and mapping of the architecture use requirements to the functional requirements is described by implementing a relationship between the system use case and the service use case.
7. The avionics architecture and system architecture requirement transfer method according to claim 6, wherein the system case division method based on the system function expression model and the service case comprises the following implementation steps:
3.1 Defining a system object function set; receiving a system architecture model, extracting all system functions of the system object in the step 1.1) from the SV-4 view, forming a function set of the system object, and providing top-level input for direct transfer of the top-down system object functions;
3.2 Defining a system use case; combining and classifying the system object function sets in the step 3.1), and defining a system use case set from the dimension of the function realization of the system object according to a preset rule, so as to realize scientific and credible transfer of the system object function from a system level to a system level;
3.3 Defining the realization relation between the system use case and the service use case. The system use cases need to cover and support the system object use scenes of all service use cases so as to realize the coverage traceability from the functional requirements to the use requirements; performing functional analysis aiming at each service case in the step 2.2), wherein the functional analysis at least comprises a activity diagram, a sequence diagram and an interface diagram for constructing the service case; according to the function implementation flow in the function analysis of the service case, the function implementation is distributed to the related system case, the implementation relation between the related system case and the service case is added, and if the existing system case can not completely realize the service case use requirement, the system case is newly defined according to the principle in the step 3.2), so that the function requirement leak detection and defect filling based on the use requirement are realized.
8. The method of claim 7, wherein the predetermined rules in step 3.2) are:
a) The system use case must interact with the participant presence data;
b) The system use case must be a complete functional description, and may consist of a series of actions;
c) The system use cases need to be mutually independent and completely exhausted;
d) One or more system use cases have an implementation relation with a certain service use case, the service use case only needs to further develop functional analysis, and the system use case needs to further distribute system functions to the system logic architecture design after the functional analysis link.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311491433.7A CN117539435A (en) | 2023-11-09 | 2023-11-09 | Avionics architecture and system architecture demand transfer method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311491433.7A CN117539435A (en) | 2023-11-09 | 2023-11-09 | Avionics architecture and system architecture demand transfer method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117539435A true CN117539435A (en) | 2024-02-09 |
Family
ID=89791098
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311491433.7A Pending CN117539435A (en) | 2023-11-09 | 2023-11-09 | Avionics architecture and system architecture demand transfer method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117539435A (en) |
-
2023
- 2023-11-09 CN CN202311491433.7A patent/CN117539435A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106502266B (en) | Multi-machine collaborative operation command control system | |
| CN112153010B (en) | Network security shooting range system and operation method thereof | |
| CN105429780A (en) | Virtualized network service business automatic generation and dynamic monitoring method | |
| CN109558114A (en) | A kind of avionics system service architecture modeling method | |
| CN110113188A (en) | Across subdomain communication O&M method, total O&M server and medium | |
| CN103106368A (en) | Vulnerability scanning method for grade protection | |
| CN113486451B (en) | Unmanned aerial vehicle system architecture design method based on model | |
| CN107479876A (en) | A kind of five layer architecture design methods for building unmanned aerial vehicle station software | |
| CN107871050A (en) | The hybrid modeling method and storage medium of data-oriented and object-oriented | |
| CN209267610U (en) | A kind of electric field inspection remote supervisory and control(ling) equipment | |
| CN115270437A (en) | Novel task-level combat simulation modeling method and framework | |
| US11526335B2 (en) | Digital engineering platform configured to support future space systems development and acquisition | |
| CN117539435A (en) | Avionics architecture and system architecture demand transfer method | |
| CN111552461B (en) | Association mapping method for service framework design and service component development | |
| Lin | Evental infrastructure: Momentous geographies of technoscience production | |
| CN115037769B (en) | SOA-based air traffic control automation system and realization method thereof | |
| CN104106012A (en) | Information and control system for a multifunctional aircraft | |
| Zhang et al. | A UAF based method for next generation air traffic management system development | |
| CN113485435B (en) | Heterogeneous multi-unmanned aerial vehicle monitoring system and method | |
| Xiao et al. | An Architecture of Cross-Domain Support System for Multiple Space Command and Control Platforms | |
| Van et al. | Enabling cognitive manufacturing in heterogeneous industrial automation systems | |
| CN117767999A (en) | Aviation platform communication demand design method oriented to system integration | |
| CN113625779B (en) | Unmanned aerial vehicle control system and ground control system | |
| CN114443005B (en) | Middleware-based system integration method | |
| CN117289625A (en) | Interoperation simulation platform and operation method applied to multiple types of aircraft |
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 |