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: Monday 1 - 3 (subject to change)
Email: tharvey at udel.edu
Phone: don't phone, email!

TA:

Bryan Youse email: bryouse at udel.edu
Office: 103 Smith Hall
Office hours: Thurs 12-2 (subject to change)

Email for appt

Bryan's Website

 

Useful Links

Text: Program Development in Java, Barbara Liskov (with John Guttag)
ISBN-10: 0201657686
ISBN-13: 978-0201657685


All students are required to have an i>clicker.

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 dates, subject to change:

3/13 Midterm 1
4/24 Midterm 2
UML use cases, class and sequence diagrams
First code review: classes, stubs, compiles
Second code review: demo simple use case w/GUI, JUnit tests
Third code review: demo multiple use cases w/GUI, JUnit tests
Alpha testing
Project final code review, all JUnit tests, all functionality
Inter-team testing
Rehearsal Presentations
5/13-15 Presentations at ??
5/17-23 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

  1. GUI programming
  2. UML diagrams
  3. Object-oriented style
  4. Modular design
  5. Method-level specification
  6. Automated testing
  7. simple Design Patterns
  8. simple version control
  9. using an IDE
  10. Working in teams
  11. Working with non-technical team members
  12. Making presentations
  13. 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 sometimes be due during lab, and sometimes due later. Many labs will not have a component that gets turned in, but attendance is required regardless.
One quarter of the semester lab grade will be a lab attendance grade. This grade is marked by your TA based on each lab. Marks on Sakai will be either 1:present, 2: excused (by the professor and in advance), 3:late, and 4:absent. Students who depart early will also be marked 3 for "left early" for missing part of lab. More than 15 minutes late constitutes absence.


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, in pairs, 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 (if any - ask your TA).

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. Part of this grade will be based on your clicker participation.

Your project grade will be scaled by a factor determined by team peer evaluations. The professor reserves the right to make adjustments to this factor if he deems it necessary, but be aware that no previous student has benefitted from such adjustment.

Finally, about 20 percent of your project 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

5% Labs

5% Quizzes

15% 2 Midterms (5,10)

50% Project (includes all phases)

15% Cumulative Final

10% Participation

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.

Grade Scale

Number

100-93

93-90

90-87

87-83

83-80

80-77

77-73

73-70

70-67

67-63

63-60

<60

Letter

A

A-

B+

B

B-

C+

C

C-

D+

D

D-

F

Project

This semester's project will involve working in a team composed of students from 275, and also students from the Art department. Teams will design and implement software for DelDOT. The project grade will be composed of a number of parts, including multiple presentations, all parts of the software engineering cycle, quality of teamwork and team evaluations, and final presentation. Projects which pass the final presentation may present their work to faculty, administration, and adoring fans. DelDOT may select software to use at the Delaware State Fair in July.

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.