Кафедра "Програмна інженерія та інтелектуальні технології управління ім. А. В. Дабагяна"

Постійне посилання колекціїhttps://repository.kpi.kharkov.ua/handle/KhPI-Press/1665

Офіційний сайт кафедри http://web.kpi.kharkov.ua/asu

Від січня 2022 року кафедра має назву "Програмна інженерія та інтелектуальні технології управління ім. А. В. ДАБАГЯНА" (тоді ж, у січні 2022 року в окремий підрозділ виділилася кафедра "Інформаційні системи та технології"), попередні назви – "Програмна інженерія та інформаційні технології управління" (від 2015), "Автоматизовані системи управління" (від 1977); первісна назва – кафедра автоматичного управління рухом.

Кафедра автоматичного управління рухом заснована в 1964 році задля підготовки інженерів-дослідників у галузі автоматичного управління рухом з ініціативи професора Харківського політехнічного інституту Арега Вагаршаковича Дабагяна та генерального конструктора КБ "Електроприладобудування" Володимира Григоровича Сергєєва.

Кафедра входить до складу Навчально-наукового інституту комп'ютерних наук та інформаційних технологій Національного технічного університету "Харківський політехнічний інститут".

У складі науково-педагогічного колективу кафедри працюють: 4 доктора технічних наук; 24 кандидата наук: 22 – технічних, 1 – фізико-математичних, 1 – економічних, 1 – доктор філософії; 3 співробітників мають звання професора, 19 – доцента, 1 – старшого наукового співробітника.

Переглянути

Результати пошуку

Зараз показуємо 1 - 8 з 8

Methodical guidelines for laboratory works "Data modeling using the IDEF1X notation"
(2022) Orlovskyi, D. L.; Kopp, A. M.
Goal: State the laboratory practice problem. Study and analyze the subject area. Select main database objects based on analysis. Simplified description of the subject area. Some enterprise purchases products from various suppliers. Suppliers can be both legal entities and individual entrepreneurs. Products purchase is performed as batches and processed in the form of supply contracts. Each supply contract has unique number and might be concluded with single supplier. Preliminary order, invoice or similar document is reason for supply. Each contract document for each product type contains product name, number of items, and cost (in UAH). Supplied products are brought to the warehouse for the purpose of further sales through various channels. Subject area analysis allowed to identify and describe core business processes related to products supply. It is assumed that enterprise will have to store large enough amount of data related to products supply. Besides, product supply information should be organized in the way that staff and management could perform analytical processing of this information. Therefore, it is necessary to create database used to store and process information related to products supply. Business process analysis allowed to define following information that might be included in the database.
Methodical guidelines for laboratory works "Learning the basics of working with DBMS MySQL: the main tools for implementing and supporting the business logic of SQL language"
(2022) Orlovskyi, D. L.; Kopp, A. M.
MySQL Database Management System (DBMS) is a freely distributed relational database developed and maintained by Oracle. From the very beginning, MySQL was developed by the Swedish company MySQL AB, which was later acquired by Sun Microsystems, which, in turn, was later acquired by Oracle. MySQL is distributed under both the GNU General Public License (GPL) and its commercial license. Under the terms of the GPL, software that uses MySQL libraries must also be distributed under the GPL license. For cases where developers do not want to open the source code of their software, a commercial license is provided. The advantage of a commercial license is quality service support. Contrary to Oracle’s MySQL licensing policy and to ensure free DBMS status, a fork of MySQL was created and called MariaDB. This database supports high compatibility with MySQL, ensuring the exact correspondence of the programming interface, the socalled API (Application Programming Interface), and MySQL commands. MySQL is a great solution for small, medium, and sometimes even large software systems. MySQL is also part of the WAMP (Windows, Apache, MySQL, PHP/Perl/Python) and LAMP (Linux, Apache, MySQL, PHP/Perl/Python) web application development stacks. This database is included in many ready-made assemblies of servers designed for web applications, such as XAMPP (which is proposed for use in this laboratory workshop), OpenServer, Denwer, and more. Recently, however, it is because of openness support, server builders and hosting providers are increasingly incorporating MariaDB into WAMP and LAMP stacks. Typically, MySQL is used as a server accessed by local or remote clients. However, the distribution also contains a library that provides the deployment of an internal server for standalone applications. In this laboratory workshop, we get acquainted with the implementation and maintenance of business logic in the database.
Methodical guidelines for the individual work "Development of the software application to work with the database using MySQL and PHP tools"
(2022) Orlovskyi, D. L.; Kopp, A. M.
MySQL Database Management System (DBMS) is a freely distributed relational database developed and maintained by Oracle. From the very beginning, MySQL was developed by the Swedish company MySQL AB, which was later acquired by Sun Microsystems, which, in turn, was later acquired by Oracle. MySQL is distributed under both the GNU General Public License (GPL) and its commercial license. Under the terms of the GPL, software that uses MySQL libraries must also be distributed under the GPL license. For cases where developers do not want to open the source code of their software, a commercial license is provided. The advantage of a commercial license is quality service support. Contrary to Oracle’s MySQL licensing policy and to ensure free DBMS status, a fork of MySQL was created and called MariaDB. This database supports high compatibility with MySQL, ensuring the exact correspondence of the programming interface, the socalled API (Application Programming Interface), and MySQL commands. MySQL is a great solution for small, medium, and sometimes even large software systems. MySQL is also part of the WAMP (Windows, Apache, MySQL, PHP/Perl/Python) and LAMP (Linux, Apache, MySQL, PHP/Perl/Python) web application development stacks. This database is included in many ready-made assemblies of servers designed for web applications, such as XAMPP (which is proposed for use in this methodical guidelines), OpenServer, Denwer, and more. Recently, however, it is because of openness support, server builders and hosting providers are increasingly incorporating MariaDB into WAMP and LAMP stacks. Typically, MySQL is used as a server accessed by local or remote clients. However, the distribution also contains a library that provides the deployment of an internal server for standalone applications. These guidelines discuss the basics of the database application development using the MySQL DBMS and PHP programming language.
Guidelines for laboratory works on the topic "Learning the basics of working with DBMS MySQL: Fundamental DDL and DML tools of SQL language"
(2021) Orlovskyi, D. L.; Kopp, A. M.
MySQL Database Management System (DBMS) is a freely distributed relational database developed and maintained by Oracle. From the very beginning, MySQL was developed by the Swedish company MySQL AB, which was later acquired by Sun Microsystems, which, in turn, was later acquired by Oracle. MySQL is distributed under both the GNU General Public License (GPL) and its commercial license. Under the terms of the GPL, software that uses MySQL libraries must also be distributed under the GPL license. For cases where developers do not want to open the source code of their software, a commercial license is provided. The advantage of a commercial license is quality service support. Contrary to Oracle’s MySQL licensing policy and to ensure free DBMS status, a fork of MySQL was created and called MariaDB. This database supports high compatibility with MySQL, ensuring the exact correspondence of the programming interface, the socalled API (Application Programming Interface), and MySQL commands. MySQL is a great solution for small, medium, and sometimes even large software systems. MySQL is also part of the WAMP (Windows, Apache, MySQL, PHP/Perl/Python) and LAMP (Linux, Apache, MySQL, PHP/Perl/Python) web application development stacks. This database is included in many ready-made assemblies of servers designed for web applications, such as XAMPP (which is proposed for use in this laboratory workshop), OpenServer, Denwer, and more. Recently, however, it is because of openness support, server builders and hosting providers are increasingly incorporating MariaDB into WAMP and LAMP stacks. Typically, MySQL is used as a server accessed by local or remote clients. However, the distribution also contains a library that provides the deployment of an internal server for standalone applications. In this laboratory workshop, we get acquainted with the main features of MySQL in the role of the client-server database.
Guidelines for laboratory works on the topic "Learning the basics of working with DBMS Microsoft Access: Database creation and fundamentals of work with DML tools of SQL"
(2021) Orlovskyi, D. L.; Kopp, A. M.
Experience in using computers in the building of applied data processing systems shows that universal programming languages are not the most effective tool in contrast with the specific languages of data management systems. Such tools are commonly included in the Database Management Systems (DBMS) but also might be stand-alone. DBMS provides users with the ability to manage data directly, as well as rapid application development tools used by programmers to develop the data processing software. These guidelines consider problems related to database development, work with data, and the basics of programming in the Microsoft Access DBMS environment. Today Microsoft Access DBMS is extremely popular, first of all, because it is provided as part of the Microsoft Office package. As well as the text processor Word and Excel spreadsheets, Access DBMS is widely used for business workflow automation. User-friendly and simple interface, advanced help system, and various in-built tools (so-called wizards) simplify the users’ training process and make Access DBMS very attractive especially for users without enough experience in database management systems. The set of tasks includes the complete list of problems – from database development to user interface design. During the study, students will learn various tools used to automate data storage and processing tasks. There are tools used to design forms, queries, reports, etc. It is recommended to use Microsoft Access 2007 or newer. Efficient learning of the Microsoft Access DBMS features is possible only by practical implementation of the proposed tasks on the computer.
A web service to detect modeling mistakes in BPMN 2.0 business process models
(Черкаський національний університет ім. Б. Хмельницького, 2021) Kopp, A. M.; Orlovskyi, D. L.
An overview of business intelligence core capabilities and software platforms
(Черкаський національний університет ім. Б. Хмельницького, 2021) Orlovskyi, D. L.; Kopp, A. M.
Development of adaptive parametric interface for analytical queries: electrical equipment management system case study
(Одеська національна академія харчових технологій, 2020) Orlovskyi, D. L.; Kopp, A. M.; Bilous, I. S.
This paper considers the case study of the development of adaptive parametric interface for analytical queries in an electrical equipment management system. The relevance of information technology usage in a power engineering industry is considered, as well as the related studies in the field of query form generation for information systems are analyzed. The set of query form parameters is defined and example of such form is demonstrated. Formalized query form features could be used to gather the most preferable configurations and develop a recommender module in order to improve the user experience.