the swebok guide – a curriculum analysis tool le guide...
TRANSCRIPT
1
The SWEBOK Guide The SWEBOK Guide –– A Curriculum A Curriculum Analysis ToolAnalysis Tool
Le Guide SWEBOK Le Guide SWEBOK –– Un Un outiloutil dd’’analyseanalysede de cursuscursus
Pierre BourquePierre Bourque
ICSSEA 2005Paris, France
30 November 2005
SW
EB
OK
ÉTS
2
Project managed by:
Corporate Support by:
3
Presentation ObjectivesPresentation 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
4
Development of a ProfessionDevelopment of a Profession
Initial professional education
Skills Development
One or both
Full Professional
Status
Certification Licensing
Accreditation
Professional development
Code of ethics
Professional societies
Adapted from Steve McConnell, After the Gold Rush, Microsoft Press, 1999, p. 93
5
Guide to the Software Engineering Guide to the Software Engineering Body of Knowledge (SWEBOKBody of Knowledge (SWEBOK ®®))
� Available free of charge on www.swebok.org
� International participation from industry, professional societies, standards bodies, academia, authors
� Trial Version in 2001
� 2004 Version is the current version
� 2001 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 19759
� Translation of the SWEBOK Guide in French is currently in progress
® Registered in U.S. Patent Office
6
SWEBOK Guide ObjectivesSWEBOK Guide Objectives
� Characterize the contents of the Software Engineering Body of Knowledge
� Provide a topical access to the Software Engineering Body of Knowledge
� Promote a consistent view of software engineering worldwide
7
SWEBOK Guide ObjectivesSWEBOK 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
8
Categories of Knowledge Categories of Knowledge in the SWEBOKin the SWEBOK
GenerallyAccepted
Advanced
Spe
cial
ized
andResearch
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
9
10
Three Underlying Principles Three Underlying Principles of the Projectof 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
11
Formal resolutionsFormal resolutions� Industrial Advisory Board (2001)� IEEE CS Board of Governors (2001)
� "The Board of Governors of the IEEE Computer Society accepts the Guide to the Software 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 19759
12
Deliverables: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
13
Guide to the Software Engineering Body of Knowledge2004 Version
Software
ConstructionSoftware
MaintenanceSoftware Testing
Basic Concepts
of Construction
Managing
Construction
Software
Maintenance
Fundamentals
Key Issues in
Software
Maintenance
Techniques for
Maintenance
Sofware
Testing
Fundamentals
Test Levels
Test Techniques
Test Related
Measures
Test
Process
Software Design
Software Design
Fundamentals
Key Issues in
Software Design
Software Structure
and Architecture
Software Design
Quality Analysis
and Evaluation
Software Design
Notations
Software
Requirements
Software
Requirements
Fundamentals
Requirements
Process
Requirements
Elicitation
Requirements
Specification
Requirements
Validation
Requirements
Analysis
Software Design
Strategies and
Methods
Practical
Considerations
Practical
Considerations
Maintenance
Process
14
Related
Disciplines
Computer
Science
Management
Mathematics
Project
management
Quality
management
Software
Ergonomics
Systems
engineering
Closure
Process
Assessment
Software Design Tools
Guide to the Software Engineering Body of Knowledge
(2004 Version)
Software
Configuration
Management
Software
Engineering Tools
and Methods
Software
Engineering
ProcessSoftware Quality
Software
Configuration
Management
Fundamentals
Keys
Issues in
SCM
Software
Configuration
Control
Software
Configuration
Status Accounting
Software
Configuration
Auditing
Software Release
Management and
Delivery Software Methods
Software ToolsProcess
Implementation
and Change
Process and
Product
Measurement
Software Quality
Fundamentals
Software Quality
Management
Processes
Heuristic Methods
Formal Methods
Prototyping Methods
Software Requirements
Tools
Software Testing Tools
Software Maintenance
Tools
Software Engineering
Process Tools
Process
Definition
Practical
Considerations
Software Construction
Tools
Software Quality Tools
Software Configuration
Management Tools
Software Engineering
Management Tools
Infrastructure Support
Tools
Miscellaneous Tool
Issues
Miscellaneous Method
Issues
Software
Engineering
Management
Initiation and
Scope
Definition
Software
Project
Planning
Software Project
Enactment
Review and
Evaluation
SW Engineering
Measurement
Computer
Engineering
15
16
Number of publications citing the SWEBOK Guide Number of publications citing the SWEBOK Guide by publication type and by year of publicationby publication type and by year of publication
(as of April 2005)(as of April 2005)
11072228331082Total number of citations
12132231Other
1352321Book
558192053Refereed
Conference
Paper
306658221Journal
Paper or
Refereed
Book
Chapter
Total2005200420032002200120001999
17
NumberNumber ofof CitationsCitations
� 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 Software, two citations in Information and Software Technology, and five citations in the Journal of Systems and Software.
� For papers appearing in 2005, these citations already include four citations in the Journal of Systems and Software and two citations in IEEE Software.
� Roughly 10 additional citations have appeared since this citation analysis was completed in April 2005.
1811012135530Total number of
citations
34371113Other
11Code of Ethics
11Professional
Societies
13112Professional
Development
3111Licensing
321Certification
422Skills
Development
3111Accreditation
3731267Initial
Professional
Education
111235Maturation of
Software
Engineering as a
Recognised
Profession
Total number of
citations
OtherBookRefereed
Conference
Paper
Journal Paper
or Refereed
Book Chapter
19
Initial Professional Initial Professional EducationEducation
� 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.
20
Initial Professional Initial Professional EducationEducation
� 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 Software Engineering and Training (CSEET).
21
AccreditationAccreditation andand SkillsSkillsDevelopmentDevelopment
� 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 Software paper.
22
Professional Professional DevelopmentDevelopment
� 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
23
LOG330LOG510Software Quality
LOG310Software Engineering Tools and Methods
LOG330Software Engineering Processes
GPE450
GIA400
LOG510Software Engineering Management
Organizational Management
Project Management
Software Engineering Measurement
LOG330
LOG410
Software Configuration Management
LOG530Software Maintenance
Basic Concepts
Maintenance Process
Key issues in Software Maintenance
Techniques for Maintenance
LOG120
LOG510
Software Testing
LOG120
LOG220
Software Construction
LOG120
LOG220
LOG420
Software Design
LOG410LOG230
.
.
.
.
.
.
.
.
.
.
.
.
Software Requirements
DedicatedPartially Covered Overview
ETS Course LabelsSWEBOK Knowledge Area and First-Level Topics
24
Curriculum Coverage AnalysisCurriculum Coverage Analysis
� LOG230 covers the full set of Knowledge Areas but only at the introductory level
� No course explicitly covers Software Configuration Management
� Little coverage of Software Maintenance in spite of its importance to industry and in the student’s work terms
� No course is dedicated to Software Testing in spite of its importance to industry and to the student’s work terms
� Software Engineering Management is not well covered in the curriculum
� Software Engineering Tools and Methods is well covered in the student lab assignments
25
26
7Présentation sur sous-marin
SONIA
System requirements and software requirements
Labo 4http://www.serc.nl/quint-book/
Séance de questions sur les exigences
non-fonctionnelles
Quantifiable requirements
Emergent properties
Labo 2 et 4IEEE 830-1998IEEE 1362-1998
http://www.serc.nl/quint-book/Xavier Franch and Juan Pablo Carvallo, Using Quality Models in Software Package Selection, IEEE Software, January/February 2003
20, 22Functional and non-functional requirements
Design Constraintsdans Labo 2 et 4
Product and process Requirements
2Definition of a software requirement
Chapitre Software Requirements du Guide SWEBOKHofmann, H. F., Lehner, F. Requirements Engineering as a Success Factor in Software Projects, IEEE Software, July/August 2001
Présentation en classe sur
le chapitre Software
Requirementsdu Guide SWEBOK
Software RequirementsFundamentals
LABORATOIRESNORMESAUTRES LECTURES
CHAP. DANS LE MANUEL DU COURS
MATÉRIEL VU EN CLASSE
TAXONOMIE DES SUJETS POUR SOFTWARE REQUIREMENTS
27
2009 Version of the SWEBOK 2009 Version of the SWEBOK GuideGuide
� 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
� 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
28
Presentation ObjectivesPresentation 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
29
www.swebok.orgwww.swebok.org