İlişkisel veri tabanı mantığına dayalı sigorta otomasyonu
An overview of database management and relational databases
- Tez No: 66561
- Danışmanlar: DOÇ. DR. GAZANFER ÜNAL
- Tez Türü: Yüksek Lisans
- Konular: Mühendislik Bilimleri, Engineering Sciences
- Anahtar Kelimeler: Otomasyon, Sigorta, Veri tabanı, Automation, Insurance, Database
- Yıl: 1997
- Dil: Türkçe
- Üniversite: İstanbul Teknik Üniversitesi
- Enstitü: Fen Bilimleri Enstitüsü
- Ana Bilim Dalı: Mühendislik Bilimleri Ana Bilim Dalı
- Bilim Dalı: Sistem Analizi Bilim Dalı
- Sayfa Sayısı: Belirtilmemiş.
Özet
ÖZET Proje konusu olarak, sigortacılık sektöründe, daha çok Nakliyat Sigorta Poliçeleri yapan bir acentanın poliçe işlevlerini gerçekleştiren bir uygulama geliştirilmiştir. Genel olarak uygulama, acentanın geçici ve kati nakliyat sigorta poliçelerinin veritabanını tutmakta, bu poliçelerin basımım yapmaktadır. Acente aynı zamanda bir bankanın yan kuruluşu olduğu için; bu banka şubelerinin de kestiği poliçeler veritabanında tutulmaktadır. Ayrıca, bu şubelere verilecek olan primlerin hesaplanması ve dökümüyle ilgili raporlarda basılabilmektedir. Uygulama, Visual Basic'te ilişkisel veritabanı yönetim sistemine göre, tek kullanıcılı olarak tasarlanmıştır. Veritabanı uygulamaları Visual Basic veri ulaşım metodlarını kullanarak Access veritabanı yönetim sistemi üzerinde gerçekleşmektedir. Uygulama Windows95 işletim sistemi üzerinde çalışmaktadır (32 Bit). Ayrıca Windows 3.X'e göre (16 Bit) derleyip çalıştırmakta mümkündür. Tez, beş ana bölümden oluşmaktadır; Birinci bölümde, Windows programcılığının özellikleri, Visual Basic' in tarihçesi ve projede neden Visual Basic programlama dilinin kullanıldığı anlatılmıştır. İkinci bölümde, Visual Basic de uygulama geliştirme, Visual Basic projeleri ve kullanılan standart kontrollerin özellikleri incelenmiştir. Üçüncü bölümde, Visual Basic'in kullandığı veri ulaşım metodları incelenmiştir. Dördüncü bölümde, SQL'in yapısı, gelişimi ve Visual Basic'de kullanımı anlatılmıştır. Beşinci bölümde ise proje konusu, kullanılan formların açıklaması, hesaplamaların nasıl yapıldığı yer almaktadır. Veritabanı uygulamaları ve program çıktısı Ekler bölümünde verilmiştir. IX
Özet (Çeviri)
A database system is essentially nothing more than a computerized record keeping system. The database itself can be regarded as a kind of electronic filing cabinet; in other words, it is a repository for a collection of computerized data files. The user of the system will be given facilities to perform a variety of operations on such files, including the following among others:. Adding new (empty) files to the database;. Inserting new data into existing files;. Retrieving data from existing files;. Updating data in existing files;. Deleting data from existing files;. Removing existing files (empty or otherwise) from the database. A database system is basically a computerized record keeping system; that is, it is a computerized system whose overall purpose is to maintain information and to make that information available on demand. Figure 1 is intended to show that a database system involves four major components, namely data, hardware, software, and users. Database systems are now available on machines that range all the way from quite small micros (even portable PCs) to the largest mainframes. So, the facilities provided by any given system are to some extent determined by the size and power of the underlying machine. In particular, systems on large machines (“large systems”) tend to be multi-user, whereas those on smaller machines (“small systems”) tend to be single-user. A single-user system is a system in which at most one user can access the database at any given time; a multi-user system is a system in which multiple users can access the database concurrently. In general, the data in the database-at least in a large system-will be both integrated and shared. These two aspects, integration and sharing, represent a major advantage of database systems in the“large”environment; and integration, at least, can be significant in the“small”environment also.Application programs 7777 Database Management System (DBMS) 'yrp Tf} <. Database. 4 ^==^J r4 End-users Figure 1 Simplified picture of a database system The hardware portions of the system consist of:. The secondary storage volumes-typically moving-head magnetic disks-that are used to hold the stored data, together with the associated I/O devices (disk drives, etc.), device controllers, I/O channels, and so forth;. The processors) and associated main memory that are used to support the execution of the database system software. Between the physical database itself and the users of the system is a layer of software, the database manager (DB manager) or, more usually, database management system (DBMS). All requests from users for access to the database are handled by the DBMS; the facilities for adding and removing files (or tables), retrieving data from and updating data in such files or tables, and so forth, are all facilities provided by the DBMS. We consider three broad classes of user.. First, there is the application programmer, responsible for writing application programs that use the database, typically in a language such as COBOL or PL/I or some more modern language such as C or Pascal.. The second class of user, then, is the end user, interacting with the system from an on-line terminal. A given end user can access the database via one of the on line applications mentioned in the previous paragraph, or he or she can use an interface provided as an integral part of the database system software..The third class of user is the database administrator or DBA. XIWhat Is A Database? Persistent Data It is convenient to refer to the data in a database as“persistent”data. By the term“persistent,”we mean to suggest that database data differs in kind from other, more ephemeral, data, such as input data, output data, control statements, work queues, software control blocks, intermediate results, and more generally any data that is somewhat transient in nature..“Input data”refers to information entering the system for the very first time (typically from a terminal keyboard or card reader or similar device).. Similarly,“output data”refers to messages and results emanating from the system (typically printed or otherwise displayed on a terminal screen). A database consists of some collection of persistent data that is used by the application systems of some given enterprise. The term“enterprise”as used in this definition is simply a convenient generic term for any reasonably self-contained commercial, scientific, technical, or other orgaiuzation. An enterprise might be a single individual (with a small private database), or a complete corporation or similar large body (with a large shared database), or anything in between. Here are some examples: A manufacturing company; A bank; A hospital; A university. Why Database? Why use a database system? What are the advantages? To some extent the answer to these questions depends on whether the system in question is single- or multi-user (or rather, to be more accurate, there are numerous additional advantages in the multi-user case). Let us consider the single-user case first. Imagine a similar database for a large restaurant, with a stock of perhaps thousands of bottles and with very frequent changes to that stock; or think of a liquor store, with again a very large stock and with high turnover on that stock. (These would typically still be single-user systems, incidentally, even though the database is larger.) The advantages of a database system over traditional, paper-based methods of record keeping will perhaps be more readily apparent in these examples. Here are some of them:. Compactness: No need for possibly voluminous paper files.. Speed: The machine can retrieve and change data far faster than a human can. In particular, can be answered quickly without any need for time-consuming manual or visual searches.. Less drudgery: Much of the sheer tedium of maintaining files by hand is eliminated. Mechanical tasks are always better done by machines.. Currency: Accurate, up-to-date information is available on demand at any time. XllThe foregoing benefits apply with even more force in a multi-user environment, of course, where the database is likely to be much larger and much more complex than in the single-user case. However, there is one overriding additional advantage in such an environment, namely as follows: The database system provides the enterprise with centralized control of its data. Such a situation contrasts sharply with that found in an enterprise without a database system, where typically each application has its own private files-quite often its own private tapes and disks, too-so that the data is widely dispersed and is therefore probably difficult to control in any systematic way. Relational Databases Before looking at the individual components of relational databases, let's first establish a simple definition. A Relational Database is defined as“a collection of data that indicates relation among data elements”; or, to put it even more directly, a relational database is“ a collection of related data.”. In order to build a collection of related data, you need three key building blocks. These building blocks are as follows (from smallest to largest) : ? Data Fields (sometimes called Data Columns) ? Data Records (also known as Data Rows) ? Data Tables The first building block in a relational database is the data field. The data field contains the smallest element of data that you can store in a database, and each field contains only one data element. For example, if you want to store the name of a customer, you must create a data field somewhere in the database and also give that field a name, such as CustomerName. If you want to store the current account balance of a customer, you must create another field, possibly calling it AccountBalance. All the fields you create are stored in a single database (see Figure 2). Although it is possible to store more than one data element in a single field (such as first and last name), it is not good database practice to do so. In fact, storing more than one data element in a field (for example, storing two data elements in the CcustomerName field (firstname and lastname)) can lead to problems when users try to retrieve or update data. Figure 2 Examples of data fields in a database XlllData records are collection of related data fields. To use the example started earlier, a Customer Record could contain the fields LastName, FirstName, and AccountBalance. All three fields describe a single customer in the database. A single data record contains only one copy of each defined data field. For example, a single data record cannot contain more than one LastName data field. Figure 3 shows the Company Database with a Customer Record defined. The Customer Record (row) contains three fields (columns). Company Database Figure 3 An example of data record in a database By combining data fields and data records, you create the most common element of relational databases - the data table. This element contains multiple data records, and each data record contains multiple data fields (see Figure 4). Just as each data record contains related data fields (LastName, FirstName, and AccountBalance), each data table contains related records. Data tables have meaningful names in the same way that data fields have meaningful names. This names help you and other users to remember the contents of the elements (table elements and field elements). Company Database Figure 4 An example of a data table in a database Database Relationships Just as a data record can contain several related data fields, a database can contain several related tables. Using relationships is a very efficient way to store complex data. For example, a table storing customer names could be related to XIVanother table storing the names of items the customer has bought, which could be in turn related to a table storing the names of all the items you have to sell. By establishing meaningful relationships between data tables, you can create flexible data structures that are easy to maintain. You establish relationships between data tables by using pointer or qualifier fields in your data table. You use qualifier fields to point to records in other tables that have additional information. Qualifier fields usually describe what's known as one - to - one relationships. A good example of a one - to - one relationship is the relationship between a single customer record and a single record in the shipping address table (see Figure 5). One to one relationships are used to link records in a master table (such as the Customer Table) to a single related record in another table. Company Database LastName Field FirsfName Field AccountBalance Field LastName Field FirstName Field AccountBalance Field LastName Field FirstName Field AccountBalance Field LastName Field ShipAddr LastName Field ShipAddr LastName Field ShipAddr Figure 5 An example of a one - to - one relationship between tables You use pointer fields to point to one or more records in other tables that have related information. Pointer fields usually describe what are known as one - to - many relationships. A good example of a one - to - many relationship is the relationship between a single customer master record and several outstanding customer orders. One-to-many relationships are used to link records in a master table (such as the customer table) to multiple records in another table. Indexes: Key Fields Usually, at least one data field in each data table acts as a key field for the table. Key fields in relational databases are used to define and maintain database integrity and to establish relationships between data tables. You create keys in your data table by designating one (or more) fields in your table as either a primary key or XVa foreign key. A data table can only have one primary key, but it can have several foreign keys. It can also have no foreign key at all. The primary key is used to control the order in which the data is displayed. The main role of the primary key is to maintain the interval integrity of a data table. For this reason, no two records in a data table can have the same primary key value. The foreign key is used to relate fields to fields in other (foreign) tables in the database. Key fields are sometimes referred to as index fields or indexes. It is important to note that in most PC databases (xBase, Paradox, Btrieve, and so forth), indexes are used only to speed processing of large files and play only a minor role in maintaining table relationships. The Visual Basic database model and other true relational database models use key fields to establish database integrity rules as well as to speed database search and retrieval. As the subject of my project, I developed an application realizing policy activities of the insurance company that serve in the sector of insurance. The application has been planned according to relational database management system. And it is running on single user Windows platform. The application is running on Windows95 operating system (32 Bit), but it can be compiled for Windows 3.X (16 Bit) if desired. The application is developed with Microsoft Visual Basic 4.0. My thesis consists of five main sections. In the first section, Windows programming techniques, the history of Visual Basic and the reason why it is used in the project are mentioned. In the second section, developing an application with Visual Basic, Visual Basic projects and standard controls are scratinized. In the third section, Visual Basic Data Access Objects are examined. In the fourth section, the structure of SQL and using SQL with Visual Basic is explained. Finally, in the last section, subject of the project, and the forms of the project are examined. XVI
Benzer Tezler
- Televizyon programcılığında izlence çizelgelerini oluşturma sanatı
The Art of creating charts for TV programs
KUDRET AKIN
Yüksek Lisans
Türkçe
1997
Radyo-Televizyonİstanbul ÜniversitesiRadyo Televizyon ve Sinema Ana Bilim Dalı
DOÇ. DR. EDİBE SÖZEN
- Dağıtık veritabanı konfigürasyonlu stok kontrol sistemi
Stock control system with distributed database
ASUMAN EROL
- Bilgisayar programlamada sorgulama optimizasyonu teknikleri
Query optimization in database systems
ÇİĞDEM KAPTANOĞLU
Yüksek Lisans
Türkçe
1992
Bilgisayar Mühendisliği Bilimleri-Bilgisayar ve Kontrolİstanbul Teknik ÜniversitesiDOÇ. DR. MİTHAT UYSAL
- İstatistiki bilgi işlemde veri bankaları ve veri tabanlarının analizde etkinlik bakımından değerlendirilmesi ve mekansal veriler
Assesment and efficiency analysis of databanks and data bases in statistical information processing for spatial data
MERT ECE
- Teknik yenileştirmeye elverişli donanım envanter takibi ve bir uygulama
Başlık çevirisi yok
PELİN KOCAMAN
Yüksek Lisans
Türkçe
1998
Bilgisayar Mühendisliği Bilimleri-Bilgisayar ve KontrolYüzüncü Yıl ÜniversitesiBilgisayar Mühendisliği Ana Bilim Dalı
YRD. DOÇ. DR. E. MURAT ESİN