Added by Gil Jun Ko, last edited by Gil Jun Ko on Sep 22, 2014  (view change)

Labels

 

Table of Content

1. REFERENCES DOCUMENT

Knowledge and application of the following standards is crucial to the development of quality business requirements specifications. Other key references are shown in the appropriate part of the document.

UN/CEFACT. Techniques and Methodologies Group (TMG). UN/CEFACT's Modelling Methodology (UMM): UMM Meta Model Core Module. (Candidate for 2.0). 2009-01-30.

UN/CEFACT Techniques and Methodologies Group (TMG) UN/CEFACT's Modelling Methodology (UMM): UMM Meta Model Foundation Module (Candidate for 2.0) 2009-01-30.

Formal definitions of many of the technical terms used in this RSM guideline may be found in the above references but for convenience some key definitions are included in Annex 1 of this document.

UN/CEFACT Core Components Technical Specification – Part 8 of the ebXML Framework dated 15 November 2003 Version 2.01 - (CCTS 2.01)
UN/CEFACT – Core Component Technical Specification Technical Corrigendum Version 2.01 (Corr. 1) dated 12 February 2007 (CCTS 2.01 Corr.1)
UN/CEFACT Core Components Data Type Catalogue Version 2.1 dated 2008-04-08 (CCDTC 2.1)
UN/CEFACT XML Naming and Design Rules Version 2.0, dated 17 February 2006 (NDR 2)
UN/CEFACT UML Profile for Core Components (UPCC), Version 1.0, Final Specification, 2008-01-16

UN/CEFACT Core Components Technical Specification Version 3.0 dated 29 September 2009 - (CCTS 3)
UN/CEFACT Core Components Data Type Catalogue Version 3.0 dated 29 September 2009 - (CCDTC 3)
UN/CEFACT XML Naming and Design Rules Technical Specification Version 3.0 dated 17 December 2009 - (NDR 3)
UN/CEFACT UML Profile for Core Components (UPCC), Version 3.0, Latest Version

In this document the set of CCTS 2.01 / CCTS 2.01 Corr.1 / NDR 2 / CCDTC 2.1 specifications are referred to as "UN/CEFACT Technical Specifications Version 2" and the set of CCTS 3 / NDR 3 / CCDTC 3 specifications are referred to as "UN/CEFACT Technical Specifications Version 3”.

The following Technical Specifications are at the time of the writing of this document not finalized, but are all highly relevant to the contents of this document and are referred to herein.

UN/CEFACT Core Component Business Document Assembly

UN/CEFACT Context Methodology

UN/CEFACT XML For CCTS

2.INTRODUCTION

The tourism industry in many countries around the world in electronic trading and the management of the common things that will manage a standard. Among a lot of information in a common location for a tourist destination, so that the data used in electronic commerce.
Since 2009, BRS documents based on the research by utilizing a tourist destination business models of electronic commerce and the tourism industry worldwide in developing and maintaining redundant systems through the exchange of information narrowed down, its the first things disclosed to enable electronic transactions to proceed.
 

2.1 PURPOSE AND SCOPE

The document is utilized for electronic trading tourist destinations tourist information exchange requirements for clean up.
This document is a tourist destination objects and properties of the information necessary for business stakeholders to define and standardize the message.
BRS needed for electronic trading destinations listed in the classification, visit destination for the system data flow, utilizing destination information includes the business modeling.

2.2 TARGET SOLUTION

Tourism destination attribute definitions needed to exchange information and provide XML standards for data exchange and electronic trading of goods by presenting a method for distinguishing generic name or description, or an error occurred failed to distinguish the unique tourism products distinguish.

  • XML Schema

2.3 BUSINESS REQUIREMENTS SUMMARY 

Is defined in consideration of the data utilized for the service building DTI BRS 1.0 systems needed functional requirement. First, do not make part of the tourism services of RSM to build a DB and use of the building of the system.

  • Sensitive and unique tourism destination awareness
  • Identify geographical locations of tourist destinations
  • Understanding the geographic relationship between tourism destination information
  • Anger Anger constant support list for multiple destination
  • Identifying the location information using a satellite

2.4 BUSINESS PROCESSES, INFORMATION ENVELOPES AND AUTHORISED ROLES 

2.5 BUSINESS PARTNER TYPES AND AUTHORISED ROLES 

requirements to use the information
Private provider: individual Customers that share their own travel information through DTI servers
DTI Customers: information Customers with the access to the original information or partially disclosed information depending on the information provider. Customers can create or develop businesses or products using DTI.

2.5.1 Conceptual Model 


2.6 INFORMATION MAPPING

2.7 LOGICAL MESSAGE STRUCTURE 

2.7.1 Message Assembly 


2.7.2 Business Information Entities Used

2.7.3 Code Lists Used 


  
 
 Categories  Description and Values