1 / 22

Pierre Bourque, SWEBOK V3.0 Lead Coeditor 29 June 2016

Pierre Bourque, SWEBOK V3.0 Lead Coeditor 29 June 2016. Computer Society Learning Series Webinar Guide to the Software Engineering Body of Knowledge (SWEBOK) V3.0 Intro, Usages and Ongoing Work. Project Objectives. Promote a consistent view of software engineering worldwide

bye
Download Presentation

Pierre Bourque, SWEBOK V3.0 Lead Coeditor 29 June 2016

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Pierre Bourque, SWEBOK V3.0 Lead Coeditor 29 June 2016 Computer Society Learning Series WebinarGuide to the Software Engineering Body of Knowledge (SWEBOK) V3.0 Intro, Usages and Ongoing Work

  2. Project Objectives • Promote a consistent view of software engineering worldwide • Clarify the place of, and set the boundary of, software engineering with respect to other disciplines • Characterize the contents of the Software Engineering Body of Knowledge • Provide a topical access to the Software Engineering Body of Knowledge • Provide a foundation for curriculum development and individual certification and licensing material

  3. Categories of Knowledge in the SWEBOK Target of the SWEBOK Guide «Applicable to most projects, most of the time, and widespread consensus about their value and usefulness» Project Management Institute - PMI • North American Bachelor’s degree + 4 years of experience

  4. Three Underlying Principles of the Project • Transparency: the development process is itself published and fully documented • Consensus-building: the development process is designed to build, over time, consensus in industry, among professional societies and standards-setting bodies and in academia • Available free on the web at least in one format on www.swebok.org

  5. Deliverables: • Consensus on a list of Knowledge Areas • Consensus on a list of topics and relevant reference materials for each Knowledge Area • Consensus on a list of Related Disciplines

  6. Updated Knowledge Areas in V3 • Descriptions of all existing KAs have been updated often by newly recruited coeditor(s) • Reference material citations have been renewed for all topics of all KAs • Breakdown of topics and included topics have been revisited for all KAs

  7. Updated Knowledge Areas in V3 • Software Requirements • Software Design • User Interface Design is a new subarea • Software Construction • Software Construction Technologies is a new subarea • Software Testing • Software Maintenance

  8. Updated Knowledge Areas in V3 • Software Configuration Management • Software Engineering Management • Software Engineering Process • Significantly different structure • Software Quality

  9. New Knowledge Areas in V3 • Software Engineering Models & Methods • Includes material from previous Software Engineering Tools and Methods KA. Previous Software Engineering Tools subarea has been distributed across all existing KAs • Three new subareas on Software Engineering Models • Software Engineering Professional Practice • Software Engineering Economics • Computing Foundations • Engineering Foundations • Mathematical Foundations

  10. Recognized Related Disciplines • Computer Engineering • Computer Science • Mathematics • Project Management • Management • Quality Management • Systems Engineering

  11. Sample Subarea Breakdown of Topics for Software Requirements

  12. Two Useful Appendices • Appendix B: An annotated list of IEEE and ISO/IEC standards applicable to each of the KAs. • Appendix C: Consolidated Reference List • Final consolidated reference list contains 36 reference items

  13. V3 Review Process • Approval by the SWEBOK Change Control Board of all changes to initial baseline breakdown of topics, consolidated reference list items and KA specifications • Editors from 9 countries • All KAs were submitted for public review. Roughly 150 reviewers from over 30 countries • Public adjudication of roughly 2000 review comments • Formal ballot among IEEE CS members (259 Yes, 5 No) • Formal resolutions by IEEE CS PAB and BOG • Formal adoption as ISO/IEC TR 19759:2015

  14. Number of Hits of SWEBOK (As of 25 June 2016) • books.google.com identifies 4060 hits for “SWEBOK” • scholar.google.com identifies 5930 hits for “SWEBOK” • Google.com identifies 95900 hits for “SWEBOK” • IEEE Xplore identifies 828 hits for “SWEBOK”

  15. Usage Opportunities of SWEBOK V3 • Studying about generally accepted knowledge in software engineering • Identifying relevant reference material and standards within a given knowledge area • Reviewing software engineering courses focusing on particular KAs. • Reviewing coverage of KAs in graduate and undergraduate curricula.

  16. Usage Opportunities of SWEBOK V3 • Incorporating consolidated reference list items and standards listed in Appendix B into educational and training materials • Developing certification and training programs • Developing other frameworks: model curricula, competency models, program accreditation criteria, licensing criteria… • Developing educational and training materials • Developing software engineering career development programs

  17. Usage Opportunities of SWEBOK V3 • Developing job descriptions or competency profiles • Situating research contributions within the field of software engineering • Structuring asset libraries or repositories • Developing survey questionnaires on the state of software engineering practice within an organization or region

  18. Usage Opportunities of SWEBOK V3 • Classifying software engineering tools • Developing ontologies or knowledge models of software engineering • Comparing with bodies of knowledge of other related fields • Adopting the development process for bodies of knowledge of other fields or for more specialized bodies of knowledge within software engineering

  19. Call for Submissions and Participation • SWEBOK Evolution: Virtual Town Hall Meeting • 25 August 2016 • Contribute ideas, lessons learned to the next edition of the SWEBOK • Submissions due:29 July 2016 • Details: • www.computer.org/web/peb/engineering-disciplines-committee • Contact: • Rich Hilliard, r.hilliard@computer.org

  20. Call for Submissions and Participation • Topics include (but are not limited to): • user feedback, experiences, lessons learned • new knowledge areas, knowledge areas in need of refreshment or update • integration with other resources (including standards, publications, other bodies of knowledge such as EITBoK and SEBoK) • release strategies (e.g., 4.0 vs incremental) • enabling technologies for delivery and usage (e.g., wiki, meta data, rich media) • All submissions will be made available to the SWEBOK team • Selected submissions will be identified for presentation and discussion during the town hall meeting

  21. Concluding Remarks • SWEBOK V3 is a significant new edition of the SWEBOK Guide • SWEBOK V3 offers many opportunities for usage • Already seeking participation and submissions for next version

  22. pierre.bourque@etsmtl.cawww.swebok.org

More Related