KR20200072657A - System for building software of combat system - Google Patents

Abstract

The present invention relates to a combat system software build system. More specifically, the present invention relates to the combat system software build wherein a build time is estimated for each component, and a build work is executed by arranging a work order based on the estimated build time. The combat system software build system includes an estimation unit, an arrangement unit, and an execution unit.

Description

Battle system software build system {SYSTEM FOR BUILDING SOFTWARE OF COMBAT SYSTEM}

The present invention relates to a software build system, and more specifically, to a build system of combat system software such as a trap, and more specifically, to predict the build time of each component to build the combat system software and build order It relates to a software build system for optimizing to shorten the time required for a build operation.

When a software developer writes in accordance with the syntax of a specific programming language and completes the original software source, it is necessary to change the original source to an execution source that is operated in an actual driving environment. In this way, changing the original source to the execution source is called a software build.

Software development can be done by one or two developers if the software to be developed has simple functions. However, when the software to be developed has a large variety of functions, a plurality of developers are forced to write the source by dividing each function or each field. Accordingly, software development by a plurality of developers may be performed after synthesizing the sources developed by each developer and then building the software.

In addition, some contents of the existing source may be changed in already developed software. As described above, when some contents of the existing source are changed, the software build must be performed again with the entire source including the changed contents.

Since the existing build system was developed for the general use of software build, the operation was performed inefficiently because the user had to input all the detailed dictionary information necessary to perform the build based on text.

In addition, since each software component is sequentially built, it takes a considerable amount of time to build a large software such as combat system software, so there is a problem in that work efficiency is reduced.

Therefore, even when building large-scale software such as combat system software, there is a need to develop a technology to predict the build time and optimize the build order.

Therefore, the present invention has been proposed to solve the above-described problems, and even when building large-scale software such as combat system software, software to optimize the build order by predicting the build time of each component. Providing a build system.

In addition, the present invention is to provide a software build system that can reduce the overall build time by reducing the idle time of the process by arranging the build order from the component that takes the longest build time by predicting the build time.

The objects of the present invention are not limited to those mentioned above, and other objects not mentioned will be clearly understood by those skilled in the art from the following description.

The combat system software build system according to the present invention includes a prediction unit for predicting a build time for each component; A placement unit for arranging a work order based on the estimated build time; And an execution unit performing a build operation based on the arranged operation order.

In addition, the battle system software build system according to the present invention, the prediction unit for predicting the build time for each component; A placement unit for arranging a work order based on the estimated build time; And an execution unit performing a build operation based on the arranged operation order.

In addition, the battle system software build system according to the present invention includes: a prediction unit for predicting a build time for each component by an average value of time required for repetitive build operations for each component; A placement unit for arranging a work order based on a build time for each of the predicted components; And an execution unit performing a build operation for each component according to the arranged operation order.

In addition, the battle system software build system according to the present invention includes: a prediction unit for predicting a build time for each component by an average value of time required for repetitive build operations for each component; A placement unit for arranging a work order based on a build time for each of the predicted components; And a performing unit performing a build operation for each component according to the arranged work order, wherein the prediction unit collects a time spent in a build operation repeatedly performed for each component; And a calculator configured to calculate a remaining build time based on the predicted build time, and the placement unit includes an alignment unit to sort the build time for each predicted component in descending order.

According to the present invention, even when building large software such as combat system software, it is possible to optimize the build order by predicting the build time of each component.

In addition, according to the present invention, it is possible to shorten the overall build time by reducing the idle time of the process by arranging the build order from the component that takes the longest build time by predicting the build time.

The effects of the present invention are not limited to those mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the following description.

1 is a block diagram illustrating a combat system software build system according to an embodiment of the present invention.
2 is a flowchart illustrating a method of building a battle system software according to an embodiment of the present invention.
3 is a view for showing an example of component arrangement according to an embodiment of the present invention.
4A is a diagram illustrating an example of a conventional text-based commercial CI tool.
4B is a diagram illustrating an example of a CI dedicated to a combat system according to an embodiment of the present invention.

The objectives and effects of the present invention, and technical configurations for achieving them, will be clarified with reference to embodiments described below in detail together with the accompanying drawings. In describing the present invention, when it is determined that a detailed description of known functions or configurations may unnecessarily obscure the subject matter of the present invention, the detailed description will be omitted. In addition, terms to be described later are terms defined in consideration of donations in the present invention, which may vary according to a user's or operator's intention or practice.

However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms. Only the present examples are provided to make the disclosure of the present invention complete, and to fully inform the person of ordinary skill in the art to which the present invention pertains, the scope of the invention being defined by the scope of the claims. It just works. Therefore, the definition should be made based on the contents throughout this specification.

On the other hand, in the entire specification, when a part is "connected" with another part, it is not only "directly connected" but also "indirectly connected" with another member in between. Includes. Also, when a part “includes” a certain component, this means that other components may be further provided instead of excluding other components, unless otherwise stated.

The present invention is to optimize the build order by predicting the build time of each component in order to build the software and arranging the build order to build the component that takes the longest of the predicted build time.

The commander's battle system software, as an example, has a system that automatically collects information from the various sensors of the ship in the battlefield environment and optimizes it to the best decision and armed use for each situation. Hundreds of functionally divided software components exist because they are composed of various components in order to implement algorithms necessary for acquiring various sensor information, controlling armament, and determining situations with software.

In the development process of each component, the source code is modified several times for each test step, and the modified source code is progressed through a test environment, a regression test, etc. through a build operation.

Since it takes a considerable amount of time to rebuild the modified source code during the development process to create components, if you shorten the build time by streamlining the build process, the development process in the order of source code modification, build, and test The cycle can be shortened. In addition, it can help improve software completeness through additional tests for a shorter time.

These build automation software tools are called CI (Continuous Integration) tools, and there are various open source, commercial products such as TRAC, JENKINS, and JIRA.

However, large-scale software such as this trap combat system software has difficulty in applying existing CI tools due to its specificity.

Therefore, if a large software is built by applying the CI tool according to the present invention, the time required for the build operation may be reduced.

Hereinafter, a method and system for building a battle system software according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram illustrating a combat system software build system according to an embodiment of the present invention.

Referring to FIG. 1, the combat system software build system 100 includes a prediction unit 110, a deployment unit 130, and a performance unit 150.

The prediction unit 110 predicts a time required to build the component, that is, a build time.

The prediction unit 110 includes a collection unit 111 and a calculation unit 113. The collection unit 111 measures the build time required for the build whenever the component is repeatedly built during the development process. To collect. At this time, the average value of the collected build time is predicted as the next build time of the component. That is, in the development process, it collects each build time spent on repeatedly building for components, calculates the average value, and determines the predicted value for the next build time of the component.

However, since a difference may occur in the time required for the build depending on the usage of hardware resources at the time of the build, the correction constant is appropriately determined to reduce the difference between the actual build time and the predicted value.

At this time, the correction constant can be expressed as Equation 1 below based on empirical results.

<Equation 1>

Correction constant = (1 + CPU utilization) × 0.7

Thus, the time required for the build, that is, the build time can be expressed as <Equation 2> below.

<Equation 2>

Build time = (build end time-build start time) × correction constant

Meanwhile, the calculation unit 113 calculates the remaining build time of the corresponding component by subtracting the time spent in the current build from the predicted next build time of the corresponding component.

That is, the remaining build time can be expressed as <Equation 3> below.

<Equation 3>

Remaining build time = Average build time-(Current time-Build start time)

Here, the build tool of the component is a web-based tool, and can display the time spent for build, the remaining build time, etc. through the web browser used by the user.

The placement unit 130 arranges a build order based on a build time required for each component predicted by the prediction unit 110.

Here, the placement unit 130 includes an alignment unit 131, and if the alignment unit 131 sorts the build time required for each component predicted by the prediction unit 110 in descending order, the placement unit 130 ) Places the build work order based on that sort order. That is, the longer the build time is, the more preferentially it is placed to reduce the idle time of the process so that the overall build time can be shortened.

The execution unit 150 builds each component based on the build work order arranged by the placement unit 130.

2 is a flowchart illustrating a method of building a battle system software according to an embodiment of the present invention.

First, it collects the time required to build a component repeatedly, and predicts the average value of the collected time required to build the next component.

The prediction unit 110 predicts the build time of each component in this manner (S201), and the arrangement unit 130 sorts the predicted build time of each component in descending order (S203).

In addition, the placement unit 130 arranges the build work order based on the sort order (S205), and the execution unit 150 builds each component based on the deployed build work order (S207).

3 is a view for showing an example of component arrangement according to an embodiment of the present invention, in the process of building components (C1 to C6) having different build times, the entire build according to the order in which each component is placed This indicates that a difference may occur in the time required for the operation.

Referring to FIG. 3, the first build work process 310 and the second build work process 330 arrange the work order for each component to perform a build work differently, and the time when the build work is completed is also t And t'.

Specifically, the first build work process 310 performed a build operation by allocating tasks to two processes P1 and P2, and finally, as much as t, which is the end of build of the C5 component where the build operation is completed, is completed. It takes time.

On the other hand, the second build work process 330 allocates work to the same two processes P1' and P2' to perform the build work, and as the C5 component that takes the most time to build is placed first, the C2 component It takes time for the entire build operation as much as t'at the end of the build.

Compared to the first build work process 310, the second build work process 330 completed the build operation relatively quickly, because the first build work process 310 inefficiently arranged the order of the build work. to be. That is, the idle time of the first build work process 310 is significantly larger than the idle time of the second build work process 330.

4A is a diagram illustrating an example of a conventional text-based commercial CI tool, and FIG. 4B is a diagram illustrating an example of a CI tool dedicated to a combat system according to an embodiment of the present invention.

In the conventional battle system software build system, after the user inputs all predefined information for the software component build in text through the text-based use CI tool shown in FIG. 4A and registers it with the server, the battle system software build condition is required ( Code update, user request, etc.) are performed automatically and the result is provided. The pre-defined information for this build varies with the storage location of the software, platform information on which the software should be built, and commands for performing the build, and is configured to directly define for each component the user wants to build.

As such, the conventional battle system software build system increases the time required for the build operation in proportion to the size of software to be built according to the physical performance limitations of the build environment.

On the other hand, as the battle system software build system according to the present invention simplifies the definition of the build operation procedure, the user does not need to input all the predefined information for the software component build as text, as shown in FIG. You can perform the build operation by entering.

Referring to Figure 4b, the combat system-specific CI tool according to an embodiment of the present invention is a basic information, name (Name), path (Path), platform (Platform) and project file (Project File) by entering only the build work You can do

However, this is only an embodiment, and basic information that needs to be input to define a build operation procedure can be changed as necessary.

Therefore, the present invention predicts the time required for the build operation of each component, that is, the build time, and preferentially arranges the work order of the component having a long time required for the build operation based on the predicted build time. By reducing the idle time of the process, it is possible to shorten the time required for the entire build operation.

In the present specification and drawings, preferred embodiments of the present invention have been disclosed, and although specific terms are used, they are merely used in a general sense to easily describe the technical contents of the present invention and to understand the present invention. It is not intended to limit the scope. It is apparent to those skilled in the art to which the present invention pertains that other modifications based on the technical spirit of the present invention can be implemented in addition to the embodiments disclosed herein.

Claims (12)

In the battle system software build system,
A prediction unit that predicts a build time required for each component;
A placement unit for arranging a work order based on the estimated build time; And
Combat system software build system, characterized in that it comprises a performing unit for performing a build operation based on the arranged work order.
According to claim 1,
Build time for each component is
When developing, the battle system software build method, characterized in that it is calculated based on the average value of the time spent repeatedly building for each component.
According to claim 1,
The above work order,
Combat system software build system, characterized in that the build time for each predicted component is sorted in descending order.
In the battle system software build system,
A prediction unit that predicts a build time required for each component;
A placement unit for arranging a work order based on the estimated build time; And
Combat system software build system, characterized in that it comprises a performing unit for performing a build operation based on the arranged work order.
According to claim 4,
Build time for each component is
When developing, the battle system software build method, characterized in that it is calculated based on the average value of the time spent repeatedly building for each component.
According to claim 4,
The above work order,
Combat system software build system, characterized in that the build time for each predicted component is sorted in descending order.
In the battle system software build system,
A prediction unit for predicting a build time for each component by an average value of time required for repetitive build operations for each component;
A placement unit for arranging a work order based on a build time for each of the predicted components; And
And a performing unit performing a build operation for each component according to the arranged work order.
The method of claim 7,
Predicting the build time for each component,
Combat system software build system, characterized in that it is predicted by considering the correction constant determined according to the usage of hardware resources.
The method of claim 7,
The above work order,
Combat system software build system, characterized in that the build time for each predicted component is sorted in descending order.
In the battle system software build system,
A prediction unit for predicting a build time for each component by an average value of time required for repetitive build operations for each component;
A placement unit for arranging a work order based on a build time for each of the predicted components; And
It includes an execution unit for performing a build operation for each component in accordance with the arranged work order,
The prediction unit is a collection unit for collecting the time required for the build operation repeatedly performed for each component; And a calculator configured to calculate the remaining build time based on the estimated build time required,
The placement unit includes a sorting unit for sorting the build time required for each of the predicted components in descending order.
The method of claim 10,
Predicting the build time for each component,
Combat system software build system, characterized in that it is predicted by considering the correction constant determined according to the usage of hardware resources.
The method of claim 10,
The placement unit,
Combat system software build system, characterized in that the work order is arranged to minimize the idle time.

Images