Short URL: http://bit.ly/ee461L
This course focuses on providing hands-on experience in designing and developing large-scale software systems.
Specifically, the course studies tools and techniques that enable large-scale software development. Specific topics include version control systems, the UNIX shell, design and modeling tools, build automation, testing tools, tools for debugging and finding bugs, object-oriented design and analysis, design patterns, and refactoring.
Pre-requisite: EE422C (or EE322C) or Computer Science 336 with a grade of at least C-; credit with a grade of at least C- or registration for EE 360C or Computer Science 357. (Students may take 360C concurrently with 461L.)
HW & Project
Overview, Collaborative Development
HW: version control
Due Th 1/24
Exercise: Subversion Version Control
Exercise: Saros Distributed Pair Programming
Due Tu 2/12
Exercise: UNIX quiz
Marketing and Design Documents
Exercise: Patterns: Observer and Factories
HW: patterns and refactoring Due Tu 3/19
(Max 3 students per HW team)
HW: testing Due Th 4/4 (Max 3 students per HW team)
Exercise: Unit and system testing
Exercise: build management
Project: implementation progress
Exercise: Eclipse debugger
Hands on project demo
In class presentation via video/screenshots. Key findings. Future work.
Much of this class is based on material created by Dr Miryung Kim in our department. Here’s a link to her class. Here’s her version of the lectures: Collaborative Software Development, UML Diagrams, Unix, Information Hiding, Design Patterns, Refactoring, Testing, Build Management & Documentation, Debugging
Exercises and HW will be graded on a 0-3 scale, where 0 = not done, 1 = means attempted superficially, 2 = completed, but missing some deliverables, 3 = completed and meets all deliverables. (This is not a linear scale.)
Late submissions will not be accepted barring verifiable medical/personal emergencies.
We’ll use Piazza for discussions: piazza.com/utexas/spring2013/ee461l/home
Homeworks will be due in class, at the start of lecture. They will be collected by the appropriate TA, and returned in class the following week. Late submissions will not be accepted. Put your name, your EID, and instructor on each page.
You may work on HW in groups - turn in a single solution for the group, and list all the students in the group. Each student will get equal credit.
Google calendar showing sections and office hours in ENS 307
Mehmet E Yesin
This document defines policies around add-drop, cheating, students with disabilities, emergency procedures, etc.