BBS646 - OPERATING SYSTEMS
| Course Name | Code | Semester | Theory (hours/week) |
Application (hours/week) |
Credit | ECTS |
|---|---|---|---|---|---|---|
| OPERATING SYSTEMS | BBS646 | Any Semester/Year | 3 | 0 | 3 | 6 |
| Prequisites | None | |||||
| Course language | Turkish | |||||
| Course type | Elective | |||||
| Mode of Delivery | Face-to-Face | |||||
| Learning and teaching strategies | Lecture Discussion Question and Answer | |||||
| Instructor (s) | Dr. Ahmet Burak Can | |||||
| Course objective | To teach basic concepts of operationg systems and operationg systems infrastructure. | |||||
| Learning outcomes |
| |||||
| Course Content | Basic operating systems concepts, Input/Output subsystem, Process Management, Process syncronization, Memory management, File management, Distributed processing and network infrastructure, Operating systems security | |||||
| References | Bilgisayar İşletim Sistemleri, Ali Saatçi, 2. Baskı, Bıçaklar Kitabevi. Modern Operating Systems, Andrew Tanenbaum, 3rd edition,Pearson Education. Operating System Design, Avi Silberschatz, Peter Baer Galvin, Greg Gagne, 8th edition, John Wiley & Sons, Inc. | |||||
Course outline weekly
| Weeks | Topics |
|---|---|
| Week 1 | Basic operating system concepts |
| Week 2 | Input/Output subsytem |
| Week 3 | Processes, Process queues, Process scheduling |
| Week 4 | fork(), exec() calls, Threads |
| Week 5 | Low level synchronization methods, Semaphores |
| Week 6 | High level synchronization methods, pipe() call |
| Week 7 | Primitive memory management methods, Paged memory management |
| Week 8 | Virtual memory management, Segmented memory management |
| Week 9 | Midterm exam |
| Week 10 | File/directory concept, Primitive file management systems, MS-DOS FAT, |
| Week 11 | UNIX file management system, Backup methods, RAID systems |
| Week 12 | TCP/IP network infrastructure |
| Week 13 | Connection-oriented and connectionless communication, Socket programming |
| Week 14 | Introduction to operating system security, Malwares, Protection mechanisms |
| Week 15 | Preparation to Final Exam |
| Week 16 | Final exam |
Assesment methods
| Course activities | Number | Percentage |
|---|---|---|
| Attendance | 0 | 10 |
| Laboratory | 0 | 0 |
| Application | 0 | 0 |
| Field activities | 0 | 0 |
| Specific practical training | 0 | 0 |
| Assignments | 3 | 15 |
| Presentation | 0 | 0 |
| Project | 0 | 0 |
| Seminar | 0 | 0 |
| Midterms | 1 | 30 |
| Final exam | 1 | 45 |
| Total | 100 | |
| Percentage of semester activities contributing grade succes | 0 | 55 |
| Percentage of final exam contributing grade succes | 0 | 45 |
| Total | 100 | |
WORKLOAD AND ECTS CALCULATION
| Activities | Number | Duration (hour) | Total Work Load |
|---|---|---|---|
| Course Duration (x14) | 14 | 3 | 42 |
| Laboratory | 0 | 0 | 0 |
| Application | 0 | 0 | 0 |
| Specific practical training | 0 | 0 | 0 |
| Field activities | 0 | 0 | 0 |
| Study Hours Out of Class (Preliminary work, reinforcement, ect) | 14 | 5 | 70 |
| Presentation / Seminar Preparation | 0 | 0 | 0 |
| Project | 0 | 0 | 0 |
| Homework assignment | 3 | 12 | 36 |
| Midterms (Study duration) | 1 | 12 | 12 |
| Final Exam (Study duration) | 1 | 20 | 20 |
| Total Workload | 33 | 52 | 180 |
Matrix Of The Course Learning Outcomes Versus Program Outcomes
| D.9. Key Learning Outcomes | Contrubition level* | ||||
|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | |
| 1. Has comprehensive knowledge in fundamental areas of software engineering. | X | ||||
| 2. Has knowledge in the area of software requirements understanding process planning, output specification, resource planning, risk management and quality planning. | X | ||||
| 3. Understands the interplay between theory and practice and the essential links between them. | X | ||||
| 4. Defines real life problems by identifying functional and non-functional requirements a software has to satisfy. | X | ||||
| 5. Overcomes technical or scientific software engineering problems on their own and is in a position to propose the most suitable solution; has good communication skills to explain the completeness of their solution and clearly state the assumptions that were made. | X | ||||
| 6. Completes a project on a larger scale than an ordinary course project in order to acquire the skills necessary to work efficiently in a team. | X | ||||
| 7. Identifies, evaluates, measures and manages changes in software development by applying software engineering processes. | X | ||||
| 8. Understands the social, legal, ethical and cultural issues involved in the deployment and use of software engineering and conducts all occupational pursuits in an ethical and responsible manner. | X | ||||
| 9. Has good command of technical terms in both Turkish and English, where they have the ability to make succinct presentations (including face-to-face, written or electronic) to a range of audiences about technical/scientific problems and their solutions. | X | ||||
| 10. Identifies and conducts research by applying scientific methods in order to solve scientific problems. | X | ||||
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest