SE652 - Summer 2007


TSPi Tool

Team List

Cycle 2 Test Status


Course Code:    SE 652 - C50
Course Title:    Software Quality Management
Semester:    Summer, 2007
Catalog Description:    Management issues regarding the software process. This course is centered around the concept of management for quality in software processes. It covers the three fundamental elements in the management of software processes: policies, procedures and tools. It examines how software processes are defined, established, monitored and controlled in a continuous cycle of planning, doing, checking and acting to improve its quality and therefore the quality of the resulting product. The ISO 9001 and SEI's Capability Maturity Models (CMM) are discussed. Prerequisite: None
Course Overview & Objectives “The major problems of our work are not so much technological as sociological in nature.”  So reads the self-proscribed thesis for DeMarco & Lister’s landmark book, Peopleware.  In most development organizations managers spend most of their time solving technical problems, instead of addressing the political & interpersonal issues that are the real culprits for the high failure rate of software projects.  Similarly, we teach students the virtues of use-cases and spiral development models, frequently ignoring the true keystones of student success in the project world:  teamwork, collaboration and the processes that tie everything together.

This course has two primary objectives:

1) To help students develop a broad understanding of the requirements and considerations in planning, managing and implementing a software project, with special emphasis on teams, quality, processes & metrics.  

2) To help students understand (and experience) the role and importance of sociological issues and how to address them in a way that substantially increases the probability of project and personal success.  It is based on the premise that software engineering is so much more than the technical disciplines. 

Class Schedule:    Thursday 4:30-7:45pm
Instructor:    Adjunct Prof. Lee Vallone
Office Hours:    By appointment
Office Location:    TBD
E-mail address:
Telephone:    Office – 732-949-4651
    Mobile – 908-313-2053

Required Texts:

DeMarco, Tom & Lister, Timothy; Peopleware: Productive Projects & Teams;  Dorset House, 1999

Humphrey, Watts S.; Introduction to the Team Software Process;  Addison Wesley, 2000

McGarry, John,; Practical Software Measurement; Addison Wesley , 2002

Recommended Readings:

Humphrey, Watts S.; Introduction to the Personal Software Process; Addison Wesley, 1997

Yourdon, Edward; Death March; Prentice Hall, 1999

Brooks, Frederick P.; The Mythical Man-Month; Addison Wesley, 1995

Adams, Scott; The Dilbert Principle; Harper Business, 1996

Chrissis, Mary Beth,; CMMI: Guidelines for Process Integration and Product Improvement; Addison Wesley, 2003

Other Referenced Readings:

Zachary, G. Pascal; Showstopper!; Free Press, 1994

Jones, Capers; Software Assessments, Benchmarks, and Best Practices; Addison Wesley, 2000

Course Requirements: Students should complete the reading assignments before coming to class. Lecture will frequently not match contents of the reading, so class attendance is important. Participants will work in groups to plan and implement two iterations of the TSP change counter project.  The instructor will be available to informally review progress plan throughout the semester. Teams will periodically present their project status & metrics to the class for review and discussion.  In addition, each team will maintain a project notebook that will be handed in to the instructor.  In addition to the team project, there will be a final exam.

Methods of Evaluation and Grading Policy:

Attendance Requirement: Attendance at all sessions is mandatory, although accommodations will be made for extraordinary circumstances. 

Last date to withdraw with an automatic assignment of "W" grade:

Statement on Academic Honesty: All materials and exams must be your own individual work. Exams will be open book. The team project, presentations and classroom discussions are expected to be done by teams of students openly sharing information with each other. Monmouth University will not tolerate violations of the code of academic honesty

Statement on Special Accommodations: Students with disabilities who need special accommodations for this class are encouraged to meet with me or the appropriate disability service provider on campus as soon as possible. In order to receive accommodations, students must be registered with the appropriate disability service provider as set forth in the student handbook and must follow the University procedure for self-disclosure, which is stated in the University Guide to Services and Accommodations for Students with Disabilities. Students will not be afforded special accommodations for academic work done prior to completion of the documentation process with the appropriate disability service office.


Outline of Course Content and Schedule





Forms & Classroom Materials

May 22

Overview of class and team project

PSP Refresher


Student Info Sheet (.doc)
Tracking time exercise
Tracking time answer

LOC counting exercise 
LOC counting answer

May 29

Team Exercise



 Peopleware, Ch 10 & 11

Humphrey, Ch. 1, 2, 3, 4
Appendix A & E

  Project Plan Template

Meeting Minutes Template

June 5

Team Survival Behaviors

Concept Phase & Risks

Configuration Management

Project Planning (Cycle 1)



Humphrey, Appendix B

Humphrey, Ch 5

Project Plan

Cycle 1 Project Presentations


June 12

Configuration Management

Project Requirements & Inspections (Cycle 1)

Design Phase

Humphrey, Ch. 6 & Appendix C


SRS for Inspection

Updated ITL

Plan, Sched, etc. Forms

SRS Template

Inspection Form (INS)
Defect Log (LOGD)


Baseline Sheet

June 19

Code Inspection

Measurement Plan

Project Design & Integration Test Plan (Cycle 1)

System Test


McGarry, Chapters 2, 3 & 4

Humphrey, Ch. 7

CM Plan

Baselined SRS including quality records

Baselined HLD (SDS), Design/Coding Stds & ITP

System Test Plan for Inspection

Code for inspection

Collated code inspection comments

June 26

Project Implementation Complete (Cycle 1)

Integration Test Complete

System Test Start
(link to slides)

Mythical Man Month

Measurement topics (continued from 19 June)

Humphrey, Ch. 8




Test Plan Inspect by June 21

Test Plan baseline by June 24

Code Complete

Updated Test Plan

spell INS completed INS form

spell review comments w/ disposition


July 3

No Class

Cycle 1 System Test Complete

Humphrey, Ch. 9

McGarry Chapter 5

Final Cycle 1 code, SRS, Test Results, LOGD, CCRs


July 10

Project Post-Mortem (Cycle 1)

Team Assessments

Peopleware Topics

Humphrey, Ch. 10, 16, 17 & 18

Humphrey, Ch. 11 - 15

Peopleware - all chapters

Cycle 1 Post Mortem Presentation

Cycle 1 Post Mortem report

Final Cycle 1 Work Products

Peer Evaluation Form

Team Leader Eval Form

July 17

Phase 2 Launch & Plan

Peopleware Topics (continued)




Cycle 2 Project Plan

Project Measurement Plan


July 24

Requirements (Cycle 2) & Inspection

Death March Projects

Config Mgmt - IEEE 828-1998

Cycle 2 Requirements



July 31

Design & Implementation Complete (Cycle 2)

Process (CMMI, TL9000, ...)


Cycle 2 SDS & ITP updated stds

Cycle 2 System Test Plan

August 7

Cycle 2 System Test Complete

Miscellaneous Topics


Cycle 2 System Test Quality Records

Cycle 2 insights presentation


August 14

Post Mortem (Cycle 2)

Case Discussion

Course Review

Team audits (outside class)


Cycle 2 Post Mortem Presentations

LOC counter demo w/ cycle 1 & cycle 2 code

Case prep

Course Feedback Survey
(please return to
 Terry Powers)

Special Thanks: The contents of this web page are based on Jim McDonald's SE518 course page.