KR100738209B1 - System for programming an application based on virtual machine and a method the same - Google Patents

Abstract

A system and a method for developing VM(Virtual Machine)-based enterprise applications are provided to change a dynamic business environment of an enterprise into a mobile environment through a BCP(Business Continuity Planning) service and quickly develop the VM-based enterprise application based on a mobile terminal of enterprise entities with small human resource by using an SDK. A user authentication manager(329) executes a login process through a use authentication server of BCP, and the use authentication server stores information of a developer accessible to a BCP platform. A form creator(328) adds a new form to a project of the VM application(350) through a login procedure. A GUI(Graphic User Interface) form builder(327) sets details of the forms forming the project. An interface designer(326) generates and encodes an interface script by automatically generating an I/O(Input/Output) function for the GUI-built form. The system develops the VM application through the SDK(320) and includes a GNEX(General and NEXt multimedia player)-based operation environment for enabling an enterprise legacy system to communicate with the mobile terminal mounted with the VM application.

Description

SYSTEM FOR PROGRAMMING AN APPLICATION BASED ON VIRTUAL MACHINE AND A METHOD THE SAME

1 is a block diagram showing a BCP service providing system according to an embodiment of the present invention,

FIG. 2 is a block diagram illustrating in more detail the mobile solution shown in FIG. 1; FIG.

3 is a flowchart showing an operation process of the system shown in FIG. 1;

4 is a flowchart illustrating in more detail the step S100 shown in FIG.

5 is a flowchart illustrating in more detail the step S200 shown in FIG.

FIG. 6 is a flowchart illustrating a process of executing a control view function among steps S700 illustrated in FIG. 3;

FIG. 7 is a flowchart illustrating a process of executing an attribute view function among steps S700 illustrated in FIG. 3;

FIG. 8 is a flowchart showing in more detail the step S800 shown in FIG. 3;

9 is a flowchart illustrating a code generation process in step S200 shown in FIG.

FIG. 10 is a flowchart illustrating a code generation process when a control is added to a form in step S700 shown in FIG.

FIG. 11 is a flowchart illustrating a code generation process when an input / output function is added to an interface script generated during step S800 shown in FIG. 3.

<Description of Symbols for Main Parts of Drawings>

100: wireless communication terminal 200: mobile communication network

210: base station 300: BCP platform

310: gateway 320: SDK

321: Code Generator 322: Emulator / Debugger

323: Project Manager 324: Source Editor

325: Compiler 326: Interface Designer

327: GUI Form Builder 328: Form Crater

329: authentication manager 330: library

340: Wifi Genex 350: B-M Applications

400: BCP authentication server 500: Internet

510: dedicated line 511, 512: router

600: Enterprise Legacy System

The present invention relates to a system and method for developing a B-M based enterprise application, and more particularly, to a B-M based enterprise application including an SDK for developing the enterprise application in a short time. A system and method for feet.

In recent years, companies have tended to build a corporate legacy system for processing a line of business by utilizing a wireless communication terminal owned by each member in order to meet a dynamic work environment. As a service for a dynamic work environment to be implemented through the enterprise legacy system, a sales force automation (SFA) service for mobilizing and providing customer information to a remote salesperson, and an external service for customer A / S processing Field Force Automation (FFA) service that provides customer or technical information to A / S personnel, SCM (Supply Chain Management) service for realizing rapid and accurate inventory management, and mobilizing transportation and delivery business, and securing number of customers In addition, there are customer relationship management (CRM) services to collect customer information on site to collect and improve customer quality, and to collect customer preferred product information.

Here, the enterprise legacy system introduces and has a mobile solution for implementing the service through a mobile communication network established by a communication provider. As a result, the system is uncertain in terms of the installation cost, the upgrade cost may be incurred due to the evolution of the mobile solution, the development of the application for the service will take a long time, and the service itself as a service There is a burden to operate. In addition, the system is not easy to cope with the change of the wireless communication terminal possessed by the corporate member, and the system must be rebuilt to cope with the evolution of the mobile communication network by using the mobile communication network of the carrier as an infrastructure. Problems arise.

Accordingly, a BCP including a mobile solution for implementing a service according to a dynamic business environment by a service provider providing an infrastructure of a mobile communication network rather than an enterprise legacy system having a mobile solution on its own. A business continuity planning (BCP) service has emerged that provides a working environment infrastructure between a corporate legacy system that provides a platform and establishes a database for corporate business through a wireless communication terminal of a corporate member through the BCP platform. The BCP service provides one-stop operation from B-M applications of wireless communication terminals owned by corporate members, including authentication, encryption, data conversion, business logic processing, and communication with corporate legacy systems. The service to implement.

However, as it takes a lot of manpower and time to develop a B-M application that meets the needs of a corporate customer based on the BCP service, the development of the B-M application at the request of various corporate customers is delayed. There was a problem that the cost rises.

Therefore, the present invention has been created to solve the above problems, an object of the present invention is to make the dynamic work environment of the enterprise through the BCP service, the enterprise B-M based on the wireless communication terminal of the corporate member The present invention provides a system and method for developing a B-M-based enterprise application including SDK to develop an application in a short time with a small staff.

In order to achieve the above object, a system for developing a B-M-based enterprise application according to the first aspect of the present invention may generate, project and emulate a source file programmed and generated by a project for a predetermined B-M application. B-M in development through a login authentication process to execute a login-authentication process through a BCP authentication server that stores developer information accessible to the BCP platform in an SDK provided in the BCP platform for debugging. Generates interface scripts by automatically generating input and output functions for GUI form builders and GUI-built forms for setting form requirements for adding new forms to the project's project, the form forming the project, and Further includes an interface designer for coding interface scripts And that is characterized.

Preferably, a predetermined B-M application is developed through the SDK, and a wireless communication terminal equipped with the B-M application and the enterprise legacy system are provided as a Genex-based operating environment for mutual communication. It is done.

In addition, a method for developing a B-M based enterprise application according to a second aspect of the present invention for achieving the above object is (a) a newly created form file in a predetermined project for the development of the B-M application or A control view function for adding a pre-stored form file to a database, selecting a GUI control and an interface control used in the B-M application, placing the GUI control and the interface control in the form file, and then Executing a form building on the form file using a GUI form builder that provides a form view function to provide and a property view function to set property values of the GUI control, an interface control, and the form file itself. Characterized in that.

Preferably, the method further comprises the step of (b) executing the use authentication for the developer to which the SDK attempts to access.

Hereinafter, a preferred embodiment of a system for implementing a BCP service according to the present invention with reference to the accompanying drawings in more detail.

First, in the present invention, in developing a B-M application 350 according to a request of a corporate customer, the key for developing the B-M application 350 is to reflect the requirements desired by the corporate customer in a short time. Developing with workforce is key. As a development characteristic for this, the enterprise B-M application 350 based on the company's main work has characteristics similar to each other in user interface or application configuration. By equipping the BCP platform 300 with a mobile solution including the SD 320 reflecting these characteristics, an optimal application development environment is realized.

1 is a block diagram illustrating a BCP service providing system according to an embodiment of the present invention. As shown in FIG. 1, the system is provided through an enterprise legacy system 600 having a main server and a database for a line of business, the enterprise legacy system 600 and the Internet 500, or routers 511, 512. The BCP platform is connected to a dedicated line 510 and the BCP platform 300 includes a BCP platform 300 for developing a B-M application 350 for implementing a BCP service requested by a corporate customer, and a mobile communication network 200 including a base station 210. By starting the B-M application 350 provided from the 300 to communicate with the enterprise legacy system 600, the wireless communication terminal 100 and the developer information for accessing the BCP service to the wireless communication terminal 100 In order to determine the BCP platform 300 includes a BCP usage authentication server 400 is connected.

The corporate member using the BCP service starts the corresponding B-M application 350 of the wireless communication terminal 100 possessed by the user and accesses the BCP platform 300 through the mobile communication network 200. Due to the connection through the gateway 310, the BCP platform 300 executes the use authentication in conjunction with the BCP use authentication server 400, and when the authentication process is completed, the process of encryption, data conversion, business logic processing, etc. In one-stop interworking with the enterprise legacy system 600 having a server and a database related to the main work.

In addition, a mobile solution is provided in the BCP platform 300 to implement a BCP service. The mobile solution includes an SD 320 for developing a corresponding B-M application 350 to provide a BCP service requested by an enterprise customer. It is preferable to implement an environment for operating the B-M application 350 in the BCP service based on Genex. Of course, the SDK 320 is based on Genex, and is implemented to develop a large number of B-M applications 350 requested by various corporate customers with a short workforce.

FIG. 2 is a diagram illustrating the mobile solution of FIG. 1 in more detail. As shown in FIG. 2, the mobile solution includes a SD library 320 for developing a B-M application 350, a beads library 330 for storing controls and forms used repeatedly for the SDK 320. And a Wi-Fi Genex 340 for matching the B-M application 350 developed in the SD 320 with an infrastructure providing a BCP service.

The existing SD 320 may include a project manager 323 for generating a project, a source editor 324 for programming using mobile C, a compiler 325 (or assembler) for converting a source file into an executable file, and the execution. An emulator 322 for testing the file, a debugger 322 for checking and correcting errors, a code generator 321 for parsing and generating code of the formed file, and the like. SDK 320 of the present invention is a user authentication manager (329) for executing a log-in process through the BCP use authentication server 400 stored in the developer information that can be connected to the existing BCP service 320, Form Clarator for adding new forms to the project of the B-M application 350 under development after being certified for use, GUI Form Builder 327 for setting sub-settings for the forms forming the project, and GUI building It further includes an interface designer 326 for automatically generating an input / output function for the completed form to generate an interface script, and for coding the interface script. The SDK 320 can significantly reduce coding work due to the additionally included device, and enables the development of the Wiziwick method in the development of the B-M application 350.

Hereinafter, the operation of the BCP service providing system according to the present invention with reference to the accompanying drawings in more detail as follows.

FIG. 3 is a flowchart illustrating an operation process of the system shown in FIG. 1. As shown in FIG. 3, in the method for generating the B-M application 350 according to the present invention, the developer of the B-M application 350 connects to the SD 320 of the BCP platform 300. A developer authentication process for performing a log-in process through a developer account and a password is executed (S100).

In addition, the developer generates a project for developing a predetermined B-M application 350 using the project manager 323 (S200). The developer generates a source file by driving the source editor 324 to perform programming for the B-M application 350 under the project (S300). In addition, the developer who has undergone the developer certification process may create a new form for the application under development using the form crater 328 of the SDK 320 and add it to the project (S400). In addition, the developer may cancel while the process of adding a new form (S500). In addition, the form newly created by the developer is stored and managed in the database of the SDK 320 (S600).

In addition, the developer selects a predetermined form file included in the form file item from the workspace of the SDK 320 to execute Wi-Wick's programming while programming the B-M application 350. At this time, in the selection of a form file, as described above, a new form is created by adding a new form creation / addition menu in the operation menu, and then a new form is selected or the form is saved by executing the add form menu. Select a form file from the file. Due to the selection of the form file, the SD 320 programming screen is switched to the GUI form builder 327 screen. Accordingly, the developer executes the building of the selected form using the control view, form view, and property view functions of the GUI form builder 327 (S700).

In addition, the developer automatically generates an input / output function for the built form file using the interface designer 326, generates an interface script through the input / output function, and codes the interface script to execute the B-M application 350. Implemented as a source file (S800). Thereafter, the developer converts the source file formed through the above process into an executable file such as an SGS file through the compiler 325 (or assembler) (S900). In addition, the executable file is tested through the emulator 322, and the executable file, which has been tested, checks for errors through the debugger 322 and corrects errors (S910). The developer generates the B-M application 350 through the above process (S920).

FIG. 4 is a flowchart showing in more detail the step S100 shown in FIG. 3. As shown in FIG. 4, in step S100, the developer inputs a developer account and password through the SD 320 of the BCP platform 300 (S102). The developer account and password entered by the developer is transmitted to the BCP using authentication server 400 that stores the developer information that can be authenticated (S104). The BCP user authentication server 400 compares and determines the stored developer information on the basis of the authorized developer account and password, and if the comparison determination result is confirmed to be authenticated, the developer accepts the log-in (S106). In addition, if the developer account and password entered by the developer do not meet the rules, the client is filtered again by the corresponding client of the SDK 320. If the login is failed, the cause of the log-in failure using the message box is failed. Pass it to the developer correctly. If login fails due to a password error several times, the account is temporarily blocked and the block is closed after the administrator's approval.

FIG. 5 is a flowchart illustrating the S200 step shown in FIG. 3 in more detail. As shown in FIG. 5, in step 200, a developer may select a new form creation / addition menu or a form addition menu from among execution menus for a project of the B-M application 350. If the developer selects a new form creation / addition menu, the form crater 328 of the SD 320 is executed on the screen (S202). Accordingly, the developer inputs a form property including a form name, form width, form height, and background color on the form creator screen (S204). In addition, the developer selects whether to generate or cancel the form according to the form property input value (S206). The form script to which the form attribute input value is applied is generated in the XML format by the developer / addition execution (S208). The form script is written in mobile C code that is responsible for the presentation of the form through the code generator 321 (S210). Accordingly, the newly generated form file is newly added to the form file item in the work menu of the SDK 320 and is switched to the GUI form builder 327 screen in the form creation screen (S212). Also, if a developer cancels the form creation in the form creation screen, all the property values related to the form are deleted. In addition, the form attribute value input by the developer can be limited to the format and range suitable for each field.

FIG. 6 is a flowchart illustrating an execution process of a control view function in step S700 illustrated in FIG. 3. As shown in FIG. 6, in step S700, the developer selects a GUI control and an interface control to be placed in the selected form file through the control view function of the GUI form builder 327 (S702). In addition, the GUI controls and the interface controls are placed in the form file through the form view function of the GUI form builder 327 (S704). Alternatively, the GUI control and the interface control may be canceled to reselect predetermined controls or the GUI form builder 327 may be immediately terminated (S706).

In addition, in step S704, when the controls are placed in the corresponding form file, the stored form script is also updated (S708). Accordingly, the presentation code, which is a mobile C code, is also updated together with the update of the form script (S710). Form arrangement of the controls selected by the developer is made through the above process (S712). In addition, when the developer wants to add a new control after form placement of the controls, the developer further executes steps S702 to S712 (S714). In addition, the developer may delete the placed control from the form file using a mouse or a keyboard hot-key (S716). The deleted or added control changes the form script in XML format, and accordingly, the mobile C code that is responsible for presentation of the form is updated again through the code generator 321.

As part of the form building, it is also possible to move up, down, left, and right of the control placed in the form file, and the movement of the control also updates the mobile C code of the corresponding form script (S718). This completes the form placement of the controls. The starting coordinates of the GUI controls do not leave the area of the form, and the GUI controls do not overlap each other and are not disposed on the form. In addition, if you select a control through the Control View function and then perform another action without placing the control selected by the Form View function on the form, the control is automatically selected. In addition, if the form presentation code is forcibly changed from the outside, the code is not reflected in the form design.

FIG. 7 is a flowchart illustrating an execution process of an attribute view function in step S700 illustrated in FIG. 3. As shown in FIG. 7, the property view function of the GUI form builder 327 is a function of setting property values of a GUI control, an interface control, or a corresponding form file itself. The developer selects a predetermined control from among the controls arranged on the form (S720). Due to the selection, the property settable for the control can be edited by an input means such as a hot key of a mouse or a keyboard (S722). The property view function of the control is activated due to the editing process by the input means (S724). The developer selects a corresponding property to be changed through the active window displayed on the monitor (S726). The attribute value of the selected attribute is modified within the changeable range (S728). Accordingly, the form script of the XML method is updated and stored due to the property value of the modified control (S730). The form script updates the mobile C code in charge of the presentation of the form through the code generator 321 (S732). The form view is updated through the above process (S734). If the property value is not changed in step S728, the property is set to a preset property value.

FIG. 8 is a flowchart illustrating in more detail the step S800 illustrated in FIG. 3. As shown in Figure 8, in step S800, select the control disposed on the form (S802). In selecting the control, the developer selects the GUI control and the interface control supported by the data binding function by the hot key of the mouse or the keyboard to execute the interface designer 326 (S804). In addition, the GUI controls that provide interface controls and data binding capabilities are grid view controls, radio button controls, and combo box controls. The execution screen of the interface designer 326 is displayed on the monitor (S806). Accordingly, the developer selects the in / out field (S808). Select the type (read or write) of the function to be added to the source control, the selected control (S810). In addition, an out control which is a control to be read or written is selected (S812). The out control is an interface control included in a form.

Thereafter, function field names for the two controls are defined (S814). The mapping is performed between the same field names among all the input / output fields (S816). In addition, due to the mapping, an interface script of an XML method is created (S820). This completes the interface design by the interface designer 326.

In addition, when a GUI control that does not support data binding is selected in the form, the execution menu of the interface designer 326 is not activated, and the source and the date of the data binding cannot be the same control.

FIG. 9 is a flowchart illustrating a code generation process in step S200 illustrated in FIG. 3. As shown in FIG. 9, the coding process when adding the generated form is as follows (S930). First, when a form is generated by the form generator, a form script is generated using the form name (hereinafter, 'SAMPLE' will be described as an example) (S932). The form script is generated and stored as 'SAMPLE.FRM' according to the XML method. The form script also includes attribute information of the form and information about controls placed on the form. The SD 320 calls the code generator 321 when the form script is completed (S934). The code generator 321 parses the stored form script (S936). In addition, the XML parsing process is monitored (S938). In addition, when the XML parsing process is abnormal, a warning message is output on the work screen and notified to the developer (S940). Accordingly, the developer cancels the code creation of the generated form after checking the warning message (S942).

Meanwhile, when the XML parsing process is normally performed, a SAMPLE_VIEW.mc file and a SAMPLE_ACTION.mc file are generated (S944). The main function of the form name is implemented in the SAMPLE_VIEW.mc file, and the code for drawing the form and handling the event is created. In addition, the SAMPLE_ACTION.mc file implements developer-defined logic for handling events in controls and forms. For each form generator event, a function prototype is declared.

In addition, when the SAMPLE_VIEW.mc file is updated due to a form script modification, any work added by the developer to the SAMPLE_VIEW.mc file is not preserved. In addition, if the verification of the form script fails, the failed message is displayed correctly so that the developer can check it.

FIG. 10 is a flowchart illustrating a code generation process when a control is added to a form in step S700 illustrated in FIG. 3. As shown in FIG. 10, the coding process when the control is added in the form building process is as follows (S950). First, a process of adding or modifying a selected control to a form script is executed (S952). When the control is added to the form or the information of the pre-arranged control is modified, the form script with the form name is stored as 'SAMPLE.FRM' rewritten according to the XML method based on the modified information. When the writing of the form script is completed, the SD 320 calls the code generator 321 (S954). In addition, the code generator 321 parses the corresponding form script (S956). In addition, the parsing process is monitored (S958). In addition, when the XML parsing process is abnormal, a warning message is output on the work screen and notified to the developer (S960). Accordingly, the developer cancels the code creation of the generated form after checking the warning message (S962).

Meanwhile, when the XML parsing process is normally performed, a SAMPLE_VIEW.mc file and a SAMPLE_ACTION.mc file are generated (S964). The main function of the form name is implemented in the SAMPLE_VIEW.mc file, and the code for drawing the form and handling the event is created. In addition, the SAMPLE_ACTION.mc file implements developer-defined logic for handling events in controls and forms. For each form generator event, a function prototype is declared.

In addition, when the SAMPLE_VIEW.mc file is updated due to a form script modification, any work added by the developer to the SAMPLE_VIEW.mc file is not preserved. In addition, if verification of the form script fails, the failed message is displayed correctly so that the developer can check it. And, if there is already implemented code when adding function prototype to SAMPLE_ACTION.mc file, the existing code is preserved.

FIG. 11 is a flowchart illustrating a code generation process when an input / output function is added to an interface script generated in step S800 shown in FIG. 3. As shown in FIG. 11, the coding process when adding an input / output function to the SAMPLE form is as follows (S970). The control (GridView, INetwork, IFile, ISerial) interworking with the interface designer 326 among the controls arranged on the form additionally generates a function for performing input / output operations to the control through the interface designer 326 (S972). When the function design using the interface designer 326 is finished, the function is stored in an XML file named 'SAMPLE.INF'. After storing the INF file, the code generator 321 is called (S974). In addition, the code generator 321 parses the INF file (S976). In addition, the parsing process is monitored (S978). In addition, when the XML parsing process is abnormal, a warning message is output on the work screen and notified to the developer (S980). Accordingly, the developer cancels the code creation of the generated form after checking the warning message (S982).

Meanwhile, when the XML parsing process is normally performed, a mobile C input / output function is implemented using the INF file information (S984). The mobile C code implemented in step S986 is written in a format such as SAMPLE_IO.mc. Through the above process, the coding process for adding the input / output function is completed. In addition, if the interface script verification fails, the developer should accurately reflect the failed message. If the developer modifies the input / output function implemented in the SAMPLE.INF file, the code added by the developer is not preserved when the function design information for the function is modified and the SAMPLE.INF file is updated.

Although described above with reference to a preferred embodiment of the present invention, those skilled in the art will be variously modified and changed within the scope of the invention without departing from the spirit and scope of the invention described in the claims below. I can understand that you can.

Therefore, in the present invention, by developing an SDK for developing a G-NEX-based B-M application on the BCP platform for providing a work environment infrastructure between the enterprise legacy system and the wireless communication terminal, the developer exactly meets the requirements desired by the customer. Reflected B-M applications can be developed with less manpower in the shortest time possible. In addition, the business application for the enterprise has the characteristics that the user interface or the configuration of the application is similar to each other, the present invention reflects the above similar characteristics to overcome the limitations of the existing universal SDK for the development of enterprise B-M application development There is an advantage to implement the development environment of.

Claims (36)

A system comprising a BCP platform equipped with an SDC for generating, projecting, emulating, and debugging a source file programmed by creating a project for a predetermined B-M application. A usage authentication manager for executing a log-in process through a Business Continuity Planning (BCP) usage authentication server storing developer information accessible to the BCP platform; A form clarator for adding a new form to the project of the B-M application through a log-in process; A graphical user interface (GUI) form builder for setting the general requirements of the form forming the project; And System for the development of B-M based enterprise application, characterized in that it automatically generates the input and output functions for the GUI building form, the interface script, and SDC including the interface designer for coding the interface script . The system of claim 1 wherein the system is In order to develop a predetermined B-M application through the SDK, the wireless communication terminal equipped with the B-M application and the enterprise legacy system are provided with a Genex-based operating environment. System for developing M-based enterprise applications. In the method for developing a B-M application using the SDC provided in the BCP platform for providing a work environment infrastructure between the enterprise legacy system and the wireless communication terminal, (a) a control view for adding a newly created form file or a pre-stored form file to a predetermined project for developing the B-M application and selecting a GUI control and an interface control used in the B-M application; A function, a form view function for providing a user interface, and a property view function for setting property values of the GUI control, an interface control, and the form file itself after placing the GUI control and the interface control in the form file. A method for developing a B-M based enterprise application comprising the step of executing a form building on the form file using a GUI form builder providing. The method of claim 3 wherein the method is A method for developing a B-M based enterprise application, wherein the G-NEX is adopted as the operating environment of the B-M application, and the B-M application is developed in the SDK based on the Genex. The method of claim 3, wherein step (a) comprises: (a-1) the developer activating a menu window to select a form creation and addition menu or a form addition menu; (a-2) executing the form crater when selecting a form creation and addition menu; (a-3) setting properties of a form to be generated using the form crater; (a-4) storing the generated form script by executing form creation and addition according to the setting; (a-5) the form script is written in mobile C code that is responsible for presentation of a form through a coding process; And (a-6) A method for developing a B-M-based enterprise application, comprising the step of switching to a GUI form builder screen with the form added to the form file item of the SDK. The method according to claim 5, wherein in (a-3), The property of the form is set to be limited within the data of the format and range for each field limited. The method of claim 5, wherein in step (a-4), The form script is a method for developing a B-M-based enterprise application, characterized in that implemented in XML. The method of claim 5, wherein (a-5) step, (a-5_1) parsing the form script through a code generator provided in the SDK when the form script generation is completed; And (a-5_2) When the parsing process is executed normally, the mobile C code is implemented in the form of 'form name_VIEW.mc file' and 'form name_ACTION.mc file' using the parsed information. Method for developing a B-M-based enterprise application, characterized in that made. The method of claim 8, wherein in the step (a-5_2), The main form of the form name is implemented in the 'form name_VIEW.mc file', and a method for developing a B-M-based enterprise application, characterized in that a code for drawing and processing an event is written. The method of claim 9, wherein in the step (a-5_2), When the 'form name_VIEW.mc file' is updated due to the birth of the form script, the B-M, which the developer adds to the 'form name_VIEW.mc file', is not preserved. For developing business-based enterprise applications. The method of claim 8, wherein in the step (a-5_2), The 'form name_ACTION.mc file' is a method for developing a B-M-based enterprise application, characterized in that the developer defined in relation to the GUI control, the interface control and the event processing for the form is implemented. . The method of claim 5, wherein step (a-6), (a-6_1a) in the form building using the control view and the form view function, selecting a predetermined form file from the form file item of the SDK and switching to a GUI form builder screen; (a-6_2a) selecting at least one of the GUI control and the interface control in the control view and placing the selected control on the form; (a-6_3a) updating the form script based on the control information placed on the form; And (a-6_4a) updating the mobile C code of the form in accordance with the update of the form script. The method of claim 12, wherein in the step (a-6_2a), The control disposed on the form comprises the step of changing the position up / down / left / right by the developer's settings. The method of claim 12, wherein in the step (a-6_2a), And deleting the control disposed on the form from the form through an input means including a hot-key of a mouse or a keyboard. The method of claim 12, wherein in the step (a-6_2a), And adding a predetermined control to the control placed form through the control view. The method of claim 12, wherein in the step (a-6_2a), The SDK may automatically release the control selected by the control view when performing another operation before placing at least one of the GUI control and the interface control on the form through the form view function. For developing B-M based enterprise applications. The method of claim 12, wherein in the step (a-6_4a), If the mobile C code that is responsible for the presentation of the form is forcibly changed from outside the GUI form builder, the method for developing a B-M-based enterprise application, characterized in that not reflected in the form design. The method of claim 12, wherein in the step (a-6_4a), (a-6_4a_1) regenerating the form script based on the added or modified information when the control information added or pre-located to the form is modified; (a-6_4a_2) parsing the form script through a code generator provided in the SDK when the form script generation is completed; And (a-6_4a_3) When the parsing process is executed normally, the mobile C code is implemented in the form of 'form name_VIEW.mc file' and 'form name_ACTION.mc file' by using the parsed information. Method for developing a B-M-based enterprise application, characterized in that made. The method of claim 18, wherein in the step (a-6_4a_3), The main form of the form name is implemented in the 'form name_VIEW.mc file', and a method for developing a B-M-based enterprise application, characterized in that a code for drawing and processing an event is written. The method of claim 18, wherein in the step (a-6_4a_3), The 'form name_ACTION.mc file' is a method for developing a B-M-based enterprise application, characterized in that the developer defined in relation to the GUI control, the interface control and the event processing for the form is implemented. . The method of claim 5, wherein step (a-6), (a-6_1b) in the form building using the property view function, selecting at least one of the GUI control and the interface control disposed on the form by the form view function; (a-6_2b) editing a settable property by activating a property view function for at least one of the GUI control and the interface control; And (a-6_3b) Updating a form script of the form file by reflecting the attribute value changed in the editing process, and updating the mobile C code corresponding to the form script How to develop an application. The method of claim 21, wherein step (a-6_2b) In the editing of the property, if the required input item is set to be edited and completed, the SDK displays a warning message on the screen using a message box, and includes moving the cursor to the corresponding input item. Method for developing a B-M-based enterprise application, characterized in that. The method of claim 5, wherein step (a-6) And designing an interface through an interface designer that automatically generates an input / output function through a data binding function between a GUI control disposed on the form and an interface control. The method of claim 23, wherein the (a-6) step, (a-6_1c) selecting at least one source control for designing an interface among the GUI control and the interface control disposed on the form; (a-6_2c) setting a type of a function to add to the source control by executing the interface designer; (a-6_3c) selecting the out control to be read or written by the setting; (a-6_4c) generating an interface script by mapping input / output fields between the source control and the out control; And (a-6_5c) A method for developing a B-M based enterprise application comprising the step of completing the interface design by writing the interface script as a mobile C function in charge of the interface of the form through a coding process . The method of claim 24, wherein in the step (a-6_1c), If the source control is a GUI control that does not support the data binding function, the execution screen of the interface designer is deactivated. The method of claim 24, wherein in the step (a-6_3c), And a control corresponding to the out control is an interface control included in the form. The method of claim 24, wherein in the step (a-6_4c), The interface script is a method for developing a B-M-based enterprise application, characterized in that implemented in XML. The method of claim 24, wherein the step (a-6_5c) (a-6_5c_1) generating a function for performing an input / output operation in a corresponding control due to a control interworking with the interface designer when adding a predetermined input / output function to the interface script; (a-6_5c_2) after the function design using the interface designer is completed, storing the generated input / output function in an XML file of a form “form name.INF”; And (a-6_5c_3) The INF file comprises the step of being implemented as an input and output function of the mobile C code through the code generator provided in the SDK B-M-based enterprise application development method. The method of claim 23, wherein in step (a), GUI control for providing a data binding function with the interface control comprises a grid view control, radio button control, combo box control. The method of claim 3, wherein in step (a), The start coordinates of the GUI control is disposed in the form area for a B-M based enterprise application development. The method of claim 3, wherein in step (a), And the GUI controls are placed on the form so that they do not overlap with each other. The method of claim 3 wherein the method is (b) executing the use authentication for the developer to which the SD is trying to access the B-M-based enterprise application development method. 33. The method of claim 32, wherein step (b) comprises: (b-1) the SDK displaying a log-in generation screen on a developer access screen; (b-2) a developer inputting a developer account and password on the log-in creation screen; (b-3) receiving, by the BCP user authentication server, the developer account and password to determine whether to use the authentication; And (b-4) The SDK is a method for developing a B-M based enterprise application, characterized in that the step of switching to the application development activation screen when the use authentication determination result received from the BCP use authentication server is normal. . The method of claim 33, wherein in step (b-4), The SDK comprises the step of returning to the log-in creation screen for re-authentication if the received use authentication determination result is log-in failure, characterized in that for the BR-M based enterprise application development method . The method of claim 34, wherein in step (b-4), The SDK uses a message box to display a log-in failure cause, including an unregistered account or password error on the connection screen, characterized in that for the B-M-based enterprise application development. The method of claim 35, wherein in step (b-4), The SDK temporarily blocks the corresponding account when failing to log in due to a password error more than a few times, and terminates the block with the approval of an administrator. Way for you.

Images