april 2003stcjames w. moore - 1 making software development a professional discipline: the ieee...

April 2003 STC James W. Moore - 1

Making Software Development a Making Software Development a Professional Discipline:Professional Discipline:

The IEEE Computer Society’s ProgramThe IEEE Computer Society’s Program

James W. MooreThe MITRE Corporation

May 2003

The opinions contained in this presentation are those of the author and do not necessarily represent those of The MITRE Corporation or its sponsors.


From Grady Booch,From Grady Booch,The Future of SoftwareThe Future of Software

2

The Future Of Software Engineering

Technical– The dominance of component-based software

engineering– The codification of reference architectures– The evolution of virtual teams– The acceptance of well-defined processes– The creation of frictionless surfaces– The rise of software engineering as a profession

Social– The impact of legal issues– The scarcity of skilled workers– The growth of non-programmers


From Grady Booch,From Grady Booch,The Future of SoftwareThe Future of Software

3

The Growth Of Non-Programmers

World-wide, there exist approximately 12million developers Gartner Group

Like the telephone network, new classesof developers will emerge– Content creators– Information architects– End users

When I was a young teenager in the early1960s, there weren't many programmers in

the world. Now everybody needs to be aprogrammer.

Brian Reid

In 10 years, the world will have 100 millionuser-programmers -- and 44% of their

programs will continue to have missioncritical bugs. We sorely need the

equivalent of seat belts and air bags foruser-programmers.

Barry Boehm

"Software Engineering" will have no futureunless we accept the fact that only a small

fraction of software developers arequalified to be called "Software Engineers“

and agree on standards that distinguishthose who are qualified from the rest of us.

David Parnas


What is Software Engineering?What is Software Engineering?

(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).

-- IEEE Std 610.12


Model of the Maturity Model of the Maturity of a Professionof a Profession

Education Accreditation Skills development Licensing/certification Professional development Code of ethics Professional society or

societies

G. Ford and N. E. Gibbs, A Mature Profession of Software Engineering, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pennsylvania, Technical CMU/SEI-96-TR-004, January 1996.


Individual Engineer’s Development

Initial professional education

Skills Development

One or both

Full Professional

Status

Certification Licensing

Infrastructure Support for the Profession

Accreditation

Professional development programs

Code of ethics

Professional Societies

Adapted from Steve McConnell, After the Gold Rush, Microsoft Press

Software Engineering as a Software Engineering as a Profession: A ModelProfession: A Model

Adapted from Steve McConnell, After the Gold Rush, Microsoft Press, 1999, p. 93


Software Engineering is Becoming Software Engineering is Becoming Recognized as an Engineering ProfessionRecognized as an Engineering Profession

IEEE-CS/ACM Computing Curriculum 2001 completed. Basic curriculum is completed. Four specialty volumes are planned: Computer Science, Computer Engineering, Software Engineering, Information Systems.

Merger of CSAB and ABET completed. A single organization now accredits all university programs in computer science, information systems, software engineering and computer engineering.

RIT granted the first-in-US Software Engineering bachelor degrees in 2001. (Degree requires five years, including coop work.) Accreditation process is now underway.

IEEE-CS Software Engineering Body of Knowledge published in book form. Trial usage is underway leading to revision circa 2004. Several universities are using it to rationalize curriculum, e.g. SMU, NTU, NJIT.

Licensing of software engineers underway in Texas, BC, Ontario, Quebec, other countries.


IEEE CS Support of the ProfessionalIEEE CS Support of the Professional

Professional Development


Skills Development

Possibly

Full Professional

Status


Necessary Infrastructure Support

Example Products and Services of Professional

Societies


Curricula CC2001, CCSE

Accreditation ABET/CSAB

Body of knowledge SWEBOK

Prof. literature IT Pro, Software

Prof. interaction Chapters,Elec. Communities

Prof. training DVP, Tutorials,Distance Learning

Design solutions Standards, Workshops

Practice norms Standards,Best Practices

Ethical norms Code of Ethics

Prof. certification CSDP


Software Engineering Body Software Engineering Body of Knowledge Projectof Knowledge Project


Software Engineering Body of Software Engineering Body of Knowledge: Project ObjectivesKnowledge: 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 - SWEBOK

Provide a topical access to the Software Engineering Body of Knowledge

Provide a foundation for curriculum development and individual certification and licensing material


Key Interrelationships for a Key Interrelationships for a Core Body of KnowledgeCore Body of Knowledge

Development of Software

Engineering Curricula

Development of Certification /

Licensing Criteria and Exams

Development of University Program

Accreditation Criteria

Consensus on a Core Body of KnowledgeIn

fluen

ces Influences

Influences


Project OrganizationProject Organization

Editorial team Project “Champion”:

Leonard Tripp, 1999 President, IEEE Computer Society

Executive Editors: Alain Abran, École de Technologie Supérieure James W. Moore, The MITRE Corp.

Editors: Pierre Bourque, École de Technologie

Supérieure Robert Dupuis, UQAM

Industrial Advisory Board Provided funding so that the SWEBOK

Guide will always be free. Provided practical advice Provided early feedback

Knowledge Area Specialists Pete Sawyer & Gerald Kotonya, UK Guy Tremblay, Canada Terry Bollinger, USA, Louis Martin & Philippe Gabrini,

Canada Antonia Bertolino, Italy Tom Pigoski, USA John Scott & David Nisse, USA Stephen MacDonell & Andrew Gray, New Zealand Khaled El Emam, Canada David Carrington, Australia Dolores Wallace & Larry Reeker, USA

Reviewers Three review cycles Approximately 500 reviewers, 42 countries Approximately 10,000 comments


Project managed by:

Corporate Support by:

Industrial Advisory BoardIndustrial Advisory Board


Reviewer DemographicsReviewer Demographics

Level of Education

DoctorMasterBachelorOther

USA

Europe

Canada

Australia

Asia

L. America

Unknown

Number of Employees

0-5050-500500+

Version 0.1: 33 reviewers

Version 0.5: 195 reviewers

Version 0.7: 378 + 5 ISO nations


What What Software Software

Engineers Engineers Should Should KnowKnow

Math

ApplicationDomain

KnowledgeAdvanced

SWEKnowledge

Guide to theSWEBOK

C.S.

etc.

SpecializedSWE

Knowledge


Types of Knowledge Types of Knowledge

GenerallyAccepted

Advanced

Sp

ecia

lized

andResearch

Focus of the SWEBOK Guide

Generally accepted: “Applies to most projects most of the time and widespread consensus validates its value and effectiveness.” -- PMI

In operational terms, we target the SWEBOK at bachelor’s degree plus four years of experience.


Knowledge Areas Knowledge Areas

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 Science• Mathematics• Project Management• Computer Engineering• Cognitive Sciences• Human Factors• Systems Engineering• Management• Management Science

Related Disciplines


Knowledge Area DescriptionKnowledge Area Description

Classification of Topics

Matrix of Topics & References

References

Topic Descriptions

Classification by Vincenti’s

Taxonomy

Classification by Bloom’s Taxonomy

References to Related Disciplines

Not implemented in Stoneman


ProcessMeasurement

Software Design Tools

Guide to the Softw are Engineering Body of Knowledge(Version 0.95)

SoftwareConfigurationManagement

SoftwareConstruction

SoftwareEngineering Tools

and Methods

SoftwareEngineering

Process

SoftwareMaintenance Software QualitySoftware Testing

Management ofthe SCM Process

SoftwareConfigurationIdentification

SoftwareConfiguration

Control


Status Accounting


Auditing

Software ReleaseManagement and

Delivery

Reduction inComplexity

Anticipation ofDiversity

Software Methods

Software ToolsSoftware

EngineeringProcess Concepts

Process Definition

ProcessImplementation

and Change

Basic Concepts

MaintenanceProcess

Key Issues inSoftware

Maintenance

Techniques forMaintenance

Software QualityConcepts

Definition &Planning for Quality

Testing BasicConcepts and

Definitions

Test Levels

Test Techniques

Test-RelatedMeasures

Managing the TestProcess

Linguistic ConstructionMethods

Formal ConstructionMethods

Visual ConstructionMethods

Heuristic Methods

Formal Methods

Prototyping Methods

Software RequirementsTools

Software Testing Tools

Software MaintenanceTools

Software EngineeringProcess Tools

ProcessInfrastructure

Qualitative ProcessAnalysis

TechniquesRequiring Two or

More People

Support to OtherTechniques

Testing Special toSQA or V&V

Software ConstructionTools

Software Quality Tools

Software ConfigurationManagement Tools

Software EngineeringManagement Tools

Infrastructure SupportTools

Miscellaneous ToolIssues

Miscellaneous MethodIssues

Software Design

Software DesignBasic Concepts

Key Issues inSoftware Design

Software Structureand Architecture

Software DesignQuality Analysisand Evaluation

Software DesignNotations

SoftwareRequirements

RequirementEngineering

Process

RequirementsElicitation

RequirementAnalysis

RequirementsValidation

RequirementsManagement

RequirementsSpecification

SoftwareEngineeringManagement

OrganizationalManagement

Process/ProjectManagement

SoftwareEngineering

Measurement

Software DesignStrategies and

Methods

Defect FindingTechniques

Measurement inSoftware Quality

Analysis




Structuring forValidation




Use of ExternalStandards




Overall SWEBOK GuideOverall SWEBOK Guide


Uptake of SWEBOKUptake of SWEBOK

1999-2002: 32 conferences and workshops: North America Europe Australia, New Zealand,

Argentina, …

Editorial team presentations: USA, Canada, Spain, Brazil,

Japan, China, …

2370 references to SWEBOK on Web in March 2003 University

Software Engineering curriculum

University lectures Research Papers

Professional development Conferences & Workshops Certification & Licensing Government & Policy

organizations Individualshttp://www.swebok.org


Examples of SWEBOK UptakeExamples of SWEBOK Uptake

CSDP, CC2001/SE, and planned CS SW Portal are traceable to SWEBOK. A large defense contractor has experimented with the Guide to calibrate skills descriptions in

proposals. An FFRDC has rewritten its “Software Systems Engineer” job description in terms of the

SWEBOK knowledge areas. Construx, Inc. has rewritten its position descriptions in terms of the Guide, structures its

professional development around the Guide. NTU and SMU have rationalized their software engineering offerings using the SWEBOK. SWEBOK provides the taxonomical basis for VISEK, a SWE Portal funded by the German

government. SWEBOK contributed to “SW Development” portion of a BOK developed by the Canadian

Council of Professional Engineers for use in provincial licensing programs. SWEBOK influenced (how much?) IFIP committee on IT professionalism. International Organization for Standardization (ISO) is adopting SWEBOK as a “Technical

Report.”


Software Engineering Software Engineering StandardsStandards


Roles of Software Roles of Software Engineering StandardsEngineering Standards

Specify techniques to develop software faster, cheaper, better, IEEE 982.1 (Measures for Reliable SW)

Provide consensus validity for “best practices” that cannot be scientifically validated, IEEE 1008 (Unit Testing)

Provide a systematic treatment of “ilities”, IEEE 730 (SW Quality Assurance)

Provide uniformity in cases where agreement is more important than small improvements, IEEE P1320.1 (IDEF0)

Provide a framework for communication between buyer and seller, IEEE/EIA 12207 (SW Life Cycle Processes)

Give precise names to concepts that are fuzzy, complex, detailed and multidimensional, IEEE 1028 (SW Reviews)

More exciting

More effective


A standard is a name for an A standard is a name for an otherwise fuzzy conceptotherwise fuzzy concept

In a complex, multidimensional trade space of solutions ...

… a standard gives a name to a bounded region.

It defines some characteristics that a buyer can count on.


Software EngineeringSoftware EngineeringStandards in ContextStandards in Context

SWE Body of Knowledge

Fundamental Principles

ISO/IEC

Integrating FrameworkIEEE

DoDISO/IEC

Umbrella Standard(s)IEEE

ISO/IEC

Integrated Collection of Practice StandardsIEEE

Motivate

Education

Certification

Practice

Body of Standards

Quality Management

Project Management

System Engineering

Process Definition

Process Assessment

Process Measurement

Best Practices Competency Certification

Organizational Adoption

Buyer/Seller Agreement

Critical System Assurance

Dependability


Standards should Balance Standards should Balance Principles and PracticePrinciples and Practice

StandardsObserved “Best” Practices

A priori Principles

Standards should exist in a “tension” balancing the integrating and organizing forces of a priori principles with the messy real-world

demands of observed effective practices.

In many cases, a priori considerations are provided by science and mathematics. Sometimes they are provided by custom or by

marketing forces. In the case of software engineering, we have to invent them.


Principes fondamentaux du Principes fondamentaux du ggénie logicielnie logiciel

Principlesof Engineering

and otherDisciplines

Principlesof

SoftwareEngineering

PracticeStandards

Implemented“Best”

Practices

SWE Principles are specific cases of

general engineering principles.

SWE Principles organize, explain and validate the

practice standards.

Practices are deployed based on

the practice standards.

Some SWE Principles may be

generalized to principles for the

engineering of complex systems.

SWE Principles should be

“abstractions” of practice standards.

Practice standards should be recordings

of observed best practices.

A collaboration between the IEEE Computer Society and the Université du Québec à Montréal and the École de Technologie Supérieure.

Source: [Jabir97]


Examples of Fundamental Examples of Fundamental PrinciplesPrinciples

Currently, 16 candidates. Examples are … Since change is inherent in software, plan for it and

manage it.

Comme le logiciel est, de par sa nature même, sujet au changement, il faut planifier et gérer ce changement.

Since tradeoffs are inherent to SWE, make them explicit and document them.

Les compromis étant inhérents au GL, il faut les rendre explicites et les documenter.

Source: [Dupuis97]


Certified Software Certified Software Development ProfessionalDevelopment Professional


CertificationCertification

There are now 185,000 Certified Novell Engineers and 267,000 Microsoft Certified Software Engineers.

Market projected at $4B by 2004. (IT training market $34B.) There are certification trainers, vendors, consultants and magazines.

Certification is a voluntarily gained recognition by peers. There are 3 types: professional, product-related, training-related.

Certification ≠ Licensing ≠ Accreditation IT certifications have exploded from about 200 to more than 400

in three years.


IT CertificationsIT Certifications

IDC reports nine-month payback on company investment.

Who was the big winner? Answer to come.

Information Week reports bonus pay growing for certifications (and falling for non-certified skills). Median bonus for certified IT skill in 4Q01 was 8.3% of base pay.


Impact of Certification: Impact of Certification: The PMI ExampleThe PMI Example

Project Management Institute (100K members growing at 20-30% per year) offers a Project Management Professional (PMP) certification.

PMP is based on education, experience, examination, plus adherence to code of conduct.

PMI provides PMBOK, self-assessment material, books, training courses, seminars, and examination. Process is ISO 9001 certified.

Success: 30,000 PMPs in 26 countries. Many employers (e.g. State of California)

require it of project managers. Salary bonus for PMP is top one surveyed – median bonus is 14% of base pay.


IEEE CS Certified Software IEEE CS Certified Software Development ProfessionalDevelopment Professional

IEEE Computer Society has rolled out the Certified Software Development Professional (CSDP) program.

Possesses fundamental knowledge and understanding of computing principles and concepts and their application to the definition, design, construction, testing, and maintenance of software. Is able to provide appropriate design with technical and economic tradeoffs of modules, subsystems, and systems in accordance with standards of practice, specifications, and principles of behavior of software as required to perform the functions as stated in the software requirements.

Computer Society web site for CSDP:http://www.computer.org/certification

http://www.computer.org/certification




IEEE Computer Society CSDPIEEE Computer Society CSDP Certification based:

education, experience (9000 hours), examination, code of ethics, and continuing education.

Exam based on a Body of Knowledge and professional standards – 3.5 hours, 180 questions.

Developed with Chauncey Group (a subsidiary of Educational Testing Service) to be fair, reliable and valid.

First test in April 2002. About 250 certifications to date.


Examination DevelopmentExamination Development

Exam Specification

Determine content weights

Job AnalysisDescribe the job domain

Identify needed skills

Exam questionsWrite questions

Review at workshop

Validate examBeta test

Analyze questionsSet cut score

Assemble examSelect questions according

to content weightsReview results

Approval by IEEE


Requirements for CSDP Requirements for CSDP CertificationCertification

Education Bachelor or equivalent university degree

Experience 9000 hours of experience in 6 of the 11 Software Engineering

Knowledge Areas

Proof of Professionalism Review and acknowledge the Software Engineering Code of

Ethics and Professional Practice

Examination Pass the CSDP written examination


11 Knowledge Areas for CSDP11 Knowledge Areas for CSDP

Software Requirements Software Design Software Construction Software Testing Software Maintenance Software Configuration Management Software Engineering Management Software Engineering Process Software Tools and Methods Software Quality Business Practices & Engineering Economics

Same as SWEBOK

plus


Approximate Distribution of Approximate Distribution of QuestionsQuestions

Business4% Reqmts

14%

Design23%

Construction11%

Testing16%

Maintenance4%

CM4%

Mgmt11%

Process 3%

Tools/Methods3%

Quality7%


Examination Topics (1 of 4)Examination Topics (1 of 4)

Business Practices and Engineering Economics (3-4%)

• Economics

• Ethics

• Professional Practice

• Standards

Software Requirements (13-15%)

• Requirements engineering process

• Requirements elicitation

• Requirements analysis

• SW requirements specification

• Requirements validation

• Requirements management

Software Design (22-24%)

• SW design concepts

• SW architecture

• SW design quality analysis and evaluation

• SW design notations and documentation

• SW design strategies and methods

• Human factors in SW design

• SW and system safety



Software Construction (10-12%)

• Construction planning

• Code design

• Data design and management

• Error processing

• Source code organization

• Code documentation

• Construction QA

• System integration and deployment

• Code tuning

• Construction tools

Software Testing (15-17%)

• Types of tests

• Test levels

• Testing strategies

• Test design

• Test coverage of code

• Test coverage of specifications

• Test execution

• Test documentation

• Test management



Software Maintenance (3-5%)

• SW maintainability

• SW maintenance process

• SW maintenance measurement

• SW maintenance planning

• SW maintenance management

• SW maintenance documentation

Software Engineering Management(10-12%)

• Measurement

• Organization management and coordination

• Initiation and scope definition

• Planning

• Software acquisition

• Enactment

• Risk management

• Review and evaluation

• Project closeout

• Post-closure activities

Software Configuration Mgmt (3-4%)

• Management of SCM process

• SW configuration identification

• SW configuration control

• SW configuration status accounting

• SW configuration auditing

• SW release management and delivery



Software Engineering Process (2-4%)

• Process infrastructure

• Process measurement

• Process definition

• Qualitative process analysis

• Process implementation and change

Software Quality (6-8%)

• SW quality concepts

• Planning for SQA and V&V

• Methods for SQA and V&V

• Measurement applied to SQA and V&V

Software Engineering Tools and Methods (2-4%)

• Management tools and methods

• Development tools and methods

• Maintenance tools and methods

• Support tools and methods


Process of Becoming CertifiedProcess of Becoming Certified

Complete application including: resumé transcript or diploma report of education verification of reading Code of

Ethics report of experience in at least 6

of the 11 knowledge areas

Prepare for examination Self-study using a recommended

two-volume resource guide, or Take exam preparation tutorial

Schedule the exam at a Prometric test center

Take the exam 4-hour, computer-based, 180-

question, multiple-choice Pass/Fail is determined immediately Diagnostic scores for self-

assessment in content areas are provided to candidates who do not pass


Taking the TestTaking the Test

The 2003 Testing Window is from April 1, 2003 to June 30, 2003.

The computerized exam can be taken at over 230 Prometric Testing Centers.

Special exam opportunity here at STC this week: Discount on pre-exam tutorial. Discount on exam itself. Free retest within one year (so you can use the exam for your own personal

gap analysis).


Certification RenewalCertification Renewal

Certificate is valid for 3 years Renewal is based upon earning continuing

education credits


Importance to IndividualsImportance to Individuals

Self-assessment of professional knowledge Differentiation from less qualified individuals Credibility of qualifications for employment or

contracts Professional recognition

But certification is not a guarantee of competency.


Importance to OrganizationsImportance to Organizations

Hiring: A method to credibly assess qualifications. Salary Management: A rational way to provide salary bonuses

for vital IT skills. Training: A structure for a development program leading to a

recognizable result. Competency: A method to assess strengths in important areas. Consulting: A means to assert qualifications to consult in

important areas. Suppliers: A way to evaluate the ability of suppliers to perform.


Code of EthicsCode of Ethics


Software Engineering Code of Software Engineering Code of Ethics and Professional PracticesEthics and Professional Practices

Developed by a Joint IEEE-CS/ACM Task Force on Software Engineering Ethics and Professional Practices. Approved in 1998.

“The short version of the code summarizes aspirations at a high level of the abstraction; the clauses that are included in the full version give examples and details of how these aspirations change the way we act as software engineering professionals. Without the aspirations, the details can become legalistic and tedious; without the details, the aspirations can become high sounding but empty; together, the aspirations and the details form a cohesive code.”


Short Version States Eight Short Version States Eight PrinciplesPrinciples

Public: Software engineers shall act consistently with the public interest.

Client and employer: Software engineers shall act in a manner that is in the best interests of their client and employer consistent with the public interest.

Product: Software engineers shall ensure that their products and related modifications meet the highest professional standards possible.

Judgment: Software engineers shall maintain integrity and independence in their professional judgment.

Management: Software engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance.

Profession: Software engineers shall advance the integrity and reputation of the profession consistent with the public interest.

Colleagues: Software engineers shall be fair and supportive of their colleagues.

Self: Software engineers shall participate in lifelong learning regarding the practice of their profession and shall promote an ethical approach to the practice of the profession.


Example from Long VersionExample from Long Version

Principle 4 JUDGMENT Software engineers shall maintain integrity and independence in their professional judgment. In particular, software engineers shall, as appropriate:

4.01. Temper all technical judgments by the need to support and maintain human values.

4.02 Only endorse documents either prepared under their supervision or within their areas of competence and with which they are in agreement.

4.03. Maintain professional objectivity with respect to any software or related documents they are asked to evaluate.

4.04. Not engage in deceptive financial practices such as bribery, double billing, or other improper financial practices.

4.05. Disclose to all concerned parties those conflicts of interest that cannot reasonably be avoided or escaped.

4.06. Refuse to participate, as members or advisors, in a private, governmental or professional body concerned with software related issues, in which they, their employers or their clients have undisclosed potential conflicts of interest.


IEEE CS Support of the ProfessionalIEEE CS Support of the Professional

Professional Development


Skills Development

Possibly

Full Professional

Status


Necessary Infrastructure Support

Example Products and Services of Professional

Societies


Curricula CC2001, CCSE

Accreditation ABET/CSAB

Body of knowledge SWEBOK

Prof. literature IT Pro, Software

Prof. interaction Chapters,Elec. Communities

Prof. training DVP, Tutorials,Distance Learning

Design solutions Standards, Workshops

Practice norms Standards,Best Practices

Ethical norms Code of Ethics

Prof. certification CSDP

april 2003stcjames w. moore - 1 making software development a professional discipline: the ieee...

Documents

stc software engineering

software development

software engineering

computer engineering

software engineers

maintenance of software

application of engineering

computer science