TWI884522B - Electronic apparatus and providing information method thereof - Google Patents

Abstract

The present invention provides a method for providing information by an electronic device. The information providing method may include the following steps: obtaining information of an application; generating a relationship diagram between a plurality of components corresponding to one or more pages in a first domain of the application based on the information of the application; confirming 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; confirming the coverage ratio of the at least one first component in the first domain; and providing information of the coverage ratio.

Description

Electronic device and information providing method thereof

The present invention relates to an electronic device for providing information on the ratio of components used in a specific page or a specific domain of an application and a control method thereof.

The trend of consumers purchasing items through online ordering rather than offline ordering is increasing, and the recent outbreak of COVID-19 has further accelerated this trend.

Consumers can install applications on their respective terminals and use the applications to purchase items. As mentioned above, there are multiple applications used by consumers, and multiple companies are providing related services and competing with each other. In such a competitive situation, in order to maintain the interest of consumers compared with the services provided by other companies, it is necessary to improve the design of the pages provided in the application.

An application provides multiple pages, and each page can be designed using multiple components. In this case, if the design of the components commonly provided in multiple pages is systematically managed, the user experience (UX) of consumers will be increased, which can increase the utilization rate of the application.

Therefore, it is necessary to provide operators with information on whether the designs of multiple components included in multiple pages provided in the application are rendered consistently.

[The problem the invention is trying to solve]

The disclosed embodiment is intended to provide an electronic device and an information providing method thereof. More specifically, the object is to provide an electronic device and a control method thereof for providing information of the ratio of components of a setting used in a specific page or a specific domain of an application.

The technical problems to be solved by this embodiment are not limited to the technical problems described above, and other technical problems can be introduced based on the following embodiments. [Technical means for solving the problem]

One aspect of the present invention can provide an information providing method, which includes the following steps: obtaining information of an application; based on the above application information, generating a relationship diagram between a plurality of components corresponding to one or more pages in a first domain of the above application; confirming 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 above plurality of components; confirming the coverage ratio of the above at least one first component in the above first domain; and providing information of the above coverage ratio.

Furthermore, in one embodiment of the present invention, a method for providing information may be provided, wherein the above-mentioned first type of components includes components that match one or more components that are set, the above-mentioned second type of components includes components that do not match one or more components but are set to be replaced by one or more components, and the above-mentioned third type of components includes components that do not match one or more components and are set not to be replaced by one or more components.

Furthermore, in one embodiment of the present invention, a method for providing information may be provided, wherein the step of confirming the coverage ratio includes the following steps: filtering out the at least one third component among the plurality of components; confirming the number of the at least one first component and the number of the at least one second component; and determining the coverage ratio based on the number of the at least one first component and the number of the at least one second component.

Furthermore, in one embodiment of the present invention, a method for providing information may be provided, wherein the information of the above-mentioned application includes an XML (extensible markup language) file, and the step of generating a relationship diagram between the above-mentioned multiple components includes the following steps: by parsing the above-mentioned XML file, a tree view of multiple views displayed on the above-mentioned one or more pages is generated; the step of confirming the above-mentioned at least one first component, the above-mentioned at least one second component and the above-mentioned at least one third component includes the following steps: confirming at least one first view of the above-mentioned first type, at least one second view of the above-mentioned second type and at least one third view of the above-mentioned third type in the above-mentioned multiple views.

Furthermore, in one embodiment of the present invention, a method for providing information may be provided, wherein the step of confirming the number of the at least one first component and the number of the at least one second component includes the following steps: confirming the number of the at least one first view and the number of the at least one second view; 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.

Furthermore, in one embodiment of the present invention, an information providing method may be provided, wherein the step of providing the information of the above-mentioned coverage ratio includes the following steps: based on the tree view of the above-mentioned multiple views, providing the information of the subordinate relationship of the above-mentioned at least one second view.

Furthermore, in one embodiment of the present invention, a method for providing information may be provided, wherein the information of the above-mentioned application includes the code of the application, and the step of generating a relationship diagram between the above-mentioned multiple components includes the following steps: by parsing the code of the above-mentioned application, a call graph of multiple nodes corresponding to the above-mentioned one or more pages is generated; the step of confirming the above-mentioned at least one first component, the above-mentioned at least one second component and the above-mentioned at least one third component includes the following steps: confirming at least one first node of the above-mentioned first type, at least one second node of the above-mentioned second type and at least one third node of the above-mentioned third type among the above-mentioned multiple nodes.

Furthermore, in one embodiment of the present invention, a method for providing information may be provided, wherein the step of confirming the number of the at least one first component and the number of the at least one second component includes the following steps: confirming the number of calls of the at least one first node and the number of calls of the at least one second node; 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.

Furthermore, in one embodiment of the present invention, an information providing method may be provided, wherein the step of providing the above-mentioned coverage ratio information further includes the following step: based on the call graph of the above-mentioned plurality of nodes, providing the above-mentioned call relationship information of the at least one second node.

Furthermore, in one embodiment of the present invention, a method for providing information may be provided, wherein the coverage ratio is further determined by taking into account at least one of the following factors: the areas respectively occupied by the at least one first component and the at least one second component in the one or more pages; the respective positions of the at least one first component and the at least one second component in the one or more pages; and the time when the at least one first component and the at least one second component are respectively exposed to the user.

Furthermore, in one embodiment of the present invention, a method for providing information can be provided, wherein the greater the number of the 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 exposure time of the at least one first component, the higher the coverage ratio is determined to be.

Another aspect of the present invention may provide an electronic device, which includes a transceiver, a memory and a processor. The processor is as follows: obtains information about an application, generates a relationship diagram 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, confirms 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, confirms the coverage ratio of the at least one first component in the first domain, and provides information on the coverage ratio.

Another aspect of the present invention is to provide a computer-readable recording medium that records a program for implementing a method implemented by an electronic device.

Specific matters of other embodiments are included in the detailed description and drawings. [Effects of the invention]

According to the circumstances of the proposed embodiments, one or more of the following effects can be expected.

According to the embodiment of the present specification, multiple operators who manage multiple pages of the domain provided by the application can efficiently manage each page. Specifically, the operator who manages each page can design the page using the set user interface component, and the design consistency of the multiple pages provided in the application can be improved.

Furthermore, in the case of the embodiment of the present specification, the electronic device provides information on the ratio of components used by the domain in the application to the components corresponding to the set list, thereby uniformly designing the components of the domain to make it more convenient for operators. Therefore, the overall page is managed consistently and systematically, thereby improving the user experience (UX) of users using the application.

Furthermore, in the case of the embodiment according to the present specification, the electronic device provides information on the rendering path or call path of a component of a type that should be replaced by one or more set components, thereby allowing an operator to more easily replace the component.

The effects of the invention are not limited to the effects mentioned above. A person with common sense in the technical field can clearly understand other effects not mentioned according to the description of the invention patent application scope.

The terms used in the embodiments are common terms that are currently widely used as much as possible in consideration of the functions of the present invention, but these terms may vary according to the intentions of technicians in this field or precedents, the emergence of new technologies, etc. In addition, in specific cases, there are terms that the applicant arbitrarily selects. In such cases, their meanings will be described in detail in the corresponding description section. Therefore, the terms used in the present invention should be defined based on the meanings of the terms and the overall content of the present invention, rather than simply based on the names of the terms.

Throughout the specification, when it is described that a certain part “includes” a certain constituent element, unless there is a special description to the contrary, it means that other constituent elements may be further included, rather than excluding other constituent elements.

The expression "at least one of a, b, and c" recorded throughout the specification may include "a alone", "b alone", "c alone", "a and b", "a and c", "b and c" or "a, b, and c".

The "terminal" mentioned below can be implemented by a computer or a portable terminal, and the computer or portable terminal can be connected to a server or other terminal via a network. Here, the computer includes, for example, a notebook computer, a desktop computer, a laptop computer, etc. installed with a web browser. The portable terminal is a wireless communication device that ensures portability and mobility, for example, it may include communication terminals such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), LTE (Long Term Evolution), and all types of handheld wireless communication devices such as smart phones and tablet PCs (Personal Computers).

Hereinafter, the embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those with common knowledge in the technical field can easily implement the present invention. However, the present invention can be implemented in various different ways and is not limited to the embodiments described here.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG1 shows a system of an embodiment.

1, the system may include at least one of an electronic device 100, a user terminal 120, an operator terminal 140, and a network 160. On the other hand, the system shown in FIG1 only represents the components related to the present embodiment. Therefore, those with common sense in the technical field related to the present embodiment can understand that in addition to the components shown in FIG1, general components may be further included.

The electronic device 100 is a device that constructs and provides various information. The electronic device 100 can provide the constructed information as a web page or application screen, or provide the information in a form that can be displayed as a web page or application screen on a receiving terminal.

According to one embodiment, the electronic device 100 can provide information about the coverage ratio of components set in at least one domain of the application. For example, the electronic device 100 can obtain information about the application and, based on the information about the application, generate a relationship diagram between a plurality of components corresponding to one or more pages in the first domain of the application. Thereafter, the electronic device 100 can confirm at least one first component of the first type and at least one second component of the second type among the plurality of components, confirm the coverage ratio of at least one first component in the first domain, and provide information about the coverage ratio.

The user terminal 120 is a terminal used by each user. The user can use the terminal 120 to access the services provided by the network 160. For example, the electronic device 100 can provide a platform or application for ordering various items to the user terminal 120. The user can use the application installed in the user terminal 120 to order various items.

The operator terminal 140 is a terminal used by each operator. The operator can use each terminal 140 to confirm the coverage ratio information of the components set in one or more domains of the application. For example, the operator terminal 140 provides a user interface based on the information received from the electronic device 100, and the user interface displays the coverage ratio information of the components set in each of the one or more domains of the application.

The user terminal 120, the operator terminal 140 and the electronic device 100 can communicate with each other in 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 the network is a comprehensive data communication network that enables the network components shown in FIG. 1 to communicate with each other smoothly, and may include a wired Internet, a wireless Internet and a mobile wireless communication network. Wireless communication may include, for example, Wi-Fi, Bluetooth, Bluetooth low energy, ZigBee, WFD (Wi-Fi Direct), UWB (ultra wideband), infrared communication (IrDA), NFC (Near Field Communication), etc., but is not limited thereto.

FIG. 2 is a diagram for explaining a process in which the electronic device 100 provides information on the coverage ratio of a component configured in at least one domain of an application according to an embodiment.

According to one embodiment, the electronic device 100 can obtain information of the application. More specifically, the electronic device 100 can obtain a code or file for implementing at least one domain of the application.

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

On the other hand, the application code 240 may include Java code or Kotlin code, but the type of code included in the application code 240 is not limited to the above content.

According to one embodiment, the electronic device 100 may generate a relationship graph between a plurality of components corresponding to one or more pages in at least one domain of the application based on the information of the application.

For example, the XML analysis module 200 can generate a tree view of a plurality of views displayed on one or more pages in the first domain by parsing the obtained XML file 230. Here, a view is a basic component of a user interface displayed on a display, and may include various types of user interface components such as text, images, input fields, icons, or buttons.

For another example, the code analysis module 210 can generate a call graph of multiple nodes corresponding to one or more pages in the first domain by parsing the obtained application code 240. At this time, the node can include functions, classes or methods included in the application code 240.

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 components set among a plurality of components as a first type of component. Furthermore, the electronic device 100 can identify a component that does not match one or more components but is set to be replaced by one or more components among a plurality of components as a second type of component.

For example, the XML parsing module 200 may identify a view that matches one or more components among a plurality of views as a view of the first type, and may identify a view that does not match one or more components but is set to be replaced by one or more components as a view of the second type.

For another example, the code analysis module 210 may identify nodes among the plurality of nodes that match one or more components as nodes of the first type, and may identify nodes that do not match one or more components but are set to be replaced by one or more components as nodes of the second type.

On the other hand, the first type of component can be represented as an RDS (rocket design system) component as a user interface component designed in a manner that meets the set criteria, and the second type of component can be represented as a Non-RDS component as a user interface component that does not meet the set criteria. However, the terms used to represent them are not limited to the above.

According to one embodiment, the electronic device 100 may confirm the number of components of the first type and the number of components of the second type. For example, the XML analysis module 200 may confirm the number of views of the first type and the number of views of the second type. Alternatively, the code analysis module 210 may confirm the number of calls of nodes of the first type and the number of calls of nodes of the second type.

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

For example, in the case where the first domain of the application is implemented by the XML file 230, the data integration module 220 may obtain information of 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 may determine the following value as the coverage ratio, that is, 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.

For another example, when the first domain of the application is implemented by the code 240 of the application, the data integration module 220 may obtain information on the number of calls of the first type of nodes and the number of calls of the second type of nodes from the code analysis module 210. Thereafter, the data integration module 220 may determine the following value as the coverage ratio, that is, the value obtained by dividing the number of calls of the first type of nodes by the sum of the number of calls of the first type of nodes and the number of calls of the second type of nodes.

For another example, when the first domain of the application is implemented by the XML file 230 and the code 240 of the application, the data integration module 220 can obtain information on 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 on 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 the following value as the coverage ratio, that is, the 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.

According to one embodiment, the electronic device 100 may provide coverage ratio information 260 based on application information. For example, the electronic device 100 may provide a user interface through the operator terminal 140, and the user interface displays the coverage ratio information of the first type of components in each of more than one domain of the application.

According to one embodiment, the electronic device 100 may provide information of the result of analyzing at least one domain of the application. More specifically, the electronic device 100 may provide at least one of the information 270 of the view rendering path, the information 280 of the view position, and the information 290 of the function call path.

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

FIG3 is a diagram for explaining a process of providing information of a coverage ratio of a component set in at least one domain of an application by an electronic device 100 according to an embodiment. Contents repeated with FIG2 are briefly explained or omitted.

According to one embodiment, the XML parsing module 300 may obtain code or files for implementing at least one domain of the application. For example, the XML parsing module 300 may obtain an XML file 305 for implementing the first domain of the application.

According to one embodiment, the XML analysis module 300 may generate a tree view 315 of a plurality of views corresponding to one or more pages in at least one domain of the application based on the XML file 305. For example, the parsing module 310 may generate the tree view 315 by parsing the obtained XML file 305, and the tree view 315 indicates the dependency relationship between the first view to the ninth view of the one or more pages displayed in the first domain.

At this time, the tree view may represent a diagram that represents the subordinate relationship when rendering multiple views as a hierarchical structure. For example, referring to FIG. 3 , in order to render the fifth view, the first view and the second view should be rendered first, so the fifth view may have a subordinate relationship with the first view and the second view, and it can be represented in the tree view 315 with a structure of the first view → the second view → the fifth view. On the other hand, the tree view can be used interchangeably with the view tree, etc., but the terms used to represent it are not limited to the above content.

According to one embodiment, the XML parsing module 300 can confirm the type of each of the plurality of views. More specifically, the XML parsing module 300 can confirm a view of type 1, a view of type 2, and a view of type 3 among the plurality of views based on whether they match one or more components set and whether they are set to be replaced by one or more components set.

For example, referring to FIG3 , the XML analysis module 300 may confirm the 5th view, the 6th view, the 7th view, and the 9th view that match one or more components set among the plurality of views as views of type 1. Furthermore, the XML analysis module 300 may confirm the 3rd view and the 8th view that do not match one or more components but are set to be replaced by one or more components as views of type 2. The XML analysis module 300 may confirm the 1st view, the 2nd view, and the 4th view that do not match one or more components and are set not to be replaced by one or more components as views of type 3.

According to one embodiment, the XML parsing module 300 may filter views of type 3 among the plurality of views. For example, the filtering module 320 may exclude the first view, the second view, and the fourth view that are confirmed as views of type 3. However, the process of filtering views of type 3 may be omitted.

According to one embodiment, the XML parsing module 300 may confirm the number of views of the first type and the number of views of the second type among the plurality of views. For example, the counting module 350 may confirm that the number of views of the first type is 4 and the number of views of the second type is 2.

According to one embodiment, the XML analysis module 300 confirms the reference information 345 based on at least one of the application code 325 and the JAR file 330, and further considers the information, thereby confirming 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 can confirm the number of times the views of the first type and the views of the second type included in the tree view 315 are rendered in the second domain. Thereafter, the counting module 350 further considers the number of renderings obtained from the reference analysis module 340, thereby confirming the number of views of the first type and the number of views of the second type. However, in the case of calculating only the coverage ratio of the view of the first type in the first domain, the process of generating or considering the reference information may be omitted.

According to one embodiment, the XML parsing module 300 may provide information 355 of the number of views. For example, the counting module 350 may provide the information 355 of the number of views to the data integration module, and the information 355 of the number of views includes information that the number of views of the first type is 4 and the number of views of the second type is 2.

According to one embodiment, the XML parsing module 300 may provide path information 365. More specifically, the XML parsing module 300 may provide information on the dependency of the views of the second type or information on the rendering path 365 based on the tree view 315 of the plurality of views.

For example, the path identification module 360 may provide the path information 365 to the data integration module, the path information 365 including information that the subordinate relationship of the 3rd view of the 2nd type is the 1st view → the 3rd view and the subordinate relationship of the 8th view of the 2nd type is the 1st view → the 4th view → the 8th view.

As described above, the XML parsing module 300 provides information on the rendering path of the second type of view that should be replaced by one or more components set, whereby the operator can more easily replace the second type of view.

On the other hand, the XML parsing module 300 of FIG. 3 may correspond to the XML parsing module 200 of FIG. 2 .

FIG4 is a diagram for explaining a process of providing information of a coverage ratio of a component set in at least one domain of an application by an electronic device 100 according to an embodiment. Contents repeated with FIG2 are briefly explained or omitted.

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 for implementing the application of the first domain of the application.

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 in at least one domain of the application based on the application code 410. For example, the parsing module 420 may generate the call graph 430 by parsing the obtained application code 410, and the call graph 430 indicates the call relationship between the first node to the eighth node corresponding to one or more pages in the first domain.

At this time, the call graph may represent a weighted directed acyclic graph, which represents the call relationship and call times between a plurality of nodes. For example, referring to FIG. 4 , the code 410 of the application may be written such that the second node calls the third node three times and the third node calls the fourth node two times, which can be represented in the call graph 430 by the structure of the second node → (3) the third view → (2) the fourth view. In addition, the first node, the second node, the third node and the fifth node corresponding to the function of executing the view rendering function among the plurality of nodes may be represented by asterisks.

According to one embodiment, the code analysis module 400 can confirm the type of each of the plurality of nodes. More specifically, the code analysis module 400 can confirm the first type of node, the second type of node, and the third type of node among the plurality of nodes based on whether they match one or more components set and whether they are set to be replaced by one or more components set.

For example, referring to FIG. 4 , the code analysis module 400 may confirm the 4th node among the plurality of nodes that matches one or more components set as a node of the first type. Furthermore, the code analysis module 400 may confirm the 7th node and the 8th node that do not match one or more components but are set to be replaced by one or more components as nodes of the second type. The code analysis module 400 may confirm the 1st node, the 2nd node, the 3rd node, the 5th node, and the 6th node that do not match one or more components and are set not to be replaced by one or more components as nodes of the third type.

According to one embodiment, the code analysis module 400 may filter the nodes of the third type among the 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 that are confirmed as the nodes of the third type. However, the process of filtering the nodes of the third type may be omitted.

According to one embodiment, the code analysis module 400 can confirm the number of calls of the first type of nodes and the number of calls of the second type of nodes among the plurality of nodes. More specifically, the code analysis module 400 can confirm how many times the node corresponding to the function of executing the view rendering function calls the first type of nodes and the second type of nodes respectively.

For example, the counting module 450 may confirm that the first node calls the fourth node of the first type once, the second node calls the fourth node of the first type six times (3×2) through the third node, and the third node calls the fourth node of the first type twice. In addition, the counting module 450 may confirm that the fifth node calls the seventh node of the second type once through the sixth node and calls the seventh node of the second type twice (1×2) through the eighth node. The counting module 450 may confirm that the fifth node calls the eighth node of the second type once.

According to one embodiment, the code analysis module 400 may provide the node's call count information 460. For example, the counting module 450 may provide the node's call count information 460 to the data integration module, and the node's call count information 460 includes information that the call count of the first type of node is 9 and the call count of the second type of node is 4.

According to one embodiment, the code analysis module 400 may provide path information 480. More specifically, the code analysis module 400 may provide call path information 480 of the second type of nodes based on the call graph 430 of the plurality of nodes.

For example, the path identification module 470 may provide path information 480 to the data integration module, wherein the path information 480 includes information that the call path of the 7th node of the second type is the 5th node→the 6th node→the 7th node, the 5th node→the 8th node→the 7th node, and the call path of the 8th node of the second type is the 5th node→the 8th node.

As described above, the code analysis module 400 provides information on the call path of the second type of node that should be replaced by one or more components set, whereby the operator can easily replace the second type of node.

On the other hand, the code analysis module 400 of FIG. 4 may correspond to the code analysis module 210 of FIG. 2 .

FIG5 is a diagram for explaining a process of determining the coverage ratio of a component configured in at least one domain of an application by the electronic device 100 according to an embodiment. Contents that are repeated with FIG2 may be briefly described or omitted.

According to one embodiment, the electronic device 100 can obtain a code or file for implementing at least one domain of the application. For example, the electronic device 100 can obtain an XML file for implementing the first domain of the application.

According to one embodiment, the electronic device 100 can generate a tree view of a plurality of views corresponding to one or more pages in at least one domain of the application based on the XML file. For example, referring to FIG. 5 , the electronic device 100 can generate a tree view by parsing the obtained XML file, and the tree view represents the subordinate relationship between the first view 500, the second view 520, the third view 540, the fourth view 560, and the fifth view 580 displayed on the first page of the first domain of the application.

According to one embodiment, the electronic device 100 can confirm the type of each of the plurality of views. More specifically, the electronic device 100 can confirm the first type of view and the second type of view in the plurality of views based on whether it matches one or more components set and whether it is set to be replaced by one or more components set.

For example, referring to Fig. 5, the electronic device 100 may identify the fourth view 560 and the fifth view 580 that match one or more components set among the plurality of views as views of the first type. In addition, the electronic device 100 may identify the first view 500, the second view 520, and the third view 540 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.

According to one embodiment, the electronic device 100 can confirm the number of views of the first type and the number of views of the second type among the plurality of views. For example, the electronic device 100 can confirm that the number of views of the first type is 2 and the number of views of the second type is 3.

According to one embodiment, the electronic device 100 may determine the coverage ratio of the components of the first type in at least one domain of the application based on the number of components of the first type and the number of components of the second type. More specifically, the electronic device 100 may determine the coverage ratio as a 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.

For example, the electronic device 100 may determine the coverage ratio of the first type of components in the first domain as 2/5 or 40% obtained by dividing the number of views of the first type, i.e., 2, by the sum of the number of views of the first type and the number of views of the second type, i.e., 5.

On the other hand, although FIG. 5 shows that the first page of the first domain of the application corresponds to the first view 500, this is only an example, and whether the page itself corresponds to a view may vary depending on how the code or file used to implement the module is written.

6a to 6c are diagrams for explaining a process of determining the coverage ratio of a component configured in at least one domain of an application by the electronic device 100 according to an embodiment. The contents repeated with FIG. 2 may be briefly described or omitted.

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

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

According to one embodiment, the electronic device 100 can confirm the type of each of the plurality of views. More specifically, the electronic device 100 can confirm the first type of view, the second type of view, and the third type of view among the plurality of views based on whether they match one or more components set and whether they are set to be replaced by one or more components set.

For example, referring to FIG. 6a, the electronic device 100 may confirm the second view 634, the sixth view 642, the seventh view 644, and the eighth view 646 that match one or more components set among the plurality of views displayed on the first page 600 as views of the first type. Furthermore, the electronic device 100 may confirm the third view 636, the ninth view 648, the tenth view 650, the eleventh view 652, and the twelfth view 654 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 electronic device 100 may confirm the first view 632, the fourth view 638, and the fifth view 640 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.

For another example, referring to FIG. 6 b , the electronic device 100 may 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 matched with one or more components set, among the plurality of views displayed on the second page 610, as views of the first type. Furthermore, the electronic device 100 may 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 not matched with one or more components but are set to be replaced by one or more components, as views of the second type.

For another example, referring to FIG. 6c , the electronic device 100 may identify the 25th view 680, the 28th view 686, the 29th view 688, the 31st view 692, and the 32nd view 694, which are matched with one or more components set, among the plurality of views displayed on the third page 620, as views of the first type. Furthermore, the electronic device 100 may identify the 26th view 682, the 27th view 684, the 30th view 690, and the 33rd view 696, which are not matched with one or more components but are set to be replaced by one or more components, as views of the second type.

According to one embodiment, the electronic device 100 may filter the views of the third type among the plurality of views. For example, the electronic device 100 may exclude the first view 632, the fourth view 638, and the fifth view 640 that are confirmed as the views of the third type. However, the process of filtering the views of the third type may be omitted.

According to one embodiment, the electronic device 100 can confirm the number of views of the first type and the number of views of the second type in a plurality of views. More specifically, the electronic device 100 can confirm the total number of views of the first type and the total number of views of the second type corresponding to each of more than one page in at least one domain.

For example, the electronic device 100 can confirm 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 confirm 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.

According to one embodiment, the electronic device 100 may confirm the coverage ratio of the components of the first type in at least one domain of the application based on the number of components of the first type and the number of components of the second type. More specifically, the electronic device 100 may determine the coverage ratio as 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.

For example, the electronic device 100 may determine the coverage ratio of the Type 1 component in the SDP domain as 15/30 or 50% obtained by dividing the total number of Type 1 views, i.e., 15, by the sum of the total number of Type 1 views and the total number of Type 2 views, i.e., 30.

7a and 7b are diagrams for explaining a process of determining the coverage ratio of a component configured in at least one domain of an application by an electronic device 100 according to an embodiment. The contents repeated with FIG. 2 are briefly explained or omitted.

According to one embodiment, the electronic device 100 can determine the coverage ratio of the components of the first type in at least one domain of the application based on the number of components of the first type and the number of components of the second type. More specifically, the more components of the first type there are, the higher the coverage ratio of the components of the first type can be determined by the electronic device 100.

According to one embodiment, the electronic device 100 can determine the coverage ratio of the first type of components in at least one domain of the application based on the areas occupied by the first type of components and the second type of components in the page, respectively. More specifically, the larger the area occupied by the first type of components in the page, the higher the coverage ratio of the first type of components can be determined by the electronic device 100.

For example, referring to FIG. 7a , the electronic device 100 can confirm that the ratio of the areas 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 in the page is 1:1:2. Therefore, the electronic device 100 can determine the coverage ratio of the components of the first type as 2/(1+1+2)=2/4=50%.

According to one embodiment, the electronic device 100 can determine the coverage ratio of the first type of components in at least one domain of the application based on the respective positions of the first type of components and the second type of components in the page. More specifically, the closer the position of the first type of components is to the center of the page, the higher the coverage ratio of the first type of components can be determined by the electronic device 100.

For example, referring to FIG. 7b , the electronic device 100 may determine that the ratio of the distance from the center of each of the fourth view 730 and the 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 the components close to the center of the page, the electronic device 100 may subtract 1 from the ratio of the distance from the center of each component to the center of the page to obtain (1-0.5):(1-0.5):(1-0)=0.5:0.5:1 as the value applied to each component. Therefore, the electronic device 100 may determine the coverage ratio of the components of the first type to be 1/(0.5+0.5+1)=1/2=50%.

According to one embodiment, the electronic device 100 can determine the coverage ratio of the first type of components in at least one domain of the application based on the time when the first type of components and the second type of components are respectively exposed to the user. More specifically, the longer the exposure time of the first type of components is, the higher the coverage ratio of the first type of components can be determined by the electronic device 100.

For example, the electronic device 100 may receive information about the time when the first type of components and the second type of components are respectively exposed to the user from the user terminal. Thereafter, the electronic device 100 may determine the coverage ratio of the first type of components based on the ratio of the time when the first type of components and the second type of components are respectively exposed to the user. At this time, the time when the component is exposed to the user means the time when the component is actually displayed on the display of the user terminal, and may be determined differently according to the user's scrolling action or the icon selected by the user.

According to one embodiment, the electronic device 100 applies different weighting values to the number of components of the first type and the second type, i.e., the first factor; the area occupied by components of the first type and the second type, respectively, on a page, i.e., the second factor; the position of components of the first type and the second type, respectively, on the page, i.e., the third factor; and the time that components of the first type and the second type, respectively, are exposed to the user, i.e., the fourth factor, thereby confirming the coverage ratio of components of the first type in at least one domain of the application.

For example, the electronic device 100 may determine the weighted values applied to the third factor and the fourth factor to be 0 based on the setting information received from the operator terminal. Therefore, the electronic device 100 may determine the coverage ratio of the first type of components in at least one domain by considering only the number of the first type of components and the second type of components, i.e., the first factor, and the areas occupied by the first type of components and the second type of components, respectively, in the page, i.e., the second factor.

FIG. 8 is a diagram for explaining a process of determining a coverage ratio of a component configured in at least one domain of an application by the electronic device 100 according to an embodiment.

According to one embodiment, the electronic device 100 may obtain a code or file for implementing at least one domain of an application. More specifically, the electronic device 100 may obtain a code or file respectively included in a plurality of modules for implementing at least one domain.

For example, the electronic device 100 may obtain an XML file, java code, kotlin code, or JAR file included in the first module for implementing the first area 820 of the first domain 800. Alternatively, the electronic device 100 may obtain an XML file, java code, kotlin code, or JAR file included in the second module for implementing the 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 the third module for implementing the third area 860 of the first domain 800.

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

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

According to one embodiment, the electronic device 100 may filter the views of the third type from the plurality of views. For example, the electronic device 100 may exclude the views that are confirmed to be the views of the third type from the plurality of first views, the plurality of second views, and the plurality of third views. However, the process of filtering the views of the third type may be omitted.

According to one embodiment, the electronic device 100 can confirm the number of views of the first type and the number of views of the second type in the plurality of views. For example, the electronic device 100 can confirm 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.

According to one embodiment, the electronic device 100 may confirm the coverage ratio of the components of the first type for each of the areas included in at least one domain of the application based on the number of components of the first type and the number of components of the second type. More specifically, the electronic device 100 may determine the following value as the coverage ratio, i.e., a value obtained by dividing the number of views of the first type displayed in each of the areas included in at least one domain by the sum of the number of views of the first type and the number of views of the second type.

For example, the electronic device 100 may determine the coverage ratio of the first type of components in the first area 820 as 20% obtained by dividing the number of views of the first type displayed in the first area 820 by the sum of the number of views of the first type and the number of views of the second type. Alternatively, the electronic device 100 may determine the coverage ratio of the first type of components in the second area 840 as 100% obtained by dividing the number of views of the first type displayed in the second area 840 by the sum of the number of views of the first type and the number of views of the second type. The electronic device 100 may determine the following value as the coverage ratio of the first type of components in the third area 860, namely, 50% obtained by dividing the number of views of the first type displayed in the third area 860 by the sum of the number of views of the first type and the number of views of the second type.

According to one embodiment, the electronic device 100 applies different weighting values to each of the at least one region included in the at least one domain, thereby confirming the coverage ratio of the first type of components in the at least one domain of the application. More specifically, the electronic device 100 applies different weighting values to each of the at least one region based on the area occupied by the at least one region, the location of the at least one region, and the time when the at least one region is exposed to the user, thereby confirming the coverage ratio of the first type of components in the at least one domain of the application.

For example, the electronic device 100 may apply different weighting values to the first area 820, the second area 840, and the third area 860 according to the areas respectively occupied by more than one area based on the setting information received from the operator terminal. Therefore, the electronic device 100 may confirm that the ratio of the areas occupied by the first area 820, the second area 840, and the third area 860 is 1:2:1, and determine the coverage ratio of the first type of components as (1×20%＋2×100%＋1×50%)/(1＋2＋1)＝67.5%.

FIG. 9 shows an example of a user interface 900 provided by the electronic device 100 according to an embodiment.

According to one embodiment, the electronic device 100 can provide a user interface 900 to an operator through an operator terminal, and the user interface 900 includes information about the coverage ratio of components set in one or more domains of an application. For example, referring to FIG. 9 , the operator terminal can receive information in the form of a web page or an application screen from the electronic device 100, and display the user interface 900 on a display based on the received information. The user interface 900 includes an area that displays information about the coverage ratio of components set in the entire application or an area that displays information about the coverage ratio of components set in one or more domains of an application.

According to one embodiment, the user interface 900 may include an area 910 for setting parameters of the application. For example, the area 910 may include an area for setting the version of the application, an area for setting the platform of the user terminal in which the application is installed, and an area for setting the domain.

According to one embodiment, the user interface 900 may include an area 920 that displays information about the coverage ratio of components set in the entire application. For example, when the 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, the following information may be displayed in area 920: the coverage ratio of the first type of components of the entire application of version 7.7.1 installed on the Android platform of the user terminal is 8%.

According to one embodiment, the user interface 900 may include an area 930 that displays information about the coverage ratio of components set in a specific domain of the application. For example, when the operator sets the version of the application to 7.7.1 and the domain to domain-cart in area 910, the following information may be displayed in area 930: the coverage ratio of components of type 1 in the domain-cart of the application of version 7.7.1 is 13.2%. In addition, the following information is also displayed in area 930: the coverage ratio of components of type 1 in the domain-cart of the application of version 7.6.9, which is a version before 7.7.1, is 12.9%, thereby providing information about the improvement ratio.

According to one embodiment, the user interface 900 may include areas 940 and 950 for displaying information about the coverage ratio of components set in one or more domains of the application. For example, information about the coverage ratio of components of the first type in each of the plurality of domains of the application may be displayed in areas 940 and 950.

On the other hand, the specific example of the types and coverage ratios of the user interface components shown in FIG. 9 is only an example. Those having common sense in the technical field to which the present invention belongs should understand that the present invention can be implemented by examples different from the above contents.

Fig. 10 is a flow chart showing an information providing method of an electronic device according to an embodiment. For repeated contents, the above description can be applied.

In step S1000, the electronic device may obtain information of the application.

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

According to one embodiment, the information of the application may include the code of the application.

In step S1020, the electronic device may generate a relationship diagram between a plurality of components corresponding to one or more pages in the first domain of the application based on the information of the application.

According to one embodiment, when generating a relationship diagram between a plurality of components, the electronic device may parse an XML file to generate a tree view of a plurality of views displayed on more than one page.

According to one embodiment, when generating a relationship graph between a plurality of components, the electronic device may parse the code of the application program to generate a call graph of a plurality of nodes corresponding to one or more pages.

In step S1040, the electronic device may 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.

According to one embodiment, the first type of components may include components that match more than one component that is set, the second type of components includes components that do not match more than one component but are set to be replaced by more than one component, and the third type of components includes components that do not match more than one component and are set not to be replaced by more than one component.

According to one embodiment, when confirming at least one first component, at least one second component, and at least one third component, the electronic device can confirm 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.

According to one embodiment, when confirming at least one first component, at least one second component, and at least one third component, the electronic device can confirm 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 a plurality of nodes.

In step S1060, the electronic device may confirm a coverage ratio of at least one first component in the first domain.

According to one embodiment, when confirming the coverage ratio, the electronic device can filter out at least one third component among the plurality of components, confirm 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.

According to one embodiment, when confirming the number of at least one first component and the number of at least one second component, the electronic device can confirm the number of at least one first view and the number of at least one second view, and the coverage ratio is 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.

According to one embodiment, when confirming the number of at least one first component and the number of at least one second component, the electronic device can confirm the number of calls of at least one first node and the number of calls of at least one second node, and the coverage ratio is determined as the 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.

According to one embodiment, the coverage ratio can be determined by considering at least one of the following factors: the area occupied by at least one first component and at least one second component in one or more pages, the respective positions of at least one first component and at least one second component in one or more pages, and the time that at least one first component and at least one second component are exposed to the user.

According to one embodiment, the greater the number of at least one first component, the larger the area occupied by at least one first component, the closer the position of at least one first component is to the center of one or more pages, or the longer the exposure time of at least one first component, the higher the coverage ratio can be determined.

In step S1080, the electronic device may provide coverage ratio information.

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

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

FIG. 11 is a block diagram of an electronic device 100 according to an embodiment.

According to an embodiment, the electronic device 100 may include a transceiver 1120, a memory 1140, and a processor 1160. The electronic device 100 shown in FIG. 11 only shows the components related to the present embodiment. Therefore, those with common sense in the technical field related to the present embodiment can understand that in addition to the components shown in FIG. 11, other general components may be further included. In an embodiment, the transceiver 1120 may be included in a communication device. In addition, in an embodiment, the processor 1160 may be included in a controller.

The transceiver 1120 is a device for realizing wired/wireless communication and can communicate with an external electronic device. The external electronic device can be a terminal or a server. In addition, the communication technology used by the transceiver 1120 can include GSM (Global System for Mobile communication), CDMA (Code Division Multi Access), LTE (Long Term Evolution), 5G (5th Generation Mobile Communication Technology), WLAN (Wireless LAN), Wi-Fi (Wireless-Fidelity), Bluetooth™, RFID (Radio Frequency Identification), Infrared Data Association (IrDA), ZigBee, NFC (Near Field Communication), etc.

The processor 1160 can control the overall operation of the electronic device 100 and process data and signals. The processor 1160 can include at least one hardware unit. In addition, the processor 1160 can operate by executing one or more software modules generated by executing the program code stored in the memory 1140. The processor 1160 can include a memory, and the processor 1160 can execute the program code stored in the memory to control the overall operation of the electronic device 100 and process data and signals.

Processor 1160 can obtain information about the application, generate a relationship diagram between multiple components corresponding to one or more pages in the first domain of the application based on the application information, confirm 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 among the multiple components, confirm the coverage ratio of at least one first component in the first domain, and provide information on the coverage ratio.

The electronic device of the above embodiment may include a processor, a memory for storing and executing program data, a permanent storage such as a disk drive, a communication port for communicating with external devices, a user interface device such as a touch panel, a key, a button, etc. The method implemented by the software module or algorithm is stored in a computer-readable recording medium as a computer-readable code or program command that can be executed on the above processor. Here, as computer readable recording media, there are magnetic storage media (e.g., ROM (read-only memory), RAM (random-Access memory), floppy disk, hard disk, etc.) and optical readable media (e.g., CD-ROM, DVD, Digital Versatile Disc), etc.). Computer readable recording media are distributed in computer systems connected to the network, so that computer readable codes can be stored and executed in a distributed manner. The media can be read by the computer, stored in the memory and executed in the processor.

The present embodiment may be represented by a functional block structure and various processing steps. Such functional blocks may be implemented by different numbers of hardware and/or software structures that perform specific functions. For example, the embodiment may be implemented by an integrated circuit structure that can perform various functions such as memory, processing, logic, look-up tables, etc. through the control of one or more microprocessors or other control devices. The components may be executed by software programming or software components. Similarly, the present embodiment includes various algorithms implemented by a combination of data structures, programs, routines, or other programming structures, and can therefore be implemented by programming or scripting languages such as C, C++, Java, assembler, Python, etc. In terms of functions, it can be implemented by algorithms executed in one or more processors. In addition, the present embodiment can use prior art to perform electronic environment settings, signal processing and/or data processing, etc. Terms such as "mechanism", "component", "mechanism", and "configuration" can be used widely and are not limited to mechanical and physical configurations. The above terms can be associated with processors and include the meaning of a series of processes (routines) of software.

The above embodiment is only an example, and other embodiments may be implemented within the scope of the invention application described below.

100: Electronic device 120: User terminal 140: Operator terminal 160: Network 200: XML analysis module 210: Code analysis module 220: Data integration module 230: XML file 240: Application code 250: JAR file 260: Coverage ratio information 270: View rendering path information 280: View location information 290: Function call path information 300: XML analysis module 305: XML file 310: Parsing module 315: Tree view 320: Filter module 325: Application code 330: JAR file 340: Reference analysis module 345: Reference information 350: Counting module 355: Information about the number of views 360: Path identification module 365: Information about paths 400: Code analysis module 410: Application code 420: Parsing module 430: Call graph 440: Filtering module 450: Counting module 460: Information about the number of node calls 470: Path identification module 480: Information about paths 500: View 1 520: View 2 540: View 3 560: View 4 580: View 5 600: Page 1 610: Page 2 620: Page 3 632: View 1 634: View 2 636: View 3 638: View 4 640: View 5 642: View 6 644: View 7 646: View 8 648: View 9 650: View 10 652: View 11 654: View 12 656: View 13 658: View 14 660: View 15 662: View 16 664: View 17 666: View 18 668: View 19 670: View 20 672: View 21 674: View 22 676: View 23 678: View 24 680: View 25 682: View 26 684: View 27 686: View 28 688: View 29 690: View 30 692: View 31 694: View 32 696: View 33 700: View 1 710: View 2 720: View 3 730: View 4 740: View 5 750: View 6 800: Area 1 820: Area 1 840: Area 2 860: Area 3 900: User Interface 910: region 920: region 930: region 940: region 950: region 1120: transceiver 1140: memory 1160: processor S1000: step S1020: step S1040: step S1060: step S1080: step

FIG. 1 shows a system of an embodiment. FIG. 2 is a diagram for illustrating a process in which an electronic device of an embodiment provides information on the coverage ratio of a component set in at least one domain of an application. FIG. 3 is a diagram for illustrating a process in which an electronic device of an embodiment provides information on the coverage ratio of a component set in at least one domain of an application. FIG. 4 is a diagram for illustrating a process in which an electronic device of an embodiment provides information on the coverage ratio of a component set in at least one domain of an application. FIG. 5 is a diagram for illustrating a process in which an electronic device of an embodiment determines the coverage ratio of a component set in at least one domain of an application. Figures 6a to 6c are diagrams for illustrating a process of determining a coverage ratio of a set component in at least one domain of an application by an electronic device of an embodiment. Figures 7a to 7b are diagrams for illustrating a process of determining a coverage ratio of a set component in at least one domain of an application by an electronic device of an embodiment. Figure 8 is a diagram for illustrating a process of determining a coverage ratio of a set component in at least one domain of an application by an electronic device of an embodiment. Figure 9 shows an example of a user interface provided by an electronic device of an embodiment. Figure 10 shows a flow chart of an information providing method of an electronic device of an embodiment. Figure 11 shows a block diagram of an electronic device of an embodiment.

100: Electronic devices

200: XML analysis module

210: Code analysis module

220: Data integration module

230: XML file

240: Application code

250:JAR file

260: Coverage ratio information

270: Information about view rendering path

280: View location information

290: Function call path information

Claims (12)

A method for providing information, which is implemented by an electronic device, comprises the following steps: Obtaining information of an application; Based on the information of the application, generating a relationship diagram between a plurality of components corresponding to one or more pages in the first domain of the application; Confirming 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 among the plurality of components; Confirming the coverage ratio of the at least one first component in the first domain; and Providing information of the coverage ratio; Wherein the components of the first type include components that match one or more set components, The components of the second type include components that do not match the one or more components but are set to be replaced by the one or more components, The above-mentioned Type 3 components include components that do not match with one or more of the above-mentioned components and are not configured to be replaced by one or more of the above-mentioned components. The information providing method of claim 1, wherein the step of confirming the above-mentioned coverage ratio includes the following steps: Filtering the above-mentioned at least one third component among the above-mentioned multiple components; Confirming the number of the above-mentioned at least one first component and the number of the above-mentioned at least one second component; and Determining the above-mentioned coverage ratio based on the number of the above-mentioned at least one first component and the number of the above-mentioned at least one second component. As in the information providing method of claim 2, wherein the information of the application includes an XML file, The step of generating a relationship diagram between the plurality of components includes the following steps: by parsing the XML file, a tree view of a plurality of views displayed on the one or more pages is generated, The step of confirming the at least one first component, the at least one second component, and the at least one third component includes the following steps: confirming 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 in the plurality of views. The information providing method of claim 3, wherein the step of confirming the number of the at least one first component and the number of the at least one second component comprises the following steps: confirming the number of the at least one first view and the number of the at least one second view; 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. As in the information providing method of claim 3, the step of providing the information of the above-mentioned coverage ratio includes the following steps: Based on the tree view of the above-mentioned multiple views, provide the information of the subordinate relationship of the above-mentioned at least one second view. The information providing method of claim 2, wherein the information of the application includes the code of the application, The step of generating the relationship graph between the plurality of components includes the following steps: by parsing the code of the application, generating a call graph of a plurality of nodes corresponding to the one or more pages; The step of confirming the at least one first component, the at least one second component and the at least one third component includes the following steps: confirming 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. The information providing method of claim 6, wherein the step of confirming the number of the at least one first component and the number of the at least one second component comprises the following steps: confirming the number of calls of the at least one first node and the number of calls of the at least one second node; 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. As in the information providing method of claim 6, the step of providing the information of the above-mentioned coverage ratio includes the following steps: Based on the call graph of the above-mentioned plurality of nodes, providing the information of the call relationship of the above-mentioned at least one second node. The information providing method of claim 2, wherein the coverage ratio is determined by considering at least one of the following factors: The area occupied by the at least one first component and the at least one second component in the one or more pages; The respective positions of the at least one first component and the at least one second component in the one or more pages; and The time when the at least one first component and the at least one second component are exposed to the user. In the information providing method of claim 9, the greater the number of the 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 exposure time of the at least one first component, the higher the coverage ratio is determined to be. A non-transitory computer-readable recording medium records a program for executing the method of claim 1 in a computer. An electronic device, comprising: a transceiver; a memory; and a processor; the processor is as follows: obtains information about an application, generates a relationship diagram 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, confirms 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, confirms the coverage ratio of the at least one first component in the first domain, provides information about the coverage ratio; wherein the components of the first type include components that match one or more set components, The above-mentioned second type of components includes components that do not match with one or more of the above-mentioned components but are set to be replaced by one or more of the above-mentioned components. The above-mentioned third type of components includes components that do not match with one or more of the above-mentioned components and are set not to be replaced by one or more of the above-mentioned components.