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
LOG3711	Logistics Operations Management	Fall	3	0	3	5

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

Basic information

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 :	Prof. Dr. YAVUZ GÜNALAY
Course Lecturer(s):	Dr. Öğr. Üyesi LEVENT AKSOY
Recommended Optional Program Components:	none
Course Objectives:	Students are exposed to different processes seen in logistics operations, and their importance both at the strategic and operational levels. Differences as well as similarities among manufacturing and service operations are discussed. Basic management tools used at the operational level of logistics institutions are presented. Moreover, students are asked to prepare a team project on one of the course topics of their choice.

Learning Outcomes

The students who have succeeded in this course;
I. Be familiar with the basic Operations Management terminology, and describe the similarities and differences of goods and service operations
II. Define Mission-Strategy relationship and describe operations/production strategies.
III. Define logistics operations.
IV. Identify different location and distribution models and compare them.
V. Identify logistics and supply chain networks
VI. Define supply chain and why bullwhip effect occurs.
VII. Define capacity and aware of different capacity management models.
VIII. Be familiar of benefits and risks of inventory and inventory management techniques.
IX. Define waste and lean production.
X. Describe quality and different quality management tools.

Course Content

Description of Operations Management and Operations Strategy. Discussion of basic topics in logistics operations, such as design of supply networks, location and layout, capacity management, inventory management, lean management, and quality.

Weekly Detailed Course Contents

Week	Subject	Related Preparation
1)	What is operations? Importance of Operation Management.
2)	Mission-Goal-Strategy. Operations strategy.	Pre-reading
3)	Performance of operations.	Pre-reading
4)	Design of services and goods.	pre-reading
5)	Process design.	Pre-reading
6)	Decision of location and layout	Pre-reading
7)	Supply chain management.	Pre-reading
8)	Capacity management.	Pre-reading
9)	Review
10)	Inventory management.	Pre-reading
11)	Planning, scheduling and ERP	pre-reading
12)	Lean management.	Pre-reading
13)	Quality management.	Pre-reading
14)	Operations improvement and review

Sources

Course Notes / Textbooks:	Russell and Taylor, Operations Management,: Creating Value along the Supply Chain, 7th Ed., Wiley, 2011. (ISBN:9780470646236)
References:	Stevenson W. L., Operations Management, 9th Ed., McGraw Hill, 2007. Heizer, J, and B. Render, Operations Management, 10h Ed., Pearson Education, 2011. (ISBN:0-13-607366-2)

Evaluation System

Semester Requirements	Number of Activities	Level of Contribution
Attendance	10	% 10
Quizzes	7	% 10
Project	1	% 25
Midterms	1	% 25
Final	1	% 30
Total		% 100
PERCENTAGE OF SEMESTER WORK		% 45
PERCENTAGE OF FINAL WORK		% 55
Total		% 100

ECTS / Workload Table

Activities	Number of Activities	Workload
Course Hours	14	42
Study Hours Out of Class	14	64
Presentations / Seminar	4	12
Midterms	1	2
Final	1	2
Total Workload		122

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.