UCLA Computer Science 130, Winter 2005.
Software Engineering

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

• News
• Syllabus
• Homework
• Grading

Instructor: Paul Eggert <eggert@cs.ucla.edu>, Boelter 4532J, office hours Mondays and Tuesdays from 14:00 to 15:00.

Teaching assistant, in Boelter 4428:

• Teresa Breyer <tbreyer@cs.ucla.edu>

Lectures are Tuesdays and Thursdays from 10:00 to 11:50 at 362 Royce. Discussions are Fridays from 10:00 to 11:50 at 5249 Boelter.

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

Prerequisite: Computer Science 32 (required), 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 IEEE/ACM Computing Curricula 2001 bodies of knowledge:

• SE1. Software design
• SE2. Using APIs
• SE3. Software tools and environments
• SE4. Software processes
• SE5. Software requirements and specifications
• SE6. Software validation
• SE7. Software evolution
• SE8. Software project management
• SE9. Component-based computing
• SE10. Formal methods
• SE11. Software reliability
• SE12. Specialized systems development

Related IEEE/ACM Software Engineering 2004 (SE2004) bodies of knowledge:

• CMP.ct. Construction technologies
• CMP.tl. Construction tools
• FND.ec. Engineering economics for software
• PRF. Professional practice
• MAA. Software modeling & analysis
• DES. Software design
• VAV. Software verification and validation
• EVL. Software evolution
• PRO. Software process
• QUA. Software quality
• MGT. Software management