| 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 |
| COP4481 | Adesso Global Delivery Model | Spring | 3 | 0 | 3 | 6 |
| 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: | Departmental Elective |
| Course Level: | Bachelor’s Degree (First Cycle) |
| Mode of Delivery: | Face to face |
| Course Coordinator : | Assist. Prof. TAMER UÇAR |
| Course Objectives: | The main goal of GDM is to enable project transparency, create a collaborative environment between customer and project teams and to deliver high-quality software, which customer asked for. Teaching Methods and Techniques Used in the Course: Lecture, reading, project, individual study |
|
The students who have succeeded in this course; 1. Acquire information about software project stages from end to end 2. Understand project roles and responsibilities 3. Acquire information about critical factors of project initiation phase 4. Acquire knowledge about change management, risk management, and escalation management plans 5. Analyze the methods for implementing quality control on a Project 6. Acquire information about the necessary meetings and reports in order to monitor the progress of the project. |
| The course introduces students to structured software project management methodologies, emphasizing transparency, collaboration, and quality assurance. Students will explore the phases of aGDM, including project initiation, change management, risk assessment, and escalation management. Practical applications will be reinforced through case studies, quality control methods, and real-world project examples. Agile frameworks, project monitoring techniques, and reporting structures will be covered, equipping students with essential tools for professional project execution. The course fosters a practical understanding of software project management within an interdisciplinary and global framework. |
| Week | Subject | Related Preparation |
| 1) | Introduction to aGDM | |
| 2) | Roles and Responsibilities | |
| 3) | aGDM Phases | |
| 4) | Change Management, Risk Management, Issue Management | |
| 5) | Smart Start | |
| 6) | Project Example - I | |
| 7) | Project Example - II | |
| 8) | Midterm | |
| 9) | Agile Quality Gates | |
| 10) | Meetings - I | |
| 11) | Meetings - II | |
| 12) | Reporting | |
| 13) | Test Approach | |
| 14) | Release Management |
| Course Notes / Textbooks: | Service Delivery Models A Complete Guide, Gerardus Blokdyk (ISBN-13: 978-0655846840) |
| References: |
| Semester Requirements | Number of Activities | Level of Contribution |
| Project | 1 | % 40 |
| Midterms | 1 | % 20 |
| Final | 1 | % 40 |
| Total | % 100 | |
| PERCENTAGE OF SEMESTER WORK | % 20 | |
| PERCENTAGE OF FINAL WORK | % 80 | |
| Total | % 100 | |
| 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. |