<br>


Last revised May 6, 2006

Last revised June 10, 2006. Periodically check for updates, revisions may occur through August 21, 2006.

Course Syllabus for IRLS 471/571, Introduction to Information Technology.

Link to Course Outline

Fall 2006 Instructor: Trevor Smith

Image of Trevor Smith

 

COURSE NAME, NUMBER, AND PREREQUISITES

Introduction to Information Technology

IRLS 471/571 Section 791

This course is an elective and there are no prerequisites.
[return to top of page]


COURSE DESCRIPTION

"This course is designed to introduce the basic concepts and applications of Internet-related information technology and its impacts on individual users, groups, organizations, and society. The topics in this survey course include computing basics, network applications, human computer interactions, computer-support cooperative work, social aspects of information systems, and some economic and legal issues related to digital services and products." (3 credit hours)

"If the automobile had followed the same development cycle as the computer, a Rolls-Royce would today cost $100, get a million miles per gallon, and explode once a year, killing everyone inside." -- Robert X. Cringely.

Introduction to Information Technology is a course about computers, but it is not just about computers. More than any other recent development, the computer, and specifically Internet-related technology, has changed the way humans interact with the world, information, and each other. To understand social change in the digital age and the implications for information professionals, it is necessary to have a broad understanding of technology. This course will cover the history and development of computers and networking, survey Internet technologies, and describe some of the electronic tools that are found in modern libraries. Students will be assigned hands-on projects that reinforce important concepts. Finally, we will look at the implications and consequences of information technology such as collaboration, hacking, access/ownership, free-inquiry, and information economics.

The purpose of this course is not to teach you how to be an engineer, administrator, web mistress, or even a systems librarian. Rather, upon completion of IRLS 471/571, you should be able to intelligently discuss library and Internet technology with IT professionals, make reasoned purchase recommendations, constructively critique web sites, and present information online in an effective and appealing manner. You should also understand enough about inevitable technological change to help your institution plan for success.

General familiarity with computers will help on some assignments, but as the semester progresses, we'll find that we all have strengths and weaknesses when it comes to the course material. "1337 haxors" may find some of the early tech-oriented assignments relatively easy, but they won't necessarily have any advantage when it comes to the contextual issues surrounding technology.

Brass Tacks

This is a virtual course with the majority of interaction taking place in the UofA's course management system, Desire2Learn (D2L). In D2L we have access to email, announcements, discussion boards, an assignment drop-box, a resource repository, a chat room, and a secure grade book. We will use all of these features this semester. No on-campus attendance is required.

A normal week will start on Monday when the Unit assignment (if any) from the previous week will be due by 8:00pm. New lectures, announcements, and any additional required reading for the next week will be posted on Tuesday and Thursday. Every attempt will be made to post the grade for Monday's assignment by midnight on Friday.

Small groups will be assigned about three weeks in to the class when the roster has stabilized. This is also when we will discuss the details of the group project.

The final exam will be distributed the last week of the course. It will be essay format, select several questions from a list, and will require synthesis of the knowledge you have been acquiring during the semester. The final is optional for student registered in IRLS 471.

What to Expect

There are two areas to consider when planning your time commitment during the semester. We will share about 40 hours of "mediated instruction" (it would be "classroom time" if we were in a face-to-face course), or about 2.5 hours per week. This will consist of everything from text-based lectures and interactive tutorials to multi-media Flash presentations with music, dancing, and explosions (okay, I'm exaggerating a bit here). Homework will include required reading, finding and using optional resources, and assignments--a target of 10 hours per week, with some weeks much less, other weeks slightly more. Plan on a combined total of 12-13 hours per week for an average student to keep up with the class.

The good news is that, other than scheduled chat office hours (which are optional, and subject to re-scheduling based on the needs of the class), the course is entirely asynchronous, you can log in to D2L any time you wish. Having said that, you should expect to check in about 5 times a week; once a day Monday-Friday is perfect. Keep in mind that most of the important information will be distributed on Tuesday and Thursday. If you are going to be unable to access the class for more than three or four days in a row, please let me know so we can make some special arrangements.

I have a love-hate relationship with group projects. It is very difficult to make sure every participant does his/her fair share and receives an appropriate grade. However, there are three aspects of groupwork that redeem it as a learning tool for this particular course. First, it tends to break down the sense of isolation, a chronic problem of distance education. Second, virtually all technology development is done in groups, teams, and committees--to really understand technology development you have to understand small-group dynamics. Third, an important aspect of this class is understanding collaborative technologies; how better to learn than by using technology to collaborate? A couple of components of the group project will be assigned as individual work to make the experience less stressful.

The final exam will be written toward a three-hour time block, that is to say, spending much more time on it than three hours will result in diminishing returns.

[return to top of page]

COURSE OBJECTIVES

By the completion of this course, you will:

[return to top of page]



REQUIRED COURSE MATERIALS

Textbook:

Krug, S (2005). Don't make me think: A common sense approach to web usability (2nd Edition). Berkeley, CA: New Riders Press. ISBN: 0321344758. ($35.00 -- check your favorite online bookseller for specials.)

Internet Access:

Students will need reliable online access. High speed internet such as broadband cable or DSL is highly recommended. Much of the course material will be presented in the form of large PDF documents, online tutorials, and multimedia files. While it is certainly possible to successfully complete this course with a dial-up connection, it will require advanced planning and patience--think World-Wide-Wait. Consider using the SIRLS computer lab, the UofA information commons, or even a public library computer center.

U-System Account:

You will need to have a U-System account for both the group project and several of the individual unit assignments. You must request this account be created for you (it is not automatically created when you get your email address). Once you have your UA NetID, go to https://account.arizona.edu/ and follow the "Create your U of A Email and other CCIT computer accounts" link. Request a U-System Computing account. The process can take 24 hours or longer, so try to get this done as soon as possible. If you have any trouble contact the CCIT helpdesk at http://support.ccit.arizona.edu/.

 

[return to top of page]



COURSE REQUIREMENTS

  1. Coursework
  2. Group Project
  3. Final Exam (optional for IRLS 471)

The coursework will be eight "Unit" level assignments that will focus on the previous week(s) topics. Each assignment will be worth 5 points for a total of 40% of the 571 student's grade and 57% of the 471 student's grade. These assignments will require you to post information on the discussion boards, answer essay questions, provide a link to something you found online or created, and/or write up the result of a "hands-on" exercise. While study groups, either in-person or virtual, are encouraged, the Unit assignments should be your own work. In other words, you can talk to each other about the assignments but do the exercises and write-up the results independently.

The group project will be detailed in week 3 or 4; you will be assigned to a small group and will select (or be given) a technology topic to develop an informational web site around. As part of this process you will individually assess your site, some of your classmates' sites, some external sites, and provide recommendations for improvement. In total, it is worth 30% of the 571 student's grade and 43% of the 471 student's grade.

The final exam will consist of a list of essay questions from which you will be asked to select and answer several. Each question will involve a combination of concepts from Units studied during the semester. This will give you an opportunity to demonstrate your mastery of the material as well as your ability to apply and synthesize the underlying ideas in new and different ways. The final is worth 30% of the 571 student's grade and it is optional for the 471 students.

[return to top of page]



COURSE POLICIES

Academic Code of Integrity

Students are expected to abide by The University of Arizona Code of Academic Integrity, see . 'The guiding principle of academic integrity is that a student's submitted work must be the student's own.' If you have any questions regarding what is acceptable practice under this Code, please ask an Instructor.

Accommodating Disabilities

The University has a Disability Resource Center . If you anticipate the need for reasonable accommodations to meet the requirements of this course, you must register with the Disability Resource Center and request that the DRC send me, the Instructor, official notification of your accommodation needs as soon as possible. Please plan to meet with me by appointment or during office hours to discuss accommodations and how my course requirements and activities may impact your ability to fully participate.

Assignment Policies

  • How to submit assignments: All unit/weekly assignments must be submitted in the D2L drop-box. They may be submitted by email (either D2L or my external email) only if there are technical problems with the drop-box. The format must be "standard" HTML--what this means is that you can not just use your word processor to "save-as" an HTML file (the files created by MS Word, for example, wreak havoc with some browsers). If you have Dreamweaver or FrontPage, they will work fine for your assignments; but if not, check out NVU, a free web development tool for all three major PC operating systems. If a unit assignment asks you to make a contribution to the discussion groups, please cut-and-paste what you posted into your drop-box submission. If you have any graphics or other objects referenced in your HTML, make sure that you submit all the files and use a relative link to objects from the same directory as your HTML document.

    A link to your group assignment must be submitted by every participant in their D2L drop-box. This will allow me to give you your individual grades and feedback.

    The final exam should also be submitted in the D2L drop box in "standard" HTML.
  • Assignment due dates: The Course Schedule will list specific due dates for assignments, and reminders will be posted in D2L. In general, late assignments will not be routinely accepted. I understand that emergencies and problems can occur in the course of the semester, so please contact me as soon as you find you may not be able to make a particular due date; under certain circumstances partial credit may be possible. To avoid technical problems remember my digital mantra, "save early, save often!"
  • Writing style: Be sure to include your name at the top of every submission. Clear and concise writing consistent with upper-division undergraduate and graduate course-work is expected on all assignments. I am not a stickler for precisely following a style manual (it can be almost impossible to create some things like "hanging indents" in HTML), but be certain to properly attribute the quotes, work, and ideas of others with citations--check out APA and Citation Machine for help. Spell-check is your friend.

Incompletes

The 1997-8 University of Arizona General Academic Manual, p.23 reads

The grade of I may be awarded only at the end of a semester, when all but a minor portion of the course work has been satisfactorily completed. The grade of I is not to be awarded when the student is expected to repeat the course; in such a case the grade of E must be assigned. Students should make arrangements with the instructor to receive an incomplete grade before the end of the semester ...

If the incomplete is not removed by the instructor within one year the I grade will revert to a failing grade.


[return to top of page]



GRADING

Every effort will be made to rapidly correct assignments. Grades and feedback can be found by clicking on a submitted and corrected assignment in the D2L dropbox. Grades can also be accessed through the "Grades" link on the D2L toolbar.

Points possible for each assignment
8 Unit Assignments

40 points (5 each)

Group Project 30 points
Final Exam (not required for 471) 30 points

 

Letter Grade 471 571
"A" 63-70 points 90-100 points
"B" 56-62 points 80-89 points
"C" 49-55 points 65-79 points
"D" 42-54 points N/A
"F" below 42 points below 65 points

Note: A student taking the class for 471 credit is not required to submit the final exam. However, a 471 student may choose to turn in the exam and be graded on the 571 scale. The student will receive the higher of the two possible grades.

How to get a good grade:

[return to top of page]

CONTACTING ME

Email is the quickest and most reliable way of contacting me. For class matters, internal D2L email is preferred and I will be checking it frequently during the semester. You can also contact me at my regular email address: smitht followed by @cochise.edu .

I will hold a weekly online office hour through the D2L "chat" interface from 7:00-8:00pm MST on Wednesday evenings (this is subject to change if the class agrees on a more convenient time for everyone).

If you have a question or situation that might be easier to talk about than exchange email, or if you get frustrated with technology and just want help from a human voice, I am available via telephone or Skype virtually anytime by appointment. Feel free to call my number at Cochise College, (520) 515-5421, but please understand if I have to reschedule our conversation to work around my "day job".

[return to top of page]