UCLA Computer Science 130, Spring 2016.
Software Engineering

Course objective: Turn the student into a practicing software engineer.

• Piazza
• CCLE
• Core class material news
• Syllabus
• Homework
• Resources for oral presentations and written reports
• Grading

Instructor: Paul Eggert, Boelter 4532J. Office hours are Mondays 10:00–11:00 and Tuesdays 14:00–15:00.

Teaching assistants:

• 1A. Brooke Wenig <brookewenig@cs.ucla.edu>. Office hours are Tuesdays 13:00–15:00 in Boelter 2432.
• 1B. Sucharitha Prabhakar <prabhakarsucharitha@gmail.com>. Office hours are Mondays 15:00–17:00 in Boelter 2432.
• 1C. Jae Lee <jlee734@cs.ucla.edu>. Office hours are Wednesdays 14:00–16:00 in Boelter 2432.

Lecture, 4 hours; discussion, 2 hours; outside study, 6 hours.

Prerequisites: Computer Science 111 (required), Engineering 183EW or 185EW (recommended), Computer Science 131 (suggested).

Structured programming, program specification, program proving, modularity, abstract data types, composite design, software tools, software control systems, program testing, team programming. Letter grading.

Related Computer Science Curricula 2013 knowledge areas:

• SDF/Development Methods
• SE/Software Processes
• SE/Software Project Management
• SE/Tools and Environments
• SE/Requirements Engineering
• SE/Software Design
• SE/Software Construction
• SE/Software Verification and Validation
• SE/Software Evolution
• SE/Software Reliability
• SE/Formal Methods

Related knowledge areas in the IEEE Software Engineering Body of Knowledge, Version 3.0 (SWEBOK V3.0), 2014:

1. Software Requirements
2. Software Design
3. Software Construction
4. Software Testing
5. Software Maintenance
6. Software Configuration Management
7. Software Engineering Management
8. Software Engineering Process
9. Software Engineering Models and Methods
10. Software Quality
11. Software Engineering Professional Practice
12. Software Engineering Economics