Model-based servitization design method
By adopting a model-based service-oriented design approach, the avionics system is transformed from process-oriented design to function object-oriented design, which solves the problems of high system coupling, poor function reusability, difficult maintenance and poor consistency, and achieves consistency between system design and software implementation and high function reusability.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-28
- Publication Date
- 2026-04-03
AI Technical Summary
Traditional avionics system design methods suffer from problems such as high system coupling, poor functional reusability, difficult maintenance, poor consistency between requirements and design, and poor traceability, which are particularly evident in complex systems.
By adopting a model-based service-oriented design approach, the avionics system is transformed from process-oriented design to function-object-oriented design. Through service-oriented design, the system functions are decomposed into independent services, and the capabilities are exposed through interfaces to achieve loosely coupled interaction, supporting high reusability and scalability of services.
This achieves a high degree of consistency between system design results and software implementation, reduces maintenance difficulty, improves functional reusability and portability, and supports efficient system iteration and upgrades.
Smart Images
Figure CN121785587A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of model-based systems engineering technology, and specifically relates to a model-based service design method. Background Technology
[0002] The guiding significance of model-based systems engineering for the development and design of complex systems has long been recognized in the industry. However, traditional avionics system design methods mainly adopt a process-oriented design paradigm. This method focuses on sequentially executed task steps and decomposes system functions into a series of predefined processes. Although it achieves specific functions, it generally has the following limitations: a) High system coupling: The functional modules are closely interdependent, and modifying a certain function requires recompiling and deploying the entire system; b) Poor reusability: The functionality is tightly bound to the hardware platform and the underlying operating system, making it difficult to port to different systems; c) Maintenance difficulties: As system complexity increases, adding new functions or modifying existing logic is risky, costly, and technically challenging. d) Poor consistency and traceability: The system design results and software implementation are not well integrated, and consistency cannot be accurately traced. Meanwhile, existing process-oriented design methods have revealed significant shortcomings in modern complex avionics systems. Problems such as numerous projects, frequent requirement iterations, a surge in the number of software programs, and heavy reliance on human resources all require systematic design methods to solve, lacking a complete design framework to guide the process from requirements to deployment. Summary of the Invention
[0003] The purpose of this invention is to address the problems of high system coupling, poor functional reusability, maintenance difficulties, poor consistency between requirements and design, and poor traceability in the development of avionics systems using traditional process-oriented design methods. This invention provides a model-based service-oriented design method that transforms the design of avionics systems from a business process-oriented approach to a functional object-oriented approach, achieving the design goals of high modularity, service reusability, and system scalability.
[0004] To achieve the above objectives, the technical solution adopted by the present invention is as follows: In a first aspect, the present invention provides a model-based service-oriented design method, which includes the following steps: Based on user input, analyze the functions the system needs to provide to meet those needs, and form system use cases. Based on the initial decomposition of the system use cases, identify the relevant capabilities and form key activities; Key activities serve as the prototype of service operations. Under the constraints of system architecture and functional domain division, service operations related to the same business domain are clustered to form services. Analyze the service operations' dependencies, driving methods, internal logic processes, and the capabilities that the service operations can provide externally, and expose them to the outside world in the form of interfaces; The interface is designed in detail, including its name and identifier, type, load capacity, and performance. Service deployment is based on the service's dependence on hardware resources, the service's own QoS requirements, and the mutual influence between services; Virtual simulations of services are performed using simulation software, and the simulation results are monitored to verify the correctness of the design. The service code framework is automatically generated based on the relationships between services and the data structure transfer relationships.
[0005] As a further technical solution of the present invention: analyze and clarify the system use cases involved in the requirements, and analyze the preliminary process of the system to implement the requirements.
[0006] As a further technical solution of the present invention: key activities are obtained through domain analysis.
[0007] As a further technical solution of the present invention: the service operation processing logic is a general description of the functions of the service operation.
[0008] As a further technical solution of the present invention: the service operation interface is the only and standard entry point for other services to use the service capability.
[0009] As a further technical solution of the present invention: define the interface name, identifier, type, and performance, and design the interface load.
[0010] As a further technical solution of the present invention: the priority considerations for service deployment are as follows: First consider the service's dependence on hardware resources; Next, consider the mutual influence between service software; Finally, consider the QoS requirements of the service itself.
[0011] As a further technical solution of the present invention: service code development is realized by passing the framework code to the downstream, thereby achieving consistency between design and development.
[0012] In a second aspect, the present invention provides an electronic device for executing the above-described service-oriented design method, comprising: a processor and a memory storing a computer program, wherein when the processor runs the computer program, the steps of the above-described service-oriented design method are implemented.
[0013] Thirdly, the present invention provides a computer storage medium storing a computer program, which, when executed by a processor, implements the steps of the above-described service-oriented design method.
[0014] Compared with the prior art, the beneficial effects of the present invention are as follows: This invention adopts an object-oriented design paradigm instead of the traditional procedural design paradigm, specifically as follows: a) Encapsulation: Encapsulates data and its operations within a service object, providing a clear interface to the outside world; b) Consistency between design and development: The system design results and software implementation are highly integrated, and consistency can be accurately traced; c) Inheritance: By deeply cultivating domain knowledge, and using services as a carrier, functions are driven to be inherited, iterated, and upgraded within the services; d) Portability: The service itself is separated from design logic and deployment relationships, improving the reusability and portability of functional design. Attached Figure Description
[0015] Figure 1 This is a flowchart of a model-based service design method according to the present invention.
[0016] Figure 2 This is a schematic diagram of the source code files of the service framework of this invention. Detailed Implementation
[0017] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions in the embodiments of this invention will be described in more detail below with reference to the accompanying drawings.
[0018] In the accompanying drawings, the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The described embodiments are some, but not all, of the embodiments of the present invention.
[0019] The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain the present invention, and should not be construed as limiting the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.
[0020] The following is in conjunction with the appendix Figure 1-2 The embodiments of the present invention will be described in detail below.
[0021] Example 1 This invention discloses an eight-step service-oriented design method, comprehensively covering the entire process from requirements analysis to service simulation. Compared to traditional design methods, the core innovation of this invention lies in shifting from a business process-oriented design method to a functional object-oriented design method. It decomposes system functions into cohesive, independent services and exposes capabilities through service interfaces to achieve loosely coupled interaction.
[0022] According to the service-oriented design method of the present invention, the method includes: 1. Requirements analysis: Based on user input, this step analyzes the functions required by the system to meet those requirements; these functions are system use cases. The method analyzes and clarifies the system use cases involved in the requirements, including the preliminary process of implementing the requirements, the approximate scope of impact, and the functional domain. 2. Business chain design: Based on the preliminary decomposition of the system use cases, this step clarifies the involved capabilities and forms key activity items. Key activities can generally be obtained through domain analysis. 3. Preliminary service design: In defining the business chain, the key activities are the prototypes of service operations. Under constraints such as system architecture and functional domain division, service operations related to the same business domain are clustered to form services. 4. Service operation processing logic design: This step provides a general description of the functions of the service operations. The method analyzes the dependencies, driving methods, internal logic processes, and capabilities that the service operations can provide externally, i.e., exposed externally in the form of interfaces. 5. Detailed design of the service operation interface: This step is the unique and standard entry point for other services to use the service capabilities. The detailed design of specific interfaces should include the following: interface name and identifier, interface type, interface load, interface performance, etc.; service deployment design, which takes into account the service's dependence on network and hardware, computing power, and its own QoS requirements, as well as the mutual influence between service software and system backup level requirements, to comprehensively design the service deployment and define the hardware platform on which the service should be deployed; service simulation, which supports the virtual simulation of the service model through simulation software, real-time monitoring of simulation results, and verification of the correctness of the design; and service framework code generation, which automatically generates the service code framework based on the relationships between services and data structure transmission relationships, and passes the framework code to downstream services to achieve service code development, thus ensuring consistency between design and development.
[0023] Example 2 This invention discloses a model-based service design method, which includes the following steps: 1) Requirements Analysis: a) Functional requirements: Provide functions such as route calculation, position update, and yaw alarm; b) Service boundaries: Divide into "Navigation Calculation Service", "Location Acquisition Service", "Alarm Service", etc.; 2) Business chain design: a) Business process: Flight plan loading → Periodic position acquisition → Route deviation calculation → Yaw alarm triggering; b) Business activities: These are broken down into discrete activities such as "plan loading", "location acquisition", "deviation calculation" and "alarm judgment". 3) Preliminary Service Definition a) Navigation calculation service: including route update service operation and deviation calculation service operation; b) Location acquisition service: including location request service operation and location update service operation; c) Alarm service: including alarm judgment service operations; 4) Service Operation Design a) Taking navigation computing services as an example: i. Input: Current position coordinates; ii. Output: Deviation from flight path iii. Exceptions: Invalidity handling logic, computation timeout handling logic 5) Service Interface Design a) Define standardized interfaces using IDL: Interface NavigationService { Double calculateDeviation(in Coordinate currentPos); Void updateRoute(in Route newRoute); } 6) Service deployment design: a) Deployment topology: Navigation computing services are deployed on high-performance processing nodes, and location acquisition services are deployed on dedicated navigation hardware nodes; b) Fault-tolerant deployment: Critical services such as alarm services are deployed with dual-node redundancy; 7) Service Simulation: a) Functional verification: Simulate various flight scenarios to verify the correctness of navigation calculations; b) Integration testing: Verify that the navigation service works properly with other systems; 8) Service framework code generation: a) Generate the service software source code file.
[0024] Example 3 This invention provides an electronic device, including: a processor and a memory storing a computer program; in practical applications, the number of processors can be one or more; the number of memories can be one or more. When the processor runs the computer program, the service-oriented design method applied to the above-described electronic device is implemented.
[0025] The memory can be volatile or non-volatile, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).
[0026] The memory of this invention is used to store various types of data to support the operation of the electronic device. Examples of such data include: any computer programs used to operate on the electronic device, such as operating systems and applications; contact data; phonebook data; messages; pictures; videos, etc. The operating system includes various system programs, such as a framework layer, core library layer, driver layer, etc., used to implement various basic services and handle hardware-based tasks. Applications can include various applications, such as media players, browsers, etc., used to implement various application services. Here, the program implementing the method of the embodiments of this invention can be included in the application.
[0027] Example 4 This invention provides a computer storage medium storing a computer program. The computer storage medium can be a magnetic random access memory (FRAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM), etc.; it can also be various devices including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc. When the computer program stored in the computer storage medium is executed by a processor, it implements the service-oriented design method applied to the aforementioned electronic device.
[0028] Thus, the objective of this invention has been achieved.
[0029] The above description is merely a specific embodiment of the present invention, providing a detailed description of the invention. Parts not covered herein are conventional techniques. However, the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention. The scope of protection of the present invention should be determined by the scope of the claims.
Claims
1. A model-based service-oriented design method, characterized in that, Includes the following steps: Based on user input, analyze the functions the system needs to provide to meet those needs, and form system use cases. Based on the initial decomposition of the system use cases, identify the relevant capabilities and formulate key activities; Key activities serve as the prototype of service operations. Under the constraints of system architecture and functional domain division, service operations related to the same business domain are clustered to form services. Analyze the service operations' dependencies, driving methods, internal logic processes, and the capabilities they can provide externally, exposing them to the outside world in the form of interfaces; The interface is designed in detail, including its name and identifier, type, load capacity, and performance. Service deployment is based on the service's dependence on hardware resources, the service's own QoS requirements, and the mutual influence between services; Virtual simulations of services are performed using simulation software, and the simulation results are monitored to verify the correctness of the design. The service code framework is automatically generated based on the relationships between services and the data structure transfer relationships.
2. The model-based service design method according to claim 1, characterized in that, Analyze and clarify the system use cases involved in the requirements, and analyze the preliminary process of the system to implement the requirements.
3. The model-based service design method according to claim 1, characterized in that, Key activities are identified through domain analysis.
4. The model-based service design method according to claim 1, characterized in that, Service operation processing logic is a general description of the functionality of a service operation.
5. The model-based service design method according to claim 1, characterized in that, The service operation interface is the only and standard entry point for other services to use the service's capabilities.
6. The model-based service-oriented design method according to claim 5, characterized in that, Define the interface name, identifier, type, and performance, and design the interface load.
7. The model-based service design method according to claim 1, characterized in that, The priority for service deployment is as follows: First consider the service's dependence on hardware resources; Next, consider the mutual influence between service software; Finally, consider the QoS requirements of the service itself.
8. The model-based service design method according to claim 1, characterized in that, By passing the framework code to downstream service code development, consistency between design and development is achieved.
9. An electronic device, characterized in that, include: A processor and a memory storing a computer program, wherein, when the processor executes the computer program, the service-oriented design method of any one of claims 1 to 8 is implemented.
10. A computer storage medium, characterized in that, The system contains a computer program that, when executed by a processor, implements the service-oriented design method as described in any one of claims 1 to 8.