1、 Reference numberISO/IEC 12207:2008(E)IEEEStd 12207-2008INTERNATIONAL STANDARD ISO/IEC12207IEEEStd 12207-2008Second edition2008-02-01Systems and software engineering Software life cycle processes Ingnierie des systmes et du logiciel Processus du cycle de vie du logiciel ISO/IEC 12207:2008(E) IEEE St
2、d 12207:2008 PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloadin
3、g this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the Gener
4、al Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given
5、below. ISO Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org ISO/IEC 2008 All rights reserved IEEE 2008 All rights reserved iISO/IEC 12207:2008(E) IEEE Std 12207-2008 (Revision of IEEE/EIA 12207.0-1996) Systems and software enginee
6、ring Software life cycle processes Sponsor Software provide a common terminology between the revision of ISO/IEC 15288 and ISO/IEC 12207; where applicable, provide common process names and process structure between the revision of the ISO/IEC 15288 and this International Standard; enable the user co
7、mmunity to evolve towards fully harmonized standards and to provide a stable standard, while maximizing backward compatibility; and leverage ten years of experience with the development and use of ISO/IEC 12207 and ISO/IEC 15288. A subsequent revision is intended to achieve a fully harmonized view o
8、f the system and software life cycle processes. Identified areas to address in the future include: common process purposes and outcomes, architecture of the standards, level of prescription of activities and tasks, life cycle treatments, treatment of products and services, common verification and va
9、lidation concepts, common configuration management concepts, deferred recommendations and alignment with other applicable standards. The IEEE Computer Society collaborated with ISO/IEC JTC 1 in the development of this International Standard. IEEE/EIA 12207.0-1996, Industry Implementation of Internat
10、ional Standard ISO/IEC 12207:1995 Standard for Information Technology Software Life Cycle Processes, was one of the base documents used in the development of this International Standard. ISO/IEC 12207:2008(E) IEEE Std 12207-2008 ISO/IEC 2008 All rights reserved IEEE 2008 All rights reserved vIEEE St
11、andards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National Standards Institute, which bring
12、s together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the consensus development proce
13、ss, the IEEE does not independently evaluate, test, or verify the accuracy of any of the information contained in its standards. Use of an IEEE Standard is wholly voluntary. The IEEE disclaims liability for any personal injury, property or other damage, of any nature whatsoever, whether special, ind
14、irect, consequential, or compensatory, directly or indirectly resulting from the publication, use of, or reliance upon this, or any other IEEE Standard document. The IEEE does not warrant or represent the accuracy or content of the material contained herein, and expressly disclaims any express or im
15、plied warranty, including any implied warranty of merchantability or fitness for a specific purpose, or that the use of the material contained herein is free from patent infringement. IEEE Standards documents are supplied “AS IS.” The existence of an IEEE Standard does not imply that there are no ot
16、her ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the IEEE Standard. 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
17、comments received from users of the standard. Every IEEE Standard is subjected to review at least every five years for revision or reaffirmation. When a document is more than five years old and has not been reaffirmed, it is reasonable to conclude that its contents, although still of some value, do
18、not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE Standard. In publishing and making this document available, the IEEE is not suggesting or rendering professional or other services for, or on behalf of, any person
19、 or entity. Nor is the IEEE undertaking to perform any duty owed by any other person or entity to another. Any person utilizing this, and any other IEEE Standards document, should rely upon the advice of a competent professional in determining the exercise of reasonable care in any given circumstanc
20、es. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specific applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standar
21、ds represent a consensus of 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
22、interpretation requests except in those cases where the matter has previously received formal consideration. At lectures, symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall make it clear that his or her views should be considered the personal vie
23、ws of that individual rather than the formal position, explanation, or interpretation of the IEEE. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affiliation with IEEE. Suggestions for changes in documents should be in the form of a proposed c
24、hange of text, together with appropriate supporting comments. Comments on standards and requests for interpretations should be addressed to: Secretary, IEEE-SA Standards Board 445 Hoes Lane Piscataway, NJ 08854 USA Authorization to photocopy portions of any individual standard for internal or person
25、al 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, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA;
26、+1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. ISO/IEC 12207:2008(E) IEEE Std 12207-2008 vi ISO/IEC 2008 All rights reserved IEEE 2008 All rights reservedIntroduction ISO/IEC 1220
27、7 was published on 1 August 1995 and was the first International Standard to provide a comprehensive set of life cycle processes, activities and tasks for software that is part of a larger system, and for stand alone software products and services. That International Standard was followed in Novembe
28、r 2002 by ISO/IEC 15288 which addressed system life cycle processes. The ubiquity of the software meant that the software and its design processes should not be considered separately from those systems, but be considered as an integral part of the system and system design processes. The ISO/IEC 1220
29、7 Amendments in 2002 and 2004 added process purpose and outcomes to the International Standard and established a Process Reference Model in accordance with the requirements of ISO/IEC 15504-2. This International Standard, a revision of the amended ISO/IEC 12207, is an initial step in the SC7 harmoni
30、zation strategy to achieve a fully integrated suite of system and software life cycle processes and guidance for their application. This revision integrates ISO/IEC 12207:1995 with its two Amendments and applies SC7 guidelines for process definition to support consistency and improved usability. Pro
31、ject execution was carefully coordinated with the parallel revision of ISO/IEC 15288:2002 to align structure, terms, and corresponding organizational and project processes. This International Standard can be used in one or more of the following modes: By an organization to help establish an environm
32、ent of desired processes. These processes can be supported by an infrastructure of methods, procedures, techniques, tools and trained personnel. The organization may then employ this environment to perform and manage its projects and progress systems through their life cycle stages. In this mode thi
33、s International Standard is used to assess conformance of a declared, established set of life cycle processes to its provisions. By a project to help select, structure and employ the elements of an established set of life cycle processes to provide products and services. In this mode this Internatio
34、nal Standard is used in the assessment of conformance of the project to the declared and established environment. By an acquirer and a supplier to help develop an agreement concerning processes and activities. Via the agreement, the processes and activities in this International Standard are selecte
35、d, negotiated, agreed to and performed. In this mode this International Standard is used for guidance in developing the agreement. By organizations and assessors to perform assessments that may be used to support organizational process improvement. This International Standard contains requirements i
36、n four Clauses: Clause 6, which defines the requirements for the system life cycle processes, Clause 7, which defines the requirements for specific software life cycle processes, clauses of Annex A, which provides requirements for tailoring of this International Standard and clauses of Annex B, whic
37、h provides a Process Reference Model (PRM) which may be used for assessment purposes. Five informative annexes support the harmonization strategy initiated by this revision. Annex C expands on history and rationale for the changes, and provides high-level traceability among the International Standar
38、ds which were used as the inputs to this revision. Annex D describes the alignment of the processes of ISO/IEC 15288 and ISO/IEC 12207 a key focus of this revision. Annex E provides an example of a process view for Usability, intended to illustrate how a project might assemble processes, activities
39、and tasks of ISO/IEC 12207 to provide focused attention to the achievement of product characteristics that have been selected as being of special interest. ISO/IEC 12207:2008(E) IEEE Std 12207-2008 ISO/IEC 2008 All rights reserved IEEE 2008 All rights reserved vii Annex F contains some example proce
40、ss descriptions that are considered useful to some readers of this International Standard. Annex G provides support for IEEE users and describes relationships of this International Standard to IEEE standards. Readers of this International Standard are advised to consult Clause 5 to gain understandin
41、g of the key concepts used. NOTE A future Technical Report (ISO/IEC TR 24748) will describe the relations between this International Standard and ISO/IEC 15288:2008. ISO/IEC 12207:2008(E) IEEE Std 12207-2008 viii ISO/IEC 2008 All rights reserved IEEE 2008 All rights reservedIEEE Introduction This in
42、troduction is not part of IEEE Std 12207-2008, Systems and Software EngineeringSoftware Life Cycle Processes. IEEE Std 12207-2008 and IEEE Std 15288-2008 are identical to ISO/IEC 12207:2008 and ISO/IEC 15288:2008. Therefore, all references to ISO/IEC 12207 or ISO/IEC 15288 apply equally well to thei
43、r IEEE counterparts. Further details regarding relationships to IEEE standards can be found in Annex G. This standard replaces IEEE/EIA 12207.0-1996, Industry Implementation of International Standard ISO/IEC 12207: 1995 Standard for Information Technology Software Life Cycle Processes, which was an
44、adoption with changes of ISO/IEC 12207:1995. Users of the earlier standard may be interested to know what will happen to its companions, IEEE/EIA 12207.1-1996 and IEEE/EIA 12207.2-1997. There is currently a project underway to replace IEEE/EIA 12207.1 with an adoption of ISO/IEC 15289. Completion of
45、 the current project will render IEEE/EIA 12207.2 obsolete; it will probably be withdrawn unless there is a demonstration of interest to revise it. The original ISO/IEC 12207 was published on 1 August 1995 and was the first international standard to provide a comprehensive set of life cycle processe
46、s, activities and tasks for software that is part of a larger system, and for stand alone software products and services. That international standard was followed in November 2002 by ISO/IEC 15288 which addressed system life cycle processes. IEEE cooperated with the Electronic Industries Alliance (E
47、IA) in adopting ISO/IEC with changes to become IEEE/EIA 12207-1996. In 2004, IEEE performed an identical adoption of ISO/IEC 15288:2002. The ISO/IEC 12207 amendments in 2002 and 2004 added process purpose and outcomes to the International Standard and established a Process Reference Model in accorda
48、nce with the requirements of ISO/IEC 15504-2. IEEE did not pick up these amendments, preferring a stable base for the users of its standard. This new revision of ISO/IEC 12207 is the product of a coordinated effort by IEEE and ISO/IEC JTC 1/SC 7. The base documents for the revision included the ISO/
49、IEC standard and its amendments, and the IEEE/EIA standard and its unique material. This revision integrates ISO/IEC 12207:1995 with its two Amendments and applies SC7 guidelines for process definition to support consistency and improved usability. Project execution was carefully coordinated with the parallel revision of ISO/IEC 15288:2002 to align structure, terms, and corresponding organizational and project processes. This revised standard is a step in the SC7 harmonization strategy to achieve a
