|
IST 311 (3 credits)Object-Oriented Design and Software ApplicationsFall 2007 |
"There's more to object-orientation than just programming."-Scott Ambler: The Object Primer "Achieving good communication, along with good understanding of the users' world, is the key to developing good software"-Martin Fowler: UML Distilled |
Required Text:
|
Morelli: Java, Java, Java: Object-Oriented Problem Solving, 3rd Edition Companion Web Site |
Other Materials: |
A few CDs |
Instructor: |
Suzanne E. Gladfelter, A.S., B.S., M.Ed., M.S.
sgladfelter@psu.edu |
Office Hours: |
Tuesdays & Thursdays 1:30pm- 2:45pm Other hours by appointment Schedule an appointment via email or voice mail |
|
|
|
Office Location: |
230 ISTC |
Office Phone: |
771-4119 |
In IST 311 students will:
In all IST courses at Penn State York we strive to help students:
This course requires extensive use of:
|
Object-Oriented (Team) Software Project |
25% |
|
Tests (2) |
40% |
|
Homework/Lab Assignments |
30% |
|
In class exercises, attendance, class participation, professional attitude and demeanor |
5% |
Letter grades will be assigned according to the scale listed below:
|
94 - 100 |
A |
|
90 - 93 |
A- |
|
87 - 89 |
B+ |
|
84 - 86 |
B |
|
80 - 83 |
B- |
|
77 - 79 |
C+ |
|
70 - 76 |
C |
|
60 - 69 |
D |
|
below 60 |
F |
|
Test questions will be taken from textbook reading assignments, class lectures/notes/activities, lab assignments and homework assignments. Test questions will consist primarily of short answer/completion questions and program segments to code and/or trace. There will be some multiple choice or true/false questions on each test. All tests will contain a closed book and open book/open notes portion. The closed book portion of each test will focus on mastery of the course vocabulary. |
|
Students who do not earn at least a 60% average on the tests should expect to fail the course. Test #1 - October 11 |
************ NOTE ************If you are unable to attend class the day of a test due to illness or circumstances beyond your control, it is your responsibility to notify the instructor in person, by phone or in writing prior to the beginning of class on the day the test is to be taken. Otherwise, arranging to take a make-up exam will not be possible. |
|
All students will be required to work on a team object-oriented software project. The semester project will include a design component using UML diagrams and software development using Java. S. Gladfelter will distribute the project specifications during the second week of class. The final grade for the project will be based on the quality of the final presentation, final project deliverables, a working project, S. Gladfelter's individual observations of teamwork, and other related activities. Students will be required to evaluate themselves and fellow team members. Each person will earn an individual grade for the group project; individual grades will be based on the successful completion of stated project criteria in combination with the student evaluation feedback, instructor observations of individual contributions to the team project and other related items. This project constitutes a significant portion of your learning experience and 25% of your grade for the course. Students who do not fully participate in the project should expect to fail the course. |
|
Homework and lab assignments comprise 30% of your grade in this course. Students may collaborate/pair program with a classmate or work individually on assignments. Students who choose to collaborate are expected to contribute their fair share to the homework/lab team both during and (if needed) in addition to class time. |
|
Assignments must be submitted in a folder (supplied by S. Gladfelter) and must clearly display your name(s), assignment due date, and your email address(es) on the cover sheet and as part of the beginning comments in any source code submitted. Your lab assignment disc must be labeled with your name(s) and email address(es). You are expected to follow good programming style as discussed and exemplified in your texts and examples provided in class. Students will not receive full credit for homework/lab assignments that are submitted after the due date. |
|
All students are expected to act with civility and personal integrity; respect other students' dignity, rights and property; and help create and maintain an environment in which all students can succeed through the fruits of their own efforts. An environment of academic integrity is requisite to respect for self and others and to maintaining a civil community. Academic integrity includes a commitment to not engage in or tolerate acts of falsification, misrepresentation or deception. Such acts of dishonesty include cheating or copying, plagiarizing, submitting another person's work as one's own, using Internet sources without citation, fabricating field data or citations, "ghosting" (taking or having another student take an exam), stealing examinations, tampering with the academic work of another student, facilitating other students' acts of academic dishonesty, etc. Academic dishonesty violates the fundamental ethical principles of the University community and compromises the worth of work completed by others. A student should avoid academic dishonesty when preparing work for any class. If charged with academic dishonesty, students will receive written or oral notice of the charge by the instructor. Students who contest the charge should first seek resolution through discussion with the faculty member or the campus Director of Academic Affairs. If the matter is not resolved, the student may request a hearing with the Commonwealth College Committee on Academic Integrity at the campus.
Sanctions for breaches of academic integrity may range (depending on the severity of the offense) from receiving an "F" for the assignment to receiving an "F" for the course. In severe cases of academic dishonesty, including, but not limited to, stealing exams or "ghosting" an exam, students may receive a grade of "XF", a formal University disciplinary sanction that indicates on the student's transcript that failure in the course was due to a serious act of academic dishonesty. The University's statement on Academic Integrity from which the above statement was drawn is available at: |
|
Students are expected to abide by the Penn State Policy AD20 Computer and Network Security. Violations of this policy can result in termination of privileges, academic probation, expulsion from Penn State or criminal prosecution. |
|
It is our policy at Penn State York not to discriminate against qualified students with documented disabilities. If you have a disability related need for modifications in this course, please contact S. Gladfelter during the first week of class. You also may choose to contact the Learning Center for assistance with testing accommodations that extend beyond the scope of the instructor. |
| Week | Topics | Corresponding Text Material |
|
1 (8/28 & 8/30) |
Review from IST 240 Lab/Homework #1 (True/False Console Application) Lab/Homework #2 (Java Applets vs. Java Applications) |
Morelli: Chapters 0 - 3 |
|
2 (9/4 & 9/6) |
Begin Course Project
Java Data and Operators (on your own) Control Structures (on your own) Lab/Homework #1 due (9/4) |
Supplemental Material provided by S. Gladfelter Fowler, UML Distilled, Chapter 2 (Safari ) Morelli: Chapters 5 & 6 |
|
3 (9/11 & 9/13) |
Catch Up Input/Output: Designing the User Interface
|
Morelli: Chapter 4 |
|
4 (9/18 & 9/20) |
Input/Output: Designing the User Interface
|
Morelli: Chapter 4 |
|
5 (9/25 & 9/27) |
Input/Output: Designing The User Interface
|
Morelli: Chapter 4 |
|
6 (10/2 & 10/4) |
Input/Output: Designing The User Interface
|
Morelli: Chapter 4 |
|
7 (10/9 & 10/11) |
Input/Output: Designing The User Interface Arrays (on your own) File Input
|
Morelli: Chapter 4 Morelli: Chapter 9 Morelli: Chapter 11 - Sections 11.1 to 11.3 (pages 511 - 529) |
|
8 (10/16 & 10/18) |
Arrays (on your own) Graphical User Interfaces (GUIs) Applets
|
Morelli: Chapter 9 Morelli: Chapter 13 Supplemental Material for Use Cases (ANGEL Lessons/October 16) |
|
9 (10/23 & 10/25) |
Arrays (on your own) Graphical User Interfaces (GUIs) Applets Activity Flow Diagrams
|
Morelli: Chapter 9 Morelli: Chapter 13 Fowler: Chapter 11 |
|
10 (10/30 & 11/1) |
Exceptions
|
Morelli: Chapter 10 |
|
11 (11/6 & 11/8) |
Exceptions
|
Morelli: Chapter 10 |
|
12 (11/13 & 11/15) |
Radio Buttons & Checkboxes
|
Morelli: Chapter 13 |
|
13 (11/27 & 11/29) |
Strings and String Processing File Input
|
Morelli: Chapter 7 |
|
14 (12/4 & 12/6) |
Strings and String Processing File Input
|
Morelli: Chapter 7 |
|
15 (12/11 & 12/13) |
Course Wrap Up Activities
|
Morelli: Chapter 8 |
Last updated: November 23, 2007