SOFTWARE ENGINEERING | |||||
Bachelor | TR-NQF-HE: Level 6 | QF-EHEA: First Cycle | EQF-LLL: Level 6 |
Course Code | Course Name | Semester | Theoretical | Practical | Credit | ECTS |
CMP3001 | Operating Systems | Spring | 3 | 0 | 3 | 6 |
This catalog is for information purposes. Course status is determined by the relevant department at the beginning of semester. |
Language of instruction: | English |
Type of course: | Non-Departmental Elective |
Course Level: | Bachelor’s Degree (First Cycle) |
Mode of Delivery: | Face to face |
Course Coordinator : | Dr. Öğr. Üyesi TARKAN AYDIN |
Course Lecturer(s): |
Dr. Öğr. Üyesi TARKAN AYDIN |
Recommended Optional Program Components: | None |
Course Objectives: | This course is a core course on one of the pillars of computer systems: Operating Systems (OS). The course will make the student appreciate things he takes for granted such as process management, file systems, and so on. It will also help him/her make an entry into the domains of efficient use of OSes and OS design. |
The students who have succeeded in this course; 1. Be able to understand importance of Operating System as a resource management tool 2. Become familiar with the mechanics of processes and threads 3. Be able to understand memory management details of OS 4. Be able to understand file systems 5. Be able to use input and output 6. Be able to understand deadlocks, and avoiding deadlocks |
1.History of Operating Systems, Introduction to Operating Systems 2.Processes and Threads 3.Memory Management 4.File Systems 5.Input Output 6.Deadlocks |
Week | Subject | Related Preparation |
1) | History of Operating Systems, Introduction to Operating Systems | None |
2) | Processes and Threads | None |
3) | Processes and Threads (cont.) | None |
4) | Memory Management | None |
5) | Midterm 1 | Study all the topics covered so far |
6) | Memory Management (cont) | None |
7) | Memory Management (cont) | None |
8) | File Systems (cont) | None |
9) | File Systems | None |
10) | Midterm 2 | Study all the topics covered so far |
11) | Input Output | None |
12) | Input Output (cont) | None |
13) | Deadlocks | None |
14) | Deadlocks | None |
Course Notes / Textbooks: | Operating System Concepts Abraham Silberschatz (Author), Peter B. Galvin (Author), Greg Gagne (Author) |
References: | Andrew S. Tanenbaum, Modern Operating Systems, (3rd Edition), 2007, Prentice Hall |
Semester Requirements | Number of Activities | Level of Contribution |
Quizzes | 8 | % 20 |
Project | 1 | % 10 |
Midterms | 1 | % 30 |
Final | 1 | % 40 |
Total | % 100 | |
PERCENTAGE OF SEMESTER WORK | % 50 | |
PERCENTAGE OF FINAL WORK | % 50 | |
Total | % 100 |
Activities | Number of Activities | Duration (Hours) | Workload |
Course Hours | 14 | 3 | 42 |
Study Hours Out of Class | 14 | 2 | 28 |
Project | 1 | 10 | 10 |
Quizzes | 8 | 1 | 8 |
Midterms | 1 | 25 | 25 |
Final | 1 | 35 | 35 |
Total Workload | 148 |
No Effect | 1 Lowest | 2 Low | 3 Average | 4 High | 5 Highest |
Program Outcomes | Level of Contribution | |
1) | Be able to specify functional and non-functional attributes of software projects, processes and products. | |
2) | Be able to design software architecture, components, interfaces and subcomponents of a system for complex engineering problems. | |
3) | Be able to develop a complex software system with in terms of code development, verification, testing and debugging. | |
4) | Be able to verify software by testing its program behavior through expected results for a complex engineering problem. | |
5) | Be able to maintain a complex software system due to working environment changes, new user demands and software errors that occur during operation. | |
6) | Be able to monitor and control changes in the complex software system, to integrate the software with other systems, and to plan and manage new releases systematically. | |
7) | Be able to identify, evaluate, measure, manage and apply complex software system life cycle processes in software development by working within and interdisciplinary teams. | |
8) | Be able to use various tools and methods to collect software requirements, design, develop, test and maintain software under realistic constraints and conditions in complex engineering problems. | |
9) | Be able to define basic quality metrics, apply software life cycle processes, measure software quality, identify quality model characteristics, apply standards and be able to use them to analyze, design, develop, verify and test complex software system. | |
10) | Be able to gain technical information about other disciplines such as sustainable development that have common boundaries with software engineering such as mathematics, science, computer engineering, industrial engineering, systems engineering, economics, management and be able to create innovative ideas in entrepreneurship activities. | |
11) | Be able to grasp software engineering culture and concept of ethics and have the basic information of applying them in the software engineering and learn and successfully apply necessary technical skills through professional life. | |
12) | Be able to write active reports using foreign languages and Turkish, understand written reports, prepare design and production reports, make effective presentations, give clear and understandable instructions. | |
13) | Be able to have knowledge about the effects of engineering applications on health, environment and security in universal and societal dimensions and the problems of engineering in the era and the legal consequences of engineering solutions. |