KR102261841B1 - Device for recommending cloud system based on legacy environment analysis - Google Patents

Abstract

A cloud system recommendation method according to an embodiment of the present invention includes the steps of retrieving a cloud system recommendation history and information on the cloud system, receiving environmental information, requirements, and budget of the legacy system, the environmental information and the budget and recommending a cloud system according to the steps and storing the recommended cloud system.

Description

{DEVICE FOR RECOMMENDING CLOUD SYSTEM BASED ON LEGACY ENVIRONMENT ANALYSIS}

The present invention relates to a device for recommending a cloud system by analyzing a legacy environment.

Recently, as the development and dissemination of cloud computing-related technology expands, not only the private sector, but also the government and public sector can eliminate negative factors in the construction and management of the existing computing environment, such as cost reduction, efficient use of resources, and management convenience. We are actively promoting the introduction of cloud computing that can In general, when a new computing environment is introduced, the most desirable in terms of development and operation is to build a new one in the new environment, but since it is difficult to stop data or services in operation, the technology or method for transferring them to the cloud computing environment is difficult. have to pay a lot of attention.

Currently, the transfer to the cloud computing environment is determined by the transfer experts of each cloud service provider, and then the method and cost are determined. Therefore, the period required for analysis varies depending on the complexity and constraints of the existing legacy environment, and it is difficult to guarantee the objectivity of the recommended transfer method or the calculated cost. In addition, when using a cloud service provider, it is difficult and time consuming to find a suitable service to move and operate the current environment because each company provides a variety of services. It is difficult to guarantee a more optimized service by comparison.

Korean Patent Laid-Open Publication No. 10-2012-0116773 (published on October 23, 2012)

The problem to be solved by the present invention can contribute to the spread of the cloud computing environment by automating and more objectifying the process in which such passive and subjective bias intervention is possible, and each institution or individual considering cloud introduction conforms to their own operating concept. Find the right cloud service for you to use and allow you to consider an appropriate migration method.

However, the problems to be solved of the present invention are not limited to those mentioned above, and other problems to be solved that are not mentioned can be clearly understood by those of ordinary skill in the art to which the present invention belongs from the following description. will be.

A cloud system recommendation method according to an embodiment of the present invention includes the steps of retrieving a cloud system recommendation history and information on the cloud system, receiving environmental information, requirements, and budget of the legacy system, the environmental information and the budget and recommending a cloud system according to the steps and storing the recommended cloud system.

In addition, the step of recommending the cloud system may include reviewing whether the legacy system is transferable according to the environment information, comparing it with the recommendation history, and recommending a cloud system according to the cost within the requirements and budget range. .

In addition, if the budget is not determined, the cost may be adjusted to a minimum amount that satisfies the environmental information.

In addition, before the step of calling the cloud system recommendation history and information on the cloud system, the method further includes periodically collecting information on the cloud system, wherein the information on the cloud system is related to each of the plurality of cloud systems. Visiting a plurality of first web pages displaying information, obtaining first information about the plurality of cloud systems from the plurality of visited first web pages, and a cloud system posted on each of the plurality of first web pages Based on the information on the components of , a second web page displaying information about the components may be visited, and second information regarding the components may be obtained from the visited second web page.

Also, the environment information of the legacy system may be obtained by analyzing image information of the legacy system.

Also, when the provided environment information of the legacy system is insufficient, additional information may be requested.

A cloud system recommendation apparatus according to an embodiment of the present invention includes a profile manager providing a plurality of cloud system recommendation histories, a data manager providing information on a plurality of cloud systems, and a user interface receiving information on a legacy system. , a transfer target request analysis unit that receives and analyzes requirements, a budget/estimate management unit that receives and provides a budget, and the plurality of cloud system recommendation histories and information on the plurality of cloud systems, the legacy system and the requirements It includes a case analysis unit that reviews and recommends a cloud system according to the budget.

In addition, the system may further include an environment analysis unit for analyzing the environment information of the legacy system.

The apparatus may further include a transfer possibility analysis unit for each element that compares the environment information with the requirements to determine whether the legacy system is transferable.

In addition, the transferability analysis unit for each element may recommend other compatible elements if transfer is not possible among the elements.

Also, the case analysis unit may recommend the cloud system with the budget as a maximum value.

In addition, when there is no budget, the budget/estimate management unit may recommend the cloud system at the lowest cost in consideration of an estimate recognized through information on the plurality of cloud systems and the requirements.

According to an embodiment of the present invention, it is possible to be more objective and not dependent on specific companies and services for cloud computing transfer procedures and methods, environment configurations, and estimates, which are mostly performed through expert consultation. In addition, by recognizing information about the cost, service, and method required for cloud migration by the user himself/herself, it can help to perform more appropriate services and methods at an objective cost than the actual migration. In particular, for example, when there are many complex and interlocking target systems such as each command and control system in the defense field, analyzing the legacy environment requires a lot of time and money. The more complex the system, the more effective and efficient the analysis will be through the present invention.

1 is a block diagram of an apparatus for recommending a cloud system according to an embodiment of the present invention.
FIG. 2 is a detailed configuration diagram of the user interface unit of FIG. 1 .
3 is a detailed configuration diagram of the first data collection unit.
4 is an exemplary diagram illustrating a process in which the data collection unit operates.
5 and 6 are structural examples of a user interface unit, and are exemplary views of obtaining information of a legacy system.
7 is an exemplary diagram expressing requirements according to an embodiment of the present invention.
8 is an exemplary diagram of a result analyzed by the case analysis unit according to an embodiment of the present invention.
9 is a flowchart of a cloud system recommendation method according to an embodiment of the present invention.
10 is a detailed flowchart of the cloud system recommendation process of FIG. 9 .

Advantages and features of the present invention and methods of achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only these embodiments allow the disclosure of the present invention to be complete, and common knowledge in the art to which the present invention pertains It is provided to fully inform those who have the scope of the invention, and the present invention is only defined by the scope of the claims.

In describing the embodiments of the present invention, if it is determined that a detailed description of a well-known function or configuration may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. In addition, the terms to be described later are terms defined in consideration of functions in an embodiment of the present invention, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification.

A cloud system recommendation apparatus 100 according to an embodiment of the present invention will be described with reference to FIGS. 1 to 8 .

1 is a configuration diagram of a cloud system recommendation apparatus 100 according to an embodiment of the present invention, FIG. 2 is a detailed configuration diagram of the user interface unit 110 of FIG. 1 , and FIG. 3 is the first data collection It is a detailed configuration diagram of the unit 190, FIG. 4 is an exemplary diagram illustrating a process in which the data collection unit 190 operates, and FIGS. 5 and 6 are configuration examples of the user interface unit 110, and the legacy system. It is an exemplary diagram of obtaining information, FIG. 7 is an exemplary diagram expressing requirements according to an embodiment of the present invention, and FIG. 8 is an example of the analysis result by the case analysis unit 170 according to an embodiment of the present invention It is also

As shown in FIG. 1 , the legacy environment analysis-based cloud system recommendation apparatus 100 according to an embodiment of the present invention includes a user interface unit 110 , an environment analysis unit 120 , a transfer target demand analysis unit 130 , Element-wise transferability analysis unit 140, budget/estimate management unit 150, data management unit 160, case analysis unit 170, profile management unit 180, data collection unit 190, transfer method management unit 200 may include.

1, 2, 5 and 6 , the user interface unit 110 may receive environment information for the legacy system. For example, information on communication of the legacy system, each server system included in the legacy system, an external linkage system of the legacy system, and hardware and software included in the legacy system may be provided. For example, the user interface 110 may receive information on software included in the legacy system as shown in FIG. 5 and information on hardware included in the legacy system as shown in FIG. 6 . In order to stably transfer the legacy system to the cloud system, it is necessary to check the legacy system, so the user interface 110 needs to specifically receive the environment information of the legacy system as shown in FIGS. 5 and 6 .

In this case, the user interface unit 110 is information about the hardware of the legacy system, for example, the manufacturer of the legacy system, the model name of the legacy system, the price of the legacy system, the specifications of the hardware constituting the legacy system, etc. Can be provided. . More specifically, the server system may receive information about the operating system, DB, Web Server, and Web Application Server.

The user interface unit 110 may also receive information on software included in the legacy system. For example, information such as types and versions of each of a plurality of software belonging to and utilized in the legacy system, and specifications required for the operation of the software may be input. Software can be broadly divided into commercial software and self-made software. A plurality of software can be divided into commercial software and self-produced software. For example, commercial software is a commercial software product such as MS Office, Hangul below, and Adobe Acrobat Reader, and self-produced software is a software product created directly to perform a specific function. may mean, but is not limited thereto. In the case of self-produced software, transfer by element by directly receiving input from the user on whether or not the transfer to the cloud system is possible, or by inputting information necessary to determine the transferability, such as implementation language and version of implementation language, and dependency with other software. It should be used when the possibility analysis unit judges the possibility of analysis during analysis. The transferable analysis unit for each element will be described later.

There are largely two methods for inputting environmental information into the user interface unit 110 , a method in which a user directly inputs environmental information and a method in which a legacy system is captured as an image, for example, a picture or video, and then analyzed and inputted. There is this. In the case of input by the user, the user may directly input the above-described environment information. In particular, in the case of self-made software, since it is difficult to grasp the related information, the user needs to input it. On the other hand, in the case of inputting an image, each component is identified from the input image or image, and the environment is analyzed by referring to the physical performance technology of hardware that has been collected through element identification that can specify the component such as the model name of each component. Analyze.

Referring to FIG. 2 , the user interface unit 110 may include an image acquisition unit 111 , a specification analysis unit 113 , and a guide unit 115 . The image acquisition unit 111 acquires an image of the legacy system. The video may be a photo, a video, etc., and includes the manufacturer, model name, price of the legacy system, the types and specifications of hardware constituting the legacy system, and the types and specifications of software used in the legacy system. The specification analysis unit 113 may analyze the image of the legacy system acquired by the image acquisition unit 111 to automatically recognize the specification of the legacy system. The specification analysis unit 113 may generate environment information as shown in FIGS. 5 and 6 . For example, if the image of the web server is acquired by the image acquisition unit 111, the specification analysis unit 113 through OCR has 4 gigabytes of RAM of the web server, the CPU is Intel core I5-66000K, and the HDD capacity is 1 TB. environment information can be created. In addition, the program used in the web server by capturing the screen of the software can create environment information such as Apache 2.0.64 version, Java 2.0 version, and Unix AIX 5L version. The generated environment information is stored in the data management unit 160 .

Meanwhile, the specification analysis unit 113 may be trained according to a machine learning algorithm to analyze the legacy system image. The information in the data management unit 160 may be used to learn by a machine learning algorithm. The machine learning algorithm used herein uses general algorithms that can be accessed and utilized by those skilled in the art, and a detailed description of the algorithm will be omitted here.

The guide unit 115 informs the user of requirements for the image of the legacy system. Users can be informed of the requirements of which part of the image to acquire to acquire hardware information and which screen to acquire to acquire software information. For example, you can tell the user how to take a single image so that all environmental information of the legacy system can be obtained. Alternatively, for example, when a plurality of images of the legacy system are required, it may indicate which image is required to generate environment information, how to input the image, and what information to include in the image. The user can easily know how to secure an image containing information of the legacy system through the guide unit 115 , and can input the image into the image acquisition unit 111 without difficulty. Also, if it is determined that the environment information of the legacy system is insufficient, the guide unit 115 may request additional information to additionally acquire the environment information.

The user may directly take an image of the legacy system and input it into the image acquisition unit 111, or may input an image already owned or provided by the manufacturer into the image acquisition unit 111. There are many ways to obtain it. The specification analysis unit 113 analyzes the image of the legacy system and generates environmental information of the legacy system.

The environment analysis unit 120 analyzes the environment information generated by the user interface unit 110 . The environment analysis unit 120 may receive information on a plurality of cloud systems from the case analysis unit 170 and find a cloud that is the same as or most similar to the legacy system among them by using the environment information. For example, the environment analysis unit 120 analyzes the environment, such as communication or network input from the user, each server system, and external interworking target system, and identifies the physical specifications of each environmental component and the relationship between the components. do. At this time, it is judged whether the physical specification of each component is above the minimum level that can be currently supported, and the most similar level is recommended. That is, it is possible to find the lowest specification that satisfies the environment information among the plurality of cloud systems. The cloud system selected by the environment analysis unit 120 from among the plurality of cloud systems is again provided to the case analysis unit 170 , and the case analysis unit 170 recommends the cloud system to the user.

The transfer target request analysis unit 130 acquires a requirement for a cloud system to be recommended. Specifically, it performs a function of analyzing the requirements for the computing environment to which the legacy system is to be moved and operated. The transfer target requirement analysis unit 130 recommends a minimum hardware component specification that can be reflected when a function is added or a component is changed by modifying some self-made software. In this case, if modification of self-made software or component change affects dependency with other self-made software or commercial software, it should be indicated additionally. As shown in FIG. 7 , the prior target request analysis unit 130 organizes and analyzes the requirements, and the requirements may be obtained automatically by analyzing the environment information of the legacy system or may be obtained by a user's direct input.

When there is a request desired by the user, the prior target request analysis unit 130 receives and analyzes information about the request. By comparing the requirements with the legacy system, implicit requirements are identified for those not explicitly required and added to the requirements after confirming whether they are added to the user. These implicit requirements can be entered by the administrator in case there are no initial cases. For example, when the number of requirements input by the user input to the previous target demand analysis unit 130 is greater than the number of environmental information derived by analyzing the legacy system in the environment analysis unit 120, the case analysis unit ( 170) (to be described in detail later) recommends a cloud system according to the number of requirements. Even if the number of environment information is small, related information is received from the profile manager 180 and the data manager 160 to match the number of requirements. The case analysis unit 170 may recommend a cloud system by receiving additional information about a part not in the requirements through the recommendation histories of a plurality of cloud systems stored in the profile management unit 180 .

On the other hand, when the number of requirements input by the user input to the previous target demand analysis unit 130 is less than the number of environmental information derived by analyzing the legacy system in the environment analysis unit 120, the user for the implicit requirements receive additional information from Since the cloud system recommendation apparatus 100 must stably transfer all of the legacy system to the cloud system, it must receive additional information.

The element-specific transferability analysis unit 140 performs a function of determining the transferability of each component by hardware and software to the cloud system based on the results of the environment analysis unit 120 and the transfer target demand analysis unit 130 . . In this case, in the case of hardware, the element-specific transferability analysis unit 140 considers the specifications closest to the requirements in consideration of the requirements of the legacy system and the cloud system. If there is no component described in the requirements, it is marked as non-transferable and another component with the most similar performance and compatible is recommended.

The element-specific transferability analysis unit 140 considers the functions and performance most similar to the target environment in consideration of the legacy system and requirements in the case of software as well as hardware. In addition, if there is no component described in the requirements, it is marked as non-transferable and other compatible components are recommended. In the case of self-made software, transferability is determined by considering dependencies and transferability entered by the user. For example, when JEUS 5.0 components cannot be transferred to the cloud system as shown in FIG. 8, other compatible components such as Tomcat 5.5 and 5.6 are recommended.

The budget/estimate management unit 150 receives a budget determined when transferring the cloud system. The budget input by the user is used to select available services or tools when transferring to the maximum value. If there is no budget input, the minimum amount that satisfies the environmental information of the legacy system is calculated and presented to the user. In this case, the minimum amount is calculated based on the collected costs possessed by the data management unit 160 , and details of the cost collection will be described later.

The data management unit 160 stores various types of information necessary for recommending the cloud system. The cloud system recommendation apparatus 100 receives and stores various types of information collected by each component, for example, the environment information of the legacy system acquired through the user interface unit 110 and the environment analysis unit 120 , the legacy system of the image, the requirements input from the transfer target demand analysis unit 130, the first and second information collected from the data collection unit 190, the information analyzed by the specification information case analysis unit 170, the budget / estimate The budget input to the management unit 150 and the transferability of each component may be stored for each hardware and software analyzed by the element-wise transferability analysis unit 140 , but is not limited thereto.

In addition, the data management unit 160 provides the stored data when each component of the cloud system recommendation apparatus 100 requests data.

The profile manager 180 stores the recommendation history of the cloud system and provides the stored recommendation history when the case analysis unit 170 requests it. Whenever the case analysis unit 170 recommends a cloud system to a user, a recommendation history of the cloud system is generated, and the profile manager 180 stores it each time it is generated.

The recommendation history of the cloud system may include budget information, information on a legacy system, a cloud system selected by a user, and the like. The recommendation history of the cloud system is classified and stored by type in the profile management unit 180. Specifically, the recommendation history of the cloud system includes basic information about the legacy system such as the system name of the cloud system, budget information, and each server name, and recommended Some information such as cloud services and deployment models, hardware configuration information for each server, software configuration information for each server, service configuration of a recommended cloud system, etc. may be classified by type and stored. However, more specific information of hardware configuration information for each server and software configuration information for each server and user requirements are stored in the data management unit 160 .

The recommendation history of the cloud system stored in the profile manager 180 may be loaded or modified by the user, and is utilized for case analysis when recommending a new cloud system. Since there is not much recommendation history in the initial stage of the cloud system recommendation device 100 , a recommendation history input from a user or generated in another device may be brought. Alternatively, the case analysis unit 170 may combine a plurality of recommendation histories to generate a new recommendation history and store it in the profile manager 180 . Through this, more diverse recommendation histories can be secured, and the case analysis unit 170 can recommend an appropriate cloud system to the user.

The data collection unit 190 collects information on a plurality of cloud systems. In order to recommend a cloud system to a user, it is necessary to secure information on a plurality of cloud systems, and the data collection unit 190 plays this role. The information collected by the data collection unit 190 is stored in the data management unit 160 .

How the data collection unit 190 collects data will be described with reference to FIGS. 3 and 4 . The data collection unit 190 may include a first visit unit 191 , a second visit unit 193 , and a setting unit 195 .

The first visiting unit 191 visits a plurality of first web pages 192 that post information on each of a plurality of cloud systems, and provides information about a plurality of cloud systems from the visited first web pages 192 . 1 Get information.

The second visiting unit 193 is a second web page 194 that posts information about the components of the cloud system based on the information about the components of the cloud system posted on each of the plurality of first web pages 192 . and acquires second information about the component from the visited second web page 194 .

For example, the first web page 192 may be a site providing a cloud system, and the second web page 194 may be a site selling components (hardware, software, etc.) constituting the cloud service.

The first information is information obtained by the first visiting unit 191 by accessing the plurality of first web pages 192, for example, the type of service provided by each of the plurality of cloud systems, the form of an estimate, and the information of the cloud system. It may include information such as a deployment model.

The second information is information obtained by the second visiting unit 193 by accessing the plurality of second web pages 194, price information of components constituting the cloud system, compatibility information of components, and product names of components , the image of the component, the serial number of the component, and version information of the component, etc. may be included. Specifically, the second information extracts and stores prices, license information, and specific performance, version, compatibility information, etc. of hardware such as RAM and CPU to software such as OS and database. These information are used when the case analysis unit 170 recommends a cloud system.

On the other hand, the second web page 194 may be a search site such as Google as well as a component sales site, for example, the data collection unit 190 through Google image search for various images of each component, product name, serial number , detailed performance, specifications, price, etc. are extracted and stored in the data management unit 160 , which can be utilized when the user interface unit 110 analyzes the image of the legacy system.

The setting unit 195 controls the first visit unit 191 and the second visit unit 193 to adjust the information that the data collection unit 190 should collect and the information it should not collect. Specifically, the setting unit 195 may determine the first web page 192 to be visited by the first visiting unit 191 by controlling information on the plurality of first web pages 192 . Also, the setting unit 195 may control information on the plurality of second web pages 194 to determine the second web page 194 to be visited by the second visiting unit 193 . In addition, the composition and type of the first information and the second information may be determined, and an activity period and an activity time of the first visiting unit 191 and the second visiting unit 193 may be controlled. The data collection unit 190 may periodically collect information on a plurality of cloud systems through the setting unit 195 .

The data collection unit 190 converts the specification information on each of the collected cloud systems posted on the plurality of web pages into text so that it can be conveniently managed and stores it in the data management unit 160 .

The transfer method management unit 200 filters which cloud system among the plurality of cloud systems is recommended by using the first information. For example, the transfer method management unit 200 performs a function of managing information about a service for each cloud service provider collected through the data collection unit 190 and a conversion tool provided by each company. Information on cloud service providers' services and conversion tools is periodically updated, and the available conditions are modified or managed, such as creation. In addition, when recommending applicable services and conversion tools through legacy system analysis, filtering is performed.

The case analysis unit 170 recommends the cloud system to the user. Specifically, the case analysis unit 170 analyzes the environment information of the legacy system generated by the user interface unit 110 , the requirements of the transfer target demand analysis unit 130 , and the transfer possibility analysis unit 140 for each element. The content of the possibility review and the budget of the budget/estimate management unit 150 are comprehensively considered, and the specification information of a plurality of cloud systems stored in the data management unit 160 is compared primarily. When one of the plurality of cloud systems is selected through the primary comparison, it is compared with the recommendation histories of the plurality of cloud systems stored in the profile manager 180 to finally recommend an appropriate cloud system to the user.

When the case analysis unit 170 compares the requirements of the previous target request analysis unit 130 and the recommendation history of the profile management unit 180, if there is information included in the recommendation history but not included in the acquired requirements Request the user to confirm and review additional requirements.

Since the recommendation history is classified and stored by type, when the case analysis unit 170 compares the requirement and the recommendation history, the recommendation history classified into the type matching the requirement may be compared with the requirement.

Meanwhile, the case analysis unit 170 recommends a cloud system according to a budget. If the budget is set, the cloud system is recommended within the budget with the maximum budget. Even if it meets the requirements, if the budget is small and exceeds the set budget, a recommendation can be made according to the legacy system. Referring to FIGS. 7 and 8 , the user wanted to use the Windows 10 version in the file server of the cloud system as a requirement of the user, but it was recommended to use the Windows 7 version in the file server because the budget did not fit.

If the budget is not determined, the case analysis unit 170 may satisfy the environmental information of the legacy system, refer to estimates for a plurality of cloud systems, and match the lowest cost in consideration of the requirements requested by the user.

The case analysis unit 170 recommends a cloud system according to the number of requirements when the number of requirements input to the previous target request analysis unit 130 is greater than the number of environment information. Even if the number of environment information is small, the number of requirements is matched by receiving the cloud system recommendation history of the profile management unit 180 and the first information and the second information from the data management unit 160 . That is, the case analysis unit 170 uses the recommendation histories of a plurality of cloud systems stored in the profile management unit 180 to provide the cloud system even if the user does not receive additional information on the part that is not in the requirements even if the user's desired requirements are insufficient. can recommend In other words, by identifying requirements not explicitly requested and reflecting them together with explicit requirements, user satisfaction with cloud system recommendations can be improved. Of course, the case analysis unit 170 may directly request a requirement that is not explicitly requested from the user to receive additional information and recommend a cloud system.

A cloud system recommendation method according to an embodiment of the present invention will be described with reference to FIGS. 1 to 10 . Contents overlapping with the above description will be simplified or omitted.

9 is a flowchart of a cloud system recommendation method according to an embodiment of the present invention, and FIG. 10 is a detailed flowchart of the cloud system recommendation process of FIG. 9 .

9 and 10 , first, information on the cloud system is collected ( S100 ). Information is collected by using the first visiting unit 191 and the second visiting unit 193 of the data collection unit 190 , and the collected information is stored in the data management unit 160 . Information collection may be performed periodically by the setting unit 195 .

Next, the cloud system recommendation history and information on the cloud system are called (S200). A recommendation history is provided from the profile manager 180 , and information about the cloud system collected by the data collector 190 is provided from the data manager 160 .

Next, environmental information of the legacy system, user requirements, and a budget set before the cloud system are provided (S300).

Next, the cloud system is recommended by utilizing the cloud system recommendation history, information about the cloud system, environment information of the legacy system, user requirements, budget, and the like ( S400 ). At this time, by analyzing the environmental information of the legacy system, it is reviewed whether the legacy system is transferable (S410), and if there are non-transferable elements among the elements of the legacy system, compatible elements are searched for and replaced (S420). Next, the user's requirements are reviewed (S430). After the review of the requirements is completed, a cloud system suitable for the user is selected by comparing it with the recommendation histories of a plurality of cloud systems ( S440 ). Next, the input budget is compared with the selected cloud system (S450). If there is an input budget, the budget is compared with the selected cloud system, and the configuration and specifications of the cloud system are adjusted and recommended (S460). For example, if the estimate of the selected cloud system is lower than the budget, it is not a problem, but if it exceeds the budget, the selected cloud system is adjusted by changing the configuration, specifications, etc. within the budget.

If there is no input budget, the selected cloud system estimate is recommended to be the lowest cost (S470). However, the recommended cloud system must satisfy the environmental information of the legacy system, and the estimate is adjusted within the information about the cloud system.

The cloud system recommended to the user is stored as a recommendation history of the cloud system ( S500 ). The recommended cloud system is classified by type and stored in the profile manager 180, and the point used when recommending a cloud system in the future is as described above.

Meanwhile, the cloud system recommendation apparatus 100 and the recommendation method may be implemented in the form of a computer-readable recording medium storing a computer program programmed to perform each configuration and each step.

The above description is merely illustrative of the technical idea of the present invention, and various modifications and variations will be possible without departing from the essential quality of the present invention by those skilled in the art to which the present invention pertains. Therefore, the embodiments disclosed in the present invention are not intended to limit the technical spirit of the present invention, but to explain, and the scope of the technical spirit of the present invention is not limited by these embodiments. The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present invention.

100: cloud system recommendation device 110: user interface unit
111: image acquisition unit 113: specification analysis unit
115: guide unit 120: environmental analysis unit
130: transfer target demand analysis unit 140: element transfer possibility analysis unit
150: budget/estimate management unit 160: data management unit
170: case analysis unit 180: profile management unit
190: data collection unit 191: first visit unit
193: second visit unit 195: setting unit
200: old method management department

Claims (12)

delete delete delete delete delete delete a profile manager providing a plurality of cloud system recommendation histories;
a data management unit that provides information on a plurality of cloud systems;
a user interface unit for receiving information about a legacy system that stores and processes information;
a transfer target request analysis unit that receives and analyzes requirements for a cloud system to be recommended;
Budget/estimate management unit that receives and provides budget; and
including a case analysis unit;
The user interface unit,
a guide unit that provides information on a part to be photographed among the exteriors of hardware constituting the legacy system and information on a part to be photographed when software installed in the legacy system is running;
an image acquisition unit that acquires an image related to hardware constituting the legacy system and an image related to the software captured according to the information provided by the guide unit; and
and a specification analysis unit that analyzes the acquired image of the legacy system to generate environmental information,
The case analysis unit,
A cloud system is recommended based on a result of comparing the environment information, the information on the plurality of cloud systems, the requirements, and the budget, and a portion of the environment information that is not in the requirements is the recommendation history of the plurality of cloud systems. received as additional information from
Cloud system recommendation device. 8. The method of claim 7,
The cloud system recommendation apparatus further comprising an environment analyzer to analyze the environment information of the legacy system. 9. The method of claim 8,
The cloud system recommendation apparatus further comprising a transferability analysis unit for each element that compares the environment information with the requirements to determine whether the legacy system is transferable. 10. The method of claim 9,
The transfer possibility analysis unit for each element,
A cloud system recommendation device for recommending other compatible components if transfer is not possible among the components of the legacy system. 8. The method of claim 7,
The cloud system recommendation device for the case analysis unit to recommend the cloud system with the budget as a maximum. 12. The method of claim 11,
The budget / estimate management unit,
A cloud system recommendation device for recommending the cloud system at the lowest cost in consideration of the requirements and the estimates recognized through information on the plurality of cloud systems when there is no budget.

Images