UCLA Computer Science 130, Winter 2010.
Software Engineering

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

• News
• Syllabus
• Homework
• Resources for oral presentations and written reports
• Grading

Instructor: Paul Eggert, Boelter 4532J. Office hours are Mondays 12:00–13:00 and Thursdays 11:00–12:00.

Teaching assistant: Indranil Saha <indranil@cs.ucla.edu>, Boelter 4428. Office hours are Tuesdays 16:00–17:00 and Thursdays 13:00–14:00.

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 Computer Science Curriculum 2008 (CS2008) bodies of knowledge:

• SE/SoftwareDesign
• SE/UsingAPIs
• SE/ToolsAndEnvironments
• SE/SoftwareProcesses
• SE/RequirementsSpecifications
• SE/SoftwareVerificationValidation
• SE/SoftwareEvolution
• SE/SoftwareProjectManagement
• SE/ComponentBasedComputing
• SE/FormalMethods
• SE/SoftwareReliability
• SE/SpecializedSystems
• SE/RiskAssessment
• SE/RobustAndSecurity-EnhancedProgramming

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