BS PD ISO IEC TR 19759-2016 Software Engineering Guide to the software engineering body of knowledge (SWEBOK)《软件工程 软件工程管理知识体系 (SWEBOK) 指南》.pdf

《BS PD ISO IEC TR 19759-2016 Software Engineering Guide to the software engineering body of knowledge (SWEBOK)《软件工程 软件工程管理知识体系 (SWEBOK) 指南》.pdf》由会员分享，可在线阅读，更多相关《BS PD ISO IEC TR 19759-2016 Software Engineering Guide to the software engineering body of knowledge (SWEBOK)《软件工程 软件工程管理知识体系 (SWEBOK) 指南》.pdf（350页珍藏版）》请在麦多课文档分享上搜索。

1、Software Engineering Guide to the Software Engineering Body of Knowledge (SWEBOK) PD ISO/IEC TR 19759:2016 BSI Standards Publication WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06PD ISO/IEC TR 19759:2016 PUBLISHED DOCUMENT National foreword This Published Document is the UK implementation

2、of ISO/IEC TR 19759:2016. The UK participation in its preparation was entrusted to Technical Committee IST/15, Software and systems engineering. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the nec

3、essary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2016. Published by BSI Standards Limited 2016 ISBN 978 0 580 88300 2 ICS 35.080 Compliance with a British Standard cannot confer immunity from legal obligations. This Published Docum

4、ent was published under the authority of the Standards Policy and Strategy Committee on 31 May 2016. Amendments issued since publication Date Text affected e Engineering Guide to the oftw e ngineering ody of ledge (SWEBOK) Ingnierie du logiciel Guide du corps de connaissance de lingnierie du logicie

5、l (SWEBOK) TECHNICAL REPORT C TR Second edition 2015-10-01 Reference number ISO/IEC TR 19759:201 (E) ISO/IEC 201 201 - -01ii ISO/IEC 201 All rights reserved OPYRIGHT PR CTED DOCUMENT ISO/IEC 201 , Published in Switzerland the requester. www.iso.org PD ISO/IEC TR 19759:2016 ISO/IEC TR 19759:2016(E)Co

6、ntents Page Foreword .iv Introductionv 1 Scope.1 2 Recommendations.1 3 Revision of the IEEE Computer Society Publication 1 4 Publication1 ISO/IEC 201 All rights reserved iii PD ISO/IEC TR 19759:2016 ISO/IEC TR 19759:2016(E) ISO/IEC 201 All rights reserved i PD ISO/IEC TR 19759:2016 ISO/IEC TR 19759:

7、2016(E)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 Kno

8、wledge is subdivided into fifteen software engineering Knowledge Areas (KA) providing an outline of topics. The descriptions in 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, rea

9、ders are referred to key papers or books selected because they succinctly present the knowledge. Publication of the 2004 version of this Guide to the Software Engineering Body of Knowledge (SWEBOK 2004)adopted as ISO/IEC TR 19759:2005was a major milestone in establishing software engineering as a re

10、cognized engineering discipline. The goal in developing this update to SWEBOK is to improve the currency, readability, consistency, and usability of the Guide. All knowledge areas (KAs) have been updated to reflect changes in software engineering since publication of SWEBOK 2004. Four new foundation

11、 KAs and a Software Engineering Professional Practices KA have been added. The Software Engineering Tools and Methods KA has been revised as Software Engineering Models and Methods. Software engineering tools is now a topic in each of the KAs. Three appendices provide the specifications for the KA d

12、escription, an annotated set of relevant standards for each KA, and a listing of the references cited in the Guide. 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 engine

13、ering 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 conse

14、nsus 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 Soc

15、iety Software and Systems Engineering Standards Committee and ISO/IEC JTC1/SC7) cooperated in the project. 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 educ

16、ation 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

17、. 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 t

18、rainers engaged in defining curricula and course content. ISO/IEC 201 All rights reserved PD ISO/IEC TR 19759:2016 ISO/IEC TR 19759:2016(E)This page deliberately left blankPD ISO/IEC TR 19759:2015 ISO/IEC 201 All rights reserved 1 Software Engineering Guide to the Software Engineering Body of Knowle

19、dge (SWEBOK) Version 3.0 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 Technical Report, this document does not make technical recommendations. The inf

20、ormation 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 (SWEBOK) V3.0, IEEE Computer Society 3 Revision of the IEEE Computer Society Publication It has been agree

21、d with the IEEE Computer Society that ISO/IEC JTC 1/SC 7 will be consulted in the event of any revision or amendment of this IEEE Computer Society publication. Consultation will be accomplished by the existing Category A liaison relationship between SC 7 and IEEE Computer Society. 4 Publication The

22、report of the IEEE Computer Society appears on the following pages. CHNICAL REP T ISO/IEC TR 19759:201 PD ISO/IEC TR 19759:2016 ISO/IEC TR 19759:2016(E)This page deliberately left blank ISO/IEC TR 19759:201 PD ISO/IEC TR 19759:2016 ISO/IEC TR 19759:2016(E)Guide to the Software Engineering Body of Kn

23、owledge Version 3.0 SWEBOK A Project of the IEEE Computer Society PD ISO/IEC TR 19759:2016 ISO/IEC TR 19759:2016(E)Guide to the Software Engineering Body of Knowledge Version 3.0 Editors Pierre Bourque, cole de technologie suprieure (TS) Richard E. (Dick) Fairley, Software and Systems Engineering Associates (S2EA) ISO/IEC TR 19759:201 PD ISO/IEC TR 19759:2016 ISO/IEC TR 19759:2016(E)Copyright and Reprint Permissions. Educational or personal use of this material is permitted without fee provided such copies