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 : |
Dr. Öğr. Üyesi CEMAL OKAN ŞAKAR |
Course Lecturer(s): |
Prof. Dr. TAŞKIN KOÇAK
Dr. Öğr. Üyesi CEMAL OKAN ŞAKAR
|
Recommended Optional Program Components: |
None |
Course Objectives: |
The students will take lectures from senior executives from IBM. Each lecture will focus on a different subject and the lecturer will share his/her own experiences together with the theoretical basis of the subject.
The courses will include Business Analytics & Big Data capabilities and service areas including key concepts, services, IBM software, hardware offerings and IBM assets. In addition, industry use cases are used to illustrate effective use of Big Data services. The courses will help students to prepare for a successful professional career. |
Week |
Subject |
Related Preparation |
1) |
Big Data & Analytics for Better Business Outcomes |
|
2) |
Industry Aligned Big Data, Top Use Cases |
|
3) |
Overview of Big Data Technology & IBM Big Data Platform |
|
4) |
IBM Big Data Platform, Data Explorer |
|
5) |
Data Warehousing |
|
6) |
Information Integration, Master Data Management, Guardium, OPTIM |
|
7) |
Hadoop Technology |
|
8) |
Midterm |
|
9) |
Master Data Management for Customer |
|
10) |
Integrating Unstructured Data in the Enterprise |
|
11) |
Text Analytics |
|
12) |
Infrastructure for Big Data & Analytics |
|
13) |
Infrastructure for Big Data & Analytics |
|
14) |
Recap |
|
|
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. |
|