1、 SH94620ISBN 0-7381-0190-7Copyright 1998 by the Institute of Electrical and Electronics Engineers, Inc. (IEEE)The IEEE hereby grants a non-exclusive license to reproduce and distribute theinformation contained on pages i through v without charge.IEEE Std 1462-1998(Adoption of International Standard
2、ISO/IEC 14102: 1995)Information technologyGuideline for the evaluation and selection of CASE toolsSponsorSoftware Engineering Standards Committeeof theIEEE Computer SocietyAdopted 19 March 1998 by IEEE-SA Standards BoardAbstract: IEEE Std 1462-1998 is an adoption of International Standard ISO/IEC 14
3、102: 1995. TheInternational Standard deals with the evaluation and selection of CASE tools, covering a partial orfull portion of the software engineering life cycle. The adoption of the International Standard by IEEEincludes an implementation note, which explains terminology differences, identifies
4、related IEEEstandards, and provides interpretation of the International Standard.Keywords:CASE tools, computer-aided software engineering, computer applications, computersoftware, software engineeringTMIEEE Std 1462-1998(R2004)Reaffirmed 8 December 2004IEEE Standardsdocuments are developed within th
5、e 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 standards developed within IEEE represent a consensus of
6、 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 IEEE Standard does not implythat there are no othe
7、r 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 through developments inthe state of the art and comme
8、nts 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 contents,although still of some value, do not wh
9、olly 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 affiliation with IEEE. Suggestions for changes in document
10、s 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 for interpretations is brought to the attention of
11、IEEE, 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 interests. For this reason, IEEE and the members of it
12、ssocieties 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 interpretations should be addressed to:Secretary, IEEE-SA
13、Standards Board445 Hoes LaneP.O. Box 1331Piscataway, NJ 08855-1331USANote: 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 vali
14、dity 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.iiiImplementation note(Thi
15、s implementation note is informative for IEEE Std 1462-1998, Adoption of International Standard ISO/IEC 14102:1995, Information technologyGuideline for the evaluation and selection of CASE tools. It is not part of ISO/IEC14102: 1995.)IEEE Std 1462-1998 is an adoption of ISO/IEC 14102: 19951. The fol
16、lowing implementation notes relate toIEEE interpretation of ISO/IEC 14102. TerminologyThe terms “metric” and “measurement” are both used in the document, and can be read as having the samemeaning. Some differences exist between the terminology used in IEEE Std 1462-1998 and that in IEEE Std 610.12-1
17、990.The reader should use the local definitions in IEEE Std 1462-1998 where there is a conflict with those of IEEEStd 610.12-1990. In some cases, the definition in IEEE Std 610.12-1990 may provide further clarification. It isimportant to keep in mind, however, that full compatibility of definitions
18、has yet to be achieved in the evolvingfield of software engineering.Related IEEE standardsIEEE Std 610.12-1990, IEEE Standard Glossary of Software Engineering Terminology.2IEEE Std 1348-1995, IEEE Recommended Practice for the Adoption of Computer-Aided Software Engi-neering (CASE) Tools.The role of
19、the standardIEEE Std 1462-1998 deals with the technical evaluation of a CASE tool. This represents only a portion ofthe overall process that covers the introduction of a new CASE tool into the organization. For example, thebusiness case including the business objectives that the CASE tool is intende
20、d to address are part of activi-ties that would precede the use of IEEE Std 1462-1998.Specifically, IEEE Std 1348-1995 covers the broader view, and places the evaluation as one of four steps.The reader is advised to review IEEE Std 1348-1995 together with IEEE Std 1462-1998 in order to establisha pr
21、oper scope and business case for the evaluation. IEEE recommends that the evaluation of a CASE tool betreated as a project with its associated budget and schedule controls.Section 9 and CASE tool characteristicsSection 9 of IEEE Std 1462-1998 describes a set of product characteristics against which
22、the evaluationshould be done. These are organized under the following four areas, which together form the basis for estab-lishing the requirements and performing the final evaluation:1) How the CASE tool meets the needs of the life cycle processes used;1ISO and ISO/IEC publications are available fro
23、m the ISO Central Secretariat, Case Postale 56, 1 rue de Varemb, CH-1211, Genve20, Switzerland/Suisse. ISO publications are also available in the United States from the Sales Department, American National Stan-dards Institute, 11 West 42nd Street, 13th Floor, New York, NY 10036, USA.2IEEE publicatio
24、ns are available from the Institute of Electrical and Electronics Engineers, 445 Hoes Lane, P.O. Box 1331, Piscataway,NJ 08855-1331, USA.iv2) How the CASE relates to the overall tool environment;3) How the CASE tool itself performs; and 4) Other criteria.The requirements are organized as characteris
25、tics and subcharacteristics, adopting the software productquality model as defined in ISO/IEC 9126: 1991, Information technologySoftware product evaluationQuality characteristics and guidelines for their use. The high-level characteristic (also referred to as qualityfactor) is subdivided into subcha
26、racteristics, that in turn may be further subdivided. At the lowest level, theyare referred to as atomic subcharacteristics. The evaluation of each chosen characteristic and subcharacteris-tic is done through the establishment of a value for each atomic subcharacteristic.The user of IEEE Std 1462-19
27、98 should select from the set of characteristics noted. However, the followingshould be noted: Characteristics from each of the four areas should be selected to cover each of the major tool features. The characteristics, once selected, should be prioritized. This is particularly true for Areas 1 and
28、 3.These priorities should reflect the main objectives of the tool.ComplianceIEEE Std 1462-1998 provides guidance in the steps recommended to undertake the evaluation of a CASEtool or tools, and in the features (characteristics) of the CASE tool. The four processes described are notmandatory; there
29、are few “shall” statements, and the tailoring of these processes should be done carefully,since tailoring down may introduce added risk for a CASE evaluation project. Assumptions should be veri-fied with experienced staff whenever possible. IEEE recommends that any organization undertaking one or mo
30、re tool evaluations should provide the gen-eral level of compliance that it requires for any tool evaluation project. The process activities for a givenproject can then be further tailored, since the number of activities may vary depending on the criticality ofthe CASE tool being evaluated.In situat
31、ions where the evaluation is being subcontracted, it is recommended that the organization (pur-chaser) formally specify the minimum processes, activities, and tasks that are to be followed in IEEE Std1462-1998.vParticipantsThe following persons were on the balloting committee:When the IEEE-SA Standa
32、rds Board adopted this standard on 19 March 1998, it had the followingmembership:Richard J. Holleman,ChairDonald N. Heirman,Vice ChairJudith Gorman,Secretary*Member EmeritusSyed AliPamela K. AryaRobert E. BarryLeo BeltracchiMordechai Ben-MenachemH. Ronald BerlackAlan L.BridgesKathleen L. BriggsEdwar
33、d R. ByrneMichael CaldwellThomas G. CallaghanKeith ChanJohn P. ChihorekAntonio M. CicuTheo ClarkeGregory T. DaichBostjan K. DergancSanjay DewalLeo EganWilliam EventoffJonathan H. FaircloughJohn W. FendrichJay ForsterSimon GabrihelidisJuan Garbajosa-SopenaHiranmay GhoshMarilyn Ginsberg-FinnerJohn Gar
34、th GlynnJulio Gonzalez-SanzLewis GrayL. M. GuntherJohn HarauzHerbert HechtManfred HeinMark HeinrichMark HenleyJerry HullerFabrizio ImelioFrank V. JorgensenVladan V. JovanovicWilliam S. JunkRon S. KenettJudith S. KernerRobert J. KierzykDwayne L. KnirkShaye KoenigThomas M. KuriharaJohn B. LaneJ. Denni
35、s LawrenceRandal LeavittMichael LinesWilliam M. LivelyDieter LookPhilip P. MakTomoo MatsubaraSue McGrathBret MichaelAlan MillerCharles S. MooneyJames W. MooreR. MuralidharanPavol NavratMyrna L. OlsonMike OttewillIndradeb P. PalLalit M. PatnaikDonald J. PfeifferAlex PolackPeter T. PoonKenneth R. Ptac
36、kJohn ReddanAnn E.ReedyAndrew P. SageHelmut SandmayrStephen R. SchachNorman SchneidewindRobert W. ShillatoCarl A. SingerRichard S. SkyAlfred R. SorkowitzJulia StesneyFred J. StraussToru TakeshitaLeonard L. TrippRichard D. TuckerThomas E. VollmanDolores WallaceDavid M. WaxmanCamille S. White-PartainS
37、cott A. WhitmirePeter F. ZollSatish 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. Bruce McClungLouis-Franois PauRonald C. PetersenGerald H. PetersonJohn B. PoseyGary S. RobinsonHans E. WeinrichDonald W. Zipse
