UTA CSE 6329-002 Advanced Topics in Software Engineering Software Measurement and Quality Engineering

UTA CSE 6329-002
Advanced Topics in Software

Engineering
Software Measurement and

Quality Engineering
Module 00
 Administrative Details
 Overview of the Course
Copyright 2020, Dennis J. Frailey CSE 6329-002 – Software Measurement and Quality Engineering
CSE 6329-002 M00 - Version 20.01
Administrative Details and Course
Overview
CSE 6329-002 M00 - Version 20.01
Dennis J. Frailey
Adjunct Professor – UT Arlington
e-MAIL: dennis.frailey@uta.edu
Backup: frailey@ACM.org
Copyright 2020, Dennis J. Frailey

CSE 6329-002 M00 - Version 20.01
CSE 6329-002 - Software Measurement and Quality Engineering
3
Dennis J. Frailey
Retired Principal Fellow - Raytheon Company
PhD Purdue, 1971, Computer Science

Assistant Professor, SMU, 1970-75
Associate Professor, SMU, 1975-77
(various titles), Texas Instruments, 1974-1997;
Raytheon Co. 1997-2010
Adjunct Associate Professor, UT Austin, 1981-86
Adjunct Professor, SMU, 1987-2017
Adjunct Professor, UTA, 2014-present
-----
Areas of specialty: software development process,
software project management, software quality
engineering, software metrics, compiler design,
operating system design, real-time system
design, computer architecture

CSE 6329-002 M00 - Version 20.01
4
Quotations from Lord Kelvin
"To measure is to know."
"If you can not measure it, you can not improve it."
“…when you can measure what you are speaking about, and express it
in numbers, you know something about it; but when you cannot
measure it, when you cannot express it in numbers, your knowledge is
of a meagre and unsatisfactory kind; it may be the beginning of
knowledge, but you have scarcely in your thoughts advanced to the
state of Science, whatever the matter may be."
Source: Popular Lectures and Addresses, vol. 1,

"Electrical Units of Measurement", 1883-05-03
CSE 6329-002 M00 - Version 20.01
5
Course Objective
This course is intended to cover:
Software Software
Measurement Measurement First Half
Principles Applications
Software Quality Software Quality

Engineering Engineering Second Half
Principles Applications
These will be useful for any software developer or

manager, especially for those wishing to produce
high quality products.

CSE 6329-002 M00 - Version 20.01
6
This Course is an Introduction To
These Concepts
The goal is for you to have
the knowledge to make better decisions
– To know what CAN be done
– To know what techniques are most appropriate for a given
situation
The goal is not for you to become an expert in the techniques
covered
– That would require additional study
For most topics, we will explain how a technique or method can

be used
– To help measure something important
– To help improve quality
– To help make better decisions
CSE 6329-002 M00 - Version 20.01
7
What the Student Should Learn
 Principles of measurement
– What it means to measure Focus of the first part of the
– Collecting data course (modules 00-17)
– Analyzing data
 Measurement and improvement of Focus of the second

software’s internal characteristics, such as part of the course
(modules 18-20)
size, structure and complexity
 Measurement and improvement of software’s
external characteristics, especially quality Focus of the
third part of
– Definitions of Quality
the course
– Measurement of Quality (modules 21-
38)
– Analysis of Quality Problems
– Methods of Quality Improvement
CSE 6329-002 M00 - Version 20.01
8
How Grades are Determined
 Assignments will count 70% of the grade

– 10% for A1 - Personal WBS / burn down chart
– 20% for A2 – Defect analysis spreadsheet/report
– 20% for A3 – Software Complexity Measures
– 20% for A4 – DMAIC / Root Cause Analysis
 Exams (midterm and final) will count 30%

of the grade (15% each)

CSE 6329-002 M00 - Version 20.01
9
Terminology Used in This Class
 An assignment is evaluated (by the grader, the

instructor, or other students) to provide
suggestions for improvement and other feedback
Smallcollegeathletics.com
 An assignment is graded (by the grader and

instructor) to contribute to the final course grade
CSE 6329-002 M00 - Version 20.01
10
Major Student Assignments (summary)
1. Personal Work Breakdown Structure (PWBS)

– PWBS is a way to:
 estimate the work required to complete this course and
keep track of what work has been completed / what work is
yet to be done
 track and show progress on completing the work, via
– a Burn Down chart,
– a Burn Up chart, and
– an Earned Value chart.
2. Analysis of Defects
– From a small amount of data you can learn a lot by doing
proper analysis

CSE 6329-002 M00 - Version 20.01
11
Major Student Assignments
(summary) (continued)
3. Software Complexity Measurement
– Complexity is an indicator of many things
 Likelihood of errors
 Difficulty of maintenance
– You will write a small program in C, analyze it for complexity,
and then analyze the programs of other students
4. DMAIC and Root Cause Analysis

– Getting past the symptoms to the underlying cause(s) of a
problem

CSE 6329-002 M00 - Version 20.01
12
Personal WBS and Burn Down Chart
(concept)
A WBS is a Charts such as this one tell

hierarchical list of tasks to be you what has been
performed or work to be accomplished vs the plan
completed
It shows how you are doing
A plan for doing something relative to your plan
CSE 6329-002 M00 - Version 20.01
13
Personal WBS and Burn Down Chart
(as used in this course)
A WBS is a Charts such as this one tell

hierarchical list of tasks to be you what has been
performed or work to be accomplished vs the plan
completed
It shows how you are doing
A plan for the course relative to your plan
CSE 6329-002 M00 - Version 20.01
14
Personal Work Breakdown Structure
(PWBS) Process
Week  1 2 3 4 … 15 16
Produce Produce Produce

DRAFT INTERIM FINAL
PWBS PWBS PWBS
Track Track Track Track Track

Progress Progress Progress Progress Progress
Student
Evaluate Grade Grade

DRAFT INTERIM FINAL
Instructor PWBS PWBS PWBS
/ grader

CSE 6329-002 M00 - Version 20.01
15
Personal Work Breakdown Structure (PWBS)
Process Detail (slide 1 of 2)
Week 1:
– Lecture will cover the WBS and charts and what is expected
for the assignment
– Student will produce a DRAFT of their PWBS
– Student will track progress during week 1
Week 2:
– Student will submit DRAFT PWBS for evaluation
– grader/instructor will evaluate the draft PWBS
– grader/instructor will provide comments to student
– Student will make corrections and updates
– Student will track progress during week 2

CSE 6329-002 M00 - Version 20.01
16
Personal Work Breakdown Structure (PWBS)
Process Detail (slide 2 of 2)
Week 3:
– Student will track progress for week 3
– Student will produce an INTERIM PWBS
Week 4:
– grader/instructor will grade the draft PWBS
– grader/instructor will provide comments to student
– Student will make corrections and updates
Weeks 5-15:
– Student will track progress
Week 16:
– Student will turn in the FINAL PWBS
 Showing final data and charts
CSE 6329-002 M00 - Version 20.01
17
Course Schedule
Lectures focus on
First Measurement
Half
As
Midterm Examination si
gn
m
Lectures focus on en
Quality ts
Second
Half
Engineering
Final Examination

CSE 6329-002 M00 - Version 20.01
18
Teaming
For A1 (assignment 1), you must work alone!!!

But you should coordinate with your teammate (if
you have one)
See the SOW for A1 for further instructions.

CSE 6329-002 M00 - Version 20.01
19
Teaming
For assignments 2, 3, and 4 you may choose to work

in teams of two
– But you must inform the instructor and grader of this
when you turn in each assignment

CSE 6329-002 M00 - Version 20.01
20
Not Teaming
Students may (if they prefer) work individually on any

assignments
Students must work individually on:

 A1 – PWBS (but may coordinate with team mate)
 E1 (midterm exam)
 E2 (final exam)

CSE 6329-002 M00 - Version 20.01
21
Submitting Assignments
 Submit all assignments via the Canvas system.
 All queries should go to the instructor / grader via e-mail in the

Canvas system.
 If the Canvas is insufficient, you can also contact the instructor

at:
– Email: dennis.frailey@uta.edu
– Phone: --
– Fax: 817-272-3784
(do not use Fax except with advance approval)
All
All correspondence
correspondence regarding
regarding the
the course
course that
that is
is intended
intended for
for the
the
instructor
instructor MUST
MUST be
be sent
sent via
via Canvas
Canvas or
or to
to the
the e-mail
e-mail address
address above.
above.
CSE 6329-002 M00 - Version 20.01
22
Meeting Times
Course Meets in WH 208
Class Time:
Friday, 1:00-3:50pm
January 24 – May 1
All assignments are due:

no later than May 2
______________________________________________________________________

CSE 6329-002 M00 - Version 20.01
23
Correspondence by Mail
 For normal mail delivery, use:

University of Texas at Arlington
Computer Science and Engineering
attn: Dennis Frailey
500 UTA Boulevard, Room 640
Box 19015
Arlington, TX 76019
 For overnight mail delivery, use:

University of Texas at Arlington
Computer Science and Engineering
attn: Dennis Frailey
500 UTA Boulevard, Room 640
Arlington, TX 76019

CSE 6329-002 M00 - Version 20.01
24
Course Structure
 14 lecture sessions (one of these will be a

midterm examination session)
 Final exam in May (May 8)
 Each lecture session covers three modules
– ~50-minute Modules
– Short break roughly every 50 minutes

CSE 6329-002 M00 - Version 20.01
25
Examinations & Assignments
Examinations
Midterm March 20 15% of grade
Final May 8 15% of grade
Assignments
(see separate handouts for more details)
A1 PWBS 10% of grade
A2Defect Analysis 20% of grade
A3 Complexity Analysis 20% of grade
A4 DMAIC/Root Cause Analysis 20% of
grade

CSE 6329-002 M00 - Version 20.01
26
Obtaining Course Materials
 All material will be downloaded from the Canvas

system
 Exams will be downloaded from and uploaded to
Canvas (or we may give paper exams)

CSE 6329-002 M00 - Version 20.01
27
Submitting Examinations
 For paper exams:
– Bring a pen or pencil and write very legibly
– Put answers in the space provide
 You may also write on the back of the page
 For computerized exams:

– The examination will be a Microsoft Word document
– You will need a computer to do the examination
 Or we may do the exam in a classroom that has computers
– The examination should be completed on the form
supplied and in the space provided
 You may insert extra space if required
– Submit the examination directly via Canvas
CSE 6329-002 M00 - Version 20.01
28
Re-Evaluation of Grades
 Graders and instructors

occasionally make mistakes
when grading assignments and
examinations
 You may present any graded assignment or exam for re-

evaluation
– You must explain exactly which part was graded incorrectly and why
your answer was correct
– The grader or instructor will re-evaluate the entire exam or
assignment, not just the part where you believe an error was made.
– This may result in a higher grade.
– It may also result in a lower grade.

CSE 6329-002 M00 - Version 20.01
29
Course Slides
 Download from Canvas system for this course

 PowerPoint® format
 The slides are not complete. You should take notes
as you listen to the lectures.
 The slides use some fonts and other features that
may not work on your computer
– you may need to adjust fonts or copy down material during
lectures
 If you print the slides, hard copy can be in black and
white or color. Looks OK either way.
PowerPoint® is a trademark of Microsoft Corporation

CSE 6329-002 M00 - Version 20.01
30
Course Handouts
 Microsoft Word® format

 Microsoft PowerPoint® format
 Microsoft Excel® format
 PDF format for some reference materials
 General Handouts:
– Syllabus, welcome memo, schedule, etc.
 Assignment Handouts:
– A “statement of work” (SOW) for each assignment
 Tells what you must do and what you must deliver
– A “template” for some assignments
 Shows the format for those assignments

CSE 6329-002 M00 - Version 20.01
31
Always Use a Cover Sheet!
Each
Assignment assignment
template
also
contains
Cover Sheet the cover
Last Page
of SOW
sheet.
The
you cove
how r she
e
allo poin t tel
cat ts a ls
ed . re

CSE 6329-002 M00 - Version 20.01
32
Words to the Wise
Each assignment and each exam must be
– A single document (usually a “Word™” or “PowerPoint™” or “Excel™” or text document)
[or in a few cases, several separate documents]
– With the proper cover page
– With your name on it!
 If I have two students with the same document name, I won’t know which belongs to
which
– With the following file name: ent
g nm
 An CSE6329-002 2020sp last first.docx Assi
 E1 CSE6329-002 2020sp last first.docx Midterm Exam

 E2 CSE6329-002 2020sp last first.docx Final
Exam
– Example:
 E1 CSE6329-002 2020sp Jones Peter.docx
CSE 6329-002 M00 - Version 20.01
33
File Naming for
Team Assignments
Each assignment must have:
 Both names on it! Last name and first initial.
 In alphabetical order by last name
 With the following file name:

An CSE6329-002 2020sp Last1 F1 Last2 F2.docx
 Example:
A3 CSE6329-002 2020sp Report Jones P Shah M.docx
If an assignment has multiple deliverables, you

may distinguish them in the file name

CSE 6329-002 M00 - Version 20.01
34
Textbook
 The course slides are your primary course textbook!

– Take good notes when reading the slides, listening to
lectures, reading FAQs on the web site, asking questions,
talking with classmates, etc.
– You have permission to use the course slides after the class
is over if you retain the copyright statement and do not use
them for commercial purposes
 There is a strongly recommended textbook (but not

mandatory):
Fenton, Norman and James Bieman, Software Metrics – A Rigorous
and Practical Approach, Third Edition.

CSE 6329-002 M00 - Version 20.01
35
About the Fenton Textbook
The course, especially the first half, will

follow the overall outline of this book and
will use many examples from this book.
However not everything in the course is in

the book, and not everything in the book is
in the course.
The UTA library has made the book

available electronically.
https://login.ezproxy.uta.edu/login?url=http
://www.utarl.eblib.com/EBLWeb/patron/?ta
rget=patron&extendedid=P_1575383_0
CSE 6329-002 M00 - Version 20.01
36
Other Highly Recommended
References
These books relate to some portions of the course.
Root Cause Analysis will be helpful with assignment 4.
See the syllabus for details on these books.

CSE 6329-002 M00 - Version 20.01
37
More Recommended References
SWX – The Software Extension to the Project

Management Body of Knowledge, available from
PMI (www.pmi.com) and the IEEE Computer Society
(www.computer.org).
– This is a general reference that may be important if you
want to apply metrics and quality engineering techniques
in project management.
SWEBOK – The Guide to the Software Engineering
Body of Knowledge, available from the IEEE
Computer Society and also at www.swebok.org
– This is another general reference that covers topics that
any software engineer should know about.

CSE 6329-002 M00 - Version 20.01
38
Things to Do Immediately
(if you have not already done so)
1. Read the Welcome Memo (on Canvas)
2. Review the Syllabus and Schedule (on Canvas) –

these tell you all the basic facts about the course
3. Send me your Student Profile (so I have

background and contact information)
4. Decide whether you want to team with someone

else on the assignments
– If so, BOTH of you must send an email (via Canvas) to
me and the grader, saying you wish to be partners

CSE 6329-002 M00 - Version 20.01
39
Advice
The
The sooner
sooner you
you get
get behind,
behind, the
the
longer
longer you
you have
have to
to catch
catch up.
up.
 In other words,start on the
assignments right away

CSE 6329-002 M00 - Version 20.01
40
Typical Student – Week 1
Finding the Library

CSE 6329-002 M00 - Version 20.01
41
Typical Student - Week 2
Looking for Shortcuts

CSE 6329-002 M00 - Version 20.01
42
Typical Student - Weeks 3-n
Learns Additional Techniques

CSE 6329-002 M00 - Version 20.01
43
Typical Student – Just Before
Assignment or Exam is Due

CSE 6329-002 M00 - Version 20.01
44
Typical Student – After Assignment or
Exam is Graded
1. Denial: You miscalculated my grade!

2. Anger: I am a good student; I don't deserve this grade!
3. Bargaining: Can I do an extra project to raise my
grade?
4. Depression: If I don't get a good grade in this course
my future will be ruined!
5. Acceptance: Can you give me permission to take the
course again?

CSE 6329-002 M00 - Version 20.01
45
Summary of Module
At the end of most modules there will be one or more

slides highlighting important points that were covered
in that module
– This means that these points are important.
– It does NOT mean you don’t need to learn any of the other
things covered in the module!

CSE 6329-002 M00 - Version 20.01
46
Sample Exam Questions
There may also be a few slides showing sample exam

questions based on material covered in the module
– This may help you study the materials
 You should be able to answer any of the sample exam questions
– It does not mean that an exam will contain any of these

questions!
 But it might
– An exam might contain different questions

CSE 6329-002 M00 - Version 20.01
47
References
 Many modules will have a list of references at the end

 For example, here are some books mentioned in this
module
Andersen, Bjorn and Tom Fagerhaug, Root Cause Analysis, 2nd
Edition, Quality Press, Milwaukee, WI, 2006. ISBN 13: 978-0-
87389-692-4.
Fenton, Norman and James Bieman, Software Metrics: A
Rigorous and Practical Approach, Third Edition, Chapman and
Hall, 2014. ISBN 978-1439838228.
Weinberg, Gerald M. Quality Software Management, Volume 1,
Systems Thinking, Dorset House, New York, 1992. ISBN: 0-
932633-22-6.
CSE 6329-002 M00 - Version 20.01
48
References (continued)
Other items mentioned in this module
P. Bourque and R.E. Fairley, eds., Guide to the Software

Engineering Body of Knowledge, Version 3.0, IEEE Computer
Society Press, 2014. ISBN 978-0769551661. Available at
Amazon.com and at www.swebok.org. PDF format version is
available free of charge.
Project Management Institute, SWX – The Software Extension to

the PMBOK Guide Fifth Edition, Project Management Institute,
2013. ISBN 978-1628250138. Available at Amazon.com and at
www.pmi.org/software. PMI Product 001-01457501.

CSE 6329-002 M00 - Version 20.01
49
Appendix A
A few modules will have one or more

appendices, providing additional information
beyond what was covered in the lecture.
CSE 6329-002 M00 - Version 20.01
CSE 6329-002 M00 - Version 20.01
The UTA Honor Code
 All students are expected to abide by the UTA honor

code
 This code says that you will not plagiarize
 This code is taken seriously

CSE 6329-002 M00 - Version 20.01
52
Common Situations where Plagiarism
Must Be Guarded Against
1. A student from a previous semester shows you his
or her solution to an assignment
2. Another student from the class (not your team-
mate) wants to compare solutions to an
assignment or techniques for doing the assignment

CSE 6329-002 M00 - Version 20.01
53
What is Permitted
You may look over what the other student did or talk
to the other student to learn:
– The approximate size of the assignment
– Roughly what the assignment consists of
– What must be done to complete the assignment
– Suggestions about what parts are more difficult or
techniques to use when completing certain parts of the
assignment
– How to do specific things, such as:
 How to draw a graph in Excel®
 How to make a table in Word®
 How to use formulas in Excel®

CSE 6329-002 M00 - Version 20.01
54
What is NOT Permitted
 Copying anything from the other student’s

assignment
– Text in a report
In previous semesters, several
– Diagrams students have lost credit
because they copied material
– Spreadsheets from other students.
– Graphs
 Getting assignment answers from the other student

– What tasks should I put in my PWBS? (A1)
– What is the root cause of this problem? (A4)

CSE 6329-002 M00 - Version 20.01
55
Warning
 Each semester I change each assignment
and use different exam questions
Last Semester Next Semester
 So if you copy from a student in a previous

semester, I will usually know you did.
CSE 6329-002 M00 - Version 20.01
56
Key Issues
 Did you do your own work?

 Did you learn the material?
Magnapubs.com
Menafeeassociates.com Blog.noplag.com
Timeshighereducation.com
Kidshealth.org
Thielmann.blogspot.com

CSE 6329-002 M00 - Version 20.01
57
Possible Consequences of Plagiarism
 A grade of 0 on the
assignment
 A lower grade in the course
 Failure in the course May be decided by the
instructor or the UTA
 Failure to graduate on time Honor Council
 Suspension from UTA
 Expulsion from UTA

CSE 6329-002 M00 - Version 20.01
58
Teaming
 If you team with another student, you produce your

assignments as a team.
 You may discuss all assignments and work together to
produce assignment deliverables
– Both team members should know how to do all parts of each
assignment
 You must take all examinations separately

– Exams may have questions based on your understanding of
the assignments

CSE 6329-002 M00 - Version 20.01
59
END OF
MODULE 00

CSE 6329-002 M00 - Version 20.01
60

UTA CSE 6329-002 Advanced Topics in Software Engineering Software Measurement and Quality Engineering

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UTA CSE 6329-002 Advanced Topics in Software Engineering Software Measurement and Quality Engineering

Uploaded by

Copyright:

Available Formats

UTA CSE 6329-002

Advanced Topics in Software

Software Measurement and

Copyright 2020, Dennis J. Frailey

PhD Purdue, 1971, Computer Science

Copyright 2020, Dennis J. Frailey

"To measure is to know."

Source: Popular Lectures and Addresses, vol. 1,

This course is intended to cover:

Software Quality Software Quality

These will be useful for any software developer or

Copyright 2020, Dennis J. Frailey

For most topics, we will explain how a technique or method can

 Measurement and improvement of Focus of the second

 Assignments will count 70% of the grade

 Exams (midterm and final) will count 30%

Copyright 2020, Dennis J. Frailey

 An assignment is evaluated (by the grader, the

 An assignment is graded (by the grader and

1. Personal Work Breakdown Structure (PWBS)

Copyright 2020, Dennis J. Frailey

4. DMAIC and Root Cause Analysis

Copyright 2020, Dennis J. Frailey

A WBS is a Charts such as this one tell

A WBS is a Charts such as this one tell

Produce Produce Produce

Track Track Track Track Track

Evaluate Grade Grade

Copyright 2020, Dennis J. Frailey

Copyright 2020, Dennis J. Frailey

Copyright 2020, Dennis J. Frailey

For A1 (assignment 1), you must work alone!!!

Copyright 2020, Dennis J. Frailey

For assignments 2, 3, and 4 you may choose to work

Copyright 2020, Dennis J. Frailey

Students may (if they prefer) work individually on any

Students must work individually on:

Copyright 2020, Dennis J. Frailey

 All queries should go to the instructor / grader via e-mail in the

 If the Canvas is insufficient, you can also contact the instructor

(do not use Fax except with advance approval)

Course Meets in WH 208

All assignments are due:

Copyright 2020, Dennis J. Frailey

 For normal mail delivery, use:

 For overnight mail delivery, use:

Copyright 2020, Dennis J. Frailey

 14 lecture sessions (one of these will be a

 Final exam in May (May 8)

 Each lecture session covers three modules

– Short break roughly every 50 minutes

Copyright 2020, Dennis J. Frailey

Copyright 2020, Dennis J. Frailey

 All material will be downloaded from the Canvas

Copyright 2020, Dennis J. Frailey

 For computerized exams:

 Graders and instructors

 You may present any graded assignment or exam for re-

Copyright 2020, Dennis J. Frailey

 Download from Canvas system for this course

PowerPoint® is a trademark of Microsoft Corporation

Copyright 2020, Dennis J. Frailey

 Microsoft Word® format