CITS 3220
Recommended Books and
Articles for
Software Requirements and Project Management
Last updated July 2009
Searching for a copy of a paper online?
Try ieexplore http://www.ieeexplore.ieee.org/Xplore/DynWel.jsp,
ACM digital library and guide to computing literature http://portal.acm.org/
Google Scholar http://scholar.google.com/
CiteSeer Scientific Literature digital library at http://citeseer.nj.nec.com/cs
Wondering how to make sense of it all?
Try How
to Read An Engineering Research Paper, an excellent guide by Bill Griswold
Accessed http://www-cse.ucsd.edu/users/wgg/
November 2002
New recommendations for this
page are welcome. Please email citations
to help3220
Recommended Text Books
Pressman, Roger S. Software engineering : a practitioner's
approach 7th ed. McGraw-Hill, 2010, (also
see 6th ed at UWA MPSL 005.1
2005 SOF and 005.1
2000 SOF for 2000 edition)
Ian Sommerville, Software
engineering 7th Edition. Pearson/Addison-Wesley,
2004
UWA MPSL 005.1
2004 SOF
Other Books
Bernd Bruegge and Allen H Dutoit, Object-Oriented
Software Engineering, Prentice Hall, 2000, ISBN 0-13-017452-1, UWA MPSL 005.117
2000 OBJ
Boehm, B., Software
Engineering Economics, Prentice Hall, 1981, UWA MPSL 005.1068
1981 SOF
Brooks, F.P. The
Mythical Man-Month: Essays on Software Engineering, Addison-Wesley Pub.
Cockburn, A. Agile
Software Development, Addison Wesley, 2002, UWA MPSL 005.1
2002 AGI
Capers Jones, Patterns of Software Systems Failures and
Successes,
International Thompson Computer Press, 1996, ISBN 1850328048
Fenton, Norman and Pfleeger,
Freeman,
Peter. Software Perspectives The System is the Message Addison-Wesley
1987
A unique
book that delves into the underlying nature and quality of SW and the processes
use to create it.
UWA MPSL 005
1987 SOF
Gilb, T, Graham, T. and Finzi, S. Software Inspection, Addison-Wesley Longman, 2003
Hall, Elaine M. Managing risk :
methods for software systems development
Jacobson, Ivar, The unified software development process, Addison-Wesley, c1999, UWA MPSL 005.1 1999 UNI
Jacobson, Ivar, Object-Oriented
Software Engineering: A Use Case Driven Approach,
Leveson,
Nancy. Safeware: System Safety and Computers Addison-Wesley 1995 ISBN:
0-201-11972-2, UWA MPSL 629.890289
1995 SAF
Ould, Martyn
A. Strategies for software engineering : the management of risk and quality, Wiley,
c1990 UWA MPSL 005.1
1990 STR
Ould, Martyn
A. Testing in software development, Cambridge University Press
on behalf of the British Computer Society, 1986, UWA MPSL 005.14
1986 TES
Robertson,
Suzanne and Robertson, James, Mastering the Requirements Process, Addison
Wesley,1999
UWA MPSL 005.12 1999 MAS
Sommerville,
Ian and Sawyer, Pete. Requirements Engineering A Good Practice Guide,
Wiley,1997
UWA MPSL 005.1 1997 REQ
Richard H. Thayer and
Merlin Dorfman (editors), Software requirements engineering, IEEE
Computer Society Press 1997, UWA MPSL 005.12
1997 SOF (currently missing from the library)
Daniel R. Windle, L. Rene
Abreo, Software requirements using the unified process : a practical approach, Prentice
Hall, c2003, UWA MPSL 005.1
2003 SOF
Software Engineering Journals
Requirements
Engineering, Springer,
IEEE
Transactions on Software Engineering, ISSN: 0098-5589 http://ieeexplore.ieee.org/xpl/RecentIssue.jsp?punumber=32
Magazines
IEEE Software
IEEE
Computer
Articles (arranged by topic)
Software Engineering
Kitchenham, B.A. Dyba, T. Jorgensen, M. Evidence-based software engineering In Proceedings of the 26th International Conference on Software Engineering, 2004. ICSE 2004. page(s): 273- 281, 2004
Burnett, M,
Cook, C and Rothermel, G. End-user software engineering, Communications of
the ACM, Volume 47, Issue 9 (September 2004) Pages: 53 - 58 http://doi.acm.org/10.1145/1015864.1015889
ARIANE 5 Flight 501 Failure Report by the Inquiry Board, Paris, 19 July 1996, see http://www.niwotridge.com/Resources/DomainLinks/Ariane5Failure.htm for this report and many other resources
Brooks, Frederick P., No Silver Bullet: Essence and Accidents of Software Engineering, Computer, Vol. 20, No. 4 (April 1987) pp. 10-19.
Gibbs, W.W. (1994), 
Software''s
Chronic Crisis,
Scientific American 271, 3, 72–81.
Le Lann, G.; An analysis of the Ariane 5 flight 501 failure-a system
engineering perspective, Engineering of Computer-Based
Systems, 1997. Proceedings., International Conference and Workshop on
, 24-28 March 1997, Pages:339 – 346, http://ieeexplore.ieee.org/iel3/4458/12639/00581900.pdf
Leveson., Nancy, Medical Devices: Therac-25 In Software: System Safety and Computers, Addison-Wesley
Large 293KB An updated version of the
original 1993 Leveson and Turner paper on the Therac-25 accidents
Levenson N.G.; C.S. Turner. An Investigation of the Therac-25 Accidents, IEEE Computer, July 1993, pp. 18 – 41
Report on Project Management in NASA by the Mars Climate Orbiter Mishap Investigation Board March 13, 2000. Source http://mars.jpl.nasa.gov/msp98/misc/MCO_MIB_Report.pdf accessed February 2002 Large 464KB This comprehensive report includes an interesting survey of recurring themes from failure investigations and studies in Appendix F.
Swartz, A.J. Airport 95: Automated Baggage System?,
ACM Software Engineering Notes, vol. 21, no. 2, March 1996, pp. 79-83 http://doi.acm.org/10.1145/227531.227544
Sommerville, I. Systems engineering for software engineers, Annals of Software
Engineering, Volume
6, Numbers 1-4 / March, 1998, DOI 10.1023/A:1018901230131
Requirements Engineering
Anderson, Stuart., and Felici,
Massimo. Requirements
Evolution From Process to Product Oriented Management, In Proceedings of Profes 2001, 3rd International
Conference on Product Focused Software Process Improvement, Kaiserslautern,
Germany, September 10-13, 2001, LNCS 2188, Springer-Verlag, pp. 27-41. http://www.dirc.org.uk/publications/inproceedings/papers/7.pdf
Boehm, B. and Egyed, A., Software
Requirements Negotiation: Some Lessons Learned, Proceedings of the 20th
International Conference on Software Engineering, April 1998. http://sunset.usc.edu/~aegyed/publications/Software_Requirements_Negotiation-Some_Lessons_Learned.pdf
Burrel, Lenna, Brooke, Tim and
Beckwith, Richard, Vineyard Computing: Sensor Networks in Agricultural
Production, IEEE Pervasive Computing, vol Jan-March 2004, pp 38-45. http://www.ieeexplore.ieee.org/iel5/7756/28394/01269130.pdf
Debra Haley, Bashar Nuseibeh, HC Sharp, Josie Taylor: The Conundrum of
Categorising Requirements: Managing Requirements for Learning on the Move,
Proceedings of the Requirements Engineering Conference, 12th IEEE International
(RE'04) - Volume 00 Pages: 309 – 314,
2004 http://www.ieeexplore.ieee.org/iel5/9273/29455/01335688.pdf
Higgins, S.A.; de Laat, M.; Gieles,
P.M.C.; Geurts, E.M. Managing requirements for medical IT products, pp
26- 33, IEEE Software, Vol 20 (1), Jan-Feb 2003 http://www.ieeexplore.ieee.org/iel5/52/25969/01159025.pdf
David L. Parnas and Paul C.
Clements. A rational
design process: How and why to fake it. IEEE Transactions on Software
Engineering, SE-12(2):251-- 257, February 1986
Raghavan, Zelesnik and Ford, Lecture
Notes on Requirements Elicitation, Software Engineering Institute, Carnegie
Mellon University, CMU/SEI-94-EM-10, March 1994, http://www.sei.cmu.edu/publications/documents/ems/94.em.010.html
van
Lamsweerde, A.; Goal-oriented
requirements enginering: a roundtrip from research to practice,
Requirements Engineering Conference, 2004. Proceedings. 12th IEEE International
, Sept. 6-10, 2004, Pages:3 – 6, http://www.ieeexplore.ieee.org/iel5/9273/29455/01335648.pdf
Weber, M.; Weisbrod, J. Requirements engineering in automotive development:
experiences and challenges, pp 16- 24, IEEE Software, Vol 20 (1), Jan-Feb
2003 http://www.ieeexplore.ieee.org/iel5/52/25969/01159026.pdf
Project Management
McConnell, S.; Avoiding classic mistakes [software engineering], Software, IEEE, Volume 13, Issue 5, Sept. 1996 Page(s):111-112, Digital Object Identifier 10.1109/52.536469
VR Basili, G Caldiera, HD Rombach, The goal
question metric approach, Encyclopedia of Software Engineering, 1994 from
wwwagse.informatik.uni-kl.de
Boehm, B. Software Risk Management:
Principles and Practices, IEEE Software, 1991, Page(s): 32-41,
http://ieeexplore.ieee.org/iel1/52/2296/00062930.pdf
Fairley, R. Risk Management for Software
Projects, IEEE Software, 1994, http://ieeexplore.ieee.org/iel1/52/6975/00281716.pdf
Jinhua Li; Zhibing Ma;
Huanzhen Dong, Monitoring
Software Projects with Earned Value Analysis and Use Case Point, Computer and Information Science, 2008. ICIS 08.
Seventh IEEE/ACIS International Conference on , vol., no., pp.475-480, 14-16
May 2008
From IEEE Explore Digital Object Identifier: 10.1109/ICIS.2008.29
Lindvall,
M. and Sandahl, K., How Well do Experienced Software Developers Predict
Software Change?, Journal of Systems and Software, vol. 43, no. 1, pp.
19-27, 1998.
Rada, Roy and Craparo, John, Sharing Standards: Standardising Software Projects, Communications of the ACM, Vol 43, Issue 12, December 2000, http://delivery.acm.org/10.1145/360000/355117/p21-rada.pdf
Verification & Validation
Butler and Finelli, The Infeasibility of Quantification of Life Critical Software Reliability, ACM SIGSOFT Software Engineering Notes , Proceedings of the conference on Software for citical systems, Volume 16 Issue 5, http://delivery.acm.org/10.1145/130000/123054/p66-butler.pdf
L. Briand, J. Wuest, J. Daly, and V. Porter: Exploring the
Relationships Between Design Measures and Software Quality in Object Oriented
Systems. In Journal of Systems and Software. V7-02/11/99 22 http://citeseer.nj.nec.com/briand98exploring.html
R.-K. Doong and P. G. Frankl. The ASTOOT approach to testing object-oriented programs, ACM Transactions on Software Engineering and Methodology, Vol 3, Num 2, pp 101-130, 1994
Erdem, A., Johnson, W.L., and Marsella S. Task Oriented Software
Understanding. In Proceedings of the 13th IEEE International Automated
Software Engineering Conference, 230-239.
P.G. Frankl, R. Hamlet, B. Littlewood, and L. Strigini. Choosing a testing method to deliver reliability. In Proceedings of the 19th International Conference on Software Engineering IEEE Computer Society, 1997.
Filippo
Lanubile and Giuseppe Visaggio, Evaluating
Empirical Models for the Detection of High-Risk Components: Some Lessons
Learned, In 20th Annual Software
Engineering Workshop, November 29-30, 1995,
D.L. Parnas and J. Madey. Functional documents for computer systems. In Science of Computer Programming, 25:41--61, 1995. http://citeseer.nj.nec.com/parnas95functional.html
Peters, D.K. and Parnas, D.L: Requirements-based Monitors for Real-Time Systems, in International Symposium on Software Testing and Analysis 2000, ISSTA ’00, ACM Press.
Adam Porter, Harvey Siy, and
Martin,
D., Rooksby, J., Rouncefield, M., and Sommerville,