Electronic device and information provision method thereof

Abstract

Provided is an information provision method of an electronic device. The information provision method comprises the steps of: obtaining information about an application; generating a graph of the relationships between a plurality of components corresponding to one or more pages in a first domain of the application on the basis of the information about the application; identifying at least one first component of a first type, at least one second component of a second type, and at least one third component of a third type among the plurality of components; determining the coverage ratio of the at least one first component in the first domain; and providing information about the coverage ratio.

Description

Electronic devices and their methods of providing information

[0001] The present disclosure relates to an electronic device and a control method thereof for providing information about the ratio of a set component used in a specific page or a specific domain of an application.

[0002] There is a growing trend of consumers purchasing items online rather than offline, and this trend has been further accelerated by the recent COVID-19 outbreak.

[0003] Consumers can install applications on their devices and use them to purchase items. As such, consumers utilize multiple applications, and multiple companies offer related services and compete with each other. In this competitive environment, the design of the application pages needs to be improved to maintain consumer interest over competing companies.

[0004] An application may offer multiple pages, each designed with multiple components. Systematically managing the design of these shared components across multiple pages can enhance the user experience (UX) and, consequently, increase application usability.

[0005] Therefore, the worker needs to be informed about whether the design of multiple components included in multiple pages provided by the application is rendered consistently.

[0006] The disclosed embodiments provide an electronic device and a method for providing information thereon. More specifically, the present invention provides an electronic device and a control method thereof for providing information regarding the ratio of configured components used in a specific page or domain of an application.

[0007] The technical tasks to be achieved by this embodiment are not limited to the technical tasks described above, and other technical tasks can be inferred from the following embodiments.

[0008] One aspect of the present disclosure may provide an information providing method, including: obtaining information about an application; generating a relationship graph between a plurality of components corresponding to one or more pages in a first domain of the application based on the information about the application; identifying at least one first component of a first type, at least one second component of a second type, and at least one third component of a third type among the plurality of components; identifying a coverage ratio of the at least one first component in the first domain; and providing information about the coverage ratio.

[0009] In addition, in one embodiment of the present disclosure, an information providing method may be provided, wherein the first type of component includes a component that matches one or more of the set components, the second type of component includes a component that does not match one or more of the set components but is set to be replaced by the one or more components, and the third type of component includes a component that does not match one or more of the set components and is set not to be replaced by the one or more components.

[0010] In addition, in one embodiment of the present disclosure, the step of checking the coverage ratio may include a step of filtering out at least one third component among the plurality of components; a step of checking the number of at least one first component and the number of at least one second component; and a step of determining the coverage ratio based on the number of at least one first component and the number of at least one second component. A method for providing information may be provided.

[0011] In addition, in one embodiment of the present disclosure, the information about the application includes an XML (extensible markup language) file, and the step of generating a relationship graph between the plurality of components includes a step of generating a tree view of the plurality of views displayed on the one or more pages by parsing the XML file, and the step of identifying the at least one first component, the at least one second component, and the at least one third component includes a step of identifying at least one first view of the first type, at least one second view of the second type, and at least one third view of the third type among the plurality of views. A method for providing information may be provided.

[0012] In addition, in one embodiment of the present disclosure, the step of checking the number of the at least one first component and the number of the at least one second component includes the step of checking the number of the at least one first view and the number of the at least one second view, and the information providing method can be provided, wherein the coverage ratio is determined as a value obtained by dividing the number of the at least one first view by the sum of the number of the at least one first view and the number of the at least one second view.

[0013] In addition, in one embodiment of the present disclosure, the step of providing information about the coverage ratio may provide an information providing method including the step of providing information about a dependency relationship of at least one second view based on a tree view of the plurality of views.

[0014] In addition, in one embodiment of the present disclosure, the information about the application includes code about the application, and the step of generating a relationship graph between the plurality of components includes a step of generating a call graph of a plurality of nodes corresponding to the one or more pages by parsing the code about the application, and the step of identifying the at least one first component, the at least one second component, and the at least one third component includes a step of identifying at least one first node of the first type, at least one second node of the second type, and at least one third node of the third type among the plurality of nodes.

[0015] In addition, in one embodiment of the present disclosure, the step of checking the number of the at least one first component and the number of the at least one second component includes the step of checking the number of calls of the at least one first node and the number of calls of the at least one second node, and the information providing method may be provided, wherein the coverage ratio is determined as a value obtained by dividing the number of calls of the at least one first node by the sum of the number of calls of the at least one first node and the number of calls of the at least one second node.

[0016] In addition, in one embodiment of the present disclosure, the step of providing information about the coverage ratio may further include a step of providing information about a call relationship of at least one second node based on a call graph of the plurality of nodes, thereby providing an information providing method.

[0017] In addition, in one embodiment of the present disclosure, the coverage ratio may be determined by a method for providing information, further considering at least one of the following: an area occupied by each of the at least one first component and each of the at least one second component on each of the at least one page; a position of each of the at least one first component and each of the at least one second component within each of the at least one page; and a time during which each of the at least one first component and each of the at least one second component is exposed to a user.

[0018] In addition, in one embodiment of the present disclosure, the coverage ratio may be determined to be higher as the number of the at least one first component increases, the area occupied by the at least one first component increases, the position of the at least one first component is closer to the center of the one or more pages, or the time for which the at least one first component is exposed increases, thereby providing an information providing method.

[0019] Another aspect of the present disclosure may provide an electronic device including a transceiver, a memory, and a processor, wherein the processor obtains information about an application, generates a relationship graph between a plurality of components corresponding to one or more pages in a first domain of the application based on the information about the application, identifies at least one first component of a first type, at least one second component of a second type, and at least one third component of a third type among the plurality of components, identifies a coverage ratio of the at least one first component in the first domain, and provides information about the coverage ratio.

[0020] Another aspect of the present disclosure may provide a computer-readable recording medium having recorded thereon a program for implementing a method performed by an electronic device.

[0021] Specific details of other embodiments are included in the detailed description and drawings.

[0022] According to the proposed embodiment, one or more of the following effects can be expected.

[0023] According to embodiments of the present specification, multiple workers managing multiple pages of a domain provided through an application can efficiently manage each page. Specifically, the workers managing each page can design the page using established user interface components, thereby improving the design consistency of the multiple pages provided by the application.

[0024] Furthermore, according to embodiments of the present disclosure, the electronic device provides information regarding the proportion of components used in the application domain that correspond to a set list, allowing the user to more conveniently design the domain components in a consistent manner. Consequently, the entire page can be systematically managed in a consistent manner, improving the user experience (UX) of users using the application.

[0025] Additionally, in accordance with embodiments of the present disclosure, by providing information regarding the rendering path or call path of a component of a type that must be replaced with one or more components set by the electronic device, the operator can more easily replace the component.

[0026] The effects of the invention are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description of the claims.

[0027] Figure 1 illustrates a system according to one embodiment.

[0028] FIG. 2 is a diagram illustrating a process in which an electronic device provides information regarding a coverage ratio of a set component in at least one domain of an application according to one embodiment.

[0029] FIG. 3 is a diagram illustrating a process in which an electronic device provides information regarding a coverage ratio of a set component in at least one domain of an application according to one embodiment.

[0030] FIG. 4 is a diagram illustrating a process in which an electronic device provides information regarding a coverage ratio of a set component in at least one domain of an application according to one embodiment.

[0031] FIG. 5 is a diagram illustrating a process by which an electronic device determines a coverage ratio of a set component in at least one domain of an application according to one embodiment.

[0032] FIGS. 6A to 6C are diagrams illustrating a process by which an electronic device determines a coverage ratio of a set component in at least one domain of an application according to one embodiment.

[0033] FIGS. 7A and 7B are diagrams illustrating a process by which an electronic device determines a coverage ratio of a set component in at least one domain of an application according to one embodiment.

[0034] FIG. 8 is a diagram illustrating a process by which an electronic device determines a coverage ratio of a set component in at least one domain of an application according to one embodiment.

[0035] FIG. 9 illustrates an example of a user interface provided by an electronic device according to one embodiment.

[0036] Figure 10 shows a flowchart of a method for providing information of an electronic device according to one embodiment.

[0037] Figure 11 shows a block diagram of an electronic device according to one embodiment.

[0038] The terms used in the embodiments have been selected from widely used and common terms, taking into account the functions of the present disclosure. However, these terms may vary depending on the intentions of those skilled in the art, precedents, the emergence of new technologies, etc. Furthermore, in certain cases, terms may be arbitrarily selected by the applicant, in which case their meanings will be described in detail in the relevant description. Therefore, the terms used in this disclosure should not be defined simply as names of terms, but rather based on the meanings of the terms and the overall content of the present disclosure.

[0039] When a part of a specification is said to "include" a component, this does not mean that it excludes other components, but rather that it may include other components, unless otherwise stated.

[0040] The expression "at least one of a, b, and c" described throughout the specification may encompass 'a alone', 'b alone', 'c alone', 'a and b', 'a and c', 'b and c', or 'all of a, b, and c'.

[0041] The "terminal" mentioned below may be implemented as a computer or portable terminal that can connect to a server or other terminal via a network. Here, the computer includes, for example, a notebook, desktop, laptop, etc. equipped with a web browser, and the portable terminal may include, for example, a wireless communication device that guarantees portability and mobility, and may include all types of handheld-based wireless communication devices such as communication-based terminals such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), LTE (Long Term Evolution), smartphones, tablet PCs, etc.

[0042] Below, embodiments of the present disclosure are described in detail with reference to the attached drawings so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein.

[0043] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings.

[0044] Figure 1 illustrates a system according to one embodiment.

[0045] Referring to FIG. 1, the system may include at least one of an electronic device (100), a user terminal (120), a worker terminal (140), and a network (160). Meanwhile, the system illustrated in FIG. 1 only illustrates components related to the present embodiment. Therefore, those skilled in the art will appreciate that, in addition to the components illustrated in FIG. 1, other general-purpose components may be included.

[0046] An electronic device (100) is a device that configures and provides various types of information. The electronic device (100) may provide the configured information as a web page or application screen, or may provide the information in a form that can be displayed as a web page or application screen on a receiving terminal.

[0047] According to one embodiment, the electronic device (100) may provide information regarding the coverage ratio of a configured component in at least one domain of an application. For example, the electronic device (100) may obtain information regarding the application, and based on the information regarding the application, generate a relationship graph between a plurality of components corresponding to one or more pages within a first domain of the application. Thereafter, the electronic device (100) may identify at least one first component of a first type and at least one second component of a second type among the plurality of components, identify the coverage ratio of at least one first component in the first domain, and provide information regarding the coverage ratio.

[0048] The user terminal (120) is a terminal used by each user, and users can access services provided by the network (160) using their respective terminals (120). For example, the electronic device (100) may provide the user terminal (120) with a platform or application that allows users to order various items. Users can order various items using applications installed on their respective user terminals (120).

[0049] The worker terminal (140) is a terminal used by each worker, and the workers can use their respective terminals (140) to check information regarding the coverage ratio of a set component in one or more domains of the application. For example, the worker terminal (140) may provide a user interface that displays information regarding the coverage ratio of a set component in each of one or more domains of the application based on information received from the electronic device (100).

[0050] The user terminal (120), the worker terminal (140), and the electronic device (100) can communicate with each other within the network (160). The network (160) includes a Local Area Network (LAN), a Wide Area Network (WAN), a Value Added Network (VAN), a mobile radio communication network, a satellite communication network, and a combination thereof, and is a comprehensive data communication network that allows each network component illustrated in FIG. 1 to communicate smoothly with each other, and may include wired Internet, wireless Internet, and a mobile radio communication network. Wireless communication may include, but is not limited to, wireless LAN (Wi-Fi), Bluetooth, Bluetooth low energy, Zigbee, Wi-Fi Direct (WFD), ultra wideband (UWB), infrared communication (IrDA, infrared Data Association), NFC (Near Field Communication), etc., for example.

[0051] FIG. 2 is a diagram illustrating a process in which an electronic device (100) provides information about a coverage ratio of a set component in at least one domain of an application according to one embodiment.

[0052] According to one embodiment, the electronic device (100) can obtain information about an application. More specifically, the electronic device (100) can obtain code or files for implementing at least one domain of the application.

[0053] For example, the electronic device (100) may obtain at least one of an XML (extensible markup language) file (230), a code (240) regarding the application, and a JAR (java archive) file (250) for implementing a first domain of the application. At this time, the first domain may be implemented by each of the XML file (230), the code (240) regarding the application, or the JAR file (250), or may be implemented by a combination of two or more of the XML file (230), the code (240) regarding the application, and the JAR file (250).

[0054] Meanwhile, the code (240) regarding the application may include Java code or Kotlin code, but the type of code included in the code (240) regarding the application is not limited to that described above.

[0055] According to one embodiment, the electronic device (100) may generate a relationship graph between a plurality of components corresponding to one or more pages within at least one domain of the application based on information about the application.

[0056] For example, the XML analysis module (200) can generate a tree view of multiple views displayed on one or more pages within the first domain by parsing the acquired XML file (230). At this time, the view is a basic component of the user interface displayed on the display and can include various types of user interface components such as text, images, input fields, icons, or buttons.

[0057] As another example, the code analysis module (210) can generate a call graph of multiple nodes corresponding to one or more pages within the first domain by parsing the code (240) regarding the acquired application. In this case, the nodes may include functions, classes, methods, etc. included in the code (240) regarding the application.

[0058] According to one embodiment, the electronic device (100) can identify a first type of component and a second type of component among a plurality of components. More specifically, the electronic device (100) can identify a component that matches one or more configured components among the plurality of components as a first type of component. In addition, the electronic device (100) can identify a component that does not match one or more configured components among the plurality of components but is configured to be replaced by one or more configured components as a second type of component.

[0059] For example, the XML analysis module (200) can identify a view that matches one or more components set among multiple views as a first type view, and can identify a view that does not match one or more components but is set to be replaced by one or more components as a second type view.

[0060] For another example, the code analysis module (210) can identify a node that matches one or more components set among a plurality of nodes as a first type node, and can identify a node that does not match one or more components but is set to be replaced with one or more components as a second type node.

[0061] Meanwhile, the first type of component may be referred to as an RDS (rocket design system) component as a user interface component designed to conform to the established guidelines, and the second type of component may be referred to as a non-RDS component as a user interface component that does not conform to the established guidelines. However, the terms used to refer to these components are not limited to those described above.

[0062] According to one embodiment, the electronic device (100) can check the number of components of the first type and the number of components of the second type. For example, the XML analysis module (200) can check the number of views of the first type and the number of views of the second type. Alternatively, the code analysis module (210) can check the number of calls of nodes of the first type and the number of calls of nodes of the second type.

[0063] According to one embodiment, the electronic device (100) can determine the coverage ratio of the first type of component in at least one domain of the application based on the number of the first type of components and the number of the second type of components. More specifically, the data integration module (220) can determine the coverage ratio based on information obtained from the XML analysis module (200) or the code analysis module (210).

[0064] For example, if the first domain of the application is implemented by an XML file (230), the data integration module (220) can obtain information about the number of views of the first type and the number of views of the second type from the XML analysis module (200). Thereafter, the data integration module (220) can determine the value obtained by dividing the number of views of the first type by the sum of the number of views of the first type and the number of views of the second type as the coverage ratio.

[0065] For another example, if the first domain of the application is implemented by the code (240) regarding the application, the data integration module (220) can obtain information regarding the number of calls of the first type node and the number of calls of the second type node from the code analysis module (210). Thereafter, the data integration module (220) can determine the value obtained by dividing the number of calls of the first type node by the sum of the number of calls of the first type node and the number of calls of the second type node as the coverage ratio.

[0066] For another example, if the first domain of the application is implemented by an XML file (230) and a code (240) regarding the application, the data integration module (220) can obtain information about the number of views of the first type and the number of views of the second type from the XML analysis module (200), and obtain information about the number of calls of nodes of the first type and the number of calls of nodes of the second type from the code analysis module (210). Thereafter, the data integration module (220) can determine a value obtained by dividing the sum of the number of views of the first type and the number of calls of nodes of the first type by the sum of the number of views of the first type, the number of views of the second type, the number of calls of nodes of the first type, and the number of calls of nodes of the second type as a coverage ratio.

[0067] According to one embodiment, the electronic device (100) may provide information (260) regarding a coverage ratio based on information regarding an application. For example, the electronic device (100) may provide a user interface that displays information regarding a coverage ratio of a first type of component in each of one or more domains of the application via the worker terminal (140).

[0068] According to one embodiment, the electronic device (100) may provide information regarding the results of analyzing at least one domain of an application. More specifically, the electronic device (100) may provide at least one of information regarding a view rendering path (270), information regarding a view position (280), and information regarding a function call path (290).

[0069] For example, the electronic device (100) may provide information (270) about the dependency relationship of each view of the second type or information about the rendering path based on a tree view of a plurality of views. Alternatively, the electronic device (100) may provide information (280) about the location of each view of the second type in the tree view based on a tree view of a plurality of views. The electronic device (100) may provide information (290) about the call relationship of each node of the second type based on a call graph of a plurality of nodes.

[0070] FIG. 3 is a diagram illustrating a process in which an electronic device (100) provides information regarding the coverage ratio of a set component in at least one domain of an application, according to one embodiment. Any content overlapping with FIG. 2 will be briefly described or omitted.

[0071] According to one embodiment, the XML analysis module (300) may obtain code or files for implementing at least one domain of the application. For example, the XML analysis module (300) may obtain an XML file (305) for implementing a first domain of the application.

[0072] According to one embodiment, the XML parsing module (300) may generate a tree view (315) of multiple views corresponding to one or more pages within at least one domain of the application based on the XML file (305). For example, the parsing module (310) may generate a tree view (315) representing the dependency relationship between the first view to the ninth view displayed on one or more pages within the first domain by parsing the acquired XML file (305).

[0073] At this time, the tree view may refer to a graph that represents the dependency relationship when multiple views are rendered in a hierarchical structure. For example, referring to FIG. 3, since the rendering of the first view and the second view must be performed first in order for the fifth view to be rendered, the fifth view may have a dependency relationship with the first view and the second view, which may be expressed in the tree view (315) as a structure of first view → second view → fifth view. Meanwhile, the tree view may be used interchangeably with a view tree, etc., but the term referring thereto is not limited to the above-described term.

[0074] According to one embodiment, the XML analysis module (300) can verify the type of each of the plurality of views. More specifically, the XML analysis module (300) can verify a first type of view, a second type of view, and a third type of view among the plurality of views based on whether they match one or more configured components and whether they are configured to be replaced by one or more configured components.

[0075] For example, referring to FIG. 3, the XML analysis module (300) can identify the fifth, sixth, seventh, and ninth views that match one or more components set among the plurality of views as views of the first type. In addition, the XML analysis module (300) can identify the third and eighth views that do not match one or more components but are set to be replaced by one or more components as views of the second type. The XML analysis module (300) can identify the first, second, and fourth views that do not match one or more components and are set not to be replaced by one or more components as views of the third type.

[0076] According to one embodiment, the XML analysis module (300) may filter out a third type of view among multiple views. For example, the filtering module (320) may exclude the first, second, and fourth views identified as third type views. However, the process of filtering the third type views may be omitted.

[0077] According to one embodiment, the XML analysis module (300) can check the number of views of the first type and the number of views of the second type among the multiple views. For example, the counting module (350) can check that the number of views of the first type is 4 and the number of views of the second type is 2.

[0078] According to one embodiment, the XML analysis module (300) may verify the reference information (345) based on at least one of the code (325) and the JAR file (330) regarding the application, and may additionally consider the reference information to verify the number of views of the first type and the number of views of the second type. For example, when calculating the coverage ratio of the views of the first type in the first domain and the second domain, the reference analysis module (340) may verify the number of times the views of the first type and the views of the second type included in the tree view (315) were rendered in the second domain. Thereafter, the counting module (350) may additionally consider the number of times rendered obtained from the reference analysis module (340) to verify the number of views of the first type and the number of views of the second type. However, when calculating only the coverage ratio of the views of the first type in the first domain, the process of generating and considering the reference information may be omitted.

[0079] According to one embodiment, the XML analysis module (300) may provide information (355) regarding the number of views. For example, the counting module (350) may provide the data integration module with information (355) regarding the number of views, including information that the number of views of the first type is 4 and the number of views of the second type is 2.

[0080] According to one embodiment, the XML analysis module (300) may provide information (365) about a path. More specifically, the XML analysis module (300) may provide information (365) about a dependency relationship of a second type of view or information (365) about a rendering path based on a tree view (315) of multiple views.

[0081] For example, the path identification module (360) can provide the data integration module with information (365) about a path that includes information that the dependency relationship of the third view of the second type is the first view → the third view, and the dependency relationship of the eighth view of the second type is the first view → the fourth view → the eighth view.

[0082] In this way, by providing information about the rendering path of a second type of view that must be replaced with one or more components configured in the XML analysis module (300), the worker can more easily replace the second type of view.

[0083] Meanwhile, the XML analysis module (300) of FIG. 3 can correspond to the XML analysis module (200) of FIG. 2.

[0084] FIG. 4 is a diagram illustrating a process in which an electronic device (100) provides information regarding the coverage ratio of a set component in at least one domain of an application, according to one embodiment. Any content overlapping with FIG. 2 will be briefly described or omitted.

[0085] According to one embodiment, the code analysis module (400) may obtain code or files for implementing at least one domain of the application. For example, the code analysis module (400) may obtain code (410) relating to the application for implementing a first domain of the application.

[0086] According to one embodiment, the code analysis module (400) may generate a call graph (430) of a plurality of nodes corresponding to one or more pages within at least one domain of the application based on the code (410) regarding the application. For example, the parsing module (420) may generate a call graph (430) representing a call relationship between the first node to the eighth node corresponding to one or more pages within the first domain by parsing the acquired code (410) regarding the application.

[0087] At this time, the call graph may refer to a weighted directed acyclic graph that represents the call relationship and the number of calls between multiple nodes. For example, referring to FIG. 4, the code (410) for the application may be written such that the second node calls the third node three times and the third node calls the fourth node twice, which may be expressed in the call graph (430) as a structure of second node → (3) third view → (2) fourth view. In addition, among the multiple nodes, the first node, the second node, the third node, and the fifth node corresponding to a function that performs a view rendering function may be indicated with an asterisk.

[0088] According to one embodiment, the code analysis module (400) can verify the type of each of the plurality of nodes. More specifically, the code analysis module (400) can verify a first type of node, a second type of node, and a third type of node among the plurality of nodes based on whether they match one or more configured components and whether they are configured to be replaced by one or more configured components.

[0089] For example, referring to FIG. 4, the code analysis module (400) can identify a fourth node that matches one or more components set among a plurality of nodes as a first type node. In addition, the code analysis module (400) can identify a seventh node and an eighth node that do not match one or more components but are set to be replaced by one or more components as a second type node. The code analysis module (400) can identify a first node, a second node, a third node, a fifth node, and a sixth node that do not match one or more components and are set not to be replaced by one or more components as a third type node.

[0090] According to one embodiment, the code analysis module (400) may filter out a third type of node among a plurality of nodes. For example, the filtering module (440) may exclude the first node, the second node, the third node, the fifth node, and the sixth node, which are identified as third type nodes. However, the process of filtering out the third type nodes may be omitted.

[0091] According to one embodiment, the code analysis module (400) can check the number of calls to a first type of node and the number of calls to a second type of node among a plurality of nodes. More specifically, the code analysis module (400) can check how many times a node corresponding to a function performing a view rendering function calls the first type of node and the second type of node, respectively.

[0092] For example, the counting module (450) can confirm that the 4th node of the 1st type is called once by the 1st node, the 2nd node is called 6 times (3x2) through the 3rd node, and the 3rd node is called twice. In addition, the counting module (450) can confirm that the 7th node of the 2nd type is called once by the 5th node through the 6th node, and the 8th node is called twice (1x2). The counting module (450) can confirm that the 8th node of the 2nd type is called once by the 5th node.

[0093] According to one embodiment, the code analysis module (400) may provide information (460) regarding the number of calls of a node. For example, the counting module (450) may provide the data integration module with information (460) regarding the number of calls of a node, including information that the number of calls of a first type of node is 9 and the number of calls of a second type of node is 4.

[0094] According to one embodiment, the code analysis module (400) may provide information (480) regarding a path. More specifically, the code analysis module (400) may provide information (480) regarding a call path of a second type of node based on a call graph (430) of a plurality of nodes.

[0095] For example, the path identification module (470) can provide the data integration module with path information (480) including information that the call path of the 7th node of the 2nd type is the 5th node → 6th node → 7th node, the 5th node → 8th node → 7th node, and the call path of the 8th node of the 2nd type is the 5th node → 8th node.

[0096] In this way, by providing information about the call path of a second type of node that must be replaced with one or more components set by the code analysis module (400), the worker can more easily replace the second type of node.

[0097] Meanwhile, the code analysis module (400) of FIG. 4 can correspond to the code analysis module (210) of FIG. 2.

[0098] FIG. 5 is a diagram illustrating a process by which an electronic device (100) determines a coverage ratio of a set component in at least one domain of an application according to one embodiment. Any content overlapping with FIG. 2 will be briefly described or omitted.

[0099] According to one embodiment, the electronic device (100) may obtain code or files for implementing at least one domain of the application. For example, the electronic device (100) may obtain an XML file for implementing a first domain of the application.

[0100] According to one embodiment, the electronic device (100) may generate a tree view of a plurality of views corresponding to one or more pages within at least one domain of an application based on an XML file. For example, referring to FIG. 5, the electronic device (100) may generate a tree view indicating a dependency relationship among a first view (500), a second view (520), a third view (540), a fourth view (560), and a fifth view (580) displayed on a first page of a first domain of the application by parsing the acquired XML file.

[0101] According to one embodiment, the electronic device (100) can identify the type of each of the plurality of views. More specifically, the electronic device (100) can identify a first type of view and a second type of view among the plurality of views based on whether they match one or more configured components and whether they are set to be replaced by one or more configured components.

[0102] For example, referring to FIG. 5, the electronic device (100) can identify the fourth view (560) and the fifth view (580), which match one or more components set among the plurality of views, as views of the first type. In addition, the electronic device (100) can identify the first view (500), the second view (520), and the third view (540), which do not match one or more components but are set to be replaced by one or more components, as views of the second type.

[0103] According to one embodiment, the electronic device (100) can check the number of views of the first type and the number of views of the second type among a plurality of views. For example, the electronic device (100) can check that the number of views of the first type is 2 and the number of views of the second type is 3.

[0104] According to one embodiment, the electronic device (100) may determine a coverage ratio of a first type of component in at least one domain of an application based on the number of first type of components and the number of second type of components. More specifically, the electronic device (100) may determine a value obtained by dividing the number of first type of views by the sum of the number of first type of views and the number of second type views as the coverage ratio.

[0105] For example, the electronic device (100) can determine 2 / 5 or 40% as the coverage ratio of the first type component in the first domain by dividing 2, which is the number of views of the first type, by 5, which is the sum of the number of views of the first type and the number of views of the second type.

[0106] Meanwhile, although FIG. 5 illustrates that the first page of the first domain of the application corresponds to the first view (500), this is only one embodiment, and whether the page itself corresponds to one view may vary depending on how the code or file for implementing the module is written.

[0107] FIGS. 6A to 6C are diagrams illustrating a process by which an electronic device (100) determines a coverage ratio of a set component in at least one domain of an application, according to one embodiment. Any content overlapping with FIG. 2 will be briefly described or omitted.

[0108] According to one embodiment, the electronic device (100) may obtain code or files for implementing at least one domain of the application. For example, the electronic device (100) may obtain XML files for implementing the first page (600), the second page (610), and the third page (620) of the product detail page (SDP) domain of the application.

[0109] According to one embodiment, the electronic device (100) may generate a tree view of a plurality of views corresponding to one or more pages within at least one domain of the application based on an XML file. For example, the electronic device (100) may generate a first tree view indicating a dependency relationship between a first view (632) to a twelfth view (654) displayed on a first page (600), a second tree view indicating a dependency relationship between a thirteenth view (656) to a twenty-fourth view (678) displayed on a second page (610), and a third tree view indicating a dependency relationship between a twenty-fifth view (680) to a thirty-third view (696) displayed on a third page (620) by parsing the XML file.

[0110] According to one embodiment, the electronic device (100) can identify the type of each of the plurality of views. More specifically, the electronic device (100) can identify a first type of view, a second type of view, and a third type of view among the plurality of views based on whether the view matches one or more configured components and whether the view is set to be replaced by one or more configured components.

[0111] For example, referring to FIG. 6A, the electronic device (100) can identify the second view (634), the sixth view (642), the seventh view (644), and the eighth view (646), which are set to match one or more components among the plurality of views displayed on the first page (600), as views of the first type. In addition, the electronic device (100) can identify the third view (636), the ninth view (648), the tenth view (650), the eleventh view (652), and the twelfth view (654), which are not matched to one or more components but are set to be replaced by one or more components, as views of the second type. The electronic device (100) can identify the first view (632), the fourth view (638), and the fifth view (640), which are not matched to one or more components and are set not to be replaced by one or more components, as views of the third type.

[0112] For another example, referring to FIG. 6B, the electronic device (100) can identify the 13th view (656), the 15th view (660), the 16th view (662), the 18th view (666), the 23rd view (676), and the 24th view (678), which are set to match one or more components among the multiple views displayed on the second page (610), as views of the first type. In addition, the electronic device (100) can identify the 14th view (658), the 17th view (664), the 19th view (668), the 20th view (670), the 21st view (672), and the 22nd view (674), which are set to be replaced with one or more components but do not match one or more components, as views of the second type.

[0113] For another example, referring to FIG. 6C, the electronic device (100) can identify the 25th view (680), the 28th view (686), the 29th view (688), the 31st view (692), and the 32nd view (694), which are set to match one or more components among the plurality of views displayed on the third page (620), as views of the first type. In addition, the electronic device (100) can identify the 26th view (682), the 27th view (684), the 30th view (690), and the 33rd view (696), which are set to be replaced with one or more components but do not match one or more components, as views of the second type.

[0114] According to one embodiment, the electronic device (100) may filter out a third type of view among a plurality of views. For example, the electronic device (100) may exclude the first view (632), the fourth view (638), and the fifth view (640) identified as views of the third type. However, the process of filtering out views of the third type may be omitted.

[0115] According to one embodiment, the electronic device (100) can check the number of views of a first type and the number of views of a second type among a plurality of views. More specifically, the electronic device (100) can check the total number of views of the first type and the total number of views of the second type corresponding to each of one or more pages within at least one domain.

[0116] For example, the electronic device (100) can verify that the total number of views of the first type included in each of the first page (600), the second page (610), and the third page (620) of the SDP domain is 15, and can verify that the total number of views of the second type included in each of the first page (600), the second page (610), and the third page (620) of the SDP domain is 15.

[0117] According to one embodiment, the electronic device (100) may determine a coverage ratio of a first type of component in at least one domain of an application based on the number of first type of components and the number of second type of components. More specifically, the electronic device (100) may determine a value obtained by dividing the total number of views of the first type by the sum of the total number of views of the first type and the total number of views of the second type as the coverage ratio.

[0118] For example, the electronic device (100) can determine 15 / 30 or 50% as the coverage ratio of the first type component in the SDP domain by dividing 15, which is the total number of views of the first type, by 30, which is the sum of the total number of views of the first type and the total number of views of the second type.

[0119] FIGS. 7A and 7B are diagrams illustrating a process by which an electronic device (100) determines a coverage ratio of a set component in at least one domain of an application according to one embodiment. Any content overlapping with FIG. 2 will be briefly described or omitted.

[0120] According to one embodiment, the electronic device (100) can determine the coverage ratio of the first type of component in at least one domain of the application based on the number of the first type of components and the number of the second type of components. More specifically, the electronic device (100) can determine a higher coverage ratio of the first type of component as the number of the first type of components increases.

[0121] According to one embodiment, the electronic device (100) may determine a coverage ratio of a first type component in at least one domain of an application based on the area occupied by each of the first type component and the second type component on a page. More specifically, the electronic device (100) may determine a higher coverage ratio of the first type component as the area occupied by the first type component on the page increases.

[0122] For example, referring to FIG. 7A, the electronic device (100) can confirm that the ratio of the area occupied by the first view (700) of the second type, the second view (710) of the second type, and the third view (720) of the first type on the page is 1:1:2. Accordingly, the electronic device (100) can determine the coverage ratio of the component of the first type as 2 / (1+1+2) = 2 / 4 = 50%.

[0123] According to one embodiment, the electronic device (100) may determine a coverage ratio of a first type component in at least one domain of an application based on the respective positions of the first type component and the second type component within a page. More specifically, the electronic device (100) may determine a higher coverage ratio of the first type component as the position of the first type component is closer to the center of the page.

[0124] For example, referring to FIG. 7B, the electronic device (100) can confirm that the ratio of the distance from the center of each of the fourth view (730) and sixth view (750) of the second type and the fifth view (740) of the first type to the center of the page is 0.5:0.5:0. In order to give a higher weight to a component closer to the center of the page, the electronic device (100) can determine (1-0.5):(1-0.5):(1-0)=0.5:0.5:1, which is obtained by subtracting the ratio of the distance from the center of each component to the center of the page from 1, as a value to be applied to each component. Accordingly, the electronic device (100) can determine the coverage ratio of the component of the first type as 1 / (0.5+0.5+1)=1 / 2=50%.

[0125] According to one embodiment, the electronic device (100) may determine the coverage ratio of the first type of component in at least one domain of the application based on the time that each of the first type of component and the second type of component is exposed to the user. More specifically, the electronic device (100) may determine the coverage ratio of the first type of component to be higher as the time that the first type of component is exposed to the user increases.

[0126] For example, the electronic device (100) may receive information from the user terminal regarding the time at which each of the first type of component and the second type of component was exposed to the user. Thereafter, the electronic device (100) may determine the coverage ratio of the first type of component based on the ratio of the time at which each of the first type of component and the second type of component was exposed to the user. In this case, the time at which the component was exposed to the user indicates the time at which the component was actually displayed on the display of the user terminal, and may be determined differently depending on the user's scrolling action or the icon selected by the user.

[0127] According to one embodiment, the electronic device (100) can determine a coverage ratio of a first type component in at least one domain of an application by applying different weights to a first factor regarding the number of each of the first type components and the second type components, a second factor regarding an area each of the first type components and the second type components occupies on a page, a third factor regarding a position of each of the first type components and the second type components within the page, and a fourth factor regarding a time each of the first type components and the second type components is exposed to a user.

[0128] For example, the electronic device (100) may determine the weights applied to the third and fourth factors as 0 based on the configuration information received from the worker terminal. Accordingly, the electronic device (100) may determine the coverage ratio of the first type component in at least one domain by considering only the first factor regarding the number of each of the first type components and the second type components and the second factor regarding the area each of the first type components and the second type components occupies on the page.

[0129] FIG. 8 is a diagram illustrating a process for an electronic device (100) to determine a coverage ratio of a set component in at least one domain of an application according to one embodiment.

[0130] According to one embodiment, the electronic device (100) may obtain code or files for implementing at least one domain of an application. More specifically, the electronic device (100) may obtain code or files included in each of a plurality of modules for implementing at least one domain.

[0131] For example, the electronic device (100) may obtain an XML file, Java code, Kotlin code, or JAR file included in a first module for implementing a first area (820) of a first domain (800). Alternatively, the electronic device (100) may obtain an XML file, Java code, Kotlin code, or JAR file included in a second module for implementing a second area (840) of the first domain (800). The electronic device (100) may obtain an XML file, Java code, Kotlin code, or JAR file included in a third module for implementing a third area (860) of the first domain (800).

[0132] According to one embodiment, the electronic device (100) may generate a relationship graph between a plurality of components corresponding to one or more pages within at least one domain of the application based on information about the application. For example, the electronic device (100) may generate a tree view of a plurality of first views displayed in a first area (820) by parsing code included in a first module. Alternatively, the electronic device (100) may generate a tree view of a plurality of second views displayed in a second area (840) by parsing code included in a second module. The electronic device (100) may generate a tree view of a plurality of third views displayed in a third area (860) by parsing code included in a third module.

[0133] According to one embodiment, the electronic device (100) can identify the type of each of the plurality of views. For example, based on whether it matches one or more configured components and whether it is set to be replaced by one or more configured components, the electronic device (100) can identify a first type of view, a second type of view, and a third type of view among the plurality of first views, the plurality of second views, and the plurality of third views.

[0134] According to one embodiment, the electronic device (100) may filter a third type of view among a plurality of views. For example, the electronic device (100) may exclude a view identified as a third type of view among a plurality of first views, a plurality of second views, and a plurality of third views. However, the process of filtering the third type of view may be omitted.

[0135] According to one embodiment, the electronic device (100) can check the number of views of a first type and the number of views of a second type among a plurality of views. For example, the electronic device (100) can check the number of views of the first type and the number of views of the second type for each of the plurality of first views, the plurality of second views, and the plurality of third views.

[0136] According to one embodiment, the electronic device (100) may determine the coverage ratio of the first type of component for each area included in at least one domain of the application based on the number of the first type of component and the number of the second type of component. More specifically, the electronic device (100) may determine the value obtained by dividing the number of the first type of views displayed in each area included in at least one domain by the sum of the number of the first type of views and the number of the second type of views as the coverage ratio.

[0137] For example, the electronic device (100) may determine 20%, which is obtained by dividing the number of the first type of views displayed in the first area (820) by the sum of the number of the first type of views and the number of the second type of views, as the coverage ratio of the first type of components in the first area (820). Alternatively, the electronic device (100) may determine 100%, which is obtained by dividing the number of the first type of views displayed in the second area (840) by the sum of the number of the first type of views and the number of the second type of views, as the coverage ratio of the first type of components in the second area (840). The electronic device (100) may determine 50%, which is obtained by dividing the number of the first type of views displayed in the third area (860) by the sum of the number of the first type of views and the number of the second type of views, as the coverage ratio of the first type of components in the third area (860).

[0138] According to one embodiment, the electronic device (100) can determine the coverage ratio of the first type component in at least one domain of the application by applying different weights to each of one or more areas included in at least one domain. More specifically, the electronic device (100) can determine the coverage ratio of the first type component in at least one domain of the application by applying different weights to each of one or more areas based on an area occupied by each of the one or more areas, a location of each of the one or more areas, and a time during which each of the one or more areas is exposed to a user.

[0139] For example, the electronic device (100) may apply different weights to the first region (820), the second region (840), and the third region (860) based on the area occupied by each of the one or more regions based on the setting information received from the worker terminal. Accordingly, the electronic device (100) may confirm that the ratio of the areas occupied by the first region (820), the second region (840), and the third region (860) is 1:2:1, and may determine the coverage ratio of the first type of component as (1x20% + 2x100% + 1x50%) / (1+2+1) = 67.5%.

[0140] FIG. 9 illustrates an example of a user interface (900) provided by an electronic device (100) according to one embodiment.

[0141] According to one embodiment, the electronic device (100) may provide a user interface (900) including information regarding a coverage ratio of a set component in one or more domains of an application to a worker via a worker terminal. For example, referring to FIG. 9, the worker terminal may receive information in a form that can be displayed as a web page or an application screen from the electronic device (100), and based on the received information, may display a user interface (900) including an area displaying information regarding a coverage ratio of a set component in the entire application or an area displaying information regarding a coverage ratio of a set component in one or more domains of the application.

[0142] According to one embodiment, the user interface (900) may include an area (910) for setting parameters regarding the application. For example, the area (910) may include an area for setting a version of the application, an area for setting a platform of a user terminal on which the application is installed, and an area for setting a domain.

[0143] According to one embodiment, the user interface (900) may include an area (920) that displays information regarding the coverage ratio of a set component in the entire application. For example, when an operator sets the version of the application to 7.7.1 in area (910) and sets the platform of the user terminal on which the application is installed to Android, information indicating that the coverage ratio of the first type of component in the entire application of version 7.7.1 installed in the user terminal of the Android platform is 8% may be displayed in area (920).

[0144] According to one embodiment, the user interface (900) may include an area (930) that displays information regarding the coverage ratio of a set component in a specific domain of the application. For example, when an operator sets the version of the application to 7.7.1 in area (910) and the domain to domain-cart, area (930) may display information indicating that the coverage ratio of the first type of component in the domain-cart of the application of version 7.7.1 is 13.2%. In addition, area (930) may also display information indicating that the coverage ratio of the first type of component in the domain-cart of the application of version 7.6.9, which is the version immediately preceding 7.7.1, is 12.9%, thereby providing information regarding an improved ratio.

[0145] According to one embodiment, the user interface (900) may include an area (940) and an area (950) that display information regarding a coverage ratio of a configured component in one or more domains of the application. For example, the area (940) and the area (950) may display information regarding a coverage ratio of a first type of component in each of a plurality of domains of the application.

[0146] Meanwhile, the specific examples of the types and coverage ratios of the user interface components illustrated in FIG. 9 are merely exemplary, and it is apparent to a person skilled in the art to which the present disclosure pertains that the present disclosure can be implemented with examples different from those described above.

[0147] Figure 10 illustrates a flowchart of a method for providing information in an electronic device according to one embodiment. The above description may apply to overlapping content.

[0148] At step S1000, the electronic device can obtain information about the application.

[0149] According to one embodiment, information about the application may include an extensible markup language (XML) file.

[0150] In one embodiment, information about an application may include code about the application.

[0151] At step S1020, the electronic device can generate a relationship graph between a plurality of components corresponding to one or more pages within a first domain of the application based on information about the application.

[0152] According to one embodiment, the electronic device can generate a tree view of multiple views displayed on one or more pages by parsing an XML file when generating a relationship graph between multiple components.

[0153] According to one embodiment, when generating a relationship graph between a plurality of components, the electronic device can generate a call graph of a plurality of nodes corresponding to one or more pages by parsing code related to the application.

[0154] At step S1040, the electronic device can identify at least one first component of a first type, at least one second component of a second type, and at least one third component of a third type among a plurality of components.

[0155] According to one embodiment, a first type of component may include a component that matches one or more of the configured components, a second type of component may include a component that does not match one or more of the configured components but is configured to be replaced by one or more of the configured components, and a third type of component may include a component that does not match one or more of the configured components and is configured not to be replaced by one or more of the configured components.

[0156] According to one embodiment, when the electronic device identifies at least one first component, at least one second component, and at least one third component, the electronic device can identify at least one first view of a first type, at least one second view of a second type, and at least one third view of a third type among a plurality of views.

[0157] According to one embodiment, when the electronic device identifies at least one first component, at least one second component, and at least one third component, the electronic device can identify at least one first node of a first type, at least one second node of a second type, and at least one third node of a third type among a plurality of nodes.

[0158] At step S1060, the electronic device can check the coverage ratio of at least one first component in the first domain.

[0159] According to one embodiment, when checking the coverage ratio, the electronic device may filter out at least one third component among a plurality of components, check the number of at least one first component and the number of at least one second component, and determine the coverage ratio based on the number of at least one first component and the number of at least one second component.

[0160] According to one embodiment, when the electronic device determines the number of at least one first component and the number of at least one second component, the electronic device determines the number of at least one first view and the number of at least one second view, and the coverage ratio can be determined as a value obtained by dividing the number of at least one first view by the sum of the number of at least one first view and the number of at least one second view.

[0161] According to one embodiment, when the electronic device checks the number of at least one first component and the number of at least one second component, the number of calls of at least one first node and the number of calls of at least one second node may be checked, and a coverage ratio may be determined as a value obtained by dividing the number of calls of at least one first node by the sum of the number of calls of at least one first node and the number of calls of at least one second node.

[0162] According to one embodiment, the coverage ratio may be determined by further considering at least one of an area occupied by each of the at least one first component and each of the at least one second component on one or more pages, a location of each of the at least one first component and each of the at least one second component within one or more pages, and a time during which each of the at least one first component and each of the at least one second component is exposed to a user.

[0163] According to one embodiment, the coverage ratio may be determined to be higher as the number of at least one first component increases, the area occupied by at least one first component increases, the position of at least one first component is closer to the center of one or more pages, or the time for which at least one first component is exposed increases.

[0164] At step S1080, the electronic device may provide information regarding the coverage ratio.

[0165] According to one embodiment, when providing information about a coverage ratio, the electronic device may provide information about a dependency relationship of at least one second view based on a tree view of a plurality of views.

[0166] According to one embodiment, when providing information about a coverage ratio, the electronic device may provide information about a call relationship of at least one second node based on a call graph of a plurality of nodes.

[0167] FIG. 11 shows a block diagram of an electronic device (100) according to one embodiment.

[0168] According to an embodiment, the electronic device (100) may include a transceiver (1120), a memory (1140), and a processor (1160). The electronic device (100) illustrated in FIG. 11 only illustrates components related to the present embodiment. Therefore, those skilled in the art will appreciate that, in addition to the components illustrated in FIG. 11, other general-purpose components may be included. In the embodiment, the transceiver (1120) may be included in a communication device. Additionally, in the embodiment, the processor (1160) may be included in a controller.

[0169] The transceiver (1120) is a device for performing wired / wireless communication and can communicate with external electronic devices. The external electronic devices may be terminals or servers. In addition, communication technologies used by the transceiver (1120) may include GSM (Global System for Mobile communication), CDMA (Code Division Multi Access), LTE (Long Term Evolution), 5G, WLAN (Wireless LAN), Wi-Fi (Wireless-Fidelity), Bluetooth (Bluetooth), RFID (Radio Frequency Identification), Infrared Data Association (IrDA), ZigBee, NFC (Near Field Communication), etc.

[0170] The processor (1160) can control the overall operation of the electronic device (100) and process data and signals. The processor (1160) can be composed of at least one hardware unit. In addition, the processor (1160) can operate by one or more software modules generated by executing program codes stored in the memory (1140). The processor (1160) can include a memory, and the processor (1160) can control the overall operation of the electronic device (100) and process data and signals by executing program codes stored in the memory.

[0171] The processor (1160) may obtain information about an application, and based on the information about the application, generate a relationship graph between a plurality of components corresponding to one or more pages in a first domain of the application, identify at least one first component of a first type, at least one second component of a second type, and at least one third component of a third type among the plurality of components, identify a coverage ratio of at least one first component in the first domain, and provide information about the coverage ratio.

[0172] The electronic device according to the above-described embodiments may include a processor, a memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with an external device, a user interface device such as a touch panel, a key, a button, etc. The methods implemented as software modules or algorithms may be stored on a computer-readable recording medium as computer-readable codes or program instructions executable on the processor. Here, the computer-readable recording medium includes a magnetic storage medium (e.g., read-only memory (ROM), random-access memory (RAM), floppy disk, hard disk, etc.) and an optical reading medium (e.g., CD-ROM, DVD: Digital Versatile Disc)). The computer-readable recording medium may be distributed to computer systems connected to a network, so that the computer-readable code may be stored and executed in a distributed manner. The medium may be readable by a computer, stored in a memory, and executed by a processor.

[0173] The present embodiment may be represented by functional block configurations and various processing steps. These functional blocks may be implemented by various hardware and / or software configurations that perform specific functions. For example, the embodiment may employ direct circuit configurations such as memory, processing, logic, look-up tables, etc., which may perform various functions under the control of one or more microprocessors or other control devices. Similarly, the present embodiment may be implemented in a programming or scripting language such as C, C++, Java, assembler, etc., including various algorithms implemented as a combination of data structures, processes, routines, or other programming configurations. Functional aspects may be implemented as algorithms that execute on one or more processors. Furthermore, the present embodiment may employ conventional techniques for electronic configuration, signal processing, and / or data processing. Terms such as "mechanism," "element," "means," and "composition" can be used broadly and are not limited to mechanical or physical structures. These terms can also encompass a series of software routines, such as those associated with a processor.

[0174] The above-described embodiments are merely examples, and other embodiments may be implemented within the scope of the claims set forth below.

Claims

1. In the method of providing information of an electronic device, Step of obtaining information about the application; A step of generating a relationship graph between a plurality of components corresponding to one or more pages within a first domain of the application based on information about the application; A step of identifying at least one first component of a first type, at least one second component of a second type, and at least one third component of a third type among the plurality of components; A step of checking the coverage ratio of at least one first component in the first domain; and An information providing method comprising the step of providing information regarding the above coverage ratio.

2. In paragraph 1, The first type of component includes a component that matches one or more of the set components, The second type of component includes a component that does not match one or more of the components but is set to be replaced by the one or more components, A method for providing information, wherein the third type of component includes a component that is not matched to one or more of the components and is set not to be replaced by the one or more components.

3. In the first paragraph, the step of checking the coverage ratio is: A step of filtering out at least one third component among the plurality of components; A step of checking the number of at least one first component and the number of at least one second component; and An information providing method comprising the step of determining the coverage ratio based on the number of at least one first component and the number of at least one second component.

4. In paragraph 3, Information about the above application includes an XML (extensible markup language) file, The step of generating a relationship graph between the plurality of components includes the step of generating a tree view of the plurality of views displayed on the one or more pages by parsing the XML file, A method for providing information, wherein the step of verifying at least one first component, at least one second component, and at least one third component includes the step of verifying at least one first view of the first type, at least one second view of the second type, and at least one third view of the third type among the plurality of views.

5. In paragraph 4, The step of checking the number of at least one first component and the number of at least one second component includes the step of checking the number of at least one first view and the number of at least one second view, An information providing method, wherein the coverage ratio is determined as a value obtained by dividing the number of the at least one first view by the sum of the number of the at least one first view and the number of the at least one second view.

6. In the fourth paragraph, the step of providing information on the coverage ratio is: An information providing method comprising the step of providing information about a dependency relationship of at least one second view based on a tree view of the plurality of views.

7. In paragraph 3, Information about the above application includes code about the application, The step of generating a relationship graph between the plurality of components includes the step of generating a call graph of the plurality of nodes corresponding to the one or more pages by parsing the code related to the application, A method for providing information, wherein the step of verifying at least one first component, at least one second component, and at least one third component includes the step of verifying at least one first node of the first type, at least one second node of the second type, and at least one third node of the third type among the plurality of nodes.

8. In paragraph 7, The step of checking the number of the at least one first component and the number of the at least one second component includes the step of checking the number of calls of the at least one first node and the number of calls of the at least one second node, An information providing method, wherein the coverage ratio is determined as a value obtained by dividing the number of calls of the at least one first node by the sum of the number of calls of the at least one first node and the number of calls of the at least one second node.

9. In the 7th paragraph, the step of providing information on the coverage ratio is: An information providing method, comprising the step of providing information about a call relationship of at least one second node based on a call graph of the plurality of nodes.

10. In the third paragraph, the coverage ratio is The area occupied by each of said at least one first component and said at least one second component on said one or more pages; The location of each of said at least one first component and said at least one second component within said one or more pages; and An information providing method, wherein at least one of the times at which each of the at least one first component and the at least one second component is exposed to the user is determined by further considering the time.

11. In the 10th paragraph, the coverage ratio is A method for providing information, wherein the higher the number of at least one first component, the larger the area occupied by the at least one first component, the closer the position of the at least one first component is to the center of the one or more pages, or the longer the time for which the at least one first component is exposed, the higher the determined value.

12. A non-transitory computer-readable recording medium having recorded thereon a program for executing the method of paragraph 1 on a computer.

13. As an electronic device, transceiver; memory; and A processor comprising: Obtain information about the application, Based on information about the application, a relationship graph is generated between a plurality of components corresponding to one or more pages within a first domain of the application, Among the plurality of components, at least one first component of the first type, at least one second component of the second type, and at least one third component of the third type are identified, Check the coverage ratio of at least one first component in the first domain, An electronic device providing information regarding the above coverage ratio.

Images