introduction to the swebok guide and...

1

© IEEE www.swebok.org1

Introduction to the SWEBOK Introduction to the SWEBOK Guide and ProjectGuide and Project

Pierre BourquePierre Bourque

Internet Seminar given to 3IL StudentsInternet Seminar given to 3IL Students20 March 200720 March 2007SW

EBO

K

ÉTS


Project managed by:

Corporate Support by:

2


IEEE Computer SocietyIEEE Computer Society

Institute of Electrical and Electronics Engineers:

360,000 members in 175 countries.

Publishes 30% of the world’s technical literature within its scope of interest.

The Computer Society is the largest of IEEE’s 37 technical societies:

100,000 members, 40% outside the US.

Founded in 1946, the world’s oldest and largest association of computing professionals.


Trial Version (2001)Trial Version (2001)

3


2004 Version2004 Version


Guide to the Software Engineering Guide to the Software Engineering Body of Knowledge (SWEBOKBody of Knowledge (SWEBOK®®))

Began as a collaboration among IEEE CS, ACM and the Université du Québec à MontréalInternational participation from industry, professional societies, standards bodies, academia, authorsOver 500 hundred software engineering professionals have touched the documentRelease of Trial Version in 2001

® Registered in U.S. Patent Office

4


2004 SWEBOK Guide2004 SWEBOK GuideAvailable on www.swebok.orgThe 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 2004Also published in book form by the IEEE Computer Society Press and in Japanese by OhmshaAlso published as ISO Technical Report 19759Current draft versions in Arabic, French and Spanish


List of Knowledge AreasList of Knowledge AreasSoftware RequirementsSoftware DesignSoftware ConstructionSoftware TestingSoftware MaintenanceSoftware Configuration ManagementSoftware QualitySoftware Engineering Tools & MethodsSoftware Engineering ProcessSoftware Engineering Management

5


Presentation ObjectivesPresentation Objectives

Give an overview of the emerging international consensus on the “core body of knowledge” of software engineeringBriefly present the development process used to reach this emerging consensus


Presentation PlanPresentation Plan

Project backgroundProject backgroundProject scope, objectives, audience and development processContents of the GuideEvolution of the GuideConclusionAppendix: Breakdown of topics

6


What is Software What is Software Engineering?Engineering?

IEEE 610.12:“(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.(2) The study of approaches as in (1).”


Recognized Profession?Recognized Profession?

Starr*:Knowledge and competence validated by the community of peersConsensually validated knowledge rests on rational, scientific groundsJudgment and advice oriented toward a set of substantive values

* P. Starr, The Social Transformation of American Medicine: BasicBooks, 1982.

7


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



Project background

Project scope, objectives, audience Project scope, objectives, audience and development processand development processContents of the GuideHow you can leverage the Guide within your organizationEvolution of the GuideConclusionBreakdown of topics

8


Project ObjectivesProject Objectives

Characterize the contents of the Software Engineering Body of KnowledgeProvide a topical access to the Software Engineering Body of KnowledgePromote a consistent view of software engineering worldwide


Project ObjectivesProject ObjectivesClarify 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

9


Intended AudienceIntended Audience

Public and private organizationsPracticing software engineersMakers of public policyProfessional societiesSoftware engineering studentsEducators and trainers


What Are we Not Trying What Are we Not Trying to Accomplish?to Accomplish?

Not a curriculum development effort!Not an all-inclusive description of the sum of knowledge in the fieldNot all categories of knowledge

10


Categories of Knowledge Categories of Knowledge in the SWEBOKin the SWEBOK

GenerallyAcceptedAdvanced

Spec

ializ

ed

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


Maths

Applicationdomain

knowledgeAdvanced

SEKnowledge

Guide to theSWEBOKStoneman

C.S.

...

Knowledgeof a

SoftwareEngineer

SpecializedSE

Knowledge

11


Three Underlying Principles Three Underlying Principles of the Projectof the Project

Transparency: the development process is itself published and fully documentedConsensus-building: the development process is designed to build, over time, consensus in industry, among professional societies and standards-setting bodies and in academiaAvailable free on the web


Project TeamProject Team

Editorial Team of the GuideIndustrial Advisory BoardAssociate Editors of the Knowledge AreasReviewers

12


Roles of the Industrial Roles of the Industrial Advisory BoardAdvisory Board

Provide input to ensure relevance to various audiencesReview and approve strategy and deliverablesOversee development processAssist in promoting the Guide to the Software Engineering Body of KnowledgeLend credibility to the project


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)

2004Version

2004Version

TrialVersion

TrialVersion

13


Formal resolutionsFormal resolutionsIndustrial 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

Official recognition as ISO Technical Report 19759


Trial Version Review ProcessTrial Version Review ProcessVersion 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

14


Trial Version Review ProcessTrial Version Review Process

Transparency and consensus-buildingAll intermediate versions of documents are published and archived on www.swebok.orgAll comments are made public as well as the identity of the reviewersDetailed comment disposition reports are produced for Review Cycle 2 and 3


15


Comment ResolutionComment Resolution


Data on reviewersData on reviewersTrial VersionTrial Version

Version 0,1: 33

Version 0,5: 195

Version 0,7: 378+ ISO reviews from 5 countries

16


GeographicGeographic Distribution of Distribution of ReviewersReviewersTrial VersionTrial Version

USA: 55%Europe: 18%

90 reviewers from 25 countries

Canada: 10%Australia: 5%Asia: 5%Latin America: 4%


Education level of reviewers Education level of reviewers (Version 0,7)(Version 0,7)

34%

39%

24% 3%Ph.D.MastersBachOther

17


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


Number of years of practical Number of years of practical experience (Version 0,7)experience (Version 0,7)

32%

38%

21%

9%

0-9

10-19

20-29

18


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 VersionTrial Version

Revision

Experimentation and Trial Usage

2004Version

2004Version


Reviewers (2004 Version)Reviewers (2004 Version)Registered reviewers: 573Number of countries: 55Number of comments: 1020Number of reviewers submitting comments: 124Number of represented countries: 21

4741

28

8

05

101520253035404550

0-9 years 10-19 years 20-29 years 30-39 years

Num

ber o

f Rev

iew

ers

17

48 44

132

0

10

20

30

40

50

60

0-9 years 10-19 years 20-29 years 30-39 years 40-49 years

Num

ber o

f Rev

iew

ers

Years in the field

Years in industry

19


Project OverviewProject OverviewPresentation PlanPresentation Plan

Project backgroundProject scope, objectives, audience and development process

Contents of the GuideContents of the GuideEvolution of the GuideConclusionAppendix: Breakdown of topics


Deliverables:Deliverables:Consensus on a list of Knowledge AreasConsensus on a list of topics and relevant reference materials for each Knowledge AreaConsensus on a list of Related Disciplines

20


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


Knowledge Area DescriptionKnowledge Area DescriptionClassification

of TopicsMatrix of Topics

& ReferencesReferences

Topic Descriptions

Classification by Vincenti’s

Taxonomy

Classification by Bloom’s Taxonomy

References to Related Disciplines

Not implemented

21


Guide to the Software Engineering Body of Knowledge2004 Version

SoftwareConstruction

SoftwareMaintenanceSoftware Testing

Basic Conceptsof Construction

ManagingConstruction

SoftwareMaintenance

Fundamentals

Key Issues inSoftware

Maintenance

Techniques forMaintenance

SofwareTesting

Fundamentals

Test Levels

Test Techniques

Test RelatedMeasures

TestProcess

Software Design

Software DesignFundamentals

Key Issues inSoftware Design

Software Structureand Architecture

Software DesignQuality Analysisand Evaluation

Software DesignNotations

SoftwareRequirements

SoftwareRequirementsFundamentals

RequirementsProcess

RequirementsElicitation

RequirementsSpecification

RequirementsValidation

RequirementsAnalysis

Software DesignStrategies and

Methods

PracticalConsiderations


MaintenanceProcess


RelatedDisciplines

ComputerScience

Management

Mathematics

Projectmanagement

Qualitymanagement

SoftwareErgonomics

Systemsengineering

Closure

ProcessAssessment

Software Design Tools

Guide to the Software Engineering Body of Knowledge

(2004 Version)

SoftwareConfigurationManagement

SoftwareEngineering Tools

and Methods

SoftwareEngineering

ProcessSoftware Quality

SoftwareConfigurationManagementFundamentals

KeysIssues in

SCM

SoftwareConfiguration

Control


Status Accounting


Auditing

Software ReleaseManagement and

Delivery Software Methods

Software ToolsProcess

Implementationand Change

Process andProduct

Measurement

Software QualityFundamentals

Software QualityManagement

Processes

Heuristic Methods

Formal Methods

Prototyping Methods

Software RequirementsTools

Software Testing Tools

Software MaintenanceTools

Software EngineeringProcess Tools

ProcessDefinition


Software ConstructionTools

Software Quality Tools

Software ConfigurationManagement Tools

Software EngineeringManagement Tools

Infrastructure SupportTools

Miscellaneous ToolIssues

Miscellaneous MethodIssues

SoftwareEngineeringManagement

Initiation andScope

Definition

SoftwareProject

Planning

Software ProjectEnactment

Review andEvaluation

SW EngineeringMeasurement

ComputerEngineering

22



Summary of changes Summary of changes in 2004 Versionin 2004 Version

Standardization of the contents of the chapters in terms of table of contents, topic breakdown, terminology, reference citations and writing styleStructural improvements in breakdown of topics: Software Construction, Software Engineering Management, Software Quality, Software Engineering ProcessBetter representation of text in topic breakdown : Software Requirements, Software Testing, Software Maintenance

23


Summary of changes Summary of changes in 2004 Versionin 2004 Version

New chapter on Related Disciplines (instead of an appendix)Better representation of standards in chapters and a new Appendix devoted to standardsUpdating of reference materialHandling of trial usage feedbackHandling of reviewer comments



Project backgroundProject backgroundProject scope, objectives, audience and development processContents of the Guide

Evolution of the GuideConclusionAppendix: Breakdown of topics

24


Evolution of the SWEBOK Evolution of the SWEBOK GuideGuide

Next planned version is 2009Main focus of changes

Harmonization of IEEE software engineering professional products with the SWEBOK Guide as the cornerstone

Time-boxed block updatesTo ensure currencyTo permit structural evolution while ensuring internal consistencyTo permit synchronization with coordinated effortsTo allow “follower” efforts to perform their own planning


Evolution of the SWEBOK Evolution of the SWEBOK GuideGuide

Involvement with stakeholder groupsTo support existing audiences

Openness and transparencyTo appeal to new audiencesTo give credibility to the product

Technical excellence

25



Project backgroundProject backgroundProject scope, objectives, audience and development processContents of the GuideHow you can leverage the Guide within your organizationEvolution of the Guide

ConclusionAppendix: Breakdown of topics


Concluding RemarksConcluding Remarks

Consensus on the core body of knowledge is key in all disciplines and pivotal for the evolution toward a professional status

26


www.swebok.orgwww.swebok.org



Project backgroundProject backgroundProject scope, objectives, audience and development processContents of the GuideHow you can leverage the Guide within your organizationEvolution of the GuideConclusion

Appendix: Breakdown of topics

27


Guide to the Software Engineering Body of Knowledge2004 Version

SoftwareConstruction

SoftwareMaintenanceSoftware Testing



SoftwareMaintenance

Fundamentals

Key Issues inSoftware

Maintenance

Techniques forMaintenance

SofwareTesting

Fundamentals

Test Levels

Test Techniques

Test RelatedMeasures

TestProcess

Software Design

Software DesignFundamentals

Key Issues inSoftware Design

Software Structureand Architecture

Software DesignQuality Analysisand Evaluation

Software DesignNotations

SoftwareRequirements

SoftwareRequirementsFundamentals

RequirementsProcess

RequirementsElicitation

RequirementsSpecification

RequirementsValidation

RequirementsAnalysis

Software DesignStrategies and

Methods



MaintenanceProcess


RelatedDisciplines

ComputerScience

Management

Mathematics

Projectmanagement

Qualitymanagement

SoftwareErgonomics

Systemsengineering

Closure

ProcessAssessment


Guide to the Software Engineering Body of Knowledge

(2004 Version)


SoftwareEngineering Tools

and Methods

SoftwareEngineering

ProcessSoftware Quality

SoftwareConfigurationManagementFundamentals

KeysIssues in

SCM


Control


Status Accounting


Auditing

Software ReleaseManagement and

Delivery Software Methods

Software ToolsProcess

Implementationand Change

Process andProduct

Measurement



Processes

Heuristic Methods

Formal Methods

Prototyping Methods


Software Testing Tools


Software EngineeringProcess Tools

ProcessDefinition




Software ConfigurationManagement Tools


Infrastructure SupportTools

Miscellaneous ToolIssues


SoftwareEngineeringManagement

Initiation andScope

Definition

SoftwareProject

Planning




ComputerEngineering

28



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-oriented

design

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)

29


Reduction of Complexity

Software Construction



Constructing forValidation

Anticipation of Change

Role of Standards inConstruction

Construction Languages

Coding


Construction Quality

Construction Testing

Integration

Construction Tools

Construction Methods

ConstructionMeasurement

Construction Planning

Construction design

Figure 1. Breakdown of topics for the Software Construction KA.


Software Testing

1. SoftwareTesting

Fundamentals2. Test Levels 3. Test

Techniques4. Test Related

Measures 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

30


Software Maintenance

Fundamen talsKey Issu es in

SoftwareMainten ance

Main ten anceProcess

Techn iqu es forMain ten ance

Definitions andTerm inology

Nature ofM aintenance

Need for Maintenance

M ajority ofM aintenance Costs

Evolution of Soffware

C ategories ofM aintenance

Technical

M anagem ent

M aintenance C ost andM aintenance C ostEstim ation

S oftware M aintenanceM easurement

M aintenance P rocessM odels

M aintenance Activities

P rogram C om prehension

Re-engineering

Reverse Engineering

Impact Analysis


Software Configuration Management

3. SoftwareConfiguration

Control


StatusAccounting


Auditing

6. SoftwareRelease

Managementand Delivery

In-ProcessAudits of SCM

Requesting,Evaluating and

ApprovingSoftwareChangesSoftware

ConfigurationControl Board

Software ChangeRequest Process

ImplementingSoftwareChanges

Deviations andWaivers


StatusInformation


StatusReporting

SoftwareFunctional

ConfigurationAudit

SoftwarePhysical

ConfigurationAudit

In-ProcessAudits of aSoftwareBaseline

SoftwareBuilding

SoftwareRelease

Management

1. SoftwareConfigurationManagement

Fundamentals

IdentifyingItems to beControlled



ItemsSoftware

ConfigurationItem

RelationshipsSoftwareVersions

BaselineAcquiringSoftware

ConfigurationItems

SoftwareLibrary

2. Keys Issuesin SCM

OrganizationalContext for

SCMConstraints and

Guidance forSCM

Planning forSCM


Plan

SCMOrganization andResponsibilities

SCM Resourcesand Schedules

Tool Selectionand

ImplementationVendor/

SubcontractorControl

Interface Control

Surveillance ofSoftware

ConfigurationManagementSCM Measures

andMeasurement

31


Process Planning

DetermineDeliverables

Effort, Scheduleand CostEstimation

ResourceAllocation

Risk Management

QualityManagement

Plan Management

Software EngineeringManagement

Initiation andScope Definition

Determinationand Negotiationof Requirements

FeasibilityAnalysis

Process forRequirementsReview/Revision


Implementationof Plans

Supplier ContractManagement

Implementationof MeasurementProcess

Monitor Process

Control Process

Reporting


DeterminingSatisfaction ofRequirements

Reviewing andEvaluatingPerformance

Closure

DeterminingClosure

ClosureActivities


Establish and SustainMeasurementCommitment

Plan theMeasurementProcess

Perform theMeasurementProcess

EvaluateMeasurement

Software ProjectPlanning


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

32


Software Software EngineeringEngineeringTools and Tools and

MethodsMethods

Software Engineering Tools and Methods

I. Software Tools II. Software Methods


Heuristic Methods



Requirements modelingTraceability

Program editorsCompilersInterpretersDebuggers

Software Testing ToolsTest generators

Test execution frameworksTest evaluation

Test managementPerformance analysis


ComprehensionRe-engineering

Software EngineeringProcess ToolsProcess modeling

Process managementIntegrated CASE environments

Process-centered softwareengineering environments

Inspection


Static analysisSoftware Configuration

Management ToolsDefect, enhancement, issue and

problem trackingVersion managmentRelease and build


Project planning and trackingRisk management

MeasurementInfrastructure Support

Tools

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


StylesPrototyping target

Evaluation techniques

Method evaluation


Software EngineeringCulture and Ethics

Value and Costsof Quality

Quality Improvement

Verification andValidation

Software QualityAssurance

Software Quality



Processes


Models andQualityCharacteristics

Reviews andAudits

Application QualityRequirements

DefectCharacterization

Software QualityMeasurement

Software QualityManagementTechniques

introduction to the swebok guide and...

Documents