SOFTWARE ENGINEERING
Bachelor	TR-NQF-HE: Level 6	QF-EHEA: First Cycle	EQF-LLL: Level 6

Course Introduction and Application Information

Course Code	Course Name	Semester	Theoretical	Practical	Credit	ECTS
ISM5211	Technology Management	Spring	3	0	3	12

This catalog is for information purposes. Course status is determined by the relevant department at the beginning of semester.

Basic information

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 :	Dr. Öğr. Üyesi ALPER CAMCI
Recommended Optional Program Components:	None
Course Objectives:	This course is designed to lead the student to understand the importance and the nature of technological innovations, how they are integrated into business level strategies and how technological innovation process is managed. In this course, the aim is not only to understand the theories of technological innovations but also to discuss the practice of technological innovation. Therefore case studies are important; most of the theoretical parts are followed by case studies.

Learning Outcomes

The students who have succeeded in this course;
After finished this course students are expected to be able to
* develop an awareness of the scope and complexity of technological innovations and issues in management of technology.
* explain some main concepts such as types of innovation, open innovation, product life cycle; technology life cycle; dominant design; path dependency.
* understand the process of creating technological innovations
* be familiar with technological innovation strategy formulation and implementation
* develop a strategic business thinking towards the use of technology in various sectors.
* understand the tools and methods used in management of technology. Some of these tools are integrated into case analyses.

Course Content

Introduction to the management of technological innovations
Sources of innovation
Types and patterns of innovation
Technology life cycle and dominant design
Timing of entry
Integrating technology-innovation strategy to general business strategy
Internal strategy and capabilities for innovation
R&D management
Open innovation, networks and communities
Choosing innovation projects
Protecting innovations
Managing new product development process
Delivering value from innovation, commercialization, technology transfer
Technology management actions and tools

Weekly Detailed Course Contents

Week	Subject	Related Preparation
1)	Overview of some concepts Introduction to the management of technological innovations	Instructor's notes
2)	Sources of technological innovation Types and patterns of innovation	Instructor's notes
3)	Emergence of technology standards, standards battles and dominant design	Instructor's notes
4)	Timing of market entry for technological innovations	Instructor's notes
5)	Defining organization's strategic direction Integrating technology-innovation strategy to general business strategy	Instructor's notes
6)	Internal strategy and capabilities for innovation R&D management	Instructor's notes
7)	External technology-innovation strategy: Open innovation Networks and communities, users	Instructor's notes
8)	Midterm exam	Preparation for midterm exam
9)	Choosing innovation projects Protecting innovations	Instructor's notes
10)	Managing creativity for technological innovations	Instructor's notes
11)	Managing new product development process	Instructor's notes
12)	Delivering value from technological innovation Commercialization, technology transfer	Instructor's notes
13)	Technology management actions, tools and methods	Instructor's notes
14)	Course project presentations	Preparation for project presentations

Sources

Course Notes / Textbooks:	Ders notları ve sunumları
References:	Schilling, Melissa A., Strategic Management of Technological Innovation, McGraw-Hill Irwin, 2010 Frederick Betz (2010) Teknolojik Yenilik Yönetimi. TÜBİTAK Popüler Bilim Kitapları, Ankara.

Evaluation System

Semester Requirements	Number of Activities	Level of Contribution
Presentation	1	% 5
Project	1	% 20
Midterms	1	% 30
Final	1	% 45
Total		% 100
PERCENTAGE OF SEMESTER WORK		% 35
PERCENTAGE OF FINAL WORK		% 65
Total		% 100

ECTS / Workload Table

Activities	Number of Activities	Duration (Hours)	Workload
Course Hours	14	3	42
Study Hours Out of Class	14	5	70
Presentations / Seminar	2	20	40
Project	1	75	75
Midterms	1	32	32
Final	1	32	32
Total Workload			291

Contribution of Learning Outcomes to Programme Outcomes

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.