Course Home | Syllabus | Assignments | Schedule | Readings | Downloads | Grades | Submissions | [print]

IT 3100: Systems Design and Administration I

Fall 2018 Syllabus

Course Description

Required of Computer and Information Technology majors and students with an emphasis in Information Technology. Covers system administration topics for managing Internet facing services, including DNS, SMTP, and HTTP. Students will install, configure, and test services in a server environment.


CS 1400 and IT 2400 both with a C- or better

Course fees

The fee for this course is $25.00, used to assist in maintaining the CIT infrastructure.


One section:

  1. MWF 11:00-11:50 am in SCC 117

    Final exam Wed Dec 12, 11am-12:50 pm


Professor: Dr Joe Francom

Joe’s Fall 2018 Schedule

Days Time
MWF 8am - 10:00 - By appointment only
MWF 10am-10:50 - Office
MWF 11am-11:50 - IT3100
MWF 12pm-12:50 - Office
MWF 1pm-1:50 - IT4510
MWF 2pm-2:50 - IT3300
MWF 3pm-3:50 - IT4200


The student will be able to discuss the principles of :

The student will be able to demonstrate practical skills in :



There are no required text for this course. There isn’t really a ‘single’ book that would contain all the topics that we are learning; however, you could find most any Linux administration book to be of help. In particular, try the books found on safari online (as they are free).

Computer Labs

You may use the computers in the general lab area in the Smith Computer Center. There will also be lab assistants in these labs. You will also have access to virtual machines to complete most of the tasks.

Course Web Site

This course has an accompanying website. You are responsible for announcements, the schedule, and other resources posted on the website. Assignments and grades will be managed using Canvas, which requires a valid Dixie username and password. The course website is accessible at

Assignments and Exams


The student is responsible for reading the material in the textbook. A reading schedule is provided with the class schedule on the course website. The student is expected to read the material before the class in which it is discussed. The book also includes material beyond what we will discuss in lecture, which you are encouraged to study on your own. Feel free to bring questions from the reading to lectures or to office hours.


There will be approximately 20 projects, with multiple projects due almost every week. The assignments are designed to promote the course objectives listed above.

Assignments are due before 11:55 pm on the due date.

All assignment submissions will be weighted equally.


This course will have about 7 quizzes in the semester. Quizzes are designed to check understanding of the course materials. Quizzes may be short in-class activities, or out-of-class activities.

All quizzes will be weighted equally.


There will be approximately 5 practical exams scheduled near the end of the semester. The practical exams will require students to complete hands-on work on computer systems, relating to homework assignments. The students will be expected to demonstrate the practical skills listed in the course objectives. The practical exams will be conducted in a time limited setting.

There will be a final exam as scheduled during finals week. The final will be a comprehensive written exam. The students will be expected to demonstrate understanding of the principles listed in the course objectives.


Assignments will count for 25% of your point total. Quizzes will count for 5% of your point total. The final exam will count for 10% of your point total. The practical exams will count for 60% of your point total.

Letter grades are assigned based on the percentage of possible points attained, according to the following chart:

Here is the grading scale:

  >= 94 = A
  >= 90 = A-
  >= 87 = B+
  >= 84 = B
  >= 80 = B-
  >= 77 = C+
  >= 74 = C
  >= 70 = C-
  >= 67 = D+
  >= 64 = D
  <  64 = F

Course Policies


Students are responsible for material covered and announcements made in class. School-related absences may be made up only if prior arrangements are made. The class schedule presented is approximate. The instructor reserves the right to modify the schedule according to class needs. Changes will be announced in class and posted to the website. Exams and quizzes cannot be made up unless arrangements are made prior to the scheduled time.


Courses should require about 45 hours of work per credit hour of class. This class will require about 135 hours of work on the part of the student to achieve a passing grade, which is approximately 9 hours per week. If you do not have the time to spend on this course, you should probably rethink your schedule.

Late work

Late work is not accepted. You are expected to turn things in by the date they are due. If something is due at 11:59pm and you are 1 minute late, you will not receive credit. Your lowest assignment score will be dropped.

Any Exceptions must be discussed with the instructor. Computer failure does not qualify as an excuse for late work.

It is your responsibility to see that assignments/projects are turned in and on time. If you come to me and say, “I turned in that assignment”, yet I have no record of it, you will receive a 0. The burden of proof is on you to prove that you turned in something at a given time. We are using an electronic submission system which records when a item is submitted.

Finally, no points can be contested after a test which covers that assigned material has been given. So for example, if you come to me at the end of the semester and say “Oh, but I turned in that assignment the second week of the semester”. If I don’t have a record of it, and we have already tested on it, you will not get the points.

Cheating and Collaboration

Limited collaboration with other students in the course is permitted. Students may seek help learning concepts and developing programming skills from whatever sources they have available, and are encouraged to do so. Collaboration on assignments, however, must be confined to course instructors, lab assistants, and other students in the course. Students are free to discuss strategies for solving programming assignments with each other, but this must not extend to the level of programming code. Each student must code his/her own solution to each assignment. See the section on cheating.

Cheating will not be tolerated, and will result in a failing grade for the students involved as well as possible disciplinary action from the college. Cheating includes, but is not limited to, turning in homework assignments that are not the student’s own work. It is okay to seek help from others and from reference materials, but only if you learn the material. As a general rule, if you cannot delete your assignment, start over, and re-create it successfully without further help, then your homework is not considered your own work.

You are encouraged to work in groups while studying for tests, discussing class lectures, discussing algorithms for homework solutions, and helping each other identify errors in your homework solutions. If you are unsure if collaboration is appropriate, contact the instructor. Also, note exactly what you did. If your actions are determined to be inappropriate, the response will be much more favorable if you are honest and complete in your disclosure.

Where collaboration is permitted, each student must still create and type in his/her own solution. Any kind of copying and pasting is not okay. If you need help understanding concepts, get it from the instructor or fellow classmates, but never copy another’s code or written work, either electronically or visually. The line between collaborating and cheating is generally one of language: talking about solutions in English or other natural languages is usually okay, while discussions that take place in programming languages are usually not okay. It is a good idea to wait at least 30 minutes after any discussion to start your independent write-up. This will help you commit what you have learned to long-term memory as well as help to avoid crossing the line to cheating.

College Policies

Click on this link - - for comprehensive information on the Semester Dates, the Final Exam Schedule, university resources such as the library, Disability Resource Center, IT Student Help Desk, Online Writing Lab, Testing Center, Tutoring Center, and Writing Center. In addition, please review DSU policies and statements with regards to Academic Integrity, Disruptive Behavior and Absences related to university functions.

If you are a student with a medical, psychological, or learning disability or think you might have a disability and would like accommodations, contact the Disability Resource Center (652-7516) in the Student Services Center. The Disability Resource Center will determine eligibility of the student requesting special services and determine the appropriate accommodations related to their disability.

Important Links

Last Updated 08/17/2018