|
Week |
Subject |
Related Preparation |
1) |
General definition and aspects of Turkish oral narrative |
|
2) |
The definitions and aspects of tales and legends |
|
3) |
The comparative aspects of Turkish folktales and world folk tales |
|
4) |
Message-index of tales |
|
5) |
Motif-index of legends |
|
6) |
The example of adaptation of motif-index of narratives |
|
7) |
The example of adaptation of motif-index of narratives |
|
8) |
The example of adaptation of motif-index of legends |
|
9) |
The example of adaptation of motif-index of legends |
|
10) |
The linguistic aspects of narratives |
|
11) |
The reflections of the linguistic aspects of narratives in daily life |
|
12) |
The analyze of narratives |
|
13) |
The analyze of tales |
|
14) |
The analyze of legends |
|
15) |
Final Exam |
|
16) |
Final Exam |
|
Course Notes: |
- |
References: |
-Masallar ve Eğitimsel İşlevleri-Mesaj Index, Muhsine Helimoğlu Yavuz, 5. Baskı Cumhuriyet Kitapları Yayınları, İst. 2009
-Diyarbakır Efsaneleri-Motif Index, Muhsine Helimoğlu Yavuz, 4. Baskı Cumhuriyet Kitapları Yayınları, İst. 2007
-“Mit-Din-Gelenek Aynasında Kadın”, Muhsine Helimoğlu Yavuz, Folklor-Edebiyat C.10, S. 37
-Evvel Zaman İçinde-Anadolu Masalları-1, Muhsine Helimoğlu Yavuz, Can Yay. 2011
-Gel Zaman Git Zaman-Anadolu Masalları-2, Muhsine Helimoğlu Yavuz, Can Yay. 2011
-Zaman Zaman İçinde-Anadolu Masalları-3, Muhsine Helimoğlu Yavuz, Can Yay. 2011
|
|
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. |
|