CSE 8314 / NTU SE762-N : SOFTWARE METRICS AND QUALITY ENGINEERING

Syll!"#

C$"%#& D&#'%()*($+/O!,&'*(-&: This course presents modern methods of achieving high quality software, with emphasis
on pragmatic issues and use of examples from real applications. In particular, the course focuses on the importance of
process definition, measurement and continuous improvement as part of a discipline of quality engineering. Specific
metrics and their uses are discussed along with pitfalls and risks in using metrics.
I+#*%"'*$%: Dr. Dennis J. railey SMU C$+*'*: !s. De"ra !cDowell
#d$unct %rofessor Dept. of &omputer
.72-344-8366 /-$('&01 Science and 'ngineering
.72-344-7721 /FA301 214-768-3282
4%(l&y5&+6%7#8"7&9" 9&!%8'95&+6%7#8"7&9"
C$"%#& :+9$"*# A+9 O*;&% I+4$( http())www.seas.smu.edu)*frailey)
O44('& :$"%#( +y #ppointment and "y internet communication
,-o #ppointment .equired for "rief meetings after class/
0000000000000000000000000000000000000000000000000000000000000000000000000000
M(l(+6 A99%&##&# 4$% A##(6+8&+*# +9 E<8#:
or 1.S. !ail(
Southern Methodist University
Computer Science and Engineering
Fondren Library Center, Room 306
SC
attn! "rader, CSE#3$%
&' (' )o* #%0$++
,a--as ./ #%+#%00$++
or 2vernight !ail(
Southern Methodist University
Computer Science and Engineering
Fondren Library Center, Room 306 SC
attn! "rader, CSE#3$%
61+% (2nby ,rive
,a--as ./ #%+0%
000000000000000000000000000000000000000000000000000000000000000000000000000
S';&9"l&( &3#SS TI!'( 4aries 5 usually taught in a 65hour time slot, once a week

E<8#( !IDT'.! ,&lass 789 after module 7:;/9 I-#3 ,Due < week after last class/
In5class students take midterm as class 78 and final after class 7<=.
Students taking the course via tape delay or on5line methods take midterm via their
local proctor after completing module :; and do final after completing
the course.

A##(6+8&+*#( < minor ,#:/9 < moderate ,#=/9 and < ma$or ,#<, #6, and #>/. The latter is either a quality
improvement plan or a research paper, completed in three stages.
'ach student will prepare either a comprehensive ="l(*y (8)%$-&8&+* )l+ for her or his organi?ation, or else
will select a topic for further research and will prepare a %&#&%'; ))&% on his or her topic. 'ach student
choosing the research paper option will "e encouraged to #"!8(* ))&% 4$% )"!l('*($+ "ased on the research
paper.

G%9(+6: 6;@ for plan or paper ,assignments <, 6, and >/9 >@ for assignment :, <>@ for assignment = ,further details on
assignments are in separate handouts/9 :>@ for each exam.
G%9(+6 S'l& +9 E<)&'**($+#:.#( A65<;;9 #5( A;5A:9 +B( 8858A9 +( 8658C9 +5 8;58:9 &B( C85CA9 &( C65CC9 &5 C;5C:9
and so forth. -o curve is used. In grading, I focus on evidence that the student has learned the concepts taught in
the class and applied them to the pro"lem presented in the examination or assignment. .ote memori?ation will
not help the student as much as seeking to understand the concepts through study, discussion and application. I
welcome dialog with students on these concept and encourage discussion of the concepts among students ,for
example, study groups/, so long as students do not discuss specific details of assignments and examinations.

_______________________________________________________________________________________________________________
CSE8314 / SE762-N Syllabus Page < of >
T&<*:
,D</ Dein"erg, Eerald !. Quality Software Management, Volume 1, Systems Thinking, Dorset Fouse, -ew Gork, <AA:.
IS+-( ;5A6:H665::5H. ,'xplores quality improvement with many insights from a psychological and cultural point
of view./
O*;&% R&'$88&+9&9 R&9(+6 ,I J Strongly .ecommended/ K-ote( some of these are out of printL
,+a/ +aumert, John F., and !ark S. !cDhinney, Software Measures and the Capability Maturity Model, &!1)S'I5A:5
T.5:>, 'S&5T.5A:5;:>, Software 'ngineering Institute, &arnegie !ellon 1niversity, %itts"urgh, %a., <AA:.
,Identifies which measures can reasona"ly "e expected at various levels of the S'I maturity model./
,De/ De!arco, Tom, Controlling Software Projets! Management, Measurement, and "stimation, -ew Gork, Gourdon
%ress, <A8:. ,%ractical guidance for collecting and analy?ing software measures/.
,D/ Do""ins, James F. Software Quality #ssurane and "$aluation. ,# good review of the conventional view of software
quality assurance./
I ,Do/ Department of Defense, Joint 3ogistics &ommanders Joint Eroup on Systems 'ngineering, %ratial Software
Measurement, a %uide to &bjeti$e Program 'nsight ($ersion )*1+, -aval 1ndersea Darfare &enter, c)o John
!cEarry, mcgarryMada.npt.navy.mil. ,'xplains "asic concepts of the software measurement process and offers
detailed implementation guidance as well as realistic case studies from the DoD environment./
,/ enton, -orman '. Software Metris! # ,igorous #pproah, &hapman N Fall, 3ondon S'< 8F-, <AA<. IS+- ;5
==:56<6>>5<. ,This "ook is an excellent discussion of software metrics, "ased on fundamental theory. %rovides
specific tools to overcome deficiencies of typical measurement programs./
I ,E</ Erady, .o"ert +. and De"orah 3. &aswell, Software Metris! "stablishing a Company-.ide Program. 'nglewood
&liffs, -.J., %rentice5Fall, Inc., <A8C. IS+- ;5<658:<8==5C. ,Eood description of the issues faced "y a company
developing a metrics program./
I ,E:/ Erady, .o"ert +. Pratial Software Metris for Projet Management and Proess 'mpro$ement. 'nglewood
&liffs, -.J., %rentice5Fall, Inc., <AA:. IS+- ;5<65 C:;68=5>. ,This is a follow5on to E<, reflecting what has "een
learned in the > years since it was pu"lished, and delving into more detail 5 especially with respect to software
process improvement./
,I</ I''' Std <;=>5<AA:. '""" Standard for Software Produti$ity Metris. -ew Gork, Institute of 'lectrical and
'lectronics 'ngineers, Inc. ,Descri"es more than 6; software measures that can "e used to consistently define
software productivity./
,I:/ I''' Std <;H<5<AA:. '""" Standard for a Software Quality Metris Methodology. -ew Gork, Institute of 'lectrical
and 'lectronics 'ngineers, Inc. IS+- <5>>A6C5:CC5O. ,Defines a methodology for esta"lishing quality requirements
and identifying, implementing, analy?ing, and validating the process and product of software quality metrics Kfrom
the a"stractL/
,J</ Jones, &apers #pplied Software Measurement! #ssuring Produti$ity and Quality* !cEraw5Fill, Inc., <AA<. IS+-
;5;C5;6:8<65C. ,This "ook contains a large selection of possi"le metrics./
,!</ !arciniak and 'vans. Software Quality #ssurane and Management. ,.ecommended "y several SP#
professionals/
,!:/ !Qller, R. F. and D. J. %aulish. Sotware Metris! # pratitioner/s guide to impro$ed produt de$elopment .
3ondon, &hapman N Fall &omputing, <AA6. IS+- ;5=<:5=>A;;5;. #lso availa"le from I''' %ress, IS+- ;5C8;65
;===5H. ,This is a report on experiences at Siemens)-ixdorf corporation, performed largely as part of the %G.#!ID
research pro$ect, funded "y the 'sprit II program./
,S/ Schulmeyer, E. Eordon. 0ero 1efet Software. !cEraw Fill, <AA;. IS+- ;5;C5;>>HH65H. ,&omprehensive
coverage of the su"$ect "y one of the originators of the concept./
,F/ Schulmeyer, E. Eordon and James !c!anus. 2andbook of Software Quality #ssurane, Seond "dition. 4an
-ostrand .einhold, -ew Gork, <AA:. IS+- ;5==:5;;CAH5>. ,2ne of the "est references on conventional SP#./
_______________________________________________________________________________________________________________
CSE8314 / SE762-N Syllabus Page : of >
I ,D:/ Dein"erg, Eerald !. Quality Software Management, Volume ), 3irst &rder Measurement, Dorset Fouse, -ew
Gork, <AA6. IS+-( ;5A6:H665:=5:. ,Second volume in series 55 expands coverage into the area of metrics./
,D6/ Dein"erg, Eerald !. Quality Software Management, Volume 4, Congruent #tion, Dorset Fouse, -ew Gork, <AA=.
IS+-( ;5A6:H665:85>. ,Discusses the role of management in achieving a high quality software program. #pplies
!yers5+riggs "ehavior type indicators to discuss patterns of "ehavior in software organi?ations and how managers
can use this knowledge to improve. Stresses the difference "etween knowing and doing./
,D=/ Dein"erg, Eerald !. Quality Software Management, Volume 5, #ntiipating Change, Dorset Fouse, -ew Gork,
<AAH, IS+-( ;5A6:H6656:56. ,ocuses on how change really happens and how to manage it./
,O/ Oie, !. Software ,eliability Modelling, Dorld Scientific, 3ondon, <AA<. IS+- A8<5;:5;H=;5:. ,This hard5to5find
"ook is a solid, theoretical look at software relia"ility/.
_______________________________________________________________________________________________________________
CSE8314 / SE762-N Syllabus Page 6 of >
21T3I-'
&S'86<= 5 S2TD#.' !'T.I&S #-D P1#3ITG '-EI-''.I-E
-ote( this is a topical outline, not necessarily the exact order in which material is covered.

!odule,s/ Text N .eference
<. 2verview of Software Puality 'ngineering ;56 +ook &hapters
&ourse and Text"ooks
%rocess and %rocess !aturity
&oncepts of Puality D<( <
:. undamentals of Software Puality Improvement 65>
&oncepts of Puality Improvement F( <
&oncepts of %rocess !aturity D<( :
Improving %rocess !aturity D<( 6
6. 'lements of a Puality 'ngineering %rogram H58 F( <
rom Puality &ontrol to Puality #ssurance to Puality 'ngineering
'lements of a Puality %rogram( .elia"ility, !aintaina"ility, 4erifia"ility, Testa"ility, Safety and
Supporta"ility
Some Forror Stories
=. #dding 4alue through Software Puality 'ngineering A5<< F( 8
4alue #dded
&ost 'lements
&ost of Puality #nalysis
!easuring &ost of Puality
>. Software .elia"ility <:5<= F( <8,<A
H. Six Sigma, Sero Defects and Statistical Puality &ontrol <>5<C
Sero Defects S( ,all/9 F( <;
Six Sigma
Statistical Puality &ontrol F( <C
C. &ycle Time and %roductivity Improvement <85:<
8. %rinciples of !easurement and !etrics ::5:=
Data, !easures and !etrics ,%rimitive)&ompound/ E<( #ppendix #
Eraphs of !etrics
%roduct, %rocess and %ro$ect !etrics E<( <>.: ,p<88/9 E:( 8
A. Selecting Puality Eoals and !etrics :>5:H
Puality unction Deployment
Eoal)Puestion)!etric %aradigm E:( p:6
Puality &haracteristics Tree E<( <<56 ,p<>8/9 F( p66=
The 1.%S !odel and 1.%SB E<( <<56 ,p<>A/9 E:( =
_______________________________________________________________________________________________________________
CSE8314 / SE762-N Syllabus Page = of >
<;. Rey !etrics for Software 'ngineers :C5:8
Defects
%roductivity and Puality D<( p:<9 E<( =
<<. !easuring and Improving the Development %rocess :A E<( A, <H9 F( <;.6
#ssigning !etrics to %rocess 'lements and 'vents
Isikawa Diagrams E<( p<:C
<:. 2"serving, &ollecting and Storing Data 6;56:
!ethods of 2"servation D:( <5=
!ethods of Interpretation D:( >589 E:( =, <:9 F<<
&ollection #pproaches and their %ro"lems E<( 8,<;
Data &ollection E:( =
<6. Puantitative %rocess !anagement 6656H
<=. Testing and !etrics 6C
<>. &hanging the !anagement %rocess 68 E<( <C9 D<( =58
Justifying &hange E:( <=
_______________________________________________________________________________________________________________
CSE8314 / SE762-N Syllabus Page > of >