swebokchp1intro

8/9/2019 SwebokChp1Intro

1/29

Glenn L. Ray 2009

IS 1092IT Management

SWEBOK

Intro & Chapter 1


2/29

Glenn L. Ray 2009

SWEBOK

Sponsored by IEEE & ACM

In progress since 1993

Supported by major IT organizations

Outlines SWE

Knowledge areas (KAs)

Recommended best practices

Baseline body of knowledge Guide to the SWE literature

Handy quick reference


3/29

Glenn L. Ray 2009

SWEBOK

Mapping of SWEBOK to BSIS Curriculum

Goal is to cover SWE KAs in BSIS program

SWEBOK to BSIS Course Matrix


4/29

Glenn L. Ray 2009

SWEBOK

Why would you care?

SWE is a defined profession

ABET accredits SWE degree programs

Texas licenses SWEs Professional associations recognize SWE

SWEs have a broad, foundational IT skillset

SWEs are in high demand

SWE ranked the #1 career for the next 10 years byMoney magazine!


5/29

Glenn L. Ray 2009

SWEBOK

Focus for this course

Not a technology course

No programmingyea!!!

Priority SWE KAs for IT Mgnt.

Management of SW development processes

Critical analysis of SW development processes

Configuration & change management

Quality assurance & testing


6/29

Glenn L. Ray 2009

SWEBOK

Whats the course like?

A lot of reading!

Much of it rather dry

Not particularly complex or technical

Youre expected to read critically and be skeptical of

what you read

Be prepared for quizzes & assignments every class

Be prepared to think!


7/29

Glenn L. Ray 2009

SWEBOK

SWEBOK establishes boundary of SWE

profession

Divides SWE into Knowledge Areas (KAs) and

closely related disciplines (e.g., Project

management)

SWE is NOT computer science

Scientists study laws of nature Engineers apply laws of nature to build useful

solutions to pressing problems


8/29

Glenn L. Ray 2009

SWEBOK

SWEBOK vs. IT

IT more concerned with specific technologies

OO programming languages

Relational databases XML parsers

Technology tools obsolesce quickly

SWE must know which tool(s) to use for the job

SWE best practices are developed & documentedover time

SWE best practices do not obsolesce rapidly


9/29

Glenn L. Ray 2009

SWEBOK

SWEBOK is guide to normative literature Literature that tells SWE what is best practice for a

particular situation Intended equivalent of undergrad degree + 4 yrs. experience

Validated by consensus of practicing professionals

Involves many large IT organizations

Caveat Best practices = generally accepted

Emerging or niche practices not included

SWE is dynamic field


10/29

Glenn L. Ray 2009

SWEBOK

IEEE definition of SWE

(1) The application of a systematic, disciplined,

quantifiable approach to the development, operation,

and maintenance of software; that is, the applicationof engineering to software.

(2) The study of approaches as in (1)


11/29

Glenn L. Ray 2009

SWEBOK

What percentage of SW do you think is

engineered?

Review the definition carefully for guidance in making

your estimate


12/29

Glenn L. Ray 2009

SWEBOK

Is software engineering an oxymoron?

Is SWE a profession?


13/29

Glenn L. Ray 2009

SWEBOK

Classic engineering professions have

Established professional education curriculum

accredited by a professional society

Registration via certification and/or licensing Specialized continuing education

A professional code of ethics


14/29

Glenn L. Ray 2009

SWEBOK

SWEBOKs 5 primary objectives

Promote consistent view of SWE

Define SWE boundary WRT allied fields, such as CS

Characterize contents of SWE discipline

Topical access to SWEBOK

Foundation for curriculum development and

certification/licensing


15/29

Glenn L. Ray 2009

SWEBOK

SWE related disciplines

Computer engineering

CS

Management

Math

Project management (TELCOM 2420!)

Quality management

Software ergonomics

Systems engineering


16/29

Glenn L. Ray 2009

SWEBOK

Can you think of any distinctions between SWE

and Information Science?

Is one a subset of the other?

Are they disjoint or overlapping?


17/29

Glenn L. Ray 2009

SWEBOK

Categories of knowledge

Generally accepted

Established practices recommended by many organizations

Applies to most projects most of the time

Specialized

Applies to only some projects some of the time

Advanced & Research

Innovative practices still under development & testing Actual application not fully understood

Use at your own risk


18/29

Glenn L. Ray 2009

SWEBOK

Each SWE KA is decomposed into

Subareas

Topics

Subtopics


19/29

Glenn L. Ray 2009

SWEBOK

Requirements KAs

Fundamentals

Process

Elicitation

Specification

Validation

Practical considerations


20/29

Glenn L. Ray 2009

SWEBOK

Design KAs

Fundamentals

Key Issues

Data persistence, distribution, exception handling etc.

Structure & Architecture

Quality analysis & evaluation

Design notations

Strategies & methods OO, structured, etc.


21/29

Glenn L. Ray 2009

SWEBOK

Construction (Implementation) KAs

Fundamentals

Managing construction

Planning & measurement

Practical considerations

Languages, reuse, testing, integration, etc.


22/29

Glenn L. Ray 2009

SWEBOK

Testing KAs

Fundamentals

Test levels

Test techniques Usage-related, code-based, etc.

Test-related measures

Test process


23/29

Glenn L. Ray 2009

SWEBOK

Maintenance KAs

Fundamentals

Key issues

Cost estimation, management, etc.

Maintenance process

Techniques

Reengineering, reverse engineering, etc.


24/29

Glenn L. Ray 2009

SWEBOK

Configuration management KAs

SCM is the discipline of identifying the configuration

of software at distinct points in time for the purpose of

systematically controlling changes and maintainingintegrity and traceabilitythroughout the system life

cycle

Version control

Allows for management of releases Rollback to last stable version

Change management is virtually synonymous


25/29

Glenn L. Ray 2009

SWEBOK

Configuration Management KAs

Management of SCM process

System configuration ID

SW configuration control

SW configuration status accounting

SW configuration auditing

Release management & delivery


26/29

Glenn L. Ray 2009

SWEBOK

Engineering management The management & measurement of SWE

Collection & use of metrics a key issue in SWE

KAs are Initiation & scope definition

Project planning

Project enactment

Review & evaluation Closure

Measurement


27/29

Glenn L. Ray 2009

SWEBOK

Process

Definition, implementation, assessment,

measurement, management, change and

improvement of the.SW process

KAs are

Implementation & change

Definition

Assessment

Process & product measurements


28/29

Glenn L. Ray 2009

SWEBOK

Tools & methods KAs

Tools

Methods

Heuristic, formal, prototyping


29/29

Glenn L. Ray 2009

SWEBOK

Quality KAs

Fundamentals

Quality management processes

Practical considerations Defect characterization, measurement, requirements, etc.

swebokchp1intro

Documents