Product development method, apparatus, computing device, and storage medium
By generating software and hardware schematics through a functional component library, the problem of software and hardware development processes being unsuitable for agile development is solved, enabling parallel development and independent iteration of software and hardware, and improving development efficiency and flexibility.
Patent Information
- Application Number
- PCT/CN2023/093291
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-10
- Publication Date
- 2024-11-14
AI Technical Summary
Existing software and hardware development processes are not suitable for agile development, leading to complex and error-prone communication between software and hardware engineers, and making it difficult to migrate software to hardware, thus hindering feature delivery.
By using a pre-configured functional component library, a list of functional components is generated, along with basic software code and hardware schematics, enabling parallel development of software and hardware. The package manager automatically generates dependencies, supporting iterative modifications.
It enables parallel development of software and hardware, reduces mutual dependencies, improves development efficiency and flexibility, and supports independent iterative modifications.
Smart Images

Figure CN2023093291_14112024_PF_FP_ABST
Abstract
Description
Product development method, device, computing device and storage medium Technical Field
[0001] The present disclosure generally relates to the field of automation system technology, and more particularly, to a product development method, apparatus, computing device, and storage medium. Background Art
[0002] The demand for designing devices with highly coupled software and hardware is increasing. However, hardware and software engineering tools operate in completely different ecosystems. Aligning design requirements between software and hardware relies heavily on communication between software and hardware engineers. This increases the communication workload between software and hardware engineers and increases the risk of errors.
[0003] Currently, most embedded devices are developed according to the workflow described below.
[0004] First, product definition is carried out, then software definition and hardware definition are carried out respectively, and then software prototype design and hardware prototype design are carried out respectively. After hardware prototype design, BSP (board support package) development is carried out, and finally software migration is carried out.
[0005] This workflow isn't well-suited for agile development of embedded devices. In agile development, requirements can change rapidly. If the changed requirements affect both software and hardware, the aforementioned workflow will need to be re-executed, which can be time-consuming.
[0006] For most embedded device vendors, their hardware team can provide a fully functional PCB (printed circuit board) with all the necessary features, known as a "development board." The software team can code on this development board without the need for actual production hardware. Once the requirements and software are finalized, the hardware team will provide the production hardware, allowing the software team to migrate the software code to this hardware.
[0007] In the above process, software definition and prototyping are performed on the development board. This approach separates software iteration from hardware iteration, saving the effort and cost of repeated hardware prototyping. It also enables software development using an agile approach.
[0008] However, it is impossible to design a fully functional "development board" (some functions are even mutually exclusive), and it is difficult to migrate software from a development board to a production board. Therefore, any software changes that may trigger hardware design changes must be made with extreme caution, which hinders the delivery of some cool features that require both hardware and software to implement.
[0009] Summary of the Invention
[0010] A brief overview of the present invention is provided below to provide a basic understanding of certain aspects of the present invention. It should be understood that this overview is not an exhaustive overview of the present invention. It is not intended to identify key or important aspects of the present invention, nor is it intended to limit the scope of the present invention. Its purpose is simply to present certain concepts in a simplified form as a prelude to the more detailed description discussed later.
[0011] In view of this, the present disclosure proposes a new product development method that can achieve parallel development of software and hardware without relying on each other.
[0012] According to one aspect of the present disclosure, there is provided a product development method, comprising:
[0013] Identify at least one desired feature of the target product;
[0014] Based on the function and a pre-configured function component library, generating a function component list that implements the function; and
[0015] A code generation operation is performed on each functional component in the functional component list to generate respective basic software codes and basic hardware schematics.
[0016] In this way, functional components can be used to develop and test product functions, and any hardware that can provide corresponding hardware resources can be used as a test platform for the function.
[0017] Optionally, in an example of the above aspect, the functional component library includes a plurality of pre-configured functional components, each functional component including hardware, software, configuration information, dependency information with other functional components, and a generator related to a function.
[0018] In this way, software codes and hardware schematics of different functions are combined together to form corresponding functional components, and product developers can easily select corresponding functions by selecting functional components.
[0019] Optionally, in an example of the above aspect, generating a list of functional components for implementing the function based on the function and a preconfigured functional component library includes:
[0020] Based on the dependency information between the functional component and other functional components, a package manager is used to automatically generate a list of functional components that implement the function.
[0021] In this way, the package manager can be used to easily generate a list of functional components that implement product functions.
[0022] Optionally, in an example of the above aspect, performing a code generation operation on each functional component in the functional component list to generate respective basic software codes and basic hardware schematics includes:
[0023] For each functional component in the functional component list, a basic software code is generated by a generator based on the software and configuration information in the functional component; and a basic hardware schematic diagram is generated by a generator based on the hardware and configuration information in the functional component.
[0024] In this way, basic software code and basic hardware schematics can be easily generated using the configuration information and generators in the functional components.
[0025] Optionally, in an example of the above aspect, the product development method further includes: synthesizing the target product based on the basic software code and the basic hardware schematic diagram.
[0026] Optionally, synthesizing the target product based on the basic software code and the basic hardware schematic diagram includes:
[0027] Compiling a complete software code based on the basic software code, performing binary processing on the software code to obtain a software prototype;
[0028] Obtaining a complete printed circuit board schematic based on the basic hardware schematic, performing printed circuit board layout, and obtaining a hardware prototype; and
[0029] The target product is synthesized based on the software prototype and the hardware prototype.
[0030] Optionally, synthesizing the target product based on the basic software code and the basic hardware schematic diagram includes:
[0031] Iterative execution as needed: obtaining a complete software code based on the basic software code, performing binary processing on the software code, and obtaining a software prototype;
[0032] Iteratively perform as needed: obtain a complete PCB schematic based on the basic hardware schematic, perform PCB layout, and obtain a hardware prototype; and
[0033] The target product is synthesized based on the software prototype and the hardware prototype.
[0034] In this way, the target product can be easily synthesized using the generated basic software code and basic hardware schematics, and the software or hardware parts can be modified separately or iteratively as needed without affecting each other.
[0035] According to another aspect of the present disclosure, there is provided a product development apparatus, comprising:
[0036] a function determination unit configured to determine at least one function required by a target product;
[0037] a function component list generating unit configured to generate a function component list for implementing the function based on the function and a pre-configured function component library;
[0038] The basic software and hardware generation unit is configured to perform code generation operations on each functional component in the functional component list to generate respective basic software codes and basic hardware schematics.
[0039] According to another aspect of the present disclosure, there is provided a product development method, comprising:
[0040] receiving, through a graphical user interface, a functional component related to at least one function required by a target product;
[0041] Based on the functions and a pre-configured functional component library, generate a list of functional components that implement all functions of the target product;
[0042] Receiving an instruction to execute a code generation operation through the graphical user interface, and executing the code generation operation for each functional component on the graphical user interface to generate respective basic software codes and basic hardware schematics;
[0043] A schematic diagram of the basic software code is displayed in a first display area of the graphical user interface, a schematic diagram of the basic hardware schematic diagram is displayed in a second display area of the graphical user interface, and a schematic diagram of configuration information representing a mapping relationship between the basic software code and the corresponding basic hardware schematic diagram is displayed in a third display area of the graphical user interface.
[0044] According to another aspect of the present disclosure, a computing device is provided, comprising: at least one processor; and a memory coupled to the at least one processor, the memory being configured to store instructions that, when executed by the at least one processor, enable the processor to perform the method described above.
[0045] According to another aspect of the present disclosure, a non-transitory machine-readable storage medium is provided, which stores executable instructions. When the instructions are executed, the machine is caused to perform the method described above.
[0046] According to another aspect of the present disclosure, a computer program is provided, comprising computer-executable instructions, which, when executed, cause at least one processor to perform the method described above.
[0047] According to another aspect of the present disclosure, a computer program product is provided, which is tangibly stored on a computer-readable medium and includes computer-executable instructions that, when executed, cause at least one processor to perform the method described above.
[0048] According to the product development method and apparatus of the embodiments of the present disclosure, software code and hardware schematics for different functions are combined to form corresponding functional components. Product developers can conveniently select the corresponding function by selecting the functional component. Functional components can be used to develop and test product functions, and any hardware that can provide the corresponding hardware resources can serve as a test platform for the function. Only the software code or the hardware circuit can be modified, allowing iterative software development and iterative hardware development to proceed separately without relying on each other. BRIEF DESCRIPTION OF THE DRAWINGS
[0049] The above and other purposes, features and advantages of the present invention will be more easily understood by referring to the following description of the embodiments of the present invention in conjunction with the accompanying drawings. The components in the accompanying drawings are only for illustrating the principles of the present invention. In the accompanying drawings, the same or similar technical features or components will be represented by the same or similar reference numerals. In the accompanying drawings:
[0050] FIG1 is a flowchart of an exemplary process of a product development method according to an embodiment of the present disclosure.
[0051] FIG2 is a block diagram illustrating an exemplary configuration of a product development apparatus according to an embodiment of the present disclosure.
[0052] FIG3 is a schematic diagram of a graphical user interface of a development tool for developing a product using the product development method according to an embodiment of the present invention.
[0053] FIG4 is a flowchart illustrating an exemplary process of a method for developing a product using a graphical user interface according to another embodiment of the present disclosure.
[0054] FIG5 shows a block diagram of a computing device for implementing a product development method according to an embodiment of the present disclosure.
[0055] The reference numerals are as follows: 100: Product development method S102, S104, S106, S108: Step 200: Product development apparatus 202: Function determination unit 204: Functional component list generation unit 206: Basic software and hardware generation unit 208: Product synthesis unit 300: Graphical user interface 302: First display area 304: Second display area 306: Third display area CA: Functional component 400: Product development method S402, S404, S406, S408: Step 500: Computing device 502: Processor 504: Memory DETAILED DESCRIPTION
[0056] The subject matter described herein will now be discussed with reference to example embodiments. It should be understood that discussing these embodiments is intended only to enable those skilled in the art to better understand and implement the subject matter described herein, and is not intended to limit the scope of protection, applicability, or examples set forth in the claims. The functions and arrangements of the elements discussed may be changed without departing from the scope of protection of this disclosure. Various examples may omit, replace, or add various processes or components as needed. For example, the described method may be performed in an order different from the described order, and various steps may be added, omitted, or combined. In addition, features described relative to some examples may also be combined in other examples.
[0057] As used herein, the term "including" and its variations are open terms meaning "including but not limited to". The term "based on" means "based at least in part on". The terms "one embodiment" and "an embodiment" mean "at least one embodiment". The term "another embodiment" means "at least one other embodiment". The terms "first", "second", etc. may refer to different or the same objects. Other definitions may be included below, whether explicit or implicit. Unless the context clearly indicates otherwise, the definition of a term is consistent throughout the specification.
[0058] In view of this, the present invention proposes a new product development method, which can realize the parallel development of software and hardware without mutual dependence.
[0059] The product development method and apparatus according to the embodiments of the present disclosure will be described below with reference to the accompanying drawings.
[0060] FIG1 is a flowchart of an exemplary process of a product development method 100 according to an embodiment of the present disclosure.
[0061] First, in step S102 , at least one function required by the target product is determined.
[0062] The target product is the product to be developed. First, determine the functions that the product will support. For example, determine that the product needs to support screen projection. It is understood that the function determined to be supported by the product can be one or more.
[0063] Next, in step S104, based on the functions required for the target product determined in the above steps and the pre-configured functional component library, a functional component list for realizing the functions is generated.
[0064] In the method according to an embodiment of the present invention, a functional component library is preconfigured. The functional component library includes functional components defined for different functions of different products. A functional component includes hardware, software, configuration information related to a particular function, information about dependencies with other functional components, and a generator.
[0065] Specifically, the hardware is the hardware resources that implement the function, for example, it may include circuit modules, interface information, etc.
[0066] Software refers to software resources that implement the function, including, for example, header files, source files, etc.
[0067] Wherein, based on the function and a pre-configured function component library, generating a function component list for realizing the function includes: based on dependency information between the function component and other function components, using a package manager to automatically generate a function component list for realizing the function.
[0068] Each functional component includes dependencies with other functional components. For example, if the product is determined to support screen projection, and screen projection depends on WiFi, then in addition to the functional component corresponding to the screen projection function, the package manager will automatically add the functional component corresponding to the WiFi function to the functional component list. It is understood that if other functions of the product are also determined, the functional component list will also include the functional components corresponding to other functions and the functional components with which they have dependencies.
[0069] Specifically, the package manager may be, for example, Conan, Npm, Pip, Apt, Yarn, etc. In the embodiment of the present invention, there is no limitation on which package manager is used.
[0070] Next, in step S106 , a code generation operation is performed on each functional component in the functional component list to generate respective basic software codes and basic hardware schematics.
[0071] Specifically, for each functional component in the functional component list, a basic software code is generated by a generator based on the software and configuration information in the functional component; and a basic hardware schematic diagram is generated by a generator based on the hardware and configuration information in the functional component.
[0072] After executing the above operations of the method according to the embodiment of the present invention, basic software codes and basic hardware schematics related to the target product are obtained.
[0073] In one example, the product development method 100 may further include step S108 , synthesizing the target product based on the obtained basic software code and basic hardware schematic diagram.
[0074] Optionally, software engineers and hardware engineers can further carry out product development work based on the basic software code and basic hardware schematics respectively.
[0075] The generated basic software code already includes all the software code required to implement the product's functions. Software engineers only need to use some upper-level logic to arrange the source code to meet product requirements. Using the generated basic hardware schematics, hardware engineers only need to add some peripheral circuits and layout the printed circuit board.
[0076] Specifically, synthesizing the target product based on the basic software code and the basic hardware schematic diagram may include:
[0077] Compiling a complete software code based on the basic software code, performing binary processing on the software code to obtain a software prototype;
[0078] Obtaining a complete printed circuit board (PCB) schematic diagram based on the basic hardware schematic diagram, performing PCB layout, and obtaining a hardware prototype;
[0079] The target product is synthesized based on the software prototype and the hardware prototype.
[0080] Through the above process, the software prototype and hardware prototype of the target product can be determined. The hardware prototype can be used to produce the hardware circuit, and then combined with the software prototype to make the target product. This process is not described in detail in the specification of this disclosure.
[0081] In another specific example, a software engineer and a hardware engineer may iteratively optimize a software prototype and a hardware prototype based on the basic software code and the basic hardware schematic, respectively. In this case, synthesizing the target product based on the basic software code and the basic hardware schematic includes:
[0082] Iterative execution as needed: obtaining a complete software code based on the basic software code, performing binary processing on the software code, and obtaining a software prototype;
[0083] Iterative execution as needed: obtaining a complete PCB schematic based on the basic hardware schematic, performing PCB layout, and obtaining a hardware prototype;
[0084] The target product is synthesized based on the software prototype and the hardware prototype.
[0085] According to the product development method of the disclosed embodiments, software code and hardware schematics for different functions are combined to form corresponding functional components. Product developers can conveniently select the corresponding function by selecting the functional component. Functional components can be used to develop and test product functions, and any hardware that can provide the corresponding hardware resources can serve as a test platform for the function. Only the software code or the hardware circuit can be modified, allowing iterative software development and iterative hardware development to proceed separately without relying on each other.
[0086] FIG. 2 is a block diagram showing an exemplary configuration of a product development apparatus 200 for executing the product development method shown in FIG. 1 .
[0087] In FIG. 2 , the product development apparatus 200 includes a function determination unit 202 , a function component list generation unit 204 , and a basic software and hardware generation unit 206 .
[0088] The function determination unit 202 is configured to determine at least one function required by the target product.
[0089] The function component list generating unit 204 is configured to generate a function component list for realizing the function based on the function and a pre-configured function component library.
[0090] The basic software and hardware generating unit 206 is configured to perform code generation operations on each functional component in the functional component list, and generate respective basic software codes and basic hardware schematics.
[0091] The functional component library includes a plurality of pre-configured functional components, and each functional component includes hardware, software, configuration information, dependency information with other functional components, and a generator related to a function.
[0092] The function component list generating unit 204 is further configured to automatically generate a function component list for implementing the function by using a package manager based on the dependency relationship information between the function component and other function components.
[0093] Among them, the basic software and hardware generation unit 206 is further configured to generate basic software code for each functional component in the functional component list based on the software and configuration information in the functional component using a generator; and generate basic hardware schematics based on the hardware and configuration information in the functional component using a generator.
[0094] The product development apparatus 200 may further include a product synthesis unit 208 configured to synthesize the target product based on the basic software code and the basic hardware schematic diagram.
[0095] The product synthesis unit 208 is further configured to:
[0096] Compiling a complete software code based on the basic software code, performing binary processing on the software code to obtain a software prototype;
[0097] Obtaining a complete printed circuit board schematic based on the basic hardware schematic, performing printed circuit board layout, and obtaining a hardware prototype; and
[0098] The target product is synthesized based on the software prototype and the hardware prototype.
[0099] Optionally, the product synthesis unit 208 may also be configured to:
[0100] Iterative execution as needed: obtaining a complete software code based on the basic software code, performing binary processing on the software code, and obtaining a software prototype;
[0101] Iteratively perform as needed: obtain a complete PCB schematic based on the basic hardware schematic, perform PCB layout, and obtain a hardware prototype; and
[0102] The target product is synthesized based on the software prototype and the hardware prototype.
[0103] It should be noted that the structure of the product development device 200 and its component units shown in FIG2 is merely exemplary, and those skilled in the art may modify the structural block diagram shown in FIG2 as needed.
[0104] The details of the operations and functions of the various parts of the product development apparatus 200 may be the same as or similar to the relevant parts of the embodiment of the product development method of the present disclosure described with reference to FIG1 , and will not be described in detail here.
[0105] Figure 3 is a schematic diagram of a graphical user interface of a development tool for product development using a product development method according to an embodiment of the present invention. Figure 4 is a flow chart of an exemplary process of a method 400 for product development using a graphical user interface according to another embodiment of the present disclosure.
[0106] The following describes a graphical user interface and a method 400 for developing a product using the graphical user interface in conjunction with FIG. 3 and FIG. 4 .
[0107] First, in step S402 shown in FIG. 4 , functional components related to functions required by a target product are received through a graphical user interface.
[0108] Specifically, for example, the user can drag and drop functional components related to the functions required by the target product in the functional component library on the graphical user interface to the display area. In Figure 3, the graphical user interface 300 includes a first display area 302, a second display area 304, and a third display area 306. The graphical user interface in Figure 3 does not show a schematic diagram of the functional component library. It can be understood that, for example, a schematic diagram of a functional component library can be included on the left side of the graphical user interface 300, which includes a plurality of functional components with different functions. The user can drag the corresponding functional components to any display area on the right according to the functions required by the product. For example, the mark "CA" in Figure 3 represents a schematic diagram of a functional component, which includes five parts: hardware, software, configuration information, dependency information with other functional components, and a generator.
[0109] Next, in step S404, a list of functional components that realize all functions of the target product is generated based on the functions and a pre-configured functional component library.
[0110] As described above, the functional component list includes not only the functional components corresponding to the functions selected by the user, but also the functional components corresponding to the functions on which these functions depend.
[0111] In an embodiment of the present invention, a package manager may be used to automatically generate a list of functional components that implement all functions of the target product.
[0112] Next, in step S406, an instruction to execute a code generation operation is received through the graphical user interface, and a code generation operation is executed for each functional component on the graphical user interface to generate respective basic software codes and basic hardware schematics.
[0113] For example, the graphical user interface shown in Figure 3 can also include a button (not shown in the figure). By clicking this button on the graphical user interface, the user can trigger the execution of the generator of each functional component on the graphical user interface to generate their respective basic software codes and basic hardware schematics.
[0114] In step S408, a schematic diagram of the basic software code is displayed in the first display area of the graphical user interface, a schematic diagram of the basic hardware schematic diagram is displayed in the second display area of the graphical user interface, and a schematic diagram of configuration information representing the mapping relationship between the basic software code and the corresponding basic hardware schematic diagram is displayed in the third display area of the graphical user interface.
[0115] Using the graphical user interface shown in Figure 3, users can conveniently add or remove functional components corresponding to the functions required by the target product as needed, and can also automatically add or remove other related functional components. After obtaining the basic software code and basic hardware schematics, users can further synthesize the target product, which will not be explained in detail here.
[0116] The above describes a specific embodiment of product development using a graphical user interface in combination with Figures 3 and 4. The graphical user interface shown in Figure 3 and the text therein are merely a specific example of implementing the product development method according to the present invention. The layout of the graphical user interface and the text therein do not affect the scope of protection of the present invention. The technical solution of the present invention does not need to pay attention to the text details in Figure 3. Those skilled in the art can adopt any other style of graphical user interface, which will not be described in detail here.
[0117] The product development method and product development apparatus according to the present disclosure are described above with reference to Figures 1 to 4. Each unit of the product development apparatus described above can be implemented using hardware, software, or a combination of hardware and software.
[0118] 5 shows a block diagram of a computing device 500 for implementing a product development method according to an embodiment of the present disclosure. According to one embodiment, the computing device 500 may include at least one processor 502 that executes at least one computer-readable instruction (i.e., the aforementioned elements implemented in software form) stored or encoded in a computer-readable storage medium (i.e., memory 504).
[0119] It should be understood that the computer executable instructions stored in the memory 504, when executed, cause the at least one processor 502 to perform the various operations and functions described above in conjunction with Figures 1-4 in various embodiments of the present disclosure.
[0120] According to one embodiment, a non-transitory machine-readable medium is provided. The non-transitory machine-readable medium may have machine-executable instructions (i.e., the elements implemented in software above), which, when executed by a machine, cause the machine to perform the various operations and functions described above in conjunction with Figures 1-4 in various embodiments of the present disclosure.
[0121] According to one embodiment, a computer program is provided, including computer-executable instructions, which, when executed, enable at least one processor to perform the various operations and functions described above in conjunction with Figures 1-4 in various embodiments of the present disclosure.
[0122] According to one embodiment, a computer program product is provided, including computer-executable instructions, which, when executed, enable at least one processor to perform the various operations and functions described above in conjunction with Figures 1-4 in various embodiments of the present disclosure.
[0123] It should be understood that the various embodiments in this specification are described in a progressive manner, and reference can be made to the common or similar parts of the various embodiments. Each embodiment focuses on the differences from the other embodiments. For example, the above-mentioned apparatus embodiments, computing device embodiments, and machine-readable storage medium embodiments are generally similar to the method embodiments, so their descriptions are relatively simple. For relevant details, reference can be made to the descriptions of the method embodiments.
[0124] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0125] Not all steps and units in the above processes and system structure diagrams are required, and some steps or units may be omitted according to actual needs. The device structures described in the above embodiments can be physical structures or logical structures, that is, some units may be implemented by the same physical entity, or some units may be implemented by multiple physical entities, or may be implemented by certain components in multiple independent devices.
[0126] The specific embodiments described above in conjunction with the accompanying drawings describe exemplary embodiments, but do not represent all embodiments that can be implemented or fall within the scope of protection of the claims. The term "exemplary" used throughout this specification means "used as an example, instance or illustration" and does not mean "preferred" or "having advantages" over other embodiments. For the purpose of providing an understanding of the described technology, the specific embodiments include specific details. However, these technologies can be implemented without these specific details. In some instances, in order to avoid obscuring the concepts of the described embodiments, well-known structures and devices are shown in block diagram form.
[0127] The foregoing description of the present disclosure is provided to enable any person skilled in the art to implement or use the present disclosure. Various modifications to the present disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is intended to be consistent with the widest range of principles and novel features disclosed herein.
[0128] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.
Claims
1. Product development methods (100), including: Determine at least one function required for a target product (S102); Based on the function and a pre-configured function component library, a function component list for implementing the function is generated (S104); as well as A code generation operation is performed on each functional component in the functional component list to generate respective basic software codes and basic hardware schematics (S106).
2. The method (100) of claim 1, wherein: The functional component library includes a plurality of pre-configured functional components, each of which includes hardware, software, configuration information, dependency information with other functional components, and a generator related to a function.
3. The method (100) of claim 2, wherein: Based on the function and the pre-configured function component library, generating a function component list for implementing the function (S104) includes: Based on the dependency information between the functional components and other functional components, a package manager is used to automatically generate a list of functional components for implementing the functions.
4. The method (100) of claim 2, wherein: Performing code generation operations on each functional component in the functional component list to generate respective basic software codes and basic hardware schematics (S106) includes: For each functional component in the functional component list, a basic software code is generated by a generator based on the software and configuration information in the functional component; a basic hardware schematic diagram is generated by a generator based on the hardware and configuration information in the functional component.
5. The method (100) according to any one of claims 2 to 4, further comprising: The target product is synthesized based on the basic software code and the basic hardware schematic diagram (S108).
6. The method (100) of claim 5, wherein: Synthesizing the target product based on the basic software code and the basic hardware schematic diagram (S108) includes: Compile a complete software code based on the basic software code, perform binary processing on the software code, and obtain a software prototype; Based on the basic hardware schematic diagram, a complete printed circuit board schematic diagram is obtained, and a printed circuit board layout is performed to obtain a hardware prototype; and The target product is synthesized based on the software prototype and the hardware prototype.
7. The method (100) of claim 5, wherein: Synthesizing the target product based on the basic software code and the basic hardware schematic diagram (S108) includes: Iterative execution as needed: obtaining a complete software code based on the basic software code, performing binary processing on the software code, and obtaining a software prototype; Iteratively perform as needed: obtain a complete PCB schematic diagram based on the basic hardware schematic diagram, perform PCB layout, and obtain a hardware prototype; and The target product is synthesized based on the software prototype and the hardware prototype.
8. A product development device (200), comprising: A function determination unit (202) is configured to determine at least one function required by a target product; A function component list generating unit (204) is configured to generate a function component list for implementing the function based on the function and a pre-configured function component library; The basic software and hardware generation unit (206) is configured to perform code generation operations on each functional component in the functional component list to generate respective basic software codes and basic hardware schematics.
9. Product development methods (400), including: receiving, through a graphical user interface, a functional component related to at least one function required by a target product (S402); Based on the functions and the pre-configured functional component library, a functional component list that realizes all functions of the target product is generated (S404); Receiving an instruction to execute a code generation operation through the graphical user interface, and executing a code generation operation for each functional component on the graphical user interface to generate respective basic software codes and basic hardware schematics (S406); A schematic diagram of the basic software code is displayed in a first display area of the graphical user interface, a schematic diagram of the basic hardware schematic diagram is displayed in a second display area of the graphical user interface, and a schematic diagram of configuration information representing a mapping relationship between the basic software code and the corresponding basic hardware schematic diagram is displayed in a third display area of the graphical user interface (S408).
10. A computing device (500), comprising: at least one processor (502); as well as A memory (504) coupled to the at least one processor (502), the memory being used to store instructions, and when the instructions are executed by the at least one processor (502), the processor (502) executes the method according to any one of claims 1-7, 9.
11. A non-transitory machine-readable storage medium storing executable instructions, wherein when the instructions are executed, the machine executes the method according to any one of claims 1 to 7 and 9.
12. A computer program product tangibly stored on a computer readable medium and comprising computer executable instructions which, when executed, cause at least one processor to perform the method according to any one of claims 1-7, 9.
Citation Information
Patent Citations
Design method of reconfigurable embedded system based on ontology and system
CN102054087A
Hardware effect simulation method and device based on software programming platform
CN111026381A
Automatic hardware and firmware generation for multi-function custom controls
US20060015844A1
Memory mapping for single and multi-processing implementations of code generated from a block diagram model
US7584465B1
