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 |
INT4921 | Design Semiotics | 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 : | Assoc. Prof. SEZİN HATİCE TANRIÖVER |
Course Lecturer(s): |
Assoc. Prof. SEZİN HATİCE TANRIÖVER |
Recommended Optional Program Components: | None |
Course Objectives: | This course aims to make students able to use knowledge of basic semiotics as a tool in designing process and as a method for the analysis and evaluations of the interior architectural projects. |
The students who have succeeded in this course; I. Determining the parts constituting the structure of meaning II. Defining the relations between design and meaning III. Understanding of the basic components of Semiotics and by means of this, ability of analysing of products in various disciplines of design IV. Establishing spatial equivalences of the components of basic Semiotics V. Determining, interpreting and using of multi-leveled meanings in design. |
1.Introductıon ‘Design as Communication’ Movie and discussion 2.‘Design as Communication’ ‘Parts of Meaning Production: Sender-receiver 3.‘Design as Communication’ ‘Parts of Meaning Production: Massage – (signifier / sign / signified) (Movie:Limits of Control / Jim Jarmusch) 4.‘Design as Communication’ ‘Parts of Meaning Production: Code Movie and Discussion 5.‘Design as Communication’ ‘Parts of Meaning Production: Context 6.‘Design as Communication’ ‘Parts of Meaning Production: Channel Reading and Discussion 7‘Design as Communication’ ‘Parts of Meaning Production: Medium 8. Interpretations: ‘Design as Text’Concept 9. Interpretations: ‘Design as Text’Concept 10. Interpretations of Architectural SpaceConcept 11. Interpretations of Architectural Space Individual Researches and Presentations 12. Interpretations of Architectural Space Individual Researches and Presentations 13. Interpretations of Architectural Space Individual Researches and Presentations 14. Review |
Week | Subject | Related Preparation |
1) | Introductıon ‘Design as Communication’ Movie and discussion | |
2) | ‘Design as Communication’ ‘Parts of Meaning Production: Sender-receiver | |
3) | ‘Design as Communication’ ‘Parts of Meaning Production: Massage – (signifier / sign / signified) (Movie:Limits of Control / Jim Jarmusch) | |
4) | ‘Design as Communication’ ‘Parts of Meaning Production: Code Movie and Discussion | |
5) | ‘Design as Communication’ ‘Parts of Meaning Production: Context | |
6) | ‘Design as Communication’ ‘Parts of Meaning Production: Channel Reading and Discussion | |
7) | ‘Design as Communication’ ‘Parts of Meaning Production: Medium | |
8) | Interpretations: ‘Design as Text’Concept | |
9) | Interpretations: ‘Design as Text’ Concept | |
10) | Interpretations of Architectural Space Concept | |
11) | Interpretations of Architectural Space Individual Researches and Presentations | |
12) | Interpretations of Architectural Space Individual Researches and Presentations | |
13) | Interpretations of Architectural Space Individual Researches and Presentations | |
14) | Review |
Course Notes / Textbooks: | Chandler, Daniel. 2002. Semiotics: The Basics New York: Routledge / Barnard, Malcolm. 1996. Fashion as Communication. London: Routledge. |
References: | Chandler, Daniel. 2002. Semiotics: The Basics New York: Routledge / Barnard, Malcolm. 1996. Fashion as Communication. London: Routledge. |
Semester Requirements | Number of Activities | Level of Contribution |
Attendance | 14 | % 5 |
Presentation | 1 | % 15 |
Project | 1 | % 15 |
Midterms | 1 | % 25 |
Final | 1 | % 40 |
Total | % 100 | |
PERCENTAGE OF SEMESTER WORK | % 45 | |
PERCENTAGE OF FINAL WORK | % 55 | |
Total | % 100 |
Activities | Number of Activities | Duration (Hours) | Workload |
Course Hours | 14 | 3 | 42 |
Study Hours Out of Class | 14 | 1 | 14 |
Presentations / Seminar | 2 | 4 | 8 |
Project | 3 | 4 | 12 |
Midterms | 1 | 12 | 12 |
Final | 1 | 12 | 12 |
Total Workload | 100 |
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. |