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

Abstract

The present invention relates to a combat system software build system, and more particularly, predicts a build time for each component, and performs a build operation by arranging a task sequence based on the predicted build time.

Description

Combat 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 ship, 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 and reducing the time required for the build work.

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

Software development can be done by one or two developers if the software to be developed has a simple function. However, when the software to be developed has vast and diverse functions, a plurality of developers has no choice but to create a source by dividing each function or each field. Accordingly, in the development of software by a plurality of developers, a software build may be performed after the sources developed by each developer are synthesized.

In addition, some contents of existing sources may be changed for software that has already been developed. In this way, when some contents of the existing source are changed, software build must be performed again with the entire source including the changed contents.

Since the existing build system was developed for general use of software builds, the work was performed inefficiently because the user had to input all detailed pre-information necessary for performing the build based on text.

In addition, since each software component is sequentially built, it takes a considerable amount of time to build large-scale software such as combat system software, and thus there is a problem that work efficiency is degraded.

Therefore, even when building large-scale software such as combat system software, there is a need to develop a technology that enables optimizing the build order by predicting the build time required.

Therefore, the present invention has been proposed to solve the above-described problems, and even when large-scale software such as combat system software is built, software that predicts the build time of each component and optimizes the build order. It is in providing a build system.

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

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

The combat system software build system according to the present invention includes: a prediction unit that predicts a build time required for each component; A placement unit for arranging a work order based on the predicted build time; And a performing unit that performs a build operation based on the arranged work order.

In addition, the combat system software build system according to the present invention includes: a prediction unit that predicts a build time required for each component; A placement unit for arranging a work order based on the predicted build time; And a performing unit that performs a build operation based on the arranged work order.

In addition, the combat system software build system according to the present invention includes: a prediction unit for predicting the required build time for each component using an average value of the time taken for the repetitively progressed build work for each component; A placement unit for arranging a work order based on the estimated build time for each component; And a execution unit that performs a build operation for each component according to the arranged work order.

In addition, the combat system software build system according to the present invention includes: a prediction unit for predicting the required build time for each component using an average value of the time taken for the repetitively progressed build work for each component; A placement unit for arranging a work order based on the estimated build time for each component; And a performing unit for performing a build operation for each component according to the arranged work order, wherein the prediction unit includes a collection unit configured to collect time required for the repetitively performed build operation for each component; And a calculation unit that calculates a remaining build time based on the predicted build time required, and the arrangement unit includes a sorting unit that arranges the estimated build time for each component in descending order.

According to the present invention, even when large-scale software such as combat system software is built, the build order can be optimized by predicting the time required to build each component.

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

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

1 is a block diagram showing a combat system software build system according to an embodiment of the present invention.
2 is a flowchart showing a method of building a combat system software according to an embodiment of the present invention.
3 is a diagram illustrating 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 for a combat system according to an embodiment of the present invention.

Objects and effects of the present invention, and technical configurations for achieving them will become apparent with reference to the embodiments described below in detail together with the accompanying drawings. In describing the present invention, when it is determined that a detailed description of a known function or configuration may unnecessarily obscure the subject matter of the present invention, a detailed description thereof will be omitted. In addition, terms to be described later are terms defined in consideration of donation in the present invention, which may vary according to the intention or custom of users or operators.

However, the present invention is not limited to the embodiments disclosed below, and may be implemented in various different forms. These embodiments are provided only to make the disclosure of the present invention complete, and to fully inform the scope of the invention to those skilled in the art to which the present invention pertains, and the present invention is defined by the scope of the claims. It just becomes. 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 said to be "connected" with another part, it is not only "directly connected", but also "indirectly connected" with another member interposed therebetween. Include. In addition, when a part "includes" a certain component, it means that other components may be further provided, rather than excluding other components unless specifically stated to the contrary.

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

Taking the captain's battle system software as an example, the captain's battle system has a system that collects information from various sensors of the ship in the battlefield environment, and is automated to determine the optimal decision for each situation and use the armament. Since it is composed of various components to implement algorithms necessary for acquiring various sensor information, arming control, and situation determination in software, there are hundreds of functionally classified software components.

In the development process of each component, the source code is modified several times in each test step, and the modified source code is carried out through a build operation, loading the test environment, and regression testing.

Among these development processes, it takes a considerable amount of time to create a component by rebuilding the modified source code. Therefore, if the build process is streamlined and the build time is shortened, the development process in the order of source code modification, build, and test. The cycle can be shortened. In addition, it can be helpful to improve the software completeness through additional tests for the shortened time.

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

However, it is difficult to apply the existing CI tools to software of a large scale such as this ship combat system software due to its specificity.

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

Hereinafter, a method and system for building a combat 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 showing 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 an execution unit 150.

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

The prediction unit 110 includes a collection unit 111 and a calculation unit 113, and the collection unit 111 measures the time required for building the component whenever the component is repeatedly built during the development process. To collect. At this time, the average value of the collected build time is estimated as the next build time of the component. That is, the build time required for repetitive builds of the component during the development process is collected, the average value is calculated, and the predicted value for the next build time of the component is determined.

However, since there may be a difference in the time required for the build according to the usage of hardware resources at the time of the build process, the difference between the actual build time and the predicted value is reduced by appropriately determining the correction constant.

In this case, the correction constant can be expressed as shown in Equation 1 below based on the empirical result.

<Equation 1>

Correction constant = (1 + CPU utilization) × 0.7

Accordingly, the time required for the build, that is, the time required for the build can be expressed as shown in 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 required for the current build from the predicted next build time of the corresponding component.

That is, the remaining build time can be expressed as in 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 may display the time spent for building, the remaining build time, and the like through a web browser used by the user.

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

Here, the arrangement unit 130 includes an arrangement unit 131, and when the arrangement unit 131 arranges the build time for each component predicted by the prediction unit 110 in descending order, the arrangement unit 130 ) Is to place the build task order based on that sort order. In other words, the longer the build time is, the more priority 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 deployment unit 130.

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

First, it collects the build time of the repetitive component, and the average value of the collected build time is estimated as the next build time of the component.

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

In addition, the arrangement unit 130 arranges a build operation order based on the arrangement order (S205), and the execution unit 150 performs a build of each component based on the arranged build operation order (S207).

FIG. 3 is a diagram for illustrating 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 arranged It shows that there may be a difference in the time it takes to work.

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

Specifically, the first build work process 310 performed the build work by assigning work to the two processes P1 and P2, and the entire build work as much as t, which is the end point of the build of the C5 component where the build work is completed. It takes time.

Meanwhile, the second build work process 330 performs the build work by assigning work to the same two processes P1' and P2', and as the C5 component, which takes the most time for the build work, is placed first, the C2 component The entire build operation takes time as much as t', which is the end of the build.

Compared to the first build work process 310, the second build work process 330 completed the build work relatively faster, and this is because the first build work process 310 inefficiently arranges the order of the build work. to be. That is, this is because the idle time of the first build work process 310 is considerably 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 combat system software build system, after the user inputs all predefined information for software component build as text through the text-based CI tool shown in FIG. 4A and registers it in the server, the conditions for building the combat system software ( It automatically performs build work according to code update, user request, etc., and provides the result. Pre-defined information for this build is varied, including 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 described above, in the conventional combat system software build system, the time required for the build operation increases in proportion to the size of the 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 of the predefined information for the software component build as text, as shown in FIG. 4B. You can perform build work by entering.

Referring to FIG. 4B, the CI tool dedicated to the combat system according to the embodiment of the present invention is basic information, and builds work by inputting only a name, a path, a platform, and a project file. Can be done.

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

Therefore, the present invention predicts the time required for the build work of each component, that is, the time it takes to build, and based on the estimated time required for each build, the work order of components with a long time required for the build work is preferentially arranged. As a result, the idle time of the process can be reduced, thereby reducing the time required for the entire build operation.

In the present specification and drawings, a preferred embodiment of the present invention has been disclosed, and although specific terms are used, these are merely used in a general meaning to easily explain the technical content of the present invention and to aid understanding of the present invention. It is not intended to limit the scope. It is obvious to those of ordinary skill in the art that other modifications based on the technical idea of the present invention can be implemented in addition to the embodiments disclosed herein.

Claims (12)

In the combat system software build system,
After defining the build operation procedure by receiving basic information including at least one of the name, path, platform, and project file for each component to be built, the build operation of each component is performed. But
A prediction unit that predicts a build time required for each component;
A placement unit that arranges the work order based on the build time for each component predicted by the prediction unit, but arranges the build time for each component in descending order, and then arranges the build work order based on the sort order ; And
Includes; an execution unit that performs a build operation of each component based on the build operation order arranged by the placement unit,
The prediction unit,
A collection unit for collecting build time required for repetitive builds for each component in the development process, calculating an average value of the collected build time, and predicting the next build time for each component; And
And a calculation unit for calculating a remaining build time for each component by subtracting the time required for the current build from the next build time for each component predicted by the collection unit.
delete delete delete delete delete delete The method of claim 1,
The prediction unit,
When estimating the build time for each of the above components,
Combat system software build system for predicting the build time for each component as shown in Equation 2 below in consideration of the correction constant of Equation 1 below, which is determined according to the usage of hardware resources.
[Equation 1]
Correction constant = (1 + CPU utilization) × 0.7
[Equation 2]
Build time = (build end time-build start time) × correction constant delete delete delete delete

Images