TW202526601A - Electronic device and document provision method thereof - Google Patents

Abstract

The present invention provides a method for providing a document, comprising the following steps: verifying each type of snapshot for a user interface (UI) object having a plurality of types according to at least one selectable option; providing a business document including an item for the UI object; verifying an input for the business document related to the item for the UI object; and providing at least some of the plurality of types of snapshots of the UI object on the business document based on the input.

Description

Electronic device and document providing method thereof

The present invention relates to an electronic device and a method for providing a document therefor.

Communication between developers and designers is a crucial element of the development process. For example, even if a designer has designed appropriate UI objects for use on a service page, developers may not be able to properly implement them if they lack a clear understanding of the UI object's characteristics or the options available for that object. Therefore, it's crucial for developers to easily identify the characteristics of UI objects in this regard.

Communication between developers and designers is typically achieved through development documents. However, most development documents are static, not dynamic. Specifically, they are often based on the information available when UI objects were first created, or they simply display static examples of UI objects. Due to these characteristics, communication using standard development documents has certain limitations, often resulting in incomplete information about UI objects.

For related information, please refer to previous literature such as KR10-1636335B1.

[Identify the problem you want to solve]

The disclosed embodiments are intended to provide an electronic device and a method for providing a document therefor. Specifically, one object of the present invention is to provide a development document that can easily and visually display options that can be selected for a UI object.

The technical issues to be achieved by this embodiment are not limited to those described above; other technical issues can be derived based on the following embodiments. [Technical Solutions]

One aspect of the present invention may provide a document providing method, which is performed by an electronic device and includes the following steps: confirming snapshots of each type of user interface (UI) object having multiple types based on at least one selectable option; providing a business document including items of the above-mentioned UI objects; confirming input of the above-mentioned business document related to the items of the above-mentioned UI objects; and based on the above-mentioned input, providing at least a portion of the snapshots of each of the above-mentioned multiple types of the above-mentioned UI objects to the above-mentioned business document.

In one embodiment of the present invention, a document providing method may be included, wherein the step of providing at least a portion of the snapshots of each of the above-mentioned multiple types into the above-mentioned business document includes the following steps: based on the above-mentioned input, confirming the information of each option selected according to the category of each of the above-mentioned at least one selectable option; and providing a snapshot, which is confirmed based on the combination of each option selected according to the above-mentioned categories and corresponds to one of the above-mentioned multiple types.

Furthermore, in one embodiment of the present invention, a document providing method may be included, wherein the step of confirming the above-mentioned input includes the following steps: providing at least one of the above-mentioned selectable options through a drop-down menu of each category on the business document; and confirming the above-mentioned input including each selection made from the drop-down menu of each category.

Furthermore, in one embodiment of the present invention, a document providing method may be included, wherein the step of providing the above-mentioned business document includes the following steps: providing an item of the above-mentioned UI object as at least a part of the above-mentioned business document, the item including a snapshot corresponding to the default type of the above-mentioned UI object and a sample code corresponding to the above-mentioned default type.

Furthermore, in one embodiment of the present invention, a document providing method may be included, wherein the step of confirming the input includes the following step: in response to the modification of the sample code, the modified sample code including information of the selected option is used as the input for confirmation.

Furthermore, in one embodiment of the present invention, a document providing method may be included, wherein the step of providing at least a portion of the snapshots of each of the above-mentioned multiple types to the above-mentioned business document includes the following steps: confirming information of non-selectable options among the options included in the modified above-mentioned sample code; confirming similar types, which correspond to the information of selectable options among the options included in the modified above-mentioned sample code; and adjusting the snapshot corresponding to the above-mentioned similar type based on the inferred information corresponding to the information of the above-mentioned non-selectable options, thereby providing the confirmed inferred snapshot to the above-mentioned business document.

Furthermore, in one embodiment of the present invention, a file providing method may be included, which further includes the following steps: transmitting the above-mentioned inference snapshot to the designer terminal.

Furthermore, in one embodiment of the present invention, a document providing method may be included, wherein the step of providing at least a portion of the snapshots of each of the above-mentioned multiple types to the above-mentioned business document includes the following steps: providing at least a portion of the snapshots of each of the above-mentioned multiple types of the above-mentioned UI objects to the above-mentioned business document in sequence.

Furthermore, in one embodiment of the present invention, a document providing method may be included, wherein the step of confirming the input includes the following step: hovering a cursor over an area corresponding to the item of the UI object as the input for confirmation.

Furthermore, in one embodiment of the present invention, a document providing method may be included, wherein the step of providing at least a portion of the snapshots of each of the above-mentioned multiple types to the above-mentioned business document includes the following steps: based on the above-mentioned input, confirming the category corresponding to the detailed area of the hovering cursor; and sequentially providing the snapshots corresponding to at least a portion of the above-mentioned multiple types to the above-mentioned business document, the multiple types being confirmed by sequentially applying at least one option that can be selected for the above-mentioned category to a default type, the at least one option being at least a portion of the at least one selectable option mentioned above.

Furthermore, in one embodiment of the present invention, a document providing method may be included, wherein the step of providing the above-mentioned business document includes the following steps: compiling a database storing snapshots of the above-mentioned various types in the source document and a binding code between the above-mentioned source document to generate the above-mentioned business document; the step of providing at least a portion of the snapshots of each of the above-mentioned multiple types into the above-mentioned business document includes the following steps: based on the above-mentioned input and the compiled binding code, obtaining at least a portion of the snapshots of each type of the above-mentioned UI object rendered in the customer environment from the database, wherein the snapshot corresponds to at least a portion of the above-mentioned multiple types.

Furthermore, in one embodiment of the present invention, a document providing method may be included, which further includes the following steps: confirming change information of at least one option or category, where the option is added to make the above-mentioned UI object selectable or deleted to make the above-mentioned UI object non-selectable; updating the above-mentioned binding code based on the above-mentioned change information; and compiling the updated binding code to update at least a portion of the above-mentioned business document.

Furthermore, in one embodiment of the present invention, a document providing method may be included, wherein the step of updating at least a portion of the above-mentioned business document includes the following steps: compiling the updated above-mentioned binding code to thereby update a drop-down menu related to the item of the above-mentioned UI object.

Furthermore, in one embodiment of the present invention, a file providing method may be included, wherein the step of confirming the above-mentioned change information includes the following steps: confirming the above-mentioned change information in response to the addition or deletion of the snapshot in the folder in the above-mentioned database corresponding to the above-mentioned binding code.

Furthermore, in one embodiment of the present invention, a file providing method may be included, wherein the step of confirming the above-mentioned change information includes the following steps: in response to the addition or deletion of the above-mentioned snapshot, the above-mentioned change information is confirmed based on the file name of each snapshot of the folder in the above-mentioned database corresponding to the above-mentioned binding code.

Furthermore, in one embodiment of the present invention, a document providing method may be included, wherein the step of confirming the above-mentioned change information further includes the following step: verifying the above-mentioned change information by comparing the snapshot added to the folder in the above-mentioned database corresponding to the above-mentioned binding code with other snapshots except the above-mentioned snapshot added.

Furthermore, in one embodiment of the present invention, a document providing method may be included, wherein the business document is a computer programming-related development document shared among business team members, and the snapshots of each type are generated by rendering the UI objects according to type as the UI objects are tested in a customer environment.

Another aspect of the present invention may provide an electronic device that provides a document, comprising: a processor; and a memory storing one or more instructions; the processor being configured to: execute the one or more instructions, thereby confirming snapshots of various types generated in response to a test of a user interface (UI) object having a plurality of types based on at least one selectable option; provide a business document including items of the UI objects; confirm input related to the items of the UI objects; and based on the input, provide at least a portion of the plurality of types of the UI objects into the business document.

Another aspect of the present invention may provide a non-transitory computer-readable recording medium that records a program for executing the above-mentioned file providing method on a computer.

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

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

According to the embodiments of this specification, developers can interactively confirm options for selectable UI objects through development documents.

Furthermore, according to the embodiments of this specification, developers can visually confirm the types of various UI objects that change as they select options for UI objects through development documents.

Furthermore, according to the embodiments of the present specification, when the options for selecting a UI object are changed, the development document is also dynamically updated, thereby enabling the updated information of the UI object to be confirmed through the development document.

The effects of the present invention are not limited to the effects mentioned above. A person skilled in the art can clearly understand other effects not mentioned based on the description of the invention patent application.

The terms used in the embodiments are selected from commonly used terms, as much as possible, taking into account the functions of the present invention. However, they may vary depending on the intentions of those skilled in the art, precedents, the emergence of new technologies, and so on. Furthermore, in certain cases, there may be terms arbitrarily selected by the applicant. In such cases, their meanings will be detailed in the corresponding description. Therefore, the terms used in this invention should be defined based on their meanings and the overall content of the invention, rather than simply based on their names.

Throughout the specification, when it is stated that a certain part “includes” a certain constituent element, unless there is any special description to the contrary, it means that other constituent elements may be further included, and other constituent elements are not excluded.

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

The "terminal" mentioned below can be implemented as a computer or portable terminal, which can be connected to a server or other terminal via a network. Here, computers may include, for example, laptops, desktops, and the like equipped with a web browser. Portable terminals are wireless communication devices that ensure portability and mobility, and may include, for example, IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), LTE (Long Term Evolution), and other communication terminals, as well as all types of handheld wireless communication devices such as smartphones and tablets.

The following describes an embodiment of the present invention in detail with reference to the accompanying drawings so that those skilled in the art can easily implement the present invention. However, the present invention can be implemented in various forms and is not limited to the embodiments described herein.

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

FIG1 shows the binding relationship of an electronic device according to an embodiment.

Referring to Figure 1 , electronic device 100 controls the connection with database 300 to provide business documents 200. Figure 1 only illustrates components relevant to this embodiment. Therefore, those skilled in the art will appreciate that this embodiment may include other common components in addition to those shown in Figure 1 .

Electronic device 100 is a device that constructs and provides various types of information. Electronic device 100 can provide the constructed information via a webpage or application screen, or provide the information in a displayable form on a receiving terminal via a webpage or application screen. In short, electronic device 100 controls and manages the relationship between database 300 and business document 200, as shown in Figure 1. Referring to Figure 2, the relationship between additional components, business document 200, and database 300 that can be used to implement the document provision method described in this invention is described.

FIG2 is a diagram showing the relationship between components of a business document according to an embodiment.

2 , as described above, in addition to being able to control the database 300 associated with the business document 200 through the electronic device 100, the rendering device 400, the UI test box 500, and the user terminal 600 can also be used to provide the business document. According to one embodiment, the business document 200 is a development document related to computer programming and can be shared among business team members. At this time, the business document 200 may include various business contents related to development, but according to one embodiment, it may also include descriptions of UI objects. For example, if the business document 200 is related to the development of e-commerce related services, it may include descriptions of UI objects used to implement the service. In addition, unlike ordinary development documents in the form of static text, the business document 200 can perform actions interactively. For example, the electronic device 100 can receive input from a user terminal 600 connected to the business document 200 via a network, and interactively display at least a portion of snapshots of each of a plurality of types of UI objects on the business document 200, the snapshots being obtained from the database 300. The snapshots described above can be a UI test box 500 rendered by the rendering device 400 and stored in the database 300. The UI test box corresponds to the UI objects designed by the designer in a manner that can be used for the development of the computer program described above. Here, the rendering device 400 can render the UI test box 500 in a customer environment and generate snapshots according to each type. For example, if the customer terminal is primarily a mobile device, the UI test box 500 can be rendered in the mobile device environment and generate snapshots according to each type. According to one embodiment, snapshots of various types rendered in this manner may be stored in the database 300 after undergoing a validation process by comparing them with established design guidelines.

The database 300 and rendering device 400 described above can be devices with computing capabilities that exist independently of the electronic device 100, or they can be included within the electronic device 100. The UI test kit 500 can also be generated in a separate designer terminal or by the electronic device 100. Even if the components have any relationships other than those described above, as long as they provide files that interact with each other as described below, they are considered to be within the scope of the present invention.

3 , a document providing method according to an embodiment of the present invention will be described below.

FIG3 is a flow chart for illustrating a method for providing a document according to an embodiment.

In step S301, the electronic device 100 may confirm snapshots of each of a plurality of types of user interface (UI) objects based on at least one selectable option. In step S302, the electronic device 100 may provide a business document including an item of the UI object. In step S303, the electronic device 100 may confirm input of a business document related to the item of the UI object. In step S304, the electronic device 100 may provide at least a portion of the snapshots of each of the plurality of types of UI objects on the business document based on the input. Each step is described in more detail below.

First, before step S301, a designer may generate a UI test box 500 corresponding to a specified UI object, as described above, and render it in a customer environment via the rendering device 400. Here, the UI object may have multiple types based on at least one selectable option. Snapshots may be generated based on the multiple types of options described above, and each snapshot of the corresponding UI object type may be stored in the database 300 and verified by the electronic device 100. When storing each type of snapshot in the database 300, the file name may be determined according to a specified rule. For example, the file name may be assigned according to the order of the categories of the options that can be selected for the corresponding UI object. For example, if you can select appearance, color, and size options for the corresponding UI, the file name is FILL_RED_MEDIUM, which can include information about appearance options, color options, and size options, in that order.

Thereafter, the electronic device 100 can confirm the source file. The source file serves as the original of the business document and can be produced by the producer terminal. In the source file, various contents including descriptions related to development are recorded, and according to one embodiment, items of UI objects may be included. The items of UI objects may include descriptions of UI objects, a database 300 storing snapshots of various types, and a binding code between the source file. The electronic device 100 compiles the binding code as described above, thereby generating a business document from the source file, and displaying at least a portion of the snapshots of each of the multiple types on the business document, the snapshot being the result of an action performed by binding with the database 300. Here, the binding code may include information about the location in database 300 storing snapshots of the corresponding UI object. The binding code is compiled by electronic device 100, thereby displaying an interactive interface on the business document. This interactive interface displays options that the user can select for the corresponding UI object. Alternatively, the business document may essentially include the contents of the source document, and the binding code is compiled to display the interactive interface and the source document contents simultaneously. This interactive interface is described in more detail below.

The electronic device 100 can provide a business document including an item of a UI object as described above. According to one embodiment, the electronic device 100 can provide the business document to the user terminal 600. Thereafter, the electronic device 100 can confirm the input of the business document 200 related to the item of the UI object. Based on the input, the electronic device 100 can provide at least a portion of the snapshots of each of the multiple types of UI objects on the business document 200. Here, which snapshot of each of the multiple types of snapshots to provide and in what manner to provide them is determined based on the input, so that the electronic device 100 can regard the business document 200 as an interactive provider.

According to one embodiment, to provide at least a portion of snapshots of each of a plurality of types to the business document 200, the electronic device 100 may confirm information regarding each option selected according to each category of at least one selectable option based on input. A snapshot corresponding to one of the plurality of types confirmed based on the combination of options selected according to each category may then be provided to the business document. Examples of categories include appearance, color, and size. Options corresponding to the appearance category may include, for example, fill, tint, and outline. In the case of color, options include red, blue-gray, or black. In the case of size, options include small, medium, or large. For example, if the options for each category described above are combined with a fill for appearance, a blue-gray for color, and a medium for size, then the specific UI object can have one of the types, and the electronic device 100 can provide a snapshot corresponding to the corresponding type on the business document. The following describes an embodiment of receiving option selections for the specific type described above.

First, the electronic device 100 may provide at least one selectable option via a drop-down menu for each category on the business document 200. Thereafter, the electronic device 100 may confirm the input of each selection from the drop-down menu for each category. Referring to FIG. 4 , an example of the drop-down menu for each category described above is described.

FIG. 4 is a diagram showing items of a UI object including a drop-down menu of each category according to one embodiment.

Referring to FIG. 4 , the above example provides drop-down menus 410 , 420 , and 430 categorized by appearance, color, and size. For each category, it can be confirmed that the Fill, Blue-Gray, and Medium options 411 , 421 , and 431 , respectively, have been selected. In response, the electronic device 100 displays a snapshot 440 of the corresponding UI object type below the drop-down menu. According to an embodiment using the drop-down menu as described above, information about the selected option by category can be confirmed.

According to other embodiments, the electronic device 100 may provide a snapshot corresponding to a default type of a UI object, along with a sample code corresponding to the corresponding default type, as an item of the UI object on a business document. Subsequently, in response to a modification of the sample code, the electronic device 100 may input the modified sample code, including information about the selected option, for confirmation. For example, a user may modify the sample code via the user terminal 600, and the options configured to correspond to the default type may be modified in accordance with the corresponding modification. Here, the sample code may be configured to allow selection of options by category. The electronic device 100 can analyze the modified sample code to determine which option has been selected for each category, and can then provide a snapshot corresponding to one of a plurality of categories, determined based on a combination of options for each category, to the business document. This will be described in more detail below with reference to FIG5 .

FIG5 is a diagram showing an item of a UI object according to an embodiment, which can obtain information of an option selected in response to modification of a sample code as input.

Referring to FIG. 5 , a snapshot 510 of a default type UI object is provided. Sample code 520 is provided below the snapshot. Sample code 520 is created to correspond to the options selected for the corresponding default type. The user can modify sample code 520 via user terminal 600 . Specifically, as shown in the figure, the last three lines of sample code 520 are codes specifying appearance, size, and color. In response to the user modifying the corresponding portions of sample code 520, electronic device 100 can provide a snapshot of the type corresponding to the modified options to the business document.

According to one embodiment, if a modified sample code contains unselectable options, the electronic device 100 can provide an inferred snapshot corresponding to the corresponding options. For example, the electronic device 100 can analyze the modified sample code and identify the unselectable options among the input options. It can then identify selectable options in other categories besides the unselectable options and use these to identify similar types. For example, a user may modify the sample code and select Fill, Orange, and Medium in the Appearance, Color, and Size categories, but assume that Orange is an unselectable option. At this point, in addition to the color categories corresponding to the unselectable options included in the modified sample code, the electronic device 100 can confirm similar types based on the Fill and Medium options selected for the appearance and size categories corresponding to the selectable options. That is, types such as red and black that correspond to the Fill and Medium options but have different colors can be confirmed as similar types. Thereafter, the electronic device 100 can adjust the similar snapshots corresponding to the corresponding similar types to generate inferred snapshots. For example, the color of the similar snapshot corresponding to the similar type of the Fill, Red, and Medium combination can be changed to orange to generate an inferred snapshot. The electronic device 100 can provide the inferred snapshots described above to the business document 200, displaying the corresponding snapshots as inferred snapshots. Inferred snapshots can be similarly generated for options other than those exemplified above. For example, when a fill option is entered into a UI object where the fill option is not possible, the electronic device 100 can generate an inferred snapshot corresponding to the selected option. Furthermore, if an inferred snapshot cannot be generated, a message indicating the inability to generate the inferred snapshot can be provided on the business document.

According to one embodiment, the electronic device 100 can transmit the inference snapshot to the designer terminal that generates the UI test box. In this way, the designer can be aware of the corresponding options required by the developer, thereby smoothing the communication between the developer and the designer.

According to one embodiment, even without receiving the aforementioned options from the user terminal, the electronic device 100 can provide at least a portion of the snapshots of each of the plurality of types to the business document 200. For example, the electronic device 100 can sequentially provide at least a portion of the snapshots of each of the plurality of types to the business document 200. Here, as a trigger for sequentially providing at least a portion of the snapshots of each of the plurality of types to the business document, the electronic device 100 can confirm input by hovering the cursor over an area corresponding to an item of the UI object. That is, if the cursor hovers over an area of the business document 200 corresponding to an item of the UI object, at least a portion of the snapshots of each of the plurality of types can be sequentially provided to the business document.

According to one embodiment, the electronic device 100 can determine which snapshot to provide based on the detailed area where the cursor is hovering. Specifically, the electronic device 100 can confirm the category corresponding to the detailed area where the cursor is hovering based on the input. Thereafter, the electronic device 100 can sequentially provide snapshots corresponding to at least a portion of a plurality of categories, confirmed by sequentially applying at least one selectable option for the corresponding category to the default category, to the business document. This is illustrated with reference to FIG6 .

FIG6 is a diagram showing an embodiment of sequentially displaying items of UI objects of various types of snapshots according to hovering of the cursor.

Referring to FIG. 6 , it can be seen that the snapshots are divided into four detailed areas (610 to 640). When the cursor hovers over the first detailed area 610, the electronic device 100 can sequentially provide snapshots of the options corresponding to the corresponding area, i.e., the changes in the shape of the selectable icons. When the cursor hovers over the second detailed area 620, snapshots can be provided of the changes in the selectable options such as the text font, size, or color. When the cursor hovers over the third and fourth detailed areas (630 and 640), the shape, size, or color of the button changes. When the cursor hovers over an area other than the aforementioned areas, snapshots of the overall appearance or color can be provided.

Based on at least some of the embodiments described above, various types of snapshots of UI objects can be provided. Specifically, while the present invention describes three interactive interfaces: a drop-down menu, sample code, and cursor hover detection, embodiments utilizing these interfaces individually can also be implemented, as can embodiments utilizing at least some of these interfaces in combination. For example, an embodiment can be implemented that simultaneously provides a drop-down menu and sample code, and detects cursor hover in each detailed area of the snapshot. In this case, when the options of a UI object are changed via the drop-down menu, the sample code can also be modified accordingly based on the changed options.

Furthermore, the interactive interface described above may include the address information of the folder in database 300, which was previously included in the binding code. For example, the interactive interface may internally include code compiled like <img src="${baseURL}\${componentName}\${appearance}_${color}_${size}"\>, which can retrieve the required snapshot file from database 300 based on the address information described above.

The following describes an embodiment of processing when the option or category selected for a UI object changes.

As described above, electronic device 100 compiles the binding code on the source document, thereby generating the content of the source document and an interactive interface corresponding to the binding code. For example, a business document including a drop-down menu, sample code, and a cursor hover detection area may be generated. At this point, electronic device 100 may confirm change information for at least one option or category, such as the addition of an option to make a UI object selectable or the removal of an option to make it unselectable. Based on the change information, electronic device 100 may update the binding code and compile the updated binding code, thereby updating at least a portion of the business document, namely, the interactive interface portion. For example, in the aforementioned drop-down menu, the electronic device 100 can reflect information about at least one option or category in the drop-down menu for each option or category, which option is added to be selectable or deleted to be unselectable. That is, if red is unselectable in the options of the color category, then as the binding code is updated during compilation, red will be excluded from the options in the drop-down menu corresponding to the color. Alternatively, if all sizes are fixed to medium and the options of the size category are unselectable, the drop-down menu corresponding to the corresponding category can be deleted. Conversely, if orange is added as an option in the color category and is selectable, orange can be added to the options in the drop-down menu corresponding to the color.

Electronic device 100 can confirm the change information described above in response to the addition or deletion of a snapshot in a folder on database 300 corresponding to a binding code. Specifically, if a file is detected to have been added or deleted in a folder on database 300, and database 300 stores snapshots of multiple types of UI objects, electronic device 100 can confirm the change information based on the file name of each snapshot in the corresponding folder. For example, the snapshot file name may specify a status of Category 1 to Category N, thereby including options selected by category. The snapshot file name may be Category 1_Category 2_Category 3_…_Category N. At this point, if red is deleted from category 1, the electronic device 100 can confirm that selecting red is no longer possible, thereby updating the binding code. Furthermore, if category 4 is added to the file name of a snapshot that previously had the form category 1_category 2_category 3, the electronic device 100 can confirm that selecting the new category option is now possible, thereby updating the binding code. Even when deleting a category or adding an option, the electronic device 100 can update the binding code similarly to the above description. Thereafter, the electronic device 100 can compile the updated binding code and update the interactive interface included in the business document.

At this time, the electronic device 100 can further implement a process of verifying the change information. For example, the electronic device 100 can verify the change information by comparing the snapshot added to the folder on the database 300 corresponding to the binding code with other snapshots excluding the added snapshot. For example, the change information includes information that a red option has been added to the color category confirmed based on the file name, but the added snapshot may correspond to yellow instead of red. The electronic device 100 compares the added snapshot with the existing snapshot to determine whether the information indicated by the change information is correct, thereby verifying the change information. At this time, the process described above can be implemented by a neural network that processes the natural language included in the electronic device 100.

FIG7 is a block diagram showing an electronic device according to an embodiment.

According to one embodiment, electronic device 100 may include a memory 101 and a processor 102. The electronic device 100 shown in FIG7 only illustrates components relevant to this embodiment. Therefore, those skilled in the art will appreciate that, in addition to the components shown in FIG7 , other common components may be included. In one embodiment, processor 102 may be included in a controller.

Processor 102 controls the overall operation of electronic device 100 and processes data and signals. Processor 102 may include at least one hardware unit. Furthermore, processor 102 may operate by executing one or more software modules generated by program code stored in memory 101. Processor 102 may include memory and execute program code stored in memory to control the overall operation of electronic device 100 and process data and signals.

The processor 102 is configured to execute one or more instructions to, based on at least one selectable option, confirm snapshots of various types generated in response to a test of a user interface (UI) object having a plurality of types; provide a business document including items of the UI object; confirm input related to the items of the UI object; and, based on the input, provide at least a portion of the plurality of types of UI objects to the business document.

According to an embodiment, the electronic device 100 may further include a transceiver for implementing wired/wireless communication. The electronic device 100 may communicate with an external electronic device using the transceiver. The external electronic device may be a terminal or a server. In addition, the communication technology used by the transceiver may 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 Communication (IrDA), ZigBee, NFC (Near Field Communication), etc.

The electronic device or terminal of the above-mentioned 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, and a user interface device such as a touch panel, keys, or buttons. The method implemented by the software module or algorithm may be stored on a computer-readable recording medium as computer-readable code or program commands that can be executed on the above-mentioned processor. Here, computer-readable recording media include magnetic storage media (e.g., ROM (read-only memory), RAM (random-access memory), floppy disks, hard disks, etc.) and optical readable media (e.g., compact disc read-only memory (CD-ROM) and digital versatile discs (DVD)). Computer-readable recording media are distributed across computer systems connected to a network, enabling the storage and execution of computer-readable code in a distributed manner. The media can be read by the computer, stored in memory, and executed by the processor.

The present embodiment may be represented by a functional block structure and various processing steps. These functional blocks may be implemented by a different number of hardware and/or software structures that perform specific functions. For example, the embodiment may be implemented using an integrated circuit structure that can perform various functions, such as memory, processing, logic, look-up tables, etc., controlled by one or more microprocessors or other control devices. The components may be implemented by software programming or software components. Similarly, the present embodiment includes algorithms implemented by a combination of data structures, procedures, routines, or other programming structures, and thus may be implemented by programming or scripting languages such as C, C++, Java, and assemblers. Functionally, this can be achieved through algorithms executed on one or more processors. Furthermore, this embodiment can utilize existing technologies for electronic environment configuration, signal processing, and/or data processing. Terms such as "mechanism," "element," "mechanism," and "configuration" are used broadly and are not limited to mechanical or physical configurations. These terms can be associated with processors and the like and include software routines.

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

100: Electronic device 101: Memory 102: Processor 200: Business document 300: Database 400: Rendering device 410: Drop-down menu 411: Options 420: Drop-down menu 421: Options 430: Drop-down menu 431: Options 440: Snapshot 500: UI test box 510: Snapshot 520: Sample code 600: User terminal 610: Region 620: Region 630: Region 640: Region S310: Step S320: Step S330: Step S340: Step

Figure 1 illustrates a binding relationship within an electronic device according to an embodiment. Figure 2 illustrates a relationship diagram between components for providing business documents according to an embodiment. Figure 3 illustrates a flow chart for describing a document providing method according to an embodiment. Figure 4 illustrates a UI object including a drop-down menu of categories according to an embodiment. Figure 5 illustrates a UI object that receives information about an option selected in response to a modification of a template code according to an embodiment. Figure 6 illustrates a UI object that sequentially displays snapshots of various categories upon hovering a cursor according to an embodiment. Figure 7 illustrates a block diagram of an electronic device according to an embodiment.

S310: Step

S320: Step

S330: Step

S340: Step

Claims (19)

A document providing method, performed by an electronic device, comprises the following steps: According to at least one selectable option, confirming snapshots of each type of a plurality of types of user interface objects; Providing a business document including items of the UI objects; Confirming input regarding the business document related to the items of the UI objects; Based on the input, providing at least a portion of the snapshots of the plurality of types of UI objects to the business document. The document providing method of claim 1, wherein the step of providing at least a portion of the snapshots of each of the plurality of types in the business document comprises the following steps: Based on the input, confirming information for each option selected according to each category of the at least one selectable option; and Providing a snapshot, the snapshot confirmed based on a combination of the options selected according to each category and corresponding to one of the plurality of types. The document provision method of claim 2, wherein the step of confirming the input comprises the following steps: Providing at least one selectable option via a drop-down menu for each category on the business document; and Confirming the input, including each selection made from the drop-down menu for each category. The document providing method of claim 1, wherein the step of providing the business document comprises the following steps: Providing an item of the UI object as at least a portion of the business document, the item comprising a snapshot corresponding to a default type of the UI object and sample code corresponding to the default type. The document providing method of claim 1, wherein the step of confirming the input includes the following steps: In response to the modification of the sample code, confirming the modified sample code including information of the selected option as the input. The document providing method of claim 5, wherein the step of providing at least a portion of the snapshots of each of the plurality of types in the business document comprises the following steps: Confirming information regarding unselectable options among the options included in the modified sample code; Confirming similar types corresponding to the information regarding selectable options among the options included in the modified sample code; and Adjusting the snapshot corresponding to the similar type based on inferred information corresponding to the information regarding the unselectable options, thereby providing the confirmed inferred snapshot in the business document. The document providing method of claim 6 further comprises the following steps: Transmitting the above-mentioned inference snapshot to the designer's terminal. In the document providing method of claim 1, the step of providing at least a portion of the snapshots of each of the plurality of types to the business document comprises the following steps: Sequentially providing at least a portion of the snapshots of each of the plurality of types of the UI object to the business document. The document providing method of claim 8, wherein the step of confirming the input comprises the following steps: Holding a cursor over an area corresponding to the item of the UI object as confirmation of the input. The document providing method of claim 9, wherein the step of providing at least a portion of the snapshots of each of the plurality of types to the business document comprises the following steps: Based on the input, determining a category corresponding to a detail area where the cursor is hovered; and Sequentially providing snapshots corresponding to at least a portion of the plurality of types to the business document, wherein the plurality of types are determined by sequentially applying at least one selectable option for the category to a default type, the at least one option being at least a portion of the at least one selectable option. The document providing method of claim 1, wherein the step of providing the business document comprises the following steps: Compiling a binding code between a database storing snapshots of each type in a source document and the source document to generate the business document; The step of providing at least a portion of the snapshots of each of the plurality of types into the business document comprises the following steps: Based on the input and the compiled binding code, obtaining from the database at least a portion of the snapshots of each type for rendering the UI object in the customer environment, the snapshot corresponding to at least a portion of the plurality of types. The document providing method of claim 11 further comprises the following steps: Identifying change information regarding at least one option or category, wherein the option is added to make the UI object selectable or deleted to make the UI object unselectable; Updating the binding code based on the change information; and Compiling the updated binding code to update at least a portion of the business document. The document providing method of claim 12, wherein the step of updating at least a portion of the business document comprises the following steps: Compiling the updated binding code to thereby update a drop-down menu associated with an item in the UI object. The document providing method of claim 11, wherein the step of confirming the change information comprises the following steps: In response to the addition or deletion of a snapshot in the folder in the database corresponding to the binding code, confirming the change information. The document providing method of claim 14, wherein the step of confirming the change information comprises the following steps: In response to the addition or deletion of the snapshot, confirming the change information based on the file name of each snapshot of the folder in the database corresponding to the binding code. The document providing method of claim 15, wherein the step of confirming the change information further comprises the following step: Verifying the change information by comparing a snapshot added to the folder corresponding to the binding code in the database with snapshots other than the added snapshot. In the document providing method of claim 1, wherein the business document is a computer programming-related development document shared among business team members, the snapshots of each type are generated by rendering the UI objects according to type as the UI objects are tested in a customer environment. A non-transitory computer-readable recording medium recording a program for executing the method of any one of claims 1 to 17 on a computer. An electronic device for providing a document comprises: a processor; and a memory storing one or more instructions. The processor is configured to: execute the one or more instructions to, based on at least one selectable option, confirm snapshots of various types generated in response to a test of a plurality of types of user interface (UI) objects; provide a business document including items of the UI objects; confirm input related to the items of the UI objects; and, based on the input, provide at least a portion of the plurality of types of the UI objects in the business document.