KR20130008951A

KR20130008951A - The distributed developing method for software

Info

Publication number: KR20130008951A
Application number: KR1020110069672A
Authority: KR
Inventors: 종 진 임
Original assignee: 종 진 임
Priority date: 2011-07-13
Filing date: 2011-07-13
Publication date: 2013-01-23

Abstract

PURPOSE: A software distribution development method is provided to enable each developer to develop tasks, thereby easily developing an application with corporation. CONSTITUTION: When a driving program is executed, a module management unit downloads information for each module from a server(1,2). A control unit in the driving program delivers a module, which is firstly executed, to an engine. The engine executes the delivered module(3). The module which is firstly executed comprises a main screen(4). When an event is generated, the control unit processes the event(5). [Reference numerals] (1) Executing a driving program; (2) Downloading a module; (3) Executing the module; (4) Forming a screen; (5) Processing the event; (6) External module ?; (7) Module exists ?; (AA) Start; (BB) Event occurs ?

Description

The distributed developing method for software

Software Development Tools, Scripts, Engines, Windows

Script, windows

In general, when developing applications, existing development tools had to compile several source files on a single computer to create an executable file.

Of course, some functions may be written in script and executed using a script engine, but the general application itself that develops a screen and shows it to the user and handles the event when the user clicks a menu or a button occurs. We developed, compiled, and distributed the tool.

Therefore, it is difficult for many developers to develop application programs by dividing each module or screen, and source code management is difficult.

In order to solve this problem, each executable file is executed to execute the executable file. In this case, the interface between each executable file is limited, so it is difficult to pass parameters and the screen configuration is limited.

To solve this problem, write code in a language that does not need to be compiled or independently compile and provide an executable file that includes an engine that executes the written code.

In the present invention, since there is no process of compiling the entire source file into a single executable file, each developer can share the task and develop it separately. You can do it separately, so updating is very simple.

This greatly reduces the time and effort required to develop and update software.

1 is an example of the configuration of a program to which the present invention is applied.
2 is an example of a program driving process to which the present invention is applied.

The present invention will be described in detail step by step according to the drawings.

Prior to the description, for convenience of explanation, the following terms will be defined.

Executable file: A file that runs as an independent process. In Microsoft Windows, the file has the EXE extension.

Module: An intermediate or source code file executed by a separate engine within the process of the above executable file rather than a separate process

First, to implement the present invention

An engine unit (for example, a script engine if written in a script language) that executes each module independently written in a language that does not require compilation or is independently compiled;

A control unit which delivers and executes a required module to an engine, creates and controls windows and controls according to a request of each module, and receives an event when an event occurs in a window or each control, and calls a specific procedure in each module;

In addition, if the module is downloaded from the server, the module management unit for downloading the module and providing the module on request of the control unit;

It consists of an executable file (driving program).

The development process applying the method according to the present invention will be described.

Each developer writes his or her part of the program.

Nowadays, most of them are window programs, so we call the control section of the executable file to create windows and controls (child windows), configure the screen, and write a module to include event procedures for the windows and events from each control.

Each module developed is uploaded to the server according to the state of the source code or according to a set rule that makes it easy to compile and distribute each of them into intermediate code.

At this time, it is desirable to encrypt the code content so that it is not exposed to the outside.

Next, a program execution process according to the present invention will be described.

When the running program is executed, the module manager downloads information on each module from the server and checks whether there is an updated module, and downloads the updated module if there is one.

The control unit of the driving program requests the module to be executed first, receives it from the module management unit, and delivers it to the engine, and the engine executes the received module.

The first module executed initializes each variable in the program, creates the necessary objects, calls the control unit, creates a window or control, and brings up the main screen.

When the user clicks a menu or button, the control receives the event and calls a specific procedure in the module to handle the event.

At this time, if a module other than the current module is called, the control unit requests the module manager to receive the module and executes it using the engine.

If there is a parameter provided by the previous module, the new module receives the parameter and configures the screen by creating a window and a control through the control unit.

Repeat the above steps until the user exits the program.

In general, the screen is modularized. Some of the above screens can be included in the executable file to execute the executable file and the module in parallel.

For example, a main screen, a screen that requires speed, or a complex screen can execute code in an executable file, while ordinary screens can execute code in a module.

You can also download a module every time you run a program, or you can download the module every time you call each module.

The above is only one embodiment of the present invention, and various modulations and modifications are possible within the scope of the present invention.

1,2,3,4,5,6,7: each step

Claims

Software development method characterized in that each module is executed by engine instead of executable file type in developing and distributing each module separately without going through compiling entire source file and making one executable file.

In paragraph 1
An engine unit for executing each module written in a language that does not require compilation or independently compiled;
A control unit which delivers and executes a required module to an engine, creates and controls windows and controls according to a request in each module, and receives a event when an event occurs in a window or each control, and calls a specific procedure in each module;
In addition, if the module is downloaded from the server, the module management unit for downloading the module and providing the module on request of the control unit;
Software distributed development method characterized by

In paragraph 1
A first step of executing an executable file;
Step 2 of downloading a module required by the module manager in the executable file;
A third step of transmitting a received module to the engine by requesting the module management unit from the control unit in the execution file;
Step 4, when the engine executes the received module, the module calls a control unit to generate a window and a control, and displays and composes a screen;
Step 5, in which a control unit receives an event when a user clicks a menu or a button on a screen and calls a specific procedure of a module to process it;
In step 5, if it is necessary to call another module, the control unit calls the module management unit. If the module management unit is not yet downloaded, the module proceeds to step 2 to download the necessary module and the control unit proceeds to step 6;
In step 4 again, the engine executes the module;
Software distributed development method characterized by repeating steps 2 to 7 until the end of the program

In paragraph 1
Some execute code in executables and some execute code in each module

In paragraph 1
Software distributed development method characterized by encrypting the source code of each module so as not to be exposed to the outside