CN113204369A - Intelligent monitoring tool for GitLab code warehouse activity - Google Patents
Intelligent monitoring tool for GitLab code warehouse activity Download PDFInfo
- Publication number
- CN113204369A CN113204369A CN202110469479.3A CN202110469479A CN113204369A CN 113204369 A CN113204369 A CN 113204369A CN 202110469479 A CN202110469479 A CN 202110469479A CN 113204369 A CN113204369 A CN 113204369A
- Authority
- CN
- China
- Prior art keywords
- module
- information
- code
- gitlab
- submitted
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 55
- 230000000694 effects Effects 0.000 title claims abstract description 39
- 238000012795 verification Methods 0.000 claims abstract description 15
- 230000005012 migration Effects 0.000 claims description 4
- 238000013508 migration Methods 0.000 claims description 4
- 238000011161 development Methods 0.000 abstract description 5
- 238000000034 method Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000001788 irregular Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Mathematical Physics (AREA)
- Computer Security & Cryptography (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses an intelligent monitoring tool for GitLab code warehouse activities, and relates to the technical field of java. The GitLab code warehouse activity intelligent monitoring tool verifies whether a folder has an illegal folder and files inside the illegal folder through the folder verification module, the file naming verification module verifies whether file naming accords with a hump naming rule, the submission instruction verification module verifies whether submitted information is carried out according to a submitted template, and code information is transmitted to the filter submission module, so that the folder verification module, the file naming verification module and the submission instruction verification module can verify the submitted file information, the standardization of development files is improved, the filter submission module filters the submitted files which are not required to be pushed, the intelligence of the monitoring tool is enhanced, the same code information is combined through the combination early warning notification module, early warning reminding is carried out, and the operation burden of the monitoring tool is reduced.
Description
Technical Field
The invention relates to the technical field of java, in particular to an intelligent monitoring tool for GitLab code warehouse activities.
Background
Java is an object-oriented programming language, not only absorbs various advantages of C + + language, but also abandons concepts such as much inheritance and pointers which are difficult to understand in C + +, so the Java language has two characteristics of strong function, simplicity and easy use. The Java language, which is representative of the static object-oriented programming language, excellently implements object-oriented theory, allowing programmers to perform complicated programming in an elegant thinking manner, often believing that updating codes results in code conflicts and false submissions, and irregular file submissions during cooperative work. To standardize and address code audits, unsupervised merges are performed.
At present, in the monitoring process of a GitLab code warehouse, file information of developers is mainly monitored, but now used nodesjs realizes a basic pushing function of git information, so that early warning notifications that whether files submitted by people who do not want to push the files and people who use gits meet development specifications and can not merge codes can not be filtered, and therefore technical personnel in the field provide an intelligent monitoring tool for GitLab code warehouse activity.
Disclosure of Invention
Technical problem to be solved
Aiming at the defects of the prior art, the invention provides an intelligent GitLab code warehouse activity monitoring tool, which solves the problems that personnel who do not want to push the files cannot be filtered, whether the files submitted by the personnel using git conform to the development specifications or not and code merging and early warning notification cannot be performed.
(II) technical scheme
In order to achieve the purpose, the invention is realized by the following technical scheme: a GitLab code warehouse activity intelligent monitoring tool comprises a code submitting module, wherein the output end of the code submitting module is connected with the input end of a GitLab monitoring service module, the output end of the GitLab monitoring service module is connected with the input end of a warehouse activity monitoring unit, the output end of the warehouse activity monitoring unit is connected with the input end of an information sending module, and the output end of the information sending module is connected with the input end of an enterprise WeChat robot module.
The warehouse activity monitoring unit comprises a standard file checking module, a filter personnel submitting module, a merging early warning notification module, a submitting description checking module, an event classification module and a distinguishing submitting item main body module, wherein the output end of the event classification module is connected with the input end of the merging early warning notification module, the output end of the merging early warning notification module is connected with the input end of the standard file checking module, the output end of the standard file checking module is connected with the input end of the submitting description checking module, the output end of the submitting description checking module is connected with the input end of the filter personnel submitting module, and the output end of the filter personnel submitting module is connected with the input end of the distinguishing submitting item main body module.
Preferably, the event classification module includes a push event, a merge event, a warehouse update event, an add user event, a kick user out of a team event, a project update event, a create project event, a project delete event, a delete user event, a create user event, a project migration event, a tag push event, and a destroy ssh key event.
Preferably, the filter submitting module reads local code information submitted by a developer, filters a submitted file which is not required to be pushed, and transmits the code information to the main body module for distinguishing and submitting projects.
Preferably, the merging early warning notification module merges submitted same code information, gives an early warning prompt, and transmits the code information to the specification file verification module.
Preferably, the canonical file checking module comprises a folder checking module and a file naming checking module,
preferably, the folder checking module checks whether the folder has an illegal folder and files inside the illegal folder,
preferably, the file naming checking module checks whether the file naming conforms to a hump naming rule.
Preferably, the submission instruction checking module checks whether the submitted information is performed according to the submitted template, and transmits the code information to the filter submission module.
Preferably, the subject module for distinguishing submitted items screens and retains subject item information in the submitted information.
Preferably, the information sending module binds the name of the project with the robot, determines to send the message according to the submitted warehouse information, and transmits the code information to the enterprise WeChat robot module.
(III) advantageous effects
The invention provides an intelligent monitoring tool for GitLab code warehouse activity. The method has the following beneficial effects:
(1) the GitLab code warehouse activity intelligent monitoring tool comprises a file folder checking module and a file naming checking module through a standard file checking module, wherein the file folder checking module checks whether a file folder has an illegal file folder and files inside the illegal file folder, the file naming checking module checks whether file naming accords with a hump naming rule, the submission instruction checking module checks whether submitted information is carried out according to a submitted template, and code information is transmitted to the filter submission module, so that the file folder checking module, the file naming checking module and the submission instruction checking module can check the submitted file information, and the standardization of file development is improved.
(2) According to the GitLab code warehouse activity intelligent monitoring tool, the filter submitting module is used for reading local code information submitted by developers and transmitting the code information to the distinguishing submitting project main body module, so that the filter submitting module can filter submission files which do not need to be pushed, and the intelligence of the monitoring tool is enhanced.
(3) The GitLab code warehouse activity intelligent monitoring tool merges submitted same code information through the merging early warning notification module, and performs early warning and reminding, and then transmits the code information to the standard file verification module, so that the merging early warning notification module merges the same code information, performs early warning and reminding, and reduces the operation burden of the monitoring tool.
Drawings
FIG. 1 is a schematic block diagram of the system of the present invention;
FIG. 2 is a system schematic block diagram of a warehouse activity monitoring unit of the present invention;
FIG. 3 is a system schematic block diagram of a sample file verification module of the present invention;
FIG. 4 is a system schematic block diagram of the event classification module of the present invention.
In the figure, 1, a code submitting module; 2. a gitlab monitoring service module; 3. a warehouse activity monitoring unit; 4. an information sending module; 5. an enterprise WeChat robot module; 6. a model file checking module; 7. a filter submission module; 8. a merging early warning notification module; 9. a submission instruction checking module; 10. an event classification module; 11. distinguishing a submitted item main body module; 12. a folder checking module; 13. and a file naming checking module.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1-4, the embodiment of the present invention provides two technical solutions:
the first embodiment,
A GitLab code warehouse activity intelligent monitoring tool includes a code submission module 1.
As a preferred scheme, the output end of the code submitting module 1 is connected with the input end of a gitlab monitoring service module 2, the output end of the gitlab monitoring service module 2 is connected with the input end of a warehouse activity monitoring unit 3, the output end of the warehouse activity monitoring unit 3 is connected with the input end of an information sending module 4, the output end of the information sending module 4 is connected with the input end of an enterprise WeChat robot module 5, the warehouse activity monitoring unit 3 comprises a standard file checking module 6, a filter submitting module 7, a merging early warning notification module 8, a submitting description checking module 9, an event classification module 10 and a distinguishing submitting item main body module 11, the output end of the event classification module 10 is connected with the input end of the merging early warning notification module 8, the output end of the merging early warning notification module 8 is connected with the input end of the standard file checking module 6, the output end of the standard file checking module 6 is connected with the input end of the submitting description checking module 9, the output end of the submission instruction checking module 9 is connected with the input end of the filter submission module 7, and the output end of the filter submission module 7 is connected with the input end of the subject module 11 for distinguishing submission items.
Example II,
As a modification of the previous embodiment,
a GitLab code warehouse activity intelligent monitoring tool includes a code submission module 1.
As a preferred scheme, the output end of the code submitting module 1 is connected with the input end of a gitlab monitoring service module 2, the output end of the gitlab monitoring service module 2 is connected with the input end of a warehouse activity monitoring unit 3, the output end of the warehouse activity monitoring unit 3 is connected with the input end of an information sending module 4, the output end of the information sending module 4 is connected with the input end of an enterprise WeChat robot module 5, the warehouse activity monitoring unit 3 comprises a standard file checking module 6, a filter submitting module 7, a merging early warning notification module 8, a submitting description checking module 9, an event classification module 10 and a distinguishing submitting item main body module 11, the output end of the event classification module 10 is connected with the input end of the merging early warning notification module 8, the output end of the merging early warning notification module 8 is connected with the input end of the standard file checking module 6, the output end of the standard file checking module 6 is connected with the input end of the submitting description checking module 9, the output end of the submission instruction checking module 9 is connected with the input end of the filter submission module 7, the output end of the filter submission module 7 is connected with the input end of the subject module 11 for distinguishing submission items,
preferably, the event classification module 10 includes a push event, a merge event, a warehouse update event, an add user event, a kick user out of a team event, a project update event, a create project event, a project delete event, a delete user event, a create user event, a project migration event, a tag push event, and a destroy ssh key event.
Preferably, the filter submitting module 7 reads the local code information submitted by the developer, and transmits the code information to the differentiated submission item main module 11,
preferably, the merging early warning notification module 8 merges the submitted same code information, gives an early warning prompt, transmits the code information to the specification file verification module 6,
preferably, the canonical file checking module 6 includes a folder checking module 12 and a file name checking module 13,
preferably, the folder checking module 12 checks whether the folder has an illegal folder and files inside the illegal folder,
preferably, the file name checking module 13 checks whether the file name conforms to the hump name rule,
preferably, the submission instruction verifying module 9 verifies whether the submitted information is performed according to the submitted template, and transmits the code information to the filter submitting module 7,
preferably, the main body module 11 for distinguishing submitted items screens and reserves the main item information in the submitted information,
as a preferable scheme, the information sending module 4 binds the name of the project with the robot, decides to send the message according to the submitted warehouse information, and transmits the code information to the enterprise WeChat robot module 5.
The advantages of the second embodiment over the first embodiment are: the file information submitted is verified through the folder verification module 12, the file naming verification module 13 and the submission instruction verification module 9, the standardization of development files is improved, the filter submitting module 7 enables the filter submitting module to filter submitted files which do not need to be pushed, the intelligence of the monitoring tool is enhanced, the merging early warning notification module 8 enables the merging early warning notification system to merge same code information, early warning is given, and the operation burden of the monitoring tool is reduced.
When the system works, a developer submits local code information through the code submitting module 1, the gitlab monitoring service module 2 monitors the code information submitted by the developer, the event classification module 10 classifies the code information submitted by the developer, classifies events in push events, merge events, warehouse update events, add user events, kick users out team events, project update events, create project events, project delete events, delete user events, create user events, project migration events, tag push events and destroy ssh key events, the merge early warning notification module 8 merges the classified events with the submitted same code information through the merge early warning notification module 8, and early warning reminds the developer to submit repeatedly, the merged information passes through the folder checking module 12 and the file naming checking module 13, the folder checking module 12 checks whether the folder has an illegal folder and files inside the illegal folder, the file naming checking module 13 checks whether the file naming conforms to a hump naming rule, the submitted information is checked through the submission instruction checking module 9 according to whether the submitted information is a submitted template, after the checking is successful, the submitted information is transmitted into the division and submission item main body module 11, the division and submission item main body module 11 screens and retains the main item information in the submitted information, then the main item is sent to the enterprise WeChat robot module 5 through the information sending module 4, and the robot determines which enterprise WeChat group the message is sent according to the submitted warehouse information.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation. The use of the phrase "comprising one of the elements does not exclude the presence of other like elements in the process, method, article, or apparatus that comprises the element.
Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that changes, modifications, substitutions and alterations can be made in these embodiments without departing from the principles and spirit of the invention, the scope of which is defined in the appended claims and their equivalents.
Claims (10)
1. A GitLab code warehouse activity intelligent monitoring tool, comprising a code submission module (1), characterized in that: the output end of the code submitting module (1) is connected with the input end of a gitlab monitoring service module (2), the output end of the gitlab monitoring service module (2) is connected with the input end of a warehouse activity monitoring unit (3), the output end of the warehouse activity monitoring unit (3) is connected with the input end of an information sending module (4), and the output end of the information sending module (4) is connected with the input end of an enterprise WeChat robot module (5);
the warehouse activity monitoring unit (3) comprises a specification file checking module (6), a filter submitting module (7), a merging early warning notification module (8), a submission description checking module (9), an event classification module (10) and a main body module (11) for distinguishing and submitting projects, the output end of the event classification module (10) is connected with the input end of the merging early warning notification module (8), the output end of the merging early warning notification module (8) is connected with the input end of the standard file verification module (6), the output end of the specification file checking module (6) is connected with the input end of the submission description checking module (9), the output end of the submission instruction checking module (9) is connected with the input end of the filter submission module (7), the output end of the filter personnel submitting module (7) is connected with the input end of the distinguishing submitting project main body module (11).
2. The intelligent monitoring tool of a GitLab code warehouse activity of claim 1, wherein: the event classification module (10) includes push events, merge events, warehouse update events, add user events, kick users out of team events, project update events, create project events, project delete events, delete user events, create user events, project migration events, tag push events, and destroy ssh key events.
3. The intelligent monitoring tool of a GitLab code warehouse activity of claim 1, wherein: the filter person submitting module (7) reads local code information submitted by developers and transmits the code information to the distinguishing submitting project main body module (11).
4. The intelligent monitoring tool of a GitLab code warehouse activity of claim 1, wherein: the merging early warning notification module (8) merges the submitted same code information, gives an early warning prompt, and transmits the code information to the standard file verification module (6).
5. The intelligent monitoring tool of a GitLab code warehouse activity of claim 1, wherein: the standard file checking module (6) comprises a folder checking module (12) and a file naming checking module (13).
6. The intelligent monitoring tool of a GitLab code warehouse activity of claim 5, wherein: the folder checking module (12) checks whether the folder has an illegal folder or not and files inside the illegal folder.
7. The intelligent monitoring tool of a GitLab code warehouse activity of claim 5, wherein: the file naming checking module (13) checks whether the file naming conforms to a hump naming rule.
8. The intelligent monitoring tool of a GitLab code warehouse activity of claim 1, wherein: the submission instruction checking module (9) checks whether the submitted information is carried out according to the submitted template, and transmits the code information to the filter submitting module (7).
9. The intelligent monitoring tool of a GitLab code warehouse activity of claim 1, wherein: the distinguishing submission item main body module (11) filters and reserves main item information in submitted information.
10. The intelligent monitoring tool of a GitLab code warehouse activity of claim 1, wherein: the information sending module (4) binds the name of the project with the robot, determines the sending of the message according to the submitted warehouse information, and transmits the code information to the enterprise WeChat robot module (5).
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110469479.3A CN113204369A (en) | 2021-04-28 | 2021-04-28 | Intelligent monitoring tool for GitLab code warehouse activity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110469479.3A CN113204369A (en) | 2021-04-28 | 2021-04-28 | Intelligent monitoring tool for GitLab code warehouse activity |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113204369A true CN113204369A (en) | 2021-08-03 |
Family
ID=77027154
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110469479.3A Pending CN113204369A (en) | 2021-04-28 | 2021-04-28 | Intelligent monitoring tool for GitLab code warehouse activity |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113204369A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3296862A1 (en) * | 2016-09-19 | 2018-03-21 | Palantir Technologies Inc. | Version control machine |
| CN109976800A (en) * | 2019-03-28 | 2019-07-05 | 北京字节跳动网络技术有限公司 | Message informing method, device, equipment and storage medium based on Gitlab |
| CN110096303A (en) * | 2019-04-22 | 2019-08-06 | 无线生活（杭州）信息科技有限公司 | Code detection method and device |
| CN111061613A (en) * | 2019-12-12 | 2020-04-24 | 深圳前海环融联易信息科技服务有限公司 | Front-end abnormity monitoring method and device and computer equipment |
| CN111522580A (en) * | 2020-04-22 | 2020-08-11 | 浙江大搜车软件技术有限公司 | Method and device for establishing code branch and computer equipment |
| CN112099843A (en) * | 2020-09-15 | 2020-12-18 | 平安付科技服务有限公司 | Code hosting platform management method and device, computer equipment and storage medium |
| CN112433828A (en) * | 2020-10-29 | 2021-03-02 | 贵州新致普惠信息技术有限公司 | Event-driven continuous integration and continuous deployment method based on multiple types of warehouses |
| CN112685304A (en) * | 2020-12-29 | 2021-04-20 | 平安普惠企业管理有限公司 | Front-end information standard checking method, system, device and storage medium |
-
2021
- 2021-04-28 CN CN202110469479.3A patent/CN113204369A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3296862A1 (en) * | 2016-09-19 | 2018-03-21 | Palantir Technologies Inc. | Version control machine |
| CN109976800A (en) * | 2019-03-28 | 2019-07-05 | 北京字节跳动网络技术有限公司 | Message informing method, device, equipment and storage medium based on Gitlab |
| CN110096303A (en) * | 2019-04-22 | 2019-08-06 | 无线生活（杭州）信息科技有限公司 | Code detection method and device |
| CN111061613A (en) * | 2019-12-12 | 2020-04-24 | 深圳前海环融联易信息科技服务有限公司 | Front-end abnormity monitoring method and device and computer equipment |
| CN111522580A (en) * | 2020-04-22 | 2020-08-11 | 浙江大搜车软件技术有限公司 | Method and device for establishing code branch and computer equipment |
| CN112099843A (en) * | 2020-09-15 | 2020-12-18 | 平安付科技服务有限公司 | Code hosting platform management method and device, computer equipment and storage medium |
| CN112433828A (en) * | 2020-10-29 | 2021-03-02 | 贵州新致普惠信息技术有限公司 | Event-driven continuous integration and continuous deployment method based on multiple types of warehouses |
| CN112685304A (en) * | 2020-12-29 | 2021-04-20 | 平安普惠企业管理有限公司 | Front-end information standard checking method, system, device and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| DEGTYAREV A ET AL.: "A continuous integration system for MPD Root: Deployment and setup in GitLab", 《DISTRIBUTED COMPUTING & GRID-TECHNOLOGIES IN SCIENCE & EDUCATION》 * |
| 夏维嘉 等: "一种企业代码成果管控系统的设计研究", 《中国管理信息化》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11599513B2 (en) | System and method for data quality monitors | |
| CN1316425C (en) | System and method for managing resource | |
| US6751657B1 (en) | System and method for notification subscription filtering based on user role | |
| AU2005202442B2 (en) | System and method for auditing a network | |
| JP2710555B2 (en) | System and method for automating the enforcement of constraints in a database | |
| EP1787219A4 (en) | Adaptive process systems and methods for managing business processes | |
| CN111310330A (en) | Safety emergency plan digitalized parameter design method, system, storage medium and computer equipment | |
| CN103870549B (en) | The method for cleaning and device of petroleum geology software data | |
| Rouvellou et al. | Extending business objects with business rules | |
| Harley et al. | Information Integrity: Are We There Yet? | |
| CN114925391A (en) | Method and device for monitoring circulation of private information, electronic equipment and storage medium | |
| CN113204369A (en) | Intelligent monitoring tool for GitLab code warehouse activity | |
| US20050234990A1 (en) | System and method for tracking documents | |
| JP2007535013A (en) | Computer program design | |
| Amann | A systematic approach to benchmark and improve automated static detection of Java-API misuses | |
| CN113256256A (en) | Work order early warning method, device, equipment and storage medium | |
| Alpturer et al. | Optimal Eventual Byzantine Agreement Protocols with Omission Failures | |
| CN111274780A (en) | Two-ticket management method and system | |
| Dijkman | Feedback on differences between business processes | |
| Edelweiss et al. | A temporal logic language for temporal conditions definition | |
| KR102668324B1 (en) | Method for managing interface, interface governance system, and a storage medium storing a computer-executable program to manage the interface | |
| KR102668329B1 (en) | Method for managing interface, interface governance system, and a storage medium storing a computer-executable program to manage the interface | |
| KR102668325B1 (en) | Method for managing interface, interface governance system, and a storage medium storing a computer-executable program to manage the interface | |
| KR102668341B1 (en) | Method for managing interface, interface governance system, and a storage medium storing a computer-executable program to manage the interface | |
| Feldmann et al. | An ORDBMS-based reuse repository supporting the quality improvement paradigm-exemplified by the SDL-pattern approach |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210803 |