IEEE-1517-1999-R2004.pdf
《IEEE-1517-1999-R2004.pdf》由会员分享,可在线阅读,更多相关《IEEE-1517-1999-R2004.pdf(51页珍藏版)》请在三一文库上搜索。
1、 The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA Copyright 1999 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 14 July 1999. Printed in the United States of America. Print: ISBN 0-7381-1735-
2、8 SH94751 PDF: ISBN 0-7381-1736-6 SS94751 No 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 1517-1999(R2004) IEEE Standard for Information TechnologySoftware Life Cycle ProcessesR
3、euse Processes Sponsor Software Engineering Standards Committee of the IEEE Computer Society Approved 26 June 1999 IEEE-SA Standards Board Abstract: A common framework for extending the software life cycle processes of IEEE/EIA Std 12207.0-1996 to include the systematic practice of software reuse is
4、 provided. This standard spec- ifies the processes, activities, and tasks to be applied during each phase of the software life cycle to enable a software product to be constructed from reusable assets. It also specifies the process- es, activities, and tasks to enable the identification, constructio
5、n, maintenance, and management of assets supplied. Keywords: asset, domain engineering, process, software life cycle, software reuse Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not for Res
6、ale, 04/25/2007 02:53:56 MDTNo reproduction or networking permitted without license from IHS -,-,- Reaffirmed 25 March 2004 IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Com- mittees of the IEEE Standards Association (IEEE-SA) Standards Board. Member
7、s 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 the Institute as well as those activities outside of IEEE that have expressed an i
8、nterest 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 St
9、andard. Furthermore, the viewpoint 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 fi ve years for revis
10、ion or reaffi rmation. When a document is more than fi ve years old and has not been reaffi rmed, it is rea- sonable to conclude that its contents, although still of some value, do not wholly refl ect the present state of the art. Users are cautioned to check to determine that they have the latest e
11、dition of any IEEE Standard. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affi liation with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Interpr
12、etations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specifi 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 represe
13、nt 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 interp
14、retation requests except in those cases where the matter has previously received formal consideration. Comments on standards and requests for interpretations should be addressed to: Secretary, IEEE-SA Standards Board 445 Hoes Lane P.O. Box 1331 Piscataway, NJ 08855-1331 USA Authorization to photocop
15、y portions of any individual standard for internal or personal use is granted by the Institute of Electrical and 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, C
16、us- tomer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; (978) 750-8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copy- right Clearance Center. Note: Attention is called to the possibility that implementation of t
17、his standard may require use of subject matter covered by patent rights. By publication of this standard, no position 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
18、required by an IEEE standard or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 No
19、t for Resale, 04/25/2007 02:53:56 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright 1999 IEEE. All rights reserved. iii Introduction (This introduction is not part of IEEE Std 1517-1999, IEEE Standard for Information TechnologySoftware Life Cycle ProcessesReuse Proc
20、esses.) Implementing software reuse entails more than creating and using libraries of assets. It requires formalizing the practice of reuse by integrating reuse processes and activities into the software life cycle. Unless reuse is explicitly defi ned in the software life cycle processes, an organiz
21、ation will not be able to repeatedly exploit reuse opportunities in multiple software projects or products. Without this repetition, the improvement to the software life cycle and the software products that result from the practice of reuse will be limited and, perhaps, disappointing. Systematic reu
22、se is the practice of reuse according to a well-defi ned, repeatable process. Practicing system- atic reuse enables signifi cant software productivity, quality, and cost improvements. The major benefi ts that systematic reuse can deliver are as follows: Increase software productivity; Shorten softwa
23、re development time; Move personnel, tools, and methods more easily from project to project; Reduce software development and maintenance costs; Produce higher quality software products; Improve software product interoperability; Provide a competitive advantage to an organization that practices reuse
24、. There are a variety of approaches to implement the concept of reuse. What distinguishes systematic reuse is the avoidance of the proliferation of multiple versions of otherwise common elements. For example, if a reuse approach results in multiple instantiations of a common element, each of which m
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- IEEE 1517 1999 R2004
链接地址:https://www.31doc.com/p-3770670.html