ATIS 0800052-2011 IIF Requirements Guidelines.pdf
《ATIS 0800052-2011 IIF Requirements Guidelines.pdf》由会员分享,可在线阅读,更多相关《ATIS 0800052-2011 IIF Requirements Guidelines.pdf(19页珍藏版)》请在麦多课文档分享上搜索。
1、 ATIS-0800052 IIF REQUIREMENTS GUIDELINES ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the information, entertainment and communications industry. More than 200 companies actively formulate sta
2、ndards in ATIS Committees, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, Billing and Operational Support, Emergency Services, Architectural Platforms and Emerging Networks. In addition, numerous Incubators, Focus and Explo
3、ratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Connected Vehicle, IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a member and majo
4、r U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). ATIS is accredited by the American National Standards Institute (ANSI). For more information, please visit . Notice of
5、Disclaimer for traceability it is always listed in the document but marked as deprecated. The requirement reference is always before any sentence with requirement language. The requirement reference is always in Bold type. 4.5.1 Requirement Reference Figure 1 shows the requirement reference structur
6、e. A period “.” is used to delimit the parameters. Figure 1: Requirement Numbering 4.5.1.1 Requirement Number Header The text “REQ” is used to indicate the requirement reference. REQ. Deprecated.KKKOptional deprecated notice and version/date when deprecatedDocument Version or Date if not initial rel
7、easeEnumerated Requirement NumberATIS Published Specification Number or WT number ATIS-0800052 6 4.5.1.2 Document Number The document number for published specifications is the ATIS document number. For working texts, it is the WT number (e.g., WT-104). 4.5.1.3 Version Number For initial release of
8、non-ANSI ATIS documents, this field is not included. For other than initial release of non-ANSI ATIS document, this field will be one of the following: Year of release for ANSI ATIS documents. Version of released ANSI documents (e.g., v002). Revision of working text (e.g., R33). 4.5.1.4 Requirements
9、 Number An enumerated number is assigned to each requirement. Once a document is released, these numbers are fixed to that requirement. For working text, the editor may choose to fix these numbers or modify them. It should be noted that Microsoft Word allows for simple enumeration using the SEQ fiel
10、d code. These can be converted to text by using the shortcut key. 4.5.1.5 Requirements Deprecation Notice If a requirement has been deprecated, only then is the deprecation notice added. This notice is enclosed within brackets, and contains the word “Deprecated” followed by a period and the version
11、of the document from which it was deprecated. 4.5.2 Released Documents The proposed requirement reference includes the version number of the released document that the requirement first appears. For example: REQ.0000000.1 The example device shall implement the example function. (Requirement originat
12、es in initial release of document.) REQ.0000000.v002.42 The example device shall implement a new example function. (Requirement originates in V002 of document.) 4.5.3 Working Texts If a requirement is added while the document is in working text, then the working text version is included, and will be
13、 modified when the ATIS document is released. For example: REQ.WT00.R1.43 The example device shall implement another new example function. (Requirement originates in WT00, R1). Contributions can contain the requirement number; however, it may be modified at the editors discretion, for example, if th
14、ere are conflicting requirement numbers between different contributions. If a requirement is removed from a working text that was not in a released document, then the requirement is deleted (e.g., not deprecated). 4.5.4 Deprecated Requirements Once a document has been released, requirements are neve
15、r deleted. Requirements that are no longer valid are deprecated and so noted. For example: ATIS-0800052 7 REQ.0000000.1Deprecated.v003 The example device shall implement the example function. This requirement has been deprecated. (Requirement originates in initial release of document, is deprecated
16、in v003 of released document.) 4.5.5 Normatively Edited Requirements If there is a desire to normatively edit a requirement, then the original requirement is deprecated and a new requirement is added. Explanatory text is added after both requirements. For example: REQ.0000000.1Deprecated.v003 The ex
17、ample device should implement the example function A. This requirement has been deprecated and replaced with requirement REQ.0000000.v003.100. (Requirement originates in initial release of document, is deprecated in v003 of released document and replaced with new requirement.) REQ.0000000.v003.100 T
18、he example device shall implement the example function A. This is an updated version of REQ.0000000.1. (New normatively edited requirement.) 4.5.6 Non-Normative Edited Requirements If there is a desire to editorially edit a requirement, for example due to spelling, then no change is made to the requ
19、irement reference. New text is included within brackets and removed text is indicated with strikethrough within brackets. If necessary, informative text of the change follows the requirement. If a single letter is modified, it is suggested that the entire word be updated for clarity. For example: RE
20、Q.0000000.1 The example device shall implamentimplement the example function. (Requirement originated in initial release of document, editorially changed in later release to fix misspelled word.) 4.6 Requirements Language 4.6.1 Types of Requirements There are four types of requirements: Mandatory Re
21、commended Optional Conditional-Mandatory Each type has different requirement language formats. 4.6.1.1 Mandatory A Mandatory Requirement is one that must be implemented in order to meet correct operation, certification, regulatory, and interoperability. The Mandatory Requirements are written so that
22、, within a single sentence, the word “shall” is present once in italics. An example is: REQ.0000000.24 The example device shall implement the DHCP protocols for IPV4 and IPV6. Mandatory requirements that state a conditional operation and the required function will use the word “When”. 4.6.1.2 Recomm
23、ended A Recommended Requirement is one that is recommended to be implemented but does not have to be implemented. Usually, this is because of planned future functions, perceived better operation, or some ATIS-0800052 8 other reason. Recommended Requirements are written so that, within a single sente
24、nce, the word “should” is present once in italics. An example is: REQ.0000000.25 The example device should implement the SNMP protocol. 4.6.1.3 Optional An Optional Requirement is one that is completely optional to be implemented. Test procedures are not required to test optional requirements but th
- 1.请仔细阅读文档,确保文档完整性,对于不预览、不比对内容而直接下载带来的问题本站不予受理。
- 2.下载的文档,不会出现我们的网址水印。
- 3、该文档所得收入(下载+内容+预览)归上传者、原创作者;如果您是本文档原作者,请点此认领!既往收益都归您。
下载文档到电脑,查找使用更方便
10000 积分 0人已下载
下载 | 加入VIP,交流精品资源 |
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- ATIS08000522011IIFREQUIREMENTSGUIDELINESPDF
