1、 ATIS-0410002-0017 Unified Ordering Model (UOM) Volume II - Analysis For Access Service Ordering Guidelines (ASOG) Version 42 ATIS-0410002-0017 UOM-ASR Volume II Issued September 24, 2010 Issue 17 for ASOG v42 Page 2 The Alliance for Telecommunication Industry Solutions (ATIS) is the leading technic
2、al planning and standards development organization committed to the rapid development of global, market-driven standards for the information, entertainment and communications industry. More than 250 companies actively formulate standards in ATIS 18 Committees. In addition, numerous Incubators, Focus
3、 and Exploratory Groups address emerging industry priorities. For more information, please visit ATIS 0410002-0017 Unified Ordering Model (UOM) Volume II - Analysis Is an ATIS standard developed by the Ordering Solutions Committee/Access Service Ordering Subcommittee under the ATIS Ordering and Bill
4、ing Forum (OBF). Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2010 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an electronic ret
5、rieval system or otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. Notice of Disclaimer and Limitation of Liability The information provided in this document is directed solely
6、to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. ATIS-0410002
7、-0017 UOM-ASR Volume II Issued September 24, 2010 Issue 17 for ASOG v42 Page 3 NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTA
8、BILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY ATIS FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDE
9、NTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. ATIS-0410002-0017 UOM-ASR Volume II Issued September 24, 2010 Issue 17 for ASOG v42 Page 4 Change History Issue # Document Release Descript
10、ion of Changes 17 R1 Initial version for ASR 42 16 R1 Initial version for ASR 41 15 R1 Initial version for ASR 40 14 R1 Initial version for ASR 39 13 R1 Initial version for ASR 38 12 R1 Initial version for ASR 37 11 R1 Initial version for ASR 36 10 R1 Initial version for ASR 35 9 R1 Initial version
11、for ASR 34 8 R1 Initial version for ASR 33 7 R1 Initial version for ASR 32 6 R1 Initial version for ASR 31 5 R1 Initial version for ASR 30 4 R1 Initial version for ASR 29 3 R1 Initial version for ASR 28 2 R2 Minor changes to synch up with schema affecting the TQ form 2 R1 Initial version for ASR 27
12、1 R3 Final version of UOM-ASR Volume II for ASR 26 1 R2 Revisions to support synchronization with Volume III XML schema 1 R1 Base line version of UOM-ASR Volume II for ASR 26 SUMMARY OF CHANGES ASOG V42 Page 5 This issue of the Unified Ordering Model (UOM) Volume II Analysis provides the analysis an
13、d details to support the Access Service Ordering Guidelines (ASOG) and the Unified Ordering Model Volume I Business Requirements for Version 42. Changes to this document have been made in support of the following issues: 3386 The following issues went into Final Closure; however they resulted in no
14、impact to the contents of this document: 3336 (Withdrawn), 3378 (Withdrawn), 3379, 3388, 3389, 3390, 3391 Global Changes Change all ASOG 41 to ASOG 42; Version 41 to Version 42; Issue 16 to Issue 17 Change ATIS document number from ATIS-0410002-0016 to ATIS-0410002-0017 Update Issue Date Other gramm
15、atical and spelling corrections that do not impact the technical content of this document are not reflected in the Summary of Changes Table of Contents Updated to reflect new sections, re-numbered sections, and document re-pagination SUMMARY OF CHANGES ASOG V42 Page 6 UOM-ASR VOLUME II SUMMARY OF CH
16、ANGES FOR ASOG V42 Section Issue # Model Object Name Description of Change 6.4.1.2.5 3386 TRANSPORT Added new fields; IP_ADDRESS therefore UOM-ASR Volume III includes appropriate XML schemas related to unified ordering. This document does not specify a particular protocol as it is assumed that the t
17、rading partners will determine the appropriate transport protocol. It may be necessary to repeat the Design Phase when more than one implementation technology is selected. The OBF Ordering Solutions Committee/Access Service Ordering Subcommittee maintains UOM-ASR Volume III. UOM-ASR Volume IV - Impl
18、ementation This document includes implementation specifications that must be addressed before the system specifications can be realized using the selected implementation technology. In addition, a sample Joint Implementation Agreement (JIA) may be included as an appendix for trading partners to use
19、as a starting template. As with the Design Phase, the Implementation Phase may also have to be repeated in order to provide support for multiple technologies. The OBF Ordering Solutions ATIS-0410002-0017 UOM-ASR Volume II Issued September 24, 2010 Issue 17 for ASOG v42 Page 12 Committee maintains UO
20、M-ASR Volume IV Generic Implementation Guideline. Unified Model1. Business Requirements:-High Level Use Cases-Scenarios-Activity Diagrams-Data Element Definitions-Data/Presentation Requirements-Business Validation Rules2. Logical Analysis:-Informational Model-Behavioral Model-Sequence Diagrams-Class
21、/Object Diagrams-State Diagrams-Traceability Matrix3. Technical Standard:-Technology Specific- Interface Specification4. Implementation Guidelines-Design Choice Suggestions-Implementation ProfileOBF1. Business ProcessDefinition2. Analysis3. Design4. ImplementationProcessVolume IVolume IIVolume IIIVo
22、lume IVUOM Process and Document DevelopmentATIS-0410002-0017 UOM-ASR Volume II Issued September 24, 2010 Issue 17 for ASOG v42 Page 13 2. Introduction to UOM-ASR Volume II 2.1. Intended Audience The audience for this volume is the technical and software development staff of service providers and cus
23、tomers. The audience includes anyone who wishes to gain a better understanding of the interface between the customer and the provider in the provisioning of Access Services. 2.2. Purpose The document is intended to assist providers and customers in the process of conducting the analysis phase of the
24、ir development steps to realize an electronic, unified ordering system. 2.3. Scope UOM-ASR Volume II describes the detailed analysis of the informational and behavioral model within a Unified Ordering Model. In addition, it defines at a more detailed level of the business requirements and systems re
25、quirements needed to conduct ordering activities efficiently over an electronic interface. This includes a blending of the pre-ordering, service request and post-confirmation activities. Specifically, UOM-ASR Volume II-Analysis describes access service ordering as defined in UOM-ASR Volume I and the
26、 Access Service Ordering Guidelines (ASOG). Both of these sets of business requirements are developed and maintained within the Ordering and Billing Forum (OBF) under the auspices of the Ordering Solutions Committee/Access Service Ordering Subcommittee. Additionally, the Ordering Solutions Committee
27、/Access Service Ordering Subcommittee maintains several other requirement documents that have provided additional information into the development of UOM-ASR Volume II Analysis. UOM-ASR Volume II Analysis will contain both the Informational and Behavioral Models that provides the reader a broad unde
28、rstanding of Service Ordering. Specifically, each model provides a dimension to the overall process: Informational Model describes the data relationships. Behavioral Model describes the data as it acts with stimuli/events over time. ATIS-0410002-0017 UOM-ASR Volume II Issued September 24, 2010 Issue
29、 17 for ASOG v42 Page 14 Both the Informational and Behavioral Models are described using the Unified Modeling Language (UML). The UML provides the notation used within UOM-ASR Volume II. Because of the level of complexities inherent in such an electronic ordering model, unified modeling language to
30、ols (RationalRose and MyEclipse) have been used to develop this volume1. Note: A new UML tool has been chosen for updating class diagrams, starting with ASOG35. With the previous UML tool, one and only one associations displayed a 1 on the association line connecting classes. With this new tool, the
31、 1 is omitted. Any changed class diagrams (moving forward) will no longer display the 1. The absence of a multiplicity indicator on these association lines should be interpreted as one and only one multiplicity. 2.4. Development Note The UOM process is iterative in nature. Subsequent iterations of U
32、OM-ASR Volume II - Analysis may expand the functionality or services supported by the model. 1The use of RationalRose and MyEclipse does not reflect a tool recommendation by either the authors or the associated Industry Forums. ATIS-0410002-0017 UOM-ASR Volume II Issued September 24, 2010 Issue 17 f
33、or ASOG v42 Page 15 3. Overview of UOM-ASR Volume II 3.1. Assumptions of this Document UOM-ASR Volume II should be generic and not be technically or protocol specific. UOM-ASR Volume II Informational and Behavioral models reflect the current parameters defined within the OBF business rules. UOM-ASR
34、Volume II should be backward compatible, flexible, have reusability and add value. UOM-ASR Volume II is modeled using synchronous messaging; this is done simply for notation purposes, unless explicitly noted. The synchronous/asynchronous discussion may be revisited in UOM-ASR Volume III and UOM-ASR
35、Volume IV. Validation rules and processes are generally left to the customer/provider back end systems. System acknowledgements are not explicitly defined within the sequence diagrams. 3.2. Structure of Document This document is divided into these primary sections: i. Overview of the Standards Proce
36、ss and UOM Volumes ii. Summary of Business and System Requirements iii. Analysis of Requirement through Use Case Realizations iv. UOM Information Model using UML v. Behavior Analysis with States and Activities 3.3. Overall Process Description This version of UOM-ASR Volume II is based upon the busin
37、ess requirements defined with UOM-ASR Volume I and Access Service Request Ordering Guidelines for ASR Version 42. Together with additional support documentation, the analysis team developed the Informational and Behavioral Models. Key components of UOM-ASR Volume I are: Description of the business p
38、rocess through Use Cases. Definition of data elements and their associated data characteristics through a data dictionary. A functional data matrix that relates the data elements to particular inquiry/response functions. ATIS-0410002-0017 UOM-ASR Volume II Issued September 24, 2010 Issue 17 for ASOG
39、 v42 Page 16 3.4. UOM-ASR High Level Process Overview The UOM-ASR may be logically broken down into three logical stages: Pre-Order Service Request Post-Confirmation These stages define the high level processes necessary for ordering services and transmitting design information. Though it is not nec
40、essary to perform every function within each stage, it is beneficial to consider the creation, provisioning, and resolution of an order flowing through these stages. Service RequestPre-Order Post ConfirmationFigure 1 UOMASR Logical Stages (Use Case Packages) Within each of these stages, there are nu
41、merous business functions that may be initiated by the customer, the provider or both. Likewise, each business function may be further refined into a series of steps which require interaction between the customer and the provider. Therefore, it is beneficial to logically segment the control of these
42、 processes between customer and provider. At a high level, the functions may be grouped as follows: Pre-Order process Inquires/responses for Location Inquiry (LI), Service Availability Inquiry (SAI) and Connecting Facility Assignment Inquiry (CFAI). Service Request process - is defined for particula
43、r services which validate street address, CFA, NC/NCI/SECNCI combination or applicable ASOG edits, fatal error and non-fatal edits and other edits as determined by customer/provider negotiations. Process also includes Supplement, Confirmation, Clarification/Notification Request (C/NR). Post-Confirma
44、tion process - includes the functions that may take place after the customer has received a FOC. These functions may include Retrieve Service Request Information, Jeopardy ATIS-0410002-0017 UOM-ASR Volume II Issued September 24, 2010 Issue 17 for ASOG v42 Page 17 Notification, Design Layout Report (
45、DLR) and Completion Notification. The interaction between customer and provider may involve both required and optional processes, but the intent is to provide a well-defined and workable ordering and provisioning model. 4. UOM Requirements Summary 4.1. Business Requirements The Business Requirements
46、 for UOM-ASR Volume II Analysis, are defined in several documents that are maintained by the Ordering Solutions Committee/Access Service Ordering Subcommittee within the Ordering and Billing Forum (OBF). The documents are defined as: Unified Ordering Model Access Service Request (UOM-ASR Volume I).
47、This document describes the business requirements. This volume includes a high-level overview of the three primary processes in ordering: preordering, service request, and post confirmation activities. Through use cases and activity diagrams, UOM-ASR Volume I describes detailed interactions between
48、customer and provider. The appendices include a data dictionary, a functional data matrix, and a fatal error functional data matrix. This volume is focused on pre-ordering, ordering, and post confirmation for access services only. Access Service Ordering Guideline (ASOG). This document is broken up
49、into a series of practices. Each practice defines a logical grouping of data elements that may be utilized within the service ordering process. Design Layout Record Guidelines for Access Service (DLR). The DLR provides pertinent provider design information for a customer to review the design and ensure the providers ability to deliver the requested service. 4.2. System Requirements Additional system requirements are needed to support an implemented UOM interface. These requirements are in addition to the bus
