1、 ATIS-0404110-0022 Unified Ordering Model - Access Service Request (UOM-ASR) Volume I Business Requirements For An Electronic Ordering Interface ATIS-0404110-0022 UOM-ASR Volume IIssued March 29, 2013 Implemented September 21, 2013 As a leading technology and solutions development organization, ATIS
2、 brings together the top global ICT companies to advance the industrys most-pressing business priorities. Through ATIS committees and forums, nearly 200 companies address cloud services, device solutions, M2M communications, cyber security, ehealth, network evolution, quality of service, billing sup
3、port, operations and more. These priorities follow a fast-track development lifecyclefrom design and innovation through solutions that include standards, specifications, requirements, business use cases, software toolkits and interoperability testing. ATIS is accredited by the American National Stan
4、dards Institute (ANSI). ATIS is the North American Organizational Partner for the 3rdGeneration Partnership Project (3GPP), a founding Partner of oneM2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications sectors, and a member of the I
5、nter-American Telecommunication Commission (CITEL). For more information, visit www.atis.org. ATIS 0404110-0022 Unified Ordering Model - Access Service Request (UOM-ASR) Business Requirements for an Electronic Ordering Interface Is an ATIS standard developed by the Ordering Solutions Committee - Acc
6、ess Service Ordering Subcommittee under the ATIS Ordering and Billing Forum (OBF) Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2013 by the Alliance for Telecommunications Industry Solutions, Inc. All rights reserved. No p
7、art of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Limited Exception for “Customized” Forms. In recognition of the business nee
8、ds and processes implemented by companies throughout the industry, ATIS grants the following limited exception to the copyright policy. The forms contained within, once “Customized,” may be reproduced, distributed and used by an individual or company provided that the following is placed on all “Cus
9、tomized” forms: ATIS-0404110-0022 UOM-ASR Volume I Issued March 29, 2013 Implemented September 21, 2013 ii “This form/screen is based upon the Ordering and Billing Forums (OBF) industry consensus approved guidelines, found in the Access Service Ordering Guidelines (ASOG) document. The ASOG may be ob
10、tained by contacting the Alliance for Telecommunications Industry Solutions (ATIS) at 1-800-387-2199 or: http:/www.atis.org/docstore/default.aspx.” For purposes of this limited exception, the term “Customized” means, the modification, by a company, of an ASOG form to be issued to a trading partner t
11、o make it company specific by, for example, adding a company logo, graying-out optional fields not required by that specific issuing company, and converting into an electronic format/screen. This limited exception does not affect the ASOG document itself which remains copyrighted and may not be repr
12、oduced in whole or part. Telcordia Technologies, Inc. was formerly known as Bell Communications Research, Inc. or Bellcore. Portions of this document, previously published by Bellcore, may still reflect the former name as it was embedded in the documentation under a prior license from the owners of
13、the BELL trademark, which license has now expired. The use of this name does not suggest that Telcordia Technologies has licensed the names BELL, Bell Communications Research, or Bellcore for new uses or that the owners of the BELL trademark sponsor, endorse or are affiliated with Telcordia Technolo
14、gies or its products. Printed in the United States of America. Notice of Disclaimer and Limitation of Liability The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with gene
15、rally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. ATIS-0404110-0022 UOM-ASR Volume I Issued March 29, 2013 Implemented September 21, 2013 iii NO REPRESENTATION OR WARRANTY IS MADE THAT THE
16、INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE
17、, 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 INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DO
18、CUMENT IS AT THE RISK OF THE USER. ATIS-0404110-0022 UOM-ASR Volume I Issued March 29, 2013 Implemented September 21, 2013 iv THIS PAGE INTENTIONALLY LEFT BLANK.UOM-ASR VOLUME I ASOG V47 SYNOPSIS OF CHANGES Page 1 of 3 UOM-ASR VOLUME I ASOG V47 DRAFT CHANGES - ISSUES INCLUDED IN THIS SYNOPSIS ISSUE
19、NUMBER DESCRIPTION UOM-ASR VOLUME I ASOG V47 SYNOPSIS OF CHANGES Page 2 of 3 The following table depicts the type of change category definitions: TYPE OF CHANGE = CATEGORY DEFINITIONS NEW = Adding a new field REM = Removing an existing field FN = Field/Tag name change (e.g., EXEMPT REASON changed to
20、 ER) FORMAT = Field format change (e.g., moved to another section of the form, etc.) DEF = Definition change DEFN = Definition notes addition, change, deletion VE = Valid entries addition, change, deletion VEN = Valid entry notes addition, change, deletion USE = Usage statement change USEN = Usage n
21、otes addition, change, deletion DC = Data characteristics change (e.g., change from numeric to alpha/numeric) DCL = Data characteristics length change DCN = Data characteristics note addition, change, deletion EX = Example addition, change, deletion EXN = Example notes addition, change, deletion FOR
22、M = Changes made to the ASR forms (i.e., additions, rearrangements, field length changes or deletions of fields) GLOSSARY = Identifies changes within the glossary sections (i.e., additions or deletions of fields) TEXT = Identifies changes within the text of a section (i.e., additions or deletions of
23、 fields) UOM-ASR VOLUME I ASOG V47 SYNOPSIS OF CHANGES Page 3 of 3 SYNOPSIS OF CHANGES PRAC # ISSUE # Field/ Section Type Of Change Description of Change Field Length UOM Vol 1 UOM Vol 1 UOM Vol 1 UOM Vol 1 UOM Vol 1 UOM Vol 1 UOM Vol 1 UOM Vol 1 UOM Vol 1 NOTES: ATIS-0404110-0022 UOM-ASR Volume I I
24、ssued March 29, 2013 Implemented September 21, 2013 TABLE OF CONTENTS SECTION PAGE I. Introduction to UOM . 1 II. The UML Introduction . 3 A. Introduction . 3 III. UOM-ASR . 3 A. UOM-ASR Business Requirements Process . 6 IV. UOM-ASR High Level Process Overview 7 A. Pre-Order Inquiry and End-to-End S
25、ervice Request Process . 10 V. Introduction to UOM ASR Process Steps . 11 A. UOM - ASR Pre-Ordering Activities 12 B. UOM - ASR Service Request Placement Activities 13 C. UOM - ASR Post-Confirmation Notice Activities 14 VI. UOM - ASR Use Cases: High Level Overview . 21 A. UOM ASR Actors . 21 B. High
26、Level Overview of the UOM ASR Process Use Cases . 22 VII. UOM - ASR Pre-Ordering Use Cases 23 A. Pre-order Use Case: Location Inquiry . 24 B. Pre-Order Use Case: Service Availability Inquiry 25 C. Pre-Order Use Case: CFA Inquiry . 27 VIII. UOM - ASR Service Request Process Use Cases 28 A. UOM ASR Se
27、rvice Request Process: Service Request Placement/Pre-Validation Use Case 30 B. UOM - ASR Service Request Process - Service Request Supplement Use Case 35 C. UOM ASR Service Request Placement - Confirmation Notice Use Case . 36 IX. UOM - ASR Service Request Process Post-Confirmation Use Cases . 37 A.
28、 UOM - ASR Post-Confirmation Jeopardy Status Use Case . 38 B. UOM - ASR Post-Confirmation Retrieve Service Request Information Use Cases . 41 C. UOM - ASR Post-Confirmation Completion Notification Use Case 43 ATIS-0404110-0022 UOM-ASR Volume I Issued March 29, 2013 Implemented September 21, 2013 ii
29、D. UOM - ASR Design Layout Report Use Case . 44 X. Appendix A: UML Introduction 45 A. Scope 45 B. Use Case(s) 45 C. Actors 46 D. Use Case . 46 E. Use Case Diagrams 48 F. Use Case Techniques . 51 G. Tips for Actors 53 H. Tips for Primary Use Cases 54 I. Tips for Use Case Scenarios . 54 J. Tips for Us
30、e Case Relationships . 55 K. Sequence Diagrams . 55 L. State Diagrams . 57 M. Activity Diagrams . 58 XI. Appendix B: UOM - ASR Data Dictionary . 63 XII. Appendix C: UOM - ASR Functional Data Matrix . 85 XIII. Appendix D: UOM - ASR Fatal Error Functional Data Matrix . 102 XIV. Appendix E: Unified Ord
31、ering - ASR Service Packages . 110 XV. Bibliography 117 ATIS-0404110-0022 UOM-ASR Volume I Issued March 29, 2013 Implemented September 21, 2013 iii TABLE OF FIGURES Figure 1 UOM ASR Process and Document Development 2 Figure 2 Access Ordering Relationships and Deliverables 5 Figure 3 UOM ASR Logical
32、Stages . 7 Figure 4 UOM ASR Business Functions 9 Figure 5 UOM ASR Pre-Ordering Activities 12 Figure 6 UOM ASR Service Request Placement Activities . 13 Figure 7 UOM ASR Post- Confirmation Activities . 14 Figure 8 UOM ASR Provider Jeopardy Activities 15 Figure 9 UOM ASR Customer Jeopardy Activities 1
33、6 Figure 10 UOM ASR Customer Retrieve Service Request Information Activities . 17 Figure 11 UOM ASR Provider Retrieve Service Request Information Activities . 18 Figure 12 UOM ASR Completion Notification Activities 19 Figure 13 UOM ASR Process Business Requirement Use Cases . 22 Figure 14 UOM ASR Pr
34、e-Ordering Business Requirement Use Cases 23 Figure 15 UOM ASR Perform Location Inquiry Use Case . 24 Figure 16 UOM ASR Perform Service Availability Inquiry Use Case . 26 Figure 17 UOM ASR Perform CFA Inquiry Use Case 27 Figure 18 UOM ASR Service Request Process Business Requirement Use Case . 29 Fi
35、gure 19 UOM ASR Perform Service Request Placement/Pre-Validation Use Case . 31 Figure 20 UOM ASR Perform Fatal Error Processing Use Case 32 Figure 21 UOM ASR Perform Non-Fatal Error Processing Use Case . 33 Figure 22 UOM ASR Perform Clarification Request Use Case 34 Figure 23 UOM ASR Perform Service
36、 Request Supplement Use Case . 35 Figure 24 UOM ASR Perform Confirmation Notice Use Case 36 Figure 25 UOM ASR Post-Confirmation Business Requirements Use Case 37 Figure 26 UOM ASR Perform Provider Jeopardy Status Use Case 38 Figure 27 UOM ASR Perform Provider Jeopardy Clear Use Case 39 Figure 28 UOM
37、 ASR Perform Customer Jeopardy Status Use Case . 39 Figure 29 UOM ASR Perform Customer Jeopardy Status Clear . 40 Figure 30 UOM ASR Perform Customer Jeopardy Status Clear . 40 Figure 31 UOM ASR Perform Customer Retrieve Service Request Information Use Case 41 Figure 32 UOM ASR Perform Provider Retri
38、eve Service Request Information Use Case 42 Figure 33 UOM ASR Perform Completion Use Case . 43 Figure 34 UOM ASR Design Layout Report Use Case 44 Figure 35 Use Case Diagram . 48 Figure 36 Use Case Example . 50 Figure 37 Sequence Diagram . 56 Figure 38 State Diagram . 57 Figure 39 Activity Diagram No
39、 Branching . 60 Figure 40 Activity Diagram With Branching 61 Figure 41 Activity Diagram With Decision Box 61 Figure 42 Activity Diagram Concurrent Paths . 62 ATIS-0404110-0022 UOM-ASR Volume I Issued March 29, 2013 Implemented September 21, 2013 iv THIS PAGE INTENTIONALLY LEFT BLANK.ATIS-0404110-002
40、2 UOM-ASR Volume I Issued March 29, 2013 Implemented September 21, 2013 1 I. Introduction to UOM The intent of Unified Ordering Model (UOM) is to develop a complete set of system documentation using an end-to-end structured methodology. The scope of UOM encompasses business requirements, analysis, d
41、esign and implementation. Logically, these components are defined within the UOM in four volumes. UOM-ASR Volume I Provides an explanation of the business requirements and a conceptual overview of the solution. This conceptual overview is high-level. It defines “what” the user initially sees as the
42、problem and “how” the user sees the business solution. UOM Volume II Analysis may be seen as using the requirements and developing a more detailed understanding of the scope. In effect, this step defines “what” the proposed technical resolution needs to support. It is a logical view of the proposed
43、solution, which meets the business need, and it is not based on any particular software protocol. UOM Volume III The logical view of the proposed resolution (model), created in the Analysis Phase, is translated into the language appropriate for the selected implementation technology. Design focuses
44、on “how” the implementation shall resolve the business requirements. It may be necessary to repeat the Design Phase if more than one implementation technology is selected. UOM Volume IV Resolves any outstanding implementation specifications that must be addressed before the system specifications can
45、 be realized using the selected implementation technology. As with the Design Phase, the Implementation Phase may also have to be repeated in order to provide support for multiple technologies. ATIS-0404110-0022 UOM-ASR Volume I Issued March 29, 2013 Implemented September 21, 2013 2 UOM - ASR Proces
46、s and Document Development Process2. AnalysisUnified Model2. Logical Model- Class/Object Diagrams- Data Traceablity- Interaction Diagrams- State DiagramsVolume 2Volume 3Volume 43. Design3. Information Model- Technology Information Model4. Implementation4. Implementation Guidelines- Technology Specif
47、ications- Implementation Profile1. Business Process. Definition1. Business Requirements- High Level Use Cases- Data/Presentation Requirement- Business Validation Rules- Scenarios- Activity DiagramsVolume 1Figure 1 UOM ASR Process and Document Development ATIS-0404110-0022 UOM-ASR Volume I Issued Mar
48、ch 29, 2013 Implemented September 21, 2013 3 II. The UML Introduction A. Introduction By definition a model is an abstraction. The Unified Modeling Language (UML) is the “visual” notation used within UOM Volume I. The UML supports several constructs that provide a consistent notation used to describ
49、e the UOM. The use of UML is for descriptive purposes. In some instances this Volume may not strictly adhere to existing UML specifications. The UML is graphical in nature and is sometimes referred to as a visual specification language. The use of graphics helps in a) abstracting design features and b) showing the relationships between design elements. The UML should be used to document all the relevant re
