1、g44g40g40g40g3g54g87g71g3g20g24g20g26g140g16g21g19g20g19g11g53g72g89g76g86g76g82g81g3g82g73g44g40g40g40g3g54g87g71g3g20g24g20g26g16g20g28g28g28g12g44g40g40g40g3g54g87g68g81g71g68g85g71g3g73g82g85g3g44g81g73g82g85g80g68g87g76g82g81g55g72g70g75g81g82g79g82g74g92g179g54g92g86g87g72g80g3g68g81g71g3g54g8
2、2g73g87g90g68g85g72g47g76g73g72g3g38g92g70g79g72g3g51g85g82g70g72g86g86g72g86g179g53g72g88g86g72g51g85g82g70g72g86g86g72g86g44g40g40g40g3g38g82g80g83g88g87g72g85g3g54g82g70g76g72g87g92g54g83g82g81g86g82g85g72g71g3g69g92g3g87g75g72g54g82g73g87g90g68g85g72g3g9g3g54g92g86g87g72g80g86g3g40g81g74g76g81g7
3、2g72g85g76g81g74g3g54g87g68g81g71g68g85g71g86g3g38g82g80g80g76g87g87g72g72g44g40g40g40g22g3g51g68g85g78g3g36g89g72g81g88g72g3g49g72g90g3g60g82g85g78g15g3g49g60g3g20g19g19g20g25g16g24g28g28g26g15g3g56g54g36g3g3g21g24g3g36g88g74g88g86g87g3g21g19g20g19g20g24g20g26g55g48IEEE Std 1517-2010 (Revision of I
4、EEE Std 1517-1999) Copyright 2010 IEEE. All rights reserved. IEEE Standard for Information TechnologySystem and Software Life Cycle ProcessesReuse Processes Sponsor Software +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtaine
5、d through the Copyright Clearance Center. Introduction This introduction is not part of IEEE Std 1517-2010, IEEE Standard for Information Technologyg650System and Software Life Cycle Processesg650Reuse Processes. This standard replaces IEEE Std 1517-1999 B3.aThe revision of this standard is a step i
6、n the strategy of harmonizing IEEE software and systems engineering standards with those of ISO/IEC JTC 1/SC 7 in order to achieve a fully integrated suite of system and software life cycle processes and guidance for their application. This revision is closely integrated with IEEE Std 12207-2008.bTo
7、 that end, this revision does not define processes but instead adds tasks and outcomes to processes and activities defined in IEEE Std 12207-2008. Clause 3 has been modified in this revision to more closely hew to the definitions in Clause 4 of IEEE Std 12207-2008. Subclause 7.3 of IEEE Std 12207-20
8、08 encompasses many processes specified in IEEE Std 1517-1999, and so those processes have been removed from this revision. In order to couple more tightly with IEEE Std 122207-2008, the structure of this revision differs from that of IEEE Std 1517-1999. The clauses correspond with clauses of IEEE S
9、td 12207-2008. Clause 5 corresponds to Clause 6 of IEEE Std 12207-2008. Clause 6 corresponds to Clause 7 of IEEE Std 12207-2008. The objectives defined in Annex C of IEEE Std 1517-1999 have been integrated into the processes of Clause 5 and Clause 6 of this revision. They comprise the reuse-related
10、outcomes specified for the processes. Software reuse entails capitalizing on existing software and systems to create new products. An organization cannot benefit from reuse by simply creating and employing libraries of assets. Rather, successful reuse requires the integration of reuse-related activi
11、ties into the life cycle processes used to create the reuse assets associated with software and system development. Unless reuse is explicitly defined in software and system life cycle processes, an organization will not be able to repeatedly exploit reuse opportunities in multiple software projects
12、 or products. Systematic reuse is the practice of reuse according to a consistent, repeatable process. Practicing systematic reuse requires a focus on the use of engineering principles for all reuse assets involved in development. The major benefits that systematic reuse can deliver are as follows:
13、g127 Increase software productivity g127 Shorten software development and maintenance time g127 Reduce duplication of effort g127 Move personnel, tools, and methods more easily among projects g127 Reduce software development and maintenance costs g127 Produce higher quality software products g127 In
14、crease software and system dependability aThe numbers in brackets correspond to those of the bibliography in Annex A. bInformation on references can be found in Clause 2. iv Copyright 2010 IEEE. All rights reserved. g127 Improve software interoperability and reliability g127 Provide a competitive ad
15、vantage to an organization that practices reuse There are a variety of approaches to implement the concept of reuse, including systematic and ad hoc reuse. What distinguishes systematic reuse from other methods is the avoidance of multiple versions of otherwise common elements. For example, suppose
16、a reuse approach results in multiple instantiations of a common element. If the instantiations are modified by software developers, then the element is no longer common and can no longer be maintained as a single element. In the context of this standard, systematic reuse excludes such approaches. Th
17、e majority of software products can be built with reuse assetsitems, such as designs or test plans, that have been designed to be used in multiple contexts. Because reuse assets can apply to software products, implementations of software products, or systems, reuse assets present tremendous opportun
18、ity for software reuse. One major problem encountered by organizations attempting to practice reuse is that reuse is simply missing from their life cycle processes. To harness the benefits of reuse, an organization must incorporate reuse throughout its system and software processes. An organization
19、that creates systems and software first and considers reuse second may not fully benefit from reuse practices. This standard endeavors to address this problem by defining a common framework for reuse activities and by defining how to integrate the practice of reuse into traditional system and softwa
20、re life cycle processes. Reuse activities describe how software products are built with assets and how to build and manage these assets. The reuse framework presented in this standard covers both the life cycle of a system and the life cycle of a software product. IEEE Std 12207-2008 establishes a c
21、ommon framework for software and system life cycle processes. This standard provides additional life cycle activities and tasks that augment the practice of systematic reuse. In addition to supplementing the activities defined in IEEE Std 12207-2008, this standard defines outcomes and tasks applicab
22、le throughout the life cycle process. Thus, the use of this standard requires access to and understanding of IEEE Std 12207-2008. For organizations that already employ systematic reuse activities, this standard may be used to determine the conformity of those activities to this standard and as a bas
23、is for improvement of those activities where warranted. When establishing or improving systematic reuse activities, organizations are encouraged to assess the business case. Although systematic reuse fosters significant benefits such as those already described, certain costs and risks may prevent be
24、nefits of reuse from being fully realized. These factors include the following: g127 The degree to which reuse benefits are relevant to the organization. For example, a small organization, or an organization that has few resources allocated to developing and maintain software products, may not be in
25、 a position to benefit sufficiently from systematic reuse to justify the required commitments and investments. g127 The availability of suitable tools and assets that are designed for reuse. The capital costs entailed by new software tools can be significant. The costs of acquiring and/or developing
26、 assets may not be justified in relation to the expected benefits. g127 The software maturity of the organization. Although the organization may wish to undertake systematic reuse, its capability maturity may be insufficient to implement the processes in this standard. Moreover, the organization may
27、 lack the means to change its infrastructure to support the processes of systematic reuse while continuing to operate its business as usual. Capability maturity should be objectively assessed in relation to this standard, and missing prerequisites, both as to capability maturity and as to infrastruc
28、ture, need to be put in place before attempting to undertake systematic reuse. v Copyright 2010 IEEE. All rights reserved. g127 The willingness of the people within the organization to make the necessary changes to the way in which they work. Many software organizations have cultures that are not co
29、nducive to systematic reuse. Producing original software is sometimes more well-regarded than reusing existing software. Changing attitudes and associated non-reuse behaviors can be difficult. Policy changes and capital in vestments, which require senior management to be firmly committed to the achi
30、evement of systematic reuse, may be necessary. Organizations interested in undertaking systemic reuse are advised to analyze their abilities to adopt this standard. A business case that clearly describes the goals, investments, costs, risks, and benefits, along with a time line for achieving the tra
31、nsition to systematic reuse, is an excellent way to ensure success. This standard provides the basis for practices that enable the incorporation of reuse into the system and software life cycle processes. IEEE Std 1517-2009 may be used to g127 Acquire, supply, develop, manage, and maintain reuse ass
32、ets; g127 Acquire, supply, develop, operate, and maintain software products that are built in whole or in part with reuse assets; g127 Manage and improve the organizations life cycle processes with respect to the practice of reuse; Establish software management and engineering environments based on
33、reuse activities; g127 Foster improved understanding among customers and vendors and parties involved in the reuse-based life cycle of a software product or system and assets; g127 Facilitate the use of reuse assets to develop software products and systems; g127 Facilitate the development of reuse a
34、ssets. IEEE Std 1517-2009 has been written to work with and integrate into IEEE Std 12207-2008. Notice to users Laws and regulations Users of these documents should consult all applicable laws and regulations. Compliance with the provisions of this standard does not imply compliance to any applicabl
35、e regulatory requirements. Implementers of the standard are responsible for observing or referring to the applicable regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents may not be const
36、rued as doing so. Copyrights This document is copyrighted by the IEEE. It is made available for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of engineering practic
37、es and methods. By making this document available for use and adoption by public authorities and private users, the IEEE does not waive any rights in copyright to this document. vi Copyright 2010 IEEE. All rights reserved. Updating of IEEE documents Users of IEEE standards should be aware that these
38、 documents may be superseded at any time by the issuance of new editions or may be amended from time to time through the issuance of amendments, corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the document together with any amendments, corrige
39、nda, or errata then in effect. In order to determine whether a given document is the current edition and whether it has been amended through the issuance of amendments, corrigenda, or errata, visit the IEEE Standards Association web site at http:/ieeexplore.ieee.org/xpl/standards.jsp, or contact the
40、 IEEE at the address listed previously. For more information about the IEEE Standards Association or the IEEE standards development process, visit the IEEE-SA web site at http:/standards.ieee.org. Errata Errata, if any, for this and all other standards can be accessed at the following URL: http:/sta
41、ndards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL for errata periodically. Interpretations Current interpretations can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/interp/ index.html. Patents Attention is called to the possibili
42、ty that implementation of this 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 is not responsible for identifying Essential Pate
43、nt Claims for which a license may be required, for conducting inquiries into the legal validity or scope of Patents Claims or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing agreements are reasonable o
44、r non-discriminatory. Users of this standard are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from the IEEE Standards Association. vii Copyright 2010 I
45、EEE. All rights reserved. viii Copyright 2010 IEEE. All rights reserved. Participants At the time this standard was submitted to the IEEE-SA Standards Board for approval, the Reuse Processes Working Group had the following membership: Elena Strange, Chair Joshua Brody Teresa Doran Lisa Lippincott Ja
46、mes Moore The following members of the individual balloting committee voted on this standard. Balloters may have voted for approval, disapproval, or abstention. Johann Amsenga Bakul Banerjee Juris Borzovs Pieter Botman Lyle Bullock Juan Carreon Lawrence Catchpole Michael Chonoles Keith Chow Paul Cro
47、ll Geoffrey Darnton David Deighton Thomas Dineen Teresa Doran Scott Duncan Sourav Dutta Carla Ewart Harriet Feldman Andrew Fieldsend David Friscia David Fuschi Gregg Giesler Allan Gillard Lewis Gray Randall Groves Louis Gullo John Harauz Mark Henley Frank Hill Werner Hoelzl Robert Holibaugh Bernard
48、Homes Atsushi Ito Mark Jaeger Piotr Karocki Rameshchandra Ketharaju Dwayne Knirk Ronald Kohl Thomas Kurihara George Kyle Marc Lacroix Susan Land David J. Leciston Daniel Lindberg William Lumpkins G. Luri Faramarz Maghsoodlou Edward McCall James Moore Finnbarr Murphy Michael S. Newman William Petit U
49、lrich Pohl Gerald Radack Annette Reilly Robert Robinson Terence Rout Randall Safier Bartien Sayogo Robert Schaaf David J. Schultz Stephen Schwarm Gil Shultz Carl Singer Luca Spotorno Friedrich Stallinger Thomas Starai Walter Struppler Marcy Stutzman Thomas Tullia David Walden Paul Work Oren Yuen Janusz Zalewski ix Copyright 2010 IEEE. All rights reserved. When the IEEE-SA Standards Board approved this standard on 17 June 2010, it had the following membership: Robert M. Grow, Chair Richard H. Hulett, Vice Chair Steve M. Mills, Past Chair Judith Gorman, Secretary Karen B
