ISO/IEC TR TECHNICAL REPORT. Software Engineering Guide to the Software Engineering Body of Knowledge (SWEBOK) IEEE

Transcription

1 TECHNICAL REPORT ISO/IEC TR IEEE First edition Software Engineering Guide to the Software Engineering Body of Knowledge (SWEBOK) Ingénierie du logiciel Guide du corps de connaissance de l'ingénierie du logiciel (SWEBOK) Reference number ISO/IEC TR 19759:2005(E) ISO/IEC 2005

2 PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobe's 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 downloading this file, parties accept therein the responsibility of not infringing Adobe's 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 General 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 below. ISO Case postale 56 CH-1211 Geneva 20 Tel Fax copyright@iso.org Web ii ISO/IEC 2005 All rights reserved

3 Technical Report ISO/IEC TR 19759:2005(E) ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. In exceptional circumstances, the joint technical committee may propose the publication of a Technical Report of one of the following types: type 1, when the required support cannot be obtained for the publication of an International Standard, despite repeated efforts; type 2, when the subject is still under technical development or where for any other reason there is the future but not immediate possibility of an agreement on an International Standard; type 3, when the joint technical committee has collected data of a different kind from that which is normally published as an International Standard ( state of the art, for example). Technical Reports of types 1 and 2 are subject to review within three years of publication, to decide whether they can be transformed into International Standards. Technical Reports of type 3 do not necessarily have to be reviewed until the data they provide are considered to be no longer valid or useful. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC TR 19759, which is a Technical Report of type 3, was prepared by the IEEE Computer Society as the Guide to the Software Engineering Body of Knowledge, 2004 Version, and was adopted without change by ISO/IEC JTC 1/SC 7, Software and Systems Engineering. International Organization for Standardization/International Electrotechnical Commission Case postale 56 CH-1211 Genève 20 Switzerland iii

4 Introduction The purpose of the Guide to the Software Engineering Body of Knowledge is to provide a consensually validated characterization of the bounds of the software engineering discipline and to provide a topical access to the Body of Knowledge supporting that discipline. The Body of Knowledge is subdivided into ten software engineering Knowledge Areas (KA) plus an additional chapter providing an overview of the Knowledge Areas of strongly related disciplines. The descriptions of the KAs are designed to discriminate among the various important concepts, permitting readers to find their way quickly to subjects of interest. Upon finding a subject, readers are referred to key papers or book chapters selected because they succinctly present the knowledge. An emphasis on engineering practice leads the Guide toward a strong relationship with the normative literature. Most of the computer science, information technology and software engineering literature provides information useful to software engineers, but a relatively small portion is normative. A normative document prescribes what an engineer should do in a specified situation rather than providing information that might be helpful. The normative literature is validated by consensus formed among practitioners and is concentrated in standards and related documents. From the beginning, the SWEBOK project was conceived as having a strong relationship to the normative literature of software engineering. The two major standards bodies for software engineering (IEEE Computer Society Software and Systems Engineering Standards Committee and ISO/IEC JTC1/SC7) are represented in the project. Ultimately, it is hoped that software engineering practice standards will contain principles directly traceable to the Guide. The Guide is oriented toward a variety of audiences, all over the world. It aims to serve public and private organizations in need of a consistent view of software engineering for defining education and training requirements, classifying jobs, developing performance evaluation policies or specifying software development tasks. It also addresses practicing, or managing, software engineers and the officials responsible for making public policy regarding licensing and professional guidelines. In addition, professional societies and educators defining the certification rules, accreditation policies for university curricula, and guidelines for professional practice will benefit from the SWEBOK Guide, as well as the students learning the software engineering profession and educators and trainers engaged in defining curricula and course content. iv ISO/IEC 2005 All rights reserved

5 TECHNICAL REPORT ISO/IEC TR 19759:2005(E) Software Engineering Guide to the Software Engineering Body of Knowledge (SWEBOK) 1 Scope This Technical Report characterizes the boundaries of the software engineering discipline and provides topical access to the literature supporting that discipline. 2 Recommendations As a type 3 Technical Report, this document does not make technical recommendations. The information provided is that contained in the following publication (reproduced on the following pages), which is adopted as a Technical Report: Guide to the Software Engineering Body of Knowledge, 2004 Version, IEEE Computer Society. ISO/IEC 2005 All rights reserved 1