KR102616785B1 - Electronic apparatus and providing inforation method thereof - Google Patents

Abstract

A method of providing information by an electronic device is provided. The information provision method includes first information about one or more layers included in an application and second information about the public part and private part of one or more modules corresponding to each of the one or more layers. Confirming; confirming third information about a dependency relationship between the one or more modules; based on the first information, the second information, and the third information, checking whether dependency rules are observed for the one or more modules; and providing information regarding compliance with the dependency rule.

Description

Electronic device and its information providing method {ELECTRONIC APPARATUS AND PROVIDING INFORATION METHOD THEREOF}

The present disclosure provides an electronic device and the same for determining whether a dependency rule is observed for one or more modules included in an application and providing information to a user regarding a module that does not comply with the dependency rule and a rule that the module does not comply with. It's about control methods.

As the use of the Internet and the spread of mobile terminals become widespread, users can receive various services through applications. The level of service and amount of information required by users are gradually increasing, and modularization, which bundles functions and related data to perform various functions into one module to meet user needs, has been introduced into applications. It has been done.

However, as the number of modules included in an application increases, the dependency relationship between modules becomes more complex, resulting in dependency rot, where high-level modules depend on low-level modules and low-level modules depend on high-level modules, etc. There is a problem that the same error may occur.

In relation to this, prior literature such as KR 10-2015-0079887 A1 may be referred to.

The disclosed embodiments seek to provide an electronic device and a method for managing its information. More specifically, an electronic device for checking whether dependency rules are observed for one or more modules included in an application and providing information to the user regarding modules that do not comply with the dependency rules and the rules that the modules do not comply with. The purpose is to provide and a control method thereof.

The technical challenges that this embodiment aims to achieve are not limited to the technical challenges described above, and other technical challenges can be inferred from the following embodiments.

One aspect of the present disclosure is to provide first information about one or more layers included in an application and information about public parts and private parts of one or more modules corresponding to each of the one or more layers. 2 Confirming information; confirming third information about a dependency relationship between the one or more modules; based on the first information, the second information, and the third information, checking whether dependency rules are observed for the one or more modules; and providing information regarding compliance with the dependency rule.

In addition, in one embodiment of the present disclosure, the dependency rule includes: a first rule that the public part of a first module or the private part of the first module among the one or more modules cannot depend on the private part of the second module; and a second rule that a third module included in a lower layer among the one or more modules cannot depend on a fourth module included in an upper layer.

In addition, in an embodiment of the present disclosure, the public part of the fifth module among the one or more modules includes an interface and a data model related to the fifth module, and the private part of the fifth module includes one or more of the interfaces. A method of providing information, including implementation, may be provided.

In addition, in one embodiment of the present disclosure, when the application is distributed, an implementation corresponding to a region in which the application is to be distributed among the one or more implementations is implemented.

Additionally, in one embodiment of the present disclosure, the information regarding compliance with the dependency rule may include information regarding a sixth module among the one or more modules that does not comply with the dependency rule; And it is possible to provide an information provision method including information about rules that the sixth module does not comply with.

Additionally, in one embodiment of the present disclosure, the information provision method may be initiated by obtaining a pull request from a user terminal.

In addition, in an embodiment of the present disclosure, if it is confirmed that the dependency rules for the one or more modules are not observed, an information providing method is provided, further comprising generating information to reject the pull request. can do.

Additionally, in one embodiment of the present disclosure, checking the first information and the second information includes obtaining architecture information of the application including layer setting information and module setting information; A method of providing information may be provided, including the step of confirming the first information based on the layer setting information and confirming the second information based on the module setting information.

Additionally, in one embodiment of the present disclosure, confirming the third information includes obtaining a pull request from a user terminal; and confirming the third information based on the pull request.

Additionally, in one embodiment of the present disclosure, the information providing method includes: confirming fourth information regarding a changed dependency relationship between the one or more modules; Based on the third information and the fourth information, confirming at least one module whose dependency relationship has changed among the one or more modules; A method of providing information may be provided, further comprising checking whether the dependency rule is observed for the at least one module based on the first information, the second information, and the fourth information.

Additionally, in one embodiment of the present disclosure, the information providing method includes: confirming information about a region where the application will be distributed; Confirming at least one implementation corresponding to a region in which the application is to be distributed among one or more implementations included in the private part of the one or more modules; and determining whether the dependency rule is observed for the at least one implementation based on the first information, the second information, and the third information. can do.

Another aspect of the present disclosure includes a communication unit, a memory, and a controller, wherein the controller includes first information about one or more layers constituting an application and one or more layers included in each of the one or more layers. Confirm second information regarding public and private parts of modules, confirm third information regarding dependency relationships between the one or more modules, and determine the first information, the second information, and the An electronic device can be provided that checks whether a dependency rule is observed for the one or more modules based on third information and provides information regarding a result of checking whether the dependency rule is observed.

Another aspect of the present disclosure may provide a computer-readable recording medium on which a program for implementing a method performed by an electronic device is recorded.

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

If you follow the proposed embodiment, one or more of the following effects can be expected.

According to the embodiments of the present specification, users can more conveniently check whether the code regarding the dependency relationship between one or more modules written by the user complies with the dependency rules.

In addition, according to the embodiment of the present specification, the user can more conveniently check information about the code corresponding to the module that does not comply with the dependency rules among the code related to the dependency relationship between one or more modules written by the user.

The effect of the invention is 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.

1 shows a system according to one embodiment.
FIG. 2 illustrates an example of one or more layers included in an application and one or more modules corresponding to each of the one or more layers, according to an embodiment.
3 illustrates an example of a public part and a private part of a module, according to an embodiment.
FIG. 4 is a diagram illustrating a process by which an electronic device checks whether dependency rules are observed for one or more modules, according to an embodiment.
FIG. 5 is a diagram illustrating a process by which an electronic device checks whether dependency rules are observed for one or more modules, according to an embodiment.
FIGS. 6A and 6B are diagrams illustrating a process by which an electronic device checks whether dependency rules for one or more modules are observed, according to an embodiment.
FIG. 7 is a diagram illustrating a process in which an electronic device checks whether dependency rules are observed for one or more modules, according to an embodiment.
FIG. 8 is a diagram illustrating a process by which an electronic device checks whether dependency rules are observed for one or more modules, according to an embodiment.
Figure 9 shows a flowchart of a method for providing information by an electronic device according to an embodiment.
Figure 10 shows a block diagram of an electronic device according to an embodiment.

The terms used in the embodiments are general terms that are currently widely used as much as possible while considering the functions in the present disclosure, but this may vary depending on the intention or precedent of a person working in the art, the emergence of new technology, etc. In addition, in certain cases, there are terms arbitrarily selected by the applicant, and in this case, the meaning will be described in detail in the relevant description. Therefore, the terms used in this disclosure should be defined based on the meaning of the term and the overall content of this disclosure, rather than simply the name of the term.

When it is said that a part "includes" a certain element throughout the specification, this means that, unless specifically stated to the contrary, it does not exclude other elements but may further include other elements.

The expression “at least one of a, b, and c” used throughout the specification means ‘a alone’, ‘b alone’, ‘c alone’, ‘a and b’, ‘a and c’, ‘b and c ', or 'all of a, b, and c'.

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

Below, with reference to the attached drawings, embodiments of the present disclosure will be described in detail so that those skilled in the art can easily practice them. However, the present disclosure may be implemented in many different forms and is not limited to the embodiments described herein.

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

1 shows a system according to one embodiment.

Referring to FIG. 1 , the system may include at least one of an electronic device 100, one or more user terminals 120, 140, and 160, and a network 180. Meanwhile, the system shown in FIG. 1 shows only components related to this embodiment. Accordingly, those skilled in the art can understand that other general-purpose components may be included in addition to the components shown in FIG. 1.

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

According to one embodiment, the electronic device 100 includes first information about one or more layers included in the application, second information about the public part and the private part of one or more modules corresponding to each of the one or more layers, and one Third information regarding the dependency relationship between the above modules can be confirmed. Thereafter, the electronic device 100 determines whether the dependency rule is observed for one or more modules based on the first information, second information, and third information, and sends information regarding compliance with the dependency rule to one or more modules. It can be transmitted to user terminals 120, 140, and 160.

One or more user terminals 120, 140, and 160 are terminals used by each user, and the users can access services provided by the network 180 using their respective user terminals 120, 140, and 160. You can. For example, the electronic device 100 may provide one or more user terminals 120, 140, and 160 with a platform or application that provides information regarding whether code written by the user complies with dependency rules. Users can check whether the code they wrote complies with the dependency rules using a platform or application installed on their respective user terminals 120, 140, and 160.

One or more user terminals 120, 140, and 160 and the electronic device 100 may communicate with each other within the network 180. The network 180 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 their respective networks. It is a comprehensive data communication network that includes a combination and allows each network constituent shown in FIG. 1 to communicate smoothly with each other, and may include wired Internet, wireless Internet, and mobile wireless communication network. Wireless communications include, for example, wireless LAN (Wi-Fi), Bluetooth, Bluetooth low energy, ZigBee, WFD (Wi-Fi Direct), UWB (ultra wideband), and infrared communication (IrDA, infrared Data Association). ), NFC (Near Field Communication), etc., but are not limited thereto.

Figure 2 shows an example of one or more layers included in an application according to an embodiment and one or more modules corresponding to each of the one or more layers.

According to one embodiment, the application may include an application layer 200, a domain layer 220, a common layer 260, and a shared layer 280. At this time, there may be a hierarchy between one or more layers included in the application. For example, the application layer 200 may be an upper layer than the domain layer 220, the domain layer 220 may be an upper layer than the common layer 260, and the common layer 260 may be an upper layer than the domain layer 220. It may be a layer higher than the shared layer 280. However, the number of layers included in the application, the names of the layers, and the hierarchical structure between the layers are only an example and may be implemented differently from those described above.

According to one embodiment, each of the application layer 200, domain layer 220, common layer 260, and shared layer 280 may include one or more modules. For example, the application layer 200 may include an application module 210, and the domain layer 220 may include a plp (product list page)-common module 222, a srp (search result page, Search results page)-common module (224), sdp (single detail page, product detail description page)-common module (226), cart-common module (228), gw-common module (230), plp module (232) , srp module 234, sdp module 236, cart module 238, and gw module 240. Alternatively, the common layer 260 may include the common module 265 and the common-ui module 270, and the shared layer 280 may include the foundation module 282, the network module 284, and the image module 286. , may include a monitoring module 288 and an ab test module 290. However, the number of modules included in each layer and the name of the module are only an example, and may be implemented differently from those described above.

According to one embodiment, a dependency relationship may exist between modules included in each layer. More specifically, modules included in a higher layer may depend on modules included in the same layer or a lower layer. However, modules included in lower layers cannot depend on modules included in higher layers.

For example, the application module 210 included in the application layer 200 may depend on the cart-common module 228 included in the domain layer 220, which is a lower layer, and the application module 228 included in the common layer 260. The common module 265 may depend on the image module 286 included in the shared layer 280, which is a lower layer. Alternatively, the gw-common module 230 included in the domain layer 220 may depend on the cart-common module 228 included in the same layer, and the foundation module 282 included in the shared layer 280 It may depend on the network module 284 included in the same layer. However, the common-ui module 270 included in the common layer 260 cannot depend on the sdp-common module 226 included in the upper layer, the domain layer 220, and the common-ui module 270 included in the shared layer 280 The image module 286 cannot depend on the common module 265 included in the upper layer, the common layer 260.

At this time, the fact that the first module depends on the second module means that the method of the second module is called when using the first module, or that the first module has the second module as a member variable or local variable. However, it is not limited to the above.

Figure 3 shows an example of a public part and a private part of a module according to an embodiment.

According to one embodiment, the module 300 is a unit in which functions and related data for independently performing a specific function are bundled into one unit, and may include a public part 310 and a private part 320. At this time, the names of the public part 310 and the private part 320 are only an example and may be referred to differently. For example, the public part 310 may be referred to as an abstracted concept, an abstract class, etc., and the private part 320 may be referred to as a concrete concept, a class implementing an abstract class, etc., but the above-described It's not limited to bars.

According to one embodiment, the public part 310 of the module 300 may include an interface 330 and a data model 340. For example, the public part 310 may include an externally visible interface 330 and a data model 340 that performs the function of importing and exporting related data.

According to one embodiment, the private part 320 of the module 300 may include one or more implementations 350, 360, and 370. For example, private part 320 may include one or more implementations 350, 360, and 370 to implement interface 330 differently.

According to one embodiment, each of the one or more implementations 350, 360, and 370 may correspond to a region in which the application is to be distributed, and may include different code depending on the corresponding region. For example, the first implementation 350 may include code for implementing a version of an application distributed in Korea, and the second implementation 360 may include code for implementing a version of an application distributed in Japan. It may include code for implementation, and the third implementation 370 may include code for implementing the version of the application distributed in Taiwan.

According to one embodiment, when an application is distributed, one of one or more implementations 350, 360, and 370 may be implemented that corresponds to the region where the application is to be distributed. For example, when an application is distributed in Korea, the first implementation 350 corresponding to Korea among one or more implementations 350, 360, and 370 included in the private part 320 will be implemented. You can. Through this, different versions of the application can be provided to users depending on the language or culture of the region where the application will be distributed.

FIG. 4 is a diagram illustrating a process by which the electronic device 100 checks whether dependency rules are observed for one or more modules, according to an embodiment.

According to one embodiment, the electronic device 100 may check first information about one or more layers included in the application and check second information about the public part and private part of one or more modules.

For example, the electronic device 100 checks the first layer 400 and the second layer 430 included in the application based on the layer setting information, and determines the first layer 400 and the second layer 430. ) You can check the hierarchical structure between them. In addition, based on the layer setting information, the electronic device 100 checks the first module 410 and the second module 420 included in the first layer 400, and determines the first module 410 and the second module 420 included in the second layer 430. The third module 440 and fourth module 450 can be confirmed.

Alternatively, the electronic device 100 checks the public part 412 and the private part 414 of the first module 410 based on the module setting information, and configures the public part 422 and the private part 414 of the second module 420. By checking the private part 424, the first implementation 426 and the second implementation 428 included in the private part 424 can be confirmed. In addition, the electronic device 100 checks the public part 442 and the private part 444 of the third module 440 based on the module setting information, and the public part 452 and the private part 444 of the fourth module 450. You can check the private part (454).

According to one embodiment, the electronic device 100 may check third information regarding the dependency relationship between one or more modules. For example, the electronic device 100 determines that the private part 444 of the third module 440 depends on the public part 412 of the first module 410, and determines that the private part 444 of the first module 410 It can be confirmed that the part 414 depends on the public part 452 of the fourth module 450. Alternatively, the electronic device 100 determines that the public part 422 of the second module 420 depends on the private part 454 of the fourth module 450, and determines the private part of the second module 420 ( It can be confirmed that the second implementation 428 included in 424) depends on the public part 442 of the third module 440.

According to one embodiment, the electronic device 100 may check whether dependency rules are observed for one or more modules based on the first information, second information, and third information. More specifically, the electronic device 100 includes a first rule that the public part of the first module or the private part of the first module among one or more modules cannot depend on the private part of the second module and the first rule included in the lower layer. 3 It can be checked whether the second rule that a module cannot depend on a fourth module included in a higher layer is complied with.

For example, the electronic device 100 may have the private part 414 of the first module 410 depend on the public part 452 of the fourth module 450 and the private part 424 of the second module 420. It can be confirmed that the second implementation 428 included in ) depends on the public part 442 of the third module 440 in compliance with the dependency rules. Alternatively, the electronic device 100 may determine that the private part 444 of the third module 440 depends on the public part 412 of the first module 410 because the module included in the lower layer is the module included in the upper layer. Since it depends on , you can confirm that it does not comply with the dependency rules. The electronic device 100 does not comply with the dependency rule because the public part 422 of the second module 420 depends on the private part 454 of the fourth module 450 because it depends on the private part of another module. You can confirm that this is not the case.

According to one embodiment, the electronic device 100 may provide information regarding compliance with dependency rules. More specifically, the electronic device 100 may provide information about a module that does not comply with a dependency rule among one or more modules and information about a rule that the module does not comply with. For example, the electronic device 100 determines that the second rule that a module included in a lower layer cannot depend on a module included in an upper layer is not observed with respect to the private part 444 of the third module 440. Information can be provided. Alternatively, the electronic device 100 may provide information regarding the public part 422 of the second module 410 that the first rule that the public part of a module cannot depend on the private part of another module is not complied with. there is.

FIG. 5 is a diagram illustrating a process by which the electronic device 100 checks whether dependency rules are observed for one or more modules, according to an embodiment. Content that overlaps with Figure 4 will be briefly explained or omitted.

According to one embodiment, the electronic device 100 may check first information about one or more layers included in the application and check second information about the public part and private part of one or more modules.

For example, the electronic device 100 determines the first layer 500 and the second layer 530 based on layer setting information, and determines the hierarchical structure between the first layer 500 and the second layer 530. You can check. Additionally, the electronic device 100 may check the checkout module included in the first layer 500 and the payment module included in the second layer 530, based on the layer setting information.

Alternatively, the electronic device 100 may check the public part 510 and private part 520 of the checkout module based on module setting information. In addition, the electronic device 100 checks the public part 540 and private part 550 of the payment module based on the module setting information, and uses the global implementation 560 and You can check the KR implementation (570). At this time, the Global Implementation 560 may include code to implement the payment interface when the application is distributed in regions other than Korea, and the KR Implementation 570 may include code for implementing the payment interface when the application is distributed in Korea. When doing so, it may include code to implement the payment interface.

According to one embodiment, the electronic device 100 may check third information regarding the dependency relationship between one or more modules. For example, the electronic device 100 confirms that the public part 510 of the checkout module depends on the public part 540 of the payment module, and the private part 520 of the checkout module depends on the public part 540 of the checkout module. It can be confirmed that it depends on the part 510 and the public part 540 of the payment module. In addition, the electronic device 100 recognizes that each of the Global Implementation 560 and KR Implementation 570 included in the private part 550 of the payment module depends on the public part 540 of the payment module. You can check it.

According to one embodiment, the electronic device 100 may check whether dependency rules are observed for one or more modules based on the first information, second information, and third information. For example, the electronic device 100 may determine that the public part 510 of the checkout module depends on the public part 540 of the payment module and that the private part 520 of the checkout module depends on the public part 510 of the checkout module. ) and the public part 540 of the payment module can be confirmed to comply with the dependency rules. Alternatively, the electronic device 100 may determine that each of the Global implementation 560 and the KR implementation 570 included in the private part 550 of the payment module depends on the public part 540 of the payment module. You can confirm that the dependency rules are complied with.

According to one embodiment, the electronic device 100 may provide information regarding compliance with dependency rules. For example, the electronic device 100 may provide information that dependency rules are observed regarding the checkout module and payment module.

FIGS. 6A and 6B are diagrams illustrating a process by which the electronic device 100 checks whether dependency rules are observed for one or more modules, according to an embodiment. Content that overlaps with Figure 4 will be briefly explained or omitted.

In step S600, the electronic device 100 may obtain a pull request from the user terminal according to one embodiment. For example, the user saves the code related to the dependency relationship between one or more modules in a local repository and then sends a message to the user terminal to merge the saved code into the master branch or original code stored in the integrated repository. You can enter it. The user terminal may transmit a pull request containing information about the stored code to the electronic device 100 based on the user's input. As the electronic device 100 obtains a pull request, it may initiate a method of providing information regarding whether dependency rules are observed for one or more modules.

Meanwhile, the electronic device 100 is a device or worker terminal for merging and managing codes written by a plurality of users, and can receive pull requests directly from user terminals, but may be a device that exists separately from the worker terminal. . In this case, instead of receiving the pull request directly from the user terminal, the electronic device 100 may obtain information that the user terminal has transmitted the pull request to the worker terminal. As the electronic device 100 obtains information that the user terminal has transmitted a pull request to the worker terminal, the electronic device 100 may initiate a method of providing information regarding whether dependency rules are observed for one or more modules.

In step S610, the electronic device 100 may acquire application architecture information including layer setting information and module setting information according to an embodiment. For example, as shown in FIG. 6B, the electronic device 100 may receive a code regarding the architecture of an application including layer setting information and module setting information from a user terminal or worker terminal. At this time, among the codes related to the architecture of the application, the first code 670 may indicate layer setting information, and the second code 680 may indicate module setting information. Additionally, API included in the second code 680 may represent the public part of the module, and implementation may represent the private part of the module.

In step S620, the electronic device 100 determines first information about one or more layers included in the application based on layer setting information, and based on module setting information, one or more layers Second information regarding the public part and private part of one or more modules corresponding to each can be confirmed.

For example, based on the first code 670, the electronic device 100 can check the domain layer, shared layer, and foundation layer included in the application, and check the hierarchical structure between the domain layer, shared layer, and foundation layer. there is. In addition, based on the first code 670, the electronic device 100 includes the domain-gateway module, domain-search module, domain-plp module, domain-sdp module, domain-cart module, and domain-gateway module included in the domain layer. You can check the checkout module, and you can check the foundation-abtest module, foundation-logging module, foundation-payment module, foundation-member module, and foundation-webview module included in the foundation layer.

Alternatively, based on the second code 680, the electronic device 100 may configure each of the domain-gateway module, domain-search module, domain-plp module, domain-sdp module, domain-cart module, and domain-checkout module to be public. You can check the part and private part. Additionally, the electronic device 100 can check two implementations included in the private parts of each of the domain-cart module and the domain-checkout module based on the second code 680.

In step S630, the electronic device 100 may check third information about the dependency relationship between one or more modules based on a pull request, according to an embodiment. For example, the electronic device 100 may check codes related to dependency relationships between one or more modules based on a pull request received from a user terminal.

In step S640, the electronic device 100 may check whether dependency rules are observed for one or more modules based on the first information, second information, and third information, according to one embodiment. For example, the electronic device 100 may check whether dependency rules are observed for the domain-gateway module, domain-search module, foundation-payment module, or foundation-member module.

In step S650, the electronic device 100 may provide information regarding compliance with dependency rules, according to one embodiment. For example, the electronic device 100 may transmit information about a module that does not comply with a dependency rule among one or more modules and information about a rule that the module does not comply with to the user terminal.

In step S660, if it is confirmed that the dependency rules for one or more modules are not observed, the electronic device 100 may generate information that configures the electronic device 100 to reject the pull request according to an embodiment. For example, when it is confirmed that at least one of the one or more modules is not compliant, the electronic device 100 may generate information that sets the user terminal to reject the pull request and transmit it to the user terminal. there is.

FIG. 7 is a diagram illustrating a process by which the electronic device 100 checks whether dependency rules are observed for one or more modules, according to an embodiment. Content that overlaps with Figure 4 will be briefly explained or omitted.

In step S700, according to an embodiment, the electronic device 100 may provide first information about one or more layers included in the application and second information about the public part and private part of one or more modules corresponding to each of the one or more layers. You can check the information. For example, based on layer setting information, the electronic device 100 verifies first information about one or more layers included in the application, and based on module setting information, the electronic device 100 checks one or more layers corresponding to each of the one or more layers. You can check the second information about the public part and private part of the above modules.

In step S710, the electronic device 100 may check third information about the dependency relationship between one or more modules, according to an embodiment. For example, the electronic device 100 may check the first code regarding the dependency relationship between one or more modules based on the first pull request received from the user terminal.

In step S720, the electronic device 100 may check fourth information regarding the changed dependency relationship between one or more modules, according to an embodiment. For example, the electronic device 100 receives a second pull request including a second code regarding a dependency relationship between one or more modules from the user terminal, and based on the second pull request, determines the dependency relationship between one or more modules. You can check the second code regarding the relationship.

In step S730, the electronic device 100 may identify at least one module whose dependency relationship has changed among one or more modules based on the third information and fourth information, according to one embodiment. For example, the electronic device 100 compares a first code related to a dependency relationship between one or more modules and a second code related to a dependency relationship between one or more modules, and selects a subcode that is different from the first code among the second codes. You can check. Thereafter, the electronic device 100 may identify at least one module corresponding to a subcode of the second code that is different from the first code.

In step S740, the electronic device 100 may check whether the dependency rule is observed for at least one module based on the first information, second information, and fourth information, according to one embodiment. For example, the electronic device 100 may check whether at least one module depends on a private part of another module or whether at least one module depends on a module of a higher layer. Alternatively, the electronic device 100 may check whether another module depends on the private part of at least one module or whether a module of a lower layer depends on at least one module.

In step S750, the electronic device 100 may provide information regarding compliance with dependency rules, according to one embodiment. For example, the electronic device 100 may transmit information about a module that does not comply with a dependency rule among at least one module and information about a rule that the module does not comply with to the user terminal.

FIG. 8 is a diagram illustrating a process by which the electronic device 100 checks whether dependency rules are observed for one or more modules, according to an embodiment. Content that overlaps with Figure 4 will be briefly explained or omitted.

In step S800, according to one embodiment, the electronic device 100 may provide first information about one or more layers included in the application and second information about the public part and private part of one or more modules corresponding to each of the one or more layers. You can check the information. For example, based on layer setting information, the electronic device 100 verifies first information about one or more layers included in the application, and based on module setting information, the electronic device 100 checks one or more layers corresponding to each of the one or more layers. You can check the second information about the public and private parts of the above modules.

In step S810, the electronic device 100 may check third information about the dependency relationship between one or more modules, according to one embodiment. For example, the electronic device 100 may check codes related to dependency relationships between one or more modules based on a pull request received from a user terminal.

In step S820, the electronic device 100 may check information about the region where the application will be distributed, according to one embodiment. For example, the electronic device 100 may receive information about the area where the application will be distributed from the user terminal or worker terminal.

In step S830, the electronic device 100 may check at least one implementation corresponding to the region where the application is to be distributed among one or more implementations included in the private part of one or more modules according to an embodiment. there is. For example, if the region where the application is to be distributed is Taiwan, the electronic device 100 includes code for implementing a version of the application distributed in Taiwan among one or more implementations included in the private part of one or more modules. You can identify at least one implementation that does this.

In step S840, the electronic device 100 may check whether a dependency rule is observed for at least one implementation based on the first information, second information, and third information, according to one embodiment. For example, the electronic device 100 may check whether at least one implementation depends on a private part of another module or whether at least one implementation depends on a module of a higher layer. Alternatively, the electronic device 100 may check whether another module depends on at least one implementation.

In step S850, the electronic device 100 may provide information regarding compliance with dependency rules, according to one embodiment. For example, the electronic device 100 may transmit information about a module that does not comply with a dependency rule among at least one module and information about a rule that the module does not comply with to the user terminal.

Figure 9 shows a flowchart of a method for providing information by an electronic device according to an embodiment. The foregoing description may apply to overlapping content.

In step S900, the electronic device receives first information about one or more layers included in the application and information about the public part and private part of one or more modules corresponding to each of the one or more layers. 2 You can check the information.

According to one embodiment, the public part of the fifth module among the one or more modules includes an interface and a data model for the fifth module, and the private part of the fifth module includes one or more implementations of the interface. It can be included.

According to one embodiment, when an application is distributed, among one or more implementations, an implementation corresponding to the region in which the application is to be distributed may be implemented.

According to one embodiment, when checking the first information and the second information, the electronic device acquires architecture information of the application including layer setting information and module setting information, confirms the first information based on the layer setting information, and , the second information can be confirmed based on the module setting information.

In step S920, the electronic device may check third information regarding the dependency relationship between one or more modules.

According to one embodiment, when checking third information, the electronic device may obtain a pull request from the user terminal and confirm the third information based on the pull request.

In step S940, the electronic device may check whether dependency rules are observed for one or more modules based on the first information, second information, and third information.

According to one embodiment, the dependency rules include: a first rule that the public part of a first module or the private part of the first module among the one or more modules cannot depend on the private part of the second module; and a second rule that a third module included in a lower layer among one or more modules cannot depend on a fourth module included in an upper layer.

In step S960, the electronic device may provide information regarding compliance with the dependency rule.

According to one embodiment, the information about compliance with the dependency rule may include information about a sixth module among one or more modules that does not comply with the dependency rule and information about the rule that the sixth module does not comply with. .

According to one embodiment, a method for providing information may be initiated by obtaining a pull request from a user terminal. At this time, if it is confirmed that the dependency rules for one or more modules are not observed, the electronic device may generate information that configures the electronic device to reject the pull request.

According to one embodiment, the electronic device determines fourth information regarding a changed dependency relationship between one or more modules, and based on the third information and the fourth information, at least one module whose dependency relationship has changed among the one or more modules. , and based on the first information, second information, and fourth information, it can be confirmed whether the dependency rule is observed for at least one module.

According to one embodiment, the electronic device determines information about the region in which the application will be distributed, and selects at least one implementation corresponding to the region in which the application is to be distributed among one or more implementations included in the private part of one or more modules. Check the implementation and, based on the first information, second information and third information, check whether the dependency rule is observed for at least one implementation

FIG. 10 shows a block diagram of an electronic device 100 according to an embodiment.

According to one embodiment, the electronic device 100 may include a communication device 1020, a memory 1040, and a controller 1060. The electronic device 100 shown in FIG. 10 shows only components related to this embodiment. Accordingly, those skilled in the art can understand that other general-purpose components may be included in addition to the components shown in FIG. 10. Since the electronic device 100 may include content related to the above-described server, description of overlapping content will be omitted. In an embodiment, the communication unit may include one or more transceivers. Additionally, in an embodiment, the control unit may include one or more processors.

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

The control unit 1060 can control the overall operation of the electronic device 100 and process data and signals. The control unit 1060 may be composed of at least one hardware unit. Additionally, the control unit 1060 may operate by one or more software modules generated by executing program codes stored in the memory 1040. The control unit 1060 may include a processor and a memory, and the processor may execute program codes stored in the memory to control the overall operation of the electronic device 100 and process data and signals. Additionally, in an embodiment, the control unit 1060 may include at least one processor.

The control unit 1060 provides first information about one or more layers constituting the application and second information about the public part and private part of one or more modules included in each of the one or more layers. Verify third information about the dependency relationship between one or more modules, and based on the first information, second information, and third information, determine whether dependency rules are observed for one or more modules; , information can be provided regarding the results of checking compliance with dependency rules.

Electronic devices according to the above-described embodiments include a processor, memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with an external device, a touch panel, keys, buttons, etc. It may include the same user interface device, etc. 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, computer-readable recording media include magnetic storage media (e.g., ROM (read-only memory), RAM (random-access memory), floppy disk, hard disk, etc.) and optical read media (e.g., CD-ROM). ), DVD (Digital Versatile Disc), etc. The computer-readable recording medium is distributed among computer systems connected to a network, so that computer-readable code can be stored and executed in a distributed manner. The media may be readable by a computer, stored in memory, and executed by a processor.

This embodiment can be represented by functional block configurations and various processing steps. These functional blocks may be implemented as any number of hardware or/and software configurations that execute specific functions. For example, embodiments include integrated circuit configurations such as memory, processing, logic, look-up tables, etc. that can execute various functions under the control of one or more microprocessors or other control devices. can be hired. Similar to how the components can be implemented as software programming or software elements, this embodiment includes various algorithms implemented as combinations of data structures, processes, routines or other programming constructs, such as C, C++, Java ( It can be implemented in a programming or scripting language such as Java), assembler, etc. Functional aspects may be implemented as algorithms running on one or more processors. Additionally, this embodiment may employ conventional technologies for electronic environment settings, signal processing, and/or data processing. Terms such as “mechanism,” “element,” “means,” and “configuration” may be used broadly and are not limited to mechanical and physical configurations. The term may include the meaning of a series of software routines in connection with a processor, etc.

The above-described embodiments are merely examples and other embodiments may be implemented within the scope of the claims described below.

Claims (13)

In a method of providing information by an electronic device,
Confirming first information about one or more layers included in the application and second information about the public part and private part of one or more modules corresponding to each of the one or more layers. ;
confirming third information about a dependency relationship between the one or more modules;
based on the first information, the second information, and the third information, checking whether dependency rules are observed for the one or more modules; and
Providing information regarding compliance with said dependency rules,
The dependency rule is,
a first rule that the public part of a first module or the private part of the first module among the one or more modules cannot depend on the private part of the second module; and
A method for providing information, including a second rule that a third module included in a lower layer among the one or more modules cannot depend on a fourth module included in an upper layer.
delete In a method of providing information by an electronic device,
Confirming first information about one or more layers included in the application and second information about the public part and private part of one or more modules corresponding to each of the one or more layers. ;
confirming third information about a dependency relationship between the one or more modules;
based on the first information, the second information, and the third information, checking whether dependency rules are observed for the one or more modules; and
Providing information regarding compliance with the dependency rule, wherein the public part of a fifth module among the one or more modules includes an interface and a data model for the fifth module,
The private part of the fifth module includes one or more implementations of the interface.
According to clause 3,
When the application is distributed, an implementation corresponding to a region in which the application is to be distributed among the one or more implementations is implemented.
The method of claim 1, wherein the information regarding compliance with the dependency rule is:
Information about a sixth module among the one or more modules that does not comply with the dependency rule; and
A method of providing information, including information about rules that the sixth module does not comply with. In a method of providing information by an electronic device,
Confirming first information about one or more layers included in the application and second information about the public part and private part of one or more modules corresponding to each of the one or more layers. ;
confirming third information about a dependency relationship between the one or more modules;
based on the first information, the second information, and the third information, checking whether dependency rules are observed for the one or more modules; and
Providing information regarding compliance with said dependency rules,
The information provision method is initiated by obtaining a pull request from a user terminal.
According to clause 6,
A method of providing information further comprising generating information that configures the pull request to be rejected when it is determined that dependency rules for the one or more modules are not adhered to.
The method of claim 1, wherein confirming the first information and the second information comprises:
Obtaining architecture information of the application including layer setting information and module setting information;
Confirming the first information based on the layer setting information and confirming the second information based on the module setting information.
In a method of providing information by an electronic device,
Confirming first information about one or more layers included in the application and second information about the public part and private part of one or more modules corresponding to each of the one or more layers. ;
confirming third information about a dependency relationship between the one or more modules;
based on the first information, the second information, and the third information, checking whether dependency rules are observed for the one or more modules; and
Providing information regarding compliance with said dependency rules,
The step of confirming the third information is,
Obtaining a pull request from a user terminal; and
A method of providing information, including confirming the third information based on the pull request.
In a method of providing information by an electronic device,
Confirming first information about one or more layers included in the application and second information about the public part and private part of one or more modules corresponding to each of the one or more layers. ;
confirming third information about a dependency relationship between the one or more modules;
based on the first information, the second information, and the third information, checking whether dependency rules are observed for the one or more modules; and
Providing information regarding compliance with said dependency rules,
The method of providing the above information is:
confirming fourth information regarding a changed dependency relationship between the one or more modules;
Based on the third information and the fourth information, confirming at least one module whose dependency relationship has changed among the one or more modules;
Based on the first information, the second information, and the fourth information, the information providing method further includes checking whether the dependency rule is observed for the at least one module.
In a method of providing information by an electronic device,
Confirming first information about one or more layers included in the application and second information about the public part and private part of one or more modules corresponding to each of the one or more layers. ;
confirming third information about a dependency relationship between the one or more modules;
based on the first information, the second information, and the third information, checking whether dependency rules are observed for the one or more modules; and
Providing information regarding compliance with said dependency rules,
The method of providing the above information is:
Confirming information about the region where the application will be distributed;
Confirming at least one implementation corresponding to a region in which the application is to be distributed among one or more implementations included in the private part of the one or more modules; and
Based on the first information, the second information, and the third information, the information providing method further includes checking whether the dependency rule is observed for the at least one implementation.
A non-transitory computer-readable recording medium that records a program for executing the method of claim 1 on a computer.
As an electronic device,
Ministry of Communications;
Memory; and
It includes a controller, wherein the controller includes:
Confirming first information about one or more layers constituting an application and second information about public parts and private parts of one or more modules included in each of the one or more layers,
Confirm third information regarding dependency relationships between the one or more modules,
Based on the first information, the second information, and the third information, determine whether dependency rules are observed for the one or more modules,
Provide information on the results of checking compliance with the above dependency rules,
The dependency rule is,
a first rule that the public part of a first module or the private part of the first module among the one or more modules cannot depend on the private part of the second module; and
An electronic device comprising a second rule that a third module included in a lower layer among the one or more modules cannot depend on a fourth module included in an upper layer.

Images