Syllabus for UCLA Computer Science 130, spring 2018.
Software Engineering

[130 home]

• Books:
  • Steve McConnell, Code Complete, 2nd Edition, Microsoft Press (2004), ISBN 0-7356-1967-0. Chapters 1 and 5 are also on the web.
  • Ian Sommerville, Software Engineering, 10th edition, Addison-Wesley (2015), ISBN 978-0-13-394303-0. Errata are available. Chapters 1, 12, and 19 are also on the web; chapters 26–31 are only on the web.
• Lectures (this is preliminary and may change):

  	chapters to read before class
  date	McConnell	Sommerville	Topics
  04-02			introduction
  04-04	1, 3–3.4	1, 4	requirements engineering
  04-06			requirements gathering (in discussion)
  04-09	(Read homework.)		initial project meeting
  04-11	2, 21	2–3	software process models
  04-13			initial project organization (in discussion)
  04-16		5, 19, 20	system modeling and engineering
  04-18	3.5	6, 17, 28	architectural design
  04-23	4, 5, 6	7, 16, 18	component-level design
  04-25	20	24, 25	quality and change management
  04-30	22, 29	8	testing
  05-02			midterm (in lecture)
  05-07	28	22	project management
  05-09	3.6, 27	23	project planning
  05-11			midterm presentations (in discussion)
  05-14		10–14	dependability and security
  05-16	23–26, 31	9	debugging, refactoring, and tuning
  05-21	30	27	tools and formal methods
  05-23	32	29, 30	user interface and documentation
  05-30	33–35	15, 26	reuse and process improvement
  06-04		21	real-time software engineering
  06-06	(Read Burns 2013.)		legal aspects
  06-08			final presentations (in discussion)

• 06-08 (the last day of instruction) is the drop-dead date for all assignments.
• The final exam is the time and place scheduled by the Registrar.
• Chapters of McConnell omitted from the course, but still good reading, are 7–19 (routines, names, data types and control).
• A chapter of Sommerville omitted from the course, but still good reading, is 31 (aspect-oriented software engineering).