ECE 422C – Software Design and Implementation II - Fall 2025

Instructor: Prof. Edison Thomaz (ethomaz at utexas dot edu, or contact through Canvas)
Office Hours: Wednesdays 1-2PM @ EER 7.818

TAs: We will have 3 teaching assistants this semester:

TA Office Hours
Prithvi Senthilkumar (prithviksenthil at utexas dot edu) Mon 3-4pm (Location TBD)
Samuel Olatunbosun (samuel_04 at utexas dot edu) Thu 11-12:30pm (Location TBD)
David Fasasi (dif285 at utexas dot edu) Mon 12-1pm (Location TBD)

Class Meets: Three lecture hours on TTH from 12:30pm – 2:00pm. We will meet at ART 1.110. In addition to the lectures, students are registered for a 1.5 hour recitation as listed in the course catalogue and determined by a unique section number, shown below. Recitations will take place at EER 0.818.

Unique Recitation Day
18535 Fri 9-10:30am (EER 0.818)
18540 Fri 10:30am-12pm (EER 0.818)
18545 Fri 12pm-1:30pm (EER 0.818)
18550 Fri 1:30-3pm (EER 0.818)

Online Forum: We will be using Ed Discussion. You can find a link to it on Canvas. Select the course and look for "Ed Discussion" on the sidebar.

Description: Methods for engineering software with a focus on abstraction; specification, design, and implementation of object-oriented code; design and implementation of object-oriented programs in Java; abstract data types; inheritance; polymorphism; parameterized types and generic programming; the operation and application of commonly used data structures; miscellaneous high-level programming topics.

Pre-requisites: Computer Science 312 or Electrical Engineering 312 with a grade of at least C-. Incoming students are expected to know the basics of computers and computation; and how to program in C/C++ using features of the language, such as: variables and operators, built-in data types, execution control structures, pointers, arrays, screen I/O, structs , linked lists, and recursion. The student should know how to use basic programming tools and techniques, such as: a programming language development toolset and symbolic debugger.

zyBook Interactive Book: We will adopt an interactive book for the course. Students will have to purchase a license of the book so they have access to programming activities that will be needed for problem sets and also for recitations. To access the zyBook, click any zyBook assignment link in Canvas (do not go to the zyBooks website and create a new account), and subscribe.

Tentative Schedule

Day Lecture Topic Recitation Topic Assignment
Aug 26th (T) Course Overview
Aug 28th (Th) Java Basics I Meet TA, Logistics, IDE, Github
Sep 2nd (T) Java Basics II #1 Out
Sept 4th (Th) Java Basics III Assignm. #1, Java Basics
Sep 9th (T) OOP Encapsulation #1 Due
Sep 11th (Th) OOP Inheritance OOP, Exam #2 Out
Sep 16th (T) OOP Polymorphism
Sep 18th (Th) Exam I Assignm. #2, OOP
Sep 23rd (T) Abstract + Interfaces #2 Due
Sep 25th (Th) Interfaces + Types OOP, Interfaces #3 Out
Sept 30th (T) Generics
Oct 2nd (Th) Collections I Assignm. #3, Collections
Oct 7th (T) Collection II #3 Due
Oct 9th (Th) Exceptions Exceptions, Exam #4 Out
Oct 14th (T) (Exam II)
Oct 16th (Th) (Design Patterns) Assignm. #4
Oct 21st (T) Graphs I #4 Due
Oct 23rd (Th) (Graphs II) Graphs #5 Out
Oct 28th (T) (Networking)
Oct 30th (Th) Threads I Assignm. #5, Networking
Nov 4th (T) Threads II #5 Due
Nov 6th (Th) Machine Learning Threads, Exam #6 Out
Nov 11th (T) Exam III
Nov 13th (Th) Android I Assignm. #6
Nov 18th (T) Android II
Nov 20th (Th) Android III Android #6 Due
Nov 25th (T) Thanksgiving
Nov 27th (Th) Thanksgiving
Dec 2nd (T) Advanced Topics
Dec 4th (Th) Review Final
Dec 13th Final Exam (3:30pm)

Class attendance: Attendance is expected and you are responsible for keeping up with what happens in class. If you miss a class (other than for illness or an emergency), it is not reasonable for you to expect the instructor to repeat just for you the material that was covered in the class that you missed. This applies both to the content of the class as well as to announcements about class policies, events, deadlines, etc.

Equipment and Software: You can use your own computer for assignments or login and use the ECE Linux Application Servers.

Assignments: The assigned class work in this course will consist of programming assignments. Programming is a discipline that you learn by doing, not by listening to a lecturer. Therefore, doing the programming assignments is crucial to performing well in this class. If you are having considerable difficulty with the early assignments, this is a sign that you may be in over your head - you should come see the instructor or TAs immediately. The assignments will require a substantial time commitment. Be sure to budget sufficient time to complete assignments before the deadline.

At the time you submit each assignment for grading, you are highly encouraged to commit your final version to Git. This will be crucial in cases where your program gets lost, your computer gets corrupted, or if there is some dispute over what was turned in when. It is also recommended that you commit your latest incremental version at the end of each working day on the assignment. If you cannot finish an assignment on time, then submit whatever you have finished before the deadline to receive some partial credit.

Programming assignments will be submitted through Canvas and Gradescope. Unless the assignment provides specific steps for submission, please follow these rules:

Assignment grading criteria may vary on each assignment. However, in general, programs that do not compile correctly will receive no more than 25% of the possible points. Larger point deductions are given for such things as: incorrect output/results, missing features, bad design logic, poor style, etc. In addition, the following criteria are important: (i) a block structured design should be evident; (ii) comments and/or appropriate variable names should be used to make your program readable; (iii) appropriate prompts and messages for input and output should be given to the user of your program.

Unless stated otherwise, more emphasis will be placed on program clarity than on program length, speed or size. Appeals for assignment re-grades will not be honored unless you have evidence of a grading mistake (see grade disputes below for deadlines).

Late Assignments: Late deliverables will be accepted for up to 3 days after their due date, but at a penalty of 40 points -- so failure to turn in an assignment at the due date results in an immediate 40 point penalty. After 3 days past the original deadline, assignments will no longer receive any credit. In the interest of fairness, there will not be any exceptions to this policy.

Problem Sets: In addition to the programming assignments, students will also be required to complete problem sets. These problems will come straight from the Java zyBook and complement and/or extend what we cover in lectures.

Exams: There will be 4 exams in this course: 3 mid-term exams and a cumulative final. The exams will cover material from lecture, assignments, and any assigned readings. If your work or a personal situation forces you to unexpectedly miss exams, you should expect to get a zero on those occasions. If you miss an exam because of illness, you are expected to provide a statement from a doctor with a diagnosis of a medical condition that prevented you from taking the test. A slip showing you visited the UT Health Center or your personal doctor is not sufficient for this. In any other situation, you should contact the instructor beforehand. Additionally, bring your student ID to the exam; it may be requested for proof of identity. Exams turned in for re- grading will be completely re-graded to find all grading mistakes.

Grading: For consistency, assignments and exams will be graded according to a defined rubric applied uniformly to all students. I am interested in the critical thinking process you use when solving a problem. Please provide rationale and justification. For assignments and exams, I use the following rubric:

Here is a breakdown of how the final grade for each student will be computed:

Grade Distribution:

Grade Disputes and Corrections: If you are dissatisfied with a grade you receive, you must submit your complaint briefly in writing or by email, along with supporting evidence or arguments, to your TA within one week of the date that I (or the TA) first attempted to return the exam or assignment results to you. For programming assignments the dispute period starts with the posting of your score on the class Canvas gradebook page. Complaints about grades received after the one-week deadline will be considered only if there are extraordinary circumstances for missing the deadline (e.g. student hospitalization). No new disputes will be accepted after 11:59AM three days before the course grade sheets must be turned in.

The grade you are given, either on an individual exam or assignment or as your final grade, is not the starting point of a negotiation. It is your grade unless a concrete grading error has been made. Do not come to see the instructor or the TA to ask for a better grade because you want one or you "feel you deserve it". Come only if you can document a specific error in grading or in recording your scores. Errors can certainly be made in grading, especially when large classes of many students are involved. But keep in mind that the errors can be made either in your favor or not. So it's possible that if you ask to have a piece of work re-graded your grade will go down rather than up.

Remember that the most important characteristic of any grading scheme is that it be fair to everyone in the class. Keep this in mind if you're thinking of asking, for example, for more partial credit points on a problem. The important thing is not the exact number of points that were taken off for each kind of mistake. The important thing is that the number was the same for everyone. So it may not be changed once the grading is done and the exams or assignments have been returned. If you have questions or concerns about any of your grades, contact your TA first, and if not satisfied with that interaction then contact the instructor during office hours or via email.

Absence Due to Illness: If you miss deadlines or presentations due to illness, please bring the instructor a doctor's note that indicates not only that you had a medical consultation but also reports the actual illness that was diagnosed. If such note is provided within 3 days past the deadline, the instructor will consider an extension. Otherwise, all other policies apply (e.g., late deliverables).

Sharing of Course Materials is Prohibited: No materials used in this class, including, but not limited to, lecture hand-outs, videos, assessments (quizzes, exams, papers, projects, homework assignments), in-class materials, review sheets, and additional problem sets, may be shared online or with anyone outside of the class unless you have my explicit, written permission. Unauthorized sharing of materials promotes cheating. It is a violation of the University’s Student Honor Code and an act of academic dishonesty. I am well aware of the sites used for sharing materials, and any materials found online that are associated with you, or any suspected unauthorized sharing of materials, will be reported to Student Conduct and Academic Integrity in the Office of the Dean of Students. These reports can result in sanctions, including failure in the course.

FERPA and Class Recordings: Class recordings are reserved only for students in this class for educational purposes and are protected under FERPA. The recordings should not be shared outside the class in any form. Violation of this restriction by a student could lead to Student Misconduct proceedings.

Standard UT Austin Course Information and Policies

Academic Honor Code: You are encouraged to discuss assignments with classmates, but anything submitted must reflect your own, original work. If in doubt, ask the instructor. Plagiarism represents a serious violation of UT's Honor Code and standards of conduct.

Students who violate University rules on academic dishonesty are subject to severe disciplinary penalties, such as automatically failing the course and potentially being dismissed from the University. Please do not take the risk. We are REQUIRED to automatically report any suspected case to central administration for investigation and disciplinary hearings. Honor code violations ultimately harm yourself as well as other students, and the integrity of the University. Academic honesty is strictly enforced.

Notice about students with disabilities: The University of Texas at Austin provides appropriate accommodations for qualified students with disabilities. If you qualify, we will work with you to make appropriate arrangements.

Emergency Preparedness: Any students requiring assistance in evacuation must inform the instructor in writing of their needs during the first week of classes.

Coping with stress and personal hardships: The Counseling and Mental Health Center offers a variety of services for students, including both individual counselling and groups and classes, to provide support and assistance for anyone coping with difficult issues in their personal lives. As mentioned above, life brings unexpected surprises to all of us. If you are facing any personal difficulties in coping with challenges facing you, definitely consider the various services offered and do not be shy to take advantage of them if they might help. These services exist to be used.

Notice about missed work due to religious holy days: A student who misses an examination, work assignment, or other project due to the observance of a religious holy day will be given an opportunity to complete the work missed within a reasonable time after the absence, provided that he or she has properly notified the instructor. It is the policy of the University of Texas at Austin that the student must notify the instructor at least fourteen days prior to the classes scheduled on dates he or she will be absent to observe a religious holy day. For religious holy days that fall within the first two weeks of the semester, the notice should be given on the first day of the semester. The student will not be penalized for these excused absences, but the instructor may appropriately respond if the student fails to complete satisfactorily the missed assignment or examination within a reasonable time after the excused absence.

Electronic mail Notification Policy: In this course e-mail, Canvas and Ed Discussion will be used as a means of communication with students. You will be responsible for checking your e-mail regularly for class work and announcements. If you are an employee of the University, your e-mail address in Canvas is your employee address.

The University has an official e-mail student notification policy. It is the student's responsibility to keep the University informed as to changes in his or her e-mail address. Students are expected to check e-mail on a frequent and regular basis in order to stay current with University-related communications, recognizing that certain communications may be time-critical.

Edison Thomaz © 2025