UCLA Computer Science 130, Winter 2014.
Software Engineering
Course objective: Turn the student into a practicing
software engineer.
Instructor: Paul Eggert, Boelter 4532J.
Office hours are Mondays 10:00–11:00 and Thursdays 09:30–10:30.
Teaching assistants:
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
© 2005–2014 Paul Eggert.
See copying rules.
$Id: index.html,v 1.46 2014/01/06 07:02:37 eggert Exp eggert $