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 |
GEP0810 | Systems-Design Thinking and Management | Fall | 3 | 0 | 3 | 4 |
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: | GE-Elective |
Course Level: | Bachelor’s Degree (First Cycle) |
Mode of Delivery: | Face to face |
Course Coordinator : | Dr. BURCU ALARSLAN ULUDAŞ |
Course Lecturer(s): |
Dr. Öğr. Üyesi MEHMET DEĞİRMENCİ Dr. BURCU ALARSLAN ULUDAŞ |
Recommended Optional Program Components: | None |
Course Objectives: | Attendants will be informed about; thinking process, method, methodology, holistic thinking, design thinking and designing purposfull systems. |
The students who have succeeded in this course; At the end of the course attendants will be informed about: -Thinking process -Problem formulation -How to answer why, how and what questions? -The concepts of feedback, chaos, and complexity -The difference between mindless and minded systems. -Design thinking. -Interactive planning -Decision support systems |
Thinking process, systems thinking,chaos and complexity, methodology,socio-cultural systems, iterative process of inquiry, design thinking, interactive planning,decision support systems |
Week | Subject | Related Preparation |
1) | Thinking process: dreaming, metaphor, inquaiy, paradigm, environment | Text |
2) | How to answer what, how and why questions. Reductionist and holistic approaches | Text |
3) | Systems thinking: definition of systems and the implications of definitions for real life problems | Text |
4) | Systems principals | Text |
5) | Theory of chaos and complexity | Text |
6) | Socio-cultural systems | Text |
7) | General review | Text |
8) | Midterm exam | |
9) | İterative holistic inquiry | Text |
10) | Design thinking | Text |
11) | Idealized design | Text |
12) | Interactive planning | Text |
13) | Case study | Text |
14) | Desicion support systems | Text |
Course Notes / Textbooks: | DEĞİRMENCİ, M.(2007) Amaçlı canlılar:yönetimde üçüncü nesil sistem düşüncesi, İstanbul, Hiperlink |
References: | CAPRA, F. (1996) Yaşamın örgüsü : zihin ve maddenin yeni bir örgüsü, (çev. B. KURYEL).İstanbul, Yapı Merkezi. MORGAN, G. (1997) Yönetim ve örgüt teorilerinde metafor, (çev.G. BULUT). İstanbul, MESS. ACKOFF, R.L. (1999) Re-Creating the corporation : a design of organizations for the 21st centuary. New York, Oxford University Press. GHARAJEDAGHI, J. (2011) Systems thinking : managing chaos and complexity: a platform for designing business architecture. Burlington, Morgan kaufmann. |
Semester Requirements | Number of Activities | Level of Contribution |
Attendance | 14 | % 10 |
Midterms | 1 | % 40 |
Final | 1 | % 50 |
Total | % 100 | |
PERCENTAGE OF SEMESTER WORK | % 50 | |
PERCENTAGE OF FINAL WORK | % 50 | |
Total | % 100 |
Activities | Number of Activities | Duration (Hours) | Workload |
Course Hours | 14 | 3 | 42 |
Midterms | 1 | 24 | 24 |
Final | 1 | 30 | 30 |
Total Workload | 96 |
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. |