CN113971024A - Interface management method, device, electronic equipment and readable storage medium - Google Patents
Interface management method, device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN113971024A CN113971024A CN202111593173.5A CN202111593173A CN113971024A CN 113971024 A CN113971024 A CN 113971024A CN 202111593173 A CN202111593173 A CN 202111593173A CN 113971024 A CN113971024 A CN 113971024A
- Authority
- CN
- China
- Prior art keywords
- interface
- interface document
- document
- instruction
- development software
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/37—Compiler construction; Parser generation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides an interface management method, an interface management device, electronic equipment and a readable storage medium, wherein the method comprises the following steps: after receiving a plurality of modification requirements of a back-end developer on the same interface document, copying and storing a plurality of interface documents, wherein the number of the copied and stored interface documents is equal to that of the modification requirements; distributing the interface documents to a plurality of modification requirements in a one-to-one correspondence manner; after receiving the modification completion notification, combining the modified interface documents to form an interface document set; after a first instruction sent by a developer is received, determining a main interface document according to the first instruction, wherein the first instruction is used for indicating a document in an interface document set as the main interface document; and deploying the main interface document into the development software so that the development software can call the main interface document when running. The invention solves the problem that a plurality of interface definitions are mutually covered in the same interface document, improves the development efficiency and reduces the development cost.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to an interface management method, an interface management device, electronic equipment and a readable storage medium.
Background
Currently, the development of software basically adopts a mode of separating a front end from a back end, and the basic flow is roughly as follows: the back-end developer defines an interface to provide data services, and the developer calls the interface through a development page to acquire data and render the page. Thus, the interface document is very important.
The existing interface management systems can be divided into at least two categories: the first type is a pure document type, the system only has the function of editing and checking and is only used for front-end and back-end interface definition communication, the function is single, and the use is inconvenient; the second type is a system type, which has various management to interfaces, supports import and export of some interfaces and has authority control. The existing interface management systems all have the problem that when a back-end developer modifies the same interface document according to a plurality of different requirements, a plurality of interface definitions based on different requirements are mutually covered in the same interface document (namely, one or more requirements are defined in the interface document), so that the development efficiency of the existing software is low and the development cost is high.
Disclosure of Invention
The embodiment of the invention provides an interface management method, which aims to solve the problem that in the prior art, when a back-end developer modifies the same interface document according to different requirements, a plurality of interface definitions based on different requirements are mutually covered in the same interface document.
In order to solve the technical problem, the invention is realized as follows:
in a first aspect, an embodiment of the present invention provides an interface management method, including:
after receiving a plurality of modification requirements of a back-end developer on the same interface document, copying and storing a plurality of interface documents, wherein the number of the copied and stored interface documents is equal to that of the modification requirements;
distributing the interface documents to the modification requirements in a one-to-one correspondence manner;
after receiving a modification completion notification, combining the modified interface documents to form an interface document set;
after a first instruction sent by a developer is received, determining a main interface document according to the first instruction, wherein the first instruction is used for indicating a document in the interface document set as the main interface document;
deploying the main interface document into development software so that the development software can call the main interface document when running.
Optionally, deploying the main interface document into development software, and then further comprising:
after receiving a second instruction sent by a developer, determining a secondary interface document according to the second instruction, wherein the second instruction is used for indicating the secondary interface document in the interface document set;
and based on the modification of the development software by the developer according to the secondary interface document, the modified development software can realize the function of the secondary interface document.
Optionally, deploying the main interface document into development software includes:
and deploying the main interface document in the development software in a CI mode.
Optionally, deploying the main interface document in the development software in a CI manner includes:
analyzing the main interface document, and generating a data packet according to an analysis result, wherein the format of the data packet is a data exchange format which can be read by the development software;
and after receiving an execution instruction sent by a developer, operating the development software to read the data packet and returning a reading result to a development page associated with the developer.
Optionally, the development software is secondary development software of at least one of the following software: apifox, Eolink, Yapi and Swagger.
Optionally, the data exchange format is a json format.
In a second aspect, an embodiment of the present invention provides an interface management apparatus, including:
the receiving module is used for copying and storing a plurality of interface documents after receiving a plurality of modification requirements of a back-end developer on the same interface document, wherein the number of the copied and stored interface documents is equal to that of the modification requirements;
the distribution module is used for distributing the interface documents to the modification requirements in a one-to-one correspondence manner;
the modification module is used for combining the interface documents which are modified to form an interface document set after receiving a modification completion notification;
the system comprises a combination module, a first interface document collection module and a second interface document collection module, wherein the combination module is used for determining a main interface document according to a first instruction after receiving the first instruction sent by a developer, and the first instruction is used for indicating a document in the interface document collection as the main interface document;
the deployment module is used for deploying the main interface document into development software so that the development software can call the main interface document when running.
Optionally, the combining module is configured to, after receiving a second instruction issued by the developer, determine a secondary interface document according to the second instruction, where the second instruction is used to indicate the secondary interface document in the interface document set;
the deployment module is used for modifying the development software according to the secondary interface document, and the modified development software can realize the function of the secondary interface document.
In a third aspect, an embodiment of the present invention provides an electronic device, which includes a processor, a memory, and a program or an instruction stored on the memory and executable on the processor, where the program or the instruction, when executed by the processor, implements the steps in the interface management method according to any one of the first aspect.
In a fourth aspect, the embodiment of the present invention provides a readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps in the interface management method according to any one of the first aspect.
In the embodiment of the invention, after receiving a plurality of modification requirements of a back-end developer on the same interface document, the interface document is copied and stored in a plurality of interface documents, and then the plurality of interface documents are distributed to the plurality of modification requirements in a one-to-one correspondence manner, so that the problem that a plurality of interface definitions are mutually covered in the same interface document is solved, the development efficiency of software is improved, and the development cost of the software is reduced.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a flowchart illustrating an interface management method according to an embodiment of the present invention;
FIG. 2 is a second flowchart illustrating an interface management method according to a second embodiment of the present invention;
FIG. 3 is a third flowchart illustrating an interface management method according to a third embodiment of the present invention;
FIG. 4 is a schematic diagram of an internal structure of an interface management apparatus according to an embodiment of the present invention;
fig. 5 is a schematic diagram of an internal structure of an electronic device according to an embodiment of the invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
An embodiment of the present invention provides an interface management method, and as shown in fig. 1, fig. 1 is a schematic flow diagram of an interface management method according to an embodiment of the present invention, where the method includes:
step 11: after receiving a plurality of modification requirements of a back-end developer on the same interface document, copying and storing a plurality of interface documents, wherein the number of the copied and stored interface documents is equal to that of the modification requirements;
step 12: distributing the interface documents to a plurality of modification requirements in a one-to-one correspondence manner;
step 13: after receiving the modification completion notification, combining the modified interface documents to form an interface document set;
step 14: after a first instruction sent by a developer is received, determining a main interface document according to the first instruction, wherein the first instruction is used for indicating a document in an interface document set as the main interface document;
step 15: and deploying the main interface document into the development software so that the development software can call the main interface document when running.
In some embodiments of the present invention, optionally, the selection of the main interface document by the developer may be according to a modification requirement corresponding to the interface document, for example, the modification requirement may be a requirement for solving a problem to be solved by software development; the modification requirement may be a requirement for completing a portion of the last software development version that was in error.
According to the embodiment of the invention, after receiving a plurality of modification requirements of a back-end developer on the same interface document, the interface document is copied and stored in a plurality of interface documents, and then the plurality of interface documents are distributed to the plurality of modification requirements in a one-to-one correspondence manner, so that the problem that a plurality of interface definitions are mutually covered in the same interface document is solved, the development efficiency of software is improved, and the development cost of the software is reduced.
In some embodiments of the present invention, optionally, referring to fig. 2, fig. 2 is a second flowchart of the interface management method according to the embodiment of the present invention, and the deploying the main interface document into the development software further includes:
step 21: after receiving a second instruction sent by a developer, determining a secondary interface document according to the second instruction, wherein the second instruction is used for indicating the secondary interface document in the interface document set;
step 22: based on the modification of the development software by the developer according to the secondary interface document, the modified development software can realize the function of the secondary interface document.
In some embodiments of the present invention, optionally, the selection of the secondary interface document by the developer may be according to a modification requirement corresponding to the interface document, for example, the modification requirement may be a requirement for solving a problem to be solved urgently by software development, but a priority of the problem to be solved is lower than a priority of the problem to be solved by a modification requirement corresponding to the primary interface document; the modification requirement may be a requirement for completing an error portion of the last software development version, but the error portion needs to be completed with a lower priority than an error portion for which the modification requirement corresponding to the primary interface document is for.
In some embodiments of the present invention, optionally, the secondary interface document may be one interface document or may be a plurality of interface documents.
In some embodiments of the present invention, optionally, deploying the main interface document into the development software includes:
and deploying the main interface document in the development software in a CI mode.
CI (Continuous Integration), through which developers can frequently integrate code into the main branch of a common code repository. Developers can submit works to the repository multiple times at any time, rather than developing each functional module independently and submitting one at a time at the end of the development cycle.
The CI setting is beneficial to simplifying integration in the software development process into a simple and easily repeated daily development task, so that the integration is automated, manual operation is reduced, the overall construction cost is reduced, and defects are found early in the development period.
In some embodiments of the present invention, optionally, referring to fig. 3, fig. 3 is a third flowchart of an interface management method according to an embodiment of the present invention, and deploying a main interface document in development software by using a CI manner includes:
step 31: analyzing the main interface document, and generating a data packet according to an analysis result, wherein the format of the data packet is a data exchange format which can be identified and read by development software;
step 32: and after receiving an execution instruction sent by the developer, running the development software to read the data packet and returning a reading result to a development page associated with the developer.
In some embodiments of the present invention, optionally, the development software is a secondary development software of at least one of the following: apifox, Eolink, Yapi and Swagger.
Apifox solves the problem of data synchronization among a plurality of systems through a set of systems and a copy of data. As long as the interface document is defined, the interface debugging, the data Mock and the interface testing can be directly used without being defined again; the interface document and the interface development and debugging use the same tool, and the interface can be ensured to be completely consistent with the definition of the interface document after the interface debugging is finished.
Eolink supports main stream protocols such as HTTP (S), Websocket, TCP and UDP, API documents are automatically generated through code annotation, or codes of all common development languages and frameworks are generated reversely from the API documents, and the API design and development time is saved. The powerful version of the API and change management lets you not put you through any changes to the API.
YAPI is a visual interface management tool developed by a local network mobile architecture group (YMFE for short, a group of large front-end teams with imagination, creativity and influence jointly formed by FE, iOS and Android engineers), and is a locally-deployable interface management platform for communicating front and back ends and QA. YAPI is intended to provide more elegant interface management services for developers, products and testers, and can help developers easily create, publish and maintain APIs of different projects and different platforms. With YAPI, we can conveniently test, manage and maintain API interfaces of multiple items, unlike Swagger which goes on and off with application (and most of online environment needs to be shut down), YAPI is an independent service platform.
Swagger is a canonical and complete framework for generating, describing, invoking and visualizing RESTful-style Web services. The goal of Swagger is to define a standard and language-independent interface to REST APIs that allows people and computers to have the ability to discover and understand services without having to access source code, documentation, or network traffic monitoring. When properly defined by Swagger, the user can understand the remote service and interact with the remote service using minimal implementation logic. Swagger eliminates guesses that may be had when calling a service, similar to the interface implemented for the underlying programming.
Swagger supports API to automatically generate synchronized online documents: after the Swagger is used, the document can be directly generated through the code, the interface document does not need to be written manually, the method is very convenient for programmers, and the time for writing the document can be saved to learn a new technology.
Swagger provides the Web page online test API: the light documentation is not enough and the documentation generated by Swagger also supports online testing. And parameters and formats are set, and the interface can be tested on line by directly inputting values corresponding to the parameters on the interface.
In some embodiments of the invention, optionally, the data exchange format is a json format.
JSON (JavaScript Object Notation) is a lightweight data exchange format. It stores and represents data in a text format that is completely independent of the programming language, based on a subset of ECMAScript (js specification set by the european computer association). The compact and clear hierarchy makes JSON an ideal data exchange language. The network transmission method is easy to read and write by people, is easy to analyze and generate by machines, and effectively improves the network transmission efficiency.
An interface management apparatus 40 according to an embodiment of the present invention is shown in fig. 4, where fig. 4 is a schematic diagram of an internal structure of the interface management apparatus according to the embodiment of the present invention, and the interface management apparatus includes:
the receiving module 41 is configured to copy and store a plurality of interface documents after receiving multiple modification requirements of a back-end developer on the same interface document, where the number of copied and stored interface documents is equal to the number of modification requirements;
an allocation module 42, configured to allocate the plurality of interface documents to the plurality of modification requirements in a one-to-one correspondence;
a modification module 43, configured to, after receiving the modification completion notification, combine the modified interface documents to form an interface document set;
the combining module 44 is configured to determine a main interface document according to a first instruction after receiving the first instruction sent by the developer, where the first instruction is used to indicate that a document in the interface document set is the main interface document;
and the deployment module 45 is used for deploying the main interface document into the development software so that the development software can call the main interface document when running.
In some embodiments of the present invention, the first and second electrodes are, optionally,
the combining module 44 may be further configured to, after receiving a second instruction issued by the developer, determine a secondary interface document according to the second instruction, where the second instruction is used to indicate the secondary interface document in the interface document set;
the deployment module 45 may be further configured to modify the development software according to the secondary interface document, where the modified development software can implement the function of the secondary interface document.
In some embodiments of the present invention, the first and second electrodes are, optionally,
the deployment module 45 may be further configured to deploy the main interface document in the development software in a CI manner.
In some embodiments of the present invention, the first and second electrodes are, optionally,
the deployment module 45 may be further configured to parse the main interface document, and generate a data packet according to a parsing result, where a format of the data packet is a data exchange format that can be read by the development software;
the deployment module 45 may be further configured to, after receiving an execution instruction sent by a developer, run the development software to read the data packet, and return a reading result to a development page associated with the developer.
The interface management device provided in the embodiment of the present application can implement each process implemented by the method embodiments of fig. 1 to fig. 3, and achieve the same technical effect, and is not described herein again to avoid repetition.
An electronic device 50 is provided in an embodiment of the present invention, referring to fig. 5, fig. 5 is a schematic diagram of an internal structure of the electronic device 50 in the embodiment of the present invention, and includes a processor 51, a memory 52, and a program or an instruction stored in the memory 52 and capable of being executed on the processor 51, where the program or the instruction implements steps in any interface management method in the present invention when executed by the processor.
The embodiment of the present invention provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of any one of the embodiments of the interface management method described above, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.
The readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (10)
1. An interface management method, characterized by: the method comprises the following steps:
after receiving a plurality of modification requirements of a back-end developer on the same interface document, copying and storing a plurality of interface documents, wherein the number of the copied and stored interface documents is equal to that of the modification requirements;
distributing the interface documents to the modification requirements in a one-to-one correspondence manner;
after receiving a modification completion notification, combining the modified interface documents to form an interface document set;
after a first instruction sent by a developer is received, determining a main interface document according to the first instruction, wherein the first instruction is used for indicating a document in the interface document set as the main interface document;
deploying the main interface document into development software so that the development software can call the main interface document when running.
2. The interface management method according to claim 1, wherein: deploying the main interface document into development software, and then:
after receiving a second instruction sent by a developer, determining a secondary interface document according to the second instruction, wherein the second instruction is used for indicating the secondary interface document in the interface document set;
and based on the modification of the development software by the developer according to the secondary interface document, the modified development software can realize the function of the secondary interface document.
3. The interface management method according to claim 1, wherein: deploying the main interface document into development software, including:
and deploying the main interface document in the development software in a CI mode.
4. The interface management method according to claim 3, wherein: deploying the main interface document in the development software in a CI mode, including:
analyzing the main interface document, and generating a data packet according to an analysis result, wherein the format of the data packet is a data exchange format which can be read by the development software;
and after receiving an execution instruction sent by a developer, operating the development software to read the data packet and returning a reading result to a development page associated with the developer.
5. The interface management method according to claim 4, wherein: the development software is at least secondary development software of the following software: apifox, Eolink, Yapi and Swagger.
6. The interface management method according to claim 4, wherein: the data exchange format is a json format.
7. An interface management apparatus, characterized in that: the method comprises the following steps:
the receiving module is used for copying and storing a plurality of interface documents after receiving a plurality of modification requirements of a back-end developer on the same interface document, wherein the number of the copied and stored interface documents is equal to that of the modification requirements;
the distribution module is used for distributing the interface documents to the modification requirements in a one-to-one correspondence manner;
the modification module is used for combining the interface documents which are modified to form an interface document set after receiving a modification completion notification;
the system comprises a combination module, a first interface document collection module and a second interface document collection module, wherein the combination module is used for determining a main interface document according to a first instruction after receiving the first instruction sent by a developer, and the first instruction is used for indicating a document in the interface document collection as the main interface document;
the deployment module is used for deploying the main interface document into development software so that the development software can call the main interface document when running.
8. The interface management apparatus according to claim 7, wherein:
the combining module is used for determining a secondary interface document according to a second instruction after receiving the second instruction sent by a developer, wherein the second instruction is used for indicating the secondary interface document in the interface document set;
the deployment module is used for modifying the development software according to the secondary interface document, and the modified development software can realize the function of the secondary interface document.
9. An electronic device, characterized in that: comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, which when executed by the processor implements the steps in the interface management method according to any one of claims 1 to 6.
10. A readable storage medium, characterized by: the readable storage medium stores thereon a program or instructions which, when executed by a processor, implement the steps in the interface management method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111593173.5A CN113971024B (en) | 2021-12-24 | 2021-12-24 | Interface management method, device, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111593173.5A CN113971024B (en) | 2021-12-24 | 2021-12-24 | Interface management method, device, electronic equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113971024A true CN113971024A (en) | 2022-01-25 |
| CN113971024B CN113971024B (en) | 2022-02-25 |
Family
ID=79590729
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111593173.5A Active CN113971024B (en) | 2021-12-24 | 2021-12-24 | Interface management method, device, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113971024B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110362295A (en) * | 2019-05-27 | 2019-10-22 | 深圳壹账通智能科技有限公司 | Code generating method, device, computer installation and storage medium |
| CN110442378A (en) * | 2019-06-27 | 2019-11-12 | 平安科技（深圳）有限公司 | The amending method and system of interface document |
| CN112199331A (en) * | 2020-10-09 | 2021-01-08 | 平安科技（深圳）有限公司 | Automatic generation method, system, terminal and storage medium of interface document |
| CN113672204A (en) * | 2021-07-22 | 2021-11-19 | 北京明略昭辉科技有限公司 | Interface document generation method, system, electronic equipment and storage medium |
-
2021
- 2021-12-24 CN CN202111593173.5A patent/CN113971024B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110362295A (en) * | 2019-05-27 | 2019-10-22 | 深圳壹账通智能科技有限公司 | Code generating method, device, computer installation and storage medium |
| CN110442378A (en) * | 2019-06-27 | 2019-11-12 | 平安科技（深圳）有限公司 | The amending method and system of interface document |
| CN112199331A (en) * | 2020-10-09 | 2021-01-08 | 平安科技（深圳）有限公司 | Automatic generation method, system, terminal and storage medium of interface document |
| CN113672204A (en) * | 2021-07-22 | 2021-11-19 | 北京明略昭辉科技有限公司 | Interface document generation method, system, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113971024B (en) | 2022-02-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109117131B (en) | Code generation method and device, storage medium and electronic terminal | |
| US9524226B2 (en) | System and method for display of software quality | |
| US6941546B2 (en) | Method and apparatus for testing a software component using an abstraction matrix | |
| Wells | Performance analysis using CPN tools | |
| CN104035859B (en) | A kind of Visual Automatic Test method and its system | |
| WO2004036340A2 (en) | A method, a language and a system for the definition and implementation of software solutions | |
| CN110955409B (en) | Method and device for creating resources on cloud platform | |
| CN115639980A (en) | Draggable front-end logic arrangement method and device for low-code platform | |
| CN110727429A (en) | Front-end page generation method, device and equipment | |
| CN110297637A (en) | The applicable resource file thermogravimetric of full platform client software carries tool and method of development | |
| CN109542444B (en) | JAVA application monitoring method, device, server and storage medium | |
| KR101352383B1 (en) | Method of program development using Visual Programming Language and computer readable medium thereof | |
| CN112199261A (en) | Application program performance analysis method and device and electronic equipment | |
| CN111143228B (en) | Test code generation method and device based on decision table method | |
| CN113971024B (en) | Interface management method, device, electronic equipment and readable storage medium | |
| CN114327416A (en) | Interface synchronization method and device applied to development branch and electronic equipment | |
| Savic et al. | Use case specification at different levels of abstraction | |
| CN110737431B (en) | Software development method, development platform, terminal device and storage medium | |
| CN115904382A (en) | Code development method, system, client, server, device and storage medium | |
| CN112363700A (en) | Cooperative creation method and device of intelligent contract, computer equipment and storage medium | |
| Davis et al. | Requirements language processing for the effective testing of real-time systems | |
| CN117406973B (en) | Interactive data analysis method and device | |
| Morgado | Live preview and coding assistance tool for Virtual Reality programming with A-Frame | |
| CN117170654A (en) | Development method and device of graphical user interface application program and electronic equipment | |
| Bronkhorst et al. | Design Report VEmulate |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |