slide1
Download
Skip this Video
Download Presentation
Becoming a Certified Software Development Professional (CSPD) and Overview of The Software Engineering Body of Knowledge (SWEBOK)

Loading in 2 Seconds...

play fullscreen
1 / 48

Becoming a Certified Software Development Professional CSPD - PowerPoint PPT Presentation


  • 345 Views
  • Uploaded on

Becoming a Certified Software Development Professional (CSPD) and Overview of The Software Engineering Body of Knowledge (SWEBOK) (Required reading SWEBOK Chapters 1 and 2 Text Ch 1-4) The SWEBOK Guide Task Force Objectives Promote a consistent view of SE worldwide

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Becoming a Certified Software Development Professional CSPD ' - Gabriel


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
slide1

Becoming a Certified Software Development Professional (CSPD)andOverview of The Software Engineering Body of Knowledge (SWEBOK)

(Required reading SWEBOK Chapters 1 and 2

Text Ch 1-4)

the swebok guide
The SWEBOK Guide
  • Task Force
  • Objectives
    • Promote a consistent view of SE worldwide
    • Clarify the place and boundaries of SE relative to other related disciplines
    • Define/characterize the contents of the SE discipline
    • Provide access to the various components of the SWEBOK
    • Provide a foundation for curriculum development and individual certification and licensing
the swebok guide cont d
The SWEBOK Guide Cont’d
  • A guide to describe the core of the SE Body of Knowledge
  • Broken into Knowledge Areas
how we will use swebok
How we will use SWEBOK
  • Has many “definitions” of most key terms, you will be required to know the terms defined in the chapters assigned.
  • Has references to primary material (and occasional textbooks), you can use later when/if you need more details.
  • Only doing an overview, you are expected to know what is there, not necessarily how to do it.
  • Really covering the SWEBOK takes 5-8 courses!
knowledge areas
Knowledge Areas
  • Establishes boundaries that identify engineering disciplines
  • May share common boundaries with other disciplines
  • Does not attempt to describe all of the knowledge within SE
knowledge areas cont d
Knowledge Areas Cont’d
  • Captures a subset of “generally accepted” knowledge or the core of SE
knowledge areas cont d7
Knowledge Areas Cont’d
  • There are 10 KAs in the SWEBOK
  • Each KA contains a reasonable topic list presenting sound information about SE
  • Excludes specific knowledge regarding application domains, business, technology, SLCs and development methods
  • Compatible with what is generally found in industry
knowledge area cont d
Knowledge Area Cont’d
  • Each KA follows the KA Description Specification
  • Includes description, topics, related areas and reference materials.
the repeatable process
The Repeatable Process
  • The first 5 KAs cover the repeatable process
    • Requirements
    • Design
    • Construction
    • Testing
    • Maintenance
  • Define KA used in the development of software management processes
  • Together the are comparable to the definition of CMM level 2 excluding business specific knowledge
software requirements
Software Requirements
  • Requirements engineering process
  • Requirements elicitation
  • Requirements analysis
  • Software requirements specification
  • Requirements validation
  • Requirements management
software design
Software Design
  • Basic concepts
  • Key issues of software
  • Structure and architecture
  • Software design quality analysis and evaluation
  • Design notation
  • Software design strategies and methods
software construction
Software Construction
  • Considered one of the fundamental act of SE
  • The construction of working, useful software through programming, validation and testing.
  • Three styles of construction
    • Linguistic
    • Formal
    • Visual
software construction cont d
Software Construction Cont’d
  • Principles of construction
    • Reduction of complexity
    • Anticipation of diversity
    • Structuring for validation
    • Use of external standards

Where does the Software Engineer learn to construct software?

Is Computer Science a required related discipline?

software testing
Software Testing
  • Basic concepts
  • Test levels
  • Test techniques
  • Test-related measures and management
software maintenance
Software Maintenance
  • Basic concepts
  • Maintenance process
  • Key issues
  • Techniques for maintenance

Is there a SENG course that covers software maintenance?

related disciplines
Related Disciplines
  • Computer Science
  • Mathematics
  • Projects Management
  • Computer Engineering
  • Cognitive Science and Human Factors
  • Systems Engineering
  • Management and Management Science
the defined and managed process
The Defined and Managed Process
  • The last 5 KAs cover the defined and managed process:
      • Software Configuration Management
      • Software Engineering Management
      • Software Engineering Process
      • Software Engineering Tools and Methods
      • Software Quality Analysis
  • Together they are are comparable to the definition of CMM level 3 and 4
software configuration management scm
Software Configuration Management (SCM)
  • Management of the SCM Process
  • Software Configuration Identification
  • Software Configuration Control
  • Software Configuration Status Accounting
  • Software Configuration Auditing
  • Software Release Management and Delivery
software engineering management
Software Engineering Management
  • Organizational Management
  • Process/ Project Management
  • Software Engineering Measurement
software engineering process
Software Engineering Process
  • Software Engineering Process Concepts
    • Process Infrastructure
    • Process Measurement
    • Process Definition
    • Qualitative Process Analysis
    • Process Implementation and change
software engineering tools and methods
Software Engineering Tools and Methods
  • Software Tools: requirements tools, design tools, Construction tools, testing tools, maintenance tools , engineering process tools, quality tools, configuration management tools, engineering management tools, infrastructure support tools, Miscellaneous tools issues
  • Software Methods:
    • Heuristic
    • Formal
    • Prototyping
    • Miscellaneous
software quality
Software Quality
  • Software Quality Concepts
  • Purpose and Planning of SQA and V&V
  • Activities and Techniques for SQA and V&V
  • Measurement Applied to SQA and V&V
a complete swebok based education program
A complete SWEBOK based Education Program

Software Engineering

Tools and Methods

Software Engineering

Process

Software Engineering

Management

Software Quality

Software Configuration

Management

SWEBOK

Software Maintenance

Software Requirement

Software Testing

Software Construction

Software Design

an organizational alternative
An Organizational alternative
  • What is CMMI, and how related to PSP and CMM.
  • What is required to achieve CMMI?
  • Relating CMMI and EIA 859!
what is cmmi
What is CMMI?
  • Defines 5 levels of process maturity
  • Describes model framework to be used for:
  • Assessing process maturity
  • Determining priorities
  • Instituting process improvement

Capability Maturity

Model Integration

CMMI

relation to psp and cmm
Relation to PSP and CMM
  • PSP is the Personal Software process, and is basically a “process” (supported by course material to teach it) for an individual to follow a capabilities-based maturity model.
  • CMM is the older SEI Capability Maturity Model, strictly for Software Development. CMMI is a generalization that covers more systems and project issues as well as business processes.
cmmi levels

Level

5

Optimizing

Level 4

Quantitatively

Managed

Level 3 - Defined

Level 2 - Managed

Level 1 - Performed

CMMI Levels

The five levels

of CMMI process

maturity!

Level 0 - Incomplete

slide28

At what CMMI Level are we performing?

Are all process

goals being

accomplished?

  • Are Data Management requirements
  • being met?
  • Are all customers identified?
  • Are all customer requirements identified?
  • Are customer requirements being
  • met?

NO

Review data

management

procedures to

determine

CMMI Level

Are

one or

more of the

process goals not

accomplished?

YES

CMMI Level 0

Incomplete

Process not

performed

Performing at CMMI

Level 0

how do we achieve level 1
How do we achieve Level 1?

Identify your customers

Identify customers needs

Identify management

process goals

Develop steps to produce

the desired work products

  • Identify work products
what is cmmi level 1
What is CMMI Level 1?

Level 1 - Performed

  • Specific goals are being accomplished
  • No defined processes
  • Individuals may follow differing procedures
  • Using general purpose tools
cmmi level 1
CMMI Level 1
  • Dependent on individuals
  • Results vary
  • Resources vary
  • Results unpredictable
  • Practices are informal
  • Quality inconsistent

Characteristics

determining the cmmi level

YES

YES

YES

YES

YES

Is training

provided for

individuals

executing the

Process?

Are there

policies

governing the

process?

Are there

adequate

resources

to execute the

Plan?

Is there a

process plan?

Is the process

documented?

NO

NO

NO

NO

NO

CMMI Level 1

Process Performed

Performing at CMMI

Level 1

Determining theCMMI Level
eia 859
EIA 859

Includes 9 high level Data

Management Principles

Principles address functions

of Data Management

Describes fundamental

concepts to be considered

when structuring a Data

Management process

EIA Standard 859

Industry Standard

for

Data Management

DRAFT

eia 859 principles

Principles

1. Define the organizationally-

relevant scope of Data Management

2. Plan for, acquire, and provide data

responsive to customer requirements

3. Develop DM processes to fit the

context and business environment in

which they will be performed.

4. Identify data products and views so

their requirements and attributes can be

controlled.

5. Control data repositories, data

products, data views, and meta data

using approved change control process.

6. Establish and maintain an identifi-

cation process for intellectual property,

proprietary, and competition-sensitive

data.

7. Retain data commensurate with value.

8. Continuously improve data

management.

9. Effectively integrate data management

and knowledge management.

EIA 859 Principles

EIA Standard 859

Industry Standard

for

Data Management

DRAFT

eia 85935

Level

5

Optimizing

Level 3 - Defined

Level 2 - Managed

Level 1 - Performed

EIA 859

CMMI & EIA 859

CMMI

Principles

1. Define the organizationally-

relevant scope of Data Management

2. Plan for, acquire, and provide data

responsive to customer requirements

3. Develop DM processes to fit the

context and business environment in

which they will be performed.

4. Identify data products and views so

their requirements and attributes can be

controlled.

5. Control data repositories, data

products, data views, and meta data

using approved change control process.

6. Establish and maintain an identifi-

cation process for intellectual property,

proprietary, and competition-sensitive

data.

7. Retain data commensurate with value.

8. Continuously improve data

management.

9. Effectively integrate data management

and knowledge management.

Level 4

Quantitatively

Managed

Advocates Repeatable Processes

Project Level

&

Enterprise Level

relating cmmi eia 859

Principles

1. Define the organizationally-

relevant scope of Data Management

2. Plan for, acquire, and provide data

responsive to customer requirements

3.Develop DM processes to fit the

context and business environment in

which they will be performed.

4. Identify data products and views so

their requirements and attributes can be

controlled.

5. Control data repositories, data

products, data views, and meta data

using approved change control process.

6. Establish and maintain an identifi-

cation process for intellectual property,

proprietary, and competition-sensitive

data.

7. Retain data commensurate with value.

8. Continuously improve data

management.

9. Effectively integrate data management

and knowledge management.

1. Define the organizationally-

relevant scope of Data Management

EIA Standard 859

Industry Standard

for

Data Management

3.Develop DM processes to fit the

context and business environment in

which they will be performed

8. Continuously improve data

management.

DRAFT

Relating CMMI & EIA 859
cmmi level 2
CMMI Level 2

Level 2 - Managed

Level 2 - Managed

  • Planned and executed IAW policy/procedures
  • Established objectives
  • Adequate resources
  • Applicable to a particular group/project
cmmi level 238

YES

YES

YES

YES

YES

Are there

established

policies

governing the

process?

Is training

provided for

individuals

executing the

Process?

Is the process

Documented?

Is there a

process plan?

Are there adequate

resources

to execute the

Plan?

CMMI

Level 2

EIA 859

Principle 3

Develop policies for process

execution based on organizational

requirements and customer needs.

Develop standards for work

products and services.

Identify stakeholders.

Define process dependencies and

work products and services.

Define resource requirements

(funding, people etc.)

Define work products requiring

configuration control.

Define process measurement

requirements to determine

process performance.

Develop DM processes to fit the

context and business environment

in which they will be performed.

Determine related organizational

policies.

Identify external forces.

Determine related business

objectives.

Determine requirements for access

and delivery.

Determine who will create, access,

update, and dispose of the data.

CMMI Level 2
slide39

Comparing CMMI Level 2 & EIA 859

YES

YES

YES

YES

Are all relevant

stakeholders being

considered?

Is the process

monitored?

Are work products

under configuration

control?

Is the process

controlled and

measured?

CMMI

Level 2

EIA 859

Principle 3

Evaluate the effect of deviations

from the process plans and

descriptions.

Review accomplishments against

process plans and descriptions.

Place the process work products

under configuration management.

Coordinate the process plan and

description with relevant stake-

holders.

Monitor and control the process.

Assign responsibility and authority

for performing the process.

Obtain the necessary resources.

Make needed adjustments in

processes, practices, policy,

organizational alignment and

infrastructure.

Control the integrity of data, data

elements, data structures and data

views.

Establish a change control process

that imposes the appropriate level

of review and approval.

Establish mechanisms for tracking

and determining status of data.

Is the process

being objectively

evaluated?

cmmi level 3
CMMI Level 3

Level 3 - Defined

  • Process institutionalized
  • Process consistent across the organization
  • Process measurable
slide41

Is the process

institutionalized?

YES

YES

YES

YES

YES

Is the process

unique to the

organization?

Is the process

considered

standard?

Is the process

being objectively

evaluated?

Is the process

defined?

CMMI

Level 3

Define process steps for

institutionalization.

Define policy/guidelines for

tailoring process steps.

Define process tailoring.

Document process tailoring.

Collect and document work

process/product measurement

results.

Develop and maintain a data base

for process/product measurement

information.

Document and store lessons learned

in the data base.

slide42

YES

YES

Is

there a

data base to

record process

improvements?

YES

YES

Are there

guidelines

for tailoring the

institutionalized

process?

Is the

tailored process

documented?

Is the process

quantitatively

managed?

CMMI

Level 3

EIA 859

Principle 8

Define process steps for

institutionalization.

Define policy/guidelines for

tailoring process steps.

Define process tailoring.

Document process tailoring.

Collect and document work

process/product measurement

results.

Develop and maintain a data base

for process/product measurement

information.

Document and store lessons learned

in the data base.

Establish and maintain a metric

process and reporting strategy.

Establish the necessary tools and

infrastructure to support the

process and assess the results.

CMMI Level 3

cmmi level 4
CMMI Level 4

Level 4

Quantitatively Managed

  • Controlled using statistical and other techniques
  • Process variation identified
cmmi level 444

CMMI

Level 4

.

CMMI

Level 4

EIA 859

Principle 8

Determine an understanding of the

ability of the process to achieve

the quantitative objectives.

Determine objectives for statistical

control.

Identify and measure the sub-

process determined to be under

statistical control.

Identify and measure process and

product attributes important to

quality and process performance.

Identify causes for process variation.

Manage processes to attain statistical

stability and predictability.

Predict the ability of the process to

achieve performance objectives

using managed statistical data.

Institutionalize process

performance baselines.

Take appropriate action when

desired quantitative and process/

product performance objectives

are not being met.

Recognize the need to continuously

improve the quality of data resources.

Establish and maintain a metric

process and reporting strategy.

Establish the necessary tools and

infrastructure to support the process

and assess the results.

Monitor the quality of data to

improve data and processes.

CMMI Level 4

Is

the process

stable and

predictable?

Is

quantitative/

qualitative process/

product data

being

collected?

Are

the

quantitative/

qualitative objectives

based on

customer

needs?

YES

YES

YES

YES

YES

Are significant

processes/products

statistically

managed?

Is the

collected data

being analyzed?

cmmi level 5
CMMI Level 5

Level 5

Optimizing

  • Continuously improving performance
  • Incremental improvement
  • Technological improvement
comparing cmmi level 5 eia 859

CMMI

Level5

EIA 859

Principle 8

Develop and maintain process/

product improvement objectives.

Identify and implement tech-

nelogical innovations for process/

product improvements.

Manage process/product improve-

ment deployment.

Measure results against objectives.

Identify and correct process/

product defects.

Recognize the need to continuously

improve the quality of data

resources.

Implement a strategy for on-going

improvement.

Improve Data Management

through a systematic and self-

diagnostic process..

Identify objective evidence of

improvements.

Comparing CMMI Level 5 & EIA 859

Does

the process

include continuous

improvement

objectives?

YES

YES

Does

the process

allow for tech

improvements?

YES

Does

the process

include a plan

for attaining

improvement

objectives?

YES

Does

the process

identify problems

and

defects?

Is the process

optimized?

summary

5

Level

Level 4

Level 3

Level 2

Level 1

Summary

EIA Standard 859

Industry Standard

for

Data Management

DRAFT

Data Management

CMMI

references
References
  • Guide to the Software Engineering Body of Knowledge: Trial Version, 2001,http://www.swebok.org/stoneman/version09.html
  • Trip, Leonard L., Professionalization of Software Engineering: Next Steps, 1999,http://www.swebok.org/documents/x3009.pdf
  • “A Summary of the ACM Position on Software Engineering as a Licensed Engineering Profession”, http://www.acm.org/serving/se_policy/selep_main.html
  • “An Assessment of Software Engineering Body of Knowledge Efforts: A Report to the ACM Council“, http://www.acm.org/serving/se_policy/bok_assessment.pdf
  • IEEE Computer Society Web Site: http://computer.org/certification
  • Code of ethics http://computer.org/certification/ethics.htm
  • Comm. of the ACM, Nov. 2002 (45, 11)
    • Licensing Software Engineers - 6 articles
ad