Ieee Std1362-98

IEEE Std 1362-1998
(Incorporates IEEE Std 1362a-1998)

IEEE Guide for Information TechnologyÑ System DeÞnitionÑConcept 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 contents of a concept of operations (ConOps) document are described. A ConOps is auser-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 the 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 of 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, NewYork, NY 10017-2394, USA Copyright © 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: PDF: ISBN 0-7381-0185-2 ISBN 0-7381-1407-3 SH94615 SS94615

No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior writtenpermission of the publisher.

i

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 necessarily members of the Institute. The standards developed within IEEE represent a consensus of the broad expertise on the subject within theInstitute 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 Standard 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, theviewpoint expressed at the time a standard is approved and 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 reafÞrmation. When a document is more than Þve years old and has not been reafÞrmed, it is reasonable to conclude that itscontents, although still of some value, do not wholly reßect 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 interested party, regardless of membership afÞliation with IEEE. Suggestions for changes in documents should be in the form of a proposed change oftext, together with appropriate supporting comments. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to speciÞc 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 received 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.Comments on standards and requests for...