KR20220149122A - System and method for testing interoperability between documents - Google Patents

Abstract

According to one embodiment of the present invention, a system for verifying interoperability suitability between documents includes: a plurality of ICD managers which generate an ICD definition file based on a user development code, which is a project result of the user; an interoperability suitability verification server which receives a plurality of ICD definition files from the ICD managers and verifies interoperability suitability for the received ICD definition files by performing a specification and model test, a suitability test, and an information processing interoperability test for the received ICD definition files; and a system interoperability infrastructure which interoperates the ICD definition files, of which interoperability suitability is verified, to perform system integration.

Description

System and method for testing interoperability between documents}

An embodiment of the present invention relates to a document, and more particularly, to a system and method for verifying interworking suitability between documents.

According to the division of labor of the project, each developer creates an output for their own project. To complete the project, the developer's results are passively shared through the Interface Control Document (hereinafter referred to as 'ICD'), and system integration is performed at the final stage. For example, the ICD may indicate a drawing or document recorded by organizing the physical or functional characteristics and performance of the related product and the items to be tested to control the interface.

However, there was a problem in that system integration was not achieved due to conflicts between ICDs in the final stage. Even, the inconvenience occurred that the developer had to re-develop by rolling back the development he had developed. That is, due to these problems, the development cost of the project rises, the development period is delayed, and the developer's mind is consumed.

Therefore, the need for a method for solving these problems has emerged.

An embodiment of the present invention provides a system and method for verifying interworking suitability between documents so that a conflict does not occur between ICDs.

In addition, an embodiment of the present invention provides a system and method for verifying interworking suitability between documents to prevent an increase in development cost and a delay in the development period.

According to an embodiment of the present invention, a system for verifying interworking suitability between documents includes: a plurality of ICD managers generating an ICD definition file based on a user development code that is a result of a user's project; Receive a plurality of ICD definition files from the ICD managers, and perform a specification and model test, a conformance test, and an information processing interoperability test on the received ICD definition files to determine interoperability suitability for the received ICD definition files. Interworking conformity verification server to verify; and a system interworking infrastructure for performing system integration by linking the ICD definition files whose interworking suitability has been verified.

According to an embodiment of the present invention, in a method of verifying interworking suitability between documents, each of a plurality of ICD managers generates an ICD definition file based on a user development code that is a result of a user's project, and the generated ICD Transmitting the definition files to the interworking conformance verification server; A process in which the interworking suitability verification server performs a specification and model test, a conformance test, and an information processing interoperability test on the ICD definition files received from the ICD managers to verify the interoperability suitability of the received ICD definition files ; and the system interworking infrastructure performing system integration by interlocking the ICD definition files whose interworking suitability has been verified.

According to an embodiment of the present invention, conflicts between ICDs can be prevented by verifying interworking suitability between documents in advance.

In addition, according to an embodiment of the present invention, it is possible to prevent an increase in development cost and a delay in the development period by verifying the interworking suitability between documents in advance.

1 is a conceptual diagram of performing system integration between documents according to a general technique.
2 is a conceptual diagram illustrating system integration between documents according to an embodiment of the present invention.
3 is a block diagram of an interworking suitability verification system according to an embodiment of the present invention.
4 is a diagram illustrating a procedure for performing an integration test in the interworking suitability verification system according to an embodiment of the present invention.
5 is a flowchart of performing an integration test in the interworking conformance verification system according to an embodiment of the present invention.

Terms used in this specification will be briefly described, and the present invention will be described in detail.

The terms used in the embodiments of the present invention have been selected as currently widely used general terms as possible while considering the functions in the present invention, but this may vary depending on the intention or precedent of a person skilled in the art, the emergence of new technology, etc. . In addition, in a specific case, there is a term arbitrarily selected by the applicant, and in this case, the meaning will be described in detail in the description of the corresponding invention. Therefore, the term used in the present invention should be defined based on the meaning of the term and the overall content of the present invention, rather than the name of a simple term.

Embodiments of the present invention can apply various transformations and can have various embodiments, and specific embodiments are illustrated in the drawings and described in detail in the detailed description. However, this is not intended to limit the scope of the specific embodiments, and it should be understood to include all transformations, equivalents and substitutes included in the spirit and scope of the invention. In the description of the embodiments, if it is determined that a detailed description of a related known technology may obscure the subject matter, the detailed description thereof will be omitted.

Terms such as first, second, etc. may be used to describe various elements, but the elements should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.

The singular expression includes the plural expression unless the context clearly dictates otherwise. In the present application, terms such as "comprises" or "consisting of" are intended to designate that the features, numbers, steps, operations, components, parts, or combinations thereof described in the specification exist, and are intended to indicate that one or more other It is to be understood that this does not preclude the possibility of addition or presence of features or numbers, steps, operations, components, parts, or combinations thereof.

In an embodiment of the present invention, a 'module' or 'unit' performs at least one function or operation, and may be implemented as hardware or software, or a combination of hardware and software. In addition, a plurality of 'modules' or a plurality of 'units' are integrated into at least one module except for 'modules' or 'units' that need to be implemented with specific hardware and are implemented with at least one processor (not shown). can be

In an embodiment of the present invention, when a part is "connected" with another part, it is not only "directly connected" but also "electrically connected" with another element interposed therebetween. also includes In addition, when a part "includes" a certain component, this means that other components may be further included, rather than excluding other components, unless otherwise stated.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those of ordinary skill in the art to which the present invention pertains can easily implement them. However, the present invention may be embodied in various different forms and is not limited to the embodiments described herein. And in order to clearly explain the present invention in the drawings, parts irrelevant to the description are omitted, and similar reference numerals are attached to similar parts throughout the specification.

1 is a conceptual diagram of performing system integration between documents according to a general technique.

Referring to FIG. 1 , the system integration conceptual diagram includes a system interworking infrastructure 101 , a first system development module 103 , and a second system development module 105 .

Looking at each component, the system interworking infrastructure 101 performs system integration of the first system development module 103 and the second system development module 105 by linking the first ICD and the second ICD. For example, the first ICD may be a document generated by documenting the project result of the first user (or developer) for the first system development module 103 . For example, the second ICD may be a document generated by documenting the result of the second user's project for the second system development module 105 . For example, the ICD may indicate a drawing or document recorded by organizing the physical or functional characteristics and performance of the related product and the items to be tested to control the interface.

In this case, when communication between the first user and the second user is ambiguous, a human error may occur when the system interworking infrastructure 101 performs system integration. In this case, there is a problem that interworking fails between the first ICD and the second ICD. Even, the inconvenience occurred that the developer had to re-develop by reverting the development that he had developed. That is, due to these problems, the development cost of the project rises, the development period is delayed, and the developer's mind is consumed.

An embodiment of the present invention will be described with reference to FIGS. 2 to 5 for solving such a problem.

2 is a conceptual diagram illustrating system integration between documents according to an embodiment of the present invention.

Referring to FIG. 2 , the system integration conceptual diagram shows the system interworking infrastructure 201, the first interworking compatibility module 203, the second interworking compatibility module 205, the first system development module 207, and the second system development module ( 209).

Looking at each component, the first interworking compatibility module 203 receives the first ICD from the first system development module 207 and verifies interworking suitability for the inputted first ICD. If the first ICD passes the interworking suitability verification, the first interworking conformance module 203 outputs the first ICD to the system interworking infrastructure 201 . On the other hand, if the first ICD does not pass the interworking conformance verification, the first interworking conformance module 203 transmits the verification result of the first ICD to the first user. For example, the first ICD may be a document generated by documenting the project result of the first user for the first system development module 207 .

The second interworking compatibility module 205 receives the second ICD from the second system development module 209 and verifies interworking suitability for the input second ICD. If the second ICD passes the interworking conformance verification, the second interworking conformance module 205 outputs the second ICD to the system interworking infrastructure 201 . On the other hand, if the second ICD does not pass the interworking conformance verification, the second interworking conformance module 205 transmits the verification result of the second ICD to the second user. For example, the second ICD may be a document generated by documenting the result of the second user's project for the second system development module 209 . For example, the first interworking compatibility module 203 and the second interworking compatibility module 205 may be commonly distributed modules.

The system interworking infrastructure 201 receives the first ICD and the second ICD whose interworking suitability has been verified, and integrates the system between the first system development module 207 and the second system development module 209 by interworking the input first and second ICDs. carry out

As such, an embodiment of the present invention provides a system by verifying interworking compatibility for the first and second ICDs using the first and second interworking compatibility modules 203 and 205 before interworking the first and second ICDs. It can reduce the errors that occur during integration as well as reduce development time.

3 is a block diagram of an interworking suitability verification system according to an embodiment of the present invention.

Referring to FIG. 3 , the interworking conformance verification system includes an ICD manager 301 , an interworking conformance verification server 307 , a Korean protocol standard database 309 , and a test case database 311 .

Looking at each component, the ICD manager 301 is distributed to each of users (eg, project developers). For example, the ICD manager 301 may be installed in a portable terminal or terminal used by a user. For example, the mobile terminal may be a smart phone, a mobile phone, a TV, a display device, a vehicle head unit, a notebook computer, a laptop computer, a tablet computer, a personal media player (PMP), a personal digital assistant (PDA), or the like. . The portable terminal may be implemented as a pocket-sized portable communication terminal having a wireless communication function. Also, the portable terminal may be a flexible device or a flexible display device. For example, the terminal may be a desktop computer or the like.

The ICD manager 301 receives a project result from the user, and applies an automation code to the input project result to generate the ICD 305 . At this time, the ICD manager 301 converts the project result into an automation code in consideration of the Korean protocol standard database. Then, the ICD manager 301 normalizes the ICD 305 to a specific programming language to generate an ICD definition file 303 , and transmits the generated ICD definition file 303 to the interworking suitability verification server 307 . For example, the specific programming language may be XML (eXtensible Markup Language) or JSON (Javascript Object Notation). For example, the ICD manager 301 may design a common transmission/reception module based on a communication interface and an open upper interface part.

The interworking suitability verification server 307 receives the ICD definition file 303 from the ICD manager 301 and performs an interworking conformance integration test on the received ICD definition file 303 to verify the interworking suitability. For example, the interoperability conformance integration test includes a specification and model test, a conformance test, and an information processing interoperability test.

For example, the specification and model test may be a test that confirms whether the specification and model of the ICD definition file are greater than or equal to a predetermined specification and model. For example, the predefined specification and model may indicate a reference version of the specification and model of the interoperable ICD.

For example, the conformance test may be a test that confirms the expected response of the ICD to the input case in a 1:1 environment by inputting a pre-specified test case input file to the ICD. . For example, the preset test case input file may be stored in advance in the test case database 311 .

For example, the information processing interoperability test may be a test that confirms the expected response of the ICD to the input case in a 1:N environment.

Then, the interworking suitability verification server 307 generates a result report 313 according to the verification result, and transmits the generated result report 313 to an external device (eg, the ICD manager 301 ). After that, the system interworking infrastructure performs system integration by linking the ICD that has passed the interworking suitability verification with other ICDs.

Through this configuration, an embodiment of the present invention can prevent a collision between ICDs by verifying in advance the interworking suitability between documents. In addition, according to an embodiment of the present invention, it is possible to prevent an increase in development cost and a delay in the development period by verifying the interworking suitability between documents in advance.

4 is a diagram illustrating a procedure for performing an integration test in the interworking suitability verification system according to an embodiment of the present invention.

Referring to FIG. 4 , the interworking conformance verification system includes first to third ICD managers 401 , 403 , 405 , first to third interworking conformance modules 413 , 415 , 417 , and a system interworking infrastructure 419 . do.

Looking at each component, the first to third ICD managers 401, 403, and 405 normalize the project results of the first to third users for the first to third subsystems based on the ICD into XML, and First to third ICD definition files 407 , 409 , and 411 are generated. In addition, the first to third ICD managers 401 , 403 , and 405 use the generated first to third ICD definition files 407 , 409 and 411 with the first to third interworking conformance modules 413 , 415 and 417 . output as

The first and third interworking conformance modules 413 , 415 , and 417 of the interworking conformance verification server 307 receive the first to third ICD definition files 407 from the first to third ICD managers 401 , 403 , 405 . , 409 and 411 are input, and an interworking conformance integration test is performed on the input first to third ICD definition files 407 , 409 and 411 .

For example, the first interworking conformance module 413 may sequentially perform a specification and model test, a conformance test, and an information processing interoperability test on the first ICD definition file 407 . For example, the first interworking conformance module 413 checks whether the specification and model of the first ICD definition file 407 are greater than or equal to a predetermined specification and model, and performs a specification and model test for the first ICD definition file 407 can be done If the specification and model of the first ICD definition file 407 are greater than or equal to the predetermined specification and model, the first interworking conformance module 413 may determine that the specification and model of the first ICD definition file 407 are suitable for interworking. . On the other hand, if the specification and model of the first ICD definition file 407 are less than the specified specification and model, the first interworking conformance module 413 determines that the specification and model of the first ICD definition file 407 are not suitable for interworking. can

For example, the first interworking conformance module 413 may perform a conformance test on the first ICD definition file 407 by inputting a pre-specified test case input file to the first ICD definition file 407 .

For example, the first interworking conformance module 413 receives the second ICD definition file 409 from the second interworking conformance module 415 , and receives the third ICD definition file 411 from the third interworking conformance module 417 . can receive In addition, the first interworking conformance module 413 interlocks the second ICD definition file 409 with the first ICD definition file 407 in advance, and links the third ICD definition file 411 with the first ICD definition file 407 in advance. An information processing interoperability test may be performed on the first ICD definition file 407 .

For example, the second interworking conformance module 415 may sequentially perform a specification and model test, a conformance test, and an information processing interoperability test on the second ICD definition file 409 . For example, the third interworking conformance module 417 may sequentially perform a specification and model test, a conformance test, and an information processing interoperability test on the third ICD definition file 411 . For example, the second and third interworking conformance modules 415 and 417 verify interworking suitability for the second and third ICD definition files 409 and 411 in the same manner as the first interworking conformance module 413 . can do.

The system interworking infrastructure 419 receives the first to third ICD definition files 407, 409, and 411 whose interworking suitability is verified from the first to third interworking conformance modules 413, 415, and 417, and the input System integration is performed between the first to third subsystems by linking the first to third ICD definition files 407 , 409 , and 411 .

5 is a flowchart of performing an integration test in the interworking conformance verification system according to an embodiment of the present invention.

Referring to FIG. 5 , in step 507 , the first ICD manager 501 converts the first user development code, which is the project result of the first user, into XML to generate the first ICD definition file. In step 509 , the first ICD manager 501 transmits the generated first ICD definition file to the interworking suitability verification server 505 .

In step 511, the second ICD manager 503 converts the second user development code, which is the result of the second user's project, into XML to generate a second ICD definition file. In step 513 , the second ICD manager 503 transmits the generated second ICD definition file to the interworking suitability verification server 505 .

In step 515 , the interworking suitability verification server 505 performs specification and model tests on the first and second ICD definition files received from the first and second ICD managers 501 and 503 .

For example, the interworking suitability verification server 505 may perform a specification and model test on the first ICD definition file by confirming whether the specification and model of the first ICD definition file are greater than or equal to a predetermined specification and model. In addition, the interworking suitability verification server 505 may perform a specification and model test on the second ICD definition file by confirming whether the specification and model of the second ICD definition file are greater than or equal to a pre-specified specification and model.

In step 517, the interworking conformance verification server 505 performs a conformance test and an information processing interoperability test on the first and second ICD definition files.

For example, the interworking conformance verification server 505 may perform a conformance test on the first ICD definition file by inputting a pre-specified test case input file to the first ICD definition file. For example, the interworking conformance verification server 505 may perform a conformance test on the second ICD definition file by inputting a pre-specified test case input file to the second ICD definition file.

For example, the interworking suitability verification server 505 may link the second ICD definition file to the first ICD definition file in advance and perform an information processing interoperability test on the first ICD definition file. For example, the interworking suitability verification server 505 may perform an information processing interoperability test on the second ICD definition file by linking the first ICD definition file with the second ICD definition file in advance.

In step 519, the interworking suitability verification server 505 generates a report of the results of the tests performed in steps 515 and 517. Thereafter, the interworking suitability verification server 505 transmits the generated result report to the first and second ICD managers 501 and 503 .

Through this process, an embodiment of the present invention can prevent conflicts between ICDs by verifying interworking suitability between documents in advance. In addition, according to an embodiment of the present invention, it is possible to prevent an increase in development cost and a delay in the development period by verifying the interworking suitability between documents in advance.

In the above, preferred embodiments of the present invention have been illustrated and described, but the present invention is not limited to the specific embodiments described above, and it is common in the technical field to which the present invention pertains without departing from the gist of the present invention as claimed in the claims. Various modifications may be made by those having the knowledge of, of course, and these modifications should not be individually understood from the technical spirit or perspective of the present invention.

101: system interworking infrastructure 103: first system development module
105: first system development module
201: system interworking infrastructure 203: first interworking conformity verification module
205: second interlock conformity verification module 207: first system development module
209: second system development module
301: ICD manager 303: common module
305: ICD definition file 307: interworking conformance verification server
309: Korean protocol standard database
311: test case database 313: test result report
313: Spec and Model Testing
315: Conformance and interoperability testing
401: first ICD manager 403: second ICD manager
405: third ICD manager 407: first ICD definition file
409: second ICD definition file 411: third ICD definition file
413: first interlocking conformance module 415: second interlocking compatibility module
417: Third interworking conformance module 419: System interworking infrastructure

Claims (6)

a plurality of ICD managers for generating an ICD definition file based on a user-developed code that is a result of a user's project;
Receive a plurality of ICD definition files from the ICD managers, and perform a specification and model test, a conformance test, and an information processing interoperability test on the received ICD definition files to determine interoperability suitability for the received ICD definition files. Interworking conformity verification server to verify; and
A system for verifying interworking suitability between documents including a system interworking infrastructure that performs system integration by linking the ICD definition files whose interworking suitability has been verified.
According to claim 1,
The interworking suitability verification server checks whether the specification and model of the first ICD definition file among the ICD definition files are greater than or equal to a predetermined reference specification and model, and performs a specification and model test on the first ICD definition file, characterized in that A system that verifies interoperability between documents.
3. The method of claim 2,
The interworking conformance verification server performs a conformance test on the first ICD definition file by inputting a test case input file specified in advance to the first ICD definition file, and defines a second ICD from among the ICD definition files in the first ICD definition file. A system for verifying interoperability between documents, characterized in that the information processing interoperability test is performed on the first ICD definition file by linking the files in advance.
a process in which each of the plurality of ICD managers generates an ICD definition file based on a user development code that is a result of a user's project, and transmits the generated ICD definition files to an interworking suitability verification server;
A process in which the interworking suitability verification server performs a specification and model test, a conformance test, and an information processing interoperability test on the ICD definition files received from the ICD managers to verify the interoperability suitability of the received ICD definition files ; and
A method of verifying interworking suitability between documents, including a process in which the system interworking infrastructure performs system integration by linking the ICD definition files whose interworking suitability has been verified.
5. The method of claim 4,
The process of verifying the interworking suitability is a process of performing a specification and model test on the first ICD definition file by confirming whether the specification and model of the first ICD definition file among the ICD definition files are greater than or equal to a predetermined reference specification and model A method of verifying interworking suitability between documents, characterized in that
6. The method of claim 5,
The step of verifying the interworking suitability may include, by the interworking suitability verification server, performing a conformance test on the first ICD definition file by inputting a pre-specified test case input file to the first ICD definition file; and
Interoperability between documents, characterized in that it includes the process of performing an information processing interoperability test on the first ICD definition file by linking a second ICD definition file among the ICD definition files to the first ICD definition file in advance How to verify.

Images