1 Nov., 2012 UNCEFACT
Requirements Specification Mapping (RSM) Business Domain: Travel/Tourism Business Process: Small scaled Lodging House Reservati...
Requirements Specification Mapping (RSM) Business Domain: Travel/Tourism Business Process: Small scaled Lodging House Reservation Information Process Title: TT&L Small scaled Lodging House Reservation Information Process Project UNCEFACT Forum: Sectoral
Version: 1.0 Release: R.12B Status: Draft
1
Reference Documents
UMM Meta Model Core Module (Candidate for 2.0) 2009-01-30
UMM Meta Model Foundation Module (Candidate for 2.0) 2009-01-30
Core Components Technical Specification-Part 8 of the ebXML Framework V2.01(15 Nov. 2003)
Updates of Class Diagram CCs Spreadsheet BIEs Spreadsheet Update of Class Diagrams Message Assembly added
Requirements Specification Mapping Table of Contents Reference Documents ..................................................................................................... 2 Change History .............................................................................................................. 3 Table of Contents ........................................................................................................... 4 1. Objective .................................................................................................................. 5 2. Definition of Terms .................................................................................................. 5 3. Target Technology Solution ..................................................................................... 5 4. Information Payload to be Implemented ................................................................. 5 4.1
Conceptual Data Model ........................................................................................ 5
4.2 Canonical Data Model ............................................................................................. 6 5. Business Information Entity Reference ................................................................... 6 6. Core Components Developed and their UN/CEFACT Registry Version Used......... 7 7. Logical Message Structure ...................................................................................... 7
4
1. Objective The objective of this document is to identify the complete set of the class diagrams to be used to transform the business requirements shown in the BRS (Small Scaled Lodging House Reservation Information Process 17 Oct., 2012) into the target technology solutions expressed in this document
2. Definition of Terms All terms are defined in the said BRS.
3. Target Technology Solution The target technology is XML schema and is based on UN/CEFACT Technical Specification Version 2.
4. Information Payload to be Implemented 4.1 Conceptual Data Model The class diagrams of Small scaled Lodging House Reservation Information Process are shown in the following figures. Figure 1 shows Lodging House Reservation Class in Lodging House Reservation Request and Response Message, and Figure 2 shows all the relevant classes in Lodging House Reservation Class.
Lodging House Reservation Request & Response Message
Specified
0..1
Specified
Lodging House_ Organization. Details
0..*
Designated
Reservation_ Requirement. Details
0..*
Lodging House_ Contact. Details Defined 0..1
Specified
1..*
Lodging House_ Resrvation. Details
Actual
0..1
Telephone
Lodging House_ Contract. Details
Identified
0..1
Lodging House_ Party. Details
5
0..*
Universal_ Communication. Details
Postal
0..*
Structured_ Address. Details
Figure 1 Class Diagram of Lodging House Reservation Class in Lodging House Reservation Request and Response Message
Lodging House_ Reservation. Details Message Type [1..1] Code Identification [0..1] Identifier Accepted [0..1] Date Time Status [0..1] Code Total Ｃｕｓｔｏｍｅr [0..1] Quantity Sales Policy Accepted [0..1] Indicator Property Confirmation [0..] Identifier Property Confirmation Issued [0..1] Date Time Cancellation [0..1] Identifier Cancellation Accepted [0..1] Date Time Description[0..1] Text
Specified
0..*
0..*
Lodging House_ Traveller. Details
Requested
0..1
Description [0.1] Text
Details
0..1
Submitted
0..*
Special_ Query. Details
Guest_ Person. Details
Transport Mode [0.1] Code Carrier Name [0.1] Text Carrier [0.1] Identifier Expected [0.1] Date Time Description [0.1] Text
Identification [0..1} Identifier Submitted [0..1] Date Time Submitting Person Name [0..1] Text Subject [0..1] Text
Identification [0..1] Identifier Name [0..1] Text Title [0..1] Text Gender [0..1] Code Birth [0..1] Date Time Language [0..1] Identifier Description [0..1] Text Passport [0..1] Identifier
Content [0..1] Text Latest_ Response [0..1] Date Time
0..*
Instruction [0..1] Identifier Received [0..1] Date Time Paid [0..1] Amount Tax [0..1] Amount Creation [0..1] Date Time Priority [0..1] Code Status [0..1] Code Reason [0..1] Code Due [0..1] Date Time Information [0..1} Text
Information Provided
Travel_ Guest Arrival. Details
Applicable
Travel_ Payment. Details
Name [0..1] Text Title [0..1] Text Language [0..1] Identifier Description [0..1] Text
Reservation Requested [0.1] Date Time Reservation Data Locator [0.1] Identifier Status [0.1] Code
Provided
0..*
Making
Reserving_ Person. Details
Category [0.1] Code
0..1
Lodging House_ Travel Product.
0..1
Used
Travel_ Sales Channel. Details
Sequence [0.1] Identifier Category [0.1] Code Reservation Status [0.1] Code Leader [0.1] Indicator Rooming [0.1] Text Description [0.1] Text
0..1
Identified
Condition [0..1] Text
Paid [0..1] Amount
Submitted
Query_ Response. Details
0..*
Actual [0..1] Date Time Status [0..1] Code Responding Person Name [0..1] Text
0..1
Held
Travel Product_ Reservation Item. Details
0..1
0..*
Specified
Travel Product_ Period. Details
Specified
0..*
Lodging House_ Travel Product Component. Details
Unit [0.1] Quantity Unit [0.1] Identifier Description [0.1]Text
Issuing Company Name [0..1] Text Description [0.1] Text
Face [0..1] Amount Type [0..1] Code Identification [0..1] Identifier Issue [0..1] Date Time Issuing Company Name [0..1] Text Description [0.1] Text
Daily_ Price. Details
Universal_ Communication. Details
Identified
Trade Sttlement_ Financial Card. Details
Charged
Type [0.1] Code Type [0.1] Text Charge [0.1] Date Time Basic_ Charge [0.1] Amount Extra_ Charge [0.1] Amount Discount_ Charge [0.1] Amount Customer Service Point [0.1] Quantity Service_ Charge [0.1] Amount Travel Product_ Tax_ Charge [0.1] Amount Commission_ Charge [0.1] Amount Tax_ Commission_ Charge [0.1] Amount Cancellation_ Charge [0..1] Amount Information [0.1] Text
Identified
0..*
Trade Settlement_ Payment Means. Details
Financial_ Guarantee. Details
0..*
Held
Travel_ Membership. Details Identificatio [0..1] Identifier Start [0..1] Date Time End [0..1] Date Time
0..*
Additional
Person_ Note. Details Subject [0..1] Text Content [0..1] Code Content [0..1] Text
Subject [0..1] Code
New ABIE Note:
Charged
Existing ABIE
Identification [0..1] Identifier Name [0..1] Text
Creation [0..1] Date Time
0..1
Basic_ Price. Details
0..*
0..*
Extra＿Price. Details
Discount_ Price. Details
0..1
Service_ Price. Details
0..*
Travel Product_ Tax. Details
Red letter
0..*
Added
Cancellation_ Price. Details
Figure 2 Class Diagram of Lodging House Reservation Class with its sub-classes.
4.2 Canonical Data Model The Canonical Data Model is the same as in the Conceptual Data Model.
5. Business Information Entity Reference All the business information entities developed for this process, including ABIEs, BBIEs, and ASBIEs, are shown in the file embedded in this chapter in the form of UN/CEFACT harmonization template.
SLHResrvationBIE2 0121101.xlsm
6
6. Core Components Developed and their UN/CEFACT Registry Version Used The Core Component Library version used in this document is D12A. All the core components developed for this process, including ACCs, BCCs, and ASCCs, are shown in the file embedded in this chapter in the form of UN/CEFACT harmonization template.
SLHReservationCC 20121101.xls
7. Logical Message Structure The Message Assembly is shown in the file embedded in this chapter, which is based upon the message structure for Lodging House Reservation Request and Response Message shown in Figure 1.
