🚀 go-pugleaf

Greetings from the Continuing Education Department at Georgia Tech's
College of Computing.

In our continuing efforts to bring you cutting edge subjects we are adding
a new Software Engineering Certificate in:

 Software Engineering "Cleanroom" Methodology

the software development methodology based upon the practice demonstrated
by  Harlan Mills.   This approach to software development borrows the word
"Cleanroom" from the semiconductor industry to better reflect the emphasis
on preventing defects rather than removing them.

Rather than treating your software development as a typical trial-and-error
effort, the "Cleanroom" methodology approaches it as an engineering process
with the desired end result of designs without errors and executions
without failures.

These courses (and the Cleanroom Methodology Certificate) will prepare you
for the entire process and help you to plan, specify, design, verify, code,
test, and certify your software.

Descriptions and scheduled dates for the courses are listed below.  For more
information please visit our Web Pages at:

  http://www.cc.gatech.edu/conted

or you can send any inquires to:

 conted-info@cc.gatech.edu

*************************************************
Cleanroom Process
[COMP-181] 2 days $825

The Cleanroom Process is a method of software engineering with the explicit
goals of enabling software engineers to achieve: Short development cycles;
Zero failures in field use; Long product life; Cleanroom approaches these
goals by the principles of mathematics, statistics and engineering.  The
Cleanroom Process spans the entire software lifecycle, providing a
discipline for teams to plan, specify, design, verify, code, test and
certify software.  This is a process comprised of separable parts.  It can
be used in whole or in part to augment and enhance "industry best
practices".  Cleanroom is a recognized path to the SEI CMM Levels 3 and
beyond.

Objective: This course will present an overview of Cleanroom, the
principles on which it is based, its relationships to SEI CMM key process
areas, and its relationships to other industry practices.

Topics: Incremental development; specification, box structures, correctness
verification; usage models; statistical testing; process control; process
records; CMM KPAs; relationship to best practices.

Benefits:
Improvements in your process
Product improvements
Increased productivity from individual and team activities
Transition from craftsmanship to engineering
Higher return on investment

Prerequisites:  Improving Software Quality [COMP-129] or equivalent
experience participating in or managing the development of software
products.

October 21-22, 1996
February 10-11, 1997

*************************************************
Cleanroom Specification
[COMP-182] 3 days $1055

Cleanroom specifications are intended to describe in precise detail all
possible scenarios of software use.  Black Box specifications are based on
a systematic analysis of all possible sequences of inputs (at an
appropriate level of abstraction) and the correct or desired behavior of
the system to be developed.  The result is a specification that is
complete, consistent, correct and traceable.

Objective:  Participants learn how to develop Black Box specifications from
natural language requirements, and derive the control state and data state
to write a State Box specification.

Topics:  Basics of functions; input spaces; enumeration of sequences;
responses; equivalence of sequences; extension of sequences; partitions;
specification functions; abstraction techniques.

Benefits:
Create precise specifications
Earlier discovery of ambiguities and omissions
Excellent basis for development of code and certification testing models
Readily maintainable specifications

Prerequisites: Some familiarity with sets and relations; some familiarity
with combinations and permutations would be helpful.

October 28-30, 1996
February 12-14, 1997

*************************************************
Cleanroom Certification
[COMP-183] 3 days $1055

Cleanroom software certification is the demonstration that a system is fit
for its intended use, by following a defined and repeatable, experimental
protocol.  Certification testing is for the purpose of providing empirical
evidence that good software is "good enough" and is used to support a
management decision that a software-intensive product is ready to ship to
customers.

The major steps in certification are:  development and validation of usage
models; test planning and generation of test cases; performing tests,
recording results and monitoring reliability measures; and other criteria
for stopping testing.

Objective:  Participants will learn how to certify that a software system
or software-intensive product is fit for its intended use.

Topics:  Topics will include: probability; usage models; graphs; model
analysis; model validation; usage profiles; experimental control; manual
testing; automated testing; reliability; stopping criteria.

Benefits:
Software that has been tested the way it will be used
Software of measured reliability
Reusable models of software use
Automatic test case generation
Optimal use of testing resources
Quantitative feedback to developers

Prerequisites:  Some testing experience will be useful.  Some knowledge of
basic probability and statistics will be helpful.

November 13-15, 1996
February 19-21, 1997

*************************************************
Cleanroom Development
[COMP-184] 3 days $1055

Cleanroom Development practices achieve an engineering balance between
fundamental theory and practical expediency.  System design begins in
problem domains, often with considerable informality, and ends in computer
domains of deterministic code and hardware.  The Box Structure methods
scale from small units to very large systems, to produce systems that are
correct by design.

The Box Structure method follows a step-wise refinement and verification
process.  Each major step in design expands a behavioral specification
(Black Box) to a state machine (State Box) to a sequential or concurrent
procedure (Clear Box).  An immediate verification of correctness follows
each step.

Objective: Participants learn how to develop software by the Box Structure
method.

Topics:  Black Box; State Box; Clear Box; stepwise refinement; functional
verification; function abstraction, structured programming; data
abstractions; information hiding; software
architecture.

Benefits:
Software that is correct by design and verification
Software that is easy to maintain and enhance
High levels of reliability that can be demonstrated with minimal testing
and changing

Prerequisites:  Cleanroom Specification [COMP-182].  Some discrete math
(sets, relations), logic (predicates, truth tables), data structures and
programming experience will be useful.

January 22-24, 1997
February 26-28, 1997

*************************************************
-- 
					
					-Nancy Pinion (pinion@cc.gatech.edu)