Schematic diagram standard module management method and electronic device

Abstract

The embodiment of the invention provides a schematic diagram standard module management method and an electronic device. The method comprises the following steps: configuring a version number for an uploaded schematic diagram standard module, and analyzing version attribute data and module design data of the schematic diagram standard module under a current version; under the condition that the schematic diagram standard module is determined to be not uploaded for the first time according to the version number, comparing version attribute data and design data of a current version and a previous version of the schematic diagram standard module to obtain a comparison result; and notifying a calling party of the schematic diagram standard module to perform version upgrading according to the comparison result. Through the embodiment of the invention, the problems that a schematic diagram standard module management method mostly depends on manual management, versions are disordered, and traceability is lacked in the prior art are solved, and the effect of improving the cooperation efficiency and standardization degree of IC design is achieved.

Description

Technical Field

[0001] The embodiments of the present invention relate to the fields of circuit design technology and computer technology, and in particular to a schematic diagram standard module management method and an electronic device. Background Art

[0002] In the integrated circuit (IC) design process, standard modules are circuit units developed, verified, and widely reused by experienced designers, such as operational amplifiers, phase-locked loops, and low-dropout linear regulators. Effective management of these schematic standard modules is crucial for improving design efficiency, ensuring design quality, and reducing recurring development costs. However, existing schematic standard module management methods have numerous issues that hinder their efficient reuse and online management. Summary of the Invention

[0003] The embodiments of the present invention provide a schematic diagram standard module management method and an electronic device to at least solve the problems in the related art that the schematic diagram standard module management method mostly relies on manual management, has version confusion, lacks traceability, and so on.

[0004] According to one embodiment of the present invention, a schematic standard module management method is provided, comprising: configuring a version number for an uploaded schematic standard module, and parsing version attribute data and module design data of the schematic standard module under the current version; when it is determined according to the version number that the schematic standard module is not uploaded for the first time, comparing the version attribute data and design data of the current version and the previous version of the schematic standard module to obtain a comparison result; and notifying the caller of the schematic standard module to perform a version upgrade based on the comparison result.

[0005] According to yet another embodiment of the present invention, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when run.

[0006] According to another embodiment of the present invention, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any one of the above method embodiments.

[0007] According to yet another embodiment of the present invention, a computer program product is provided, including a computer program, which implements the steps of any of the above method embodiments when executed by a processor.

[0008] Through the above-described embodiments of the present invention, version numbers are automatically generated for uploaded schematic standard modules, avoiding version confusion. By storing version attribute data and module design data for different versions of schematic standard modules, changes to schematic standard modules can be backtracked. This solves the problems of related-art schematic standard module management methods, which often rely on manual management, suffer from version confusion, and lack of traceability, thereby improving collaborative efficiency and standardization in IC design. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 It is a hardware structure block diagram of a computer terminal on which the method embodiment of the present invention is executed;

[0010] Figure 2 is a schematic diagram of a schematic diagram standard module management system architecture according to an embodiment of the present invention;

[0011] Figure 3 is a flowchart of a schematic diagram standard module management method according to an embodiment of the present invention;

[0012] Figure 4 is a schematic diagram of a standard model uploading and storage process according to an embodiment of the present invention;

[0013] Figure 5 is a schematic diagram of a standard model calling process according to an embodiment of the present invention;

[0014] Figure 6 is a schematic diagram of a standard model change tracking process according to an embodiment of the present invention;

[0015] Figure 7 is a schematic diagram of a process for generating an impact analysis report according to an embodiment of the present invention;

[0016] Figure 8 FIG. 4 is a schematic diagram of a standard model calling process according to another embodiment of the present invention. DETAILED DESCRIPTION

[0017] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings and in combination with embodiments.

[0018] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0019] Circuit schematics are the foundation of chip design. Design engineers typically use Electronic Computer-Aided Design (ECAD) software to create and edit schematics to define circuit functionality, device connections, and design intent. In the IC design process, standard schematic modules (abbreviated as standard modules) are circuit units developed, verified, and widely reused by experienced designers.

[0020] Currently, the existing schematic standard module management methods mainly include the following:

[0021] Storing schematic files on a local computer or shared server and manually maintaining different versions of modules. This approach relies on manual management and can easily lead to problems such as file loss, version confusion, and untraceable changes.

[0022] Schematic file management uses software like Git and SVN, but these tools primarily target text files and are not suitable for the complex data formats found in ECAD environments. Furthermore, tools like Git cannot directly parse schematic structures, making it difficult to track fine-grained design changes.

[0023] It can be seen that the existing schematic standard module management methods have the following problems: the traditional method relies on manual maintenance, which makes it difficult to ensure the latest status of the module and the correctness of the version, and there are problems with version management confusion and lack of traceability; the reuse efficiency is low, and there is no unified online platform to store and manage standard modules, resulting in repeated development of similar modules in different projects, increasing design costs; there is a lack of permission control, that is, local storage or shared server mode cannot achieve refined permission management, and there are data security risks; in addition, since the management of standard modules usually relies on local storage or manual maintenance, there is a lack of a systematic change tracking mechanism, which will also make it difficult to track changes to standard modules; and when standard modules are updated, it is difficult for designers to accurately obtain key information such as change content, modification time, and modifier, which will lead to version confusion and increase design risks.

[0024] In response to the above problems, an embodiment of the present invention proposes a schematic standard module management method, which is an online management method that can greatly improve the management efficiency of schematic standard modules, reduce errors caused by human operations, ensure data consistency and security, and promote the optimization of enterprise-level collaborative design processes and digital management in the hardware field.

[0025] The method embodiments provided in the embodiments of the present application can be executed in a computer terminal or similar computing device. Taking running on a computer terminal as an example, Figure 1 This is a hardware block diagram of a computer terminal running the method embodiment of the present invention. Figure 1 As shown, the computer terminal may include one or more ( Figure 1 Only one is shown) a processor 102 (the processor 102 may include but is not limited to a microprocessor MCU or a programmable logic device FPGA and other processing devices) and a memory 104 for storing data. The computer terminal may also include a transmission device 106 and an input / output device 108 for communication functions. It will be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above-mentioned computer terminal. For example, the computer terminal may also include Figure 1 More or fewer components than shown, or with Figure 1 Different configurations shown.

[0026] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the schematic standard module method in the embodiment of the present invention. The processor 102 executes the computer program stored in the memory 104 to perform various functional applications and data processing, that is, to implement the above-mentioned method. The memory 104 may include a high-speed random access memory and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely located relative to the processor 102, and these remote memories may be connected to the computer terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0027] The transmission device 106 is used to receive or transmit data via a network. A specific example of the aforementioned network may include a wireless network provided by a computer terminal's communications provider. In one embodiment, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0028] Figure 2 This is a schematic diagram of the standard module management system architecture according to an embodiment of the present invention. The embodiment of the present application can be run on Figure 2 The schematic diagram standard module management system shown in Figure 2As shown, the system includes a computer terminal, a standard model database, and a file server. The computer terminal interacts bidirectionally with the standard model database and the file server, respectively. This system can address current electronic design processes, including the difficulty in tracking standard model changes, chaotic version management, difficulty in assessing the impact of changes, conflicts in multi-person collaboration, and the lack of automatic notification mechanisms. Through database management, version control, change comparison, automatic notification, and collaborative editing technologies, it achieves efficient management and accurate tracking of standard modules.

[0029] The standard model database and file server are used to store standard model files, standard model parsing metadata, standard model attributes, version history and change records, and support multi-user online access.

[0030] Specifically, the following modules can be set in the computer terminal:

[0031] The version management module is used to provide standard model version control, history backtracking, version comparison and other functions.

[0032] The change comparison module is used to provide visual standard model change comparison based on the difference analysis algorithm and intuitively display the modified content.

[0033] The standard model reuse module is used to query the online standard model database, select the appropriate standard model version, complete the automatic download and call of the standard model file, and record the call information.

[0034] The change tracking module is used to automatically record the change information of the standard model, including modification time, modifier, change content, etc.

[0035] The impact analysis module is used to identify the impact scope of standard model changes and analyze the affected circuit modules, PCB designs or other related components.

[0036] The automatic notification module is used to automatically notify all designers who call the standard model when the standard model is modified, ensuring that the changes can be updated synchronously.

[0037] The permission management module is used to set the operation permissions of different roles (such as designers, auditors, and administrators) to improve data security.

[0038] The embodiment of the present invention can also realize the integration of online storage and schematic standard module management system. Specifically, cloud database and file server management are adopted to support remote access and data sharing; designers can log in to the system at different locations to realize cross-team collaboration.

[0039] The present invention can also be integrated with existing ECAD tools. For example, by providing an API interface, it can be integrated with mainstream ECAD software (such as Cadence, Altium Designer, and Mentor Graphics). This ensures the consistency and traceability of standard model data within Product Lifecycle Management (PLM) systems, ECAD tools, and enterprise databases.

[0040] In this embodiment, a schematic diagram standard module management method running on the above-mentioned computer terminal or schematic diagram standard module management system is provided. Figure 3 FIG. 1 is a flow chart of a schematic diagram standard module management method according to an embodiment of the present invention. Figure 3 As shown, the process includes the following steps:

[0041] Step S302: configuring a version number for the uploaded schematic standard module, and parsing the version attribute data and module design data of the schematic standard module under the current version;

[0042] Step S304, when it is determined based on the version number that the schematic standard module is not uploaded for the first time, comparing the version attribute data and module design data of the current version and the previous version of the schematic standard module to obtain a comparison result;

[0043] Step S306: Notify the caller of the schematic standard module to perform version upgrade according to the comparison result.

[0044] In one embodiment, the schematic standard module management system is provided with a version record table, a version attribute table, a version parsing data table, a change storage table, and a call relationship table for storing various core data.

[0045] The version record table is used to record at least one of the following: a standard model identifier (ID), a version number, a modification time, information about the modifier, a file server storage path, an index ID for the version resolution data table, an index ID for the version attribute table, and an index ID for the change storage table. The standard model ID is unique.

[0046] The version attribute table is used to record the attributes of each standard model version, including the standard model ID, version number, technical field, selection attributes, conversion status, applicable scenarios, differences from the previous version, compatibility with historical versions, major category, minor category, and sub-minor category.

[0047] Version analysis data table: records the design analysis data of each standard model version, including standard model ID, version number, standard model name, device instance, device attributes, device pins, pin corresponding network information, network information in the module, module pins, network corresponding pin information, network connection relationship, module instance, module attributes, bus information, and nested sub-module types.

[0048] Among them, selection attributes refer to a series of key information such as performance indicators, specification parameters, and applicable scenarios that are considered when selecting and using specific electronic components or modules. For example, the selection attributes are [available], [obsolete], etc.

[0049] The change storage table is used to record the differences between the current uploaded version and the previous version. The differences include differences in version attributes and version resolution data. Version attributes and version resolution data are the data in the above version attribute table and version resolution data table.

[0050] The call relationship table (such as the Neo4j database) is used to store the reference relationship between the standard model and the schematic diagram and PCB, including the name of the called schematic diagram, the caller, the calling time, the ID of the called standard model, the name of the called standard model, and the version number of the called standard model.

[0051] In step S302 of this embodiment, the version number of the uploaded schematic standard module is configured, including: when the schematic standard module is uploaded for the first time, the first version number and a unique module identifier are configured for the schematic standard module; when the schematic standard module is not uploaded for the first time, a new version number is configured for the current schematic standard module based on the module identifier and the previous version number of the schematic standard module.

[0052] In an exemplary embodiment, each time a standard module version is changed, the standard module management tool in the schematic standard module management system compares the version attribute data and module design data of the current version and the previous version of the schematic standard module, wherein the comparison includes the following:

[0053] (1) Version attribute data comparison, that is, comparing all attribute fields in the above version attribute table.

[0054] (2) Module design data comparison, that is, comparing all fields in the above version parsing data table.

[0055] In step S306 of this embodiment, the caller of the schematic standard module is notified to perform a version upgrade based on the comparison result, including: determining the version change level of the schematic standard module based on the comparison result, and determining the caller that has called the schematic standard module based on the stored calling relationship table; and notifying the caller to perform a version upgrade based on the version change level.

[0056] In one embodiment, determining the version change level of the schematic standard module based on the comparison results includes: determining the version change level to be the first level if key version attribute data in the version attribute data has changed and / or key module design data in the module design data has changed; and determining the version change level to be the second level if the key version attribute data and the key module design data have not changed; wherein the first level is higher than the second level. The key version attribute data includes at least one of the following: selection attributes and compatibility with historical versions; and the key module design data includes at least one of the following: module pins, device type, and nested submodule type.

[0057] In one embodiment, before determining the version change level of the schematic standard module based on the comparison results, the method also includes: classifying the version change levels according to the impact of the version change differences, wherein the version change level classification rules are formulated by the business party, and the attributes to be extracted and the attribute fields to be compared can also be adjusted by the business party.

[0058] In an exemplary embodiment, the version change level classification rules may be set as follows:

[0059] Set the "selection attributes" and "compatibility with historical versions" in the above version attribute table as key version attributes, and set other version attribute data in the above version attribute table as non-key version attributes.

[0060] Set the "module pins", "device types" and "nested sub-module types" in the above version parsing data table as key module designs, and set other module design data in the above version parsing data table as non-key module designs.

[0061] If the change is a critical version attribute data change and a critical module design data change, the version change level is high, that is, the warning level is high, which means that the user needs to be prompted to force an update; if the change is a non-critical version attribute data change and a non-critical module design data change, the version change level is low, that is, the warning level is low, which means that the user needs to be prompted to recommend an update but not force an update.

[0062] In an exemplary embodiment, the key version attribute data changes include: the attribute "selection attribute" changes from [available] to [obsolete], and the attribute "compatible with historical version" changes to [no].

[0063] In an exemplary embodiment, key module design data changes include: module pinout changes, device type changes with obsolete devices existing in the device before the change, and nested sub-module types changes with obsolete modules existing in the sub-module before the change.

[0064] In one embodiment, after comparing the version attribute data and design data of the current version and the previous version of the schematic standard module, it includes: comparing and analyzing the change points of the current version and the previous version of the schematic standard module, wherein the change points are specific positions or elements where the structure, attributes or related data of the current version and the previous version of the schematic standard module have changed; marking the change points and displaying them in the display interface.

[0065] In an exemplary embodiment, the change points between the current version and the previous version of the schematic standard module are compared and analyzed, including: using difference analysis algorithms such as text comparison and graphic comparison to analyze the change points between the current version and the previous version of the schematic standard module, such as newly added, deleted, and modified components, networks, and connection relationships.

[0066] In one exemplary embodiment, the change points are marked and displayed in the display interface, including color highlighting, layer annotation, and other methods to visually display the changes. This graphical interface displays information such as the affected circuit modules, signal paths, and associated components, improving readability and helping designers quickly locate affected areas, reducing manual inspection workload.

[0067] In one embodiment, before notifying the caller of the schematic standard module to perform a version upgrade according to the comparison result, the method further includes: generating an impact analysis report, wherein the impact analysis report includes an impact scope and an alarm level.

[0068] Among them, the impact scope is retrieved based on the call relationship table. By querying the database through the ID of the standard model with the version change, all schematics, PCB information and caller information that call the standard model can be obtained; the alarm level is determined according to the above alarm level classification rules.

[0069] In one embodiment, the caller of the schematic standard module is notified to perform a version upgrade based on the comparison result, including: using a database association query to find all callers / designers who are using the standard model; when the standard model is updated, using a dependency analysis algorithm to determine the design modules that need to be updated synchronously based on the comparison results obtained; and pushing a change notification to the caller / designer to remind relevant designers to check the changes.

[0070] In an exemplary embodiment, the methods of pushing change notifications include, but are not limited to, email notifications, system message pushes, task reminders, and other methods to improve notification efficiency.

[0071] In one embodiment, the caller / designer can choose to automatically update the standard template or manually confirm the update to ensure the controllability of the design change.

[0072] In one embodiment, the method further includes: storing version attribute data, module design attribute data, and version comparison data of each version of the schematic standard module; and performing data backtracking and data recovery based on the version attribute data, module design attribute data, and version comparison data of each version of the schematic standard module.

[0073] In one embodiment, the method further includes: storing the version attribute data and module design data of the schematic standard module in a cloud database, so that the caller can remotely access and call the schematic standard module.

[0074] Through the above steps, version numbers are automatically generated for uploaded schematic standard modules, avoiding version confusion. By storing the version attribute data and module design data of different versions of schematic standard modules, changes to schematic standard modules can be traced back. This solves the problems of schematic standard module management methods in related technologies that often rely on manual management, resulting in version confusion and lack of traceability, thereby improving the collaborative efficiency and standardization of IC design.

[0075] To facilitate understanding of the technical solutions provided by the present invention, embodiments of the present invention will be described in detail below with reference to specific scenarios.

[0076] Example 1:

[0077] Figure 4 Schematic diagram of the standard model upload and storage process according to an embodiment of the present invention. The standard model upload and storage process is based on the example of hardware engineer A editing the schematic module of MODEL1 in ECAD software, submitting it for review and uploading it to the standard model management system. Figure 4 As shown, the process may include the following steps:

[0078] In step S401, hardware engineer A designs module MODEL1 in ECAD software, submits it for review and uploads it after completing the design, and edits the metadata of the version, such as the product to which it belongs, the department to which it belongs, etc.

[0079] In step S402, the standard model management tool generates a unique ID for the module (for example: MID20250301000001) and automatically generates a version number (for example: A.1); the standard model management tool also uploads the schematic file to the file server, and parses the module design data of the module, converting it into JSON standardized structure data for storage.

[0080] In one embodiment, the module design data is converted into JSON standardized structure data for storage, including: extracting key information data (such as the number of devices and the number of pages) from the obtained structured data, and storing the key information data in a database.

[0081] In step S403, hardware engineer A submits an application to add MODEL1 into the standard model library.

[0082] In step S404, the module reviewer approves the application for MODEL1 to enter the standard model library.

[0083] After approval, the first version A.1 of MODEL1 is officially generated, and the module's metadata and key schematic information can be viewed in the standard model management tool.

[0084] If the approval is rejected, the first version A.1 of MODEL1 will fail to be put into storage.

[0085] Example 2:

[0086] Figure 5 Schematic diagram of a standard model calling process according to an embodiment of the present invention. The standard model calling process takes hardware engineer B calling MODEL1 designed by hardware engineer A as an example. Figure 5 As shown, the process may include the following steps:

[0087] In step S501, hardware engineer B submits an application for permission to use MODEL1 in the standard model management tool. After the administrator approves the application, hardware engineer B has permission to use MODEL1.

[0088] In step S502, when hardware engineer B designs schematic diagram PROJECT1 in ECAD, he can open the standard model management tool and select version A.1 of MODEL1 in the module library to add it. In this way, PROJECT1 successfully calls version A.1 of module MODEL1.

[0089] Example 3:

[0090] Figure 6Schematic diagram of the standard model change tracking process according to an embodiment of the present invention, the standard model change tracking process is based on the automatic identification of the schematic diagram PROJECT1 after MODEL1 is updated to version A.2 as an example, Figure 6 As shown, the process may include the following steps:

[0091] In step S601 , hardware engineer A updates the standard model MODEL1 to update the version of MODEL1 and uploads the updated MODEL1 to the standard model management tool.

[0092] In one embodiment, updating the standard model MODEL1 includes: replacing a disabled component in MODEL1 with another available component, so that the version of MODEL1 is upgraded from A.1 to A.2.

[0093] In step S602 , the standard model management tool performs a version comparison between the newly uploaded MODEL1 and the previously uploaded MODEL1 and determines that this change is a critical design change, that is, the warning level is high.

[0094] In this embodiment, after the standard model management tool compares the versions of the newly uploaded MODEL1 and the previously uploaded MODEL1, if there is no difference between the newly uploaded MODEL1 and the previously uploaded MODEL1, a new version is not created; if there is a difference, a new version is created and the corresponding new version number is set.

[0095] For example: when the standard model management tool finds that the previous MODEL1 version is A.1, it sets the version number of the newly uploaded MODEL1 to A.2.

[0096] This change is determined to be a critical design change, including: comparing MODEL1 of version A.2 with MODEL1 of version A.1, and determining that this change is a critical design change through the version change level classification rules in the above embodiment, and the corresponding warning level is high.

[0097] In this embodiment, the standard model management tool is further used to store the new version / A.2 version of MODEL1 in the file server, and parse the metadata of the new version / A.2 version of MODEL1, and store the parsed metadata in the database.

[0098] In this embodiment, the standard model management tool is also used to record the change differences between the two versions of MODEL1.

[0099] In step S603, the standard model management tool generates an impact analysis report and searches the database to find that the standard model MODEL1 and version A.1 are called by schematics A, B, and C. The standard model management tool then notifies the relevant callers of a mandatory upgrade via email and message.

[0100] Figure 7 FIG. 1 is a schematic diagram of a process for generating an impact analysis report according to an embodiment of the present invention. Figure 7 As shown, the process includes the following steps:

[0101] Step S701: Search the call relationship table to obtain all schematics, PCB information, and caller information that call the standard model, and determine the impact scope of the current version change of the standard model based on all schematics, PCB information, and caller information that call the standard model;

[0102] Step S702: determining the warning level of the impact scope of the current version change of the standard model according to the version change level classification rule in the above embodiment;

[0103] Specifically, if the key version attribute data is changed and / or the key module design data is changed, the version change level is high and the corresponding alarm level is high;

[0104] For key version attribute data changes, for example: the data of "Shaping Attributes" in the key version attributes changes from [Available] to [Abandoned]; the "Compatible with Historical Versions" in the key version attributes is set to [No].

[0105] For key module design data changes, for example: module key changes; device type changes and there are obsolete devices before the change; nested sub-module type changes and there are obsolete modules in the sub-module before the change.

[0106] In the case of non-critical version attribute data changes and key module design data changes, the version change level is low and the corresponding alarm level is low.

[0107] Step S703: Generate an impact analysis report based on the impact scope and warning level of the current version change of the standard model.

[0108] The impact analysis report can then be sent to the caller via email and message.

[0109] In step S604, the caller may update the version of MODEL1 to A.2 through the standard model management tool.

[0110] In step S605 , the standard model management tool automatically downloads version A.2 of MODEL1 and replaces it in the ECAD tool.

[0111] Example 4:

[0112] Figure 8 Schematic diagram of the standard model calling process according to another embodiment of the present invention, the standard model change process is based on the hardware engineer B updating the MODEL1 version to A.3 as an example, Figure 8As shown, the process includes the following steps:

[0113] In step S801, the schematic designed by hardware engineer B calls version A.2 of MODEL1, and engineer B attempts to update version A.2 of MODEL1 to version A.3.

[0114] In step S802 , the standard model management tool identifies that the difference between version A.2 and version A.3 is a change in external pins, and provides a graphical interface to display the difference between A.2 and A.3.

[0115] In this embodiment, the standard model management tool recognizes that the difference between version A.2 and version A.3 is a change in external pins. It may also prompt the user that if the version A.3 is replaced, the connection relationship of MODEL1 needs to be adjusted, and a graphical interface is provided to display the difference between version A.2 and version A.3.

[0116] In step S803, hardware engineer B decides whether to replace the model independently. If he chooses to replace the model, the standard model management tool will automatically download the standard model file of version A.3 and replace it in the ECAD software. Hardware engineer B manually adjusts the pin connection of MODEL1.

[0117] Embodiment 5:

[0118] Taking the example of hardware engineer A maintaining the information of MODEL1, hardware engineer A can maintain the standard model. The specific maintenance content at least includes: repeating embodiment one in the standard model management tool to update the version of MODEL1; checking the calling information of the module MODEL1 designed by himself in the standard model management tool, including which schematics call it, the number of calls, the caller, the calling version and other information; editing the attribute information of each version of MODEL1 in the standard model management tool.

[0119] In an embodiment of the present invention, a permission management method is also provided, that is, when a user attempts to access the schematic standard module management system, the schematic standard module management system will check the user's permissions. If the user has permission to access, the user is allowed to download and call the schematic standard module managed on the schematic standard module management system. Otherwise, if the user does not have permission to access, the user's access will be denied.

[0120] The embodiments of the present invention can effectively improve design efficiency, reduce costs, enhance data security and design quality, and enhance corporate competitiveness through online management, intelligent version control, change tracking and other technologies. They are suitable for multiple fields such as IC design companies, ECAD software providers, and electronic hardware R&D teams.

[0121] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0122] An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when running.

[0123] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0124] An embodiment of the present invention further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0125] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0126] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail here.

[0127] Obviously, those skilled in the art will appreciate that the various modules or steps of the present invention described above can be implemented using a general-purpose computing device, can be centralized on a single computing device, or can be distributed across a network of multiple computing devices. They can be implemented using program code executable by the computing device, and thus, can be stored in a storage device and executed by the computing device. In some cases, the steps shown or described herein can be performed in a different order than that shown, or can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0128] The foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the principles of the present invention are intended to be within the scope of protection of the present invention.

Claims

1. A schematic diagram standard module management method, characterized in that: include: Configuring a version number for the uploaded schematic standard module and parsing the version attribute data and module design data of the schematic standard module under the current version; When it is determined according to the version number that the schematic standard module is not uploaded for the first time, comparing the version attribute data and module design data of the current version and the previous version of the schematic standard module to obtain a comparison result; The caller of the schematic standard module is notified to perform a version upgrade according to the comparison result.

2. The method according to claim 1, characterized in that The version number of the uploaded schematic standard module configuration includes: When the schematic diagram standard module is uploaded for the first time, configuring a first version number and a unique module identifier for the schematic diagram standard module; In the case that the schematic diagram standard module is not uploaded for the first time, a new version number is configured for the current schematic diagram standard module according to the module identifier and the previous version number of the schematic diagram standard module.

3. The method according to claim 1, characterized in that The notifying the caller of the schematic standard module to perform version upgrade according to the comparison result includes: Determining a version change level of the schematic standard module according to the comparison result, and determining a caller that has called the schematic standard module according to a stored call relationship table; According to the version change level, the caller is notified to perform a version upgrade.

4. The method according to claim 3, characterized in that Determining the version change level of the schematic standard module according to the comparison result includes: When key version attribute data in the version attribute data is changed, and / or key module design data in the module design data is changed, the version change level is determined to be the first level; In a case where the key version attribute data and the key module design data have not changed, the version change level is determined to be the second level; wherein the first level is higher than the second level.

5. The method according to claim 4, characterized in that in, The key version attribute data includes at least one of the following: selection attributes, compatibility with historical versions; the key module design data includes at least one of the following: module pins, device type, and nested sub-module type.

6. The method according to claim 1, characterized in that After comparing the version attribute data and design data of the current version and the previous version of the schematic standard module, including: Comparing and analyzing the change points between the current version and the previous version of the schematic standard module, wherein the change points are specific locations or elements where the structure, attributes, or related data of the current version and the previous version of the schematic standard module have changed; The change points are marked and displayed on the display interface.

7. The method according to claim 1, characterized in that The method further comprises: Store the version attribute data, module design attribute data and version comparison data of each version of the schematic standard module; Data backtracking and data recovery are performed based on the version attribute data, module design attribute data and version comparison data of each version of the schematic standard module.

8. The method according to claim 1, characterized in that The method further comprises: The version attribute data and module design data of the schematic standard module are stored in a cloud database so that a caller can remotely access and call the schematic standard module.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the steps of the method described in any one of claims 1 to 8 are implemented.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 8 are implemented.

11. A computer program product, characterized in that The method comprises a computer program, which implements the steps of the method according to any one of claims 1 to 8 when the computer program is executed by a processor.

Images