Добавил:
Upload Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
CW_TEORSKII_ANATOLII.docx
Скачиваний:
0
Добавлен:
01.07.2025
Размер:
165.08 Кб
Скачать

THE MINISTRY OF EDUCATION AND SCIENCE OF THE REPUBLIC OF KAZAKHSTAN

International information technologies university

Faculty of Information technologies

Department of Computer Systems, Software Engineering and Telecommunications

Course work Topic: Auto park

Student: Teorskii Anatolii

Group: CSSE – 137R

Accepted : Kozina L. A.

Almaty 2014

CONTENTS:

Introduction ………………………………………………………………………. 4

Database Design.

1. Subject Area Analysis ………………………………………................... 5

2. Conceptual Design ……………………………………….…… ...............7

3. Logical Design ……………………………………………. ....................8

4.Physical Design ………………………………………… ........................11

5. Content ………………………………………………..... ........................14

6. Queries ………………………………………………….. .......................17

Conclusion ………………………………………………………………………. 20

References ………………………………………………………………………. 21

Introduction

In recent years, into our life is very actively introduced computer programs and computer technology. More and more information will appear. This information is necessary to collect, store and process. This is why we use the Database. Using the database, you heads of major companies will always keep information about your company, your employees information, product information and much more at your fingertips. With a database of your information will be laid out on shelves and you will always find what you need, and you will not need to look for it for a long time. Databases are very valuable in all kinds of human activity. That is why a lot of young programmers devote a lot of attention and time to study the database design. But it is not so easy as it might seem at first glance. Database design requires accuracy, knowledge, good mental abilities and a large supply of patience. I chose the topic for my database - Auto park. I believe that the database will be very relevant in our days, in every city, there are several car park and each has a large number of transport and personnel. For this information is very difficult to keep track, but here will help my database. I hope that through my database I can facilitate the work of many companies and improve the quality and speed of many of these companies.

Database design

1. Subject area analysis

Definition:

The following data base is designed to hold information relating to Autopark. Here you can find all the information related to the vehicle fleet, transport and personnel.

Constraints:

  • Maybe a few drivers on one transport.

  • Maybe a few conductors on one transport.

  • Some drivers may be the same name or surname.

  • Some conductors may be the same name or surname.

  • Each transport should have only one validator.

  • ID cannot be the same.

  • Transport expired Inspection is not suitable for use.

  • Can be a few transports on one route.

  • Can be a few stops on one route.

  • Each transports can have only one routes.

  • One Trolleybus can contain only one validator.

  • One unit have only one ID.

Entities & relationships:

  • Autopark (autopark_id, autopark_name)

  • Driver (driver_id, driver_name, driver_surname, date_birth, class_driving, exp, salary, address, telephone_number, e_mail)

  • Conductor (conductor_id, conductor_ name, conductor_surname, date_birth, salary, address, telephone_number, e_mail)

  • Route (routes_id, start_point, final_point, interval_length)

  • Stop (stops_id, stops_name)

  • Breakage (breakage_id, date_breakage, discription)

  • Transport (transport_id, model_name, type, mileage, date_tech_inspec, rdy_for_use, number_seats, total_capacity, have_validator, autopark_id, routes_id)

  • Validator (validator_id, model_name, date_tech_inspec, rdy_for_use, transport_id)

  • TranspCond (transpcond_id, transport_id, conductor_id)

  • TranspDrive (transpdrice_id, transport_id, driver_id)

  • StopRoute (stoprute_id, route_id, stop_id, transport_id)

Relations:

  • A many-to-one links the set Transport and Autopark.

  • A many-to-many links the set Transport and driver by TranspDrive.

  • A many-to-many links the set Transport and conductor by TranspCond.

  • A many-to-many links the set Breakage and Transport.

  • A many-to-many links the set Route and Stop by StopRoute.

  • A many-to-one links the set Validator and Transport.

Queries:

  • Get information about the Autopark.

  • Get information about the number of buses and trolleybuses in the Autopark.

  • Get information about bus that is ready for operation.

  • Get information about the driver who serve any transport.

  • Get information about the conductor who serve any transport.

  • Get information about the validator is in any Trolleybus.

  • Get information about any transport routes.

  • Get information about any of the route stops.

Соседние файлы в предмете [НЕСОРТИРОВАННОЕ]