![](bg3.png)
If more issues regarding E-Gov are considered, the
situation for system analysis for interface control
toward SOA is getting harder than previous case.
3 SOA-BASED ARCHITECTURE
FOR INTERFACE CONTROL
In this paper, the way to conduct system interface
control toward SOA is discussed for System
Engineer more effectively and accurately in time
manner. As there are increasing requirements for
information exchange and service sharing in a
unified manner, the situation of change request
based on health system using HL7 protocol is
considered. And the effective representation is
addressed using XML.
<?xml version="1.0" encoding="EUC-KR"?>
<HL7import>
<Segment1>MSH
<Element1>
<Field1>^</Field1>
<Field2>~</Field2>
<Field3>\</Field3>
<Field4>amp</Field4>
</Element1>
<Element2>ADT1</Element2>
<Element3>MCM</Element3>
<Element4>LABADT</Element4>
<Element5>198808181126</Element5>
<Element6>Security</Element6>
<Element7>
<Field1>ADT</Field1>
<Field2/>
<Field3>A01</Field3>
</Element7>
<Element8>MSG00001</Element8>
<Element9>P</Element9>
<Element10>2.3.1</Element10>
</Segment1>
<Segment2>EVN
<Element1>A01</Element1>
<Element2>198808181123</Element2>
</Segment2>
<Segment3>PID
<Element1>1</Element1>
<Element2>
<Field1>PATID12345</Field1>
<Field2>M11</Field2>
<Field3>ADT</Field3>
</Element2>
<Element3>MR</Element3>
<Element4>
<Field1>MCM</Field1>
<Field2/>
<Field3>123456789</Field3>
<Field4/>
<Field5/>
<Field6>USSSA</Field6>
<Field7>SS</Field7>
</Element4>
<Element5>
<Field1>JOHNES</Field1>
<Field2>WILLIAM</Field2>
<Field3>A</Field3>
<Field4>III</Field4>
</Element5>
<Element6>M-</Element6>
<Element7>C</Element7>
<Element8>
<Field1>1200</Field1>
<Field2>N</Field2>
<Field3>ELM</Field3>
<Field4>STREET</Field4>
<Field5/>
<Field6>GREENSBORO</Field6>
<Field7>NC</Field7>
<Field8>27401-1020</Field8>
</Element8>
<Element9>GL</Element9>
<Element10>(919)379-1212</Element10>
<Element11>(919)271-3434</Element11>
<Element12>S</Element12>
<Element13/>
<Field1>PATID12345001</Field1>
<Field2>2</Field2>
<Field3>M10</Field3>
<Field4>ADT1</Field4>
<Field5>AN</Field5>
<Field6>A</Field6>
<Element14>123456789</Element14>
<Element15/>
<Field1>987654</Field1>
<Field2>NC</Field2>
</Segment3>
<Segment4>NK1
<Element1>1</Element1>
<Element2>
<Field1>JOHNES</Field1>
<Field2>BARBARA</Field2>
<Field3>K</Field3>
</Element2>
<Element3>
<Field1>WI</Field1>
<Field2>WIFE</Field2>
</Element3>
<Element4>
<Field1>NK</Field1>
<Field2>NEXT OF KIN</Field2>
</Element4>
</Segment4>
<Segment5>PV1
<Element1>1</Element1>
<Element2>I</Element2>
<Element3>
<Field1>2000</Field1>
<Field2>2012</Field2>
<Field3>01</Field3>
</Element3>
<Element4>
<Field1>004777</Field1>
<Field2>LEBAUER</Field2>
<Field3>SIDNEY</Field3>
<Field4>J.</Field4>
</Element4>
<Element5>SUR</Element5>
</Segment5>
</HL7import>
<?xml version="1.0" encoding="EUC-KR"?>
<HL7import>
<Segment1>MSH
<Element1>
<Field1>^</Field1>
<Field2>~</Field2>
<Field3>\</Field3>
<Field4>amp</Field4>
</Element1>
<Element2>ADT1</Element2>
<Element3>MCM</Element3>
<Element4>LABADT</Element4>
<Element5>198808181126</Element5>
<Element6>Security</Element6>
<Element7>
<Field1>ADT</Field1>
<Field2/>
<Field3>A01</Field3>
</Element7>
<Element8>MSG00001</Element8>
<Element9>P</Element9>
<Element10>2.3.1</Element10>
</Segment1>
<Segment2>EVN
<Element1>A01</Element1>
<Element2>198808181123</Element2>
</Segment2>
<Segment3>PID
<Element1>1</Element1>
<Element2>
<Field1>PATID12345</Field1>
<Field2>M11</Field2>
<Field3>ADT</Field3>
</Element2>
<Element3>MR</Element3>
<Element4>
<Field1>MCM</Field1>
<Field2/>
<Field3>123456789</Field3>
<Field4/>
<Field5/>
<Field6>USSSA</Field6>
<Field7>SS</Field7>
</Element4>
<Element5>
<Field1>JOHNES</Field1>
<Field2>WILLIAM</Field2>
<Field3>A</Field3>
<Field4>III</Field4>
</Element5>
<Element6>M-</Element6>
<Element7>C</Element7>
<Element8>
<Field1>1200</Field1>
<Field2>N</Field2>
<Field3>ELM</Field3>
<Field4>STREET</Field4>
<Field5/>
<Field6>GREENSBORO</Field6>
<Field7>NC</Field7>
<Field8>27401-1020</Field8>
</Element8>
<Element9>GL</Element9>
<Element10>(919)379-1212</Element10>
<Element11>(919)271-3434</Element11>
<Element12>S</Element12>
<Element13/>
<Field1>PATID12345001</Field1>
<Field2>2</Field2>
<Field3>M10</Field3>
<Field4>ADT1</Field4>
<Field5>AN</Field5>
<Field6>A</Field6>
<Element14>123456789</Element14>
<Element15/>
<Field1>987654</Field1>
<Field2>NC</Field2>
</Segment3>
<Segment4>NK1
<Element1>1</Element1>
<Element2>
<Field1>JOHNES</Field1>
<Field2>BARBARA</Field2>
<Field3>K</Field3>
</Element2>
<Element3>
<Field1>WI</Field1>
<Field2>WIFE</Field2>
</Element3>
<Element4>
<Field1>NK</Field1>
<Field2>NEXT OF KIN</Field2>
</Element4>
</Segment4>
<Segment5>PV1
<Element1>1</Element1>
<Element2>I</Element2>
<Element3>
<Field1>2000</Field1>
<Field2>2012</Field2>
<Field3>01</Field3>
</Element3>
<Element4>
<Field1>004777</Field1>
<Field2>LEBAUER</Field2>
<Field3>SIDNEY</Field3>
<Field4>J.</Field4>
</Element4>
<Element5>SUR</Element5>
</Segment5>
</HL7import>
Figure 3: Converted XML from HL7 Sample Message.
Figure 3 is the corresponding representation of
HL7 example.
XML representation is more
understandable for System Engineer and scalable to
different format for future needs. Whenever
appropriate, it can be possibly triggered and
converted by the development.
A common
environment as shown in Figure 4 can be built for
further testing and the simulation of the impact
analysis on the interface. As an input, interface
related documentation information such as ICD, and
more for specific systems, Online log file and parsed
data at the developmental engineering lab for testing
are considered. Most components are smoothly
linked through XML and triggered by XPath.
Parsed Data
HL7 Log
Do cu me nt
Do c_ 2 _T xt
DOM Checker
Path_ Fi nder
Compare_DOMtree
Analysis_Maintainer
Ac t iv e _
Do cu me n t
Report _Generat or
IIA&T_
Mi dd l e w a r e
Case(for IA)
_Generator
Vi r tu a l
_User
_Generator
SOA-based Executable Architecture (Local Server)
Simulator (User Client)
XML_2_ Tr ee
Txt _2_ XML
Cs v _ 2 _ T xt
HL7 Test Maintainer
Ex
Tr act
or
html_2_Txt
Input : Document/Parsed Data/HL7 Log, Output : Active Document
Program for conversion: *_2_*, IIA & T : Interface Impact Analyzer and Tester
Figure 4: Proposed XML-based Architecture.
The simulation system is designed to equip the
scalability for the future demands. In other words,
the experiment with another non-functional
requirement system on security as well as
performance tool and an extension of the rule
domain upon the future demands are combined.
In Figure 4, in order to compare DOM tree-based
information, to maintain the HL7 message segment
table and the previous test case history data set is
needed as a database. At this point, the performing
interface issue using the local server at the
operational environment for simulation is out of
scope in this paper, as the primary purpose of the
simulation is on showing an efficiency improvement
of the suggested impact analysis for the decision-
making during developmental testing phase on
whether or not a system change can be applied to the
systems without causing any negative interface
impact.
It is ensured that there are many more problems
to which this technique can be applied. Using XML-
based information, system and testing engineers save
their time and support customers with more value-
added service by getting more realistic information
using testing requirement for impact analysis. More
information with non-functional requirement for
impact analysis in general is discussed later. Based
on the testing for the research with XML-based
ICEIS 2006 - INFORMATION SYSTEMS ANALYSIS AND SPECIFICATION
244