This document is subject to change. Check it for updates at least
weekly during the semester.
Instructor: Terry Harvey
Office: 408 Smith Hall
Office hours: Tues 2-4, Fri 8-10
Email:
tharvey at udel.edu
Phone: don't phone, email!
TA: Charlie Greenbacker
email: charlieg at cis.udel.edu
Office Hours: Wed 2-3, Thurs 1-2
Useful Links
Text: Program Development in Java, Barbara Liskov with Somebody Else
ISBN-10: 0201657686
ISBN-13: 978-0201657685
This class web page is where you find labs, projects, examples, hints, changes to the schedule, etc. Check here every week, or more frequently. Depending on which browser you use, you may need to hit "reload" or "refresh" to see new material.
Important Project 2 dates, subject to change:
| Nov 6 |
UML use cases,
class and sequence diagrams |
| Nov 12 |
First code review:
classes, stubs, compiles |
| Nov 19 |
Second code review: simple use case w/GUI |
| Dec 3-4 |
Project 2 final
code review |
| Dec 4,7,9 |
Presentations |
| ??? |
Final Exam |
|
|
Course Objectives
This course is designed to introduce students to a variety of tools and ways of thinking about software and software development. Topics to be introduced include
- GUI programming
- UML diagrams
- Object-oriented style
- Modular design
- Method-level specification
- Automated testing
- simple Design Patterns
- simple version control
- using an IDE
- Working in teams
- Making presentations
- Evaluation of code for
At the conclusion of this course students should be more comfortable with the design and implementation of software projects requiring multiple authors, and should be well-positioned to tackle advanced versions of these same topics in Software Engineering II, CISC475.
Lecture
We will cover a wide variety material in this
course, not all of which is in the textbook. Attending lecture is essential to
learn the material and to interact with class
members, teammates, and the professor.
Lab
Labs will come out each Thursday, and be due the following Wednesday at midnight on Sakai. Also, your TA will collect paper copies of the lab (for ink grading) the following morning at the start of your lab. Do not assume that the printer in Pearson will work.
Bring your printed lab with you to lab.
After you submit a lab, I will give detailed answers to questions about the lab. For this reason, it is important that you submit on time. Late assignments will receive a 25 percent penalty immediately, and an additional ten percent each 24 hours. No exceptions will be made for traffic, dead disks, fried monitors, political protests, etc. Please work on your assignments early and often.
Labs may be done alone or in groups, We will specify which for each lab. If you work in a team, 1) put all the names on the assignment; 2) every team member must submit electronically; 3) only submit one paper copy.
Participation
There will be many opportunities to participate in class. Participation includes asking questions, answering instructor questions, and being an active and constructive party when asked to work with other students in class. Speak up! It's ten percent of your grade. If you have remarkable difficulty speaking in class, see me during the first week of class to discuss alternative assignments.
Finally, ten percent of your grade will be based on your presentations of material in class. When you are part of a team, be sure that you present material every time the team does. Know the material well enough that you are not reading. We'll go over lots of other presentation points.
Grading
10% Labs
15% Midterm
32% Projects (14/18)
23% Cumulative Final
20% Participation and Presentation
At the end of the semester, all grades will be taken into account by the instructor in determining whether or not to apply a curve of some kind. Under no circumstance will grades be curved "down", but there is no guarantee that grades will be curved up.
Assignments
Typically, labs and projects will be graded by the TA, exams by the instructor. Once an assignment is returned, you have a week to request that your grade on the assignment be re-examined. Submit the assignment to the person who graded it along with a cover sheet explaining where you think you should be credited with additional points and why. If you submit for re-grading to the TA and are not satisfied with the result, you may re-submit to the instructor, but be forewarned that historically this option has not met with much success.
See the separate document on Assignment
Standards.
Academic Honesty
I expect my students to uphold the
highest standards of academic honesty,
as described in the University Code of
Conduct at http://www.udel.edu/stuguide/09-10/code.html
Any violations will be referred to
the Office of Academic Conduct.
NOTES:
Quizzes and exams are not team activities, and must be written solely by you without assistance of any kind.
Teams must work independently of other teams. Do not share work or code between teams; this is a violation of the Academic Honesty policy.
If you are ever in doubt about whether some activity is permitted, do not do it until you have asked the professor and received clarification.