Catalog Description
This course deals with the design and implementation of software subsystems. The concept of design patterns is introduced/and common patterns are applied to the development of software components. Laboratory projects provide an opportunity for teams of students to implement components and to integrate them into complete systems. As a final assignment, students conduct research on software design patterns and present and demonstrate the results of their investigations to the class. (prereq: SE 2030, CS 2852)
2 lab hours
4 credits
Basics
- Instructor
- Josiah Yoder
- lıɐɯə
- npǝ˙ǝosɯ@ɹəpoʎ
- Office
- L341 (Library, 3rd floor)
- Office Hours
- See below
- Phone
- ƖƐ96 ᔭᔭᔭ ϛ9ㄥ Google Voice; rings my office and cell phone at the same time.
- Textbook
- Head First Design Patterns, by Freeman and Freeman, et al., O'Reilly, 2004, ISBN-10: 0-596-00712-4
Outcomes
On successful completion of this course, the student will be able to:
- Apply object-oriented design patterns in software application-specific contexts
- Determine the appropriate design pattern to apply in a specific context
- Design and implement small software components and systems
- Apply UML class and sequence diagrams in the process of designing and documenting software applications
- Conduct independent research on software design patterns
(These are the Official Course Outcomes for this course)
My Schedule (Office Hours)
| Time | Mon | Tue | Wed | Thu | Fri |
|---|---|---|---|---|---|
| 8:00 | SE2811 S210 |
||||
| 9:00 | SE2811 S210 |
SE2811 S210 |
UR4982 | SE2811 S210 |
|
| 10:00 | SE1021 Supply S210 |
Lunch | |||
| 11:00 | SE1021 S359 |
Office Hour |
SE1021 S359 |
SE1021 S359 |
|
| 12:00 | Lunch | Lunch | Lunch | Office Hour |
Office Hour |
| 1:00 | Dept Mtg | SE2811 CC03 |
SE1021 planning |
||
| 2:00 | SE2811 S359 |
SE2811 S359 |
SE2811 S359 |
||
| 3:00 | Office Hour |
Office Hour |
|||
| 4:00 |
Class
While I don't mind if you have to skip a class, class attendence is essential so you can learn what material I expect you to know, what HW and quizzes there will be, etc.
In class, I expect you to focus completely on class material. Instead of checking your email or browsing facebook, participate in the class activities and take notes of what you are learning.
If it becomes necessary to consider dropping the class, I am happy to give you advice, but I want you to make the final decision (with the help of your academic advisor). So if you stop coming class, I will not drop you, but instead give you whatever grade you have at the end of the quarter, even if it is an F.
Labs
This quarter, we are learning the foundations of programming. To ensure that you master this material, Labs are individual, unless marked in the lab handout.
Labs may be turned in electronically or on paper. See the lab checklist for when the lab is due and how it should be submitted. In every uploaded file, include your name, date, and the assignment name. Please only submit a lab once. Multiple submissions are hard for me to keep track of, especially if I've already started to grade the first one.
Untested code is buggy. I find that if your code doesn't compile or hardly runs, that there are many other errors in it. To get more than half credit for a lab, it should compile and run when I test it (or you demo it). If it does not compile & run, please fix the lab and submit it later, or drop a feature or two to get it running again (often the best option).
For every day that goes by beyond the original deadline, it gets much harder to catch up on a lab. As a result, after the deadline, you can receive partial credit for a lab, up to 10% off per day.
All assignments must be turned in by 4:30pm on Friday of Week 10 so that we can wrap things up and I can turn the grades in on time.
Please start early and ask me for help if you get stuck.
Learning Assessment
This quarter, we will use the following to measure your learning:
| Lab projects | 30% |
| Quizzes | 20% |
| Half Exam 1 | 10% |
| Half Exam 2 | 10% |
| Final Exam | 30% |
| Total | 100% |
I sometimes make mistakes in tallying points. If you become aware of an error in grading, please send me an email, and I will fix it and reply by email.
If the error goes beyond tallying points, discussing things in person is a great way to start to resolve an issue. I may ask you to send me an email if I think the case you are asking about requires careful consideration.
Please maintain your own records of your grades and check them against whatever summaries I send to you.
Quizzes & Exams
Quizzes will be announced in class at least one day in advance. They will usually be on Lab day.
Because of the difficulty of preparing fair and accurate tests, you cannot retake a quiz or exam if you miss it or do worse than you hoped. I will drop your lowest quiz score, so one 0 should not be a problem. If you need to skip an exam, you should schedule a make-up exam before the missed exam. I don't always give make-up exams, even if students ask in advance.
You must have a passing grade on the exams to pass the class.
Grade Scale
I use the official MSOE grading scale:
| ≥93% | ≥89% | ≥85% | ≥81% | ≥77% | ≥74% | ≥70% | <70% |
| A | AB | B | BC | C | CD | D | F |
In final grading, I may award a grade higher than the grade scale if I feel it is more accurate than what the "raw numbers" produce.
Integrity
Your integrity is your most valuable academic possession, significantly more valuable than passing a class or getting a high GPA.
Academic integrity is essentially truthfulness -- ensuring that if it appears you have done or know something, you have.
It is possible to accidentally give the impression that work is yours. If something like this happens to you, please let me know as early as possible. It is better if you point it out than if I find it.
Be on the watch for violations of academic integrity, including:
- Receiving code from another student not on your team, even by looking at it.
- Giving code to another student not on your team, even by showing them.
- Looking at another student's work during a quiz or exam.
Read MSOE's Policy on Student Integrity for more details.
When coding, you are encouraged to discuss strategies, but the implementations should be independent. Even discussing the details is not a good idea if it goes too far. If you want to show code, start up an independent program rather than showing an assignment -- and use a different application than the assignment at hand to demonstrate the concept you wish to share.
Because of the importance of maintaining academic integrity, I will report apparent academic dishonesty to the Vice President of Academic Affairs. If this occurs, you will get a copy of the report.
Fine Print
1In rare cases, I may need to reschedule an office hour. I will, if at all possible, announce this in class a day or more in advance.