Support device, support method, and program

Abstract

To provide a support device and the like capable of appropriately inspecting transition between pages including design of a UI element causing the transition.SOLUTION: In a support device 300, a collection unit 351 collects transition information that is information for transition from each page constituting a web site to another page and includes a path of a transition destination page and a UI element causing the transition. In addition, an output unit 352 classifies the UI element included in transition information collected by the collection unit 351 into a group according to a path of the transition destination page and outputs the same.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present invention relates to an assistance device, an assistance method, and a program. [Background technology]

[0002] With the spread of the Internet, various services are provided from various websites. For example, a betting service that allows users to purchase betting tickets for public races such as bicycle racing, horse racing, and boat racing from their terminal devices via the Internet is also known. In such a voting service, for example, a user starts from the home screen (root page) of the website, sequentially views each page such as an information screen, a voting screen, and a purchase screen, and performs the necessary operations to purchase the desired voting ticket. Therefore, voting service providers regularly test their websites to ensure that transitions between pages work as designed.

[0003] For example, Patent Document 1 discloses an invention of a test support device that supports testing of websites. The test support device disclosed in Patent Document 1 is capable of displaying a site map including a plurality of nodes each representing a plurality of pages, and a plurality of edges each representing a transition between the plurality of pages. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 7093144 Summary of the Invention [Problem to be solved by the invention]

[0005] In the invention described in Patent Document 1, the displayed site map makes it possible to check whether the transitions between pages on a website are as designed. However, while the invention of Patent Document 1 can inspect transitions between pages, it cannot properly inspect how UI (User Interface) elements that cause the transitions (such as linked buttons, banners, text, etc.) are designed. For example, in a voting service or the like, the design of UI elements for transitioning to the same destination page (such as a voting screen) is required to be the same or similar on each source page. This is because if the designs of UI elements transitioning to the same destination on each source page are different, not only will the overall sense of unity be lost, but it may also cause problems such as making the user feel uncomfortable and hindering smooth operation.

[0006] Therefore, there was a need for technology that could not only check whether transitions between pages were as designed, but also properly inspect the design of the UI elements that cause the transitions.

[0007] The present invention has been made in consideration of the above-mentioned situation, and aims to provide an assistance device, an assistance method, and a program that can properly inspect transitions between pages, including the design of UI elements that cause the transitions. [Means for solving the problem]

[0008] The support device according to a first aspect of the present invention comprises: A collection unit that collects transition information, which is information for transitioning from each page constituting a website to another page, and includes a path of the transition destination page and a UI element that causes the transition; an output unit that classifies the UI elements included in the transition information collected by the collection unit into groups according to paths of the transition destination pages and outputs the UI elements; The present invention is characterized by comprising:

[0009] In addition, in the support device according to the above aspect, The collection unit may sequentially trace the transition destination pages starting from a root page of the website, and collect only the transition information in which the path of the transition destination page is within the website.

[0010] In addition, in the support device according to the above aspect, The collection unit further collects related information for representing an appearance of the UI element; The output unit may output the associated information together with an appearance of the UI element according to the associated information.

[0011] In addition, the support device according to the above aspect includes: a storage unit that stores the transition information collected by the collection unit in association with a path of a transition source page, The output unit may generate and output a transition diagram between pages within the website based on the path of the transition source page stored in the storage unit and the transition information.

[0012] In addition, the support device according to the above aspect includes: a reception unit that receives a selection of any page in the transition diagram output by the output unit, The collection unit further collects related information for representing an appearance of the UI element; The output unit may output a list showing appearances of the UI elements in a group corresponding to a page path accepted by the acceptance unit, in accordance with the association information.

[0013] A support method according to a second aspect of the present invention comprises: An assistance method executed by an assistance device, A collection step of collecting transition information, which is information for transitioning from each page constituting the website to another page, and includes a path of the transition destination page and a UI element that causes the transition; an output step of classifying the UI elements included in the transition information collected in the collection step into groups according to paths of the transition destination pages and outputting the UI elements; The present invention is characterized by comprising:

[0014] A program according to a third aspect of the present invention comprises: On the computer, a collection step of collecting transition information, which is information for transitioning from each page constituting the website to another page, and includes a path of the transition destination page and a UI element that causes the transition; an output step of classifying the UI elements included in the transition information collected in the collection step into groups according to paths of the transition destination pages and outputting the UI elements; The present invention is characterized in that the above-mentioned is executed.

[0015] The above program may be distributed or sold via a computer communication network independently of the computer on which the program is executed. Furthermore, the information recording medium on which the above-mentioned program is recorded is a non-transitory recording medium, and can be distributed and sold independently of a computer. Here, the non-transitory recording medium refers to a tangible recording medium. Examples of non-transitory recording media include compact discs, flexible disks, hard disks, magneto-optical disks, digital video disks, magnetic tapes, and semiconductor memories. Also, the transitory recording medium refers to the transmission medium (propagation signal) itself. Examples of the transitory recording medium include electrical signals, optical signals, and electromagnetic waves. In addition, the temporary storage area refers to an area for temporarily storing data and programs, and is, for example, a volatile memory such as a RAM (Random Access Memory). Effect of the Invention

[0016] According to the present invention, it is possible to appropriately check transitions between pages, including the design of UI elements that cause the transitions. [Brief description of the drawings]

[0017] [Figure 1]1 is a block diagram showing an example of the overall configuration of an inspection system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a schematic diagram showing an example of each page constituting a website of a sales server. [Diagram 3] 1 is a block diagram showing an example of a schematic configuration of a typical information processing device in which a support device or the like according to an embodiment of the present invention is realized. [Figure 4] FIG. 2 is a block diagram showing an example of a functional configuration of the support device according to the present embodiment. [Diagram 5] 11 is a schematic diagram illustrating an example of transition management information stored in a storage unit. FIG. [Figure 6] FIG. 11 is a schematic diagram for explaining transition information in HTML data. [Figure 7] FIG. 2 is a schematic diagram for explaining related information in CSS data. [Figure 8] FIG. 13 is a schematic diagram showing an example of a transition diagram. [Figure 9] FIG. 13 is a schematic diagram showing an example of a list. [Figure 10] 10 is a flowchart illustrating a support process according to the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] An embodiment of the present invention will be described below. In the embodiment of the present invention, an inspection system for inspecting the website of a sales server that sells betting tickets for public races will be described, but the website to be inspected can be any website, and the present invention can be similarly applied to inspection systems that inspect other websites that sell products or provide various services. In other words, the following embodiments are for illustrative purposes only and do not limit the scope of the present invention. Therefore, a person skilled in the art can adopt embodiments in which each or all of these elements are replaced with equivalents, and these embodiments are also included in the scope of the present invention.

[0019] (Overall composition) An inspection system 100 according to an embodiment of the present invention is, as an example, a system for inspecting a website that sells betting tickets for public races, and as shown in Fig. 1, includes a sales server 200 and a support device 300. The sales server 200 and the support device 300 are connected to each other via the Internet 900 so as to be able to communicate with each other. Although omitted in FIG. 1, the organizer server that organizes the public race and the terminal device of the user who wishes to purchase a betting ticket are also connected so as to be able to communicate with the sales server 200 via the Internet 900.

[0020] The sales server 200 is, for example, a server computer or the like, and publishes a website on the Internet 900 for selling betting tickets. For example, the sales server 200 publishes a website consisting of pages (screens) such as those shown in FIG. 2 so that it can be viewed from a terminal device (terminal device of a user who wishes to purchase a betting ticket) not shown. Figure 2 includes, for example, a home screen (route page) for the user to select each race for which voting is available, an information screen for informing the user of various information regarding each voting target (each runner, etc.) running in the selected race, a voting screen for the user to select any voting target and cast a vote, and a purchase screen for the user to finalize the vote and purchase a voting ticket. Each of these pages includes UI elements (details of which will be described later) that transition to other pages, and transitions between pages are performed according to user operations on the UI elements.

[0021] 1, the support device 300 is, for example, a personal computer or the like, and supports the inspection of a website published by the sales server 200. Note that the support device 300 is used, for example, by an operator who inspects the website. For example, the support device 300 accesses the sales server 200 via the Internet 900 in accordance with instructions from an operator, collects transition information (described later) from each page constituting a website as shown in Fig. 2, and outputs a transition diagram that visualizes the connections between pages. The support device 300 also collects related information (described later) from each page, and outputs a list that allows comparison of the appearances of UI elements that cause transitions.

[0022] (General configuration of information processing device) A typical information processing device 400 in which the support device 300 according to this embodiment is realized will be described.

[0023] As shown in FIG. 3, the information processing device 400 includes a CPU (Central Processing Unit) 401, a ROM (Read Only Memory) 402, a RAM (Random Access Memory) 403, a NIC (Network Interface Card) 404, an image processing unit 405, an audio processing unit 406, an auxiliary memory unit 407, an interface 408, an operation unit 409, a display unit 410, and a speaker 411.

[0024] A CPU 401 controls the overall operation of the information processing device 400, and is connected to each component to exchange control signals and data.

[0025] The ROM 402 stores an IPL (Initial Program Loader) that is executed immediately after power is turned on. When this IPL is executed, a program stored in the auxiliary memory unit 407 is read into the RAM 403 and execution of the program by the CPU 401 begins.

[0026] The RAM 403 is for temporarily storing data and programs, and holds programs and data read from the auxiliary storage unit 407, as well as other data necessary for communication.

[0027] The NIC 404 is used to connect the information processing device 400 to a computer communication network such as the Internet, and may be configured as a 10BASE-T / 100BASE-T standard used in constructing a LAN (Local Area Network), an analog modem for connecting to the Internet using a telephone line, an ISDN (Integrated Services Digital Network) modem, an ADSL (Asymmetric Digital Subscriber Line) modem, a cable modem for connecting to the Internet using a cable television line, or the like.

[0028] The image processing unit 405 processes image data read from the auxiliary storage unit 407 or the like using an image calculation processor (not shown) provided in the CPU 401 or the image processing unit 405, and then records the processed image data in a frame memory (not shown) provided in the image processing unit 405. The image information recorded in the frame memory is converted into a video signal at a predetermined synchronous timing, and is output to the display unit 410 via the interface 408 or the like. In other words, under the control of the CPU 401, the image processing unit 405 generates images required in the progress of processing performed by the information processing device 400, and causes the display unit 410 to display the images.

[0029] The audio processing unit 406 converts audio data read from the auxiliary storage unit 407 or the like into an audio signal, and outputs the audio signal to the speaker 411 via the interface 408. In other words, under the control of the CPU 401, the audio processing unit 406 generates audio to be generated during the progress of processing performed by the information processing device 400, and outputs the audio from the speaker 411.

[0030] The auxiliary storage unit 407 is a hard disk or the like, and stores various programs and various data necessary for controlling the operation of the entire information processing device 400. For example, the auxiliary storage unit 407 stores a program for realizing the support device 300 according to this embodiment. Then, under the control of the CPU 401, the auxiliary storage unit 407 appropriately reads out the stored programs and data, and temporarily stores them in the RAM 403 or the like.

[0031] An operation unit 409, a display unit 410, and a speaker 411 are connected to the interface 408. Note that the interface 408 may also transmit and receive necessary information to and from other connected external devices.

[0032] The operation unit 409 is, for example, a button or a touch panel (touch screen), and receives operation inputs from a user who uses the information processing device 400.

[0033] The display unit 410 is, for example, a liquid crystal display panel, which renders an image according to the image data output by the image processing unit 405 and presents the image to the user of the information processing device 400.

[0034] The speaker 411 outputs a sound corresponding to the audio data output by the audio processing unit 406 and presents it to the user of the information processing device 400 .

[0035] Additionally, the information processing device 400 may include a drive unit such as a DVD (Digital Versatile Disc)-ROM instead of the auxiliary storage unit 407. In this case, the information processing device 400 reads out programs and data from a DVD-ROM or the like that is loaded into the drive unit, and operates in the same manner as described above.

[0036] Hereinafter, the functional configuration of the support device 300 realized by the above-mentioned information processing device 400 will be described with reference to Fig. 4 to Fig. 9. When the information processing device 400 is powered on, a program that causes the information processing device 400 to function as the support device 300 is executed, and the support device 300 according to this embodiment is realized. The sales server 200 is also realized by an information processing device 400, but a description thereof will be omitted and the support device 300, which is the most characteristic feature of this embodiment, will be described below.

[0037] (Functional configuration of the support device 300) 4 is a block diagram showing an example of a functional configuration of the support device 300 according to this embodiment. As shown in the figure, the support device 300 includes a communication unit 310, a reception unit 320, a display unit 330, a storage unit 340, and a control unit 350.

[0038] The communication unit 310 transmits and receives necessary information to and from the sales server 200 . For example, the communication unit 310 accesses the website of the sales server 200 and receives data of each page. That is, the communication unit 310 receives HTML (Hyper Text Markup Language) data, CSS (Cascading Style Sheets) data, image data, Script data, and the like that constitute each page as shown in FIG. 2 described above.

[0039] The above-mentioned NIC 404 or the like can function as such a communication unit 310.

[0040] The reception unit 320 receives various operations from an operator who inspects a website. For example, the receiving unit 320 receives, through an operation by an operator, a path (for example, a URL; Uniform Resource Locator) indicating the root page of a website to be inspected.

[0041] The above-mentioned operation unit 409 can function as such a reception unit 320.

[0042] The display unit 330 displays various information to an operator inspecting a website. For example, the display unit 330 displays a transition diagram, a list, etc. output by the control unit 350 (output unit 352, described later). The transition diagram and the list will be described in detail later.

[0043] The above-mentioned display unit 410 can function as such a display section 330.

[0044] The storage unit 340 stores various information required when checking a website. For example, the storage unit 340 stores transition management information 341 in which the transition information collected by the control unit 350 (collection unit 351 described later) is associated with the path of the transition source page. Specifically, the storage unit 340 stores the transition management information 341 as shown in FIG. 5.

[0045] The transition management information 341 shown in FIG. 5 includes, as an example, a transition source path 341a, a transition destination path 341b, a UI element 341c, and related information 341d. The transition source path 341a indicates the path of a transition source page including transition information and the like. The transition destination path 341b indicates the path of a transition destination page defined in the transition information. The UI element is an Anchor Tag (a tag) or the like that causes a transition. The UI element may be an input tag (input tag) of a submit type surrounded by form tags (form tags). The related information 341d is CSS data or image data for expressing the appearance of the UI element.

[0046] In addition, storage unit 340 also stores HTML data that constitutes each page. The above-mentioned auxiliary storage unit 407 or the like can function as such a storage unit 340.

[0047] 4, the control unit 350 controls the entire support device 300. The control unit 350 includes a collection unit 351 and an output unit 352.

[0048] The collection unit 351 collects transition information for transitioning from each page constituting a website to another page. For example, the collection unit 351 collects transition information including a path of a transition destination page and UI elements from HTML data constituting each page.

[0049] Specifically, the collection unit 351 collects the transition information TG1 and TG2 from HTML data as shown in FIG. The transition information TG1 is information including an a tag, and the transition information TG2 is information including a submit type input tag enclosed in form tags. When the receiving unit 320 receives a path of a root page of a website to be inspected, the collecting unit 351 traces each page starting from the root page, and collects only transition information whose path to a transition destination page is within the website. In other words, the collecting unit 351 collects transition information within the website, but does not collect transition information to outside the website.

[0050] The collection unit 351 also collects related information for expressing the appearance of the UI elements from CSS data and the like. Specifically, the collection unit 351 collects the related information SS1 and SS2 from the CSS data as shown in FIG. The related information SS1 is information that defines the design of the button (XXXbnt) in the transition information TG1 in Fig. 6. The related information SS2 is information that defines the design of the button (YYYbnt) in the transition information TG2 in Fig. 6. In addition, when image data such as a banner is included in the transition information, the collection unit 351 also collects the image data as related information. Then, when the collection unit 351 collects the transition information and related information, it associates them with the path of the transition source page, and stores them in the storage unit 340 as the transition management information 341 shown in FIG.

[0051] Returning to FIG. 4, the output unit 352 outputs a transition diagram that visualizes the connections between pages in the website, and a list that allows comparison of the appearances of UI elements that cause the transitions. The output unit 352 includes the generation unit 353, and outputs the transition diagram and list generated by the generation unit 353. By outputting the list, the output unit 352 classifies UI elements included in the transition information collected by the collection unit 351 into groups according to the paths of the transition destination pages and outputs the classified UI elements.

[0052] For example, the generation unit 353 generates a transition diagram as shown in Fig. 8 based on the transition management information 341 stored in the storage unit 340. This transition diagram shows the connections between pages in the website to be inspected. In other words, the generation unit 353 generates a transition diagram that shows how transitions between pages are made starting from the root page RP. 8 is output by the output unit 352, and displayed on the display unit 330. This enables the operator to check whether the transitions between pages on the website are as designed.

[0053] Furthermore, when a page (screen) in the transition diagram is selected by the operator, the generating unit 353 generates a list showing the appearance of UI elements that transition to that page. For example, as shown in Fig. 9, when a page Pn is selected by the cursor CR, the generating unit 353 generates a list LT. In this list LT, the appearances of UI elements that transition to page Pn are arranged in association with the path of the transition source page. That is, the generating unit 353 extracts records whose transition destination path 341b is the path of page Pn from the transition management information 341 shown in Fig. 5, groups them, and generates the list LT by drawing the appearances of UI elements 341c of the group based on the related information 341d, etc. 9, and displays it on the display unit 330. Therefore, the operator can use the list LT to check the appearance of the UI element that causes the transition.

[0054] The above-mentioned CPU 401, image processing unit 405, and the like can function as the control unit 350 having such a configuration.

[0055] (Operation of the support device 300) The operation of the support device 300 having such a configuration will be described below with reference to Fig. 10. Fig. 10 is a flowchart showing the flow of the support process executed by the support device 300. This support process is started, for example, when the worker operating the support device 300 inputs the root page of the website to be inspected.

[0056] The support device 300 receives the root page (step S11). That is, the receiving unit 320 receives a path (for example, a URL) indicating the root page of the website to be checked.

[0057] The support device 300 reads the data of the root page (step S12). That is, the control unit 350 controls the communication unit 310 to read the HTML data, CSS data, image data, Script data, and the like that constitute the root page.

[0058] The support device 300 determines whether or not there is transition information in the data of the root page (step S13). For example, the collection unit 351 determines whether or not transition information such as the transition information TG1, TG2, etc. is included in the HTML data as shown in FIG.

[0059] When the support device 300 determines that there is no transition information (step S13; No), the support device 300 advances the process to step S16, which will be described later.

[0060] On the other hand, when it is determined that there is transition information (step S13; Yes), the support device 300 determines whether the transition destination is within the site or not (step S14). For example, the collection unit 351 determines whether or not the transition destination pages in the transition information such as the transition information TG1, TG2, etc. shown in FIG. 6 are within the same website.

[0061] When the support device 300 determines that the transition destination is not within the site (step S14; No), the support device 300 advances the process to step S16, which will be described later.

[0062] On the other hand, when it is determined that the transition destination is within the site (step S14; Yes), the support device 300 collects and stores transition information and the like (step S15). That is, the collection unit 351 collects transition information TG1, TG2 from HTML data such as that shown in FIG. 6, and also collects related information SS1, SS2 from CSS data such as that shown in FIG. Then, when the collection unit 351 collects the transition information and related information, it associates them with the path of the transition source page and stores them in the storage unit 340 as transition management information 341 as shown in FIG.

[0063] The support device 300 determines whether or not there is any transition destination that has not been collected (step S16). That is, the collection unit 351 determines whether or not there remains a transition destination page for which transition information and the like has not been collected.

[0064] When the support device 300 determines that there is a transition destination that has not been collected (step S16; Yes), the support device 300 reads data of the transition destination (step S17). That is, the control unit 350 controls the communication unit 310 to read the HTML data, CSS data, image data, Script data, and the like that constitute the transition destination page. Then, the support device 300 returns the process to step S13 described above.

[0065] On the other hand, when it is determined in the above step S16 that there is no uncollected transition destination (step S16; No), the support device 300 generates and outputs a transition diagram (step S18). 8 based on transition management information 341 stored in storage unit 340. Then, output unit 352 outputs the generated transition diagram and displays it on display unit 330. This enables the operator to check whether the transitions between pages on the website are as designed.

[0066] The support device 300 determines whether or not any page in the transition diagram has been selected (step S19). When the support device 300 determines that any page has been selected (step S19; Yes), it generates and outputs a list (step S20). 9, when a page Pn is selected by a cursor CR, the generation unit 353 generates a list LT. Then, the output unit 352 outputs the generated list LT and displays it on the display unit 330. Therefore, the operator can use the list LT to check the appearance of the UI element that causes a transition. Then, the support device 300 returns the process to step S19 described above.

[0067] On the other hand, when it is determined in the above step S19 that there is no uncollected transition destination (step S19; No), the support device 300 determines whether or not an end has been instructed (step S21).

[0068] When the support device 300 determines that the end has not been instructed (step S21; No), the support device 300 returns the process to the above-mentioned step S19.

[0069] On the other hand, when it is determined that an instruction to end has been given (step S21; Yes), the support device 300 ends the support process.

[0070] This support process displays a transition diagram, for example, as shown in Fig. 8, allowing the worker to check whether the transitions between pages on the website are as designed. Also, when a page in the transition diagram is selected, a list LT, for example, as shown in Fig. 9, is displayed, allowing the worker to check the appearance of the UI elements that cause the transition to that page.

[0071] As a result, transitions between pages can be properly inspected, including the design of the UI elements that cause the transitions.

[0072] (Other embodiments) In the above embodiment, we have described a case where, when a page in the transition diagram is selected, a list LT showing the appearance of the UI elements that cause a transition to that page is displayed (output), as shown in FIG. 9. However, each list may be displayed regardless of the page selection. For example, the generating unit 353 generates, for each page in the transition diagram as shown in Fig. 8, a list showing the appearance of UI elements having the page as a transition destination. That is, the generating unit 353 generates each list LT by grouping each record according to the transition destination path 341b from the transition management information 341 shown in Fig. 5, and drawing the appearance of the UI element 341c of each group based on the related information 341d, etc. Then, the output unit 352 outputs each list superimposed on each page of the transition diagram as shown in Fig. 8, and displays it on the display unit 330. In this case, the worker can inspect the appearance of the UI elements that cause a transition to each page without selecting the page in the transition diagram.

[0073] In the above embodiment, the output unit 352 outputs the transition diagram and the list to the display unit 330. However, the output unit 352 may output to another terminal. For example, the output unit 352 controls the communication unit 310 to output the transition diagram and the list to a terminal device used by the worker.

[0074] In the above embodiment, the inspection system 100 that inspects the website of the sales server 200 that sells betting tickets for public races has been described as an example, but the system can also be applied to inspect other websites. For example, the present invention can be similarly applied to an inspection system 100 that inspects websites that sell products or provide various services.

[0075] As described above, according to the present invention, it is possible to provide an assistance device, an assistance method, and a program that can appropriately check transitions between pages, including the design of UI elements that cause the transition. [Explanation of symbols]

[0076] 100 Inspection Systems 200 Sales Server 300 Support equipment 310 Communications Department 320 Reception 330 Display section 340 Storage section 341 Transition management information 350 Control section 351 Collection Department 352 Output section 353 Generation part 400 Information processing device 401 CPU 402 ROM 403 RAM 404 NIC 405 Image Processing Unit 406 Audio Processing Unit 407 Auxiliary storage 408 Interface 409 Operation Unit 410 Display unit 411 Speaker 900 Internet

Claims

1. A collection unit that collects transition information, which is information for transitioning from each page constituting a website to another page, and includes a path of the transition destination page and a UI (User Interface) element that causes the transition; an output unit that classifies the UI elements included in the transition information collected by the collection unit into groups according to paths of the transition destination pages and outputs the UI elements; An assistance device comprising:

2. the collection unit sequentially follows the transition destination pages starting from a root page of the website, and collects only the transition information in which the path of the transition destination page is within the website; The support device according to claim 1 .

3. The collection unit further collects related information for representing an appearance of the UI element; The output unit outputs the appearance of the UI element according to the related information.

3. The support device according to claim 1 or 2.

4. a storage unit that stores the transition information collected by the collection unit in association with a path of a transition source page, the output unit generates and outputs a transition diagram between pages in the website based on the path of the transition source page stored in the storage unit and the transition information; 3. The support device according to claim 1 or 2.

5. a reception unit that receives a selection of any page in the transition diagram output by the output unit, The collection unit further collects related information for representing an appearance of the UI element; the output unit outputs a list showing appearances of the UI elements in a group corresponding to the page path accepted by the acceptance unit, in accordance with the associated information.

5. The support device according to claim 4.

6. An assistance method executed by an assistance device, a collection step of collecting transition information, which is information for transitioning from each page constituting the website to another page, and includes a path of the transition destination page and a UI element that causes the transition; an output step of classifying the UI elements included in the transition information collected in the collection step into groups according to paths of the transition destination pages and outputting the UI elements; An assistance method comprising:

7. On the computer, a collection step of collecting transition information, which is information for transitioning from each page constituting the website to another page, and includes a path of the transition destination page and a UI element that causes the transition; an output step of classifying the UI elements included in the transition information collected in the collection step into groups according to paths of the transition destination pages and outputting the UI elements; A program characterized by executing the above.

Images