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 |
PIH5113 | Crisis Communication | Spring | 3 | 0 | 3 | 8 |
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: | Non-Departmental Elective |
Course Level: | Bachelor’s Degree (First Cycle) |
Mode of Delivery: | Face to face |
Course Coordinator : | Prof. Dr. ÇİSİL SOHODOL |
Course Lecturer(s): |
Assoc. Prof. BURCU EKER AKGÖZ Prof. Dr. ÇİSİL SOHODOL |
Recommended Optional Program Components: | None |
Course Objectives: | This course will give the information about the nature and characteristic of negotiation and crises from the level of individual decision-making, the corporation, and the government. Also an introduction to the theoretical and practical literature on crises, their management and prevention methodologies with an emphasis on negotiation strategies will be given. A review of key case studies of crisis management will also be done. |
The students who have succeeded in this course; I. define basic terms of crisis communication II. identify the dimensions of crisis communication III. explain terms of crises IV. define types of crisis V. identify organizational change, total quality management, strategic planning and management VI. analyze the development of crisis communication VII. develop pre-crisis strategies and tactics VIII. develop strategies and tactics for period of crisis and post crisis IX. define the role of pr in crisis communication X. explain the process of crisis communication |
This course will cover the definitions of crisis, the dimensions, types and terminologies will also be covered. Important steps in crisis management will be examined and analyzed. |
Week | Subject | Related Preparation |
1) | What is a Crisis? | |
2) | Conceptual Dimensions of Crises | |
3) | Terms of Crisis | |
4) | Types of Crisis | |
5) | Related Field with Crisis Management | |
6) | Crisis Management Strategy and Models | |
7) | Pre-Crisis Management | |
8) | Period of Crisis and Post-Crisis | |
9) | Crisis and Media | |
10) | Crisis Communication and Public Relations | |
11) | Digital crises | |
12) | Case Studies | |
13) | Case Studies | |
14) | Wrap-up and Disccusion |
Course Notes / Textbooks: | Kaynaklar dönem başlangıcında öğrencilere sağlanacaktır. Course materials will be provided in the beginning of semester. |
References: | Crisis Communication Plan Components and Model: Crisis Communication Management Readliness |
Semester Requirements | Number of Activities | Level of Contribution |
Homework Assignments | 3 | % 30 |
Midterms | 1 | % 30 |
Final | 1 | % 40 |
Total | % 100 | |
PERCENTAGE OF SEMESTER WORK | % 60 | |
PERCENTAGE OF FINAL WORK | % 40 | |
Total | % 100 |
Activities | Number of Activities | Workload |
Course Hours | 14 | 42 |
Homework Assignments | 9 | 45 |
Midterms | 7 | 32 |
Final | 7 | 35 |
Total Workload | 154 |
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. |