The SWEBOK Guide A Curriculum Analysis Tool SWEBOK ÉTS Le Guide SWEBOK Un outil d analyse de cursus Pierre Bourque ICSSEA 2005 Paris, France 30 November 2005
Corporate Support by: Project managed by: 2
Presentation Objectives Give an overview of the emerging international consensus on the core body of knowledge of software engineering Discuss the impact of the SWEBOK Guide on software engineering education through a citation analysis Explain how you can use the SWEBOK Guide as a undergraduate and graduate curriculum analysis tool Briefly present the on-going work to produce the 2009 Version 3
Development of a Profession Initial professional education Skills Development One or both Certification Licensing Full Professional Status Accreditation Professional development Code of ethics Professional societies Adapted from Steve McConnell, After the Gold Rush, Microsoft Press, 999, p. 93 4
Guide to the Engineering Body of Knowledge (SWEBOK ) Available free of charge on www.swebok.org International participation from industry, professional societies, standards bodies, academia, authors Trial Version in 200 2004 Version is the current version 200 and 2004 Version are translated and published in Japanese The 2004 Version was endorsed by the project s Industrial Advisory Board in January 2004 and approved by the IEEE Computer Society Board of Governors in February 2004 Recognized and published as ISO Technical Report 9759 Translation of the SWEBOK Guide in French is currently in progress Registered in U.S. Patent Office 5
SWEBOK Guide Objectives Characterize the contents of the Engineering Body of Knowledge Provide a topical access to the Engineering Body of Knowledge Promote a consistent view of software engineering worldwide 6
SWEBOK Guide Objectives Clarify the place of, and set the boundary of, software engineering with respect to other disciplines (computer science, project management, computer engineering, mathematics, etc.) Provide a foundation for curriculum development and individual certification and licensing material 7
Categories of Knowledge in the SWEBOK Specialized Generally Accepted Advanced and Research 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 8
9
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 0
Formal resolutions Industrial Advisory Board (200) IEEE CS Board of Governors (200) "The Board of Governors of the IEEE Computer Society accepts the Guide to the Engineering Body of Knowledge (Trial Version) as fulfilling its development requirements and is ready for field trials for a period of two years IEEE CS Board of Governors (Feb. 2004) Officially approved the 2004 Version ISO Technical Report 9759
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 2
Guide to the Engineering Body of Knowledge 2004 Version Requirements Design Construction Testing Maintenance Requirements Fundamentals Design Fundamentals Basic Concepts of Construction Sofware Testing Fundamentals Maintenance Fundamentals Requirements Process Key Issues in Design Managing Construction Test Levels Key Issues in Maintenance Requirements Elicitation Structure and Architecture Practical Considerations Test Techniques Maintenance Process Requirements Analysis Design Quality Analysis and Evaluation Test Related Measures Techniques for Maintenance Requirements Specification Design Notations Test Process Requirements Validation Design Strategies and Methods Practical Considerations 3
Guide to the Engineering Body of Knowledge (2004 Version) Configuration Management Engineering Management Engineering Process Engineering Tools and Methods Quality Related Disciplines Configuration Management Fundamentals Keys Issues in SCM Configuration Control Configuration Status Accounting Initiation and Scope Definition Project Planning Project Enactment Review and Evaluation Process Implementation and Change Process Definition Process Assessment Process and Product Measurement Tools Requirements Tools Design Tools Construction Tools Testing Tools Maintenance Tools Engineering Process Tools Quality Tools Configuration Management Tools Quality Fundamentals Quality Management Processes Practical Considerations Computer Engineering Computer Science Management Mathematics Project management Configuration Auditing Release Management and Delivery Closure SW Engineering Measurement Engineering Management Tools Infrastructure Support Tools Miscellaneous Tool Issues Methods Heuristic Methods Quality management Ergonomics Systems engineering Formal Methods Prototyping Methods Miscellaneous Method Issues 4
5
Number of publications citing the SWEBOK Guide by publication type and by year of publication (as of April 2005) 999 2000 200 2002 2003 2004 2005 Total Journal Paper or Refereed Book Chapter 2 2 8 5 6 6 30 Refereed Conference Paper 3 5 20 9 8 55 Book 2 3 2 5 3 Other 3 2 2 3 2 Total number of citations 2 8 0 33 28 22 7 0 6
Number of Citations SWEBOK Guide is widely cited. Steady stream of citations over time. Citations of the SWEBOK Guide have appeared in the top journals of the discipline, including two citations in IEEE Computer, seven citations in IEEE, two citations in Information and Technology, and five citations in the Journal of Systems and. For papers appearing in 2005, these citations already include four citations in the Journal of Systems and and two citations in IEEE. Roughly 0 additional citations have appeared since this citation analysis was completed in April 2005. 7
Journal Paper or Refereed Book Chapter Refereed Conference Paper Book Other Total number of citations Maturation of Engineering as a Recognised Profession 5 3 2 Initial Professional Education 7 26 3 37 Accreditation 3 Skills Development 2 2 4 Certification 2 3 Licensing 3 Professional Development 2 3 Professional Societies Code of Ethics Other 3 7 3 34 Total number of citations 30 55 3 2 0 8
Initial Professional Education The SWEBOK Guide has had considerable impact on undergraduate software engineering education curricula and courses. Influence of the SWEBOK Guide can be found in software engineering curricula and courses taught in Australia, Canada, Germany, Iceland, Portugal, Spain, Sweden, Switzerland and the U.S.A. 9
Initial Professional Education The SWEBOK Guide was a primary source in the development of the body of knowledge component of the joint IEEE/ACM undergraduate curriculum guidelines for software engineering. With 26 citations, the SWEBOK Guide is widely cited in the proceedings of the annual IEEE Conference on Engineering and Training (CSEET). 20
Accreditation and Skills Development The SWEBOK Guide has had an influence on accreditation documents in Canada and in Australia Skills development in software engineering does not appear to be discussed widely in the literature. Nevertheless, the SWEBOK Guide is a major input to a software engineering apprenticeship framework presented in an IEEE paper. 2
Professional Development After the initial professional education component, the SWEBOK Guide is most often cited in publications discussing professional development issues. Two of the most extensive usages of the SWEBOK Guide fall into this category 22
SWEBOK Knowledge Area and First-Level Topics ETS Course Labels Overview Partially Covered Dedicated Requirements LOG230 LOG40. Design Construction Testing Maintenance Basic Concepts Maintenance Process Key issues in Maintenance........... LOG20 LOG50 LOG530 LOG20 LOG220 LOG420 LOG20 LOG220 Techniques for Maintenance Configuration Management LOG330 LOG40 Engineering Management LOG50 GPE450 Organizational Management GIA400 Project Management Engineering Measurement Engineering Processes LOG330 Engineering Tools and Methods LOG30 Quality LOG50 LOG330 23
Curriculum Coverage Analysis LOG230 covers the full set of Knowledge Areas but only at the introductory level No course explicitly covers Configuration Management Little coverage of Maintenance in spite of its importance to industry and in the student s work terms No course is dedicated to Testing in spite of its importance to industry and to the student s work terms Engineering Management is not well covered in the curriculum Engineering Tools and Methods is well covered in the student lab assignments 24
25
TAXONOMIE DES SUJETS POUR SOFTWARE REQUIREMENTS MATÉRIEL VU EN CLASSE CHAP. DANS LE MANUEL DU COURS AUTRES LECTURES NORMES LABORATOIRES Requirements Fundamentals Présentation en classe sur le chapitre Requirements du Guide SWEBOK Chapitre Requirements du Guide SWEBOK Hofmann, H. F., Lehner, F. Requirements Engineering as a Success Factor in Projects, IEEE, July/August 200 Definition of a software requirement 2 Product and process Requirements Design Constraints dans Labo 2 et 4 Functional and nonfunctional requirements 20, 22 http://www.serc.nl/quintbook/ Xavier Franch and Juan Pablo Carvallo, Using Quality Models in Package Selection, IEEE, January/February 2003 IEEE 830-998 IEEE 362-998 Labo 2 et 4 Emergent properties Quantifiable requirements Séance de questions sur les exigences nonfonctionnelles http://www.serc.nl/quintbook/ Labo 4 System requirements and software requirements Présentation sur sous-marin SONIA 7 26
2009 Version of the SWEBOK First workshop held in Edinburgh in July 2005 Second workshop planned for April 2006 in Montreal Main focus of changes Harmonization of IEEE software engineering professional products with the SWEBOK Guide as the cornerstone Guide Many stakeholders and users must be involved in the evolution process IEEE Computer Society financing is currently being finalized Currently seeking new and renewal of previous corporate sponsorships 27
Presentation Objectives Give an overview of the emerging international consensus on the core body of knowledge of software engineering Discuss the impact of the SWEBOK Guide on software engineering education through a citation analysis Explain how you can use the SWEBOK Guide as a undergraduate and graduate curriculum analysis tool Briefly present the on-going work to produce the 2009 Version 28
www.swebok.org 29