• Name: Jerry Rugg, Adjunct Associate Professor


• E-mail address: jrugg@faculty.ed.umuc.edu


• Office hours: I check into the WebTycho classroom almost daily and you are encouraged to ask all questions in one of the Conferences I will set up there.


• Details of contact: Except for emergency situations, I do not accept telephonic requests for help. By exception only, I will accept direct email contact. Once contacted, you should expect at least a preliminary answer within 1-2 days.


• Teaching Assistant information: None

This is the last in the series of Java programming courses offered to students interested in learning computer programming and desiring a degree in Computer Studies.

Course Evaluation:
Mid-Term Exam - 15%

Final Exam - 15%

Participation - 10%

Projects (4) 60% (projects may not be equal weighted)

Grading Scale:
Letter grades will be assigned as follows:

90 - 100% = A

80 - 89% = B

70 - 79% = C

60 - 69% = D

Less than 60% = F(a)



Additional Grading Information:

1. Late exam policy. Unless you have made agreeable arrangements with me PRIOR to the scheduled exam date, there will be no make-up exams. In the event of an online exam, the exam will be reduced by at least one letter grade for one day late, two letter grades for two days late and an automatic F for any exam later than two days.




2. Late programming project policy. Unless you have made agreeable arrangements with me PRIOR to the project due date, grades on all projects submitted after the due date will be reduced by 10% (one letter grade) per week after the due date.




3. WebTycho classroom participation. Participation will be judged based on the quality and quantity of your postings to the discussion conferences and your response to periodic "Question of the Day" postings I will make. Your participation points can easily become the swing points between a higher versus a lower grade.




4. Proctored final exam. It is your responsibility to make appropriate arrangements to take the proctored final exam during the week of 16 - 22 June 2008. Normally the exam is administered through your local UMUC Field Representative. If this is not a possibility for you need to make appropriate arrangements with the UMUC-Europe Distance Education Office.

The following is a list of expected student responsibilities.

1. Attendance / Participation. You are strongly encouraged to participate in all discussions. It can only help your understanding of the course material. Participation, which is 10% of your final grade, in discussions, both asking questions and providing answers, may well become the difference in your final grade between an A-B or B-C.




2. Time Requirements. Students will be spending considerable amount of non-classroom time researching, designing and implementing the programming projects. A rough estimate, based on the mythical average student, would be 10-12 hours per programming project. Note, this estimate does not include time spend reading the assigned chapters.




3. Computer Laboratory Facilities There may be University of Maryland Computer Labs available for your use. If you plan on using these facilities, you should check the exact hours and procedures as they may vary from course to course and location to location. You are not required to use these lab facilities. You may work at home, at work (with proper permissions) or any other place as long as you do your own work.




4. Java Software. It is expected you already have setup or procured access to a computer running the Java JDK and your favorite Java Integrated Development Environment (IDE). We will not be spending class time discussing the setup and configuration of any Java IDE although I am willing to answer questions for the Java IDEs I am familiar with in the classroom discussion areas. There are many free Java IDE programs available. Additional informations and help will be posted in the WebTycho classroom.

There will be four major programming assignments in this course. The assignments will be taken from or modify the exercises found at the end of each chapter. The following are general programming assignment requirements:

1. Programming assignments must be well commented
   
2. Programming assignments will follow the object-oriented design and patterns concept outlined in the text
   
3. Programming assignments will:
   
   
   
   • Use named constants to enhance modifiability
     
   • Use variable and method identifiers that are meaningful
     
   • Use established Java programming style conventions
     
   
   
4. Programming assignments must be complete
   
5. Programming assignments must be tested
   
6. Programming assignments must meet design specifications prior to submission
   

I started writing computer programs for mainframe computers using the FORTRAN computer language in 1985. These programs dealt mainly with atmospheric and aerodynamic models. I moved to writing programs for IBM compatible computers using PASCAL, C, and ADA computer languages in 1988. During my 24 year career in the U.S. Air Force I spent a great deal of time in integrating microcomputers as replacements for aging teletype machines on the worldwide Automated Weather Network. I also worked at the Automated Weather Network main switching hub routing data packets over the worldwide weather data exchange network using various protocols and transmission capabilities.

I started teaching evening courses part time for Park College in 1992 and joined the UMUC - Europe staff in the Fall of 1993. Since then I have taught just about every under graduate programming course offered my UMUC plus a few side diversions in networking protocols. I started teaching graduate courses for UMUC - Europe in the Spring 2002.

I currently program almost exclusively for the Win32 environment using the latest .NET Framework as the Data Sotorage Controller architect for an enterprise caliber, multi-tier, storage virtualization system. Other projects I have architected and / or worked on over the past few years include a Web Based Database Application Security and Group Policy system. Also a proprietary script language to record and playback routine administrative tasks and application installation routines over a LAN; a set of client / server programs, using Java, http and XML, to remotely configure and install software on a client work station running Windows, Linux Mac OS X or Solaris.