Impeller machine design software architecture and impeller machine design method
By introducing a hierarchical architecture and interface layer into the impeller mechanical design software, the dependencies between modules are decoupled, and the problem of high coupling between modules is solved, the scalability, maintainability and compilation efficiency of the software are improved, and the development is improved. efficiency.
Patent Information
- Application Number
- CN202411524509.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-30
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2044-10-30
AI Technical Summary
Due to the high coupling between modules, impeller mechanical design software leads to low development efficiency and reduced compilation efficiency, which affects the development and application of the software.
Adopt a hierarchical architecture, including application layer, business logic layer, data layer, algorithm layer and interface layer, decoupling each module through the interface layer, providing a unified calling method, reducing the coupling between modules, and improving the scalability of the software. Maintenance and compilation efficiency.
It effectively reduces the coupling between the various modules of the software, improves the scalability, maintainability and compilation efficiency of the software, and improves the efficiency of software development.
Smart Images

Figure CN119047096A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of computer-aided engineering, and more specifically, to a turbomachinery design software architecture and turbomachinery design method. Background Technology
[0002] In traditional application software development, especially in complex business processes, interdependencies between internal software modules are very common. Taking turbomachinery design software as an example, its technical characteristics dictate that it needs to handle massive amounts of parameters, multiple triggering conditions, and diverse algorithms in practical applications, resulting in a large software scale with code volumes reaching millions of lines.
[0003] Currently, with the continuous development and iteration of turbomachinery design software, the complexity of the software architecture is increasing, and when there are interdependencies between business processes, the coupling between modules will significantly increase. This high coupling not only makes it easy for code modifications during development to trigger problems in other modules, but also reduces the software's compilation efficiency, thereby affecting the software's development and application.
[0004] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention
[0005] The purpose of this disclosure is to provide a software architecture for turbomachinery design, thereby at least partially solving the problem of low software development efficiency caused by the high coupling between turbomachinery design software modules in related technologies.
[0006] According to a first aspect of this disclosure, a turbomachinery design software architecture is provided, comprising: The application layer is used to display the interactive interface of the turbomachinery design software and the design views generated during the turbomachinery design process; The business logic layer is used to implement multiple functional modules for turbomachinery design. These multiple functional modules include at least one-dimensional design, detailed design, fluid simulation, structural simulation, discrete fitting, and computer-aided manufacturing of turbomachinery. The system comprises a data layer and an algorithm layer. The data layer provides turbomachinery design data for the application layer and the algorithm layer provides turbomachinery design algorithms corresponding to each of the functional modules to the business logic layer. An interface layer is used to provide corresponding interfaces for each of the functional modules, so that the functional dependency layer related to each functional module can obtain the corresponding turbomachinery design data from the functional implementation layer through the interface and / or execute the corresponding turbomachinery design algorithm in the functional implementation layer. The functional implementation layer and functional dependency layer include at least one of the application layer, business logic layer, data layer and algorithm layer.
[0007] In one exemplary embodiment of this disclosure, the interface layer includes interface modules corresponding to each of the functional modules, and each interface module includes: An interface establishment unit is used to define corresponding business interface classes for each of the aforementioned functional modules; A pointer creation unit is used to create interface class objects corresponding to each of the business interface classes in the functional dependency layer implementation class in response to the operation of the turbomachinery design software. The subclass construction unit is used to initialize the target function in the implementation layer class based on the interface function initialization function in the business interface class; The business implementation unit is used to call the interface function in the business interface class through the interface class object, and call the target function in the implementation class of the function implementation layer according to the interface function, so that the function dependency layer can use the target function to obtain the corresponding turbomachinery design data from the function implementation layer and / or execute the corresponding turbomachinery design algorithm in the function implementation layer.
[0008] In one exemplary embodiment of this disclosure, each of the interface modules further includes: The virtual table creation unit is used to create a virtual table based on the interface functions in the business interface class. The virtual table includes at least the original virtual functions used to implement the corresponding functional modules and their corresponding original addresses.
[0009] In one exemplary embodiment of this disclosure, the subclass constructor unit includes: The function constructor subunit is used to initialize the target function in the implementation class of the functional implementation layer according to the original virtual functions in the virtual table; The virtual table rewriting subunit is used to rewrite the original virtual function and its corresponding original address in the virtual table according to the target function and the corresponding target address.
[0010] In one exemplary embodiment of this disclosure, the service implementation unit includes: The virtual table determination subunit is used to determine the corresponding virtual table based on the interface class object, and to call the interface function in the business interface class based on the interface class object; The business implementation subunit is used to determine the target address corresponding to the current business type in the virtual table according to the interface function, and call the target function according to the target address to start the first business logic of obtaining the corresponding turbomachinery design data from the functional implementation layer and / or the second business logic of executing the corresponding turbomachinery design algorithm in the functional implementation layer.
[0011] According to a second aspect of this disclosure, a turbomachinery design method is provided, implemented based on the turbomachinery design software architecture described in any one of the preceding claims, the method comprising: In response to the startup operation of the target functional module in the interactive interface of the turbomachinery design software, the interface layer is determined to be the business interface provided by the target functional module; The functional dependency layer related to the target functional module obtains the corresponding turbomachinery design data from the functional implementation layer through the business interface and / or executes the corresponding turbomachinery design algorithm in the functional implementation layer; The functional implementation layer and functional dependency layer include at least one of the following: application layer, business logic layer, data layer, and algorithm layer.
[0012] In one exemplary embodiment of this disclosure, the functional dependency layer related to the target functional module obtains corresponding turbomachinery design data from the functional implementation layer through the business interface and / or executes corresponding turbomachinery design algorithms in the functional implementation layer, including: In response to the operation of the turbomachinery design software, an interface class object corresponding to the business interface class defined in the business interface is created in the functional dependency layer implementation class; The target function in the implementation layer is implemented based on the interface function initialization function in the business interface class. The interface class object calls the interface function in the business interface class, and the interface function calls the target function in the function implementation layer implementation class to start the first business logic of obtaining the corresponding turbomachinery design data from the function implementation layer and / or the second business logic of executing the corresponding turbomachinery design algorithm in the function implementation layer.
[0013] In one exemplary embodiment of this disclosure, the method further includes: The turbomachinery design data obtained from the functional implementation layer and / or the design results after executing the turbomachinery design algorithm in the functional implementation layer are stored in the data layer and displayed through the application layer.
[0014] According to a third aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processing unit, implements the turbomachinery design method described in any of the preceding claims.
[0015] According to a fourth aspect of this disclosure, an electronic device is provided, comprising: A processing unit; and a storage unit for storing executable instructions of the processing unit; wherein the processing unit is configured to execute the turbomachinery design method described above by executing the executable instructions.
[0016] The exemplary embodiments disclosed herein may have some or all of the following beneficial effects: In the turbomachinery design software architecture provided in the exemplary embodiments of this disclosure, the application layer is used to display the interactive interface of the turbomachinery design software and the design views generated during the turbomachinery design process; the business logic layer is used to implement multiple functional modules of turbomachinery design; the data layer is used to provide turbomachinery design data for display by the application layer; the algorithm layer is used to provide turbomachinery design algorithms corresponding to each functional module; and the interface layer is used to provide corresponding interfaces for each functional module, so that the functional dependency layers related to each functional module can obtain corresponding turbomachinery design data from the functional implementation layer through the interface and / or execute corresponding turbomachinery design algorithms in the functional implementation layer. The functional implementation layer and the functional dependency layer include at least one of the application layer, business logic layer, data layer, and algorithm layer. This disclosure solves the problem of mutual dependence between the business logic layer, application layer, data layer, and algorithm layer used for turbomachinery design by adding an interface layer, thereby reducing the coupling between software modules. Combined with the layered architecture formed based on the interface layer, the software's scalability, maintainability, and compilation efficiency can be effectively improved, thereby improving software development efficiency.
[0017] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description
[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.
[0019] Figure 1 A schematic diagram of a turbomachinery design software architecture is shown in an embodiment of this disclosure.
[0020] Figure 2 A schematic diagram of the interface layer in a turbomachinery design software architecture according to an embodiment of this disclosure is shown.
[0021] Figure 3 A flowchart illustrating a turbomachinery design software method according to an embodiment of this disclosure is shown.
[0022] Figure 4 This illustration shows a schematic diagram of the interaction between the application layer and the business logic layer in a turbomachinery design software architecture according to an embodiment of this disclosure.
[0023] Figure 5This illustration shows a schematic diagram of the interaction between the business logic layer and the business logic layer in a turbomachinery design software architecture according to an embodiment of this disclosure.
[0024] Figure 6 A schematic diagram of the structure of an electronic device suitable for implementing embodiments of the present disclosure is shown.
[0025] In the accompanying drawings, the same or corresponding reference numerals indicate the same or corresponding parts. Detailed Implementation
[0026] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this disclosure more comprehensive and complete, and to fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a full understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced with one or more of the specific details omitted, or other methods, components, apparatus, steps, etc., can be employed. In other instances, well-known technical solutions are not shown or described in detail to avoid obscuring various aspects of this disclosure.
[0027] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.
[0028] This disclosure provides an example implementation of a turbomachinery design software architecture, with reference to... Figure 1As shown, the turbomachinery design software architecture includes an application layer 101, a business logic layer 102, a data layer 103, an algorithm layer 104, and an interface layer 105. The application layer 101 displays the interactive interface of the turbomachinery design software and the design views generated during the turbomachinery design process. The business logic layer 102 implements multiple functional modules for turbomachinery design, including at least one-dimensional design, detailed design, fluid simulation, structural simulation, discrete fitting, and computer-aided manufacturing. The data layer 103 provides turbomachinery design data for the application layer, and the algorithm layer 104 provides turbomachinery design algorithms corresponding to each functional module to the business logic layer. The interface layer 105 provides corresponding interfaces for each functional module, enabling functional dependency layers related to each module to obtain corresponding turbomachinery design data from the functional implementation layer and / or execute corresponding turbomachinery design algorithms at the functional implementation layer.
[0029] It should be noted that the functional implementation layer and functional dependency layer related to each functional module include at least one of the following: application layer, business logic layer, data layer, and algorithm layer. Specifically, for any functional module in the turbomachinery design software architecture, the functional implementation layer and functional dependency layer related to that module can be the same or different; this disclosure does not impose any limitations on this. For example, the functional implementation layer related to the discrete fitting module can be the business logic layer 102, and the functional dependency layer can be the application layer 101, to enable interaction with the interactive interface during the discrete fitting process. As another example, both the functional implementation layer and functional dependency layer related to the detailed design module can be the business logic layer 102. When entering the detailed design module through the discrete fitting operation interface, a detailed design business process can be performed based on the turbomachinery design data obtained from the discrete fitting module.
[0030] For example, in application layer 101, the interactive interface of the turbomachinery design software may include a menu bar, navigation bar, shortcut toolbar, and dialog boxes. The shortcut toolbar may include commonly used tool buttons such as creating new components, adding boundary conditions, and running simulation calculations. Dialog boxes can be used for functions such as inputting parameters, setting options, and confirming operations. The design views generated during the turbomachinery design process may include meridional views, 3D views, various views related to blade parameters such as blade thickness distribution diagrams, flow channel cross-sectional diagrams, residual curves from the solution process, and post-solution contour plots such as pressure distribution diagrams, temperature distribution diagrams, and line graphs such as pressure gradient diagrams along the blade surface.
[0031] In the business logic layer 102, the one-dimensional design module can include calculating the geometric and aerodynamic data of the turbomachinery based on the aerodynamic parameters and fluid working medium provided by the application layer 101; the detailed design module can include performing detailed design based on the blade flow channel data passed in from the one-dimensional design module; the fluid simulation module can include performing simulation calculations based on the blade data, flow channel data, and aerodynamic data generated by the detailed design module to verify whether the designed turbomachinery can achieve the expected performance effect; the structural simulation module can include generating a three-dimensional model based on the blade data and hub casing data generated by the detailed design module, and generating a mesh and adding boundary conditions based on the three-dimensional model, and using computer simulation and analysis to predict and optimize the structural design of the turbomachinery under various working conditions.
[0032] The data layer 103 includes at least various types of turbomachinery design data, such as aerodynamic data, fluid working medium data, flow channel parameter data, section data, blade data, flow channel data, mesh data, boundary condition data, and solution data. The algorithm layer 104 provides at least a variety of turbomachinery design algorithms required for turbomachinery design, including basic geometric algorithms, 3D model modeling algorithms, flow channel geometry smoothing algorithms, structured mesh generation algorithms, unstructured mesh generation algorithms, and surface discretization algorithms.
[0033] Interface layer 105 can separate the application layer 101, business logic layer 102, data layer 103, and algorithm layer 104 in the turbomachinery design software architecture. This means that layers or modules with dependencies can indirectly interact through the interfaces provided by interface layer 105. For example, in the discrete fitting module, the discrete function is initiated by application layer 101, but the discrete fitting function is implemented by business logic layer 102. Furthermore, it needs to pick up corresponding geometric elements from the model view displayed by application layer 101 for discrete fitting. In this case, interface layer 105 can be used to pick up the geometric elements from application layer 101 and then pass the acquired geometric elements to business logic layer 102 for discrete fitting processing.
[0034] By adding interface layer 105 to the turbomachinery design software architecture, not only are the coupling relationships between different layers and modules resolved, but the various parts can also work together correctly, thus ensuring the stable application and upgradeability of the software. Furthermore, interface layer 105 provides a unified calling method for multiple functional modules in the turbomachinery design software architecture, making it easy to integrate new functional modules into the existing system architecture, while also facilitating the upgrading or replacement of older functional modules.
[0035] In the exemplary embodiment of this disclosure, the interface layer 105 includes interface modules corresponding to each functional module. Specifically, when constructing the interface layer 105, corresponding interface modules are established according to different functional modules. (See reference...) Figure 2 As shown, a schematic diagram of an interface layer is presented, where interface layer 105 includes a detailed design interface module, a fluid simulation interface module, a structural simulation interface module, a discrete fitting interface module, and a geometric algorithm interface module. Furthermore, specific interfaces are defined within the interface modules. By establishing connections with corresponding layers through these interfaces, the direct dependencies between different modules in the software architecture can be altered, thereby achieving decoupling between modules.
[0036] Each interface module includes an interface creation unit, a pointer creation unit, a subclass construction unit, and a business implementation unit. The interface creation unit defines the corresponding business interface classes for each functional module. A business interface class is a concrete class that implements the interface, providing the specific implementations of the methods declared in the interface. For example, for the discrete fitting module, the defined business interface class could be either a discrete fitting execution interface class or a window interface class. It's understandable that for different business interface classes defined within the same functional module, the corresponding functional implementation layer and functional dependency layer can be the same or different. Continuing with the discrete fitting module as an example, for the discrete fitting execution interface class defined in this module, its corresponding functional implementation layer is the business logic layer, and its functional dependency layer is the application layer. For the window interface class, its corresponding functional implementation layer is the application layer, and its functional dependency layer is the business logic layer. It can be seen that different business interface classes provide different specific implementations of the methods, corresponding to different business processing modules.
[0037] Furthermore, the interface establishment unit also includes an interface description generation subunit, which is used to generate corresponding interface description documents based on the definitions of each business interface class, so as to facilitate development and maintenance.
[0038] For example, the interface description generation subunit dynamically retrieves interface information using reflection to ensure its accuracy. It also parses metadata about the business interface class definition, including class name, method name, parameter types, return type, and comments, supporting various document formats. Additionally, a template engine can be provided to generate documentation, ensuring consistent formatting. When the business interface class is modified, the interface description generation subunit automatically updates the documentation.
[0039] Based on the generated interface description documentation, developers can quickly understand the use of the interfaces, reducing errors caused by interface changes. Furthermore, development can be based on the same interface documentation, reducing communication costs. Simultaneously, the automatic documentation generation reduces the workload of manual writing, lowering the probability of errors and making the development process of turbomachinery design software more efficient and reliable.
[0040] It should be noted that each interface module also includes a virtual table creation unit, used to create a virtual table based on the interface functions in the business interface class when the business interface class is created. This virtual table includes at least the primitive virtual functions used to implement the corresponding functional module and their corresponding primitive addresses. Since the interface functions in the business interface class are pure virtual functions, the primitive addresses in the corresponding virtual table are empty. It's important to note that in actual use, an empty primitive address means that initialization or overriding has not been completed during the construction process, and the address currently points to a default error handling function. Therefore, when constructing subclasses, it is necessary to ensure that all interface functions are correctly initialized or overridden to avoid runtime errors.
[0041] The pointer creation unit is used to respond to the operation of the turbomachinery design software by creating interface class objects corresponding to each business interface class in the functional dependency layer implementation class. For example, for the discrete fitting running interface class defined by the discrete fitting module, when the turbomachinery design software runs, a corresponding interface class object, denoted as m_pDispFitRun, will be created in the functional dependency layer, such as the application layer. Here, m represents a member variable in a class that can store data or call functions in that class, p represents a pointer to an object or data structure, and DispFitRun represents the type or function of the object pointed to by the pointer. In other words, m_pDispFitRun is a member variable in the discrete fitting running interface class, used to point to the discrete fitting business module in the functional implementation layer, such as the business logic layer.
[0042] The subclass constructor unit is used to initialize the target function in the implementation class of the functional implementation layer based on the interface function in the business interface class. In the example implementation of this disclosure, the subclass constructor unit includes a function constructor subunit and a virtual table rewriting subunit. The function constructor subunit is used to initialize the target function in the functional implementation layer implementation class according to the original virtual function in the virtual table. The target function refers to the virtual function redefined in the functional implementation layer implementation class. The virtual table rewriting subunit is used to rewrite the original virtual function and its corresponding original address in the virtual table according to the target function and its corresponding target address.
[0043] For example, when constructing a subclass, in addition to constructing member variables, the target function in the implementation class of the functional implementation layer is initialized by overriding the original virtual function in the virtual table. At the same time, the target function and target address in the implementation class of the implementation layer are used to replace the original virtual function and original address in the virtual table, thereby ensuring that the virtual function in the implementation class of the functional implementation layer can be executed correctly during polymorphic calls.
[0044] The business implementation unit is used to call the interface function in the business interface class through the interface class object, and call the target function in the implementation class of the function implementation layer according to the interface function, so that the function dependency layer can use the target function to obtain the corresponding turbomachinery design data from the function implementation layer and / or execute the corresponding turbomachinery design algorithm in the function implementation layer.
[0045] In one example implementation, the business implementation unit includes a virtual table determination subunit and a business implementation subunit. The virtual table determination subunit is used to determine the corresponding virtual table based on the interface class object and to call the interface function in the business interface class based on the interface class object. For example, when calling the interface function in the business interface class through the interface class object, the virtual function pointer of the business interface class is first looked up, and the corresponding virtual table is determined through the virtual function pointer.
[0046] The business implementation subunit is used to determine the target address corresponding to the current business type in the virtual table based on the interface function, and then call the target function according to the target address to initiate the first business logic of obtaining the corresponding turbomachinery design data from the functional implementation layer and / or the second business logic of executing the corresponding turbomachinery design algorithm in the functional implementation layer. The current business type includes at least one of obtaining turbomachinery design data and executing a turbomachinery design algorithm. For example, if the current business type is obtaining turbomachinery design data, the target address of the specific implementation is found in the virtual table, and the corresponding target function is called. This ensures that the correct function implementation is called according to the actual object type during the turbomachinery design software runtime, i.e., the target function used to obtain turbomachinery design data is called, thereby achieving polymorphism and improving the flexibility of the turbomachinery design software architecture.
[0047] In the exemplary implementation of this disclosure, the interface functions in the business interface classes defined in the interface layer are implemented in the corresponding layers by deriving subclasses from the base class provided by the business interface. Since the interface methods in the business interface classes are pure virtual methods, the interface layer can be compiled independently without depending on other modules in the software system, thus avoiding compilation errors. Moreover, during the entire software compilation process, the functional modules in the software system do not depend on other functional modules but on the interface layer, thereby preventing reverse dependencies. This solves the problems in software architecture caused by reverse dependencies between functional modules, such as complex relationships between software modules, difficulties in system expansion, and difficulties in software maintenance.
[0048] This disclosure also provides an example implementation of a turbomachinery design software method, which is based on a turbomachinery design software architecture. (Reference) Figure 3 As shown, the method may include the following steps S310 and S320: Step S310: In response to the startup operation for the target functional module in the interactive interface of the turbomachinery design software, determine that the interface layer is the business interface provided by the target functional module.
[0049] The target functional module can be any module among one-dimensional design, detailed design, fluid simulation, structural simulation, discrete fitting, and computer-aided manufacturing of turbomachinery. It can also be other functional modules used for turbomachinery design; this disclosure does not limit this. The activation operation of the target functional module can be any operation on the interactive interface of the turbomachinery design software that can activate the target functional module, such as activating the corresponding turbomachinery design function by clicking the corresponding functional control of the target functional module.
[0050] When a user initiates a target functional module, the application layer can convert the user request into a form that can be recognized internally by the software, thereby determining the business interface provided by the interface layer for the target functional module, so as to realize information interaction between the functional dependency layer and the functional implementation layer related to the target functional module through the business interface.
[0051] Step S320: The functional dependency layer related to the target functional module obtains the corresponding turbomachinery design data from the functional implementation layer through the business interface and / or executes the corresponding turbomachinery design algorithm in the functional implementation layer; wherein, the functional implementation layer and the functional dependency layer include at least one of the application layer, business logic layer, data layer and algorithm layer.
[0052] In turbomachinery design software, the functional dependency layer and the functional implementation layer can be at least one of the application layer, business logic layer, data layer, and algorithm layer, or they can be part of each layer. The functional dependency layer depends on the services provided by the functional implementation layer to perform corresponding processing or operations. The functional implementation layer contains specific business logic, algorithm processing, or data access logic to execute specific functions.
[0053] For example, in response to the operation of turbomachinery design software, an interface class object corresponding to the business interface class defined in the business interface can be created first in the functional dependency layer implementation class, and the target function in the functional implementation layer implementation class can be initialized based on the interface functions in the business interface class. Then, the interface function in the business interface class is called through the interface class object, and the target function in the functional implementation layer implementation class is called according to the interface function, so as to start the first business logic of obtaining the corresponding turbomachinery design data from the functional implementation layer and / or the second business logic of executing the corresponding turbomachinery design algorithm in the functional implementation layer. Finally, the turbomachinery design data obtained from the functional implementation layer and / or the design results after executing the turbomachinery design algorithm in the functional implementation layer can be stored in the data layer and displayed through the application layer.
[0054] The turbomachinery design software method provided by the exemplary embodiments of this disclosure offers several advantages. Firstly, by defining business interfaces, it ensures that communication between functional modules occurs through predetermined interfaces rather than direct access to internal implementations, thus improving software modularity and enabling independent development, testing, and maintenance of each module. Secondly, the interaction between the functional dependency layer and the functional implementation layer via interfaces reduces coupling between them. When the functional implementation layer changes, the functional dependency layer remains unchanged as long as the interface definition remains the same, reducing the risk of modification. Furthermore, introducing an interface layer between the functional dependency layer and the functional implementation layer increases software robustness. Even if the underlying data or algorithms change, as long as the interface remains unchanged, it will not affect the upper-layer application logic. Moreover, once the interface is defined, the functional dependency layer and the functional implementation layer can be developed in parallel, improving development efficiency. Importantly, for complex turbomachinery design tasks, decomposing the task into multiple functional modules and coordinating them through the interface layer effectively simplifies the design and implementation process of each module. Finally, the interface layer acts as a barrier, protecting underlying data and algorithms from direct access. Only authenticated and authorized requests can interact with the functional implementation layer through the interface layer, enhancing software security.
[0055] In one specific embodiment, taking the discrete fitting module in the turbomachinery design software architecture as an example, interaction with the main program interface (i.e., the interactive interface of the turbomachinery design software) is required during the discrete fitting process. First, the application layer initiates the discrete fitting function, and the business logic layer implements the discrete fitting function. Specifically, the discrete fitting business module in the business logic layer relies on the 3D view provided by the discrete fitting main window in the application layer to complete the selection of geometric elements when executing the discrete fitting logic. Similarly, the discrete fitting main window also relies on the discrete fitting business module to perform specific discrete calculations, thereby displaying the discrete fitting results.
[0056] refer to Figure 4 As shown, a schematic diagram illustrating the interaction principle between the application layer and the business logic layer in a turbomachinery design software architecture is presented. Figure 4 In the interface layer, two interface classes are defined: IDispFitRunBase (discrete fitting interface class) and IModelMainWindow (window interface class). Therefore, when implementing the discrete fitting function, the interface class object m_pDispFitRun of IDispFitRunBase and the interface class object m_pDispFitWnd of IModelMainWindow can be used to decouple the application layer and the business logic layer.
[0057] In addition, the IDispFitRunBase class defines several interface functions, including runPickFitEntity, and the IModelMainWindow class defines several interface functions, including firePickFitEntity. Each interface function defines the basic behavior of discrete fitting business processing. Moreover, the DisperseFitRunModel (discrete fitting business module) class inherits from the IDispFitRunBase class, and the TurbDisperseFitWindow (discrete fitting main window) class inherits from the IModelMainWindow class. In other words, both the DisperseFitRunModel and TurbDisperseFitWindow classes provide specific business logic implementations.
[0058] Specifically, when the turbomachinery design software runs, it constructs an interface class object `m_pDispFitRun` at the application layer. This interface class object is a pointer to the `DisperseFitRunModel` class in the business logic layer. Taking the construction of the `DisperseFitRunModel` class as an example, it is necessary to first create the `IDispFitRunBase` class and the virtual table shown in Table 1. It should be noted that the calling functions recorded in the virtual table are consistent with the interface functions in the `IDispFitRunBase` class. Since the interface functions in the `IDispFitRunBase` class are pure virtual functions, the calling functions in the virtual table are default purecalls, indicating that no concrete implementation has been provided yet.
[0059] Table 1
[0060] After the IDispFitRunBase class is constructed, the DisperseFitRunModel class is constructed. At this stage, in addition to constructing member variables, the virtual functions in the DisperseFitRunModel class are initialized by overriding the virtual functions in the IDispFitRunBase class. The addresses of the implemented functions are then replaced with the function addresses and called functions in the virtual table shown in Table 1, resulting in a new virtual table as shown in Table 2. It is important to note that the function addresses in Table 2 are the function addresses in the DisperseFitRunModel class, allowing the corresponding implementation methods in the DisperseFitRunModel class to be called by invoking the virtual methods in the IDispFitRunBase class.
[0061] Table 2
[0062] During the operation of the turbomachinery design software, the discrete fitting main window calls the `runPickFitEntity` function (running the picking of the fitted entity) in the `IDispFitRunBase` class through the interface class object `m_pDispFitRun`. However, it actually calls the `runPickFitEntity` function in the `DisperseFitRunModel` class, thus initiating the picking of the fitted entity process in the discrete fitting business module. In this process, the application layer no longer directly depends on the specific business processing implementation (i.e., the `DisperseFitRunModel` class), but accesses it indirectly through the interface.
[0063] In addition to setting discrete parameters, the process of starting the picking and fitting entity process also requires starting the picking function of geometric elements on the 3D entity. At this time, the discrete fitting business module accesses the firePickFitEntity (trigger picking and fitting entity) function in the IModelMainWindow class through the interface class object m_pDispFitWnd, thereby calling the firePickFitEntity function in the TurbDisperseFitWindow (discrete fitting main window) class, and starting to execute the logic of picking entities at the application layer.
[0064] Throughout the interaction process, access between modules is achieved through the interface layer, avoiding the mutual dependence between the business logic layer and the application layer. This technically isolates the two modules, thereby reducing the coupling between them. This allows each module to be modified or extended independently without affecting other modules, improving the maintainability and flexibility of the software system.
[0065] In another specific embodiment, the interaction between the discrete fitting module and the detailed design module in the turbomachinery design software architecture is taken as an example. Specifically, in the turbomachinery design process, after generating blade cross-sections and other geometric data based on the discrete points of the model, the detailed design module needs to be entered to generate detailed design-related data. At this point, there is a problem of mutual dependence between the discrete fitting module and the detailed design module.
[0066] refer to Figure 5 As shown, a schematic diagram illustrating the interaction principle of different functional modules in the business logic layer of a turbomachinery design software architecture is presented. Figure 5In the interface layer, two interface classes are defined: ITurbFit (discrete fitting data interface class) and IDetailDesign (detailed design interface class). When implementing the detailed design function, the interface class object m_pTurbFit of the ITurbFit class and the interface class object m_pDetailDesign of the IDetailDesign class can be used to decouple the detailed design business module and the discrete fitting data module in the business logic layer.
[0067] Specifically, the discrete fitting data module generates blade row cross-sectional data using the `genSectionRowSpans` method in the `IDetailDesign` class. When generating the blade row cross-sectional data, the detailed design business module retrieves the original cross-sectional data and fitting parameter data from the discrete fitting data module using the `getOriDataFile` method in the `ITurbFit` class, and then uses this data to further generate blade data. For example, when handling detailed design business functions, the `IDetailDesign` class can access the business processes within the `ITurbFit` class by calling the `getOriDataFile` method through the interface object `m_pTurbFit`.
[0068] This example implementation also reduces the coupling between the discrete fitting data module and the detailed design business module through an interface layer, allowing each module to be modified or extended independently, thus improving the robustness and scalability of the turbomachinery design software. Furthermore, related technologies address coupling issues when transitioning from discrete fitting to the detailed design stage by writing to a disk file, for example, by initializing the detailed design module by reading a disk file. This process adds read / write steps and incurs additional time consumption. While this example implementation increases the code size due to the addition of the interface layer, it eliminates disk read / write operations, resulting in improved overall efficiency.
[0069] Finally, it should be noted that the exemplary implementation of this disclosure can resolve coupling relationships between business logic layers related to different functional modules, such as business logic layers and application layers, business logic layers and algorithm layers, business logic layers and data layers, application layers and application layers, algorithm layers and application layers, data layers and application layers, algorithm layers and algorithm layers, data layers and data layers, and data layers and algorithm layers. This disclosure does not limit these relationships. Specifically, by establishing interface modules corresponding to each functional module, defining corresponding business interface classes and adding pure virtual methods in the interface modules, and having classes in the functional implementation modules inherit from the business interface classes, the pure virtual methods of the business interface classes are associated with the specific implementation methods. This allows other modules that depend on the functional implementation modules to achieve the expected calling effect through the interface modules, thereby decoupling different functional modules with dependencies and improving software development efficiency.
[0070] Exemplary embodiments of this disclosure also provide a computer-readable storage medium having a program product stored thereon capable of implementing the methods described above in this specification. In some possible embodiments, various aspects of this disclosure may also be implemented as a program product including program code that, when run on an electronic device, causes the electronic device to perform the steps described in the "Exemplary Methods" section of this specification according to the various exemplary embodiments of this disclosure. This program product may be a portable compact disc read-only memory (CD-ROM) including program code and may run on an electronic device, such as a personal computer. However, the program product of this disclosure is not limited thereto. In this document, the readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.
[0071] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0072] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.
[0073] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.
[0074] Program code for performing the operations of this disclosure can be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C#, and C++, as well as conventional procedural programming languages such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).
[0075] Exemplary embodiments of this disclosure also provide an electronic device capable of implementing the above-described method. Referring below... Figure 6 To describe an electronic device 600 according to such an exemplary embodiment of the present disclosure. Figure 6 The electronic device 600 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.
[0076] like Figure 6 As shown, the electronic device 600 can be represented as a general-purpose computing device. The components of the electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one storage unit 620, a bus 630 connecting different system components (including storage unit 620 and processing unit 610), and a display unit 640.
[0077] Storage unit 620 stores program code that can be executed by processing unit 610, causing processing unit 610 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of this disclosure. For example, processing unit 610 can execute... Figure 3 The methods and steps in the text.
[0078] Storage unit 620 may include readable media in the form of volatile storage units, such as random access memory (RAM) 621 and / or cache memory (Cache) 622, and may further include read-only memory (ROM) 623.
[0079] Storage unit 620 may also include a program / utility 624 having a set (at least one) of program modules 625, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.
[0080] Bus 630 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.
[0081] Electronic device 600 can also communicate with one or more external devices 700 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 600, and / or with any device that enables electronic device 600 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 650. Furthermore, electronic device 600 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 660. As shown, network adapter 660 communicates with other modules of electronic device 600 via bus 630. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0082] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the method according to the exemplary embodiments of this disclosure.
[0083] Furthermore, the above figures are merely illustrative representations of the processes included in the methods according to exemplary embodiments of this disclosure, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.
[0084] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.
[0085] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and embodiments are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.
[0086] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.
Claims
1. A turbomachinery design software architecture, characterized in that: include: The application layer is used to display the interactive interface of the impeller machinery design software and the design views generated during the impeller machinery design process; The business logic layer is used to implement multiple functional modules of the impeller machinery design, wherein the multiple functional modules include at least one-dimensional design, detailed design, fluid simulation, structural simulation, discrete fitting and computer-aided manufacturing of the impeller machinery; A data layer and an algorithm layer, wherein the data layer is used to display and provide the impeller machinery design data for the application layer, and the algorithm layer is used to provide the impeller machinery design algorithm corresponding to each of the functional modules for the business logic layer; An interface layer, used to provide a corresponding interface for each of the functional modules, so that a function-dependent layer related to each of the functional modules can obtain corresponding impeller machinery design data from a function implementation layer through the interface and / or execute a corresponding impeller machinery design algorithm at the function implementation layer; The function implementation layer and the function dependency layer include at least one layer among the application layer, the business logic layer, the data layer and the algorithm layer.
2. The impeller machinery design software architecture according to claim 1, characterized in that: The interface layer includes interface modules corresponding to the functional modules, and each interface module includes: An interface establishment unit, used to define a corresponding business interface class for each of the functional modules; A pointer creation unit, configured to create, in response to the running of the impeller machinery design software, an interface class object corresponding to each of the business interface classes in the function dependency layer implementation class; A subclass construction unit, used for initializing a target function in a function implementation layer implementation class based on an interface function in the business interface class; A business implementation unit is used to call the interface function in the business interface class through the interface class object, and call the target function in the function implementation layer implementation class according to the interface function, so that the function dependency layer uses the target function to obtain the corresponding impeller machinery design data from the function implementation layer and / or execute the corresponding impeller machinery design algorithm in the function implementation layer.
3. The impeller machinery design software architecture according to claim 2, characterized in that: Each of the interface modules further includes: The virtual table creation unit is used to create a virtual table according to the interface function in the business interface class, and the virtual table at least includes the original virtual function and the corresponding original address used to implement the corresponding functional module.
4. The impeller machinery design software architecture according to claim 3, characterized in that: The subclass construction units include: A function construction subunit, used for initializing a target function in the implementation class of the function implementation layer according to the original virtual function in the virtual table; The virtual table rewriting subunit is used to rewrite the original virtual function and the corresponding original address in the virtual table according to the target function and the corresponding target address.
5. The impeller machinery design software architecture according to claim 4, characterized in that: The business implementation unit includes: A virtual table determination subunit, used to determine the corresponding virtual table according to the interface class object, and call the interface function in the business interface class according to the interface class object; The business implementation subunit is used to determine the target address corresponding to the current business type in the virtual table according to the interface function, and call the target function according to the target address to start the first business logic of obtaining the corresponding impeller machinery design data from the functional implementation layer and / or the second business logic of executing the corresponding impeller machinery design algorithm in the functional implementation layer.
6. A turbomachinery design method, characterized in that: Based on the impeller machinery design software architecture described in any one of claims 1 to 5, the method comprises: In response to a start-up operation for a target functional module in an interactive interface of the turbomachinery design software, determining a business interface provided by the interface layer for the target functional module; The function dependency layer related to the target function module obtains the corresponding impeller machinery design data from the function implementation layer through the business interface and / or executes the corresponding impeller machinery design algorithm in the function implementation layer; The function realization layer and the function dependency layer include at least one layer of the application layer, the business logic layer, the data layer and the algorithm layer.
7. The impeller machine design method according to claim 6, characterized in that: The function dependency layer related to the target function module obtains the corresponding impeller machinery design data from the function implementation layer through the business interface and / or executes the corresponding impeller machinery design algorithm at the function implementation layer, including: In response to the running of the turbomachinery design software, creating an interface class object corresponding to the business interface class defined in the business interface in the function dependency layer implementation class; Initialize the target function in the function implementation layer implementation class based on the interface function in the business interface class; The interface function in the business interface class is called through the interface class object, and the target function in the function implementation layer implementation class is called according to the interface function, so as to start the first business logic of obtaining the corresponding impeller machinery design data from the function implementation layer and / or the second business logic of executing the corresponding impeller machinery design algorithm in the function implementation layer.
8. The impeller machine design method according to claim 6, characterized in that: The method further comprises: The impeller machinery design data obtained from the function implementation layer and / or the design result after the impeller machinery design algorithm is executed in the function implementation layer are stored in the data layer and displayed through the application layer.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processing unit, the method according to any one of claims 6 to 8 is implemented.
10. An electronic device, characterized in that: include: Processing unit; as well as A storage unit, used to store executable instructions of the processing unit; Wherein, the processing unit is configured to perform the method of any one of claims 6-8 by executing the executable instructions.
Citation Information
Patent Citations
Method and device for developing interface layers and realizing data interaction of interface layers
CN104252339A
Data processing system, method and device
CN107885653A
Software application architecture and configuration unit thereof
CN110413264A
Service framework construction method and system based on plug-in engine
CN112822115A
Component type control system simulation platform and method based on soft bus
CN114625024A
Cited By
Operation method and device of functional module, equipment and storage medium
CN120929057A
