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 |
ARC3963 | Urban History | Fall | 2 | 0 | 2 | 4 |
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 NESLİHAN AYDIN YÖNET |
Course Lecturer(s): |
Dr. Öğr. Üyesi NESLİHAN AYDIN YÖNET |
Recommended Optional Program Components: | None |
Course Objectives: | The aim of this course is to develop students' knowledge of theories and the history of urban development. |
The students who have succeeded in this course; -Understanding urban/city typologies of different historical periods -Comprehension of the impact of social and cultural changes on urban space in specific historical periods. - Understanding the relationship between human behavior, the natural environment, and the design of the built environment. - Effective reading, writing, speaking, and listening skills. |
The course explores the social, cultural, economical, environmental factors that shape cities. The ideas, theories, and innovations that create unique aspects of cities are discussed through examples from past, present, and future. The examples from the periods of Ancient Greek, Roman, Renaissance, Baroque, Modern, and Post Modern are analyzed. The ideas about futuristic cities are also discussed. |
Week | Subject | Related Preparation |
1) | Introduction | |
2) | The Idea of City | |
3) | The Classic City | |
4) | The Medieval Town | |
5) | Renaissance and Baroque Cities | |
6) | Historical Gardens | |
7) | 19th Century City | |
8) | 20th Century City | |
9) | 21st Century City | |
10) | MIDTERM | |
11) | Looking into the Future | |
12) | Student Presentations and Discussion | |
13) | Student Presentations and Discussion | |
14) | Evaluation / Final Discussion |
Course Notes / Textbooks: | - |
References: | . Mumford, L. (1961) The City in History. Harcourt, New York . . Bacon, E. (1976) Design of Cities. Penguin Books, New York. . Gallion, E. (1975) The Urban Pattern. D.Van Nostrand Co. New York. . Kostof, S. (2004) The City Shaped: Urban Patterns and Meanings Through History. Bullfinch Press, New York. . Benevolo, L. (1995) The European City. Blackwell Pub. Oxford , UK and Cambridge, Massachusetts, USA. . Ellin, N. (2007) Postmodern Urbanism: Revised Edition. Princeton Architectural Press, New York. . Hall, P. (2014) Cities of Tomorrow: An Intellectual History of Urban Planning and Design Since 1880, Fourth Edition. Wiley Blackwell, USA and UK. . Brenner, N. and Keil, R. (Editors) (2006) The Global Cities Reader (Urban Reader Series). Routledge Taylor&Francis Group, London and New York. |
Semester Requirements | Number of Activities | Level of Contribution |
Attendance | 14 | % 10 |
Presentation | 1 | % 25 |
Midterms | 1 | % 25 |
Final | 1 | % 40 |
Total | % 100 | |
PERCENTAGE OF SEMESTER WORK | % 60 | |
PERCENTAGE OF FINAL WORK | % 40 | |
Total | % 100 |
Activities | Number of Activities | Duration (Hours) | Workload |
Course Hours | 13 | 2 | 26 |
Study Hours Out of Class | 12 | 6 | 72 |
Presentations / Seminar | 2 | 2 | 4 |
Midterms | 1 | 2 | 2 |
Final | 1 | 2 | 2 |
Total Workload | 106 |
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. |