UCLA Computer Science 130, Spring 2012.
Software Engineering

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

Instructor: Paul Eggert, Boelter 4532J. Office hours are Mondays 13:00–14:00 and Wednesdays 09:50–10:50.

Teaching assistant: Jerrid Matthews <matth122@ucla.edu>. Office hours are TBD in Boelter 2432.

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

Prerequisite: Computer Science 32 and 35L (required), Engineering 183EW or 185EW (recommended), Computer Science 111 or 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

UCLA Computer Science 130, Spring 2012. Software Engineering

UCLA Computer Science 130, Spring 2012.
Software Engineering