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 |
CMP4502 | Distributed Databases | 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: | Non-Departmental Elective |
Course Level: | Bachelor’s Degree (First Cycle) |
Mode of Delivery: | Face to face |
Course Coordinator : | Dr. Öğr. Üyesi TARKAN AYDIN |
Recommended Optional Program Components: | None |
Course Objectives: | Communication paradigms: client/server protocols, remote procedure call (e.g., Java RMI), multicast protocols handling asynchronous communication and failures. Distributed transaction management requires enhanced concurrency control methods. Comparing algorithms proposed by researchers and commercial solutions. Replicating data to increase fault-tolerance and the performance of databases. |
The students who have succeeded in this course; 1. Be able to understand Distributed computing systems, their characteristics, and desired functionality 2. Become familiar with Distributed computer system models and architectures 3. Be able to understand Synchronization 4. Be able to understand Replication 5. Be able to use distributed naming 6. Be able to understand Fault-tolerance |
1.Introduction 2.DDBMS Architecture 3.Distributed Database Design 4.Semantic Integrity Control 5.Query decomposition and data localization 6.Optimization of Distributed Queries 7.Transactions 8.Concurrency Control 9.Reliability |
Week | Subject | Related Preparation |
1) | Introduction: syllabus, administration and organization of the course, general introduction in distributed DBMS | None |
2) | DDBMS Architecture: definition of DDBMS architecture, ANSI/SPARC standard, global, local, external, and internal schemas, DDBMS architectures, components of DDBMS | None |
3) | Distributed Database Design: conceptual design (what can be distributed, design patterns), top-down, bottom-up patterns, technical design (fragmentation, allocation and replication of fragments, optimality, heuristics) | None |
4) | Semantic Integrity Control: view management, security control, integrity control | None |
5) | Semantic Integrity Control: view management, security control, integrity control | None |
6) | Midterm Exam 1 | Review all the topics |
7) | Query decomposition and data localization: normalization, analysis, elimination of redundancy, rewriting, reduction for HF, reduction for VF | None |
8) | Optimization of Distributed Queries: basic concepts, distributed cost model, database statistics | None |
9) | Optimization of Distributed Queries: ordering of joins and semijoins, query optimization algorithms, INGRES, System R, hill climbing | None |
10) | Transactions: introduction to transactions, definition and examples, properties, classification, processing issues, execution | None |
11) | Midterm Exam 2 | Review all the topics |
12) | Concurrency Control: definition, execution schedules, examples, locking based algorithms, timestamp ordering algorithm, deadlock management | None |
13) | Reliability: definitions, basic concepts, local recovery management, distributed reliability protocols | None |
14) | Reliability: distributed reliability protocols, 2PC protocol | None |
Course Notes / Textbooks: | Principles of Distributed Database Systems by M. Tamer Özsu and Patrick Valduriez |
References: | None |
Semester Requirements | Number of Activities | Level of Contribution |
Project | 1 | % 10 |
Midterms | 2 | % 40 |
Final | 1 | % 50 |
Total | % 100 | |
PERCENTAGE OF SEMESTER WORK | % 40 | |
PERCENTAGE OF FINAL WORK | % 60 | |
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. |