CN112527245B - Equipment system function demand analysis method based on model - Google Patents

Equipment system function demand analysis method based on model Download PDF

Info

Publication number
CN112527245B
CN112527245B CN202011397410.6A CN202011397410A CN112527245B CN 112527245 B CN112527245 B CN 112527245B CN 202011397410 A CN202011397410 A CN 202011397410A CN 112527245 B CN112527245 B CN 112527245B
Authority
CN
China
Prior art keywords
requirement
scene
diagram
segment
establishing
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.)
Active
Application number
CN202011397410.6A
Other languages
Chinese (zh)
Other versions
CN112527245A (en
Inventor
史文卿
袁正中
毛坤
马波
石维盛
朱睿
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
AVIC Chengdu Aircraft Design and Research Institute
Original Assignee
AVIC Chengdu Aircraft Design and Research Institute
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by AVIC Chengdu Aircraft Design and Research Institute filed Critical AVIC Chengdu Aircraft Design and Research Institute
Priority to CN202011397410.6A priority Critical patent/CN112527245B/en
Publication of CN112527245A publication Critical patent/CN112527245A/en
Application granted granted Critical
Publication of CN112527245B publication Critical patent/CN112527245B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/10Requirements analysis; Specification techniques
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/20Software design

Abstract

The invention aims to provide a model-based functional demand analysis method suitable for overall design of a complex unmanned aerial vehicle system, which comprises the following steps: (1) designing a life cycle segment scene, and establishing a life cycle division diagram, a segment scene series diagram and a segment scene summary diagram; (2) defining internal and external elements of the system, and establishing an element type graph and an element example graph; (3) analyzing two-level element behaviors, and establishing an activity diagram and a sequence diagram; (4) classifying, collecting, defining and mapping the operational requirement and the interactive requirement to form a function requirement form; (5) and compiling to form an unmanned aerial vehicle system function requirement file. Compared with the prior art, the modeling workload is greatly reduced, multi-department multi-professional parallel work can be effectively carried out, and the efficiency of the function requirement analysis of the complex unmanned aerial vehicle system is obviously improved.

Description

Equipment system function demand analysis method based on model
Technical Field
The invention possibly relates to the technical fields of system engineering, unmanned aerial vehicles and the like, in particular to a model-based equipment system function demand analysis method.
Background
The unmanned aerial vehicle system is an aviation device composed of an airplane, a load, a command control system and the like, and completes operation tasks under the operation of equipment users. Along with the continuous expansion of the application field and the continuous enhancement of the task capability of the unmanned aerial vehicle system, the functions of the unmanned aerial vehicle system are increasingly complex. The capabilities of realizing multi-unmanned aerial vehicle cooperation, manned/unmanned aerial vehicle cooperation, artificial intelligent game and the like become new targets for the research and development of unmanned aerial vehicle systems. Therefore, more and more internal and external elements, logic relations and system behaviors are considered at the initial stage of overall design of the unmanned aerial vehicle system, clear and complete functional requirements of the unmanned aerial vehicle system are defined and formed through sufficient functional requirement analysis, and input is provided for architecture design and subsystem research and development of the unmanned aerial vehicle system.
Emerging model-based system engineering utilizes standard modeling language to develop design activities, and provides a new working paradigm for unmanned aerial vehicle system functional requirement analysis. The mainstream standard system modeling language SysML can perform modeling expression on internal and external elements, logic relation and system behavior related to the unmanned aerial vehicle system in the modes of a structure diagram and a behavior diagram, and establishes a tracing relation between functional requirements and the system behavior. On the basis, a set of function requirement analysis method is needed, and steps, objects, contents and result forms of unmanned aerial vehicle system function requirement analysis are defined, so that the practical development of the model-based system function requirement analysis is guided.
However, the model-based functional demand analysis method suitable for the engineering research and development of the complex unmanned aerial vehicle system is not mature, and some existing methods have defects in the engineering practice of the overall design of the unmanned aerial vehicle system. For example, the function requirement analysis of the complex unmanned aerial vehicle system is carried out by adopting a Harmony method of American IBM company or a MagicBurd method of France Dacable company, so that the modeling links are multiple, the working flow is long, the human resource investment is large, multiple specialties are difficult to operate in parallel, and the rapid lean research and development requirements of the overall design of the unmanned aerial vehicle system cannot be met. Therefore, a set of functional requirement analysis method which is moderate in modeling workload, clear in analysis and design process and capable of achieving multi-professional parallel work is needed, and therefore functional requirement analysis efficiency of overall design of the complex unmanned aerial vehicle system is improved.
Disclosure of Invention
The invention aims to provide a model-based function requirement analysis method suitable for overall design of complex equipment, which is used for designing a life cycle fragment scene, defining two-stage element categories and element examples, analyzing two-stage behaviors of each fragment scene, establishing an activity diagram and a sequence diagram of level-by-level decomposition, classifying, collecting, defining and mapping function requirements, forming a function requirement form and a requirement-behavior mapping matrix, and compiling an equipment function requirement file, thereby providing input for equipment architecture design and subsystem research and development.
The technical scheme of the invention is that the equipment system function requirement analysis method based on the model comprises the following steps:
step (1), dividing the whole life cycle of the equipment according to stages, and analyzing and designing a corresponding series of fragment scenes for each stage; and specifies the internal and external elements to be analyzed for each segment scene.
Classifying internal and external elements according to all segment scenes of the full life cycle of the equipment, and defining a primary element class and a secondary element class; further, for each segment scene, cutting internal and external element types related to the segment scene, and determining corresponding primary element examples and secondary element examples;
And (3) performing element instance behavior analysis on each segment scene: firstly, designing a primary activity and a primary flow by taking a primary element example in a segment scene as an analysis object, and establishing a primary activity graph; secondly, decomposing and distributing each primary activity into behaviors of the primary element examples around the primary element examples, and establishing a primary sequence diagram; then designing a secondary activity and a flow according to the primary sequence diagram, and establishing a secondary activity diagram; finally, decomposing and distributing each secondary activity into behaviors of the secondary element examples around the secondary element examples, and establishing a secondary sequence diagram;
step (4), defining the functional requirements of each fragment scene: firstly, collecting operations and messages in a secondary sequence diagram according to the category of secondary elements, defining each operation as a functional requirement, and defining each message as an interactive requirement; merging the operability requirement and the interactivity requirement to obtain a function requirement item and form a function requirement form; and finally, establishing a mapping relation among the functional requirement items, the operation and the message, and establishing a requirement-behavior mapping matrix.
Preferably, the method further comprises the step (5):
Step (5) organizing the function requirement form established in the step (3) and the step (4) according to the life cycle stage, the fragment scene, the element category, the primary activity and the secondary activity, and compiling an equipment function requirement file; organizing the models established in the steps (1), (2), (3) and (4) to form a functional requirement analysis model which is matched with the functional requirement file; and releasing the function requirement file and the function requirement analysis model together and handing over the function requirement file and the function requirement analysis model to a downstream development department, thereby providing input for equipment architecture design and subsystem development.
Preferably, the operation purpose, the surrounding environment, the main process, the precondition and the postcondition of each segment scene are also required to be clear in the step (1).
Preferably, the result form of each stage segment scene comprises a segment scene series diagram and a segment scene summary diagram corresponding to each segment scene.
Preferably, the segment scene series diagram is modeled by using a block definition diagram of SysML, and the segment scene summary diagram is modeled by using a use diagram of SysML.
Preferably, the defined primary element type and secondary element form a global element type graph;
And clipping the global element category, instantiating to form an example graph of the element of the fragment scene corresponding to each fragment scene.
Preferably, the global element category map and the fragment scene element instance map are modeled using a block definition map of SysML.
Preferably, the equipment is a drone system.
The invention has the beneficial effects that: compared with other system function analysis methods based on models, the method has the advantages that through the step-by-step decomposition of the two-stage activity diagram and the sequence diagram, the modeling links are few, and the modeling workload is greatly reduced; the method has clear top-down analysis design flow and clear result form, and is suitable for engineering-level research and development of a complex unmanned aerial vehicle system; through the sequential segmentation of the life cycle stage, the segment scene, the first-level activity and the second-level activity and the global definition of the two-level element categories, the multi-department multi-professional parallel work can be effectively carried out, and the efficiency of the function requirement analysis of the complex unmanned aerial vehicle system is remarkably improved.
Drawings
FIG. 1 is a process flow diagram;
FIG. 2 is an example of a lifecycle partition diagram;
FIG. 3 is an example of a series of views of a segment scene;
FIG. 4 is an example of a segment scene summary diagram;
FIG. 5 is an example of a global element class diagram;
FIG. 6 is an example diagram of elements;
FIG. 7 is a one-level activity diagram example;
FIG. 8 is an example of a primary sequence diagram;
FIG. 9 is a secondary activity diagram example;
FIG. 10 is an example of a two-level sequence diagram;
FIG. 11 is a functional requirements form example;
FIG. 12 is an example of a need-behavior mapping matrix.
Detailed Description
The technical scheme for solving the problems comprises the following steps: (1) designing a life cycle segment scene, and establishing a life cycle division diagram, a segment scene series diagram and a segment scene summary diagram; (2) defining internal and external elements of the system, and establishing an element type graph and an element example graph; (3) analyzing two-level element behaviors, and establishing an activity diagram and a sequence diagram; (4) classifying, collecting, defining and mapping the operational requirement and the interactive requirement to form a function requirement form; (5) and compiling to form an unmanned aerial vehicle system function requirement file.
Firstly, carrying out stage division according to the production, delivery, use, guarantee and exit stages of the life cycle of the unmanned aerial vehicle system, and analyzing and designing a corresponding series of fragment scenes for each stage; and further, the operation purpose, the surrounding environment, the main process, the precondition and the postcondition of each segment scene, and the internal element and the external element to be analyzed are clarified.
Step (2) firstly, comprehensively analyzing all scenes of the segments of the life cycle, classifying internal and external elements, defining a primary element class and a secondary element class, and establishing a global element class diagram; and then for each segment scene, cutting the internal and external element types related to the segment scene, determining the corresponding primary element examples and secondary element examples, and establishing the element example graph.
And (3) performing element instance behavior analysis on each segment scene in turn. Firstly, designing a primary activity and a primary flow by taking a primary element example in a segment scene as an analysis object, and establishing a primary activity graph; secondly, decomposing and distributing each first-level activity into behaviors of the first-level element examples around the first-level element examples, and establishing a first-level sequence diagram; then designing a secondary activity and a flow according to the primary sequence diagram, and establishing a secondary activity diagram; and finally, decomposing and distributing each secondary activity into behaviors of the secondary element examples around the secondary element examples, and establishing a secondary sequence diagram.
And (4) defining the function requirement of each fragment scene in turn. Firstly, collecting operations and messages in a secondary sequence diagram according to the category of secondary elements, defining each operation as an operational requirement, and defining each message as an interactive requirement; merging the operability requirement and the interactivity requirement to obtain a function requirement item and form a function requirement form; and finally, establishing a mapping relation among the functional requirement items, the operation and the message, and establishing a requirement-behavior mapping matrix.
Step (5) organizing the functional requirement form established in the step (3) and the step (4) according to the life cycle stage, the segment scene, the element category, the primary activity and the secondary activity, and compiling a functional requirement file of the unmanned aerial vehicle system; organizing the models established in the steps (1), (2), (3) and (4) to form a functional requirement analysis model which is matched with the functional requirement file; and releasing the function requirement file and the function requirement analysis model together and handing over the function requirement file and the function requirement analysis model to a downstream development department, thereby providing input for the architecture design and subsystem research and development of the unmanned aerial vehicle system.
The process flow diagram of the present invention is shown in FIG. 1.
The step (1) of dividing the life cycle of the system in fig. 1 refers to dividing the life cycle of the unmanned aerial vehicle system from production to exit, and generally includes a production stage, a delivery stage, a use stage, a guarantee stage, and an exit stage. The result form of dividing the life cycle stage of the system is a life cycle division graph which is modeled and expressed by a block definition graph of SysML, and is shown in figure 2.
The step (1) of designing the segment scene of each stage in fig. 1 is to conceive the operation process of the unmanned aerial vehicle system at each stage, design and form a plurality of representative operation process segments, and further determine the operation purpose, the ambient environment, the main process, the precondition, the post condition, the internal element and the external element to be analyzed of each segment. Wherein, the segment scenes of the use stage and the guarantee stage are designed with emphasis. Designing the segment scenes of each stage, and taking a segment scene series diagram and a segment scene summary diagram corresponding to each segment scene as a result. The sequence of segment scenes is modeled using the block definition map of SysML, see FIG. 3. The segment scene overview is modeled using the usage graph of SysML, see FIG. 4.
The analysis in step (2) in fig. 1 defines two levels of elements, which means that internal elements and external elements related to unmanned aerial vehicle systems and equipment users in all segment scenes are integrated, the internal elements and the external elements are classified, and a first level element type and a second level element type are defined. And analyzing and defining the elements to be analyzed, taking a global element class diagram as a result, and performing modeling expression by adopting a block definition diagram of SysML (see figure 5).
The cropping scene element in step (2) in fig. 1 is to analyze each scene, crop the global element category according to the internal element and the external element related to the scene, and instantiate the global element category. The clip scene elements are clipped, resulting in a clip scene element instance graph for each clip scene. The example graph of the fragment scene element is modeled by an internal block diagram of SysML, see FIG. 6.
The analyzing of the primary behavior in step (3) in fig. 1 refers to analyzing each segment scene, taking the whole unmanned aerial vehicle system as an analysis object, decomposing the main process of the segment scene into a plurality of primary activities and a flow between the primary activities, and taking the form that each segment scene corresponds to one primary activity diagram as a result. On the basis, around the primary element example, each primary activity is decomposed and distributed into operations and messages of the primary element example, and the results are in the form that each primary activity corresponds to one primary sequence diagram. The primary activity map was modeled using the activity map of SysML, see FIG. 7. The primary sequence diagram was modeled using the sequence diagram of SysML, see FIG. 8.
The analysis of the secondary behavior in step (3) in fig. 1 refers to analyzing each primary sequence diagram, taking the primary element example related to the sequence diagram as an analysis object, decomposing into a plurality of secondary activities and flows among the secondary activities, and taking the form that each primary sequence diagram corresponds to one secondary activity diagram as a result. On the basis, around the secondary element instances, each secondary activity is decomposed and distributed into operations and messages of the secondary element instances, and the results are in the form of a secondary sequence diagram corresponding to each secondary activity. The secondary activity map was modeled using the activity map of SysML, see FIG. 9. Secondary sequence diagrams were modeled using the sequence diagram of SysML, see FIG. 10.
The collection in step (4) in fig. 1 defines the functional requirement, which means that all operations and messages in the secondary sequence diagram are collected according to the secondary element categories, each operation is defined as an operational requirement, and each message is defined as an interactive requirement; then, the operational requirement and the interactive requirement are merged to obtain a function requirement entry, and a function requirement form is formed and expressed in a tabular manner, as shown in fig. 11.
The requirement-behavior mapping established in step (4) in fig. 1 is to establish a mapping relationship between operations and messages in the secondary sequence diagram and function requirement entries in the function requirement table, map each operation in the secondary sequence diagram to an operational requirement, map each message to an interactive requirement, and form a result as a requirement-behavior mapping matrix expressed in a matrix chart manner, see fig. 12.
The step (5) of compiling and releasing the function requirements in fig. 1 means that the function requirement items obtained through analysis are organized according to a life cycle stage, a segment scene, a primary element type, a secondary element type, a primary activity and a secondary activity to form a function requirement file of the unmanned aerial vehicle system; meanwhile, organizing the modeling results formed in the steps (1) to (4) in a form to form a function requirement analysis model matched with the function requirement file; and finally, handing over the function demand file and the function demand analysis model to a downstream design department, and providing input for architecture design and subsystem research and development of the unmanned aerial vehicle system.
The following is further described in conjunction with the specific examples.
In an embodiment, the functional requirement analysis is performed on a unmanned aerial vehicle system with the capabilities of multi-unmanned aerial vehicle cooperation and manned/unmanned aerial vehicle cooperation.
Through the step (1), the life cycle of the unmanned aerial vehicle system is divided into a production stage, a delivery stage, a use stage, a guarantee stage and an exit stage, and a modeled life cycle division diagram is formed, as shown in fig. 2. And then designing a segment scene of each life cycle stage, wherein the scenes of the use stage comprise the segment scenes of cooperative task planning and setting, formation and take-off of double unmanned aerial vehicles, convergence of unmanned aerial vehicles called by people, multi-machine air aggregation formation, double-machine cooperative detection and identification and the like, and establishing a scene series diagram of the use stage, which is shown in figure 3. And designing each fragment scene, wherein a fragment scene overview chart of the multi-machine air aggregation formation fragment scene is shown in figure 4.
And (3) integrating internal elements and external elements of all the fragment scenes through the step (2), and defining a class of primary elements, wherein the internal elements comprise airplanes, loads and command control systems belonging to an unmanned aerial vehicle system, equipment support personnel and ground task personnel belonging to equipment using personnel, and the external elements comprise airspace control mechanisms, people and targets. Defining secondary element categories including an autonomous decision domain, an observation perception domain, a flight control domain and a platform resource domain belonging to the airplane, and a single machine control domain, a cooperative supervision domain, a task planning domain and a networking communication domain belonging to the command and control system, see fig. 5. And then, element category clipping and instantiation are carried out on each segment scene, and an element instance diagram is established. An example of the elements of the multi-machine air aggregation queuing clip scenario is shown in fig. 6.
Through the step (3), performing element instance behavior analysis on each segment scene in sequence, and establishing a primary activity diagram, wherein the multimachine air assembly formation segment scene is decomposed into a preset area assembly, grouping communication is established, control right handover is performed, formation sails for 5 primary activities, and the primary activity diagram is shown in a figure 7; secondly, decomposing and distributing each primary activity into behaviors of the primary element examples around the primary element examples, and establishing a primary sequence diagram, wherein the primary sequence diagram of the preset area assembly activity in the scene of the air assembly formation fragment is shown in a figure 8; then designing secondary activities and processes according to the primary sequence diagram, and establishing a secondary activity diagram, wherein the assembly activities of the preset areas in the assembly formation fragment scene are decomposed into M1 human-to-airplane arrival assembly areas, A1 airplane arrival assembly areas and A2 airplane arrival assembly areas, and the corresponding secondary activity diagram is shown in FIG. 9; finally, around the secondary element instances, each secondary activity is decomposed into behaviors that are assigned to the secondary element instances, where a1 secondary sequence diagram of the plane arrival gather area activity is shown in fig. 10.
And (5) sequentially defining the function requirements of each fragment scene through the step (4), forming a function requirement form, and establishing a requirement-behavior mapping matrix. An example of a functional requirement form of a multi-machine over-the-air assembly queuing fragment scenario is shown in fig. 11, and an example of a requirement-behavior mapping matrix is shown in fig. 12.
And (5) forming a function requirement file and a function requirement analysis model of the unmanned aerial vehicle system, releasing the files together and handing over the files to downstream development departments.

Claims (7)

1. A model-based equipment system function requirement analysis method is characterized by comprising the following steps:
step (1), dividing the whole life cycle of the equipment according to stages, and analyzing and designing a corresponding series of fragment scenes for each stage; defining internal elements and external elements to be analyzed of each segment scene;
classifying internal and external elements according to all segment scenes of the full life cycle of the equipment, and defining a primary element class and a secondary element class; further, for each segment scene, cutting internal and external element types related to the segment scene, and determining corresponding primary element examples and secondary element examples;
and (3) performing behavior analysis of element instances on each segment scene: firstly, designing primary activities and processes by taking a primary element example in a segment scene as an analysis object, and establishing a primary activity diagram; secondly, decomposing and distributing each first-level activity into behaviors of the first-level element examples around the first-level element examples, and establishing a first-level sequence diagram; then designing a secondary activity and a flow according to the primary sequence diagram, and establishing a secondary activity diagram; finally, decomposing and distributing each secondary activity into behaviors of the secondary element examples around the secondary element examples, and establishing a secondary sequence diagram;
Step (4), defining the function requirement of each fragment scene: firstly, collecting operations and messages in a secondary sequence diagram according to secondary element types, defining each operation as a functional requirement, and defining each message as an interactive requirement; merging the operability requirement and the interactivity requirement to obtain a function requirement item and form a function requirement form; finally, establishing a mapping relation among function requirement items, operation and messages, and establishing a requirement-behavior mapping matrix;
step (5), organizing the function requirement form established in the step (3) and the step (4) according to the life cycle stage, the fragment scene, the element category, the primary activity and the secondary activity, and compiling an equipment function requirement file; organizing the models established in the steps (1), (2), (3) and (4) to form a functional requirement analysis model which is matched with the functional requirement file; and releasing the function requirement file and the function requirement analysis model together and handing over the function requirement file and the function requirement analysis model to a downstream development department, thereby providing input for equipment architecture design and subsystem development.
2. The method for analyzing functional requirements of a model-based equipment system according to claim 1, wherein in step (1), the operational purpose, the surrounding environment, the main process, the precondition and the postcondition of each segment scene are also determined.
3. The model-based equipment system functional requirement analysis method of claim 1, wherein the result form of each stage segment scene comprises a segment scene series diagram and a segment scene summary diagram corresponding to each segment scene.
4. The model-based equipment system functional requirement analysis method of claim 3, wherein the segment scene series diagram is modeled by using a block definition diagram of SysML, and the segment scene summary diagram is modeled by using a use diagram of SysML.
5. The method for analyzing the functional requirements of the model-based equipment system according to claim 1, wherein the defined primary element classes and secondary element classes form a global element class diagram;
and clipping the global element category, instantiating to form an example graph of the element of the fragment scene corresponding to each fragment scene.
6. The model-based equipment system functional requirement analysis method of claim 5, wherein the global element category graph and the fragment scene element instance graph are modeled by using SysML block definition graph.
7. The method of claim 1, wherein the equipment is an unmanned aerial vehicle system.
CN202011397410.6A 2020-12-04 2020-12-04 Equipment system function demand analysis method based on model Active CN112527245B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011397410.6A CN112527245B (en) 2020-12-04 2020-12-04 Equipment system function demand analysis method based on model

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011397410.6A CN112527245B (en) 2020-12-04 2020-12-04 Equipment system function demand analysis method based on model

Publications (2)

Publication Number Publication Date
CN112527245A CN112527245A (en) 2021-03-19
CN112527245B true CN112527245B (en) 2022-06-28

Family

ID=74997323

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011397410.6A Active CN112527245B (en) 2020-12-04 2020-12-04 Equipment system function demand analysis method based on model

Country Status (1)

Country Link
CN (1) CN112527245B (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004157950A (en) * 2002-11-03 2004-06-03 Yoshihide Nakabachi Construction method and support apparatus for object model by scenario analysis

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1202167B1 (en) * 2000-10-27 2003-07-30 Interactive Objects Software GmbH Method for model based object oriented development of external interfaces for distributed software systems
US20120143570A1 (en) * 2010-12-03 2012-06-07 University Of Maryland Method and system for ontology-enabled traceability in design and management applications
US20130227382A1 (en) * 2012-02-29 2013-08-29 Naoufel Boulila Method and system for extracting requirements from narratives
CN110989973A (en) * 2019-11-14 2020-04-10 中国人民解放军陆军装甲兵学院 Scene-driven complex product function requirement analysis method and system
CN111142845B (en) * 2019-12-18 2023-03-28 中国北方车辆研究所 Model-based task system demand development method

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004157950A (en) * 2002-11-03 2004-06-03 Yoshihide Nakabachi Construction method and support apparatus for object model by scenario analysis

Also Published As

Publication number Publication date
CN112527245A (en) 2021-03-19

Similar Documents

Publication Publication Date Title
CN107169575A (en) A kind of modeling and method for visualizing machine learning training pattern
CN106557457B (en) QT-based system for automatically generating cross-platform complex flow chart
CN108170162B (en) Performance evaluation method for multi-scale wind disturbance analysis unmanned aerial vehicle cluster coordination control system
CN113255916A (en) Using method of combat knowledge system and combat decision auxiliary method
Zhao et al. An incremental clustering method for anomaly detection in flight data
CN113722912B (en) Virtual-real fused unmanned cluster collaborative verification system
CN114840022A (en) MAS-based multi-unmanned system supervision control method
Lytvyn et al. Aviation aircraft planning system project development
Slim et al. Convergence and contradiction between lean and Industry 4.0 for inventive design of smart production systems
CN110838055A (en) Electric power enterprise financial data management system based on big data
Polacsek et al. Towards thinking manufacturing and design together: An aeronautical case study
CN109871635B (en) Operation scene modeling method for capturing top-layer requirements of civil aircraft
Chen et al. Big data platform of air traffic management
CN112527245B (en) Equipment system function demand analysis method based on model
CN112084323B (en) Airworthiness approval cooperative work platform and method
US10614392B1 (en) Graphical flight dashboard display and method
CN107992560A (en) A kind of Information System configuration device based on configuration
Alharasees et al. Human Factors in the Age of Autonomous UAVs: Impact of Artificial Intelligence on Operator Performance and Safety
CN112214209B (en) Modeling method for interaction information and task time sequence in unmanned aerial vehicle operation scene
Werther et al. Colored Petri Net based formal airport control model for simulation and analysis of airport control processes
Mekdeci et al. System architecture pliability and trading operations in tradespace exploration
Luo et al. TFCluster: an efficient algorithm to mine maximal differential function-resource biclusters for single pilot operations safety analysis
Zhang et al. An Improved SoSE Model–The “V+” Model
Marti Structured task analysis in complex domains
Formentini et al. CDFA method: a way to assess assembly and installation performance of aircraft system architectures at the conceptual design

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