Article delivery version management method, device, and medium

Abstract

The application discloses a kind of product delivery version management method, equipment and medium, belong to ERP and cloud computing technical field, for solving the technical problems that existing ERP product needs to utilize artificial processing to realize the confirmation of version number and installation disc in the process of making installation disc, high labor cost, and very easy to produce human error, affect the accurate production of installation disc.Method includes: the version number configuration of each subunit corresponding to ERP installation disc is carried out about flow line, and the configured subunit product is obtained;Subunit product is tested and verified in integrated environment, and verification information is obtained;If verification information is verification pass information, then the version number of ERP installation disc is identified and configured, and the installation disc version is determined;According to subunit product, the version number rule configuration corresponding of installation disc version is obtained, and the ERP installation disc version is obtained;ERP installation disc version is configured and corresponding in total flow line, and complete ERP product installation disc is obtained.

Description

Technical Field

[0001] This application relates to the fields of ERP and cloud computing, and in particular to a method, device and medium for managing product deliverables versions. Background Technology

[0002] ERP (Enterprise Resource Planning) products have numerous modules or sub-units, along with vast codebases. While each sub-unit codebase now features automated compilation and a corresponding automated pipeline—where artifacts generated after pipeline execution are automatically added to the artifact repository and deployed to a centralized cloud platform environment for automated testing and use—customers of large-scale ERP products require independent deployment of the complete ERP product, necessitating a complete ERP installation disk.

[0003] In the process of creating installation disks for existing ERP products, the development managers of each sub-unit manage the versions themselves, manually confirm the version number of each artifact, and manually select it into the installation disk creation catalog. This process is tedious and prone to errors. Furthermore, when multiple installation disks need to be created, issues such as missing artifacts or incorrect version artifacts are frequently encountered. Summary of the Invention

[0004] This application provides a method, device, and medium for managing product deliverable versions, which addresses the following technical problem: In the process of creating installation disks, existing ERP products require manual processing to confirm the version number and the installation disk, resulting in high labor costs and easy human error, which affects the accurate creation of the installation disk.

[0005] The embodiments of this application adopt the following technical solutions: On one hand, this application provides a method for managing product deliverable versions, including: configuring version numbers for each sub-unit corresponding to an ERP installation disk according to relevant pipelines to obtain configured sub-unit products; performing integration environment testing and verification on the sub-unit products to obtain verification information; wherein, the verification information includes: verification pass information and verification fail information; if the verification information is verification pass information, then performing version number identification configuration on the ERP installation disk to determine the installation disk version; configuring the installation disk version according to relevant version number rules based on the sub-unit products to obtain the ERP installation disk version; and configuring the ERP installation disk version according to the overall pipeline configuration to obtain a complete ERP product installation disk.

[0006] This application embodiment configures the version number of each subunit related to the production line, and then, based on the configuration of the attribute association relationship between the disk version number and the version number of each product in each subunit, quickly and automatically selects the correct version product from the production line products of each subunit to form a usable and complete ERP product installation disk. When a problem occurs with the installation disk, it is possible to trace back to each stage of product development based on the installation disk version number, accurately troubleshoot the fault, reduce labor costs and human error, and facilitate the production of ERP product installation disks.

[0007] In one feasible implementation, the version numbers of each sub-unit corresponding to the ERP installation disk are configured with respect to the pipeline version number to obtain the configured sub-unit artifact. Specifically, this includes: identifying and extracting artifact version information from each sub-unit; wherein the artifact version information includes: artifact type, version number rule, and attribute status; matching the version number of each sub-unit with the pipeline version number according to the artifact version information; and configuring the version number rule and attribute status according to the artifact type in the artifact version information to obtain the sub-unit artifact; wherein the pipeline contains multiple sub-units.

[0008] In one feasible implementation, the sub-unit artifact is tested and verified in an integrated environment to obtain verification information. The verification information includes verification pass information and verification fail information. Specifically, this includes: deploying the sub-unit artifact to the integrated environment; wherein the integrated environment is a software installation environment based on the ERP installation disk version; according to the deployed integrated environment, testing and verifying the largest version number in the sub-unit artifact to obtain the verification information; if the verification information is verification pass information, then setting the largest version number in the sub-unit artifact to a stable state to obtain a stable state version of the sub-unit artifact; wherein the sub-unit artifact has one and only one stable state version; if the verification information is verification fail information, then the sub-unit artifact is determined to be an obsolete state version.

[0009] In one feasible implementation, if the verification information is verification passed, then the ERP installation disk is configured to identify the version number to determine the installation disk version. Specifically, if the verification information is verification passed, then the ERP installation disk is configured to identify the version number according to the version of the ERP product to obtain version number information; based on the version number information, the installation disk version of the ERP product is determined; wherein, the installation disk version includes at least: beta version and official version.

[0010] In one feasible implementation, before configuring the installation disk version with relevant version number rules according to the sub-unit artifact to obtain the ERP installation disk version, the method further includes: identifying and extracting the version number rule sequence number in the sub-unit artifact; wherein the version number rule sequence number includes: the first, second, third, and fourth digits; matching the installation disk version with relevant installation disk version numbers according to the artifact type in the sub-unit artifact to determine the milestone version number of the installation disk version; wherein the milestone version number includes: Snapshot, Alpha, Beta, Rc, and Release; testing and verifying the installation disk version with relevant attribute states according to the attribute states in the sub-unit artifact to obtain the artifact attribute states of the installation disk version; wherein the artifact attribute states include: maximum number and stable number; and determining the version number rule of the installation disk version based on the version number rule sequence number, the milestone version number, and the artifact attribute states.

[0011] In one feasible implementation, the version number rule for the installation disk version is determined based on the version number rule sequence number, the milestone version number, and the artifact attribute status. Specifically, this includes: establishing a one-to-one correspondence between the milestone version number and the installation disk version number of the installation disk version, and determining a first correspondence; establishing a one-to-one correspondence between the version number rule sequence number and the artifact version rule number of the installation disk version, and determining a second correspondence; establishing a one-to-one correspondence between the artifact attribute status and the version attribute status of the installation disk version, and determining a third correspondence; generating a version number rule relationship table for the installation disk version based on the first, second, and third correspondences; and determining the version number rule for the installation disk version based on the version number rule relationship table.

[0012] In one feasible implementation, the ERP installation disk version is obtained by configuring the installation disk version according to the version number rules based on the sub-unit artifact. Specifically, this includes configuring the installation disk version one-to-one according to the artifact type, version number rules, and attribute status in the sub-unit artifact, and generating the ERP installation disk version based on the version number rules.

[0013] In one feasible implementation, the ERP installation disk version is configured and mapped using a centralized pipeline to obtain a complete ERP product installation disk. Specifically, this includes: transferring the ERP installation disk version to the centralized pipeline; wherein the centralized pipeline exists within the ERP installation disk; classifying the ERP installation disk version according to the version number rules to obtain an installation disk version number based on the ERP installation disk version; wherein the installation disk version number includes a beta version number and a regular version number; and configuring the ERP installation disk version one-to-one based on the installation disk version number to generate the complete ERP product installation disk, thereby realizing the creation of the installation disk for the relevant ERP product.

[0014] Secondly, embodiments of this application also provide a product delivery version management device, the device comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to execute a product delivery version management method as described in any of the above embodiments.

[0015] Thirdly, embodiments of this application also provide a non-volatile computer storage medium, characterized in that the storage medium is a non-volatile computer-readable storage medium, the non-volatile computer-readable storage medium stores at least one program, each program including instructions, and when the instructions are executed by a terminal, the terminal executes a product delivery version management method as described in any of the above embodiments.

[0016] This application provides a method, device, and medium for managing product deliverable versions. By configuring the version number of each sub-unit in relation to the production line, and then configuring the attribute association between the version number of the disk and the version number of each product in each sub-unit, the correct version product can be quickly and automatically selected from the production line products of each sub-unit to form a usable and complete ERP product installation disk. When a problem occurs with the installation disk, it is possible to trace back to each stage of product development based on the installation disk version number, accurately troubleshoot the fault, reduce labor costs and human error, and facilitate the production of ERP product installation disks. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings: Figure 1 A flowchart of a product delivery version management method provided in this application embodiment; Figure 2 A schematic diagram of a version number rule definition structure provided in an embodiment of this application; Figure 3 This is a schematic diagram of the structure of a product delivery version management device provided in an embodiment of this application. Detailed Implementation

[0018] To enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this application.

[0019] This application provides a method for version management of manufactured goods, such as... Figure 1 As shown, the method for managing the version of workpiece deliverables specifically includes steps S101-S105: S101. Configure the version number of the relevant production line for each sub-unit corresponding to the ERP installation disk to obtain the configured sub-unit product.

[0020] Specifically, the product version information in each sub-unit is identified and extracted. This product version information includes: product type, version number rules, and attribute status.

[0021] Furthermore, based on the product version information, the version number of each subunit is matched to the corresponding version number of the pipeline. And based on the product type in the product version information, the version number rules and attribute status are configured accordingly to obtain the subunit product. The pipeline contains multiple subunits.

[0022] Table 1

[0023] In one embodiment, Table 1 is a version number configuration table for a sub-unit pipeline. As shown in Table 1, the artifact version information of this sub-unit is extracted and obtained. Artifact types include: jar, configuration files, metadata, static files, and SQL, etc. Version number rules include: 1.0.0.x-snapshot, 1.0.0.x-rc, etc. Attribute states include: maximum number state and stable state. Then, based on these artifact types in the artifact version information, the version number rules and attribute states are configured one-to-one, and finally, the sub-unit artifacts conforming to this pipeline are configured.

[0024] S102. Perform integrated environment testing and verification on the sub-unit artifacts to obtain verification information. The verification information includes: verification pass information and verification fail information.

[0025] Specifically, the sub-unit artifacts are deployed to the integration environment. This integration environment is a version-based software environment installed from the ERP installation disk. Based on the deployed integration environment, the largest version number in the sub-unit artifacts is tested and verified to obtain verification information.

[0026] If the verification information is "verification passed," the largest version number in the sub-unit artifact is set to a stable state, resulting in a stable state version of the sub-unit artifact. Each sub-unit artifact has one and only one stable state version. If the verification information is "verification failed," the sub-unit artifact is determined to be a discarded version.

[0027] In one embodiment, after each sub-unit artifact generated by the sub-unit pipeline is deployed to the integration environment, the largest version number in the sub-unit artifact is tested and verified according to the deployed integration environment. Verification information is obtained. If the verification passes, the largest version number in the sub-unit artifact is set to a stable state; that is, the largest version number for each sub-unit artifact is simultaneously set to a stable state. If the verification fails, it is set to an obsolete state. At any given time, each artifact has only one stable state.

[0028] S103. If the verification information is "verification passed", then the version number of the ERP installation disk will be identified and configured to determine the installation disk version.

[0029] Specifically, if the verification information is successful, the ERP installation disk is configured to identify the version number based on the ERP product's version. Based on this version number, the ERP product's installation disk version is determined. The installation disk version includes at least two versions: beta and official.

[0030] S104. Based on the sub-unit products, configure the version number rules of the installation disk version to obtain the ERP installation disk version.

[0031] Specifically, the version number rule sequence number in the sub-unit artifact is identified and extracted. The version number rule sequence number includes the first, second, third, and fourth digits.

[0032] Furthermore, based on the artifact type within the sub-unit artifact, the installation disk version is matched with the corresponding installation disk version number to determine the milestone version number of the installation disk version. The milestone version number includes: Snapshot, Alpha, Beta, Rc, and Release. Based on the attribute status of the sub-unit artifact, the installation disk version undergoes relevant attribute status testing and verification to obtain the artifact attribute status of the installation disk version. The artifact attribute status includes: maximum number and stable number. Based on the version number rule sequence number, the milestone version number, and the artifact attribute status, the version number rule for the installation disk version is determined.

[0033] Table 2

[0034] In one embodiment, Table 2 is a table showing the relationship between the pipeline and the version number rule in the sub-unit artifact. As shown in Table 2, there are three sub-unit artifacts in the pipeline, namely sub-unit 1 pipeline, sub-unit 2 pipeline and sub-unit 3 pipeline. Each sub-unit artifact contains artifact type, version number rule number, attribute status and verification test pass result, and the relationship between the version number rule of the sub-unit artifacts is determined.

[0035] Furthermore, a one-to-one mapping is established between the milestone version number and the installation disk version number, thus determining the first mapping relationship. A one-to-one mapping is then established between the version number rule number and the artifact version rule number of the installation disk version, thus determining the second mapping relationship. Finally, a one-to-one mapping is established between the artifact attribute status and the version attribute status of the installation disk version, thus determining the third mapping relationship.

[0036] Furthermore, based on the first, second, and third correspondences, a version number rule relationship table for the installation disk version is generated. And based on this table, the version number rule for the installation disk version is determined.

[0037] Furthermore, based on the product type, version number rules, and attribute status in the sub-unit product, and based on the version number rules, the installation disk version is configured one-to-one to generate the ERP installation disk version.

[0038] Table 3

[0039] In one embodiment, Table 3 is a table showing the relationship between the overall pipeline and version number rules of the ERP product. As shown in Table 3, based on the relationship between the pipeline and version number rules of each sub-unit product in Table 2, the installation disk version number of the installation disk version is matched one-to-one, the version number rule number is matched one-to-one with the product version rule number of the installation disk version, and the product attribute status of the installation disk version is matched one-to-one, and finally the ERP installation disk version is determined.

[0040] In one embodiment, Figure 2 This application provides a schematic diagram of a version number rule definition structure, as shown in the embodiment. Figure 2 As shown, the establishment of version number rules requires the use of version number rule sequence numbers in the pipeline of sub-unit artifacts. The version number rule sequence number includes the first, second, third, and fourth digits. Milestone version numbers include Snapshot, Alpha, Beta, Rc, and Release. Artifact attribute statuses include maximum number, obsolete number, and stable number. After completing the mutual configuration of each correspondence, a version number rule relationship table for the installation disk version is generated, i.e., the corresponding configurations from Table 2 to Table 3. Finally, the version number rules for the installation disk version are determined.

[0041] S105. Configure the ERP installation disk version to match the pipeline configuration, and obtain the complete ERP product installation disk.

[0042] Specifically, the ERP installation disk version is transferred to the assembly pipeline. The assembly pipeline exists within the ERP installation disk.

[0043] Furthermore, based on the version number rules of the installation disk, the ERP installation disk versions are categorized to obtain installation disk version numbers based on the ERP installation disk versions. These installation disk version numbers include both beta version numbers and official version numbers.

[0044] Furthermore, based on the installation disk version number, the ERP installation disk version is configured one-to-one to generate a complete ERP product installation disk, thereby realizing the creation of installation disks for relevant ERP products.

[0045] In a real-time example, as shown in Table 3, the ERP installation disk version is first transmitted to the assembly pipeline. Then, according to the version number rules of the installation disk version, the ERP installation disk version is classified and processed to obtain the installation disk version number based on the ERP installation disk version, including: installation disk V1.0 beta version and installation disk V1.0 official version. Then, based on the installation disk version number, the ERP installation disk version is configured one by one to generate a complete ERP product installation disk, so as to realize the creation of the installation disk of the relevant ERP product.

[0046] In addition, embodiments of this application also provide a product delivery version management device, such as... Figure 3 As shown, the Product Deliverables Version Management Device 300 specifically includes: At least one processor 301. And a memory 302 communicatively connected to the at least one processor 301. The memory 302 stores instructions executable by the at least one processor 301, enabling the at least one processor 301 to execute: Configure the version number of the relevant production line for each sub-unit corresponding to the ERP installation disk to obtain the configured sub-unit product. The sub-unit artifacts are tested and verified in an integrated environment to obtain verification information, which includes verification pass information and verification fail information. If the verification information is "verification passed", then the version number of the ERP installation disk will be identified and configured to determine the installation disk version. Based on the sub-unit artifacts, configure the relevant version number rules for the installation disk version to obtain the ERP installation disk version; Configure the ERP installation disk version to match the pipeline configuration, and obtain the complete ERP product installation disk.

[0047] This application provides a method, device, and medium for managing product deliverable versions. By configuring the version number of each sub-unit in relation to the production line, and then configuring the attribute association between the version number of the disk and the version number of each product in each sub-unit, the correct version product can be quickly and automatically selected from the production line products of each sub-unit to form a usable and complete ERP product installation disk. When a problem occurs with the installation disk, it is possible to trace back to each stage of product development based on the installation disk version number, accurately troubleshoot the fault, reduce labor costs and human error, and facilitate the production of ERP product installation disks.

[0048] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments for devices and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0049] The devices and media provided in this application are one-to-one with the methods. Therefore, the devices and media also have similar beneficial technical effects as their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0050] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0051] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0052] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0053] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0054] The foregoing has described specific embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired results. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0055] The above description is merely an embodiment of this application and is not intended to limit this application. For those skilled in the art, various modifications and variations can be made to the embodiments of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of the embodiments of this application should be included within the scope of the claims of this application.

Claims

1. A method for version management of manufactured deliverables, characterized in that, The method includes: Configure the version number of the relevant pipeline for each sub-unit corresponding to the ERP installation disk to obtain the configured sub-unit artifacts, specifically including: Identify and extract the product version information in each subunit; wherein, the product version information includes: product type, version number rule, and attribute status; Based on the product version information, the version number of each subunit is matched with the version number of the relevant production line; and based on the product type in the product version information, the version number rules and attribute status are configured accordingly to obtain the product of the subunit. The pipeline includes multiple sub-units; The sub-unit article is tested and verified in an integrated environment to obtain verification information; wherein, the verification information includes: verification pass information and verification fail information; If the verification information is a verification pass, then the version number of the ERP installation disk is identified and configured to determine the installation disk version; Identify and extract the version number rule sequence number in the sub-unit article; wherein the version number rule sequence number includes: the first digit, the second digit, the third digit, and the fourth digit; Based on the product type in the sub-unit product, the installation disk version is matched with the corresponding installation disk version number to determine the milestone version number of the installation disk version; wherein, the milestone version number includes: Snapshot, Alpha, Beta, Rc and Release; Based on the attribute status of the sub-unit artifact, the installation disk version is tested and verified for the relevant attribute status to obtain the artifact attribute status of the installation disk version; wherein, the artifact attribute status includes: maximum number and stable number; Based on the version number rule sequence number, the milestone version number, and the artifact attribute status, the version number rule for the installation disk version is determined, specifically including: The milestone version number is matched one-to-one with the installation disk version number of the installation disk version, and the first correspondence is determined. The version number rule number is matched one-to-one with the product version rule number of the installation disk version, and a second correspondence is determined. The product attribute status and the installation disk version version attribute status are mapped one-to-one, and a third mapping relationship is determined. Based on the first correspondence, the second correspondence, and the third correspondence, a version number rule relationship table for the installation disk version is generated; and based on the version number rule relationship table, the version number rule for the installation disk version is determined. Based on the sub-unit artifact, the version of the installation disk is configured according to the relevant version number rules to obtain the ERP installation disk version, specifically including: Based on the product type, version number rules, and attribute status of the sub-unit product, and based on the version number rules, the installation disk version is configured one-to-one to generate the ERP installation disk version. Configure the ERP installation disk version in the overall pipeline to obtain the complete ERP product installation disk.

2. The method for version management of manufactured goods according to claim 1, characterized in that, The sub-unit artifact is tested and verified in an integrated environment to obtain verification information; wherein, the verification information includes: verification pass information and verification fail information, specifically including: The sub-unit artifact is deployed to the integrated environment; wherein, the integrated environment is a version-based software installation environment based on the ERP installation disk version; Based on the integrated environment after deployment, the largest version corresponding to the sub-unit artifact is tested and verified to obtain the verification information; If the verification information is verification passed, then the largest version number in the sub-unit product is set to a stable state to obtain a stable state version of the sub-unit product; wherein, the sub-unit product has one and only one stable state version; If the verification information is a verification failure message, then the sub-unit product is determined to be a scrapped version.

3. The method for version management of manufactured goods according to claim 1, characterized in that, If the verification information is successful, then the ERP installation disk is configured to identify its version number, specifically including: If the verification information is verification passed, then the ERP installation disk is configured to identify the version number according to the version of the ERP product to obtain the version number information; Based on the version number information, the installation disk version of the ERP product is determined; wherein, the installation disk version includes at least: beta version and official version.

4. The method for version management of manufactured goods according to claim 1, characterized in that, Configure the ERP installation disk version in the overall pipeline to obtain the complete ERP product installation disk, specifically including: The ERP installation disk version is transferred to the assembly pipeline; wherein, the assembly pipeline exists on the ERP installation disk; According to the version number rules of the installation disk version, the ERP installation disk version is classified to obtain the installation disk version number based on the ERP installation disk version; wherein, the installation disk version number includes: beta version number and official version number; Based on the installation disk version number, the ERP installation disk version is configured one-to-one to generate the complete ERP product installation disk, thereby realizing the creation of the installation disk for the relevant ERP product.

5. A product delivery version management device, characterized in that, The device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor to enable the at least one processor to perform a product delivery version management method according to any one of claims 1-4.

6. A non-volatile computer storage medium, characterized in that, The storage medium is a non-volatile computer-readable storage medium that stores at least one program, each program including instructions that, when executed by a terminal, cause the terminal to perform a product delivery version management method according to any one of claims 1-4.

Images