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 SUNA ÇAĞAPTAY |
Course Lecturer(s): |
Instructor ASLI VARON
Dr. Öğr. Üyesi GÖKSUN AKYÜREK ALTÜRK
Dr. Öğr. Üyesi SUNA ÇAĞAPTAY
|
Recommended Optional Program Components: |
Site and museum visits, in class and on-site lectures |
Course Objectives: |
After dicussing the basic relationship between history and architecture, course aims to identify the formal, functional, spatial, technological and symbolic diversity of architecture, that is mainly a historical, social and cultural realm of production, starting from early ages till the 13th century.
Evaluate architectural products within a wide range of singular building to urban environment, in regard to their distinct and similar characteristics with a comparative perspective, which are produced in different cultural and historical contexts.
|
The students who have succeeded in this course;
Understanding of parallel and divergent canons and traditions of architecture, landscape and urban design including examples of indigenous, vernacular, local, regional, national settings from the Eastern, Western, Northern, and Southern hemispheres in terms of their climatic, ecological, technological, socioeconomic, public health, and cultural factors.
Understanding of the diverse needs, values, behavioural norms, physical abilities, and social and spatial patterns that characterize different cultures and individuals and the implication of this diversity on the societal roles and responsibilities of architects.
|
Week |
Subject |
Related Preparation |
1) |
Introduction: Why do we study architectural history? What is history? In what ways is it related to architecture? How do we record and evaluate them in a historical perspective? |
|
2) |
1st cities—Fertile Crescent, Sumer, India, Harappa, Jericho
small settlements everywhere, the village as the human habitation
|
Trachtenberg, Ch 1, pp: 76-84. |
3) |
Of Kings and Pharaohs: Egypt |
Trachtenberg, Ch 1, pp: 62-76 |
4) |
The Greek City: Athens |
Trachtenberg, Ch 2, pp: 90-107. |
5) |
The City Assembled: Hellenistic City Culture |
Trachtenberg, Ch 2, pp: 109-114. |
6) |
The Roman City: From Republic to Empire
Roman Empire: Asia Minor and Beyond |
Trachtenberg, Ch 3, pp:120-149. |
7) |
MIDTERM |
|
8) |
The Christian City: Early Byzantine City in Asia Minor,
Italy and the Near East
|
Trachtenberg, Ch 4, pp: 161-176. |
9) |
Middle and Late Byzantine Architecture in Constantinople and the Provinces
|
R. Ousterhout, ‘An Apologia for Byzantine Architecture,’ Gesta 35 (1996): 21-33.
|
11) |
Islamic Cities and Landscapes: Damascus, Baghdad |
D. Fairchild Ruggles, Islamic Gardens and Landscapes, Ch 1.
|
12) |
Islamic Cities and Landscapes: Cairo, Isfahan, Konya |
D. Fairchild Ruggles, Islamic Gardens and Landscapes, Ch 2. |
13) |
Medieval Cities: the Romanesque |
Trachtenberg, Ch 5, pp: 185-190 |
14) |
Medieval Cities: the Gothic |
Trachtenberg, Ch 5, pp: 185-190; Ch 7, pp: 222-245. |
|
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. |
|