Skip to content | Change text size

M O N A T A R

InfoTech Unit Avatar

CSE2040 Comparative Operating Systems - Unix and Windows

Chief Examiner

This field records the Chief Examiner for unit approval purposes. It does not publish, and can only be edited by Faculty Office staff

To update the published Chief Examiner, you will need to update the Faculty Information/Contact Person field below.

NB: This view restricted to entries modified on or after 19990401000000

Unit Code, Name, Abbreviation

CSE2040 Comparative Operating Systems - Unix and Windows (28 Jun 2004, 1:25pm) []

Reasons for Introduction

Reasons for Introduction (28 Jun 2004, 1:27pm)

This description is for an existing unit. The unit covers features of commercial operating systems including process management, memory management, concurrency, job and process scheduling, file systems, applications programming interfaces, and operating systems security. The students will gain an understanding of and experience with major commercially used operating systems.

Role of Unit (17 Jun 2004, 3:55pm)

Unit provides an indepth look at what is necessary to run a compter system ie how the hardware is managed so that other applications like Java and Visual studio can actually work

Relationship of Unit (17 Jun 2004, 3:57pm)

Related to CSE2302 at Clayton; CSE2302 focuses more on multiuser programming.

Relevance of Unit (28 Jun 2004, 1:29pm)

This unit provides students with the option of gaining knowledge and also practical experience in operating systems that are widely used in industry and acedemia.

Objectives

Knowledge and Understanding (Cognitive Domain Objectives) (13 Aug 2004, 12:12pm)

Knowledge - What are inodes;file protections; page tables;device drivers; process management, memory management and job and process scheduling.

Comprehension - How a directory system/file system is implemented in Unix and Windows; how to cope with variable length file names. Security issues for operating systems.

Application - How to install a new device (connect to) your computer system; how does 'plug and play' work. How to decide on the appropriate security measures for a group of users.

Analysis - how in interpret system error messages and troubleshoot non working applications or hardware. How to stop your computer being infected/compromised by viruses. Monitoring and tuning system performance and scheduling admnistrative tasks automatically.

Attitudes, Values and Beliefs (Affective Domain Objectives) (13 Aug 2004, 12:13pm)

Operating systems as resource managers for:

  1. CPU context switching, process scheduling and job scheduling
  2. memory management and virtual memory systems
  3. I/O device drivers and management
  4. file subsystems
  5. abstract resource allocation strategies

Asynchronous and synchronous communication mechanisms and their use in operating systems Interprocess communication and its use in distributed computer systems

Practical Skills (Psychomotor Domain Objectives) (13 Aug 2004, 12:11pm)

Upon successful completion of this unit students will be able to : manage a Unix file system

manage redirection of standard Input, Output and Error

manage environment variables

process and job control monitoring

write Unix shell scripts

write Windows scripts

manage data storage and hard disks

Relationships, Communication and TeamWork (Social Domain Objectives) (13 Aug 2004, 12:16pm)

No group work is involved in this subject. Students complete their assignments individually, but are encouraged to discuss their approaches and understanding of concepts with fellow students in tutorials.

Unit Content

Summary (17 Jun 2004, 4:17pm)

The unit covers features of commercial operating systems including process management, memory management, concurrency, job and process scheduling, file systems, applications programming interfaces, and operating systems security. Shell scripting in both Unix and Windows will be used to illustrate manipulating OS resources.

Recommended Reading (17 Jun 2004, 4:18pm)

Deital, H.M., Operating Systems (2nd Edition) , Addison Wesley

Stallings, W., Operating Systems Internals and Design Principles (3rd Edition), Prentice Hall, 1998.

Tanenbaum, A.S, Modern Operating Systems,. Prentice Hall International (2nd edition 2001).

Tanenbaum, A.S., Woodhull, A.S., Operating Systems, Design and Implementation. Prentice Hall International (2nd edition 1997).

Sobell, M., A Practical Guide to the Unix System (3rd . Edition), Benjamin Cummings.

Window Script hosting using VB script:

http://msdn.microsoft.com/scripting/default.htm?/scripting/vbscript/doc/vbstutor.htm

Teaching Methods

Mode (04 Oct 2004, 2:43pm)

on campus

* 1*2hr lecture per week * 1x2 hour lab class per week

Strategies of Teaching (28 Jun 2004, 1:58pm)

One two hour lecture per week covering the core theoretical material; One two hour practical per week to reinforce lecture material and develop programming skills necessary to support the management of an operating system installation.

Teaching Methods Relationship to Objectives (04 Oct 2004, 2:44pm)

lectures will address all the knowledge objectives

labs will address practical skills objectives, and instill appropriate attitudes amongst students

Assessment

Strategies of Assessment (17 Jun 2004, 4:20pm)

65% - 2 hr exam at the end of semester covering all theory and practical work 30% - 1 Assignment using Windows95 and Unix scripts 5% - Successful completion of the DISKUTIL exercises. To pass the subject a minimum of 40% must be attained for each component.

Workloads

Workload Requirement (28 Jun 2004, 2:00pm)

Total expected student workload 12 hrs/week.

Resource Requirements

Lecture Requirements (28 Jun 2004, 3:09pm)

One high tech lecture theatre for two hours per week

Tutorial Requirements (13 Aug 2004, 12:17pm)

none.

Laboratory Requirements (28 Jun 2004, 3:11pm)

Students need to have access to Unix accounts (eg via the SNG machine provided by ITS) and windows accounts. Expect 16 students per lab class.

Staff Requirements (28 Jun 2004, 3:13pm)

1 lecturer from CSSE staff familiar with operating system concepts. 1 tutor per 16 students for laboratory session.

Software Requirements (21 Oct 2005, 1:04pm)

Windows accounts and labs maintained by IT services FIT. Windows script host should be installed on these machines. Unix accounts on machines maintained by Monash ITS eg SNG.

Library Requirements (28 Jun 2004, 3:17pm)

No extra library resources required. Books specified in CSE1201 are sufficient. New material / articles referenced via the internet.

Implications for CASPA (13 Aug 2004, 12:18pm)

None.

Interfaculty Involvement (13 Aug 2004, 12:18pm)

None.

Interschool Involvement (13 Aug 2004, 12:19pm)

None.

Other Resource Requirements (13 Aug 2004, 12:20pm)

Working X386 machines with a 5 1/4inch drive to operate special directory editing software. This works in DOS mode only.

Prerequisites

Prerequisite Units (28 Jun 2004, 3:20pm)

CSE1201, COT1140 or equivalent

Prerequisite Knowledge (13 Aug 2004, 12:24pm)

Students are expected to:

have managed files (via directories) and know about file properties. have run multiple processes on a single CPU machine. understand data representation (text, integer, float etc) have an understanding of programming.

Corequisites (28 Jun 2004, 3:23pm)

NONE

Prohibitions (28 Jun 2004, 3:22pm)

COT2040, CSC2020,CSE2302, RDT2141,RDT2410

Alias Titles (13 Aug 2004, 12:24pm)

None.

Level (13 Aug 2004, 12:25pm)

Second Year

Research Interest (13 Aug 2004, 12:26pm)

Operating Systems

Proposed year of Introduction (for new units) (13 Aug 2004, 12:25pm)

1996

Frequency of Offering (24 Jun 2004, 1:27pm)

Once per year, in either semester 1 or semester 2.

Enrolment (28 Jun 2004, 3:26pm)

40+ students

Location of Offering (28 Jun 2004, 3:27pm)

Caulfield

Faculty Information

Proposer

Jason Ceddia

Approvals

School:
Faculty Education Committee:
Faculty Board:
ADT:
Faculty Manager:
Dean's Advisory Council:
Other:

Version History

17 Jun 2004 Jason Ceddia Initial Draft; modified UnitName; modified UnitName; modified ReasonsForIntroduction/RIntro; modified ReasonsForIntroduction/RRole; modified ReasonsForIntroduction/RRelation; modified UnitObjectives/ObjCognitive; modified UnitObjectives/ObjCognitive; modified UnitObjectives/ObjAffective; modified Classification; modified UnitContent/Summary; modified UnitContent/RecommendedReading; modified Teaching/Mode; modified Assessment/Strategies
24 Jun 2004 Dianne Hagan modified Frequency to include both semester 1 and semester 2
28 Jun 2004 Jason Ceddia modified UnitName; modified ReasonsForIntroduction/RIntro; modified ReasonsForIntroduction/RRelevance; modified UnitObjectives/ObjCognitive; modified UnitObjectives/ObjPsychomotor; modified Teaching/Strategies; modified Workload/WorkHours
28 Jun 2004 Jason Ceddia modified ResourceReqs/LectureReqs; modified ResourceReqs/LabReqs; modified ResourceReqs/StaffReqs; modified ResourceReqs/SoftwareReqs; modified ResourceReqs/LibraryReqs; modified Prerequisites/PreReqUnits; modified Prohibitions; modified Corequisites; modified Enrolment; modified LocationOfOffering
13 Aug 2004 Jason Ceddia modified UnitObjectives/ObjPsychomotor; modified UnitObjectives/ObjCognitive; modified UnitObjectives/ObjAffective; modified UnitObjectives/ObjSocial; modified ResourceReqs/TutorialReqs; modified ResourceReqs/CaspaImpact; modified ResourceReqs/InterFaculty; modified ResourceReqs/IntraFaculty; modified ResourceReqs/OtherResources; modified Prerequisites/PreReqKnowledge; modified AliasTitles; modified Level; modified DateOfIntroduction; modified Research
04 Oct 2004 John Hurst modified UnitObjectives/ObjText; modified Teaching/Objectives; modified Teaching/Mode; modified Teaching/Objectives
17 Oct 2005 David Sole Added Software requrirements template
21 Oct 2005 David Sole Updated requirements template to new format

This version: