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
COP4431	Abdi İbrahim Special Topics in Project Management	Fall	3	0	3	6

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 :
Recommended Optional Program Components:	None
Course Objectives:	This course focuses on the Project Management (PM) proccesses and key PM knowledge areas. The students develop the ability to manage the progressive maturity model of a project life-cycle independently from any industry.

Learning Outcomes

The students who have succeeded in this course;
The learner will be able to;
1. define different project management methodologies and techniques
2. justify if an idea is a commercial/ strategic opportunity and convert the idea into an official business case document
3. classify projects with multiple parameters and will be able to bring different approaches according to project categories
4. develop a commercial look on contracting processes
5. apply different risk management techniques
6. apply different communication, negotiation and conflict management techniques
7. criticise ideas and lessons learned from real project managers' experiences
8. define Agile Project Management Methodology

Course Content

This course on Project Management focuses on Project Management Methodologies, Idea Management, and Project Classification and Prioritization for finding the right PM Tools. Contracting, Risk Management, Project Communication, Schedule Optimization, and Agile/ Scrum Methodology are other topics covered.

Weekly Detailed Course Contents

Week	Subject	Related Preparation
1)	Introduction to Project Management
2)	Project Management Methodologies
3)	Idea Management
4)	Project Classification and Prioritization
5)	Finding the right PM Tool
6)	Contracting
7)	Review of PM Concepts, MidTerm
8)	Risk Management
9)	Advanced Project Communication
10)	Time Schedule Optimization
11)	Failure Stories and Lessons Learned
12)	Applied Agile/ Scrum Methodology
13)	Student Project Presentations
14)	student Project Presentations

Sources

Course Notes / Textbooks:	The ISPE Good Practice Guide: Project Management for Pharmaceutical Industry. J. Angelastro, D. Barlow, J. H. Butler, N. C. Davies, S. Errico, R. Gunderlock, J. Honey, L. Hura, S. Kelly, D. Koncak, K. Lamson, P. Loxley, C. McCann, K. O’Donnell, J. Phelan, R. H. Scherzer, W. Shelden, G. Spanel, M. Stefanowicz, M. Theobald, I. Thorne, 2011.
References:	A Guide To The Project Management Body of Knowledge. PMI (Project Management Institute), 2013. Birleşik Standartlar Sözlüğü. PROJE YÖNETİM MESLEGİ İLKELERi TEKNİKLERİ VE ROTASI DERNEGİ (PMİ TR), 2009.

Evaluation System

Semester Requirements	Number of Activities	Level of Contribution
Project	1	% 30
Midterms	1	% 30
Final	1	% 40
Total		% 100
PERCENTAGE OF SEMESTER WORK		% 30
PERCENTAGE OF FINAL WORK		% 70
Total		% 100

ECTS / Workload Table

Activities	Number of Activities	Duration (Hours)	Workload
Course Hours	14	3	42
Study Hours Out of Class	14	3	42
Project	1	50	50
Midterms	1	2	2
Final	1	2	2
Total Workload			138

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.