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 |
GEP1640 | Towards Zero Hunger (SDG 2) | Fall Spring |
3 | 0 | 3 | 5 |
This catalog is for information purposes. Course status is determined by the relevant department at the beginning of semester. |
Language of instruction: | Turkish |
Type of course: | GE-Elective |
Course Level: | Bachelor’s Degree (First Cycle) |
Mode of Delivery: | Hybrid |
Course Coordinator : | Assist. Prof. MÜGE KESİCİ |
Recommended Optional Program Components: | yok |
Course Objectives: | The aim of this course is to provide students with information about the green transition within the scope of the European Green Deal by conveying basic concepts such as food waste, agricultural production systems, food security and poverty from the production of food. |
The students who have succeeded in this course; 1. Gain information about agriculture history. 2. Comprehend the contribution of food safety to the world development. 3. Learn about poverty. 4. Learn examples in food right. 5. Understand the relationship between agriculture and food security. 6. Gain knowledge about sustainable agriculture. 7. Learn European Green Deal, green transition and etc. |
Students who responsible the course are expected to follow the course in MSTeams during the course hours. Students who have questions can have either an online or a face-to-face meeting with the instructor during the office hours. The teaching method of the course is lecture. Project assignments (in the form of a case study) given at the beginning of the semester will be given to students individually as oral presentations in the last two weeks of the semester. |
Week | Subject | Related Preparation |
1) | Introduction to the course | yok |
2) | Brief history of agriculture and revolutions | yok |
3) | What is F2F strategy? | yok |
4) | World hunger and poverty | yok |
5) | Agricultural production systems | yok |
6) | Transition to sustainable agriculture | yok |
7) | Paradigm for zero hunger | yok |
8) | Mid-term exam | yok |
9) | Food security | yok |
10) | Global climate change effect on agriculture | yok |
11) | Technology impact to achieve zero hunger | yok |
12) | European green deal | yok |
13) | Student assignment presentations | yok |
14) | Student assignment presentations | yok |
Course Notes / Textbooks: | FAO, The Future of Food and Agriculture: Trends and Challenges, 2017. Bilimsel makaleler |
References: | FAO, The Future of Food and Agriculture: Trends and Challenges, 2017. Scientific papers |
Semester Requirements | Number of Activities | Level of Contribution |
Presentation | 1 | % 20 |
Midterms | 1 | % 30 |
Final | 1 | % 50 |
Total | % 100 | |
PERCENTAGE OF SEMESTER WORK | % 50 | |
PERCENTAGE OF FINAL WORK | % 50 | |
Total | % 100 |
Activities | Number of Activities | Duration (Hours) | Workload |
Course Hours | 13 | 3 | 39 |
Study Hours Out of Class | 12 | 4 | 48 |
Presentations / Seminar | 2 | 10 | 20 |
Homework Assignments | 1 | 10 | 10 |
Midterms | 1 | 2 | 2 |
Final | 1 | 2 | 2 |
Total Workload | 121 |
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. | 4 |
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. | 3 |
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. | 3 |