The University of Western Australia
School of Computer Science and Software Engineering

School of Computer Science and Software Engineering

CITS5502 Software Processes

Project Management Proverbs

Nothing is impossible for the person who doesn't have to do it themselves.

The sooner you begin coding the later you finish.

Any project can be estimated accurately (once it's completed).

The most valuable and least used WORD in a project manager's vocabulary is "NO".

The most valuable and least used PHRASE in a project manager's vocabulary is "I don't know".

It takes one woman nine months to have a baby. It cannot be done in one month by nine women.

You can con a sucker into committing to an impossible deadline, but you cannot con him into meeting it.

At the heart of every large project is a small project trying to get out.

If you don't stand for something, you'll fall for anything.


This unit focuses on the underlying principles of software processes, their analysis, measurement and improvement. These principles are examined using current research-oriented and commercial implementations. Understanding the principles enables a student to select an appropriate process methodology for a specific software development environment, measure its effectiveness and improve the process over time. Topics covered include software process components; development life cycles; processes modelling and simulation; measuring and assessing process methodologies; and the meta process and methodology verification. Current process methodologies that are critically examined include Rational Unified Process, Personal Software Process/Team Software Process, Lightweight (Agile) Processes and OpenSource Process. A variety of software process improvement and assessment methodologies are examined including CMM, CMMI, 6Sigma, TQM and AMI-Bootstrap.

Unit coordinator: Dr. Du Huynh
Consultation: One hour after the workshop.
Lecturers: Professor Terry Woodings, Dr. Du Huynh

Textbook: There are no books which cover the full scope of this course. Students will be expected to seek out appropriate texts and research papers. Below are several useful books which will be referred to from time to time. Students wishing to specialise in this area may find it useful to purchase one or more of them. The Pressman and Sommerville texts on Software Engineering should also be useful.

On the concept of an individual's and team's software proecesses:
Watts Humphrey: "A Discipline for Software Engineering", Addison-Wesley, 1995
Watts Humphrey: "Introduction to the Personal Software Process", Addison-Wesley, 1997 (Google book)
Watts Humphrey: "Introduction to the Team Software Process", Addison-Wesley, 2000 (Science Library 005.1068 2000 INT, Google book)
B Walraet: "A Discipline of Software Engineering", Elsevier Science, eISBN 9781483294216, 2014 (EBook via UWA Library)

On the underlying theory of UML:
Walker Royce: "Software Project Management - A Unified Framework", Addison-Wesley, 1998. (Science Library 005.12 1998 SOF)

On Statistical Process Control:
William Florac and Anita Carleton: "Measuring the Software Process", Addison-Wesley, 1999. (Science Library 005.14 1999 MEA, Google book)

On models of Project Management:
Robert Wysocki: "Effective Software Project Management", Wiley, 2006. (Reid Library 3rd Floor 005.3068 2006 EFF, EBook via UWA Library (2008), Google book)

On Software Process Dynamics:
Raymond J. Madachy: "Software Process Dynamics", Wiley, 2007. (Wiley Online Library, IEEExplore)


Students must attend both lectures each week and the workshop. Lecture recordings are available (see link at left).
Type Time Day Location
Lecture 3 pm - 5 pm Tuesday Fox L.T. (Arts:G59)
Workshop 11 am - 12pm Thursday CSSE Seminar Room 1.24
Workshop (repeat) 12 pm - 1 pm Thursday CSSE Seminar Room 1.24


There are three specific assignments, a research project, plus presentation. There are no (semester or supplementary) examinations. Note that the final mark may be scaled in line with the Faculty's Policy on Assessment Practices and Procedures.

The first assignment, worth 20%, is on the classification of software processes. The second, worth 20%, is on the modelling and simulation of a process. The third, worth 25%, is on the measurement and optimisation of a process with respect to given criteria.

The subject for the research project and associated presentation will be chosen and tailored according to the needs and interests of each individual student. Students will be expected to display evidence of depth of thinking and research on the chosen topic. The research project is worth 25% of the final mark. The presentation is worth 10% and may be designed for either an academic or commercial audience.

In industry, there is usually a preference for an adequate job done early than a perfect job done late. Accordingly, projects may be marked on a sliding scale allowing extra marks for early submissions. That is, there will be a small adjustment of marks (up to 1% per day) for early or (down by 20% per day) for late submission of projects. The marking algorithm will be discussed in class and will be indicated on project sheets.

Assessment %of final mark Due Date
Assignment 1 20% Week 4, Tue Aug 22nd 3pm
Assignment 2 25% Week 6, Tue Sep 5th 3pm
Assignment 3 25% Week 9, Thu Oct 5th 3pm
Research project (group) 20% Week 13, Thu Nov 2nd 4pm
Presentation (group) 10% Week 11 onward

School of Computer Science and Software Engineering

This Page