CSSE3002
Suggested Readings
Useful references for Risk
Management
(Good
introductory article) Software risk management: principles and practices by Bohem B. W in IEEE Software (you can access the article via
UQ library http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=62930&tag=1).
Social
and Technical Reasons for Software Project Failures by Capers Jones
CMU/SEI risk management Report
CMU SEI
resources for Risk Management
Some newer references:
Understanding the Roots of Process Performance Failure by Robert Charette, Laura Dwinnell and John McGarry
Liar, Fool or both? by Robert Charette
Failing Successfully by Bob Charette
Mortality
Play: the cost of risk on software Projects Phillip G. Armour
Communications of the ACM, 50,(3):15-18, March 2007
(accessible via UQ databases on library webpage - find the ACM
Digital library)
How Software Estimation Tools Work by Capers Jones
Positive and Negative Innovations in Software Engineering by Capers Jones
Strengths and Weaknesses of Software Metrics by Capers Jones
The ROI of Software Process Improvement: A New 36 Month Case Study by Capers Jones
Karl Wiegers Describes 10 Requirements Traps to Avoid
Ten Software Process Improvement Traps to Avoid by Karl Wiegers
Articles on requirements
engineering:
So You Want to Be a Requirements Analyst? Software Development, vol. 11, no. 7 (July 2003). by Karl E. Wiegers
Habits of Effective Analysts, Software Development, vol. 8, no. 10 (October 2000). by Karl E. Wiegers
More
articles on requirements engineering from Process Impact
website
Specifying
Functional Requirements with Use Cases.
On-line tutorial from CRaG Systems
----------
The Standish Group's Chaos Report
How CMM impacts
quality, productivity, rework and the bottom line, Michael Diaz and Jeff
King
Ten Things
Your Mother Never Told You About the Capability Maturity Model, Margaret Kulpa
(there is an enormous amount of stuff at Crosstalk on
software process)
Requirements denial - examining
the excuses, Andrew Gabb
The Joel
test: 12 steps to better code, Joel Spolsky -
particularly read the story with 5. Do you fix bugs before writing new code?
(look around this site, there is a lot of
interesting stuff to read)
Why don't they practice what we preach?, Watts Humphrey
Three Process
Perspectives: Organizations, Teams and People, Watts Humphrey,
Annals of Software Engineering, 14, 39-72, 2002.
The many
dimensions of the software process, Sebastian Tyrrell,
Crossroads, 6-4, Summer 2000.
Software Development Process: A necessary evil, M,E. Fayad,
Communications of the ACM, 40,(9):101-103, September 1997
(accessible via UQ databases on library webpage - find the ACM Digital library)
The power of process,
Steve McConnell
(there are many good articles linked through this page)
Suggestions for additional relevant links are welcomed - e-mail David.
One
Hundred Rules for NASA Project Managers Jerry Madden,
Associate Director of the Flight Projects Directorate at NASA's Goddard Space
Flight Center, collected these 100 pieces of wisdom
over a number of years from various unidentified sources.
