IEEE 1233-1998 en Guide for Developing System Requirements Specifications (Includes 1233-1996 and 1233a-1998 IEEE Computer Society Document)《系统要求规范编制指南》.pdf

《IEEE 1233-1998 en Guide for Developing System Requirements Specifications (Includes 1233-1996 and 1233a-1998 IEEE Computer Society Document)《系统要求规范编制指南》.pdf》由会员分享，可在线阅读，更多相关《IEEE 1233-1998 en Guide for Developing System Requirements Specifications (Includes 1233-1996 and 1233a-1998 IEEE Computer Society Document)《系统要求规范编制指南》.pdf（36页珍藏版）》请在麦多课文档分享上搜索。

1、 The Institute of Electrical and Electronics Engineers, Inc.345 East 47th Street, New York, NY 10017-2394, USACopyright 1998 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 22 December 1998. Printed in the United States of America.Print:ISBN 0-7381-0337-3

2、 SH94659PDF:ISBN 0-7381-1515-0 SS94659No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher.IEEE Std 1233, 1998 Edition(R2002)(Includes IEEE Std 1233-1996and IEEE Std 1233a-1998)IEEE Guide for

3、Developing System Requirements SpecificationsSponsorSoftware Engineering Standards Committeeof theIEEE Computer SocietyIEEE Std 1233-1996 Reaffirmed 11 September 2002IEEE Std 1233-1996 Approved 17 April 1996IEEE Std 1233a-1998 Approved 8 December 1998by theIEEE-SA Standards BoardAbstract:Guidance fo

4、r the development of the set of requirements, System Requirements Speci-fication (SyRS), that will satisfy an expressed need is provided. Developing an SyRS includes theidentification, organization, presentation, and modification of the requirements. Also addressed arethe conditions for incorporatin

5、g operational concepts, design constraints, and design configurationrequirements into the specification. This guide also covers the necessary characteristics and qual-ities of individual requirements and the set of all requirements.Keywords:requirement, SyRS, system, system requirements specificatio

6、nIEEE Standardsdocuments are developed within the IEEE Societies and the Standards Coordinat-ing Committees of the IEEE Standards Association (IEEE-SA) Standards Board. Members of thecommittees serve voluntarily and without compensation. They are not necessarily members of theInstitute. The standard

7、s developed within IEEE represent a consensus of the broad expertise on thesubject within the Institute as well as those activities outside of IEEE that have expressed an inter-est in participating in the development of the standard.Use of an IEEE Standard is wholly voluntary. The existence of an IE

8、EE Standard does not implythat there are no other ways to produce, test, measure, purchase, market, or provide other goods andservices related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at thetime a standard is approved and issued is subject to change brought about throu

9、gh developments inthe state of the art and comments received from users of the standard. Every IEEE Standard is sub-jected to review at least every five years for revision or reaffirmation. When a document is morethan five years old and has not been reaffirmed, it is reasonable to conclude that its

10、contents,although still of some value, do not wholly reflect the present state of the art. Users are cautioned tocheck 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 ofmembership affiliatio

11、n with IEEE. Suggestions for changes in documents should be in the form of aproposed change of text, together with appropriate supporting comments.Interpretations: Occasionally questions may arise regarding the meaning of portions of standards asthey relate to specific applications. When the need fo

12、r interpretations is brought to the attention ofIEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standards rep-resent a consensus of all concerned interests, it is important to ensure that any interpretation hasalso received the concurrence of a balance of intere

13、sts. For this reason, IEEE and the members of itssocieties and Standards Coordinating Committees are not able to provide an instant response tointerpretation requests except in those cases where the matter has previously received formalconsideration. Comments on standards and requests for interpreta

14、tions should be addressed to:Secretary, IEEE-SA Standards Board445 Hoes LaneP.O. Box 1331Piscataway, NJ 08855-1331USAAuthorization to photocopy portions of any individual standard for internal or personal use isgranted by the Institute of Electrical and Electronics Engineers, Inc., provided that the

15、 appropriatefee is paid to Copyright Clearance Center. To arrange for payment of licensing fee, please contactCopyright Clearance Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA;(978) 750-8400. Permission to photocopy portions of any individual standard for educational class-room

16、 use can also be obtained through the Copyright Clearance Center.Note: Attention is called to the possibility that implementation of this standard mayrequire use of subject matter covered by patent rights. By publication of this standard,no position is taken with respect to the existence or validity

17、 of any patent rights inconnection therewith. The IEEE shall not be responsible for identifying patents forwhich a license may be required by an IEEE standard or for conducting inquiries intothe legal validity or scope of those patents that are brought to its attention.Copyright 1998 IEEE. All right

18、s reserved.iiiIntroduction(This introduction is not a part of IEEE Std 1233, 1998 Edition, IEEE Guide for Developing System Requirements Spec-ifications.)The purpose of this guide is to provide guidance for capturing system requirements. This guide serves theanalyst by providing a clear definition f

19、or identifying well-formed requirements and ways of organizingthem.This guide should be used to help the analyst capture requirements at the beginning of the system require-ments phase. It should be used to clarify what constitutes a good requirement and provide an understandingof where to look to i

20、dentify different requirement sources.The readers of this guide are referred to Annex C for guidelines for using this guide to meet the requirementsof IEEE/EIA 12207.1-1997, IEEE/EIA Guide for Information TechnologySoftware life cycle processesLife cycle data.ParticipantsIEEE Std 1233-1996 was prepa

21、red by a working group chartered by the Software Engineering Committee ofthe IEEE Computer Society. At the time it was approved, the working group consisted of the followingmembers:Louis E. Miller,ChairWilliam N. Sabor,SecretaryOther contributors includedThe following persons balloted IEEE Std 1233-

22、1996:Bakul BanerjeeDavid ByrchKim A. CadyLarry DiehrCharles A. DrozLarry C. ForrestP. Michael GubaJames R. HughesJoe IaquintoMarybeth A. JupinaThomas M. KuriharaRichard C. LeeJim LongbuccoDonald F. ParsonsEric PetersonJohn ShecklerJess ThompsonEva D. WilliamsGeoff CozensPaul DavisKristin DittmannChr

23、istof EbertDon McCashVirginia NuckollsAnne ONeillH. Ronald BerlackMark BilgerWilliam J. BollFletcher BuckleyEdward R. ByrneFranois CoallierChristopher CookeGeoff CozensAlan M. DavisRobert E. DwyerSherman EaglesLeo G. EganCaroline L. EvansRichard L. EvansJohn W. FendrichPeter FilleryLarry ForrestEuge

24、ne P. FriedmanEitan FroumineYair GershkovitchAdel N. GhannamJulio Gonzalez-SanzPatrick J. GriffinDavid A. GustavsonJohn HarauzDerek J. HatleyWilliam HefleyUmesh P. HiriyannaiahJody HowardEiichi KanekoJerry KickensonJanet KintnerThomas M. KuriharaRenee LambJohn B. LaneBoniface LauJ. Dennis LawrenceBe

25、n LivsonHarold MainsRoger MartinJames W. McCleanSue McGrathLouis E. MillerDennis E. NickleIndradeb P. PalJoseph A. PalermoStephen R. SchachNorman SchneidewindWolf A. SchnoegeGregory D. SchumacherCarl S. SeddioDavid M. SiefertRichard S. SkyAlfred R. SorkowitzivCopyright 1998 IEEE. All rights reserved

26、.IEEE Std 1233a-1998 was prepared by the Life Cycle Data Harmonization Working Group of the SoftwareEngineering Standards Committee of the IEEE Computer Society. At the time it was approved, the workinggroup consisted of the following members:Leonard L. Tripp,ChairThe following persons balloted IEEE

27、 Std 1233a-1998:Robert N. SulgroveTanehiro TatsutaRichard H. ThayerGeorge D. TiceLeonard L. TrippTom VaiskunasThomas E. VollmanRonald L. WadeDolores WallaceWilliam M. WalshPaul R. WorkJanusz ZalewskiEdward ByrnePaul R. CrollPerry DeWeeseRobin FralickMarilyn Ginsberg-FinnerJohn HarauzMark HenleyDenni

28、s LawrenceDavid MaiborRay MilovanovicJames MooreTimothy NiesenDennis RillingTerry RoutRichard SchmidtNorman F. SchneidewindDavid SchultzBasil SherlundPeter VoldnerRonald WadeSyed AliRobert E. BarryLeo BeltracchiH. Ronald BerlackRichard E. BiehlMichael A. BlackledgeSandro BolognaKathleen L. BriggsM.

29、Scott BuckMichael CaldwellJames E. CardowEnrico A. CarraraAntonio M. CicuTheo ClarkeSylvain ClermontRosemary ColemanVirgil Lee CooperW. W. Geoff CozensPaul R. CrollGregory T. DaichGeoffrey DarntonTaz DaughtreyBostjan K. DergancPerry R. DeWeeseEvelyn S. DowCarl Einar DragstedtSherman EaglesChristof E

30、bertLeo EganRichard E. FairleyJohn W. FendrichJay ForsterKirby FortenberryEva FreundBarry L. GarnerMarilyn Ginsberg-FinnerJohn Garth GlynnJulio Gonzalez-SanzL. M. GuntherDavid A. GustafsonJon D. HagarJohn HarauzHerbert HechtWilliam HefleyMark HeinrichDebra HerrmannJohn W. HorchJerry HullerPeter L. H

31、ungGeorge JackelenFrank V. JorgensenVladan V. JovanovicWilliam S. JunkGeorge X. KambicRon S. KenettJudith S. KernerRobert J. KierzykThomas M. KuriharaJohn B. LaneJ. Dennis LawrenceRandal LeavittFang Ching LimJohn LordStan MageeHarold MainsRobert A. MartinTomoo MatsubaraPatrick D. McCrayBret MichaelA

32、lan MillerJames W. MoorePavol NavratAlex PolackPeter T. PoonLawrence S. PrzybylskiKenneth R. PtackAnnette D. ReillyDennis RillingHelmut SandmayrStephen R. SchachNorman SchneidewindDavid J. SchultzLisa A. SelmonRobert W. ShillatoDavid M. SiefertCarl A. SingerRichard S. SkyAlfred R. SorkowitzDonald W.

33、 SovaLuca SpotornoJulia StesneyFred J. StraussToru TakeshitaRichard H. ThayerBooker ThomasPatricia TrellueLeonard L. TrippTheodore J. UrbanowiczGlenn D. VenablesUdo VogesDavid D. WaldenDolores WallaceWilliam M. WalshJohn W. WalzScott A. WhitmireP. A. WolfgangPaul R. WorkNatalie C. YopconkaJanusz Zal

34、ewskiGeraldine ZimmermanPeter F. ZollCopyright 1998 IEEE. All rights reserved.vWhen the IEEE-SA Standards Board approved IEEE Std 1233a-1998 on 8 December 1998, it had thefollowing membership:Richard J. Holleman,ChairDonald N. Heirman,Vice ChairJudith Gorman,Secretary*Member EmeritusValerie E. Zelen

35、tyIEEE Standards Project EditorSatish K. AggarwalClyde R. CampJames T. CarloGary R. EngmannHarold E. EpsteinJay Forster*Thomas F. GarrityRuben D. GarzonJames H. GurneyJim D. IsaakLowell G. JohnsonRobert KennellyE. G. “Al” KienerJoseph L. Koepfinger*Stephen R. LambertJim LogothetisDonald C. LoughryL.

36、 Bruce McClungLouis-Franois PauRonald C. PetersenGerald H. PetersonJohn B. PoseyGary S. RobinsonHans E. WeinrichDonald W. ZipseviCopyright 1998 IEEE. All rights reserved.Contents1. Overview 11.1 Scope 12. References 13. Definitions 24. System requirements specification 44.1 Definition . 44.2 Propert

37、ies . 44.3 Purpose. 54.4 Intended use . 64.5 Benefits 64.6 Dynamics of system requirements. 75. SyRS development process overview 75.1 Customer 75.2 Environment. 85.3 Technical community. 106. Well-formed requirements. 116.1 Definition of a well-formed requirement. 116.2 Properties of a requirement

38、126.3 Categorization 136.4 Pitfalls 147. SyRS development. 157.1 Identify requirements. 157.2 Build a well-formed requirement. 177.3 Organize requirements. 187.4 Present requirements 19Annex A (informative) System Requirements Specification outline 20Annex B (informative) Bibliography 24Annex C (inf

39、ormative) Guidelines for compliance with IEEE/EIA 12207.1-1997 25Copyright 1998 IEEE. All rights reserved.1IEEE Guide for Developing System Requirements Specications1. Overview1.1 ScopeThis guide provides guidance for the development of a set of requirements that, when realized, will satisfyan expre

40、ssed need. In this guide that set of requirements will be called the System Requirements Specica-tion (SyRS). Developing an SyRS includes the identication, organization, presentation, and modication ofthe requirements. This guide addresses conditions for incorporating operational concepts, design co

41、nstraints,and design conguration requirements into the specication. This guide also addresses the necessary charac-teristics and qualities of individual requirements and the set of all requirements.This guide does not specify industry-wide system specication standards nor state a mandatory SystemReq

42、uirements Specication. This guide is written under the premise that the current state of the art of systemdevelopment does not warrant or support a formal standards document.2. ReferencesThis guide shall be used in conjunction with the following publications:IEEE Std 100-1996, IEEE Standard Dictiona

43、ry of Electrical and Electronics Terms.1IEEE Std 610.12-1990, IEEE Standard Glossary of Software Engineering Terminology.IEEE Std 730-1998, IEEE Standard for Software Quality Assurance Plans.IEEE Std 828-1998, IEEE Standard for Software Conguration Management Plans.IEEE Std 830-1998, IEEE Recommende

44、d Practice for Software Requirements Specications.IEEE Std 1074-1997, IEEE Standard for Developing Software Life Cycle Processes.1IEEE publications are available from the Institute of Electrical and Electronics Engineers, 445 Hoes Lane, P.O. Box 1331, Piscataway,NJ 08855-1331, USA (http:/www.standar

45、ds.ieee.org/).IEEEStd 1233, 1998 Edition IEEE GUIDE FOR2Copyright 1998 IEEE. All rights reserved.IEEE Std 1220-1998, IEEE Standard for Application and Management of the Systems Engineering Process.ISO 9000-1: 1994, Quality management and quality assurance standardsPart 1: Guidelines for selectionand

46、 use.2ISO 9126: 1991, Information technologySoftware product evaluationQuality characteristics and guide-lines for their use.MIL-STD-490A, Specication Practices.3MIL-STD-498, Software Development and Documentation.3. DenitionsThe denitions listed below establish meaning in the context of this guide.

47、 Terms not dened in this guideare included in IEEE Std 610.12-1990.43.1 analyst:A member of the technical community (such as a systems engineer or business analyst, develop-ing the system requirements) who is skilled and trained to dene problems and to analyze, develop, andexpress algorithms.3.2 ann

48、otation:Further documentation accompanying a requirement such as background information and/or descriptive material.3.3 baseline:A specication or system that has been formally reviewed and agreed upon, that thereafterserves as the basis for further development and can be changed only through formal

49、change control proce-dures. (IEEE Std 610.12-1990)3.4 constraint:A statement that expresses measurable bounds for an element or function of the system. Thatis, a constraint is a factor that is imposed on the solution by force or compulsion and may limit or modify thedesign changes.3.5 customer(s):The entity or entities for whom the requirements are to be satised in the system beingdened and developed. This can be an end-user of the completed system, an organization within the samecompany as the developing organization (e.g., System Management), a compan