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 |
ISL5956 | Organizational Development and Change | 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 : | |
Course Lecturer(s): |
Dr. İBRAHİM AYHAN TON Assoc. Prof. HAKKI AKTAŞ |
Recommended Optional Program Components: | None |
Course Objectives: | The purpose of this course, is to understand the definitions of "change" and "improvement" to develop the performance and the dynamics of an organization. Moreover, the concept of "organizational learning" which is the keystone of the organizational development and change will be emphasized. |
The students who have succeeded in this course; The students who succeeded in this course; - will be able to recognize why change is important for organizations - will be able to gain knowledge about learning organizations - will be able to gain knowledge about organizational development. - will be able to define resistance to organizational change. - will be able to find solutions to resistance to change problems. |
More and more organizations today face a dynamic and changing environment. This, in turn, is requiring the organizations to adapt. “Change or die!” is the rallying cry among today’s managers worldwide. Change types, process, the resistance to change and overcoming resistance to change, methods of organizational development, challenges and opportunities of the future are the subjects that we will discuss in class. |
Week | Subject | Related Preparation |
1) | ||
2) | ||
3) | ||
4) | ||
5) | ||
6) | ||
7) | ||
8) | ||
9) | Midterm Exam | |
10) | ||
11) | ||
12) | ||
13) | ||
14) | ||
15) | Final Exam |
Course Notes / Textbooks: | Örgütsal Davranış alanındaki doktora yıllarından bugüne çeşitli kitaplardan oluşturulmuş ders notları ve makaleler, işdünyasındaki 20 yıllık deneyimden gelen uygulama bilgisi |
References: | Stephen Robbins, Timothy Judge, OB, Pearson-Prentice Hall, 2011 |
Semester Requirements | Number of Activities | Level of Contribution |
Attendance | 14 | % 10 |
Project | 1 | % 20 |
Midterms | 1 | % 30 |
Final | 1 | % 40 |
Total | % 100 | |
PERCENTAGE OF SEMESTER WORK | % 40 | |
PERCENTAGE OF FINAL WORK | % 60 | |
Total | % 100 |
Activities | Number of Activities | Workload |
Course Hours | 14 | 42 |
Application | 13 | 48 |
Study Hours Out of Class | 14 | 81 |
Midterms | 1 | 2 |
Final | 1 | 2 |
Total Workload | 175 |
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. |