home › Navigators › OBD car service. Download the access database Car service. Functions Performed by the Database

OBD car service. Download the access database Car service. Functions Performed by the Database

Technology of creation Database "Auto service"

To create the database, the goals and objectives of the “Auto Service” database were set:

? ensure customer satisfaction with both service and firm;
? provide best service near
? warranty repairs of sold new and used cars;
? commercial preventive maintenance (adjustments, etc.);
? commercial rehabilitation services (repairs);
? repair of used components and assemblies for the stock of refurbished spare parts.

? People,
? materials,
? computers,
? machines,
? building.

The developed and created Car Service Database is a set of interconnected components and displays various areas of car repair.

Figure 14. Database "Car service"

The system is divided into two subsystems and one extension:

? Repair of the technical part of the car.
? Expansion - car interior repairs.

The main system “Repair of technical parts of a car” consists of four tables (see Fig. 15):

« Order» - including the necessary information about the order for repairs and diagnostics of the car, that is:

? Automobile.
? Owner.
? Reason for contacting the service station.

« Repair"- a table describing the process of repairing technical parts of a car, namely parts that need to be repaired in the near future. This table includes the following items:

? Engine repair.
? Gearbox repair.
? Chassis repair.
? Fuel system repair.

Figure 15. Order for repair of technical parts

Table " Diagnostics", related to " By order» and distributes cars for diagnostics of certain parts of the car, i.e. engine, gearbox, chassis and fuel system.

IN " Diagnostics» information about cars that require diagnostics of a particular part is stored.

? Engine diagnostics.
? Transmission diagnostics.
? Chassis diagnostics.
? Fuel system diagnostics.

Main system works on basis “Cascade models" And refers on standard GOST 21624 -76

GOST 18507 -73

The system works from collecting information about the order, then diagnostics occurs, which determines the need to repair the machine. Each stage (except the initial one) cannot begin until the other is completed, unless the car does not need repairs.

The IT service subsystem was created to provide a repair guarantee, file a warranty claim and purchase spare parts for repairs.

1) filing a claim,
2) registration of a guarantee,
3) ordering spare parts, and includes 11 tables, one of which is common for IT service. (see Fig. 16).

Figure 16. IT service

IT service - divides the entire service into 3 parts:

? warranty claim,
? registration of guarantee,
? ordering spare parts.

Data 1 and 2 - contain information about customers.

Receipt 1 - the table contains data on the time of request and the price of services provided.

Reason for contact - a table containing information about the reason for contacting the service station under warranty. It has a connection with the tables: agreement of STO 1 and Outcome 1, where data on the agreement of the STO with the claim and the possibility of solving the problem are noted, respectively.

The expansion represents some kind of increase in car repair services. Now the system includes body repair and interior repair, which are also handled by the service station.

The extension subsystem consists of two tables and affects the 2nd table from the main system. (see Fig. 17)

Figure 17. Expansion

The “body repair and interior repair” tables include information about the types of services.

Body repair:

? Replacement of parts.
? Putty.
? Painting.
? Varnishing.
? Polishing.

Interior renovation:

? Replacement of components.
? Repair of components.

These tables lead to connections with the table " Price» to fix prices for services.

Functional:

? outfit orders,
? work,
? services,
? brigades,
? norm-hours.

Database resources:

? People,
? equipment,
? materials,
? computers,
? machines,
? building.

The cascade model, presented in Figure 18, provides for the sequential execution of all stages of the project in a strictly fixed order. The transition to the next stage means the complete completion of work at the previous stage.

This is represented in the database as follows:

? accepting orders for repairs,
? Car diagnostics,
? car repair,
? release of a car from a service station.

Figure 18. Database model

Analysis phase

Here you can fill out an application for car repairs at a service station. The customer fills out a document where the customer indicates the service that he needs.

Design phase

At this stage, the car is sent for diagnostics, which determines the cause of the car breakdown. Subsequently, at the customer’s discretion, the machine is sent for repair.

Implementation and implementation phase

At this phase, repairs are carried out on parts of the car that, according to diagnostic results, need repair or replacement. Also, without any checks, at this stage repairs can be made to the exterior of the car and the interior.

Maintenance phase

At this stage, a guarantee for repairs is issued and the funds spent on diagnosing and repairing the car are calculated, after which the car is returned to the owner.

Properties of the system

Integrability- the system is integrable, as it has the ability to interact with various banks (payment for services through these banks), with a tax company (sale of spare parts outside the region). The system is also connected with various car dealerships (under contract) and insurance companies that insure the car service itself, as well as the company where spare parts are purchased.

Divisibility- the system consists of many subsystems that perform certain functions and have the ability to work autonomously.

Integrity- despite the fact that the system is divisible, when fully operational, it will not work if the functionality of one of its subsystems is disrupted.

Structurality- distribution by levels and hierarchies of system elements, i.e. the system will not be able to continue working if one of the stages is skipped (without issuing a warranty, the customer will not be able to file a claim with the service station).

Standards

GOST 21624 -76 - this standard establishes requirements for products to ensure a given level of serviceability (ET) and maintainability (RP), as well as the values of the ET and RP indicators provided for by GOST 20334-81 for automotive products - four-wheel drive and part-wheel drive vehicles (trucks, cars and buses), trailers and semi-trailers (hereinafter referred to as products).

GOST 18507 -73 - this standard applies to buses and passenger cars (hereinafter referred to as cars) and establishes methods for their control tests after major repairs carried out by automobile repair enterprises.

The standard does not apply to passenger cars, the overhaul of which was carried out according to the orders of individual owners.

Technical specifications

1. Create a common database of all services at the service station for a specific car.

Figure 19. General base of all services at the service station

2. Data on the necessary tools and materials.

Figure 20. Tool and material data

3. Connections with third-party systems.

Figure 21. Third party systems

Figure 22. Auto centers

Figure 23. Insurers

Figure 24. Insurers field

4. Comments on the quality of service.

Figure 25. Comments

Figure 26. Visitor reviews

Figure 27. Reviews

During the work, a database was created in the MS Access database management system. The work shows a step-by-step technology for creating a Database. An example of the “Car Service” database is given. This database was tested at a service station. The system has been tested. During the work, adjustments were made and the final version of the “Car Service” database was presented in the work.

It is necessary to create a database of “Car service” accessories

Rice. 1 Main button form of the finished database “Car service”

The “Owners” form with the subordinate “Cars” form

Rice. 2 Form “Cars”

Employees form

Rice. 4 Form "Service"

Rice. 5 Requests page

Query “Grouping by jobs and employees”

Query “By last name of mechanic”

Request “Search by license plate number”

Rice. 6 Reports

Report “Grouping by jobs and employees”

Fig.7 “Search by license plate” report

Rice. 8 Report “By the name of the mechanic”

Rice. 9 The data diagram of the finished “Car Service” database displays the relationships of the tables: Owners, Cars, Service, Job Category, Employees.

Structure of the table “Cars”: state. number, brand, owner.

Structure of the “Owners” table: owner No., full name, cellular telephone, driver's license no.

Structure of the “Service” table: service number, vehicle, work category, order readiness date, employee.

Structure of the “Employees” table: employee number, cell phone, address, full name.

or here:

Download a database report with screen forms for free

Approximate price 763 rub.

The exact price depends on the payment method.

Access database payment methods: WebMoney, Payment terminals, Russian Post, QIWI, Beeline, MTC, Megafon, Debit or Credit Card, WeChat Pay, Alipay (China), UnionPay, Yandex.Money, Gift Certificate and others.

Download Access databases on similar topics:

Database access Car service 2
Generating invoices for payment at a car service center
Car registration in a motor transport company.
ATP (motor transport enterprise).
ATP 2007 (motor transport enterprise)
Auto repair shops
"Operation Accounting Vehicle»
“Accounting for road traffic accidents”
Registration of car offenders in the traffic police.
“Accounting for traffic violations”
"Replacement of auto parts at service stations"
Urban transport
"Sales of airline tickets"
"Bus station"
"Car rental"
Car rental 2
Driving school
Spare parts company
car showroom
Accounting for vehicle depreciation by MOL and vehicle groups
Taxi
Passenger car company
Minibus schedule
Accounting for road transport by car brand

Key words: database download; database program; database; coursework database; download access database; access; ready access database; databases in access; access database example; create a database in access; access database examples; creating a database in access; access databases; requests in access; access reports; access tables; macros in access; access coursework; access database examples; access forms; Database microsoft access; buy a database; creating a database; database examples; download database; course work on DBMS; database examples; ready coursework database. The course database “Car Service” was created in access 2010 and converted to access 2003, therefore it will open in access 2003, 2007, 2010.

It is necessary to create a database of “Car service” accessories. The main button form of the finished “Car Service” database. The “Owners” form with the subordinate “Cars” form. Form "Cars". Work category form. Employees form. Service form. Requests page. Query “Grouping by jobs and employees.” Query “By last name of mechanic”. Request “Search by license plate number”. “Grouping by jobs and employees” report. Report “By the name of the mechanic.” Report “By the name of the mechanic.” The data schema of the finished “Car Service” database displays the relationships of the tables: Owners, Cars, Service, Job Category, Employees. Structure of the table “Cars”: state. number, brand, owner. Structure of the “Owners” table: owner number, full name, cell phone number, driver’s license number. Structure of the “Work Category” table: work code, name of work, description, cost of work. Structure of the “Service” table: service number, vehicle, work category, order readiness date, employee. Structure of the “Employees” table: employee number, cell phone, address, full name. Structure of the query “Grouping by jobs and employees” in design mode. Structure of the query “By last name of mechanic” in design mode. Structure of the “Search by license plate” request in design mode. Macros in design mode.

Introduction 3
SECTION 1. Database development 4

SECTION 2: Modeling Data Structures 7
2.1. Development of a conceptual database model 7
2.2. Developing a logical data model 9
2.3. Converting the entity-relationship model to a relational one
data model 10
SECTION 3. Database Design 12
3.1. Development of tables 12
3.2. Development of data entry forms 17
3.3. Developing database queries 21
3.4. Report development 27
CONCLUSION 30
REFERENCES 31
APPLICATIONS 32

INTRODUCTION

Today, database design (hereinafter referred to as DB) has become important for many organizations that use computer technology to improve the productivity of their work. Databases have become the basis of information systems, and their use is becoming an integral part of the functioning of any enterprise.
Object course work is the study of relational database design technologies.
The subject of the course work is studying the principles of developing relational databases using the example of designing and creating the “Car Service” database.
The purpose of the database design is to display the process of repair activities of a small enterprise
To achieve this goal, the following tasks were set:

There are a huge number of different sources of information regarding the design of relational databases and their applications. From all the proposed resources, those that are suitable for designing databases in the OpenOffice.org Base environment were selected. For example, the books discuss the basic techniques and principles of working and creating databases using Base, which is part of OpenOffice.org. The sources provide basic information about creating tables, forms, queries and reports. The books describe methodological recommendations for the design and implementation of databases.

SECTION 1. Database development

This database is intended for organizations engaged in any type of vehicle maintenance services.
The main functions of the database relate to recording all cars ever in the service center, storing complete information about each car (make, series and technical passport number, chassis number and engine number, color, year of manufacture, etc.).
The database should also store information about each owner who has used the services of a car service at least once. It should be possible to store not only the basic and most necessary information, but also notes, clarifications, descriptions, etc. characteristics of installed spare parts and much other useful information.
The administration of the car service may require the following information:

The DBMS operator can make the following changes:

The reports must provide for the possibility of issuing a certificate about the presence of a malfunction in the owner’s car and a report on the work of the car service (the number of cars being repaired, the name of the employee who repaired them).

The "Car Service" database is designed for the administrator and car service employees who receive and process orders for repairs and car servicing.
The subject area of the task is data on faults, car owners and car service workers.
The information system being developed must perform the following functions:

Output of information in the form of reports:

The following requirements are imposed on the database being developed: data integrity, absence of duplication, absence of many-to-many relationships, absence of recursive relationships, relationships with attributes, multiple attributes.
The information contained in the database meets the following requirements:
significance, completeness, reliability, understandability, effectiveness.
This presentation increases the ease of use of the database; in this case, entering information will be reduced to selecting the necessary information from a list, where possible, which will certainly increase the speed of entering information and help avoid incorrectly entering parameters.
As a result of the creation and implementation of this database, the following performance indicators are required: reducing the time when entering new data and changing old ones and, consequently, increasing labor productivity, as well as timely and complete receipt of information necessary for the administration of the car service.

SECTION 2: Modeling Data Structures

2.1. Development of a conceptual database model

When building a conceptual database model, we will use the recommendations of I.P. Karpova. . As the author notes, the conceptual database model is a high-level object-oriented model of the subject area, representing the object domain as a set of objects that have certain properties and are in certain relationships. The main purpose of developing a high-level data model is to create a model of the user's perception of the data and to reconcile the large number of technical aspects associated with database design. The conceptual data model is not tied to a specific physical database implementation and does not depend on a specific DBMS. A conceptual model is created based on ideas about the subject area of each type of user, which represents a set of data necessary for the user to solve his problems.
The conceptual model for the Autoservice database was designed as an “entity-relationship” model.
The main concepts of the model include such concepts as entity (object), relationship (relationship), entity types, relationship types and attributes.
An entity is a real or imaginable object, information about which must be stored and accessible. In ER model diagrams, an entity is represented as a rectangle containing the name of the entity. Each entity is defined by a set of attributes.
An attribute is a named characteristic of an entity. Its name must be unique for a specific entity type, but can be the same for various types entities. An entity attribute is any detail that serves to clarify, identify, classify, quantify, or express the state of the entity. We will enter the names of the attributes in a rectangle denoting the entity and write it down under the name of the entity.
Relationships are established between entities.
A relationship is a graphically represented association established between two entities. This association is always binary and can exist between two different entities or between an entity and itself (recursive relationship). We denote connections with lines.
Thus, from the description of the subject area we extract all types
entities:
– Customers;
– Orders;
– Masters;
- List of works.
We define each entity its own set of attributes.
The Customer entity is defined by the following set of attributes:

The Orders entity attributes are defined as follows:

The essence of the Master is documented based on the following attributes:

The List of Works entity is defined by the following set of attributes:

In accordance with the domain model, the following conceptual model of the “Car Service” database is presented (Fig. 1).
Fig. 1 Conceptual model of the “Car service” database.

2.2. Development of a logical data model

Converting a local conceptual data model into a local logical model involves removing unwanted elements from conceptual models and converting the resulting models into local logical models. Undesirable elements include:
– many-to-many relationships;
– recursive connections;
– connections with attributes.
The above-mentioned undesirable elements were not found in the created conceptual model.
Logic circuit data is shown in Fig. 2.

Rice. 2. Logical data diagram.

Converting an Entity-Relationship Model to a Relational Data Model
carried out by sequentially performing a number of steps:
– each entity is associated with a relation in the relational data model;
– each entity attribute becomes an attribute of the corresponding relationship;
– the primary key of the entity becomes the primary key of the corresponding relationship. Attributes included in the primary key of a relationship are automatically assigned the required property (NOT NULL). Each relationship corresponding to a subordinate entity is appended with a set of attributes of the main entity, which is the primary key of the main entity. In the relationship corresponding to the subentity, this set of attributes becomes a foreign key.
This process is discussed below.

SECTION 3. Database Design

A table is an object designed to store data in the form of records (rows) and fields (columns).
OpenOffice.org Base provides three different ways creating a database table:

In this work, tables were created using the wizard.
For each relational database table, its structure is given: the composition of the fields, their names, the data type and size of each field, table keys and other field properties.
The development of database tables is carried out sequentially:

The table is the basis of the database, so when developing tables it is recommended to be guided by the following basic principles:

Each table contains information about a specific topic, and each field in the table contains a specific fact about the topic of the table. For each table in the database, you need to define the properties of the tables it contains.
The Car Service database contains four tables:

Rice. 3. Table Customers.

Rice. 4. Table Orders.

This table contains the following attributes:

Rice. 5. List of works.

Rice. 6. Masters.

Let's define a primary key for each entity, and we must take into account that strong entities have only one key field, and weak ones have the same number of connections. When choosing a primary key, we will be guided by the following rules:
– the key must contain a minimum set of attributes;
– you should use the key whose values are least likely to change;
– the key value must have a minimum length.
Based on the above, we will define the following key fields for existing entities:

After breaking the information into tables and defining key fields, you need to choose how the DBMS will combine the related information. To do this, it is necessary to define the relationships between the database tables.
OpenOffice.org BASE supports four types of relationships between tables:
– one-to-one (each record in one table corresponds to only one record in another table);
– one-to-many (each record in one table corresponds to many records in another table);
– many-to-one (similar to “one-to-many” notation);
– many-to-many (one record from the first table can be related to more than one record from the second table, or one record from the second table can be related to more than one record from the first table).
The connections established in the “Car Service” database have already been presented in the previous section in Fig. 2.

A form is an object designed for entering, editing and viewing tabular data in a convenient form.
Forms contain so-called controls that allow you to access data in tables. Control elements are text fields for entering and editing data, buttons, checkboxes, radio buttons, lists, and labels. Creating forms that contain the necessary controls greatly simplifies the data entry process and helps prevent errors.
OpenOffice.org Base forms provide functionality to perform many tasks that cannot be accomplished by other means, allowing you to validate data as you enter it, perform calculations, and provide access to data in related tables using subforms.
OpenOffice.org Base offers several ways to create forms. The simplest of these is to use tools to automatically create forms based on a table or query.
For the Auto Service database, there are four simple forms and three subforms.
Examples of simple forms are shown in Fig. 7-10.

Fig.7. Customer form.

Fig.8. Orders form.

Fig.9. List of works.

Fig. 10. Masters.
A compound form contains a main form and a subform - a subform. A subform is the same form in its content, but it is not used independently, but is always loaded from some form when opening or creating a document. You can do almost everything in a subform that you can do in a form, except that you can't insert another subform into it.
When creating fields in subforms, be sure to take into account that the names of all fields must be unique within the form, along with all subforms that are used in it simultaneously.
Thanks to compound forms, it becomes possible to simultaneously fill out different tables.
Examples of subforms are presented in Fig. 11-13.

Rice. 11. Customer form with the Orders subform.
The Customer form with the Orders subform - provides the input of the necessary data to identify the customer and view the work performed for this order. This form allows you to enter information into the Customer and Orders tables.

Rice. 12. Form Orders with subform Repair work.
This form allows you to enter information into the Orders and Repairs tables.

Rice. 13. Master form with the Orders subform.
The Master form with the Orders subform allows you to control the execution of work by a specific master.

A query is an object that allows you to obtain the necessary data from one or more tables.
Queries are used to extract data from tables and present it to the user in a convenient form. With their help, data is selected, sorted and filtered. You can convert data using a given algorithm, create new tables, automatically populate tables with data imported from other sources, perform simple calculations in tables, and much more.
The peculiarity of queries is that they draw data from the base tables and create on their basis a temporary resulting table (snapshot) - an image of fields and records selected from the base tables. Working with an image is faster and more efficient than working with tables stored on the hard drive.
Upon request, you can get data sorted and filtered as needed. Queries can also be used as record sources for forms, reports, and data access pages.
There are several types of requests:

 Study the specifics of the selected subject area.

 Develop an information and logical model of the “Auto Service” database

 Implement it in MS Access DBMS.

 Compose an “Explanatory Note” for the course project in accordance with the following plan:

Purpose of the database

Database "Car service" is intended for the implementation of receiving and processing orders for work by a car service company.

Of course, he does not aspire to the high title of ACS. Due to the absence of entire blocks necessary for a comprehensive automated control system:

 Accounting,

 Economic bloc

 Planned

 Supplies

 And a number of other blocks.

Only one of the ACS blocks is being implemented - the “Order Reception” workplace: working with customers: receiving and recording orders, organizing their implementation, reporting on the results of work.

Functions Performed by the Database

The database performs the following functions

1. Accounting and storage of information about car service employees. "Mechanics»

2. Entering and storing information about the types of work performed. "Orders»

3. Entering information about customers, customer cars and data about them. "Requests»

4. The “Enter information about orders” form allows you to enter actually order, selecting the customer’s full name (from the list), selecting the type of customer’s car and entering information about it.

In the same place, the composition of the work performed and the names of the car service employees performing them are entered. And also - information about the composition and quantity of spare parts used.

5. The database also provides various reports that allow you to analyze the state of affairs at the car service enterprise.

User categories

The database is intended primarily for car service employees who receive and process orders for repairs and vehicle servicing.

And the reports provided in it are for other divisions of the enterprise, as well as for its managers.

Database design

Let's introduce the following concepts And symbols :

Entities

ESSENCE

Essence - real or imagined an object , information about which must be stored and accessible. In ER model diagrams, an entity is represented as a rectangle containing the name of the entity.

Entities we will denote by rectangles,

Entity Attributes

Attribute – named entity characteristic . Its name must be unique for a specific entity type, but can be the same for different entity types. An entity attribute is any detail that serves to clarify, identify, classify, quantify, or express the state of the entity.

ESSENCE

Attributes

Attribute names we will put it in a rectangle,

denoting essence, under the entity name, and write

in small letters.

Relationships

Connection - this is graphically depicted association , set between two entities. This association is always binary and can exist between two different entities or between an entity and itself (recursive relationship).

Connections– we will designate with lines above which we will put degree of connection (« 1 » or « ∞ » , meaning “many”) and its characteristics.

Key fields

Let's define the concept primary And external keys

Key is a minimum set of attributes whose values can be used to unambiguously find the required instance of an entity. Minimality means that excluding any attribute from the set does not allow the entity to be identified by the remaining ones. Each entity has at least one possible key.

One of them is taken as primary key .

When choosing primary key preference should be given non-composite keys or keys composed of a minimum number of attributes. It is also inappropriate to use keys with long text values (it is preferable to use integer e attributes).

It is not allowed for an entity's primary key (any attribute participating in the primary key) to accept indefinite meaning. Otherwise, a contradictory situation will arise: someone without individuality will appear, and, therefore, not existing entity instance. For the same reasons, it is necessary to ensure uniqueness primary key.

Foreign keys

If entity WITH connects entities A And IN, then it must include foreign keys corresponding to the primary keys of entities A and B.

If entity IN denotes entity A, then it must include a foreign key corresponding to the entity's primary key A.

Note:

1. Since the developers of the MS Access DBMS initially took into account the problems arising with primary And foreign keys, a special field type was introduced into Access - KEY FIELD. Its type is COUNTER.

Access does not require its mandatory inclusion in the table. But urgently offers.

The features of this field type are:

When entering new entry– a new one is AUTOMATICALLY formed in this field, unique, non-repetitive numeric value.

Field cannot accept indefinite meaning.

Field – automatic indexed.

Manually changing the value of this field impossible.

Therefore the problem key fields And foreign keys in Access the solution is simple:

In the main table(entities) create special key field. We will have it primary key .

We enter a copy of it (with the same name) into the subordinate tables. It will be theirs external key .

We connect the main and subordinate tables using these fields. That's all. The connection is complete!

2. The developers introduced a tool into Access called « Data Schema »

Which allows not only to tie tables, but also indicate for each connection:

her type(“one-to-one”, “one-to-many”, etc.)

and her characteristics: Ensuring integrity, as well as cascading updates and deletions of information from related tables and fields.

What must be indicated when constructing ER– models Database.

In particular, that is why Access is ideal as a programming system for implementing ER models.

When implementing ourER– models inAccessWe will take advantage of all these opportunities.

Send your good work in the knowledge base is simple. Use the form below

Students, graduate students, young scientists who use the knowledge base in their studies and work will be very grateful to you.

Posted on http://www.allbest.ru/

FIRST HIGHER TECHNICAL INSTITUTION OF RUSSIA

MINISTRY OF EDUCATION AND SCIENCE OF THE RUSSIAN FEDERATION

Federal State Budgetary Educational Institution of Higher Professional Education

"NATIONAL MINERAL RESOURCES UNIVERSITY "MINING"

Course work

"Database - car service"

Discipline: Applied programming

Completed by: Stepanova K.A.

Checked by: Matyukhin S.A.

St. Petersburg 2013

Introduction

1. Description of the subject area

2. Description of the database structure

3. Tables

4. Terms of reference

5. Description of the program

6. Components

7. User diagram

8. Interface

Conclusion

Bibliography

Application

Introduction

In our age, the age of digital technology, computers play a vital role. Now in every organization - be it government agencies or private firms, everything is computerized, and this is due to very high computing power. The calculation of even the most complex processes and assigned tasks is carried out in the shortest possible time, and the time factor often plays a critical role in most assigned tasks. The computing power and memory capacity of computers have become incredibly large in recent years, and their prices have dropped significantly, this has contributed to the mass computerization of absolutely all sectors of human activity. Now it is difficult to imagine life without a smart machine that simplifies and speeds up a huge number of tasks. The usefulness of a computer is negated in the absence of specialized software, without which the “iron assistant” becomes useless. In this work we'll talk about the creation of such an important, and in most organizations, the main program, the name of which is a database. In this particular case, a car service database.

1. Description of the subject area

The goal of the task is to obtain software product, which allows you to store information about service clients, defects in their cars, ensuring the efficiency and reliability of data processing.

The car service database is intended for car service operators and provides access to information about the car brand, date of visit, malfunction, car vin number, as well as information about clients: phone number, etc.

The effectiveness of the program lies in reducing the processing time and searching for the necessary information.

The need to automate this task is due to the fact that the selection of the necessary data for reports and recording the work of engineers is usually done manually or using Excel, spending a significant amount of time on this. This program It also provides the ability to search, filter and sort data.

No special programming knowledge is required to work with the program.

2. Description of the database structure

Table relationships:

The custumers table is linked to the masters table using a 1:N relationship using the vin_number field

The customers table is connected to the calculation table using a 1:1 relationship using the vin_number field

3. Tables

Table 1: Clients (leading table)

Table 2: Masters (slave)

Table 3: Masters (slave)

software car service database editing

4. Technical task

Reason for development:

The teacher's assignment for conducting practical classes and completing course work.

Purpose of development:

The program is designed to automate the work of car service operators.

Program requirements:

· Should automate the work of the car service operator

Information must be permanently stored on the computer's hard drive

· It must be possible to view the database with the ability to delete specified information from it.

Reliability requirements:

· The program must process erroneous user actions and inform him about it.

· The program must provide control of input information.

5. Program description

private void Form1_Load(object sender, EventArgs e) () // loading main components

private void b_add_Click(object sender, EventArgs e) () // adding a new entry

private void b_replace_Click(object sender, EventArgs e) () // edit entry

private void b_cancel1_Click(object sender, EventArgs e) () // cancel the action

private void b_save_Click(object sender, EventArgs e) () // saving changes

private void b_record1_Click(object sender, EventArgs e) () // write data

private void b_delete_Click(object sender, EventArgs e) () // delete data

private void b_exit_Click(object sender, EventArgs e) () // exit the program

6. Components

7. Scheme foruser

Table 1 “Clients” and table 2 “Masters” are connected by a “One-to-many” relationship using the vin_number field.

Table 1 “Customers” and table 3 “cost” are related by a “One-to-one” relationship using the vin_number field.

8. Interface

Adding a new entry

Editing an old post

Deleting an entry

Sort by date of visit

Signed tables

The main table of the Auto Service program includes:

1. List of customer cars

2. Date of application by the car owner

3. Malfunction

4. Client phone number

5.VIN number

6. The client list is managed using buttons (Add/Replace/Delete)

7. Display and record salon clients

8. Sorting

10. Choice of masters

11. Name of tables

12. Exit the program

Conclusion

The result of the work was the creation software servicing the workplace of a car service operator.

During the coursework, skills were acquired in the field of building and programming databases in the C# programming language.

Bibliography

1. Matyukhin S.A. “Programming in C# object-oriented approach” - educational and methodological complex 2013

2. A. Hejlsberg, M. Torgersen, S. Wiltamut, P. Gold C# programming language. Classic Computer Science. 4th Edition = C# Programming Language (Covering C# 4.0), 4th Ed. - St. Petersburg: "Peter", 2012. - 784 p. -- ISBN 978-5-459-00283-6

3. E. Stillman, J. Green Learning C#. 2nd edition = Head First C#, 2ed. - St. Petersburg: "Peter", 2012. - 704 p. -- ISBN 978-5-4461-0105-4

4. Andrew Troelsen C# 5.0 programming language and the .NET 4.5 Framework, 6th edition = Pro C# 5.0 and the .NET 4.5 Framework, 6th edition. - M.: Williams, 2013. - 1312 p. --ISBN 978-5-8459-1814-7

5. Joseph Albahari, Ben Albahari C# 5.0. Directory. Full description of the language = C# 5.0 in a Nutshell: The Definitive Reference. - M.: "Williams", 2013. - 1008 p. --ISBN 978-5-8459-1819-2

6. Herbert Shildt. C# 4.0: complete guide= C# 4.0 The Complete Reference. -- M.: "Williams", 2010. -- P. 1056. -- ISBN 978-5-8459-1684-6

Application. Codeprograms

using System.Collections.Generic;

using System.ComponentModel;

using System.Data;

using System.Drawing;

using System.Linq;

using System.Text;

using System.Threading.Tasks;

using System.Windows.Forms;

public partial class Form1: Form

InitializeComponent();

groupBox1.Visible = false;

groupBox2.Visible = false;

private void customersBindingNavigatorSaveItem_Click_1(object sender, EventArgs e)

this.Validate();

this.customersBindingSource.EndEdit();

this.tableAdapterManager.UpdateAll(this.db_autoDataSet);

private void Form1_Load(object sender, EventArgs e)

// TODO: This line of code loads data into the "db_autoDataSet.masters" table. You can move, or remove it, as needed.

this.mastersTableAdapter.Fill(this.db_autoDataSet.masters);

// TODO: This line of code loads data into the "db_autoDataSet.calculation" table. You can move, or remove it, as needed.

this.calculationTableAdapter.Fill(this.db_autoDataSet.calculation);

// TODO: This line of code loads data into the "db_autoDataSet.customers" table. You can move, or remove it, as needed.

this.customersTableAdapter.Fill(this.db_autoDataSet.customers);

private void b_exit_Click(object sender, EventArgs e)

private void button5_Click_1(object sender, EventArgs e)

private void b_add_Click(object sender, EventArgs e)

groupBox1.Visible = true;

b_replace.Visible = false;

b_delete.Visible = false;

b_exit.Visible = false;

b_add.Visible = false;

b_exit2.Visible = false;

b_save.Visible = false;

textBox1.Text = "";

textBox2.Text = "";

textBox3.Text = "";

textBox4.Text = "";

textBox5.Text = "";

private void b_replace_Click(object sender, EventArgs e)

textBox10.Text = customers DataGridView.CurrentRow.Cells.Value.ToString();

textBox9.Text = customers DataGridView.CurrentRow.Cells.Value.ToString();

textBox8.Text = customers DataGridView.CurrentRow.Cells.Value.ToString();

textBox7.Text = customers DataGridView.CurrentRow.Cells.Value.ToString();

textBox6.Text = customers DataGridView.CurrentRow.Cells.Value.ToString();

textBox6.ReadOnly = true;

groupBox2.Visible = true;

b_add.Visible = false;

b_delete.Visible = false;

b_exit.Visible = false;

b_exit2.Visible = false;

b_replace.Visible = false;

b_save.Visible = false;

private void b_cancel1_Click(object sender, EventArgs e)

b_add.Visible = true;

b_delete.Visible = true;

b_exit.Visible = true;

b_exit2.Visible = true;

b_replace.Visible = true;

b_save.Visible = true;

groupBox1.Visible = false;

private void b_cancel2_Click(object sender, EventArgs e)

b_add.Visible = true;

b_delete.Visible = true;

b_exit.Visible = true;

b_exit2.Visible = true;

b_replace.Visible = true;

b_save.Visible = true;

groupBox2.Visible = false;

private void b_save_Click(object sender, EventArgs e)

customersBindingNavigatorSaveItem_Click_1(sender, e);

private void b_record1_Click(object sender, EventArgs e)

DataTable table = db_autoDataSet.Tables;

DataRow row = table.NewRow();

row = textBox1.Text;

row = Convert.ToDateTime(textBox2.Text);

row = textBox3.Text;

row = textBox4.Text;

row = textBox5.Text;

table.Rows.Add(row);

groupBox1.Hide();

b_replace.Visible = true;

b_delete.Visible = true;

b_exit.Visible = true;

b_add.Visible = true;

b_exit2.Visible = true;

b_save.Visible = true;

private void b_record2_Click(object sender, EventArgs e)

DataTable table = db_autoDataSet.Tables;//12 linked dynamically. table table with the first file from the database

vinRab = Convert.ToInt64 (customersDataGridView.CurrentRow.Cells.Value.ToString()); //13 got the vin of the current record

DataRow row = table.Rows.Find(vinRab);//14 combined dynamic. row row with a record of the vin file with shifrRab and moved the DataSet to the “editing” state, in which it allows you to change field values

row = textBox10.Text;//15 was written to the second field of the row given from the window

row = Convert.ToDateTime(textBox9.Text);// 15 was written to the third field of the row row

row = textBox8.Text; //15 was written in the fourth field of the line row row = textBox7.Text;

row = textBox6.Text;

table.AcceptChanges();//15 the AcceptChanges command allows you to accept changed field values

groupBox2.Hide();//16

b_replace.Visible = true;

b_delete.Visible = true;

b_exit.Visible = true;

b_add.Visible = true;

b_exit2.Visible = true;

b_save.Visible = true;

private void b_delete_Click(object sender, EventArgs e)

// deleting the line under the cursor

// first build a warning so as not to make an erroneous deletion

string s1, s2, s3, s4, s5, message;

DialogResult result; // 18

int ind = customersDataGridView.CurrentRow.Index;

s1 = customersDataGridView.CurrentRow.Cells.Value.ToString();

s2 = customersDataGridView.CurrentRow.Cells.Value.ToString();

s3 = customersDataGridView.CurrentRow.Cells.Value.ToString();

s4 = customersDataGridView.CurrentRow.Cells.Value.ToString();

s5 = customersDataGridView.CurrentRow.Cells.Value.ToString();

message = "Car brand = " + s1 + "\nDate of visit = " + s2 + "\n Fault = " + s3 + "\n Client phone number = " + s4 + "\n Vin number" + s5;

// the result variable can take the values either DialogResult.Yes or DialogResult.No

result = MessageBox.Show(message, "Delete next entry? ",

MessageBoxButtons.YesNo, MessageBoxIcon.Question);

if (result == DialogResult.Yes)//The line is deleted

(// 20 The current table from the customersDataGridView of type DataGrid is written to the buffer table

CurrencyManager CurMng = (CurrencyManager)customersDataGridView.BindingContext;

if (CurMng.Count > 0) // if the table is not empty

CurMng.RemoveAt(CurMng.Position); // removing the marked position

// here result == DialogResult.No and deletion is rejected

// exit the procedure

Posted on Allbest.ru

OBD car service. Download the access database Car service. Functions Performed by the Database

Technology of creation Database "Auto service"

Purpose of the database

Functions Performed by the Database

User categories

Send your good work in the knowledge base is simple. Use the form below

Completed by: Stepanova K.A.

Checked by: Matyukhin S.A.

Similar documents