User Interface Programming CS 395 Syllabus

Fall 2007

CS395 Section 1

Instructor: Michael Cassens

Office: SS 405

Office Hours: By Appt

University Phone: TBA

Cell: 370-1684

Office: 549-0616

e-mail: michael@silverleaf-consulting.com

Class Location: GBB 108

Overview:

This class is designed to give you a good general understanding of how to program user interfaces. This class is a programming class, however it is assumed that you have a good understanding of programming concepts. This class focuses on C# using the .NET Framework 2.0. Although this platform is used, it will not prevent you from leveraging other tools provided by other vendors. The concepts covered in this class are generic in nature and should translate to any language/platform of your choice.

Attendance:

This course meets two times a week – Tuesdays and Thursdays. You are required to attend all class sessions. If you must miss, it is your responsibility to get the assignments from classmates or from me. If you miss an exam, you will not be able to make it up. Occasionally, I need to travel out of town and on those days, we will have a guest lecture or we will have class via Blackboard. Class time concentrates not only on lectures, but on in-class lab time. This time will greatly benefit your overall knowledge and understanding and help you complete the assignments.

Grading:

Homework and Labs 50%

1 Exam 20%

Final Exam 30% Scheduled Date:Dec. 11 or Dec. 13

All Assignments will be sent to michael@silverleaf-consulting.com

Your subject must be CS 395 Assignment # (e.g CS 395 Assignment 1)

Grading Scale

100-90 A, A- 79-70 C+, C, C- 59-and beyond F

89-80 B+, B, B- 69-60 D+, D, D-

P/NP – pass/no pass, 70 or greater is passing determined by Computer Science Department policy, which is a C or better.

Late Assignments:

• Late assignments will not be accepted. Sorry for the inconvenience.

Requirements

• Required Texts:
• Pro .NET 2.0 Windows Forms and Custom Controls in C#

• You must have taken at least an introductory programming course and data structures.

Suggestions:

• It will be beneficial to read the text and ask as many questions as you can.
• Feel free to set up an appointment if you need help. I am here to help you understand and do well.

Collaboration:

• I encourage you all to work together through problems, but copying and plagiarism will not be tolerated. If you are caught cheating, I will give you an F for the course.

-         Please refer to the Student Conduct Code in how this will be dealt with: http://www.umt.edu/studentaffairs/sccAcademicConduct.htm

Incompletes:

“Incomplete for the course is not an option to be exercised at the discretion of students. In all cases it is given at the discretion of the instructor….” Some guidelines for receiving an incomplete are listed in the catalog which include having a passing grade up to three weeks before the end of the semester and being in attendance. “Negligence and indifference are not acceptable reasons.” Also note that there may be financial aid implications.

More information located here:

http://www.umt.edu/catalog/acpolpro.htm#28

Late Drops:

The University’s policy on drops after 30 days of instruction is outlined in the following link: http://www.umt.edu/catalog/acpolpro.htm#5. The Computer Science Department follows this policy rigorously. There are five circumstances under which a late drop might be approved: registration errors, accident or illness, family emergency, change in work schedule, no assessment of performance in class after this deadline. Except in very unusual circumstances, I will only approve late drops if there is documented justification for one of these circumstances.

Disabilities:

Students with disabilities should notify the instructor at the beginning of the course. Disabilities should be “certified” by DSS.

Class Etiquette:

• Be respectful of your fellow classmates.
• Call me anytime if you have a question.
• Profanity and Obscenity will not be tolerated in class or assignments.

Special Dates:

· Sept 3, 2007 Labor Day

· Nov. 12, 2007 Veterans day

· Nov 21-23 Thanksgiving

· Dec 10-14 Final Examinations

Tentative Schedule:

Week 1 User Interface Architecture Sept 4-6 (Chapter 1)

Week 2 Controls Basics Sept 11-13 (Chapter 2)

Week 3 Forms Sept 18-20 (Blackboard) (Chapter 3)

Week 4 Classic Controls Sept 25-27 (Chapter 4)

Week 5 Lists and Trees Oct 2-4 (Chapter 6)

Week 6 Tool, Menu, Status Strips Oct 9-11 (Chapter 14)

Week 7 Exam 1 Oct 16-18

Week 8 DataGridView Oct 23-25 (Chapter 15)

Week 9 Sound and Video Oct 30 – Nov 1 (Chapter 16)

Week 10 WebBrowser Control Nov 8 (Chapter 17)

Week 11 Validation and Masked Editing Nov 13-15 (Chapter 18)

Week 12 Thanksgiving Break

Week 13 Mulithreading Nov 27-29 (Chapter 20)

Week 14 Futures and other form types Dec 4-6

Week 15 Final Dec 11-13

Assignments:

Week 1 – Assignment 1 given (Basic Class/Object assignment)

Week 2 – Milestone 1 due (Project Idea), Assignment 1 due, Assignment 2 given (Simple Calculator)

Week 3 – Milestone 2 due (Specifications), Assignment2 due, Assignment 3 given (Create a Wizard)

Week 4 – Assignment 3 due, Assignment 4 given (Birthday Organizer)

Week 5 – Assignment 4 due, Assignment 5 given (Create a Windows Explorer)

Week 6 – Assignment 5 due, Assignment 6 given (Enhance Birthday Organizer)

Week 7 – Exam 1 given, Milestone 3 due (Progress Report on Implementation)

Week 8 – Assignment 6 due, Assignment 7 given (Customizing DataGridView)

Week 9 – Assignment 7 due, Assignment 8 given (Simple Media Player)

Week 10 – Assignment 8 due, Assignment 9 given (Simple Web Browser)

Week 11 – Assignment 9 due, Assignment 10 given (Contact Management)

Week 12 – Thanksgiving

Week 13 – Assignment 10 due, Assignment 11 given (Data Retrieval)

Week 14 – Assignment 11 due, Assignment 12 given (XAML form)

Week 15 – Assignment 12 due, Final Projects due