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 |
IF4420 | Mergers and Acquisitions | Fall | 3 | 0 | 3 | 9 |
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 BAHAR KÖSEOĞLU |
Course Lecturer(s): |
Dr. Öğr. Üyesi UMUT UĞURLU Prof. Dr. İPEK ALTINBAŞAK FARİNA |
Recommended Optional Program Components: | None |
Course Objectives: | This course aims at providing students an analytical and theoretical framework to understand the M&A process and will also use cases and real-world applications to develop skills necessary to evaluate and implement a transaction. |
The students who have succeeded in this course; The student who successfully completes this course; I. will have a thorough knowledge of the value drivers of a company II.Will be able to assess a company within the context of its competitive advantage and the industry it operates in III.Will learn the process of M&A of a company IV.Will know the difference of the M&A process from the buyer or seller perspectives V.Be able to do basic company valuation VI Have an insight to the participants of the M&A process, negotiation process and the legal documents involved in M&A process. |
Valuation, valuation techniques, M&A process, Negotiations |
Week | Subject | Related Preparation |
1) | Why companies are bought or sold? | |
2) | Why the industry in which the company operates is important? Hence industry analysis | |
3) | What make the medium and small companies differ from the big ones | |
5) | Valuation II | |
5) | What are the value drivers of a company? | |
6) | Valuation II | |
7) | Most used valuation techniques | |
8) | Other valuation techniques | |
9) | M&A process | |
10) | M&A milestones | |
11) | Negotiation I | |
12) | Negotiation II | |
13) | Due diligence | |
14) | Wrap up |
Course Notes / Textbooks: | Mergers & Acquisitions ,A. Sherman and Milledge Hart (2006), Investment Valuation, Aswath Damodaran (2002) |
References: | Yok / None |
Semester Requirements | Number of Activities | Level of Contribution |
Homework Assignments | 1 | % 20 |
Midterms | 1 | % 35 |
Final | 1 | % 45 |
Total | % 100 | |
PERCENTAGE OF SEMESTER WORK | % 55 | |
PERCENTAGE OF FINAL WORK | % 45 | |
Total | % 100 |
Activities | Number of Activities | Duration (Hours) | Workload |
Course Hours | 14 | 3 | 42 |
Study Hours Out of Class | 14 | 4 | 56 |
Homework Assignments | 1 | 35 | 35 |
Midterms | 1 | 40 | 40 |
Final | 1 | 45 | 45 |
Total Workload | 218 |
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. |