KR102109461B1 - Project Automation Assistance System with Micro Service Architecture - Google Patents

Abstract

The present invention relates to a micro service architecture (MSA) based project automation support system. More particularly, the MSA based project automation support system is easily applicable to a new project by modularizing a function or a service having high reusability to manage a software development project of a system integration (SI) company as a micro service. Resources being existing product can be searched and downloaded in each procedure by automating the whole procedures of start, generation, performing, product write, and modularity of the software development project. The project can be efficiently performed and a project performing increased usability of a code once can be used as a substance of another project by integrally managing Maven, Gradle, Docker Hub, and simple repository.

Description

     Project Automation Assistance System with Micro Service Architecture

The present invention modularizes a highly reusable function or service into a micro service to manage a software development project of an SI company, so that it can be easily applied to a new project, and starts, generates, performs, and outputs a software development project. By automating the entire process of creation and modularization, it is possible to easily search for and download and use the existing output resources in each process, and by integrating and managing not only the existing Maven, Gradle, and Docker Hub simple repositories , This is a technology related to a microservice architecture (MSA) -based project automation support system that makes project execution more efficient and code reusability so that a project once performed can be used as an asset for other projects.

There is a system that identifies all the components required for the currently developed Monolithic Architecture and develops them in one project at a time, but when elements required for one service are closely combined with each other, there is a need to modify each part It is difficult to accurately grasp the impact between elements, and in order to reflect the modifications, all the related functions must be tested, and there is a problem in that build and test time are prolonged.

In addition, when adding new functions, it is difficult to introduce new methods or technologies because it is dependent on the existing development environment, and the entire service may be stopped due to problems caused by one function, and the time required to reflect requirements and test deployment There is a prolonged problem.

Therefore, in order to manage software development projects of SI companies, highly reusable functions or services can be modularized into microservices to support easy application to new projects, and to start, create, perform, produce and modularize software development projects. By automating the entire process, you can easily search for and download and use the existing output resources in each process. In addition to the simple Maven, Gradle, and Docker Hub simple repositories, you can manage the project by integrating them. There is an urgent need for the development of a microservices architecture (MSA) -based project automation support system that enables efficient, code-reusable projects to be used as assets of other projects.

KR 10-2007-0057806 (2007.6.7)

Therefore, the present invention was conceived to solve the above problems, and it is possible to support easy application to a new project by modularizing a reusable function or service as a micro service for managing a software development project of an SI company. The objective is to provide a project automation support system based on a microservices architecture (MSA).

Another object of the present invention is to automate the entire process of starting, creating, performing, creating and modularizing a software development project, and thus microservice architecture that can easily support searching and downloading of resources, which are existing products, in each process. (MSA) -based project automation support system.

Another object of the present invention is to use existing Maven, Gradle, and Docker Hub simple repositories as well as to manage them in an integrated manner, making project execution more efficient and reusability of code to make a project once performed as an asset of another project. It is to provide a project automation support system based on a micro service architecture (MSA) that can be used.

A project automation support system based on a micro service architecture (MSA) according to an exemplary embodiment of the present invention for achieving the above object includes a resource repository for storing resources, a configuration management repository for storing and managing configurations, and the resource repository A resource management unit including an index and a search unit for searching information stored in the configuration management repository, and having a function of managing a version-specific configuration of a source code that is a product of a project execution process; It includes a build management unit that builds and manages code, and a deployment management unit that distributes and manages the built modules, builds the code in module units or execution units, and registers the built modules in a resource store or distributes them to a server for service. A build and distribution management unit having a function to perform; It includes a module index and a search unit that allows you to search for information stored in a resource, and has a function to store reusable modules in a common resource storage and manage them in a common resource storage during project execution, and to have a library function for easy import and use in any project. A module management unit; It includes an image repository for storing images, an image index configured to search for information in the image repository, and a search image organizer. Separately serviceable modules are separately separated to create docker images, and the generated images are projected. An image manager having a function of providing a corresponding specification together with an image when an image is requested by an automated support system; Defines the ability to integrate, manage the ability to search for modules matching the required functional specifications in the project, find the resource of the searched module and include it in the newly created project, and define the way to link the module. A project creation process including a function for automatically generating an appropriate setting therefor; It is subdivided into design, coding, build, test, and distribution processes. The design requires a lot of documents and work in requirements specification, requirements tracking, domain definition, sequence diagram, and class definition, and various design documents are developed during development. Version and change history management is necessary because frequently changes are made with code changes, and the coding should be able to manage the status and history of the implementation of specific functions of the task at any time by managing the shape of each version of the source code. It should be able to recover to the previous state, and should be able to collaborate, the build compiles the code in an executable form, packages the compiled code in a certain unit, and the test works as the code is designed. It has the function to test whether it is Twa, it includes integration tests to test if it meets the service purpose and function. The distribution should distribute the built package to one or more systems so that the service works normally, and monitor whether the system is normal after deployment. The project implementation process, including what should be possible; An output creation process including a function of presenting the document created at the design stage to match the actual result, and a function of generating a manual for the generated code; The developed code is disassembled and reassembled into module units according to reusability and singular performance, and the modules are separated into modules of library nature and modules that can be micro serviced. The modules of library nature support frameworks such as MAVEN or Gradle. And to manage it so that it can be easily referenced and used by other projects, and the Micro Service-capable module is made in the form of a docker image and can be used in other projects through its own or common docker hub; Rather than a special function, the project creation, project execution, product creation, and modularization processes are performed to make the reusability high, and to support this, the user interface is continuously used to increase accessibility and easily utilize it through the index and search functions. Characterized in that it includes the integrated management of the resource assetization process, including improvement.

As described above, the present invention micro-service architecture (MSA) -based project automation support system has the following effects.

First, the present invention can support easy application to a new project by modularizing a micro service as a reusable function or service for managing a software development project of an SI company.

Second, the present invention can assist in making it easy to search, download, and utilize existing output resources in each process by automating the entire process of starting, generating, performing, outputting, and modularizing the software development project.

Third, according to the present invention, the existing Maven, Gradle, Docker Hub, as well as simple repositories are managed by integrating them to make project execution more efficient and reusability of code to make the project once executed as an asset for other projects. Make it possible.

1 is a view showing the configuration of a microservice architecture (MSA) based project automation support system according to an embodiment of the present invention.
2 is a view showing in detail a resource management unit in the configuration of a microservice architecture (MSA) based project automation support system according to an embodiment of the present invention.
3 is a view showing in detail a build and deployment management unit during the construction of a microservice architecture (MSA) based project automation support system according to an embodiment of the present invention.
4 is a detailed diagram of a module management unit in the configuration of a microservice architecture (MSA) -based project automation support system according to an embodiment of the present invention.
5 is a view showing in detail the image management unit during the configuration of the micro-service architecture (MSA) project automation support system according to an embodiment of the present invention.
6 is a view for explaining a flow of a project process using a microservice architecture (MSA) based project automation support system according to an embodiment of the present invention.

 Hereinafter, a preferred embodiment of the present invention will be described with reference to the accompanying drawings. In the description of the present invention, if it is determined that a detailed description of known technologies or configurations related to the present invention may unnecessarily obscure the subject matter of the present invention, detailed The description will be omitted, and the terms to be described below are terms defined in consideration of functions in the present invention, and may vary according to a user's or operator's intention or convention, so the definition is a microservice architecture (MSA) based project according to the present invention. It should be based on the contents throughout this specification describing the automation support system.

Hereinafter, a microservice architecture (MSA) -based project automation support system according to an exemplary embodiment of the present invention will be described in detail with reference to the accompanying drawings.

1 is a view showing the configuration of a microservices architecture (MSA) based project automation support system according to an embodiment of the present invention, and FIG. 2 is a microservices architecture (MSA) based project according to an embodiment of the present invention. It is a diagram showing the resource management unit in detail during the configuration of the automation support system, and FIG. 3 is a view showing in detail the build and deployment management unit during the configuration of the microservice architecture (MSA) -based project automation support system according to an embodiment of the present invention 4 is a diagram showing in detail the module management unit during the configuration of the microservice architecture (MSA) -based project automation support system according to an embodiment of the present invention, and FIG. 5 is a microservice according to an embodiment of the present invention The image management department in detail during the construction of the architecture (MSA) -based project automation support system And tanaen drawings, Figure 6 is a view showing for explaining the flow of a process using a micro project Services Architecture (MSA) based project automated support system according to an embodiment of the present invention.

MSA (Micro-Service Architecture) refers to the architectural pattern that composes a large application by combining services that can be independently deployed / expanded, and has the following characteristics.

(1) Decompose the application logic into small components with clear responsibilities, and combine them to provide a solution. (2) Each component covers a small area of responsibility and is distributed completely independently of each other. (3) Microservices are responsible for only one part of the business domain and must be reusable across multiple applications. (4) Microservices are based on several basic principles and use lightweight communication protocols such as HTTP and JSON to exchange data between service consumers and service providers. (5) Since the application always communicates using a technology-neutral protocol, it is independent of the service implementation technology. This means that microservices-based applications can be built in a variety of languages and technologies. (6) By using small, independent and distributed microservices, organizations can have small teams with clearly defined areas of responsibility. These teams work towards a single goal, like launching an application, but are only responsible for the services they develop.

The above-mentioned MSA (Micro-Service Architecture) is divided into small services, and each service is independently made, suitable for a large-scale distributed environment, reduced in complexity, flexible deployment is possible, and scalability is increased through reusability, It is free to introduce and expand hw / sw platform / technology for each service. In addition, it is easy for the developer to understand and has high productivity at each stage of development / operation, continuous development / deployment can be performed under the responsibility of a small number of persons involved in biz capability units, and has the advantage of good fault isolation characteristics.

However, failure tracking, monitoring, and messaging are difficult, features that span multiple services are difficult to handle transactions, and features that span multiple services are complicated to test, and releases are difficult when there are dependencies between services. . In addition, since the number of services is large and flexible, there may be problems in continuous integration / delivery and service management, and when a system started with a monolith is converted to microservices, there is a disadvantage in that it can be accompanied by great pain.

Therefore, the project automation support system based on the microservice architecture (MSA), which is the main office, will emerge.

The inventor microservice architecture (MSA) based project automation support system includes a resource management unit 100, a build and deployment management unit 200, a module management unit 300, an image management unit 400, an index and search unit 110, and resources Storage 120, configuration management storage 130, build management unit 210, distribution management unit 220, module index, search unit 310, image index, search and image configuration unit 410, image storage 420 , Project automation support system 500, and the like.

1 to 6, the present invention is a microservice architecture (MSA) -based project automation support system, the microservice architecture (MSA) -based project automation support system 500 is a resource management unit 100, build and It is provided with integrated management of the distribution management unit 200, the module management unit 300, and the image management unit 400, and includes project management, project execution, product creation, modularization, and resource asset management. The support system includes a resource storage 120 for storing resources, a configuration management storage 130 for storing and managing configurations, and an index and search unit 110 for searching for information stored in the resource storage and configuration management storage. And a resource management unit 100 having a function of managing a shape for each version of a source code that is a product of a project execution process; It includes a build management unit 210 for building and managing code, and a distribution management unit 220 for managing deployment of the built modules, and builds the code in module units or execution units, and stores the built modules in resource storage 120 A build and distribution management unit 200 having a function of distributing to a server for registration or service; It includes a module index and a search unit 310 that allows you to search for information stored in resources, and keeps reusable modules in a common resource storage 120 in the course of project execution, and can be easily used in any project Module management unit 300 having a function to library to enable; It includes an image storage 420 for storing images, an image index configured to search for information in the image storage 420, and a search image configuration unit 410, and separates independent serviceable modules separately to docker images. An image management unit 400 having a function of generating the generated image and providing a corresponding specification together with an image when an image is requested from the project automation support system; It is provided.

When describing the functions of each technical means constituting the project automation support system based on the present invention, the micro-service architecture (MSA) is as follows.

The present invention microservice architecture (MSA) based project automation support system 500 integrates and manages the resource management unit 100, the build and distribution management unit 200, the module management unit 300, and the image management unit 400, and generates a project. In addition, the project management, product creation, modularization, and resource assetization processes are integrated and managed.

The resource management unit 100 includes a resource storage 120 for storing resources, a configuration management storage 130 for storing and managing shapes, and an index and search unit for searching for information stored in the resource storage and configuration management storage. (110), and has the function of managing the shape of each version of the source code, which is the output of the project execution process.

Here, the resource management unit 100 includes a function of integrating with source code configuration management such as Git and SVN, and a function of integrating with library integrated management such as Maven and Gradle.

The build and distribution management unit 200 includes a build management unit 210 that manages to build and manage code, and a distribution management unit 220 that manages deployment of the built modules, and builds the code in module units or execution units. It has a function to register the built module in the resource storage 120 or distribute it to a server for service.

The module management unit 300 includes a module index and a search unit 310 to search information stored in resources, and stores and manages reusable modules in a common resource storage 120 in the course of project execution. In other words, it has the ability to library for easy import and use in any project.

The image management unit 400 includes an image storage 420 for storing images, an image index configured to search for information in the image storage 420, and a search image configuration unit 410, and independent service is possible. The docker image is generated by separately separating the modules, and the generated image is provided with a corresponding specification along with the image when the image is requested by the project automation support system.

The process of integrated management in the project automation support system 500 is described as follows.

The project creation process defines the ability to search for modules that match the required functional specifications in the project, the ability to find the resources of the searched modules and include them in the newly created project, and how to link the modules. Includes the ability to automatically create appropriate settings for it.

Next, the project execution process is subdivided into design, coding, build, test, and distribution processes.

The above design requires a lot of documents and work in requirements specification, requirements tracking, domain definition, sequence diagram, and class definition, and various design documents such as the above are frequently changed with code changes in the development process. And change history management.

In addition, the coding should be able to manage the state and history of implementing a specific function of a task at any time by managing the shape of each version of the source code, and to be able to recover an erroneous task to a previous state, and to be able to collaborate.

The build compiles the code in an executable form, and packages the compiled code in a certain unit.

In addition, the test has a function to test whether the corresponding code works according to design, and includes unit tests to test in units of classes and methods, and integration tests to test if it meets service purposes and functions.

The above distribution is to distribute the built package to one or more systems so that the service operates normally, and to monitor whether the system is normal after distribution.

Next, the product creation process includes a function of currentizing the document created in the design stage to match the actual result, and a function of generating a manual for the generated code.

In addition, the modularization process decomposes and reassembles the developed code into module units according to reusability and singular performance, and separates the modules into modules with library characteristics and modules with micro service.

The library-like module supports a framework such as MAVEN or Gradle, and is managed to be easily referenced and used in other projects.

In addition, the Micro Service type module is made in the form of a docker image so that it can be used in other projects through its own or common docker hub.

Next, the resource assetization process is not a special function, but a project creation, project execution, product creation, and modularization processes are performed so that reusability is increased, and accessibility is increased through an index and search function to support this. This includes continually improving the user interface for ease of use.

Therefore, the present invention microservice architecture (MSA) -based project automation support system automates the entire process of starting, creating, executing, producing and modularizing the software development project of the SI company, thereby easily reusing existing output resources in each process. It can be searched and downloaded and utilized, and existing projects such as Maven, Gradle, and Docker Hub as well as simple repositories are integrated to manage them to make projects more efficient and to improve the reusability of code, so projects that have been performed once are different projects. It can be used as an asset.

As described above, a person having ordinary knowledge in the technical field to which the present invention pertains is capable of various substitutions, modifications, and changes without departing from the technical spirit of the present invention, and thus is limited to the above-described embodiments and the accompanying drawings. It does not work.

As described above, the present invention micro-service architecture (MSA) -based project automation support system can be widely applied to the field of integrated management of software development projects of SI companies.

100: resource management unit 200: build and deployment management unit
300: module management unit 400: image management unit
500: Project automation support system 110: Index and search department
120: resource storage 130: configuration management storage
210: build management unit 220: distribution management unit
310: module index, search unit
410: image index, search and image organizer
420: image storage

Claims (8)

In the project automation support system based on micro service architecture (MSA),
It includes a resource repository for storing resources, a configuration management repository for storing and managing configurations, and an index and search unit for retrieving information stored in the resource repository and configuration management repository, a version of source code that is a product of the project execution process. A resource management unit having a function of managing a star shape; It includes a build management unit that builds and manages code, and a deployment management unit that distributes and manages the built modules, builds the code in module units or execution units, and registers the built modules in a resource store or distributes them to a server for service. A build and distribution management unit having a function to perform; It includes a module index and a search unit that allows you to search for information stored in a resource, and maintains a reusable module in a common resource storage and manages it in a common resource storage during project execution, and has the function to library for easy import and use in any project. A module management unit; It includes an image repository for storing images, an image index configured to search for information in the image repository, and a search image organizer. Separately serviceable modules are separately separated to create docker images, and the generated images are projected. An image manager having a function of providing a corresponding specification together with an image when an image is requested by an automated support system; Defines the ability to integrate, manage the ability to search for modules matching the required functional specifications in the project, the ability to find the resources of the searched modules and include them in the newly created project, and how to interlock the modules. A project creation process including a function for automatically generating an appropriate setting therefor; It is subdivided into design, coding, build, test, and distribution processes. The design requires a lot of documents and work in requirements specification, requirements tracking, domain definition, sequence diagram, and class definition, and various design documents are developed during development. Version and change history management is necessary because frequently changes are made with code changes, and the coding should be able to manage the status and history of the implementation of specific functions of the task at any time by managing the shape of each version of the source code. It should be able to recover to the previous state, and should be able to collaborate, the build compiles the code in an executable form, packages the compiled code in a certain unit, and the test works as the code is designed. Has the function to test whether it is Twa, it includes integration tests to test if it meets the service purpose and function. The distribution should distribute the built package to one or more systems so that the service works normally, and monitor whether the system is normal after deployment. The project implementation process, including what should be possible; An output creation process including a function of presenting the document created at the design stage to match the actual result, and a function of generating a manual for the generated code; The developed code is disassembled and reassembled into module units according to reusability and singular performance, and the modules are separated into modules of library nature and modules that can be micro serviced. The modules of library nature support frameworks such as MAVEN or Gradle. And to manage it so that it can be easily referenced and used by other projects, and the Micro Service-capable module is made in the form of a docker image and can be used in other projects through its own or common docker hub; Rather than a special function, the project creation, project execution, product creation, and modularization processes are performed to make the reusability high, and to support this, the user interface is continuously used to increase accessibility and easily utilize it through the index and search functions. Resource assetization process, including improvement to; Project automation support system based on micro service architecture (MSA), characterized by including integrated management. delete According to claim 1,
The resource management unit supports the automation of the project based on the microservice architecture (MSA), which includes the function of integrating with the source code configuration management such as Git and SVN, and the function of integrating with the library integrated management such as Maven and Gradle. system. delete delete delete delete delete

Images