1. EE422C Software Design and Implementation II
Roger Priebe

2. EE422C in Context software engineering introductory systems
programming
in C/C++
systems
software
Software
Design and
Implementation II
(in Java)
embedded
systems
other ECE
areas
other non
ECE areas

3. Goals for this course
How to create appropriate abstractions (e.g., procedural and data) to solve complex programming problems
A practical understanding of a variety of common data structures
When and where they are applicable, and how to use them
Knowledge of the advanced constructs of a high level programming language (Java)

4. Goals for this course (cont.)
A good understanding of basic software engineering principles and practices
How to analyze a problem
How to design a system
How to write good code (conforming to style standards)
How to design and test for correctness
How to analyze program performance
Prepare you to use this knowledge in future courses that require you to develop software/hardware systems

5. Java programming What’s different from C (or C++)
We will be doing all programming assignments in the java programming language
There are a lot of available resources!
You will learn by doing, not by watching video or reading code (or copying code)

6. Websites Course web-page: accessible from my home page
Canvas: courses.utexas.edu
My Home Page: users.ece.utexas.edu/~rpriebe
Course web-page: accessible from my home page
Syllabus: web site
Lecture Slides: web site
Programming Assignments: web site
Discussion and Questions: Piazza
Grades: Canvas

7. The teaching team Instructor Roger Priebe (priebe (at) utexas.edu)
Office hours: (TTH 8:30-10:30)
Graduate TAs
Ravi
Xiaocheng (Shen)
Undergraduate TAs
Amr
Brendan
Shrikar
Turan
Office hours: See web page

8. Piazza Used to make some instructor announcements
Students may ask follow-on questions or make comments.
Important for students to read these instructor announcements in a timely manner.
Students may post notes, discussions, or ask questions.
Students may share allowed assignment-related material.
May use Piazza to find partner for group assignments.

9. Contacting the teaching staff
We will be using Piazza for most questions because it benefits the entire class.
the instructor or TA for questions that are personal: grades, missing class, etc.
Go to office hours.
ing through Canvas is not encouraged, unless it is a response to something the instructor has sent, or a comment that the instructor has made on Canvas.

10. Discussion Sections Will be conducted by the TA’s
Will be the primary place we discuss tools and programming environments
Will have graded quizzes (typically at the beginning of the session to get you there on time)
Come prepared with questions for TA’s about the assignments etc.
Discussion sections will start today.

11. Assignments and grading
We will have 6-7 programming assignments
Assignments will be completed independently unless we state otherwise
we might do some pair and/or team programming
Two in-class exams during the semester
may have pop quizzes any time
Quizzes in the discussion sections

12. Assignments and grading (cont.)
Exam grades may be curved if warranted
Assignments turned in late will NOT be accepted
Your program must compile and run successfully on the Linux lab configuration when graded
Assignments
each assignment may have different criteria
partial credit will be given
correctness, style, performance, etc. will be scored

13. Syllabus
The remaining details of the course policies, rules, grading criteria, and procedures are in the syllabus document on the course home page
You are responsible for knowing the contents of the syllabus.

14. Questions?