Week |
Subject |
Related Preparation |
1) |
Introduction to technological innovations and industrial strategy |
None |
2) |
Clusters and industries |
Instructor's notes |
3) |
High-tech clusters and competitiveness |
Instructor's notes |
4) |
Systems of innovation |
Instructor's notes |
5) |
National system of innovation |
Instructor's notes |
6) |
Sectoral innovation management |
Instructor's notes |
7) |
Regional systems of innovation |
Instructor's notes |
8) |
Midterm exam |
Preparation for midterm exam |
9) |
Technology transfer |
Instructor's notes |
10) |
Networks: why firms enter into innovation networks |
Instructor's notes |
11) |
Technology and firm networks |
Instructor's notes |
12) |
Network structures |
Instructor's notes |
13) |
Course project presentations |
Preparation for project presentations |
14) |
Course project presentations |
Preparation for project presentations |
Course Notes / Textbooks: |
Ders notları ve sunumlar.
Fagerberg, J., Mowery, D.C. & Nelson, R.R. (2006). Oxford Handbook of Innovation, Oxford University Press, NY. |
References: |
Porter, M. (1998). Clusters and the new economics of competition
Saxenian, AL. (1994). Regional advantage: culture and competition at Silicon Valley and Route 128
Lundvall, BA. (1992). National Systems of Innovation: Toward a Theory of Innovation and Interactive Learning .
Edquist, C. (1997). Systems of Innovation: Technologies, Institutions and Organizations |
|
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. |
|