Professional Documents
Culture Documents
∗
Philipp Liegl
Institute of Software Technology and Interactive Systems
Business Informatics Group
Favoritenstrasse 9-11/188
Vienna, Austria
liegl@big.tuwien.ac.at
(2) Agree on Business Documents
7. CONCLUSION
Business Partner A
Business Partner A Business Partner B
Business Partner B Common modeling approaches for B2B scenarios often only
(3) results in reflect a particular part of a business collaboration e.g. only
the process perspective or only the data perspective. In or-
der to allow for a holistic view on a B2B collaboration a solu-
tion embracing all necessary views and technologies is neces-
sary. We have already actively developed the UN/CEFACT’s
Modeling Methodology, reflecting the process perspective of
a business collaboration. This thesis will close the gap to
a holistic B2B methodology by incorporating the business
document modeling perspective as well. Thereby different
business document modeling standards will be evaluated and
their advantages and disadvantages will be assessed.
C
Core Component Model
C tM d l
(4) automatically derive
Based on these results and using UN/CEFACT’s core com-
<xs:schema> ponents technology, a UML profile will be developed. The
<xs:element name="OrderRequest"
... UML profile will allow to easily assemble business documents
</xs:schema> on a common semantic basis. The conceptual business doc-
(5)deploy (5) deploy
(5) deploy ument models will then serve as the basis for the derivation
Partner A's IT‐ Partner B's IT‐
of logical document models e.g. XML schema artifacts. The
System System XML schema artifacts can be fed into IT systems of partic-
ipating business partners and guarantee, that all partners
have the same understanding of the exchanged information.
Figure 3: From a conceptual model to deployment Finally the integration into the process modeling method-
ology UMM will be examined. After the finalization of the
By setting the business document semantic on a conceptual thesis a business modeler will be given a holistic methodol-
level using the core components semantic, a quick agreement ogy for the modeling of B2B scenarios.
between the two business partners is possible. Since the
derivation of the XML artifacts is done automatically, a fast
deployment is possible after the requirements of the business 8. REFERENCES
documents have changed. [1] J. Berge. The EDIFACT Standards. Blackwell
Publishers, Cambridge, MA, USA, 2 edition, 1994.
6. RELATED WORK [2] M. Bernauer, G. Kappel, and G. Kramler. Approaches
For the interested reader a general introduction into the to implementing active semantics with XML schema.
field of business document engineering is given in [6]. In the In Proceedings of the 14th International Workshop on
field of business document standardization several initiatives Database and Expert Systems Applications, pages
have been found in recent years. Mostly the efforts are in- 559–565. 2003.
dustry specific and bound to the XML standard. The most [3] P. P.-S. Chen. The Entity Relationship Model:
important standards include CIDX [4], SWIFT [19], HL7 Towards a unified view of data. 1:9–36, 1976.
[8], and PapiNet [15] just to name a few. A lot of research [4] CIDX. Chemical Industry Data Exchange Standard,
2007. on Information Technology and Applications ICITA
[5] C. Combi and B. Oliboni. Conceptual modeling of 2005, volume 2, pages 772–777. ICITA Proceedings,
XML data. In SAC ’06: Proceedings of the 2006 ACM Australia, 2005.
symposium on Applied computing, pages 467–473.
ACM, New York, NY, USA, 2006.
[6] R. Glushko and T. McGrath. Document Engineering.
Massachusetts Institute of Technology, United States,
2nd edition, 2005.
[7] A. R. Hevner, S. T. March, J. Park, and S. Ram.
Design Science in Information Systems Research.
28:75–105, 2004.
[8] HL7. Health Level Seven, 2007.
[9] C. Huemer and P. Liegl. A UML Profile for Core
Components and their Transformation to XSD. In
ICDE Workshops, pages 298–306, 2007.
[10] C. Janiesch, A. Dreiling, U. Greiner, and S. Lippe.
Configuring processes and business documents - an
integrated approach to enterprise systems
collaboration. In ICEBE, pages 516–521, 2006.
[11] C. Janiesch, A. Dreiling, U. Greiner, and S. Lippe.
Integrated configuration of enterprise systems for
interoperability – towards process model and business
document specification alignment. In EDOC, pages
445–448, 2006.
[12] J. B. Li and J. Miller. Testing the semantics of W3C
XML schema. In Proceedings of the 29th Annual
International Computer Software and Applications
Conference, pages 443–448. 2005.
[13] OASIS. RELAX NG Specification. OASIS, December
2001. Committee Specification.
[14] OASIS. Universal Business Language v2.0. OASIS,
2006.
[15] papiNet. papiNet, 2007.
[16] K. Ramamurthy and G. Premkumar. Determinants
and Outcomes of Electronic Data Interchange
Diffusion. 42:332–351, 1995.
[17] D. Skogan. UML a Schema Language for XML based
Data Interchange. In Proceedings of the Second
International Conference on the Unified Modeling
Language, volume 2, pages 211–220. Proceedings,
United States, 1999.
[18] Sparx Systems. Enterprise Architect, 2008.
[19] SWIFT. Society for Worldwide Interbank Financial
Telecommunication, 2007.
[20] UN/CEFACT. UN/EDIFACT D.07B, 2007.
[21] UN/CEFACT TMG. Core Components Technical
Specification - Part 8 of the ebXML Framework, 2003.
[22] UN/CEFACT TMG. UN/CEFACT’s Modeling
Methodology (UMM), UMM Meta Model - Foundation
Module, 2006.
[23] UN/CEFACT TMG. UPCC - UML Profile for Core
Components based on CCTS 2.01. United Nations
Center For Trade Facilitation and Electronic Business,
October 2006. Candidate for version 1.0.
[24] UN/CEFACT TMG. Core Components Technical
Specification 3.0 - draft, 2008.
[25] W3C. Simple Object Access Protocol, 2007.
[26] W3C. Web Services Description Language, 2007.
[27] A. Yu and R. Steele. An overview of research on
reverse engineering XML schemas into UML diagrams.
In Proceedings of the Third International Conference