IEEE-1362-1998.pdf
《IEEE-1362-1998.pdf》由会员分享,可在线阅读,更多相关《IEEE-1362-1998.pdf(29页珍藏版)》请在三一文库上搜索。
1、 i IEEE Std 1362-1998 (Incorporates IEEE Std 1362a-1998) IEEE Guide for Information Technology System DenitionConcept of Operations (ConOps) Document Sponsor Software Engineering Standards Committee of the IEEE Computer Society Approved 19 March 1998 IEEE-SA Standards Board Abstract: The format and
2、contents of a concept of operations (ConOps) document are described. A ConOps is a user-oriented document that describes system characteristics for a proposed system from the users viewpoint. The ConOps document is used to communicate overall quantitative and qualitative system characteristics to th
3、e user, buyer, developer, and other organizational elements (for example, training, facilities, staffing, and maintenance). It is used to describe the user organization(s), mission(s), and organizational objectives from an integrated systems point of view. Keywords: buyer, characteristics, concept o
4、f operation, concepts of operations document, ConOps, developer, operational requirements, scenario, software-intensive system, software system, system, user, user requirements, viewpoint The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA C
5、opyright 1998 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 31 December 1998. Printed in the United States of America. Print: ISBN 0-7381-0185-2 SH94615 PDF: ISBN 0-7381-1407-3 SS94615 No part of this publication may be reproduced in any form, in an el
6、ectronic retrieval system or otherwise, without the prior written per- mission of the publisher. Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/28/2007 20:48:03 M
7、DTNo reproduction or networking permitted without license from IHS -,-,- ii IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Board. Members of the committees serve voluntarily and without compensation. They are not neces
8、sarily members of the Institute. The standards developed within IEEE represent a consensus of the broad expertise on the subject within the Institute as well as those activities outside of IEEE that have expressed an interest in participating in the development of the standard. Use of an IEEE Standa
9、rd is wholly voluntary. The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at the time a standard is approved an
10、d issued is subject to change brought about through developments in the state of the art and comments received from users of the standard. Every IEEE Standard is subjected to review at least every ve years for revision or reafrmation. When a document is more than ve years old and has not been reafrm
11、ed, it is reasonable to conclude that its contents, although still of some value, do not wholly reect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE Standard. Comments for revision of IEEE Standards are welcome from any intereste
12、d party, regardless of membership afliation with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they rela
13、te to specic applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standards represent a consensus of all concerned interests, it is important to ensure that any interpretation has also rec
14、eived the concurrence of a balance of interests. For this reason, IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant response to interpretation requests except in those cases where the matter has previously received formal consideration.Com
15、ments on standards and requests for interpretations should be addressed to: Secretary, IEEE Standards Board 445 Hoes LaneP.O. Box 1331 Piscataway, NJ 08855-1331 USA Authorization to photocopy portions of any individual standard for internal or personal use is granted by the Institute of Electrical a
16、nd Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. To arrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; (508) 750-8400. Permission to photocopy portions o
17、f any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. Note: Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no posit
18、ion is taken with respect to the existence or validity of any patent rights in connection therewith. The IEEE shall not be responsible for identifying patents for which a license may be required by an IEEE standard or for conducting inquiries into the legal validity or scope of those patents that ar
19、e brought to its attention. Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=OConnor, Maurice Not for Resale, 04/28/2007 20:48:03 MDTNo reproduction or networking permitted without license from IHS -,
20、-,- iii Introduction This introduction is not a part of IEEE Std 1362-1998, IEEE Guide for Information TechnologySystem DenitionConcept of Operations (ConOps) Document. Purpose This guide presents format and contents of a concept of operations (ConOps) document to be used when developing or modifyin
21、g a software-intensive system. A software-intensive system is a system for which software is a major technical challenge and is perhaps the major factor that affects system schedule, cost, and risk. In the most general case, a software-intensive system is comprised of hardware, software, people, and
22、 manual procedures. To make this guide more readable, the term system will be used to mean a software-intensive system that includes elements to be developed or modied, in addition to software. The term software system will be used to mean a software-intensive system in which software is the only co
23、mponent to be developed or modied. This guide does not specify the exact techniques to be used in developing the ConOps document, but it does provide approaches that might be used. Each organization that uses this guide should develop a set of practices and procedures to provide detailed guidance fo
24、r preparing and updating ConOps documents. These detailed practices and procedures should take into account the environmental, organizational, and political factors that inuence application of the guide. The heart of the ConOps described in this guide is contained in Clauses 3 through 5. Clause 3 de
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- IEEE 1362 1998
链接地址:https://www.31doc.com/p-3769594.html