Shyshko Artem Aleksandrovich

Resume Abstract

Content

• Introduction
• 1. Relevance of the topic
• 2. The purpose and objectives of the study, the planned results
• 3. Review of research and development
• 3.1 Overview of international sources
• 3.2 Overview of national sources
• 4. Analysis, structure and database development
• Conclusion
• List of sources

Introduction

Nowadays, a huge number of companies use personal computers to save and process any kind of information. This information is contained in databases. Databases play an important role in the developing world of technology. Everything we interact with in life every day seems to be fixed in some database. Working with databases is the most important skill in working with computers, and specialists in this field are becoming increasingly popular. The main ideas of the current information methodology are based on the presentation, according to which information should be formed into databases with the task of displaying a dynamically changing world and satisfying all information needs of users. Databases are formed and operate under the control of special software, called database management systems.

1. Relevance of the topic

Any modern organization can not do without a database. These are educational institutions, banks, shops, factories, any enterprises and government institutions. They use them to translate data into electronic form and data aggregation, as well as online access to them. This saves time and money on costs. Of course, reducing time is only a side effect of automation. The most important task of the development of information technologies in a completely different way is in the acquisition by an organization of exclusively new qualities, which give it substantial competitiveness. And it is worth a lot. In addition, now installing and managing a database is not such a difficult process as it was a decade ago. When the design and management of databases were not automated. The database management system allows you to create a database, updating the stored information in it, providing quick access to it for viewing and searching information.

2. The purpose and objectives of the study, the planned results

The purpose of the study is to develop a subsystem of administration of a distributed database of a distribution company and search for methods to optimize logistics.

The main objectives of the study:

1. Database analysis.
2. Subsystem structure development.
3. Subsystem implementation.

3. Review of research and development

The study of this topic is popular both in the international and national scientific communities.

3.1 Overview of international sources

Among international sources were found materials devoted to databases and their management. In the work of J.K. Data "Introduction to database systems" the author considers the general concept of databases and their capabilities. The database system is essentially nothing more than a computerized storage system of the same type of records. The very same database can considered as a kind of electronic filing, i.e. repository or container for a set of data files stored in the computer. Users of this system are given the opportunity to perform (or send the system execution requests) many different operations over such files, for example:

add new empty files to the database;

insert new data into existing files;

get data from existing files;

delete data from existing files;

change data in existing files;

delete existing files from the database [ 1 ].

On the official MySQL site there is an article on the list of all MySQL versions available for this memo, listing their advantages and innovations.[2]

In his work "Firebird. Database Developer's Guide," Borri Helen examines this DBMS, describing its main characteristics and capabilities[3].

3.2 Overview of national sources

From national sources, I would like to mention S. Kuznetsov and his work "The Basics of Databases", which discusses the main differences between file systems and database management systems. Based on the analysis of the capabilities of modern file systems, areas of applications are distinguished in which it suffices to use files, as well as those for which databases are necessary. [4].

The book Kogalovsky M. R. "Encyclopedia of Database Technologies" tells about database terminology and information systems terminology.[5].

4. Analysis, structure and database development

Database - a set of information (data) that is stored in an orderly way and can be found and processed using an electronic computer (computer). [6].

Database Management System (DBMS) - a set of software and language tools that allows you to perform various actions on data, namely their creation, modification, deletion, security, and so on. Such access is performed using a special SQL language. SQL is a structured query language whose main task is to provide a simple way to read and write information to the database.[7].

The simplest database operation scheme is shown in Figure 1.

Figure 1 - DB operation diagram

By the nature of the use of the DBMS are: single-user (designed to create and use the database on a personal computer) and multi-user (designed to work with a single database of several computers connected to local networks).

The division by nature of use is presented in Figure 2.

Figure 2 - Division by nature of use

This project presents a view of the client-server database architecture. The application I developed involves placing the application on the server. The architecture itself is divided into 2 non-uniform parts such as: database client and server. Accordingly, due to the fact that the server computer is separate from the client itself, the server is called remote.

The client-server architecture is shown in Figure 3.

Figure 3 - Client-Server Architecture

The conceptual database model reflects the subject area for which the database is being developed.

Figure 4 - Conceptual model of the database subsystem

Consider this model in detail. In rectangular blocks are objects that denote things. We have this: "Buyer", "Purchase", "Shopping Magazine", "Supplier", "Delivery", "Supply Journal", "Automobile". In the so-called ovals are the attributes characterizing the object. The attribute of the “Buyer” object is the “Buyer ID”, “Full Name”, “Passport”, “Telephone Number”. At the “Purchase” object the attribute is “purchase id”, “buyer id”, “Delivery date”. The attribute on the object “Purchase log” will be “purchase id”, “Model”. The “Supplier” object has the attributes: “Car dealer id”, “Delivery address”, “Model”, “Delivery date”. Attribute of the “Delivery” object is: “Delivery Date”, “Delivery id”, “Buyer id”. The “Supply Log” object has attributes: “delivery id”, “Model”. The object "Car" has the attributes "Model / Car Brand", "Color", "Gearbox", "Engine size". Diamonds denote connections between objects. Communication power is indicated by arrows.

In order to provide more convenient operation of the subsystem, it is necessary to implement its interface. The essence of the interface in this paper is the convenience of introducing and extracting the necessary information. In this project, an interface is implemented that works with databases (DB). The main functions in it are the functions of adding information to our database.

Figure 5 - Subsystem Interface

Consider the interface in more detail. As we can see, the entire interface is conventionally divided into 4 parts, such as: “Input window”, “Special capabilities window”, “Map window”, “Output window”. Let us examine each part in more detail. The “input window” is directly divided into 3 conditional parts: “Personal data”, “Auto”, “Car dealership delivery”. Each of these parts also includes some more points. Therefore, based on Figure 1, we can conclude that each part corresponds to some data. For example, “full name”, “Passport”, “Telephone number” we can enter only in the “Personal data” part. Similarly, with the other parts, “Make / Model”, “Color”, “Gearbox”, “Engine capacity” can only be entered into the “Auto” part, and the “Auto Show”, “Address”, “Delivery Address”, “Date” Delivery ”, only in“ Car Dealer Delivery ”.

5. Subsystem implementation

1. Table "avto".
2. Table "avtosalons".
3. “personaldata” table.
4. Table "id".
5. Application interface implementation.

1The table “avto” consists of 5 columns: “id”, “name”, “color”, “value”, “korobka”. The “id” column was assigned a bigint data type of size (20), due to the fact that this column will contain numeric values, a length of 20 characters will be quite enough. This column will contain the order number of the buyer. Also, this column is marked as Auto_incremental, that is, it will fill itself. This column is a foreign key and is associated with the table "id" and its column "id_avto" The “name” column is assigned the text data type, because this column will contain information about the make and model of the car, and therefore the text. The number of characters is unlimited. The "color" column is also of type text. This column will contain information about the color of the car. The number of characters is also unlimited. The “value” column contains a varchar type of length (20). Contains information about engine size. This type of data was chosen due to the fact that in some cases the volume is entered through a period or comma (1.4 1.8), therefore the type int is not selected. The column “korobka” is assigned the text type of unlimited length. This column contains information about the type of transmission (Automatic / Manual).

Figure 6 - The implemented structure of the table “avto”

2. There are 5 columns in the “avtosalons” table: “id”, “name”, “adress”, “dostavka”, “data”. The “id” column is also of the bigint type, 20 characters in size. For the same reasons, as in the “avto” table, this type was selected with so many symbols and with auto-increment. It contains the serial number of the car dealership, coincides with the column “id” of the table “avto”. Contains the foreign key associated with the “id_avtosalons” column of the “id” table. In the columns “name”, “adress” and “dostavka” the text data type is set to unlimited size. The column "name" contains information about the name of the car dealership. The adress column stores the address of the dealership, and the dostavka column contains the shipping address information of the vehicle. The last column “data” contains data about the date of delivery of the car. This column is of type varchar with a length of 12 characters. This type is great for storing dates.

Figure 7 - The implemented structure of the table "avtosalons"

3. The “personaldata” table consists of 4 columns: “id”, “FIO”, “Pasport”, “number”. The “id” column is implemented in the same way as in the above tables. A link was established with the id_personaldata column, the id table. The “FIO” column has a mediumtext data type of unlimited length. This type is selected due to the ability to store more characters than the text type. This column stores information about the last name and patronymic of the car buyer. From the name of the “Pasport” column, it becomes clear that this column stores the buyer's passport data (series and number). The 15-character varchar data type, in my opinion, is best suited for writing both letters and numbers. This type is selected due to the ability to store more characters than the text type. This column stores information about the last name and patronymic of the car buyer. From the name of the “Pasport” column, it becomes clear that this column stores the buyer's passport data (series and number). The 15-character varchar data type, in my opinion, is best suited for writing both letters and numbers.

Figure 8 - The implemented table structure «personaldata»

4. The “id” table is a link for the previous tables. It contains the following columns: “id_avto”, “id_avtosalons”, “id_personaldata”. All columns have a bigint data type of 20 characters. Each column is a foreign key and is connected by index links between the tables.

Figure 9 - The implemented table structure «id»

5. To implement the interface, I used programming languages ??such as: HTML and PHP. In HTML, the beginning of the code always starts with the html tag. Then we use the “head” tag and inside the “head” container we use the meta tag to establish the utf-8 encoding using the @charset command, which is used to specify the encoding of the external CSS file. After that use the tag "body". In my project, this tag is used to store images that will be in the application header. In order to place images the tag “img” is used. Through the attribute “src” the address of the picture is set. Some images in this project contain links. For this purpose it is necessary to place a tag with a link before the tag “img” and its attributes. The syntax is: < a href = ”link”> < img .... >. The title of the application's tab is set by the < title> tag. To place the background you need the tag < body background= « image.format image»background-size: quantity %>.

Figure 10 - Implemented interface

Conclusion

The subsystem of administration of the distributed database of a trade organization has been developed. This subsystem allows the user to purchase a car without leaving home, which in the future will greatly simplify the purchase of all that the buyer wishes.

The master's work is devoted to the actual scientific task of uniting the main methods of instrumental minimization of Moore’s automata. In the framework of the research carried out:

1. Database analysis.
2. Development of the subsystem structure.
3. Subsystem implementation.

Further research focused on the following aspects:

1. Search for logistics optimization methods.
2. Investigation of logistics optimization methods of a distribution company.

When writing this essay master's work is not yet completed. Final Completion: May 2019. Full text of the work and materials on the topic can be obtained from the author or his manager after the specified date.

List of sources

1. J.K. Date "Introduction to Database Systems" ,2005.- 43 с.
2. MySQL [electronic resource] // dev.mysql:(сайт).[2011-2017]-Access mode: https://dev.mysql.com/doc/refman/4.1/en/news-3-23-x.html
3. Borri Helen. Firebird Database Developer’s Guide 2007. — С. 1104.
4. Kuznetsov S.D. "Basics of databases" , 2007. – 364 с.
5. Kogalovsky M. R. "Encyclopedia of Database Technology", 2005. – 528 с.
6. Database [electronic resource] // wikipedia:(сайт).[2011-2017]-Access mode:https://ru.wikipedia.org/wiki/База_данных
7. СУБД [electronic resource] // wikipedia:(сайт).[2011-2017]-Access mode:https://ru.wikipedia.org/wiki/Система_управления_базами_данных

Resume