CN115934086A - Blueprint and page design information sharing method, device, equipment and medium - Google Patents

Abstract

The present application provides an information sharing method, device, device, and medium for blueprint and page design. The method creates at least one design page corresponding to each element node in the design flowchart based on the page requirement information corresponding to each element node; Each of the design pages is bound to each of the corresponding element nodes, and an association relationship between each of the element nodes and each of the design pages is established, so as to realize information sharing between the page design terminal and the design flow chart. According to the page requirement information, determine and create the design page corresponding to each element node in the design flow chart, and establish the association relationship between the element node and the design page according to the corresponding relationship, so as to realize information sharing at both ends, so that the flow design end can Check the page design process in real time, and the page design end can obtain the change information of the process design end in real time, and update the page design in a timely manner, thereby improving the design efficiency from blueprint to design document.

Description

Blueprint and page design information sharing method, device, equipment and medium

technical field

The present application relates to the field of computer technology, in particular to an information sharing method, device, device and medium for blueprint and page design.

Background technique

At present, in the traditional page design method, the product manager makes a flow chart, and then the engineer makes the modeling diagram, and then develops. The industrial field is complex and has high requirements for leanness, and lean collaboration is very important, so blueprints to design documents are particularly important.

However, the traditional flow chart production method is difficult to adapt to frequent changes in requirements and complex business scenarios. At the same time, the workload of modification is also greatly increased. There are many obstacles to the collaboration between products and engineers, especially information out of sync. For larger systems, many pages, models, service flows, data integration connectors, etc. are often involved. Then, only the development engineers know which pages are used in the business flow chart, which is very unfavorable. Later maintenance.

Therefore, how to solve the low design efficiency from the blueprint to the design document has become a technical problem to be solved urgently.

Contents of the invention

The present application provides an information sharing method, device, equipment and medium for blueprint and page design, aiming at improving the design efficiency from blueprint to design document.

In the first aspect, the present application provides an information sharing method for blueprint and page design, and the information sharing method for blueprint and page design includes the following steps:

Based on the page requirement information corresponding to each element node in the design flowchart, create at least one design page corresponding to each element node;

Binding each of the design pages to the corresponding element nodes, establishing an association relationship between the element nodes and the design pages, so as to realize information sharing between the page design terminal and the design flow chart.

In the second aspect, the present application also provides an information sharing device for blueprint and page design, the information sharing device for blueprint and page design includes:

A design page creation module, configured to create at least one design page corresponding to each element node in the design flowchart based on the page requirement information corresponding to each element node;

An association relationship establishing module, configured to bind each of the design pages to the corresponding element nodes, and establish an association relationship between the element nodes and the design pages, so as to realize the connection between the page design terminal and the Information sharing for design flowcharts.

In a third aspect, the present application further provides a computer device, the computer device includes a processor, a memory, and a computer program stored on the memory and executable by the processor, wherein the computer program is executed by the When the processor executes, it realizes the steps of the information sharing method of the above-mentioned blueprint and page design.

In the fourth aspect, the present application also provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, wherein when the computer program is executed by a processor, the above-mentioned blueprint and page design information can be realized Steps of the shared method.

The present application provides an information sharing method, device, device, and medium for blueprint and page design. The method of the present application creates at least one design page corresponding to each element node in the design flow chart based on the page requirement information corresponding to each element node ;Binding each of the design pages with the corresponding element nodes, establishing the association relationship between the element nodes and the design pages, so as to realize the information sharing between the page design terminal and the design flow chart . Through the above method, according to the page requirement information, determine and create the design page corresponding to each element node in the design flowchart, and establish the association relationship between the element node and the design page according to the corresponding relationship, so as to realize information sharing at both ends, so that The process design end can view the page design process in real time, and the page design end can obtain the change information of the process design end in real time, and update the page design in time, thereby improving the design efficiency from blueprint to design document.

Description of drawings

In order to illustrate the technical solutions of the embodiments of the present application more clearly, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are some embodiments of the present application. Ordinary technicians can also obtain other drawings based on these drawings on the premise of not paying creative work.

FIG. 1 is a schematic flowchart of a first embodiment of a blueprint and page design information sharing method provided by the present application;

FIG. 2 is a schematic flowchart of a second embodiment of a blueprint and page design information sharing method provided by the present application;

FIG. 3 is a schematic structural diagram of a first embodiment of a blueprint and page design information sharing device provided by the present application;

Fig. 4 is a schematic structural block diagram of a computer device provided by an embodiment of the present application.

The realization, functional features and advantages of the present application will be further described in conjunction with the embodiments and with reference to the accompanying drawings.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.

The flow charts shown in the drawings are just illustrations, and do not necessarily include all contents and operations/steps, nor must they be performed in the order described. For example, some operations/steps can be decomposed, combined or partly combined, so the actual order of execution may be changed according to the actual situation.

Some implementations of the present application will be described in detail below in conjunction with the accompanying drawings. In the case of no conflict, the following embodiments and features in the embodiments can be combined with each other.

Embodiments of the present application provide a blueprint and page design information sharing method, device, device, and storage medium, which are used to determine and create a design page corresponding to each element node in the design flow chart according to the page requirement information, and according to The corresponding relationship establishes the relationship between the element node and the design page, so as to realize the information sharing between the two ends, so that the process design end can view the page design process in real time, and the page design end can obtain the change information of the process design end in real time, and carry out page design in time Updated to improve design efficiency from blueprints to design documents.

Please refer to FIG. 1 . FIG. 1 is a schematic flowchart of a first embodiment of a blueprint and page design information sharing method provided by the present application.

As shown in FIG. 1 , the method for sharing blueprint and page design information includes steps S101 to S102.

Step S101, based on the page requirement information corresponding to each element node in the design flowchart, create at least one design page corresponding to each element node;

In this embodiment, the product demand side can draw a design flowchart according to the product requirements, and the engineer can create a page that can meet the page requirements according to the page requirement information in each element node in the design flowchart.

In an embodiment, the design flowchart may be composed of element nodes and connecting lines, wherein the element nodes are related tasks of man-machine loop testing and may include information of multiple dimensions. Connectors are used to orchestrate the relationship and flow between element nodes.

In an embodiment, each element node can correspond to at least one design page. For example, the page requirement information in the element node is relatively small, and there is only one login interface, so only one design page is required, or the login interface also includes a registration interface. , it may include two design pages, that is, the element node corresponds to two design pages.

In an embodiment, the generation of the design flow chart may be performed by arranging the blueprint interface in the form of a graphic flow; it may also be arranging in the form of a text description.

Step S102, binding each of the design pages to the corresponding element nodes, establishing the association relationship between the element nodes and the design pages, so as to realize the connection between the page design end and the design flow chart Information Sharing.

In this embodiment, for the page design end and the product demand end, the association and information sharing between the two ends can be realized by binding the design flow chart and the design page.

In one embodiment, in the process of product production and application, the demand for the product will change according to the actual scene, so in the actual application process, it is necessary to update the product page in real time according to the actual demand, at this time , the product demand side needs to change the product demand information, and tell the page design side to make corresponding page changes or even redesign. Therefore, through information sharing at both ends, the real-time update of the page design can be realized and the efficiency of the page design can be improved.

In one embodiment, when there is an information change in the page requirement information corresponding to each element node in the design flowchart, based on the association relationship between each element node and each design page, it is marked that there is an information change Determine the page to be changed based on the design page corresponding to the element node; update the business flow chart based on the change of the page requirement information, and send page update information to the page design end to remind the page design end Redesign the page to be changed.

In one embodiment, when the product demand side needs to change the page demand information, you can click on a specific element node in the design flow chart to redesign or change the page corresponding to the element node, so as to avoid modifying the entire design process. The diagram and all corresponding pages are redesigned to improve design efficiency.

In an embodiment, the element node that needs to be changed can be marked through the association relationship between the element node and the design page, and then the design page corresponding to the element node can be marked.

In an embodiment, the marking method may be color distinction, such as highlighting the element node to be changed in yellow or red; it may also be marking display, such as marking a prominent icon to indicate the change.

In one embodiment, after the change of the design flow chart and page design is completed, the changed design flow chart and page design are re-saved, a new version of the page is generated, and the design flow chart and design page of the old version are retained, and a Compare the tables, mark the design pages and design flowcharts of different versions in the table, and mark the differences between different versions to facilitate design traceability.

In one embodiment, when it is necessary to view the design process of the design page, click the element node to be checked in the design flow chart, and jump to the page design terminal corresponding to the element node based on the association relationship, to view the design progress of at least one design page in the page design terminal.

In one embodiment, each element node is associated with the corresponding design page, and the blueprint design interface can display information such as the page number and status corresponding to each element node, and you can also click on the element node to jump to the design page and view each element The page design process corresponding to the node.

In one embodiment, the viewing authority can be set, and only project-related personnel are allowed to view the design flow chart and design page, as well as the authority to jump to view. For example, for the product demand side, only blueprint design, modification, and design page The view authority does not have the authority to change the design page; for the page design side, it can have the authority to view the design flow chart and the authority to design the page, but does not have the authority to change the design flow chart.

In one embodiment, the blueprint design and page design may include a log recording and viewing section, recording the historical versions of the blueprint design and page design and the operator.

In one embodiment, a reminder section can be set, and when information changes on the product demand end or the design progress of the page design end are monitored, a reminder message can be generated to remind the page designer to update the page in time, or notify the product demand end page design process.

Please refer to FIG. 2 . FIG. 2 is a schematic flowchart of a second embodiment of a blueprint and page design information sharing method provided by the present application.

In this embodiment, based on the embodiment shown in FIG. 1 above, before the step S101, it also includes:

Step S201, obtaining an element node library, which includes historical element nodes;

In this embodiment, by obtaining the historical design flow chart, the historical element nodes in the historical design flow chart can be extracted, and the element node library can be established, so that the product demand personnel can directly search the historical element nodes for flow chart design, avoiding repeated design work , improve the efficiency of flow chart design.

In one embodiment, a design page library can be established based on historical design pages, so that the page design end can directly extract the historical pages for use or modification, reduce the workload of page design, and improve the efficiency of page design.

Step S202. Based on the page requirement information, search for the matching historical element node in the element node library to obtain a target element node;

In this embodiment, the page requirement information can be searched in the element node library to find out whether there is the same or similar historical element node in the element node library. If it exists, the historical element node can be directly extracted as the corresponding page requirement information. , the target element node.

In an embodiment, the same page requirement information may correspond to one element node, or may correspond to multiple element nodes.

In one embodiment, based on the page requirement information, at least one page design keyword is extracted; based on the keyword matching algorithm and the at least one page design keyword, search for elements related to each of the page design keywords in the element node library For the historical element nodes whose keywords match, obtain at least one similar historical element node; based on the matching degree of each similar historical element node and the page design keyword, determine the similar historical element node with the highest matching degree as the The target element node.

In an embodiment, the page requirement information can be split, keywords can be extracted, and the element node library can be searched through keywords to make the search results more accurate.

In an embodiment, a keyword extraction model may be trained according to the page requirement information data and related field data in the historical element nodes, for extracting keywords in the page requirement information.

In one embodiment, the keyword extraction model may be a TF-IDF (term frequency-inverse document frequency) algorithm model, which is a commonly used weighting technique for information retrieval and information mining. A statistical method for assessing the importance of a word to a collection of documents or to a document in a corpus. It can also be an extractive text summary TextRank algorithm model. The TextRank algorithm is an algorithm based on graph sorting. Its basic idea comes from Google's PageRank algorithm. By dividing the text into several components (words or phrases or sentences) and establishing The graphical model uses the voting mechanism to sort the importance of the text, and only uses the information of a single document itself to realize keyword extraction and abstract.

In an embodiment, the keyword matching algorithm may be traversal matching, such as KMP algorithm, Brute-Force algorithm, etc.; it may also be a regular expression method to realize keyword matching.

It can be understood that the keyword extraction model and keyword extraction algorithm provided in this embodiment are only for illustration, and are not limited to the above-mentioned keyword extraction model and keyword The matching algorithm, other keyword extraction models and keyword matching algorithms that can be used to implement the embodiments of the present application should also be within the protection scope of the embodiments of the present application.

In an embodiment, when there are multiple keywords, they can be searched separately or at the same time, so as to find the corresponding historical element nodes. Separate retrieval can match more historical element nodes, while simultaneous retrieval can retrieve historical element nodes that are closer to the information required by the current page.

In an embodiment, because the same page requirement information may need to be realized by multiple pages, or there are multiple parallel requirements in the page requirement, when there are multiple historical element nodes, the historical element node with the highest matching degree can be selected , you can also select multiple historical element nodes at the same time.

In one embodiment, when the historical element node matching the page requirement information is not found in the element node library, the page requirement information is used as the target element node and entered into the element in the node library.

In one embodiment, when no historical element node matching the page requirement information is found in the element node database, the page requirement information is a brand new product requirement, and at this time, it can be edited by text description or illustration Create a new process design diagram, and enter the process design diagram and its element nodes into the database as a new historical use case.

Step S203, sort the target element nodes based on the order of the page design process, and generate the design flow chart.

In this embodiment, each element node in the page design process has an implementation order, that is, there is a logical relationship in the page display, so the order of the page design process is also included in the page requirement information, so it can be based on the order of the page design process in the page requirement information , sort the target element nodes of each step in the page requirement information, and generate a design flow chart. There are many possibilities in the element node. At this time, the element node includes the current page and there are multiple jump buttons in the current page, and the corresponding jump button points to the target page, and the sequence of the element nodes corresponding to the target page is arranged After the current element node.

Please refer to FIG. 3. FIG. 3 is a schematic structural diagram of a first embodiment of a blueprint and page design information sharing device provided by the present application. The blueprint and page design information sharing device is used to execute the aforementioned blueprint and page design information Share method. Wherein, the information sharing device of the blueprint and page design can be configured in the server.

As shown in FIG. 3 , the blueprint and page design information sharing device 200 includes: a design page creation module 201 and an association relationship establishment module 202 .

Design page creation module 201, configured to create at least one design page corresponding to each element node in the design flowchart based on the page requirement information corresponding to each element node;

An association relationship establishing module 202, configured to bind each of the design pages to the corresponding element nodes, and establish an association relationship between the element nodes and the design pages, so as to realize the connection between the page design end and the design pages. Information sharing for design flow charts.

In one embodiment, the blueprint and page design information sharing device 300 further includes a page-to-be-changed marking module, configured to, when there is information change in the page requirement information corresponding to each element node in the design flow chart, based on The association relationship between each element node and each design page, marking the design page corresponding to the element node with information change, and determining the page to be changed;

In one embodiment, the blueprint and page design information sharing device 300 further includes an information change reminder module, which is used to update the business flow chart based on the change of the page requirement information, and send page update information to the The page designer is configured to remind the page designer to redesign the page to be changed.

In one embodiment, the blueprint and page design information sharing device 300 further includes a design flow chart generation module for obtaining an element node library, which includes historical element nodes; based on the page requirement information, Searching for the matching historical element nodes in the element node library to obtain target element nodes; sorting the target element nodes based on the sequence of the page design process to generate the design flow chart.

In one embodiment, the design flowchart generation module is further configured to extract at least one page design keyword based on the page requirement information; based on the keyword matching algorithm and the at least one page design keyword, in the Searching the historical element nodes that match each of the page design keywords in the element node library to obtain at least one similar historical element node; based on the matching degree of each similar historical element node and the page design keyword, determine the matching The similar historical element node with the highest degree is used as the target element node.

In one embodiment, the design flow chart generating module is further configured to use the page requirement information as The target element node is entered into the element node library.

In one embodiment, the blueprint and page design information sharing device 300 further includes a page design process check module, which is used to click on the element to be checked in the design flow chart when viewing the design process of the design page The node jumps to the page design terminal corresponding to the element node based on the association relationship, so as to check the design process of at least one design page in the page design terminal.

It should be noted that those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working process of the above-described devices and modules can refer to the above-mentioned embodiment of the information sharing method for blueprint and page design The corresponding process will not be repeated here.

The apparatus provided in the foregoing embodiments may be implemented in the form of a computer program, and the computer program may run on a computer device as shown in FIG. 4 .

Referring to FIG. 4 , FIG. 4 is a schematic structural block diagram of a computer device provided by an embodiment of the present application. The computer device may be a server.

Referring to FIG. 4 , the computer device includes a processor, a memory, and a network interface connected through a system bus, wherein the memory may include a non-volatile storage medium and an internal memory.

Non-volatile storage media can store operating systems and computer programs. The computer program includes program instructions. When the program instructions are executed, the processor can be executed to execute any information sharing method for blueprint and page design.

The processor is used to provide computing and control capabilities and support the operation of the entire computer equipment.

The internal memory provides an environment for running the computer program in the non-volatile storage medium. When the computer program is executed by the processor, the processor can execute any information sharing method for blueprint and page design.

This network interface is used for network communication, such as sending assigned tasks, etc. Those skilled in the art can understand that the structure shown in Figure 4 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation to the computer equipment on which the solution of the application is applied. The specific computer equipment can be More or fewer components than shown in the figures may be included, or some components may be combined, or have a different arrangement of components.

It should be understood that the processor may be a central processing unit (Central Processing Unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), on-site Programmable gate array (Field-Programmable GateArray, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Wherein, the general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

Wherein, in one embodiment, the processor is used to run a computer program stored in the memory to implement the following steps:

Based on the page requirement information corresponding to each element node in the design flowchart, create at least one design page corresponding to each element node;

Binding each of the design pages to the corresponding element nodes, establishing an association relationship between the element nodes and the design pages, so as to realize information sharing between the page design terminal and the design flow chart.

In one embodiment, after the processor implements the binding of each of the design pages to the corresponding element nodes, and establishes the association between the element nodes and the design pages, Also used to implement:

When there is an information change in the page requirement information corresponding to each element node in the design flowchart, based on the association relationship between each element node and each design page, mark the corresponding element node corresponding to the information change design page, determine the page to be changed;

Based on the change of the page requirement information, the business flow chart is updated, and page update information is sent to the page designer to remind the page designer to redesign the page to be changed.

In one embodiment, before the processor implements the page requirement information corresponding to each element node in the design flowchart, before creating the design page corresponding to each element node, the processor is further configured to:

Obtaining an element node library, the element node library includes historical element nodes;

Based on the page requirement information, search for the matching historical element node in the element node library to obtain a target element node;

Based on the order of the page design process, the target element nodes are sorted to generate the design flow chart.

In one embodiment, when the processor realizes the searching for the matching historical element node in the element node library based on the page requirement information to obtain the target element node, it is used to realize:

Extracting at least one page design keyword based on the page requirement information;

Based on a keyword matching algorithm and the at least one page design keyword, searching the element node library for the historical element nodes matching each of the page design keywords to obtain at least one similar historical element node;

Based on the matching degree of each similar historical element node and the page design keyword, the similar historical element node with the highest matching degree is determined as the target element node.

In one embodiment, when the processor realizes the searching for the matched historical element node in the element node library based on the page requirement information to obtain the target element node, it is further configured to:

When the historical element node matching the page requirement information is not found in the element node library, the page requirement information is used as the target element node and entered into the element node library.

In one embodiment, the processor implements the binding of each of the design pages to the corresponding element nodes, and establishes the association relationship between the element nodes and the design pages. Afterwards, also used to implement:

When it is necessary to view the design process of the design page, click the element node to be checked in the design flow chart, and based on the association relationship, jump to the page design terminal corresponding to the element node to view the page design The design process of at least one design page in the terminal.

Embodiments of the present application also provide a computer-readable storage medium, the computer-readable storage medium stores a computer program, the computer program includes program instructions, and the processor executes the program instructions to implement the present application. Any blueprint and page design information sharing method provided by the embodiment.

Wherein, the computer-readable storage medium may be an internal storage unit of the computer device described in the foregoing embodiments, such as a hard disk or a memory of the computer device. The computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk equipped on the computer device, a smart memory card (SmartMediaCard, SMC), a secure digital (SecureDigital, SD) card, Flash card (FlashCard), etc.

The above is only a specific embodiment of the application, but the scope of protection of the application is not limited thereto. Any person familiar with the technical field can easily think of various equivalents within the scope of the technology disclosed in the application. Modifications or replacements, these modifications or replacements shall be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (10)

1. A blueprint and page design information sharing method is characterized in that the blueprint to design document implementation method comprises the following steps:

based on page demand information corresponding to each element node in the design flow chart, creating at least one design page corresponding to each element node;

and binding each design page with the corresponding element node, and establishing an association relation between each element node and each design page so as to realize information sharing between a page design end and the design flow chart.

2. The method for information sharing between blueprint and page design according to claim 1, wherein after the binding of each design page with the corresponding element nodes and the establishment of the association relationship between each element node and each design page, further comprising:

when the page demand information corresponding to each element node in the design flow chart has information change, marking a design page corresponding to the element node having information change based on the incidence relation between each element node and each design page, and determining a page to be changed;

and updating the business flow chart based on the change of the page demand information, and sending page updating information to the page design end to remind the page design end of redesigning the page to be changed.

3. The method for sharing information of blueprint and page design according to claim 1, wherein before creating the design page corresponding to each element node based on the page requirement information corresponding to each element node in the design flowchart, the method further comprises:

acquiring an element node library, wherein the element node library comprises historical element nodes;

searching the matched historical element nodes in the element node library based on the page demand information to obtain target element nodes;

and sequencing the target element nodes based on the page design flow sequence to generate the design flow chart.

4. The method for information sharing between blueprint and page design according to claim 3, wherein the searching the element node library for the matched historical element node based on the page requirement information to obtain a target element node comprises:

extracting at least one page design keyword based on the page demand information;

searching the historical element nodes matched with the page design keywords in the element node library based on a keyword matching algorithm and the at least one page design keyword to obtain at least one similar historical element node;

and determining the similar history element node with the highest matching degree as the target element node based on the matching degree of each similar history element node and the page design keyword.

5. The method for information sharing of blueprint and page design according to claim 3, wherein the searching the element node library for the matched historical element node based on the page requirement information to obtain a target element node further comprises:

and when the historical element nodes matched with the page requirement information are not searched in the element node library, taking the page requirement information as the target element nodes and inputting the target element nodes into the element node library.

6. The information sharing method for blueprint and page design according to any one of claims 1 to 5, wherein after the binding of each design page with the corresponding element nodes and the establishment of the association relationship between the element nodes and the design pages, the method further comprises:

and when the design process of the design page needs to be checked, clicking the element node to be checked in the design flow chart, and jumping to a page design end corresponding to the element node based on the association relation so as to check the design process of at least one design page in the page design end.

7. An information sharing device of blueprint and page design, characterized in that the information sharing device of blueprint and page design comprises:

the design page creating module is used for creating at least one design page corresponding to each element node based on page demand information corresponding to each element node in the design flow chart;

and the incidence relation establishing module is used for binding each design page with each corresponding element node and establishing the incidence relation between each element node and each design page so as to realize the information sharing between a page design end and the design flow chart.

8. The blueprint and page design information sharing device according to claim 7, wherein the blueprint and page design information sharing device further comprises:

a to-be-changed page marking module, configured to mark, when there is an information change in the page requirement information corresponding to each element node in the design flow diagram, a design page corresponding to the element node in which the information change exists based on an association relationship between each element node and each design page, and determine a page to be changed;

and the information change reminding module is used for updating the business flow chart based on the change of the page requirement information and sending page updating information to the page design end so as to remind the page design end to redesign the page to be changed.

9. A computer arrangement comprising a processor, a memory, and a computer program stored on the memory and executable by the processor, wherein the computer program, when executed by the processor, carries out the steps of the blueprint and page design information sharing method according to any one of claims 1 to 6.

10. A computer-readable storage medium, having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the steps of the information sharing method of blueprint and page design according to any of claims 1 to 6.

Images