SEOC Resources

The course uses UML as the basis for the design of systems implemented in Java. The adopted course textbook is UML, Second Edition, by Simon Bennet, John Skelton and Ken Lunn, Schaum's Outline Series, McGraw-Hill, 2005.

This page lists the main references for each lecture. Note that the references fall in three main categories: Textbook Readings (i.e., chapters of the UML textbook), Readings (i.e., assigned references for readings), Suggested Readings (i.e., general references that could be of interest for further readings). Each lecture identifes the relevant readings.

**SEOC Readings**
# Lecture	Date - Week	Lecture - Description	Readings
1	21/09 Week 1	Lecture Note 01 SEOC Introduction	Readings UML course textbook Chapter 1 on the Introduction to the Case Studies. Chapter 2 on the Background to UML. B. Meyer. Software Engineering in the Academy. IEEE Computer, pp. 28-35, May 2001. R.N. Charette. Why Software Fails. IEEE Spectrum, pp.42-49, September 2005. B. Nuseibeh. Ariane5: Who Dunnit? IEEE Software, pp. 15-16, May/June 1997. J.-M. J�z�quel, B. Meyer. Design by Contract: The Lessons of Ariane. IEEE Computer, pp. 129-130, January 1997. M. Grottke, K.S. Trivedi. Fighting Bugs: Remove, Retry, Replicate, and Rejuvenate. IEEE Computer, pp. 107-109, February 2007. Rational Unified Process: Best Practice for Software Development Teams. Rational Software White Paper, TP026, Rev 11/01. Suggested Readings I. Sommerville. Software Engineering, Eighth Edition, Addison-Wesley 2007. Chapter 1 for a general account of Software Engineering Chapter 3 on Critical Systems Chapter 4 on Software Processes The SWEBOK homepage provides access to the current version of the Guide to the Software Engineering Body of Knowledge (2004 Version). A. Avizienis, J.-C. Laprie, B. Randell and C. Landwehr. Basic Concepts and taxonomy of Dependable and Secure Computing. IEEE Transactions on Dependable and Secure Computing 1(1):11-33, 2004. N.G. Leveson, C.S. Turner. An investigation of the Therac-25 accidents. IEEE Computer 26(7): 18-41, Jul 1993. Dolores R. Wallace and D. Richard Kuhn. Lessons from 342 Medical Device Failures. In Proceedings of HASE 1999, pp. 123-131. G. Cernosek, E. Naiburg. The Value of Modeling. Rational Software, Copyright IBM Corporation 2004. This paper provides a brief technical discussion on software modeling.
2	25/09 Week 2	Lecture Note 02 Requirements Engineering	Readings J. Robertson, S. Robertson. VOLERE: Requirements Specification Template. Edition 10.1, Atlantic Systems Guild. [Pdf Version] [Word Version] The Volere template is quite comprehensive and provides a useful guide to constructing a requirements document. The VOLERE template (tailored for your needs) is a practical tool, which supports your group project. I. Sommerville. Integrated Requirements Engineering: A Tutorial. IEEE Software, January/February 2005, pp. 16-23. 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. Suggested Readings G. Kotonya, I. Sommerville. Requirements Engineering: Processes and Techniques. John Wiley, 1998. The book has an associated set of OHP Transparencies (Powerpoint), 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. I. Sommerville, P. 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 systems. 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. Among the Requirements Engineering guideliens, Guideline 3.1 - Define a standard document structure - describes the benefits of a standardize requirements document. Suzanne Robertson and James Robertson. Mastering the Requirements Process. Addison-Wesley, 1999. M. Jarke. Requirements Tracing. Communications of the ACM, Vol. 41, No. 12, December 1998. I. Sommerville. Software Engineering, Eighth Edition, Addison-Wesley 2007. Chapter 6 on Software Requirements Chapter 7 on Requirements Engineering Processes
3	28/09 Week 2	Lecture Note 03 Use Cases	Readings UML course textbook Chapter 3 on Use Cases Basic Use Case Template. The use case template (tailored for your purposes) is a valuable tool that supports your practical work. Alistair Cockburn. Structuring Use Cases with Goals. The paper introduces a Basic Use Case Template. Suggested Readings Alistair Cockburn maintains the UseCases.org web site in which you will find useful resources for writing use cases.
4	02/10 Week 3	Lecture Note 04 Software Design and Class Diagrams	Readings UML course textbook Chapter 4 on Class Diagram: Classes and Associations Chapter 5 on Class Diagram: Aggregation, Composition and Generalization Chapter 6 on Class Diagram: More on Associations Chapter 7 on Class Diagram: Other Notations P. Kruchten, H. Obbink, J. Stafford. The Past, Present and Future of Software Architecture. IEEE Software, March/April 2006. Suggested Readings I. Sommerville. Software Engineering, Eighth Edition, Addison-Wesley 2007. Chapter 14 on Object-oriented design B. Meyer. Applying "design by contract". IEEE Compute, 25(10):40-51, 1992.
5	05/10 Week 3	Lecture Note 05 Validation: CRC Cards	Readings K. Beck, W. Cunningham. A Laboratory for Teaching Object-Oriented Thinking. In Proceedings of OOPSLA '89. Suggested Readings Alistair Cockburn. Responsibility-based Modeling. Alistair Cockburn. Using CRC Cards.
6	09/10 Week 4	Invited Industry Presentation
7	12/10 Week 4	Lecture Note 06 Sample Designs
8	16/10 Week 5	Lecture Note 07 Software Tools for UML	Readings UML course textbook Chapter 16 on Software Tools for UML.
9	19/10 Week 5	Lecture Note 08 Component Diagrams	Readings UML course textbook Chapter 7 on Class Diagram: Other Notations. Chapter 8 on Component Diagrams.
	23/10 Week 6	No Lecture
10	26/10 Week 6	Lecture Note 09 Sequence Diagrams	Readings UML course textbook Chapter 9 on Interaction Sequence Diagrams.
11	30/10 Week 7	Lecture Note 10 Communication Diagrams	Readings UML course textbook Chapter 10 on More on Interaction Diagrams.
12	02/11 Week 7	Lecture Note 11 Activity Diagrams	Readings UML course textbook Chapter 11 on Activities.
13	06/11 Week 8	Lecture Note 12 State Machines	Readings UML course textbook Chapter 12 on State Machines. Suggested Readings D. Harel. Statecharts: A visual formalism for complex systems. In Science of Computer Programming 8 (1987) 231-274.
	09/11 Week 8	No Lecture
14	13/11 Week 9	Lecture Note 13 Software Testing	Readings James A. Whittaker. What is Software Testing? And Why is it so Hard?. In IEEE Software, January/February 2000, pp. 70-79. Suggested Readings P.C. Jorgensen, C. Erickson. Object-Oriented Integration Testing. In Communications of the ACM, September 1994, Vol. 37, No. 9.
15	16/11 Week 9	Invited Industry Presentation
16	20/11 Week 10	Lecture Note 14 Deployment Diagrams	Readings UML course textbook Chapter 14 on Deployment Diagrams.
17	23/11 Week 10	Lecture Note 15 Design Patterns	Readings UML course textbook Chapter 17 on Design Patterns. T. Winn, P. Calder, Is This a Pattern?. In IEEE Software, January/February 2002, pp. 59-66.
18	27/11 Week 11	Lecture Note 16 SEOC - Open Issues and Course Summary
	30/11 Week 11	No Lecture

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

Home : Teaching : Courses : Seoc : 2007_2008