SEOC1 Resources

In the course we will use UML as the basis for the design of systems implemented in Java. The main resources for the course are:

Books

UML

Main Course Book: UML, Schaum's Outline Series, by Simon Bennet, John Skelton and Ken Lunn, McGraw-Hill, 2001, ISBN 0-07-709673-8. It is essential that you buy this book.
Perdita Stevens and Rob Pooley. Using UML: Software Engineering with Objects and Components. Addison-Wesley, 2000.
Sinan Si Alhir. UML in a Nutshell: A Desktop Quick Reference. O'Reilly, 1998.
Sinan Si Alhir. Learning UML. O'Reilly, 2003.
James Rumbaugh, Ivar Jacobson and Grady Booch. The Unified Modeling Language Reference Manual. Addison-Wesley, 1999.

Software Engineering

Background readings are taken from the book, Software Engineering (7th Edition) by Ian Sommerville. You should have encountered most of this last year in CS2.

Requirements Engineering

Suzanne Robertson and James Robertson. Mastering the Requirements Process. Addison-Wesley, 1999.
Gerald Kotonya and Ian Sommerville. Requirements Engineering: Processes and Techniques. John Wiley, 1998. The book has an associated set of OHP Transparencies (Powerpoint 4) which may be downloaded from the Accompanying Website. The VORD method which is introduced in the book as a viewpoint-oriented technique for interactive systems specification has an associated toolset, written in Java, which is available free of charge for all readers of the book.
Ian Sommerville and Pete Sawyer. Requirements Engineering: A good practice guide. John Wiley, 1997. The book presents requirements engineering guidelines which vary from the very simple, such as make sure that your requirements are given a unique identifier, to the very complex, e.g., use formal specification for safety-critical sysems. The book also includes three chapters which provide more detailed advice on system modelling, formal methods for specification and viewpoint-oriented requirements elicitation. The Accompanying Website provides links to resources with information on requirements engineering.
Dean Leffingwell and Don Widrig. Managing Software Requirements: A Use Case Approach. Addison-Wesley, Second Edition, 2003.

Software Metrics

Norman E. Fenton and Shari Lawrence Pfleeger. Software Metrics: A Rigorous and Practical Approach. Second Edition, International Thomson Computer Press, 1996.

Software Testing

William E. Perry. Effective Methods for Software Testing. Second Edition, John Wiley & Sons, 2000.

Safety-Critical Systems

Nancy G. Leveson. Safeware: System Safety and Computers. Addison-Wesley, 1995.
Neil Storey. Safety-Critical Computer Systems. Addison-Wesley, 1996.

Templates

You may want to use the following templates (tailored for your purposes) as support for your practical work.

James Robertson and Suzanne Robertson. VOLERE: Requirements Specification Template. Edition 9, Atlantic Systems Guild. The Volere template is quite comprehensive and provides a useful guide to constructing a requirements document. [Pdf Version] [Word Version]
Alistair Cockburn. Structuring Use Cases with Goals. The paper introduces a Basic Use Case Template.
CRC Cards
- Kent Beck and Ward Cunningham. A Laboratory for Teaching Object-Oriented Thinking. In Proceedings of OOPSLA '89.
- Ward Cunningham. How Do Teams Shape Objects? How Do Objects Shape Teams?. Position Paper at OOPSLA '94.
- Ward Cunningham. CRC-Card Experience Connects Developers and Customers to Essence of the Problem.
- A CRC Description of HotDraw.
- Alistair Cockburn. Using CRC Cards.
- Alistair Cockburn. Responsibility-based Modeling.

Papers and Presentations

The SWEBOK homepage provides access to the current version of the Guide to the Software Engineering Body of Knowledge (2004 Version).
NASA (1992). Recommended Approach to Software Development. Software Engineering Laboratory Series, Revision 3, June 1992, SEL-81-305.
Ariane 5 launcher explosion. Ian Sommerville's presentation giving an overview of the causes of the system software failure. The Ariane 5 rocket failed on its maiden flight due to software problems. The presentation discusses how these occurred.
Airbus 340 flight control system. Ian Sommerville's presentation prepared from the case study in Storey's book that give an overview of the A340 system. The presentation discusses the use of redundancy in the Airbus flight control system.
London Ambulance Despatching System. Ian Sommerville's presentation gives an overview of the London Ambulance Despatching System and discusses the failure of the system.
Medical Devices: The Therac-25. This appendix is taken from Nancy Leveson, Safeware: System Safety and Computers, Addison-Wesley, 1995. This paper analyses the causes of the Therac-25 accidents.
Gary Cernosek and Eric Naiburg. The Value of Modeling. Rational Software, Copyright IBM Corporation 2004. This paper provides a brief technical discussion of software modeling.
Nenad Medvidovic and Richard N. Taylor. A Classification and Comparison Framework for Software Architecture Description Languages.
David Harel. Statecharts: A visual formalism for complex systems. In Science of Computer Programming 8 (1087) 231-274.
Peter Amey. Correctness by Construction: Better Can Also be Cheaper. In CrossTalk, The Journal of Defense Software Engineering, March 2002, pp. 24-28.
Bertrand Meyer. Software Engineering in the Academy. In IEEE Computer, May 2001, pp. 28-35.
James A. Whittaker. What is Software Testing? And Why is it so Hard?. In IEEE Software, January/February 2000, pp. 70-79.
Hutchins et al., Experiments on the effectiveness of Dataflow- and Controlflow-Based Test Adequacy Criteria. ICST, May 1994.
Manny Lehman, Software's Future: Managing Evolution. In IEEE Software, January-February 1998, pp. 40-44.
Lutz and Mikulski, Operational anomalies as a cause of safety-critical requirements evolution. In the Journal of System and Software 65(2):155-161, 2003.
William N. Robinson and Hang G. Hoo, Finding Reusable UML Sequence Diagrams Automatically. In IEEE Software, September/October 2004, pp. 60-67.
Tiffany Winn and Paul Calder, Is This a Pattern?. In IEEE Software, January/February 2002, pp. 59-66.
J. Boegh, S. De Panfilis, B. Kitchenham and A. Pasquini, A Method for Software Quality Planning, Control, and Evaluation. In IEEE Software, March/April 1999, pp. 69-77.
A. Avizienis, J.-C. Laprie and B. Randell, Fundamental Concepts of Dependability. UCLA CSD Report no. 010028, LAAS Report no. 01-145, Newcastle University Report no. CS-TR-739.
Software Engineering Bullets?
- The 70s...
  - D.L. Parnas, A Course on Software Engineering Techniques, 1972.
  - M.V. Zelkowitz, Perspectives on Software Engineering, 1978.
  - B.W. Boehm, Software Engineering - As it is, 1979.
- The 80s...
  - B.W. Boehm, Seven Basic Principles of Software Engineering, 1983.
  - D.L. Parnas, Software Aspects of Strategic Defense Systems, 1985.
  - A.N. Habermann, Technological Advances in Software Engineering, 1986.
  - M.M. Tanik, In Search of Silver Bullet, 1988.
- The 90s...
  - M. Shaw, Prospects for an Engineering Discipline of Software, 1990.
  - M. Harris, There Are No Silver Bullets!, 1991.
  - D. Harel, Biting the Silver Bullet: Toward a Brighter Future for System Development, 1992.
  - D.L. Parnas, Software Aging, 1994.
  - R.L. Glass, The Software-Research Crisis, 1994.
  - J.B. Thompson, OO is NOT the Silver Bulet, 1996.
  - L.B.S. Raccoon, Fifty Years of Progress in Software Engineering, 1996.
  - S. Shapiro, Splitting the Difference: The Historical Necessity of Synthesis in Software Engineering, 1997.
  - D.L. Parnas, Software Engineering: An Unconsummated Marriage, 1997.
  - D.L. Parnas, Successful Software Engineering Research, 1998.
  - W. Buntine, Will domain-specific code synthesis become a silver bullet?, 1998.
  - J. Voas, Software Quality's Eight Greatest Myths, 1999.
- The New Millennium...
  - A. Bryant, "It's Engineering Jim... but not as we know it": Software Engineering - solution to the software crisis, or part of the problem?, 2000.
  - M.M. Moore, Software Reuse: Silver Bullet?, 2001.
  - J. Kasser, Configuration Management: The silver bullet for cost and schedule control, 2002.
  - D.M. Berry, The Inevitable Pain of Software Development: Why There Is No Silver Bullet, 2004.
  - M. Blaha, A Copper Bullet for Software Quality Improvement, 2004.

Webpages

Practical UML: A Hands-On Introduction for Developers. The Borland intro to UML is a quick intro to UML.
The Java Tutorial provides a quick reverence to Java with many working examples.
A Collection of Software Bugs by Thomas Huckle.
The Agile Modelling (AM) site is another very good resource on object-oriented modelling. It is packed with useful information. One particularly nice reference is the essay on UML diagrams that provides lots of useful dos and don'ts in using UML diagrams.
The Object Management Group provides links to all the latest (rather unreadable) UML standards plus links to OO development work.
The Atlantic Systems Guild website provides various resourses on software engineering, requirements engineering and project management. Among them is the VOLERE: Requirements Specification Template.
The Software Engenering Institute (SEI) at Carnegie Mellon University provides many different resources (e.g., technical reports) in Software Engineering. In particular, you may want to look at the Software Architecture Technology Initiative.
In order to find additional references on Software Engineering, you may want to use the following online searchers

Software

The primary tool we will be using is the freeware Argo/UML.
There are other UML tools in the world. You might want to look at the advice provided by Objects by Design and at the UML Resource Center at Rational. The UML Resource Center is a good resource for information on UML and on the Rational Rose design tool (used in previous years).

This page is maintained by Massimo Felici (mfelici@inf.ed.ac.uk)

Home : Teaching : Courses : Seoc : 2004_2005