• Instructor: Dr. Dennis J. Frailey
• Course Handouts And Other Information may be found at the course web site
• Office Hours: By Appointment and by internet communication (No Appointment Required for brief meetings after class)
• Schedule: CLASS TIME: Varies - see web site.
• Exams: Quiz at end of class each day 10% of grade for each.
• Assignments: 1 data analysis assignment given on day 3 (20% of grade) - requires use of a spreadsheet and word processor - due 2 weeks after end of course 1 major - a quality improvement plan (30% of grade), completed within 1 month of the end of the course
• Each student will prepare a comprehensive quality improvement plan for her or his organization or for a hypothetical organization whose details and data are provided by the instructor.
• Grading: 30% for plan; 20% for data analysis assignment; 10% each for daily quizzes.
• Grading Scale and Expectations:.A: 93-100; A-: 90-92; B+: 88-89; B: 83-87; B- 80-82; C+: 78-79; C: 73-77; C- 70-72; and so forth.
• No 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 problem presented in the examination or assignment.
• Rote memorization 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.
• Policy for Missed Classes: The student is expected to make up for missed lectures by obtaining a recording of the lecture or communicating with other students.
• Policy for Late Work: All work is due when scheduled. Late work will not be accepted except under extraordinary circumstances.

This course is intended for software engineering managers, and software developers progressing towards leadership positions, who have not received formal instruction in software engineering principles and best practices.

At least a year’s experience in software development, planning or management outside of the classroom enviromnent (i.e., development of software that will be delivered to a customer); ability to use a word processor and spreadsheet; completion of courses in Software Project Planning and Management and Software Testing.

• (G2) Grady, Robert B. Practical Software Metrics for Project Management and Process Improvement. Englewood Cliffs, N.J., Prentice-Hall, Inc., 1992. ISBN 0-13- 720384-5. (This is a follow-on to G1, reflecting what has been learned in the 5 years since it was published, and delving into more detail - especially with respect to software process improvement.) This book has periodically been out of print, and is not essential for completing the coursework, but should be obtained if available because it relates to many of the coure lectures.
• (W1) Weinberg, Gerald M. Quality Software Management, Volume 1, Systems Thinking, Dorset House, New York, 1992. ISBN: 0-932633-22-6. (Explores quality improvement with many insights from a psychological and cultural point of view.)
• (Ba) Baumert, John H., and Mark S. McWhinney, Software Measures and the Capability Maturity Model, CMU/SEI-92-TR-25, ESC-TR-92-025, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pa., 1992. (Identifies which measures can reasonably be expected at various levels of the SEI maturity model.)
• (De) DeMarco, Tom, Controlling Software Projects: Management, Measurement, and Estimation, New York, Yourdon Press, 1982. (Practical guidance for collecting and analyzing software measures).
• (D) Dobbins, James H. Software Quality Assurance and Evaluation. (A good review of the conventional view of software quality assurance.)
• * (Do) Department of Defense, Joint Logistics Commanders Joint Group on Systems Engineering, Practical Software Measurement, a Guide to Objective Program Insight (version 2.1), Naval Undersea Warfare Center, c/o John McGarry, mcgarry@ada.npt.navy.mil. (Explains basic concepts of the software measurement process and offers detailed implementation guidance as well as realistic case studies from the DoD environment.)
• (F) Fenton, Norman E. Software Metrics: A Rigorous Approach, Chapman & Hall, London SE1 8HN, 1991. ISBN 0-442-31355-1. (This book is an excellent discussion of software measurement, based on fundamental theory. Provides specific tools to overcome deficiencies of typical measurement programs.)
• * (G1) Grady, Robert B. and Deborah L. Caswell, Software Metrics: Establishing a Company-Wide Program. Englewood Cliffs, N.J., Prentice-Hall, Inc., 1987. ISBN 0-13-821844-7. (Good description of the issues faced by a company developing a measurement program.)
• (I1) IEEE Std 1045-1992. IEEE Standard for Software Productivity Metrics. New York, Institute of Electrical and Electronics Engineers, Inc. (Describes more than 30 software measures that can be used to consistently define software productivity.)
• (I2) IEEE Std 1061-1992. IEEE Standard for a Software Quality Metrics Methodology. New York, Institute of Electrical and Electronics Engineers, Inc. ISBN 1-55937-277-X. (Defines a methodology for establishing quality requirements and identifying, implementing, analyzing, and validating the process and product of software quality metrics [from the abstract])
• (J1) Jones, Capers Applied Software Measurement: Assuring Productivity and Quality. McGraw-Hill, Inc., 1991. ISBN 0-07-032813-7. (This book contains a large selection of possible measures.)
• (M1) Marciniak and Evans. Software Quality Assurance and Management. (Recommended by several SQA professionals)
• (M2) Möller, K. H. and D. J. Paulish. Sotware Metrics: A practitioner's guide to improved product development. London, Chapman & Hall Computing, 1993. ISBN 0-412-45900-0. Also available from IEEE Press, ISBN 0-7803-0444-6. (This is a report on experiences at Siemens/Nixdorf corporation, performed largely as part of the PYRAMID research project, funded by the Esprit II program.)
• (S) Schulmeyer, G. Gordon. Zero Defect Software. McGraw Hill, 1990. ISBN 0-07-055663-6. (Comprehensive coverage of the subject by one of the originators of the concept.)
• (H) Schulmeyer, G. Gordon and James McManus. Handbook of Software Quality Assurance, Second Edition. Van Nostrand Reinhold, New York, 1992. ISBN 0-442-00796-5. (One of the best references on conventional SQA.). The third edition, published in 1999, is more up to date but not all of the sections map to each other.
• * (W2) Weinberg, Gerald M. Quality Software Management, Volume 2, First Order Measurement, Dorset House, New York, 1993. ISBN: 0-932633-24-2. (Second volume in series -- expands coverage into the area of measurement.)
• (W3) Weinberg, Gerald M. Quality Software Management, Volume 3, Congruent Action, Dorset House, New York, 1994. ISBN: 0-932633-28-5. (Discusses the role of management in achieving a high quality software program. Applies Myers-Briggs behavior type indicators to discuss patterns of behavior in software organizations and how managers can use this knowledge to improve. Stresses the difference between knowing and doing.)
• (W4) Weinberg, Gerald M. Quality Software Management, Volume 4, Anticipating Change, Dorset House, New York, 1996, ISBN: 0-932633-32-3. (Focuses on how change really happens and how to manage it.)
• (X) Xie, M. Software Reliability Modelling, World Scientific, London, 1991. ISBN 981-02-0640-2. (This hard-to-find book is a solid, theoretical look at software reliability).

Dr. Dennis J Frailey is a Principal Fellow at Raytheon Company in Plano, Texas and an Adjunct Professor of Computer Science at Southern Methodist University. He also teaches courses in software engineering and computer science for UCLA, National Technological University and the University of Texas Software Quality Institute.
At Raytheon, his primary duties are to provide technical and management support to software development projects. This includes writing proposals, negotiating program plans, estimating cost, reducing cycle time, and solving complex computational problems.