© IEEE www.swebok.org1
Software Engineers: Software Engineers: What does industry expect them What does industry expect them
to know & master?to know & master?
Alain AbranAlain AbranP. Bourque, R. Dupuis, J. W. Moore, L. TrippP. Bourque, R. Dupuis, J. W. Moore, L. Tripp
SPIN-CHENNAIIndia
September 14, 2004
SW
EB
OK
ÉTS
© IEEE www.swebok.org2
Presentation ObjectivesPresentation Objectives
¤ Give an overview of an international consensus on the “core body of knowledge”of software engineering
¤ Briefly present the development process used to reach this consensus
¤ Briefly present usages of SWEBOK Guide
¤ Next steps
© IEEE www.swebok.org3
Presentation PlanPresentation Plan
¤¤Project backgroundProject background¤ Project development process
¤ Contents of the Guide
¤ Usages of the Guide in organizations
¤ Next steps
© IEEE www.swebok.org4
Guide to the Software Engineering Guide to the Software Engineering Body of Knowledge (SWEBOKBody of Knowledge (SWEBOK®®))
¤ Project initiated by the IEEE CS
¤ International participation from industry, professional societies, standards bodies, academia, authors
¤ Over 500 hundred software engineering professionals have been involved
¤ Release of Ironman Version in 2004® Registered in U.S. Patent Office
© IEEE www.swebok.org6
2004 SWEBOK Guide2004 SWEBOK Guide¤ Endorsed by the project’s Industrial
Advisory Board ¤ Approved by the IEEE Computer Society
Board of Governors¤ Adopted as ISO Technical Report 19759vAvailable on www.swebok.org
v To be published in book format by the IEEE Computer Society Press
© IEEE www.swebok.org7
SWEBOK Guide = 10 Knowledge AreasMapped TO ISO/IEC 12207:1995 processes
Software Quality
Software Engineering Tools and Methods
Software Engineering Process
Software Engineering Management
Software Configuration Management
MaintenanceTestingConstructionDesignRequirements
Primary Processes Supporting Processes
© IEEE www.swebok.org8
What is Software What is Software Engineering?Engineering?
¤ IEEE 610.12:v “(1) The application of a systematic,
disciplined, quantifiable approach to the development, operation, and maintenance of software; that is, the application of engineering to software.
v (2) The study of approaches as in (1).”
© IEEE www.swebok.org9
Recognized Profession?Recognized Profession?
¤ Starr*:vKnowledge and competence validated by
the community of peers
vConsensually validated knowledge rests on rational, scientific grounds
v Judgment and advice oriented toward a set of substantive values
* P. Starr, The Social Transformation of American Medicine: BasicBooks, 1982.
© IEEE www.swebok.org10
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
© IEEE www.swebok.org11
Presentation PlanPresentation Plan
¤ Project background
¤¤ Project development processProject development process¤ Contents of the Guide
¤ Applications of the Guide in organizations
¤ Next steps
© IEEE www.swebok.org12
Project ObjectivesProject 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
© IEEE www.swebok.org13
Project ObjectivesProject 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
© IEEE www.swebok.org14
Intended AudienceIntended Audience
¤ Public and private organizations
¤ Practicing software engineers
¤ Makers of public policy
¤ Professional societies
¤ Software engineering students
¤ Educators and trainers
© IEEE www.swebok.org15
What was out of scope?What was out of scope?
¤ Not a curriculum development effort
¤ Not an all-inclusive description of the sum of knowledge in the field
¤ Not all categories of knowledge
© IEEE www.swebok.org16
Categories of Knowledge Categories of Knowledge in the SWEBOKin the SWEBOK
GenerallyAccepted
Advanced
Sp
ecia
lized
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
© IEEE www.swebok.org17
Maths
Applicationdomain
knowledgeAdvanced
SEKnowledge
Guide to theSWEBOKStoneman
C.S.
...
Knowledgeof a
SoftwareEngineer
SpecializedSE
Knowledge
© IEEE www.swebok.org18
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 was designed to build, over time, consensus in industry, among professional societies and standards-setting bodies and in academia
¤ Available free on the web
© IEEE www.swebok.org19
Project TeamProject Team
¤ Editorial Team of the Guide
¤ Industrial Advisory Board
¤ Associate Editors of the Knowledge Areas
¤ Reviewers
© IEEE www.swebok.org20
Roles of the Industrial Roles of the Industrial Advisory BoardAdvisory Board
¤ Provide input to ensure relevance to various audiences
¤ Review and approve strategy and deliverables
¤ Oversee development process
¤ Assist in promoting the Guide to the Software Engineering Body of Knowledge
¤ Lend credibility to the project
© IEEE www.swebok.org21
A ThreeA Three--Phase Approach for Phase Approach for Developing the GuideDeveloping the Guide
1998 1999 2000 2001 2002 2003
Straw ManPhase
Stone Man Phase
Iron Man Phase(Sub-phase 1)
Iron ManPhase(Sub-phase 2)
Trial Version
Revision
Experimentation and Trial Usage
2004Version
© IEEE www.swebok.org22
Version Review ProcessVersion Review Process
¤ Transparency and consensus-buildingvAll intermediate versions of documents
published and archived on www.swebok.org
vAll comments made public as well as the identity of the reviewers
vDetailed comment disposition reports
© IEEE www.swebok.org23
Data on reviewersData on reviewers2001 Trial Version2001 Trial Version
¤ Version 0,1: 33
¤ Version 0,5: 195
¤ Version 0,7: 378v + ISO reviews from 5 countries
© IEEE www.swebok.org24
Reviewers (2004 Version)Reviewers (2004 Version)
¤ Comments: 1020
¤ Reviewers: 124
¤ Countries: 21
¤ + 7 countries submittedcomments through ISO voting process
¤ Adopted by + 25 ISO participating countries
4741
28
8
0
5
10
15
20
25
30
35
40
45
50
0-9 years 10-19 years 20-29 years 30-39 years
Num
ber
of R
evie
wer
s
17
48 44
13
20
10
20
30
40
50
60
0-9 years 10-19 years 20-29 years 30-39 years 40-49 years
Nu
mb
er o
f Rev
iew
ers
Years in the field
Years in industry
© IEEE www.swebok.org25
Project OverviewProject OverviewPresentation PlanPresentation Plan
¤ Project background
¤ Project development process
¤¤Contents of the GuideContents of the Guide¤ Applications of the Guide
¤ Next steps
© IEEE www.swebok.org26
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
© IEEE www.swebok.org27
Knowledge Areas and Knowledge Areas and Related DisciplinesRelated Disciplines
¤ Software Requirements
¤ Software Design
¤ Software Construction
¤ Software Testing
¤ Software Maintenance
¤ Software Configuration Management
¤ Software Eng. Management
¤ Software Eng. Tools & Methods
¤ Software Engineering Process
¤ Software Quality
• Computer Engineering • Computer Science• Mathematics• Project Management• Management• Quality Management • Software Ergonomics• Systems Engineering
Related Disciplines
© IEEE www.swebok.org28
Knowledge Area DescriptionKnowledge Area DescriptionClassification
of TopicsMatrix of Topics
& ReferencesReferences
Topic Descriptions
Classification by Vincenti’sTaxonomy
Classification by Bloom’s Taxonomy
References to Related Disciplines
Not implemented in Trial Version
© IEEE www.swebok.org29
* XLGH�WR�WKH�6RIWZ DUH�( QJLQHHULQJ�%RG\ � RI�. QRZOHGJH��UVLRQ
6RIWZDUH&RQVWUXFWLRQ
6RIWZDUH0 DLQWHQDQFH6RIWZDUH�7HVWLQJ
%DVLF�&RQFHSWVRI�&RQVWUXFWLRQ
0 DQDJLQJ&RQVWUXFWLRQ
6RIWZDUH0 DLQWHQDQFH) XQGDPHQWDOV
. H\ � ,VVXHV�LQ6RIWZDUH
0 DLQWHQDQFH
7HFKQLTXHV�IRU0 DLQWHQDQFH
6RIZDUH7HVWLQJ
) XQGDPHQWDOV
7HVW�/ HYHOV
7HVW�7HFKQLTXHV
7HVW�5 HODWHG0 HDVXUHV
7HVW3URFHVV
6RIWZDUH�' HVLJQ
6RIWZDUH�' HVLJQ) XQGDPHQWDOV
. H\ � ,VVXHV�LQ6RIWZDUH�' HVLJQ
6RIWZDUH�6 WUXFWXUHDQG�$ UFKLWHFWXUH
6RIWZDUH�' HVLJQ4 XDOLW\ � $QDO\ VLVDQG�( YDOXDWLRQ
6RIWZDUH�' HVLJQ1RWDWLRQV
6RIWZDUH5HTXLUHP HQWV
6RIWZDUH5HTXLUHP HQWV) XQGDP HQWDOV
5HTXLUHP HQWV3URFHVV
5HTXLUHP HQWV( OLFLWDWLRQ
5HTXLUHP HQWV6SHFLILFDWLRQ
5HTXLUHP HQWV9DOLGDWLRQ
5HTXLUHP HQWV$QDO\VLV
6RIWZDUH�' HVLJQ6 WUDWHJLHV�DQG
0 HWKRGV
3UDFWLFDO&RQVLGHUDWLRQV
3UDFWLFDO&RQVLGHUDWLRQV
0 DLQWHQDQFH3 URFHVV
© IEEE www.swebok.org31
Software EngineeringCulture and Ethics
Value and Costsof Quality
Quality Improvement
Verification andValidation
Software QualityAssurance
Software Quality
Software QualityFundamentals
Software QualityManagement
Processes
PracticalConsiderations
Models andQualityCharacteristics
Reviews andAudits
Application QualityRequirements
DefectCharacterization
Software QualityMeasurement
Software QualityManagementTechniques
© IEEE www.swebok.org32
Reduction of Complexity
Software Construction
Basic Conceptsof Construction
ManagingConstruction
Constructing forValidation
Anticipation of Change
Role of Standards inConstruction
Construction Languages
Coding
PracticalConsiderations
Construction Quality
Construction Testing
Integration
Construction Tools
Construction Methods
ConstructionMeasurement
Construction Planning
Construction design
Figure 1. Breakdown of topics for the Software Construction KA.
© IEEE www.swebok.org34
Summary of changes Summary of changes in 2004 Versionin 2004 Version
¤ Structural improvements in breakdown of topics: Software Construction, Management, Quality, Process
¤ Better representation of text in topic breakdown : Software Requirements, Testing, Maintenance
¤ Standardization of the contents of the chapters:v topic breakdown, terminology, reference
citations and writing style
© IEEE www.swebok.org35
Summary of changes Summary of changes in 2004 Versionin 2004 Version
¤ Better representation of standards in chapters and a new Appendix devoted to standards
¤ Updating of reference material
¤ Handling of trial usage feedback
¤ Handling of reviewers comments
¤ New chapter on Related Disciplines (instead of an appendix)
© IEEE www.swebok.org36
Presentation PlanPresentation Plan
¤¤ Project backgroundProject background
¤ Project development process
¤ Contents of the Guide
¤ Applications of the Guide in organizations
¤ Next steps
© IEEE www.swebok.org37
Applications of the GuideApplications of the Guide
¤ Licensing & Certificationv IEEE CS CSDP exam and program
v Input in accreditation of software engineering programs in engineering faculties - CCPE
vOrdre des ingénieurs du Québec:Ø Input to recognize software engineering
© IEEE www.swebok.org38
Example Usages in Example Usages in EducationEducation
¤ Program Design/Assessment:vNational Technology University
vMonash University
vCRISTEL project
¤ Course Design/Assessment: vA large number of universities
© IEEE www.swebok.org39
Applications of the GuideApplications of the Guide
¤ Industry & Governmentv Job descriptionØ Bombardier Transportation
vCareer planningØ Construx
v Input to Policy makingØ Turkish Industry Survey
© IEEE www.swebok.org40
Applications of the GuideApplications of the Guide
¤ Professional developmentvSecurity Industry Automation Corporation
vConstrux
¤ Dissiminations of standardsv Introducing standards in software
engineering curriculum
© IEEE www.swebok.org41
Presentation PlanPresentation Plan
¤¤ Project backgroundProject background
¤ Project development process
¤ Contents of the Guide
¤ Usages of the Guide in organizations
¤ Next steps
© IEEE www.swebok.org42
Next steps: Next steps:
Generally Accepted
Advanced
Spec
ializ
ed
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
© IEEE www.swebok.org43
Evolution process for the Evolution process for the GuideGuide
¤ Copyright belongs to the IEEE
¤ Transition to self-supporting, volunteer-led process—i.e. self-funded.
¤ Coordination with related IEEE-CS projects (internal and external)
¤ Time-boxed block updates
¤ Involvement with stakeholder groups
¤ Openness and transparency
¤ Technical excellence
© IEEE www.swebok.org44
NextNext StepsStepsResearch to strengthen the foundations of a body of
knowledge:
¤ Vincenti’s classification of engineering knowledgeØ Fundamental design principles
Ø Criteria and specifications
Ø Theoretical tools
Ø Quantitative data
Ø Practical considerations
Ø Design instrumentalities
¤ Ontology of software engineering
© IEEE www.swebok.org45
NextNext StepsSteps
Being investigated at ISO level:
¤ Certification of software engineersv ISO standard on content of certification
v ISO recognized certifying bodies
v International portability of certification ofsoftware engineers
© IEEE www.swebok.org46
Next stepsNext stepsConsensus on the core body of knowledge is key in
all disciplines and pivotal for the evolution toward a professional status
India: how do you improve the skills & training of software engineers?
v In industry?
vUniversity graduates?
© IEEE www.swebok.org49
Presentation PlanPresentation Plan
¤¤ Project backgroundProject background
¤ Project development process
¤ Contents of the Guide
¤ Usages of the Guide in organizations
¤ Next steps
¤ Appendix: Breakdown of topics
© IEEE www.swebok.org50
* XLGH�WR�WKH�6RIWZ DUH�( QJLQHHULQJ�%RG\ � RI�. QRZOHGJH��UVLRQ
6RIWZDUH&RQVWUXFWLRQ
6RIWZDUH0 DLQWHQDQFH6RIWZDUH�7HVWLQJ
%DVLF�&RQFHSWVRI�&RQVWUXFWLRQ
0 DQDJLQJ&RQVWUXFWLRQ
6RIWZDUH0 DLQWHQDQFH) XQGDPHQWDOV
. H\ � ,VVXHV�LQ6RIWZDUH
0 DLQWHQDQFH
7HFKQLTXHV�IRU0 DLQWHQDQFH
6RIZDUH7HVWLQJ
) XQGDPHQWDOV
7HVW�/ HYHOV
7HVW�7HFKQLTXHV
7HVW�5 HODWHG0 HDVXUHV
7HVW3URFHVV
6RIWZDUH�' HVLJQ
6RIWZDUH�' HVLJQ) XQGDPHQWDOV
. H\ � ,VVXHV�LQ6RIWZDUH�' HVLJQ
6RIWZDUH�6 WUXFWXUHDQG�$ UFKLWHFWXUH
6RIWZDUH�' HVLJQ4 XDOLW\ � $QDO\ VLVDQG�( YDOXDWLRQ
6RIWZDUH�' HVLJQ1RWDWLRQV
6RIWZDUH5HTXLUHP HQWV
6RIWZDUH5HTXLUHP HQWV) XQGDP HQWDOV
5HTXLUHP HQWV3URFHVV
5HTXLUHP HQWV( OLFLWDWLRQ
5HTXLUHP HQWV6SHFLILFDWLRQ
5HTXLUHP HQWV9DOLGDWLRQ
5HTXLUHP HQWV$QDO\VLV
6RIWZDUH�' HVLJQ6 WUDWHJLHV�DQG
0 HWKRGV
3UDFWLFDO&RQVLGHUDWLRQV
3UDFWLFDO&RQVLGHUDWLRQV
0 DLQWHQDQFH3 URFHVV
© IEEE www.swebok.org53
Software Design
1. Software DesignFundamentals
2. Key Issues inSoftware Design
3. Software Structureand Architecture
5. SoftwareDesign Notations
6. Software DesignStrategies and
Methods
General designconcepts Concurrency
The context ofsoftware design
Enabling techniques
The software designprocess
Control and handlingof events
Architecturalstructures and
viewpoints
Structuraldescriptions(static view)
General Strategies
Distribution ofcomponents
Interaction andpresentation
Error and exceptionhandline and fault
tolerance
Data persistence
Design patterns(microarchitectural
patterns)
Architectural styles(macroarchitectural
patterns)
Families of programsand frameworks
Behavior descriptions(dynamic view)
Object-orienteddesign
Function-oriented(structured) design
Data-structrurecentered design
4. Software DesignQuality Analysis and
Evaluation
Quality attributes
Measures
Quality analysis andevaluation techniques
Other methods
Figure 1 Breakdown of topics for the Software Design KA
Component-baseddesign (CBD)
© IEEE www.swebok.org54
Software Testing
1. SoftwareTesting
Fundamentals2. Test Levels
3. TestTechniques
4. Test RelatedMeasures
5. Test Process
Testing-RelatedTerminology
Keys Issues
Relationships ofTesting to Other
Activities
The Target of theTest
Objectives ofTesting
Based on tester's intuitionand experience
Specification-based
Evaluation of theProgram Under
Test
Evaluation of theTests Performed
ManagementConcerns
Test Activities
Code-based
Usage-based
Fault-based
Based on natureof application
Selecting andCombiningTechniques
© IEEE www.swebok.org55
Software Maintenance
FundamentalsKey Issues in
SoftwareMaintenance
MaintenanceProcess
Techniques forMaintenance
Definitions andTerminology
Nature ofMaintenance
Need for Maintenance
Majority ofMaintenance Costs
Evolution of Soffware
Categories ofMaintenance
Technical
Management
Maintenance Cost andMaintenance CostEstimation
Software MaintenanceMeasurement
Maintenance ProcessModels
Maintenance Activities
Program Comprehension
Re-engineering
Reverse Engineering
Impact Analysis
© IEEE www.swebok.org56
Software Configuration Management
3. SoftwareConfiguration
Control
4. SoftwareConfiguration
StatusAccounting
5. SoftwareConfiguration
Auditing
6. SoftwareRelease
Managementand Delivery
In-ProcessAudits of SCM
Requesting,Evaluating and
ApprovingSoftwareChangesSoftware
ConfigurationControl Board
Software ChangeRequest Process
ImplementingSoftwareChanges
Deviations andWaivers
SoftwareConfiguration
StatusInformation
SoftwareConfiguration
StatusReporting
SoftwareFunctional
ConfigurationAudit
SoftwarePhysical
ConfigurationAudit
In-ProcessAudits of aSoftwareBaseline
SoftwareBuilding
SoftwareRelease
Management
1. SoftwareConfigurationManagement
Fundamentals
IdentifyingItems to beControlled
SoftwareConfiguration
SoftwareConfiguration
ItemsSoftware
ConfigurationItem
RelationshipsSoftwareVersions
Baseline
AcquiringSoftware
ConfigurationItems
SoftwareLibrary
2. Keys Issuesin SCM
OrganizationalContext for
SCMConstraints and
Guidance forSCM
Planning forSCM
SoftwareConfigurationManagement
Plan
SCMOrganization andResponsibilities
SCM Resourcesand Schedules
Tool Selectionand
ImplementationVendor/
SubcontractorControl
Interface Control
Surveillance ofSoftware
ConfigurationManagementSCM Measures
andMeasurement
© IEEE www.swebok.org57
Process Planning
DetermineDeliverables
Effort, Scheduleand CostEstimation
ResourceAllocation
Risk Management
QualityManagement
Plan Management
Software EngineeringManagement
Initiation andScope Definition
Determinationand Negotiationof Requirements
FeasibilityAnalysis
Process forRequirementsReview/Revision
Software ProjectEnactment
Implementationof Plans
Supplier ContractManagement
Implementationof MeasurementProcess
Monitor Process
Control Process
Reporting
Review andEvaluation
DeterminingSatisfaction ofRequirements
Reviewing andEvaluatingPerformance
Closure
DeterminingClosure
ClosureActivities
SW EngineeringMeasurement
Establish and SustainMeasurementCommitment
Plan theMeasurementProcess
Perform theMeasurementProcess
EvaluateMeasurement
Software ProjectPlanning
© IEEE www.swebok.org58
Software EngineeringProcess
ProcessImplementation
and ChangeProcess
DefinitionProcess
Assessment
Process Infrastructure
Activities
Models for ProcessImplementation andChange
Practical Considerations
Life Cycle Models
Software Life CycleProcesses
Notations forProcess Definitions
Process Adaptation
Automation
Process AssessmentModels
Process AssessmentMethods
Process andProduct
Measurements
Process Measurement
Software ProductsMeasurement
Quality of MeasurementResults
Software InformationModels
Process MeasurementTechniques
© IEEE www.swebok.org59
Software Software EngineeringEngineeringToolsTools and and
MethodsMethods
Software Engineering Tools and Methods
I. Software Tools II. Software Methods
Software RequirementsTools
Heuristic Methods
Software Design Tools
Software ConstructionTools
Requirements modelingTraceability
Program editorsCompilersInterpretersDebuggers
Software Testing ToolsTest generators
Test execution frameworksTest evaluation
Test managementPerformance analysis
Software MaintenanceTools
ComprehensionRe-engineering
Software EngineeringProcess ToolsProcess modeling
Process managementIntegrated CASE environments
Process-centered softwareengineering environments
Inspection
Software Quality Tools
Static analysis
Software ConfigurationManagement Tools
Defect, enhancement, issue andproblem tracking
Version managmentRelease and build
Software EngineeringManagement Tools
Project planning and trackingRisk management
Measurement
Infrastructure SupportTools
Miscellaneous ToolsIssues
Formal Methods
Interpersonal communicationInformation retrieval
System administrative andsupport
Tool integration techniquesMeta tools
Tool evaluation
Structured methods
Data-oriented methods
Object-oriented methods
Domain specific methods
Specification languages
Refinement
Verification
Prototyping Methods
Miscellaneous MethodIssues
StylesPrototyping target
Evaluation techniques
Method evaluation
© IEEE www.swebok.org60
List of Knowledge AreasList of Knowledge Areas¤ Software Requirements
¤ Software Design
¤ Software Construction
¤ Software Testing
¤ Software Maintenance
¤ Software Configuration Management¤ Software Quality
¤ Software Engineering Tools & Methods
¤ Software Engineering Process
¤ Software Engineering Management
© IEEE www.swebok.org61
Formal resolutionsFormal resolutions¤ Industrial Advisory Board (2001)¤ IEEE CS Board of Governors (2001)
v "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)v Officially approved the 2004 Version
¤ ISO Technical Report 19759 (upcoming)
© IEEE www.swebok.org62
Trial Version Review ProcessTrial Version Review Process
Version 0.1
ReviewCycle 1
Version 0.5
Reviewcycle 2
Version 0.7
ReviewCycle 3
Version 0.9
Limited number of domain experts
Selected users
Community
© IEEE www.swebok.org65
GeographicGeographic Distribution Distribution ofof ReviewersReviewersTrial VersionTrial Version
¤ USA: 55%
¤ Europe: 18% v 90 reviewers from 25 countries
¤ Canada: 10%
¤ Australia: 5%
¤ Asia: 5%
¤ Latin America: 4%
© IEEE www.swebok.org66
Education level of reviewers Education level of reviewers (Version 0,7)(Version 0,7)
34%
39%
24% 3%Ph.D.MastersBachOther
© IEEE www.swebok.org67
Number of employees at Number of employees at reviewer location (Version 0,7)reviewer location (Version 0,7)
37%
32%
31%0-5050-500Over 500
Top Related