Introduction to Operating Systems
POS / 355
University of Phoenix
Tampa Campus
Instructor:
Kurt Madsen
Starting
|
Course: |
POS/355 Introduction to Operating Systems
|
|
Version: |
POS335u2
|
|
Location: |
|
|
Schedule: |
Tuesday evenings from
|
|
Calendar: |
Starting
|
|
Course Description: |
This course provides an introduction to operating systems. Topics covered include operating system concepts,
program execution, and operating system internals such memory, processor,
device, and file management. A variety
of operating systems are compared and contrasted. This course is based upon the
|
|
Instructor: |
Email: kurtmadsen@email.uophx.edu Website: www.madsen.us
|
|
Availability: |
E-mail is the preferred method of communication. By telephone, please call Monday through Friday between 9:00 a.m. and 5:00 p.m. Or, weekday evenings between 7:00 p.m. and 9:00 p.m.
|
|
Biography: |
Kurt Madsen has worked as a software engineer, manager, and consultant in all phases of the system development lifecycle in the following industries: telecommunications, financial services, e-commerce, aviation, and healthcare. He has an M.S. in computer science from New York Polytechnic and a B.A. in economics from Rutgers University. As an Adjunct Instructor, he has taught computer science at the University of South Florida, College of Engineering.
2001 - Present. Mr. Madsen founded MetaTech, Inc., a consulting firm that helps companies become more agile with respect to how their IT departments handle continually changing requirements. This is accomplished through recommended changes in architecture, process, and organization.
1998 - 2001. As a Management Consultant at Perot Systems, he advised clients on e-commerce projects such as internet banking and e-marketplaces.
1993 - 1998. At Salomon Brothers, a wholesale investment bank, he led the development of a Business-To-Business (B2B) integration product used by banks for electronic trade confirmation and securities clearance.
1986 - 1993. He began his career at Nynex Science and Technology, an R&D laboratory, where he specialized in object-oriented technologies and distributed computing.
|
|
Books: |
Davis,
William S and T. M. Rajkumar (2001). Operating Systems: A Systematic View. Aaron, J.
E. (1997) The Little, Brown Compact
Handbook. |
|
|
Software: |
You are required to have the software specified below: · Microsoft Office Professional for Windows. The relevant programs within MS Office Professional for this course include Word, Excel, PowerPoint, and Access (database). The MS Office suite is used for the course because it is ubiquitous in business. If expenses are an issue, you may substitute alternate software such as Star Office (which is free) with prior written permission of the instructor. It is assumed that students have a basic working knowledge of this software. While some guidance on usage will be available from the instructor and fellow students, in-depth instruction in using these software applications is beyond the scope of this course. · Any version of Linux is strongly encouraged. If you do not have one, we will install one in class. · An e-mail address. · Access to the Internet with a browser (e.g., Internet Explorer, Netscape Navigator, Konqueror) · Virus protection software (e.g., Norton Antivirus from www.symantec.com) |
|
|
e-Resources: |
n/a other than |
|
|
|
“Library Handbook.” (Download from http://ecampus.phoenix.edu.) “Directions for Completing Learning Team Log.” (This is available for download from http://ecampus.phoenix.edu.) “Learning Team Log.” (Download from http://ecampus.phoenix.edu.) “Directions for Completing the Learning Summary.” (This is available for download from http://ecampus.phoenix.edu.) “Learning Summary.” (Download from http://ecampus.phoenix.edu.) |
|
|
Learning Resources |
Students are highly encouraged to participate in using the learning resource center for research and study. The digital library is open 24 hours a day, 7 days a week, and is completely free of charge. Registration to use the digital library is required – Web Site: www.library.uophx.edu
|
|
|
|
|
|
|
Course Standards |
UOP trusts each student to maintain high standards of honesty and ethical behavior. All assignments submitted in fulfillment of course requirements must be the students’ own work. All assignments except those designed as “group” is meant to be individual efforts. Group work is meant to be equal efforts by all group members. It is assumed that students will perform professionally in preparing work required for this course.
|
|
Plagiarism |
“Plagiarism (from a Latin word for “kidnapper”) is the presentation of someone else’s ideas or words as your own. Whether deliberate or accidental, plagiarism is a serious and often punishable offense” (Aaron, 1998, p. 258). Please review The Little, Brown Compact Handbook, 4th ed., pp. 329-333.
|
|
Original vs. Copied Work |
When writing papers or other assignments, it is OK to include 3rd- party quotes as long as the source is properly referenced in the back of your paper. But copying blocks or pages of text from 3rd- party sources (e.g., Internet) directly into your paper is discouraged even when properly referenced. When the need to copy limited text into a student's paper is compelling, 3rd party content should be identified as such with references and block text font such as the following:
Here is an example of material that is copied directly into a paper.
Grading is based upon the following criteria:
In summary, follow these steps when writing papers:
4. Research and read 3rd-party content to learn the topic and get ideas. 5. Then, Develop a document outline and, optionally, a logic map. 6. Next, write your own material to fill in the outline. 7. Finally, add references to the bibliography section of your paper.
Do these steps and your understanding will shine through on your papers.
|
|
Grading of Written Work |
All documents are to be typed, spell-checked and grammar checked, submitted double-spaced, and prepared in the proper APA format required for the program. The instructor will use The Little, Brown Compact Handbook (3rd ed.) for format reference. The attached “Standards for Written Work” can be used as guide to evaluate and weight the scoring of papers.
· Assignments, both oral and written, will be evaluated on: · Completion of assigned task (instructions) · Submission of assigned task on time · Evidence of sufficient time spent appropriately · Quality of content and research
|
|
Grading of Oral Presentation |
Although the facilitator is evaluating your presentation, he/she is not your sole audience. Be sure to engage your entire audience, in this case, your fellow classmates: Appropriate eye contact toward the audience; ask them questions or ask for their opinions. Structure your presentation so that you address the following elements: 8. Motivate: Why is this important? 9. Preview: What specific points/topics are being covered? 10. Discuss: Cover each point/topic with adequate support. 11. Review: What was covered and how it applies.
The attached “Standards for Oral Presentations” can be used to evaluate and weight the scoring of your presentations.
|
|
Late Policy |
All assignments are to be completed prior to the week in which they appear in the module or website. Assignments must be turned in the night that they are due. No emailed revisions will be accepted past the due date (without assessing a late penalty).
A 10% late penalty will be assessed for all late or incomplete work. All missed assignments must be made up by the next session. Assignments not submitted during next session immediately following the due date will receive a zero. No assignments will be accepted past the last night of the course.
An “I” grade may be issued if requested and approved by the instructor, before course completion. The “I” must be made up within three weeks and the highest grade possible for those assignments is a “B”.
|
|
Attendance and Participation |
Since this course is only six weeks, students are strongly encouraged to attend all workshop and learning team sessions. Per university policy, students are allowed one workshop absence and one absence for learning team meetings during the course. AN INSTRUCTOR CANNOT ISSUE A GRADE OTHER THAN “W” OR “WF” TO A STUDENT WITH MORE THAN ONE WORKSHOP ABSENCE OR LEARNING TEAM MEETING. There is no approval for second absences.
Any absence will adversely affect the final course grade (e.g., attendance points, participation points, quizzes, and the late penalty as applicable). If there are assignments that are due on the night of the absence, and those assignments are not emailed to the instructor by the 6:00 p.m. that night, they will be considered late and the late penalty will apply. [The reason for this policy is that assignments may carry more weight towards the final grade than attendance and participation points. If it were possible to turn in assignments after 6:00 p.m., there would an incentive to miss a workshop if a student were running late with completing an assignment.]
|
|
Evaluation Criteria |
The final grade will be determined by a weighted average of the following evaluation criteria:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Grading Standards |
Final letter grades and G.P.A. input will be determined using upon the following ranges:
|
|
Teaching / Learning Model |
This course will incorporate faculty facilitation of theoretical content knowledge and its applications. Student achievement of course objectives is evidenced by text-based discussions, individual written work, quizzes, oral assignments, and team work. Through the accomplishment of projects, students practice and refine learned skills and evidence application of knowledge through product submissions for evaluation and grading.
|
|
Learning Teams |
Students are encouraged to review the course module for instructions on the governance of Learning Teams, student responsibilities for the group, and themselves. Students will complete a “Learning Team Charter” for this course. The “Learning Team Log” is an official attendance log to document activities and/or performance related issues. Any Learning Team member who does not contribute risks loosing credit for the learning team evaluation criteria. The log should reflect the lack of contribution or performance and be agreed upon by the group
Learning teams are an extension of the classes and an essential part of the academic experience for students. In addition to providing a supplemental learning environment for mastery of course content, learning teams also provide students with an opportunity to develop and refine teamwork skills. Students are expected to ascertain the location for their learning team meeting each week during the class session. The instructor must approve the location as appropriate and conducive to learning. At the first meeting of the learning team, each team should create a charter that will be reviewed by the instructor during the second class session. Each week, each learning team must complete a learning team log documenting each member’s attendance at the learning team meetings. Non-attendance or attendance for less than the required scheduled time of Learning Team meetings by any individual student will be considered during the grading process for that student. Non-attendance at Learning Team meetings and/or classroom meetings may result in course withdrawal and a "W" grade being issued. Teams should create one unified log for the entire team’s activity each week that is signed by each team member. Two copies of that log should be provided to the faculty member, so that one copy can be turned in for attendance and the other copy retained by the faculty member.
|