Domen Dolar (2006) Development of meta model to prepare e-documents. MSc thesis.
Abstract
Organizations often decide for automatic electronic exchange because they gain lower costs for exchange data and faster exchanging process. But one of main advantages of using automated exchange is standardized preparation of electronic documents. Each element of document is unique and it is defined in so called electronic catalogs. Today we have lots of recommendations, specifications and standards of electronic catalogs (ebXML, UN/EDIFACT, eSLOG, xForms ...). Organizations use them in process of defining electronic documents and electronic interchange. Organization UN/CEFACT (United Nations Centre for Trade Facilitation and Electronic Business) organization did a great work specifying content of electronic business documents. Their main specification is UN/EDIFACT and it is integrated in many organizations, but due to its high price and complexity only big organizations are able to afford it. The result of connecting UN/CEFACT and OASIS (Organization for the Advancement of Structured Information Standards) consortium is specification ebXML. Even this specification does not cover all electronic business documents and organizations usually make them ad-hoc. Because of that, they lose information about elements on the documents and connections between documents. Electronic catalogs structure can be presented with multi layer structure. We divide model on different layers which are hierarchaly connected. Each layer supplement higher layer. The layers are: Meta model, Framework, Processes, Documents, Vocabulary, Data types. All standards and specifications do not include all layers. In year 2002, CEN/ISSS (European Committee for Standardization, Information and Communications Technologies) started with project eCAT in which they made analysis of more than twenty catalogs. The ebXML was one of them. EbXML specification covers almost all layers except preparing of documents. This is the reason to prepare model for preparing documents. This model should make possible easy, simple, quick and inexpensive prepare of electronic business documents and integrate them in their business process. I have named it meta model for preparing e-documents (MMeD). MMeD consist of registry, where are definitions of elements and types, and repository, where are definitions of procedures of preparing and exchanging electronic business documents. Most important standard to prepare meta model is ISO/IEC 11179. Important characteristic of prepared meta model is connectivity with other specifications. MMeD will be integrated in specification ebXML. MMeD must make possible: - To send electronic documents on different ways (services, web …), - Unique identification of documents regardless the sending way, - Easily preparing of new documents, - Security, - Connectivity with other specifications and standards. For preparing business documents we have to perform following steps: a. Analysis and designing: - Documents (business rules, code books), - Documents flows, - Documents interchange (technical architecture); b. Runtime: - Electronic business documents interchange between sender and receiver. The biggest benefit of using MMeD will gain organizations which receive many different documents that can be standardinized or any other documents. Government is one among these organizations.
Item Type: | Thesis (MSc thesis) |
Keywords: | electronic business, electronic data interchange, meta model, electronic catalogs, e-catalogs, e-documents, electronic business documents, SOAP services, ebXML |
Language of Content: | Slovenian |
Link to COBISS: | http://www.cobiss.si/scripts/cobiss?command=search&base=50070&select=(ID=5621076) |
Institution: | University of Ljubljana |
Department: | Faculty of Computer and Information Science |
Divisions: | Faculty of Computer and Information Science > Computer Vision Laboratory |
Item ID: | 226 |
Date Deposited: | 16 Jan 2007 |
Last Modified: | 13 Aug 2011 00:32 |
URI: | http://eprints.fri.uni-lj.si/id/eprint/226 |
---|
Actions (login required)