1 / 17

CGS 3763 Operating System Concepts Fall 2014 Euripides Montagne

CGS 3763 Operating System Concepts Fall 2014 Euripides Montagne. TODAY ’ S AGENDA. Go over course syllabus. What is an operating system? Class make up - who ’ s enrolled Major or Minor? Computer Science, IT or MIS Other computer science courses: CGS 1060 is minimum prerequisite

overton
Download Presentation

CGS 3763 Operating System Concepts Fall 2014 Euripides Montagne

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CGS 3763Operating System ConceptsFall 2014Euripides Montagne

  2. TODAY’S AGENDA • Go over course syllabus. • What is an operating system? • Class make up - who’s enrolled • Major or Minor? • Computer Science, IT or MIS • Other computer science courses: • CGS 1060 is minimum prerequisite • CGS 3269 would be very helpful • Programming experience will also be helpful although no programming projects required for this course

  3. SYLLABUS OVERVIEW • Office Hours • Euripides Montagne: HEC 217 MWF 11:00 a.m. to 12:00 (Noon) (HEC 217) T 2:00 p.m. to 3:00 p.m. (HEC 217) Email • eurip@eecs.ucf.edu (include CGS3763 in subject line) • Be professional in your correspondence • Website • http://www.eecs.ucf.edu/~eurip (there you will find a link to CGS3763) • Be sure to take notes in class • Text Book • Operating System Principles and Practice, 2e, Thomas Anderson and Michael Dahlin, 2014, Recursive Books, Ltd.

  4. SYLLABUS OVERVIEW • TA • Amir Mazaheri • Office hours: Wed: 10:00 a.m. to 12:00 p.m. (HEC 254) Email: amirmazaheri1990@gmail.com • (include CGS3763 in subject line) • Be professional in your correspondence

  5. SYLLABUS OVERVIEW (cont.) • Class Times • Mon, Wed & Fri, 1:30 p.m. - 2:20 p.m., CB2 206 • Final Exam • http://www.registrar.sdes.ucf.edu/calendar/exam/2014/fall/ • It will be comprehensive • Other Dates • Withdrawal deadline: Monday, October 27, 2014 • Classes end: Monday, December 1, 2014

  6. SYLLABUS OVERVIEW (cont.) • Attendance • Not taken but strongly encouraged • Homework exercises will be assigned • Turned in during class or Webcourses. • Answers given in class only. • Tests & Exams • Closed book, closed notes • Essay • Simple calculators only • Academic Behavior • Cheating or other forms of academic dishonesty will not be tolerated • Please turn off all cell phones, tablets and laptops in class.

  7. SYLLABUS OVERVIEW (cont.) • Grading Based on: • Homework 20% • First Midterm 25% • Second Midterm 25% • Final Exam 30% • Guaranteed Grading Scale: •   A 90 – 100% (88 – 89) = A- (86 - 87) = B+ • B 80 – 85% (78 – 79) = B- (76 – 77) = C+ • C 70 – 75% (68 – 69) = C- (66 – 67) = D+ • D 60 – 65% (58 – 59) = D- • F Otherwise

  8. SYLLABUS OVERVIEW (cont.) • Take advantage of multiple resources • Classroom lectures • Required text book • Lecture slides and review exercises • Publishers web site and slides • Use the internet or other text books • See me during office hours or email

  9. COURSE CONTENT • Not a course in Windows, Mac or Unix. • Not a point & click, “how to” course. • Instead we will look at the basic concepts that underlie these and other operating systems. • Processes & threads, • CPU scheduling, • memory and secondary storage management, • protection and security, • distributed systems • Why? • Dispel some of the mystery - understand what happens when you point and click. • Learn new algorithms - many OS concepts can be applied to other disciplines.

  10. TENTATIVE COURSE CALENDAR • Introduction • Computer System Structures • Operating System Structures • Processes • Threads • First Midterm (September 24 and 26) • CPU Scheduling • Process Synchronization • Deadlocks • Basic Memory Management • Second Midterm (October 29 and 31)

  11. TENTATIVE COURSE CALENDAR (cont.) • Virtual Memory • File Systems • Mass Storage Structures • Final Exam (December 8) • See UCF’s final exam schedules posted at: http://www.registrar.sdes.ucf.edu/calendar/exam/2014/fall/

  12. WHAT IS AN OPERATING SYSTEM? • Definition varies depending on who you ask: • resource allocator • master control program • everything vendor ships with the computer • program that is always running (kernel)

  13. WHAT IS AN OPERATING SYSTEM? • For purposes of our class an operating system: 1) is the interface or intermediary between a user/application and the computer hardware 2) provides an environment in which the user can execute programs conveniently and • application and/or system software 3) manages the computer’s resources efficiently • memory, disk space, CPU time, I/O, software, etc. • Often an OS is a tradeoff between convenience and efficiency • Windows (GUI) vs. Unix (command interpreter)

  14. OS AS INTERMEDIARY • We’ll discuss hardware later in Chapter 2. • What’s an application? • Software to accomplish a task • Spread sheet, word processor, browser, email • What about system software? • Depending on who you ask, can be considered application programs, a computer resource, or part of the OS

  15. WHAT IS A PROCESS?

  16. WHAT IS A PROCESS (cont.) • A process: • is a program in execution. • has a process control block (PCB) • The PCB has a program counter (PC) • A process can have one or more threads. • A thread is sometimes known as a lightweight process

  17. RUNNING MULTIPLE PROGRAMS • Parallel/Simultaneous Execution • Two or more processes performing the same activity at the same time • Requires two or more of the same resource (e.g., processors, printers, disk drives) • Concurrent Execution • Two or more processes executing at the same time but doing different activities on different devices. • Processes take turns using single shared resource • Gives the illusion of parallel processing

More Related