Development of an automated information system for managing telephone operator services. Description of accounting for sales of goods and services of a cellular operator. Ways to protect store personnel from industrial hazards

About the automated information system “System for monitoring information systems of the city of Moscow”

In order to ensure interdepartmental information interaction and provide access to information systems and resources of the city of Moscow, it decides:

1. Approve the Regulations on the automated information system "System for monitoring information systems of the city of Moscow" (appendix).

4.6. Automation of the process of collecting information on the functioning of information systems and resources of the city of Moscow and increasing the efficiency of its processing in order to ensure the stable functioning of information systems of the city of Moscow and high-quality provision of communication services for the needs of executive bodies and government agencies subordinate to them of the city of Moscow.

4.7. Increasing the efficiency of using funds from the budget of the city of Moscow, provided for financial support for the operation of information systems of the city of Moscow and the provision of communication services to executive bodies and government institutions of the city of Moscow subordinate to them.

5. SMIS consists of the following subsystems:

5.1. Unified Directory Service.

5.3. Unified system for monitoring and administering telecommunication services of executive bodies.

6. The main functions of SMIS are:

6.1. Administration of user accounts and rights for access to information systems of the city of Moscow, ensuring authorization of users at workplaces and in information systems of the city of Moscow using a single account.

6.2. Prompt collection and analysis of information on the performance of information systems of the city of Moscow, informing executive bodies and government agencies of the city of Moscow subordinate to them about failures in the operation of information systems and the provision of communication services.

6.3. Collection of statistical information on the functioning of information systems in the city of Moscow.

6.4. Accounting, monitoring and management of communication services provided to executive bodies and government agencies subordinate to them in the city of Moscow, as well as information resources used to ensure the provision of communication services.

6.5. Processing applications from executive bodies for connection and/or disconnection of communication services, changing the conditions for their provision.

6.6. Collection and synthesis of information about the incorrect operation of information systems of the city of Moscow, failures in the provision of communication services, received from participants in information interaction using SMIS, which is the basis for conducting claims work.

6.7. Automated interaction with the information systems of telecom operators providing communication services in the interests of executive bodies and government agencies subordinate to them in the city of Moscow on the basis of concluded government contracts, in order to ensure control of the quality, volumes and timing of the provision of communication services.

6.8. Generating statistical and operational reports on the functioning of information systems in the city of Moscow and the quality of communication services provided in the interests of executive bodies and government agencies subordinate to them in the city of Moscow.

7. Participants in information interaction using SMIS are users and suppliers of information, performers of services (work) provided for the operation of information systems of the city of Moscow, communication services, and the SMIS operator.

9. Suppliers of information are executive bodies, government agencies of the city of Moscow and performers of services (works) for the operation of information systems of the city of Moscow and the provision of communication services.

10. Information providers:

10.1. Place in SMIS information about the equipment of information and telecommunication systems used and its configuration parameters, about the required communication services and their parameters, about failures that have arisen, malfunctions in the operation of information systems and resources of the city of Moscow, about the inadequate quality of provision of communication services and then update it in the following manner and deadlines set by .

10.2. Appoint persons authorized to carry out operations for posting information in SMIS, and arrange for authorized persons to receive identifiers (logins) and passwords for working in SMIS.

10.3. Ensure the completeness, reliability and relevance of the information provided in the SMIS, as well as the entry of the specified information into the SMIS within the established time limits.

11. The procedure for information interaction between its participants, the regulations for access and work in SMIS, the timing of the provision of information in SMIS are determined.

12. SMIS operator:

12.1. Provides methodological guidance for the use of SMIS, including providing consultations to users and information providers on technical support and operation of SMIS.

12.2. Provides operation and technical support for SMIS operation around the clock.

12.3. Organizes the implementation of work on the development (modernization) and operation of SMIS.

12.4. Connects to SMIS information systems of the city of Moscow that meet the technical requirements established by.

12.5. Provides interaction with the information systems of those performing work on the operation of information systems of the city of Moscow and the provision of communication services.

12.6. Provides differentiation of access rights to SMIS, keeps records and statistics of user activity in accordance with the regulations for access and work in SMIS.

12.7. Organizes work to ensure the safety of information posted in SMIS.

12.8. Provides consulting support to participants in information interaction on the use of SMIS.

13. Connection and interaction of information systems of the city of Moscow using SMIS is carried out in accordance with the requirements for such connection and interaction, approved.

14. The SMIS operator is not responsible for the content, quality and reliability of information transmitted to SMIS by information providers.

15. Certain functions of the operator may be transferred to a subordinate government agency of the city of Moscow or another organization by decision in accordance with the legislation of the Russian Federation and the city of Moscow.

store operator base interface

Introduction

1. Domain analysis

1.1 Description of the store for the provision of mobile operator services

2 Technical means

3 Description of accounting for sales of goods and services of a cellular operator

3.1 Description of business processes

3.2 Data analysis

4 Review of existing analogues

4.2 AIS "MTS Service 1.15.45"

4.3 AIS "ETK: Personal Account 1.3"

5 Justification for the development of the automated information system "Operator"

Chapter Conclusion

2. Review of development tools

2.1 Selecting a DBMS

1.1 Oracle Database

1.2 DBMS MS SQL Server-2008

1.3 DBMS Firebird 2.1

2.2 Selecting a database development environment

2.2.1 IBExpert 2009

2.2 Microsoft Access

2.3 Selecting a Software Development Environment

2.3.1 Delphi 2010

3.3 Microsoft Visual Studio

Chapter Conclusion

Relational Database Design

1 Development of table structure

2 Normalization of tables

3 Design of integrity constraints

4 Development of data sampling operations

5 Issue of access rights

Chapter Conclusion

Designing the "Operator" client application

1 Description of program modules

2 Delivery package and system requirements

3 Description of the user interface

3.2 Main window of the program

3.3 Main menu

3.4 "Reporting"

Chapter Conclusion

5. Ensuring life safety of work in the showroom of a cellular operator

5.1 Organization of an automated workstation for store employees

2 Dangerous and harmful production factors accompanying the activities of PC users in a store

3 Ways to protect store personnel from industrial hazards

4 Automotive technical calculation of lighting in a showroom providing cellular operator services

Chapter Conclusion

Conclusion

List of sources used

Introduction

It is difficult to imagine the modern world of information technology without the use of databases.

Almost all systems are, to one degree or another, associated with the functions of long-term storage and processing of information.

In fact, information becomes a factor determining the effectiveness of any field of activity.

Information flows have increased and requirements for data processing speed have increased, and now most operations cannot be performed manually; they require the use of the most promising computer technologies.

Any administrative decisions require a clear and accurate assessment of the current situation and possible prospects for its change.

Databases reflect a certain part of the real world. This information should, if possible, be recorded in the database once, and all users who need this information should be able to work with it

The purpose of this final qualifying work is to develop an automated information system for managing the services of a telephone operator.

Automation of the store for the provision of telephone operator services will allow employees to get rid of many routine processes, which will ensure the fastest, most complete and high-quality service for subscribers.

Main goals:

Conducting an analysis of the activities of the store in providing telephone operator services.

Development of an information database.

Program development.

Conducting an analysis to ensure the safety of a store providing services to a cellular operator.

1. Domain analysis

1 Description of the store for the provision of mobile operator services

The main activity of the store is the provision of mobile communication services

This is a legal entity that has a registered trademark, brand name, current and other accounts in rubles in banking institutions.

The salon store includes administration, accounting, personnel department, and management department. The general management of the enterprise is carried out by the General Director. Subordinate to him are the Deputy Director for Economics and Finance. Direct management is exercised by the General Director.

The main divisions supporting the activities of the store are:

.accounting - calculation and issuance of salaries, tax reporting;

.management department - registration of clients and connections, reporting;

2 Technical means

Shops providing telephone services use information technologies that automate administrative and commercial activities. The salons have a modern material base, including computer equipment and peripherals, as well as a local computer network (LAN), which allows for centralized storage and processing of information. The network covers all departments.

The enterprise uses the following software and hardware.

Software:

Ø Windows 7 is an operating system of the Windows NT family of Microsoft Corporation.

Ø Windows Server 2008 is an operating system of the Windows NT family from Microsoft, which is designed to work on servers.

Ø 1C: Enterprise 8.3.

Ø Kaspersky Anti-Virus 2012 - the program provides anti-virus protection, protection against spam and hacker attacks.

Hardware:

The enterprise departments have computers with the following configuration:

Ø Processor INTEL Core i3 3240 LGA 1155 OEM

Ø Memory module HYNIX DDR3- 2GB 1333 DIMM OEM

Ø Hard drive WD Caviar Blue WD5000AAKX 500GB HDD SATA III

All computers are connected into a single local area network and have access to the Internet.

Information systems and application software systems:

Ø 1C: Accounting 8.3 is an automated information system created to automate accounting and tax accounting, including the preparation of mandatory (regulated) reporting.

Ø 1C: Enterprise 8.3 - is a set of software modules designed for the development and use of solutions (configurations) for accounting and automation of business activities of enterprises, and configurations or a set of configurations.

Ø MS OFICCE 2010 - a set of programs for preparing documentation.

1.3 Description of accounting for sales of goods and services of a cellular operator

The management department performs the following functions:

client connection

organizing the acceptance of an order for connecting the services of a cellular operator from a client;

accepting payments from clients;

connection status tracking;

drawing up a report on connections and payments;

Salon director - provides leadership for development and operation, conducts internal audits, analyzes their results, and monitors the implementation of corrective measures.

Sales Manager - implements connection of services.

1.3.1 Description of business processes

To implement the services of a cellular operator, the following business processes are required:

.Connecting a new subscriber - first a new subscriber is registered, then his data is entered into the database, the client selects a tariff plan, then an agreement on a new connection is concluded, payment is accepted and the client is given a payment receipt;

.Connection of the selected service - after selecting the service, an agreement is drawn up, payment is accepted and a payment receipt is issued

.Payment registration - after funds are deposited into the subscriber’s personal account, a payment receipt is issued;

.Generation of reporting documents:

Ø Generating the “Price List” report - generating information about prices for current tariffs and services;

Ø Generating the “Sales Analysis” report - creating a list of debtor clients whose debt amount exceeds the specified amount;

Ø Generating the "Payment Status" report - generating information about payments for each client.

Business rules are a set of conditions that govern a business event so that it occurs as desired for the business or customer.

Let's consider the Business rules that are necessary for the implementation of services:

.When ordering a service, the payment established by the store must be paid.

.The conclusion of an agreement to connect a new client occurs after full payment of the cost of the selected tariff and after the client provides an identification document.

.Before depositing funds into the subscriber's account, it is necessary that payment be made and the subscriber be registered in the store's database.

3.2 Data analysis

It is necessary to determine the data that will be used in the designed database. This information can be divided into the following types:

information about the agreement;

information about subscribers;

information about tariffs and services;

information about payments;

sales information.

Information about the agreement includes: subscriber code, subscriber personal account number, agreement number, subscriber number, name of the tariff or service, cost of the tariff or service, date of conclusion and amount of payment.

Information about subscribers includes: subscriber's full name, passport details, address and date of birth.

Information about tariffs and services includes: name of the tariff or service, cost.

Payment information includes: buyer's full name, subscriber number, payment amount, payment date.

Information about the sale includes: information about the tariff or individual service, full name of the buyer, passport details of the buyer, price of the tariff or service, date of sale.

3.3 Study of information flows

Only store employees will work with the system, namely:

Sales consultants who will register new connections, change or add subscriber data, as well as deposit funds into subscribers’ accounts

A manager who will make various kinds of changes related to the catalog of services and tariffs.

The administrator, in turn, will view the list of debtors and generate reports.

The following information will serve as input information:

About clients, the following information will be entered: full name, series and number of passport, by whom and when issued, date of birth, address.

About the tariffs: name of the tariff, cost of incoming and outgoing calls, SMS and Internet traffic.

About the services: name, cost, description of the service and notes.

The following reports will be generated by the client program as output information:

"Price List" report - this report will display a list of prices for current tariffs and services;

"Sales Analysis" report - this report will display a list of services and connections sold for the year;

"Payment Status" report - this report displays a list of subscribers to whose account funds were deposited by the operator over the last 2 days.

4 Review of existing analogues

Today, there are enough automated systems created for cellular operators, but in most cases they are designed for a specific operator, have limited capabilities, or are part of a large set of programs.

4.1 AIS "Mobile Operators"

Description: The "Mobile Operators" program allows you to get information by phone number:

-mobile operator

-date of registration (of the company)

-region

-official website of the Operator

-page for free SMS sending

Thanks to such information, the subscriber will always know who called him or wrote an SMS and from where.

Before calling a mobile phone, we recommend that the subscriber use this program to find out which region and mobile operator the specified number belongs to.

Otherwise, it may happen that a call to another region will cost the subscriber too much.

In addition, this AIS allows you to quickly and easily send free SMS to any number.

The program does not require installation and can be launched directly from a USB drive or CD.

The program is free, no registration required. The appearance of the AIS "Mobile Operators" is presented in Figure 1.

Fig.1. "Appearance of AIS Mobile operators"

4.2 AIS "MTS Service 1.15.45"

Description: This is an application developed for iOS, with which a subscriber can quickly find out about the status of his mobile account, connect and disconnect services, change his tariff plan and much more.

The main menu and search are shown in Figure 2.

Rice. 2. "Main menu AIS MTS Service"

1.4.3 AIS "ETK: Personal Account 1.3"

Description: The program provides a convenient tool for managing the personal account of a subscriber of the cellular operator CJSC "ETK" (Yeniseitelecom). The program consists of three modules: personal account, SMS service, help.

Your personal account allows you to manage both your personal account and others (your own accounts, corporate, etc.). Works only when connected to the Internet (Wi-Fi, GPRS, 3G). The following operations are available:

-changing the list of services;

-replenishment of balance;

-blocking/unblocking a number, etc. The service allows you to manage the personal account of only the active SIM card. No internet connection required. Operations such as managing the list of services and replenishing the balance are available.

Help is a short reference guide for the subscriber, built into the program. No internet connection required.

The main program window is shown in Figure 3.

Fig.3. "Main window of AIS ETC: Personal Account 1.3"

1.5 Rationale for the development of the automated information system "Operator"

The following disadvantages were identified in existing analogues:

-there are no flexible mechanisms for restricting access to data

-insufficient functionality

-no multi-user access

-high price

Suitable new technologies

A modern solution to the above problems is the development of the AIS "Operator", since:

flexible interface

possibility of creating a distributed information base

low price for the final product

Relevance - the ability to quickly reflect changes.

Completeness of information, that is, providing the most complete information about orders, payments, and cars.

Convenience - clear interface.

Chapter Conclusion

The creation of this automated information system will allow us to take into account all the features for the implementation of services of a cellular operator.

Expected effect from implementation:

Ø Relevance - the ability to quickly reflect changes.

Ø Completeness of information, that is, providing the most complete information about the compiled estimate.

Ø Convenience - clear interface.

Ø Consistency and reliability of data.

Ø Consolidation of information in the enterprise.

2. Review of development tools

1 Selecting a DBMS

Database management system (DBMS) ‑a set of software designed for creating, maintaining and using a database.

Based on capabilities, there are two groups of DBMS:

Full-featured DBMS ‑the most powerful, multi-user, with data protection, copying and recovery systems (Oracle, Microsoft SQL Server, Informix, DB/2), but more complex DBMS.

Personal DBMS ‑with limited capabilities, but easier to use (Access, Visual FoxPro, Paradox, Clipper, dBase, Clarion, DataEase, DataFlex, R: BASE).

1.1 Oracle Database

Oracle is one of the most powerful modern DBMSs designed for implementing corporate-level databases, which places severe demands on the server. It can run on most operating systems: Windows-NT, -2000, Linux, UNIX, AIX, Nowell Netware. And this, in turn, allows you to choose the most convenient server platform for corporate tasks. For example, if an organization prefers to use non-Windows operating systems, then it can easily afford it. Some organizations may focus on solutions based on UNIX systems, which are renowned for their reliability and stability as a server platform, while continuing to use the Windows familiar to users on client computers.

The main advantages of Oracle include support for very large databases (up to 64 GB), powerful development and administration tools, support for multiprocessing and two language environments, as well as integration with the Web. At the same time, the program imposes serious hardware requirements and a high price.

1.2 DBMS MS SQL Server-2008

MS SQL Server-2008 has become widespread both in our country and abroad, since it offers a wide range of administration services and is easily scalable. This allows it to be used in information systems for medium-sized businesses and large computer information systems (CIS).

The MS SQL Server platform is based on the Windows environment.

The main advantage of the program is its close integration with Microsoft software products and the ability to export/import data into most common data formats, which allows you to use MS SQL Server as a central data storage. 2008 Express is a free edition of the SQL Server system. It is ideal for database training, for building small server applications, and for distribution by independent software vendors. This release includes a number of powerful features, including SQL Server 2008 Reporting Services, a server-based platform for creating and sending classic and interactive reports, and SQL Server 2008 Management Studio Express, a graphical environment that simplifies database management.

-Power

-Ability to develop high-performance applications that rely on the security, reliability, and scalability of the SQL Server engine.

-Performance

-SQL Server Express's tight integration with Visual Studio designers and SQL Server Management Studio helps you develop applications faster.

-Flexibility

-Create lightly coupled applications that can run offline and automatically synchronize with a central database.

Key Applications:

-Entry-level databases, educational databases

-Building powerful desktop applications

-Free distribution rights for independent software developers.

1.3 DBMS Firebird 2.1

Firebird (FirebirdSQL) is a compact, cross-platform, free database management system (DBMS) running on Linux, Microsoft Windows and a variety of Unix platforms.

The advantages of Firebird include a multi-version architecture (parallel processing of operational and analytical queries: reading users do not block writers), compactness (5Mb distribution), high efficiency and powerful language support for stored procedures and triggers. Used in various industrial systems (warehouse and business , financial and public sectors) since 2001. It is a commercially independent project of C and C++ programmers, technical advisors and developers of multi-platform database management systems, based on the source code released by Borland Corporation on July 25, 2000 as a free version of Interbase 6.0. supports SQL-92 Entry Level 1 and implements most of the SQL-99 standard with some very useful additions. This includes DML/DDL expressions, FULL/LEFT/RIGHT JOIN syntax, UNION, DISTINCT expressions, subqueries (IN, EXISTS), built-in functions (AVG, SUM, MIN, MAX, COALESCE, CASE, ..), integrity constraints ( PRIMARY KEY, UNIQUE, FOREIGN KEY), and all common SQL data types. Supports many access methods, including: native component sets for C/C++, Delphi, classes for ADO, ODBC, JDBC (Jaybird), drivers for Python, PHP, OLE DB driver, dbExpress, .NET data provider and direct access using the server client library (fbclient.dll or GDS32.dll) supports large databases. Databases can be located in several files, the size limit of which depends on the operating system. The theoretical limit is currently 64TB for a single database file, so the main limitations are imposed by the file system and hard drive space. is the database server. A single Firebird server can handle several hundred independent databases, each with multiple user connections. It is completely royalty free even for commercial use.

2 Selecting a database development environment

2.1 IBExpert 2009

IBExpert is a GUI shell designed for developing and administering InterBase and Firebird databases, as well as for selecting and changing data stored in the databases.

The developers point out the main advantages of IBExpert:

Ø support for InterBase versions 4.x, 5.x, 6.x, 7.x; Firebird 1.x, 2.x, 3.x; Yaffil 1.x;

Ø

Ø

Ø

Ø auto-completion of SQL code (names of tables, fields, etc.)

Ø

Ø search in metadata;

Ø

Ø

Ø metadata reports;

Ø

Ø export data to various formats. has many components that make work easier: a visual editor for all database objects, a SQL editor and script executor, a debugger for stored procedures and triggers, an area builder, a tool for importing data from various sources, its own scripting language, as well as database designer.

2.2 Microsoft Access

Microsoft Access is a relational DBMS from Microsoft Corporation. Has a wide range of features including linked queries, communication with external tables and databases. Thanks to the built-in VBA language, you can write applications that work with databases in Access itself.

Ø Main components of MS Access:

Ø table builder;

Ø screen form builder;

Ø SQL query builder (the SQL language in MS Access does not comply with the ANSI standard);

Ø builder of reports for printing.

They can call scripts in the VBA language, so MS Access allows you to develop applications and databases almost from scratch or write a wrapper for an external database. Jet Database Engine (Microsoft Jet Database Engine), which is used as the MS Access database engine is file-server DBMS and therefore applicable only to applications that work with small amounts of data and with a small number of users simultaneously working with this data. Access itself lacks a number of mechanisms needed in multi-user databases, such as triggers.

Built-in means of interaction between MS Access and external DBMSs using the ODBC interface remove the limitations inherent in the Microsoft Jet Database Engine. MS Access tools that allow you to implement such interaction are called “linked tables” (a connection with a DBMS table) and “queries to the server” (a query in a SQL dialect that the DBMS “understands”).

To build full-fledged client-server applications based on MS Access, Microsoft Corporation recommends using MS SQL Server DBMS as a database engine. At the same time, it is possible to combine database management tools and development tools with the inherent simplicity of MS Access.

There are also known implementations of client-server applications based on Access 2003 with other DBMSs, in particular MySQL

3 Selecting a Software Development Environment

3.1 Delphi 2010

Delphi is an integrated software development environment for Microsoft Windows, Mac OS, iOS and Android in the Delphi language (formerly called Object Pascal), originally created by Borland and currently owned and developed by Embarcadero Technologies. Embarcadero Delphi is part of the Embarcadero RAD Studio suite and comes in four editions: Starter, Professional, Enterprise and Architect.

The environment is designed for rapid development (RAD) of application software for operating systems Windows, Mac OS X, as well as IOS and Android. Thanks to the unique combination of language simplicity and machine code generation, it allows you to directly, and, if desired, at a fairly low level interact with the operating system, as well as with libraries written in C/C++. The created programs are not dependent on third-party software, such as Microsoft .NET Framework, or Java Virtual Machine. The allocation and release of memory is controlled mainly by user code, which, on the one hand, tightens the requirements for code quality, and on the other hand, makes it possible to create complex applications with high requirements for responsiveness (real-time work). Cross-compilers for mobile platforms provide automatic counting of references to objects, making it easier to manage their lifetime.

Eclipse is a free integrated development environment for modular cross-platform applications. Developed and supported by the Eclipse Foundation.

The most well-known applications based on the Eclipse Platform are the various "Eclipse IDEs" for software development in a variety of languages ​​(for example, the most popular "Java IDE", which was supported initially, does not rely on any proprietary extensions, uses a standard open API to access the Eclipse Platform )

Eclipse was originally developed by IBM as a successor to the IBM VisualAge development environment, as a corporate IDE standard for development in various languages ​​for IBM platforms. According to IBM, design and development cost $40 million. The source code was completely open sourced and made available after Eclipse was released to a community independent of IBM for further development.

Eclipse 3.0 (2003) adopted the OSGi service platform specifications as the runtime architecture. Since version 3.0, Eclipse has ceased to be a monolithic IDE that supports extensions, and itself has become a collection of extensions. It is based on the OSGi and SWT/JFace framework, on the basis of which the next layer is developed - RCP (Rich Client Platform, a platform for developing full-fledged client applications). RCP serves as the basis not only for Eclipse, but also for other RCP applications such as Azureus and File Arranger. The next layer is Eclipse itself, which is a set of RCP extensions - editors, panels, perspectives, the CVS module and the Java Development Tools (JDT) module.

Since 2006, the Eclipse Foundation has coordinated an annual Simultaneous Release, which occurs in June. Each release includes the Eclipse platform, as well as a number of other Eclipse projects. It serves primarily as a platform for developing extensions, which is why it has gained popularity: any developer can extend Eclipse with his own modules. There are already Java Development Tools (JDT), C/C++ Development Tools (CDT), developed by QNX engineers together with IBM, and tools for Ada languages ​​(GNATbench, Hibachi), COBOL, FORTRAN, PHP, etc. from various developers. Many extensions complement the Eclipse environment with managers for working with databases, application servers, etc. JDT (Java Development Tools) is the most famous module aimed at group development: the environment is integrated with version control systems - CVS, GIT in the main package, for other systems (eg Subversion, MS SourceSafe) there are plugins. Also offers support for communication between the IDE and the task (error) management system. The main package includes support for the Bugzilla bug tracker, and there are also many extensions to support other trackers (Trac, Jira, etc.). Due to its free nature and high quality, Eclipse is the corporate standard for application development in many organizations. It is written in Java and therefore is a platform-independent product, with the exception of the SWT library, which is developed for all common platforms (see below). The SWT library is used instead of the standard Java Swing library. It relies entirely on the underlying platform (operating system), which provides a fast and natural-looking user interface, but sometimes causes compatibility and application stability issues across platforms.

The basis of Eclipse is the rich client platform (RCP). It consists of the following components:

Ø Platform core (loading Eclipse, launching modules);

Ø OSGi (standard bundles delivery environment);

Ø SWT (portable widget toolkit);

Ø JFace (file buffers, working with text, text editors);

Ø Eclipse work environment (panels, editors, views, wizards). Eclipse is written using the SWT toolkit. The latter, unlike Swing (which independently emulates graphical controls), uses the graphical components of this operating system. The Eclipse user interface also depends on a GUI middleware called JFace, which makes it easy to build an SWT-based user interface.

Eclipse's flexibility is ensured by plug-ins, which makes it possible to develop not only in Java, but also in other languages, such as C/C++, Perl, Groovy, Ruby, Python, PHP, Erlang, Component Pascal, Zonnon and others.

2.3.3 Microsoft Visual Studio

Microsoft Visual Studio is a line of Microsoft products that includes an integrated software development environment and a number of other tools. These products allow you to develop both console applications and applications with a graphical interface, including those with support for Windows Forms technology, as well as websites, web applications, web services in both native and managed code for all platforms, supported by Microsoft Windows, Windows Mobile, Windows CE, .NET Framework, Xbox, Windows Phone .NET Compact Framework and Microsoft Silverlight.Studio includes a source code editor with support for IntelliSense technology and the ability to easily refactor code. The built-in debugger can work as a source-level debugger or as a machine-level debugger. Other built-in tools include a form editor to make it easy to create an application's GUI, a web editor, a class designer, and a database schema designer. Visual Studio allows you to create and connect third-party add-ons (plugins) to extend functionality at almost every level, including adding support for source code version control systems (such as Subversion and Visual SourceSafe), adding new toolkits (for example, for editing and visual design of code in domain-specific programming languages ​​or tools for other aspects of the software development process (for example, the Team Explorer client for working with Team Foundation Server).

Chapter Conclusion

Among the vast number of existing DBMSs, Firebird 2.1 was chosen. since one of its advantages is support for many access methods, including: native sets of components for / C++ and Delphi. Firebird also supports large databases that can be located in several files. Another advantage of Firebird is its multi-version architecture, which provides parallel processing of operational and analytical queries (this is possible because reading users do not block writers), compactness (5Mb distribution), high efficiency and powerful language support for stored procedures and triggers.

The IBExpert 2009 shell was chosen as the database development environment because it has a number of advantages, such as:

Ø support for InterBase versions 4.x, 5.x, 6.x, 7.x; Firebird 1.x, 2.x; Yaffil 1.x;

Ø work simultaneously with several databases;

Ø separate editors for all database objects with syntax highlighting;

Ø powerful SQL editor with query history and the ability to run queries in the background;

Ø debugger of stored procedures and triggers;

Ø search in metadata;

Ø full and partial extraction of data and metadata;

Ø database object dependency analyzer;

Ø metadata reports;

Ø user and user privilege managers;

Ø export data to various formats. It has many components that make work easier: a visual editor for all database objects, a SQL editor and script executor, a debugger for stored procedures and triggers, an area builder, its own scripting language, as well as a database designer, etc.

Delphi 2010 was used as a software development environment because it has the following advantages:

Ø Fast application development.

Ø High performance of the developed application.

Ø Low requirements of the developed application for computer resources.

Ø Extensibility by integrating new components and tools into the Delphi environment.

Ø Ability to develop new components and tools using Delphi's own tools (existing components and tools are available in source code)

Ø Successful development of the object hierarchy

Ø De facto, a huge number of visual components from third parties are already available, some of which are freeware, some are shareware, some are commercial.

3. Relational database design

This database is designed based on the role model.

Role-based access control is a development of a policy of selective access control, in which the access rights of system subjects to objects are grouped taking into account the specifics of their application, forming roles.

Role-based access control allows you to implement flexible access control rules that change dynamically during the operation of a computer system.

This approach is used in DBMS security systems, and individual elements are implemented in network operating systems. The role-based approach is often used in systems for which users have a clearly defined range of their job duties and responsibilities, as in a given database.

Despite the fact that a Role is a set of access rights to objects of a computer system, role-based access control is by no means a special case of selective access control, since its rules determine the procedure for granting access to subjects of a computer system depending on the roles they have (or do not have) in every moment in time, which is typical for mandatory access control systems. On the other hand, the rules for role-based access control are more flexible than with the mandatory approach to control.

Since privileges are not assigned to users directly, and are acquired only through their role (or roles), managing individual user rights essentially comes down to assigning roles to them. This simplifies operations such as adding a user or changing a department by a user.

3.1 Development of table structure

The structure of the database for the AIS "Operator" is presented in Figure 4.

The database consists of 6 entities such as:

Ø Abonenti - This entity stores information about subscribers and includes the following attributes: subscriber code, last name, first name, patronymic, date of birth, passport data, residential address.

Ø Uslugi - this entity includes the following attributes: service code, description, note, cost.

Ø Tarifi - this entity includes the following attributes: tariff name, cost of incoming calls within the network, cost of outgoing calls within the network, cost of incoming calls from another operator, cost of outgoing calls to another operator, cost of incoming calls from a landline phone, cost of outgoing calls to a landline phone cost of SMS and cost of Internet traffic.

Ø Abonentskie_uslugi - this entity includes the following attributes: service code, contract number, connection date, expiration date of this service.

Ø Licevoi_schet - this entity includes the following attributes: id, personal account number, date, time, amount, contract number

Ø Zakluchenie_dogovora - this entity includes the following attributes: subscriber code, contract number, conclusion date, subscriber number, tariff, personal account number.

3.2 Table normalization

Normalization is the process of checking the structure of tables for anomalies, if there are any, then the tables are split into smaller tables. The normalization structure is presented in Figure 5.

Anomalies are situations when working with a database that can lead to ambiguous interpretation of data or inconsistent data. Anomalies occur in tables containing redundant data

Rice. 5. "Table normalization structure"

At the initial stage of database design, first normal form (1NF) is constructed: A table is in 1NF if there is an atomic value at the intersection of each row and column.

A relation is in 2NF if and only if the relation is in 1NF, and no, there are no key attributes that depend on the complex key part. In order to eliminate the dependence of attributes on part of a complex key, it is necessary to decompose the relationship into several relationships. In this case, those attributes that depend on part of the complex key are placed in a separate relation.

A relation is in 3NF if and only if the relation is in 2NF and all non-key attributes are mutually independent.

Attributes are said to be mutually independent if none of them is functionally dependent on the other.

A table is in BCNF (Normal Form Bays Code) if the determinants of all functional dependencies are potential key tables

A relation is in 4NF if the relation contains 2 multivalued dependencies.

A multi-valued dependency is a logical relationship between the values ​​of columns A and B in which for value A we can determine a set of values ​​for column B.

NF is applied to tables that have several multi-valued dependencies, and the attributes included in these dependencies are interconnected in meaning, that is, they are dependent on each other.

Relations are in DKNF (Domain Key Normal Form) if each integrity constraint imposed on this relation is a logical consequence of the definition of domains and keys.

Let's normalize the tables of the "Operator" database.

To do this, we select functional dependencies for each table and check for normal forms as shown in Figure 1. A functional dependency (FD) between columns means a logical “Many to One” relationship between the values ​​of these columns.

Abonenti table:

Functional dependencies:

.Kod_abonenta → (Familiy, name, otchestvo, data_rogdeniy, seriy_pasporta, nomer_pasporta, kem_vidan, kogda_vidan, address)

.(seriy_pasporta, nomer_pasporta) → (Kod_abonenta ,familiy, name, otchestvo, data_rogdeniy, kem_vidan, kogda_vidan, address)

3.(Familiy, name, otchestvo, data_rogdeniy, address) → (Kod_abonenta, seriy_pasporta, nomer_pasporta, kem_vidan, kogda_vidan)

Test for normal forms (NF):

NF passed, 2NF passed, NFBC passed. There are no multivalued dependencies. The table is in DKNF.

Uslugi table

Functional dependencies:

.Kod_uslugi → (Opisanie, primechanie, stoimost)

Table Abonentskie_uslugi

Functional dependencies:

.Kod_uslugi → (Nomer_dogovora, data_podklucheniy, data_okonchaniy)

.Nomer_dogovora → (Data_podklucheniy, data_okonchaniy)

.(Nomer_dogovora, data_podklucheniy → (Data_okonchaniy)

SF passed, 2NF passed, 3NF passed. There are no multivalued dependencies. The table is in DKNF.

Tarifi table

Functional dependencies:

.Nazvanie_tarifa → (St_vh_vn_s, st_ish_vn_s, st_vh_dr_op, St_ish_na_dr_op, st_vh_s_gor_tel, st_ish_na_gor_tel, st_sms, internet_trafic)

SF passed, 2NF passed, 3NF passed. There are no multivalued dependencies. The table is in DKNF.

Table Licevoi_schet

Functional dependencies:

1.Id → (Nom_licevogo_scheta, data, vremya, summa, nomer_dogovora)

2.Nom_licevogo_scheta → (Id, data, vremya, summa, nomer_dogovora)

.(Nom_licevogo_scheta, data) → (vremya, summa)

SF passed, 2NF passed, 3NF passed. There are no multivalued dependencies. The table is in DKNF.

Table Zakluchenie_dogovora

Functional dependencies:

.Kod_abonenta → (Nom_dogovora, data_zaklucheniy, abonents_nom,tariff, nom_licevogo_sheta)

.Nom_dogovora → (Kod_abonenta, data_zaklucheniy, abonents_nom,tariff, nom_licevogo_sheta)

.Subscribers_nom → Nom_licevogo_sheta

SF passed, 2NF passed, 3NF passed. There are no multivalued dependencies. The table is in DKNF.

Thus, all detected update anomalies are eliminated. The relational model, consisting of relations in third normal form, is adequate to the described domain model.

3 Design of integrity constraints

Table 1. "Abonenti"

Column nameTypeNull/not nullPrimary key/uniqueCheckForeign keyNotesKod_abonentaIntegernot nullPrimary keySubscriber codeFamiliyVarchar (25)not nullSubscriber's surnameNameVarchar (15)not nullSubscriber's first nameOtchestvoVarchar (25)not nullSubscriber's middle nameData_rogdeniyaDatenullDate of birth subscriber аSeriya_pasportaIntegernot nullPassport seriesNomer_pasportaIntegernot nullPassport numberKem_vidanVarchar (35)not nullIssued byKogda_vidanDatenot nullWhen issuedAddressVarchar (85)nullSubscriber's address

Table 2. "Uslugi"

Column nameTypeNull/ not nullPrimary key/uniqueCheckForeign keyNotesKod_uslugiIntegernot nullPrimary keyService codeOpisanieVarchar(150)not nullDescription of the service, its namePrimechanieVarchar(150)nullNotes,StoimostFloatnot nullService cost

Table 3. "Subscriber_uslugi"

Column nameTypeNull/ not nullPrimary key/uniqueCheckForeign keyNotesKod_uslugiIntegernot nullForeign keyService codeNomer_dogovoraIntegernot nullForeign keyContract numberData_PodklucheniyDatenot nullService connection dateData_okonchaniyDatenullService end date

Table 4. "Zakluchenie_dogovora"

Column nameTypeNull/ not nullPrimary key/uniqueCheckForeign keyNotesKod_abonentaIntegernot nullForeign keySubscriber codeNom_dogovoraIntegernot nullPrimary keyContract numberData_zaklucheniyDatenot nullContract dateAbonents_nomIntegernot nullSubscriber numberTarifVarchar (45)not nullForeign keyTariff planNomer_ Licevogo schetaIntegernot nullForeign key Subscriber's personal account number

Table 5. "Licevoi_schet"

Column nameTypeNull/not nullPrimary key/uniqueCheckForeign keyNotesIdIntegernot nullPrimary keyOrdinal numberNomer_licevogo_schetaIntegernot nullPersonal account numberDataDatenot nullDateVremyaTimenot nullTimeSummaFloatnot nullAmountNomer_dogovoraIntegernot nullContract number

Table 6. "Tarifi"

Column nameTypeNull/ not nullPrimary key/uniqueCheckForeign keyNotesNazvanie_tarifaVarchar (45)not nullPrimary keyTariff nameSt_vh_vn_sFloatnot nullCost of incoming calls within the networkSt_ish_vn_sFloatnot nullCost of outgoing calls within the networkSt_vh_dr_opFloatnot nullCost of incoming calls from another operator and cellular communicationsSt_ish_na_dr_opFloatnot nullCost of outgoing calls to another cellular operatorSt_vh_s_gor_telFloatnot nullCost of incoming calls from a landline phone numberSt_ish_na_gor_telFloatnot nullCost outgoing calls to a landline phone numberSt_smsFloatnot nullCost of SMSInternet_traficFloatnot nullCost of Internet traffic per megabyte

3.4 Design of data sampling operations

The design of the data sampling operation is presented in Table 7.

Table 7. "Development of data sampling operations"

No. Action description Input parameters (name, type) Output parameters (name, type) Execution algorithm 1 Adding a new subscriber (procedure ADD_NEW_ABONENT) KOD_ABONENTA integer FAMILIY varchar(25) NAME varchar(15), OTCHESTVO varchar(25), DATA_ROGDENIYA date, SERIY_PASPORTA integer , NOMER_PASPORTA integer, KEM_VIDAN varchar (35), KOGDA_VIDAN date, ADDRESSvarchar (85) Error code - integer: 0 - error Check whether there is a person with the same subscriber code in the Abonenti table, if so, exit with error code 0, if not, then add a new line with data about the new client into the table and send the values ​​of the output parameters to the output with code 1 2Editing subscriber data (UPDATE_DANNIE_OB_ABONENTE procedure)KOD_ABONENTA integer FAMILIY varchar(25) NAME varchar(15), OTCHESTVO varchar(25),DATA_ROGDENIYA date, SERIY_PASPORTAinteger ,NOMER_PASPORTA integer,KEM_VIDAN varchar(35), KOGDA_VIDAN date,ADDRESSvarchar(85)Error code - integer: 0 - errorCheck whether there is a person with the same subscriber code in the Abonenti table, then change the necessary data and exit with parameter 1, if not then exit with error code o.3 Deleting a subscriber (DELETE_ABONENT procedure) KOD_ABONENTA integer Error code - integer: 0 - error Check whether a person with the same subscriber number exists in the Abonenti table, if so, delete the line with his data, if not, then exit with error code 0.4 Adding a new contract (ADD_DOGOVOR procedure) KOD_ABONENTA integer, NOM_DOGOVORA integer, DATA_ZAKLUCHENIY date, ABONENTS_NOM bigint, TARIF varchar(45), NOM_LICEVOGO_SCHETA integer Error code - integer: 0 - error Check whether the Zakluchenie_dogovora number exists in the table agreement that matches the entered one, if yes, then exit with error code 0, if not, then add a new row with all the data to the table and send the values ​​of the output parameters to the exit with code 15 Deleting a contract (DELETE_DOGOVOR procedure) NOM_DOGOVORA integer Error code - integer: 0 - error Check whether Zakluchenie_dogovora exists in the table contract number that matches the one entered, if yes, then delete the line from the table, if not, exit with error code 0.6 Adding a new tariff plan (ADD_NEW_TARIF procedure) NAZVANIE_TARIFA varchar(45), ST_VH_VN_S float,ST_ISH_VN_S float,ST_VH_DR_OPfloat,ST_ISH_NA_DR_OP flo at, ST_VH_S_GOR_TEL float, ST_ISH_NA_GOR_TEL float ST_SMS float, NTERNET_TRAFIC float Error code - integer: 0 - error Check whether there is a tariff with the same name in the Tarifi table, if so, exit with error code 0, if not, add a line with information about the tariff to the table and send the values ​​of the output parameters to the output with code 17Changing tariff data (UPDATE_DANNIE_O_TARIFE procedure) NAZVANIE_TARIFA varchar(45), ST_VH_VN_S float,ST_ISH_VN_S float,ST_VH_DR_OPfloat,ST_ISH_NA_DR_OP float, ST_VH_S_GOR_TEL float, ST _ISH_NA_GOR_TEL float ST_SMS float, NTERNET_TRAFIC float Error code - integer: 0 - errorCheck does a tariff with the same name exist in the Tarifi table? integer: 0 - errorCheck whether a tariff with the same name exists in the Tarifi table, if so, then delete the row from the table, otherwise we exit with error code 0. 9Adding a new service (procedure ADD_NEW_USLUGA)KOD_USLUGI integer, OPISANIE varchar(150), PRIMECHANIE varchar(150), STOIMOST float,SPOSOB_PODKLUCHENIY varchar(200)Error code - integer: 0 - error Check whether a service with the same service code exists in the Uslugi table, if yes, then exit with error code 0, if not, then add a line with information about the service to the table and send the values ​​of the output parameters to the exit with code 110Changing information about services (UPDATE_DANNIE_OB_USLUGAH procedure)KOD_USLUGI integer, OPISANIE varchar(150), PRIMECHANIE varchar (150), STOIMOST float, SPOSOB_PODKLUCHENIY varchar (200) Error code - integer: 0 - error Check whether a service with the same service code exists in the Uslugi table, if so, then change the data and send the values ​​of the output parameters to the output with code 1, if no, then we exit with error code 0 11Deleting a service (DELETE_USLUGA procedure)KOD_USLUGI integerError code - integer: 0- errorCheck whether a resource with the same service code exists in the Uslugi table, if so, then delete the row with the data, otherwise we exit with error code 012Addition personal account (procedure ADD_NEW_LIC_SCHET)ID integer, NOM_LICEVOGO_SCHETA integer, DATA date, VREMYA time, SUMMA float, NOMER_DOGOVORA integer Error code - integer: 0 - error Check whether a client with the requested id exists in the Licevoi_schet table, if so, exit with error code 0 , otherwise we add data to the table and send the values ​​of the output parameters to the output with code 113 Deleting a personal account (DELETE_LIC_SCHET procedure) ID integer Error code - integer: 0 - error Check whether a client with the requested id exists in the Licevoi_schet table, if so, delete the row with the data, otherwise exit with error code 0 14Changing the deposited amount (UPDATE_SUMMA procedure)NOM_LICEVOGO_SCHETA integer, SUMMA float,Error code - integer: 0 - errorCheck whether a client with the requested id exists in the Licevoi_schet table, if so, then change the amount and send the output value 1, otherwise we exit with error code 0 3.5 Issue of access rights

Access rights to database objects are given in Table 8. Horizontal - database objects. Vertically - users or roles. In the cells - a combination of letters indicating access rights: - the right to read (select); - the right to add rows (insert); - the right to edit rows (update); - the right to delete rows (delete); - the right to run stored procedures (execute).

Table 8. "Issuing access rights"

Object DBRoles:Adnin manager Prodavec Table abonentisiudssuidTable UslugisiudsuidsTable Abonentskie_uslugisiudssiud Table TarifisiudsuidsTable Licevoi_schetsiudssiudTable Zakluchenie_dogovorasiudssiudProcedure Add_dogovoreeProcedure Add_new_abonenteeProcedure Add_new_lic_scheteePro procedure Add_new_tarifeeProcedure Add_new_uslugaeeProcedure Delete_abonenteeProcedure Delete_dogovoreeProcedure Delete_lic_scheteeProcedure Delete_tarifeeProcedure Delete_uslugaeeProcedure Update_dannie_ob_abonenteeeProcedure Update_dannie_ob_uslugaheeProcedure Update_dannie_o_tarifeeeProcedure fool Update_summaee

Chapter Conclusion

The developed database is intended to record data about clients of a salon - store that provides services of a cellular operator, as well as storing information about tariffs and operator services.

This database provides the ability to search, add, delete and edit data.

There is a differentiation of access rights for different user groups.

4. Designing the "Operator" client application

This automated information system (AIS) is designed to record data about subscribers of a store that provides mobile services, as well as about the services themselves and tariffs provided by this operator. Only employees of the salon - store will work with the AIS "Operator". It will be used in the store on a local computer and will have the following capabilities:

Ø Registering a new connection

Ø Connecting a separate service

Ø Switching to another tariff

Ø Ability to edit data about tariffs and services, as well as about subscribers

Ø Possibility of depositing funds into the subscriber’s personal account

Ø Generating reports

1 Description of program modules

The description of the AIS "Operator" modules is presented in Table 9.

Table 9 "Description of program modules"

File nameDescriptionSizeMenu.pasThe main module that calls other modules and contains the main menu of the program6 716 bAbonenti.pasModule designed to add, delete and edit data about cellular subscribers1 644 bUslugi.pasModule designed to add, delete and edit data about services1 104 bAbonentskieUslugi. pasModule intended for connecting the service1,009 bDogovori.pasModule intended for concluding, changing and deleting an agreement with a subscriber1,465 bPrice_List.pasModule intended for generating a report with a list of prices 1,059 bProdagi.pasModule intended for generating a sales report754 bDolgniki.pasModule intended to generate a report with a list of debtors835 bPassword.pas Authorization module860 bTarif.pasModule designed for adding, deleting and editing information about tariffs2 766 b LicevoiSchet.pasModule intended for depositing funds into the subscriber's account2 330 b

2 Delivery package and system requirements

The delivery package of this software tool includes: the executable file OPERATOR.exe, the source code of the program, which is a set of modules of the software tool (described above), a file with table data OPERATORSOTSV.FDB and a configuration file Config.ini.

Minimum system requirements: "Pentium166MHz", Operating system - Windows 98 and higher, Microsoft Office application (Excel) when working with reports.

The required amount of memory for the program to run is determined by the following components:

-Executable file size (1593Kb);

-DB size (2928Kb);

-Configuration file size (1Kb).

Thus, the required amount of memory is 4522Kb, that is, about 5 Mb.

3 Description of the user interface

The user interface is very important for the program, as it significantly increases productivity and the user's work becomes much more productive.

To run the program, run the executable file OPERATOR.exe.

After launching the application, you must go through authorization. To do this you need to enter your login and password.

This AIS will be used by the following user groups:

.A sales consultant who will perform the following actions:

ü Connecting new subscribers;

To prepare a complete set of documents that ensure interaction between parties in the information international legal space, basic international acts are needed

Processing a wide variety of information has today become a condition of life in an information, civil, social and legal society. Information literacy and awareness are today the most important practical task requiring a political decision, but the food for such decisions (political and economic) is primarily prepared by that army of specialists who master and process information, creating a management resource. The principle of medicine “do no harm!” is very important here.

Let's consider the problem of the formation and use of operating systems from the point of view of their social orientation and discuss the role of system operators.

Institute and types of operators in information systems

In the organizational and legal aspect, the problem of the operator is not sufficiently understood, and the legal status of this category of specialists and organizations has not been worked out.

The work of an operator must be considered as a specialized information activity associated with targeted information processing using specially oriented programs. This, in turn, leads to the solution of questions: who can be a system operator, what is his legal status (role and tasks, functions, powers, responsibilities).

In studies to determine the legal status, operators are designated as organizations specializing in providing access to information on the network through communication channels and providing remote access. Operators (providers) are distinguished by the types of services they provide: network access providers, content providers, host providers. The interaction of the operator with users of its services, acting as senders of information, is defined as interaction with the second party (the first is the operator itself), and the user - the recipient of information - acts as a third party. The content operator creates its own content and provides access to it under certain conditions; the hosting provider provides a resource for hosting user content, the availability of which is determined by these users; Network access providers provide the corresponding service by providing communication access lines or access points. Their service is to provide data traffic without permanent storage.

The current legislation has introduced rules that apply to the information system operator. In the Federal Law “On Information, Information Technologies and Information Protection” (No. 149-FZ of July 27, 2006), an information system operator is defined as “a citizen or legal entity engaged in operating an information system, including processing information contained in its databases” (Article 2, paragraph 12).

In the course of applying this article, it is possible to encounter the concept of “owner” of information as a subject of legal regulation (Article 2, paragraph 5). According to the law, the owner is the person who independently created the information, or the person who, on the basis of law or agreement, allows or restricts access to information. The law includes both individuals and legal entities, as well as the Russian Federation, constituent entities of the Russian Federation, and municipalities as the owner of information (Article 6). Here we see an expansion in the composition of the subject-owners and a lack of connection with the topic of the network operator. Compared to Art. 2 the number of owners includes government and municipal authorities. What operator can be considered as the owner of the information with which he works?

The issue of regulatory registration of the legal status of an information system operator is becoming more acute: in Art. 13, paragraph 2 states that, unless otherwise provided by federal laws, operator information system is the owner(no longer just the owner) “used to process information contained in databases technical means, which lawfully uses such databases, or a person with whom this owner has entered into an agreement on the operation of the information system". Simultaneously with this general rule in Art. 14, dedicated to government information systems, prescribes the rules for this level of resources and processing systems. State information systems are created in accordance with the federal law “On placing orders for the supply of goods, performance of work, provision of services for state and municipal needs” (No. 94-FZ of July 21, 2005). This assumes that the operator is not the same as the customer and the creator of the information. Along with this, the customer himself, that is, the government authority, can act as an operator. According to paragraph 6 of Art. 14 Federal Law “On Information” The Government of the Russian Federation establishes mandatory requirements for the procedure for commissioning certain state information systems. And according to paragraph 5 of the same article, unless otherwise established by the decision on the creation of a state information system, the body itself acts as an operator and itself puts this system into operation.

From the above, it follows that there are three options for legalizing national state information systems and defining the role of the operator. In the first option, the public authority combines the functions of operator and customer. The second provides for the creation of state information systems by decision of the Government of the Russian Federation and its regulation of the order (commissioning) of processing systems and establishes requirements for the technical support of the system. The operator status is set in the same manner. Finally, a third option is possible: the operator is also given the right to the information resource, moreover, the right to transfer it to another operator. The legal status of the information system operator in accordance with the Federal Law “On Personal Data” (No. 152-FZ of July 27, 2006) requires special consideration taking into account the standards established by the Federal Law “On Information”.

Decisions in the field of administrative reform in the Russian Federation are essential for resolving the issue of the legal status of the information system operator. The basic documents here are the legal acts of the Government of the Russian Federation, which approved the Concept of the use of information technologies in the activities of federal authorities until 2010 (dated September 24, 2004), the federal target program “Electronic Russia” (2002-2010), as well as Government Resolution No. 679 dated 11.11.2005 “On the procedure for developing and approving administrative regulations for the performance of government functions and administrative regulations for the provision of public services.” For the topic under consideration, the last of the listed regulations is important. It is this resolution that indicates the separation of government functions and government services in the information sphere. Defining the characteristics and criteria would make it possible to most clearly identify the role and status of the operator for these two categories of government activities.

For example, Government Resolution No. 679 took an important step to separate the functions of executive authorities from the performance of public services and set the task of creating a procedure for the development and approval of administrative regulations for the performance of government functions and the provision of public services. It is necessary to understand which services are implemented by the government directly in communication with the population, and which should be performed for the state apparatus itself and on what organizational and legal basis. A number of issues require more careful consideration and regulation: who is the owner (or other form of ownership) of the resource being processed by the system operator, who is outside the structure of the authority? To what extent does it serve the functions of the body, and to what extent are it government services? How does this affect his powers? Raising these questions is important for considering the legal status of a new type of operator - the operator of cross-border transfer of electronic documents in the information interaction of entities under the jurisdiction of different states.

Cross-border interaction

With the massive spread of the Internet, the world's population received virtually unlimited information freedom. Unfortunately, it did not create the necessary basis for remote, legally significant interaction between subjects of different countries. Such interaction can only be organized on the basis of secure electronic documents, which eliminates anonymity.

A study of the state of legal regulation of cross-border interaction of Internet users located in different states and determining the legality of their actions on the basis of national legislation, even when carrying out cross-border transactions, shows that information technologies are becoming increasingly important as components of a qualitatively new technical phenomenon - computer networks. Consequently, legal regulations for the implementation of electronic procedures using special programs and databases should be specific and, if possible, similar.

An analysis of scientific works and current regulations at the international level shows that the main focus for a long time has been on determining the legal nature of computer programs and databases in terms of their regulation by intellectual property institutions. The chain of relations of all subjects involved in the process of cross-border information interaction has not received due attention. The shift has occurred since the adoption of international acts regulating relations in electronic commerce, in particular the European Union Directive 2000/31/EC of June 17, 2000, and the international and national regulations that followed it.

About six months earlier, the European Commission issued Directive 1999/93/EC on the conditions for the use of electronic signatures in Member States, which attempted to lay down a pan-European legal framework for cross-border
interactions. The European Commission assumed that such signatures would facilitate the sale of goods and services via the Internet. To date, all 25 EU member countries have implemented the provisions of this directive in their legislation.

In addition, the European Commission has developed an action plan to improve technology and establish the legal status of electronic signatures, ensuring legal significance (this plan should be implemented by 2010). The European Commission would like to further promote the development of services and applications related to electronic signatures. It is planned to encourage further standardization to ensure interoperability between different electronic signature systems at both national and pan-European level, and to enable the use of different qualified electronic signature technologies within the single market.

Let us note that at the 15th Russia-European Union summit held in Moscow on May 10, 2005, a “road map” for a common space of freedom, security and justice was approved. This “road map” provides for cooperation and resolution of a number of problems, including cross-border interaction between entities of different states. In particular, the document contains the clause: “to promote cross-border cooperation with neighboring EU member states by establishing interaction between various national ministries and law enforcement agencies, starting with regions with a high intensity of cross-border traffic.”

In addition, on November 23, 2005, at the 53rd meeting of the 60th session of the General Assembly, the UN Convention on the Use of Electronic Communications in International Agreements (resolution 60/21) was adopted to ensure cross-border economic interaction.

Cross-border exchange and Russian law

As an active participant in international relations, Russia is interested in intensifying work in the field of using electronic signatures. And it is quite natural that a lot of work is being done in this direction.

Let us remind you that in connection with the adoption of the Federal Law “On Information, Information Technologies and Information Protection,” the Federal Law “On Participation in International Information Exchange” was repealed. This fact, as well as the great discussion that accompanied the adoption of the 4th part of the Civil Code of the Russian Federation, which included such subjects of legal regulation as computer programs and databases, the use of brand names, created new opportunities for more detailed and substantive regulation of cross-border relations and legal mechanisms for legalizing electronic documents in cross-border space, establishing trust between participants in information interaction.

To identify the entire composition of subjects involved in the cross-border transfer of information, it is necessary to build a clear and complete model of their relationship with each other. As is known, issues of interaction between the user and providers, as well as between different providers, were considered separately from issues of interaction between two or more users using IT, since these types of information interaction lie, as it were, on different planes.

Much work in this direction is being carried out by the Federal Information Technology Agency. The concept of a third trusted party in cross-border information interactions between residents of different states has been developed, and national and international conferences have been held.

The Institute of State and Law of the Russian Academy of Sciences has already created some methodological developments. In Anna Zharova's PhD thesis (2004), a scheme was proposed for the legal regulation of relations between subjects both at the stage of information exchange between subjects - users of network services, and at the stage of circulation of information provided by operators (it is also given in, pp. 44-47) .

Subject relationships

To date, a solution option has been presented, which is based on a generalization of bilateral agreements of different countries on the exchange of information, analysis and generalization of the legal aspects of the cross-border use of electronic signatures from the point of view of the legislation of the Polish Republic, the experience of the EurAsEC countries, the CIS, and the experience of electronic commerce. A model of interaction between participants in relations regarding the cross-border transfer of an electronic document and its electronic signature has been prepared.

Let us briefly outline the subjects and levels of legal relations, as well as the nature of legal acts that ensure the rights and obligations of each of the parties involved in this process. Firstly, the subject of the relationship is the transmitted electronic document or a set of them and, secondly, the object of legal regulation is the relationship of participants in cross-border exchange.

These relationships look like this: Conditional subjects A and B, each of which has its own jurisdiction, enter into a relationship of exchange of documents that have legal force: subject A ensures the transfer of its electronic document by interacting with its counterparty (partner) B. Each of the participants (A and B) in this case interacts with its operator (Oa and Ob).

Their operators face three tasks:

Receive correspondence from client A, enter into the register of received electronic documents for cross-border transfer; control confirmation of the validity of his electronic signature at the time of its transmission via the communications system to the jurisdiction zone of client B’s state regarding the electronic signature of an electronic document or message.

Confirm the validity (reliability) of A’s signature to another provider (Ob operator) by generating an electronic apostille, which includes the operator’s details, the date and time of its formation and dispatch, certified by the signature of the operator’s official, and transfer it over the network to Ob for addressee A.

Inform client A about the transactions performed with his ED by sending him a confirmation (receipt), if this is provided for in the contract.

Operators of participants A and B (Oa and Ob) accept electronic documents or messages and record in their registers the fact of receipt, control of the electronic signature, its certification (formation of an apostille) and sending.

Of course, the legal registration of interaction between participants in cross-border information exchange presupposes the conclusion of appropriate agreements. In this case, two types of agreements are required: each of the users of operator services with its operator, as well as each operator with its foreign partner operator (in our example, between Oa and Ob).

However, this is not enough for full-fledged legal information interaction between participants A and B, who can represent both individuals and legal entities, as well as government authorities of different states. Initial international acts are needed to regulate the procedure for implementing cross-border information exchange.

The widest information space can be provided by such an act as the international convention on ensuring cross-border interaction on the basis of an electronic document (message) and an electronic signature. States parties to such a convention, by ratifying it, would assume responsibilities for creating an infrastructure and an adequate legal framework in the structure of national legislation. To move from the convention to specific agreements between operators of interacting states, another international document is required - a standard agreement for operators of countries participating in the convention.

Within the framework of the international convention

The figure shows the interaction and systemic connection of legal acts that ensure the provision of government services for recognizing the legality of an electronic signature in cross-border information interaction between subjects of two or more states. Their conventional name is the trusted party operator (TPO).

All types of legal documents ensuring the process of cross-border information exchange based on an electronic signature (digital signature) must be prescribed by the proposed convention and accompanied by Regulations on the relevant service of each party to the convention, defining the functions, operations, and the availability of administrative and technical regulations necessary from the point of view of national legislation .

In the process of this preparatory work, a number of problems will have to be solved. First, the community must develop a consensus on the level of the convention and the procedure for its adoption. It seems that a body is needed that is competent to adopt an act that operates in the widest information space. Secondly, it is important to define the powers of cross-border trust operators, as well as their responsibilities. Thirdly, it is important to establish the subject of the operator’s control activities - is it only an electronic signature, or is it also the content of the document.

In addition, it is necessary to establish a rule according to which the operator cannot claim ownership of the registers that it maintains and the documents that it circulates over the network, but it is responsible for their integrity and safety, as well as the confidentiality of all information of its service .

For each country participating in the proposed convention, it is important to resolve the issue of the organizational form of the trust operator services, which could promptly interact with its certification centers that confirm the validity of the signature key certificate at the time the electronic document enters the legal field of the counterparty. For the Russian Federation, such an organizational center could be the Federal Information Center of the Russian Federation - an independent state body that provides services according to the scenario described above. He is responsible for the accuracy and timeliness of the data provided to the other party of the cross-border mechanism for monitoring the effectiveness of the received electronic document for a specific addressee in accordance with the convention of the participating parties, as well as under the terms of the agreement between two specific national trust services.

The proposed model will allow us to link the specifics of the national legislation of the parties to the convention with the general requirements for ensuring the cross-border exchange of electronic documents and messages.

Literature:

Zharova A.K. Information. Legal regulation of information circulation on the Internet. M.: Janus-K, 2006. 207 p.

Directive 2000/31/EC of the European Parliament and of the Council of 8 June 2000 on certain legal aspects of information society services, in particular electronic commerce, in the Internal Market (Directive on electronic commerce).

Directive 1999/93/EC of the European Parliament and of the Council of 13. December 1999 on a Community framework for electronic signatures.

Vladimir Matyukhin - head of the Federal Agency for Information Technologies of the Russian Federation;
Illaria Bachilo - professor, Honored Lawyer of the Russian Federation, head. the information law sector of the Institute of State and Law of the Russian Academy of Sciences;
Stanislav Semiletov - senior researcher at the Institute of State and Law of the Russian Academy of Sciences

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/

store operator base interface

Introduction

1. Domain analysis

1.1 Description of the store for the provision of mobile operator services

1.2 Technical means

1.3.1 Description of business processes

1.3.2 Data analysis

1.3.3 Study of information flows

1.4 Review of existing analogues

1.4.1 AIS "Mobile operators"

1.4.2 AIS "MTS Service 1.15.45"

1.4.3 AIS "ETK: Personal Account 1.3"

Chapter Conclusion

2. Review of development tools

2.1 Selecting a DBMS

2.1.1 Oracle Database

2.1.2 DBMS MS SQL Server-2008

2.1.3 DBMS Firebird 2.1

2.2 Selecting a database development environment

2.2.1 IBExpert 2009

2.2.2 Microsoft Access

2.3 Selecting a Software Development Environment

2.3.1 Delphi 2010

2.3.2 Eclipse

2.3.3 Microsoft Visual Studio

Chapter Conclusion

3.2 Table normalization

3.3 Design of integrity constraints

3.5 Issue of access rights

Chapter Conclusion

4. Designing the "Operator" client application

4.1 Description of program modules

4.2 Delivery package and system requirements

4.3 Description of the user interface

4.3.1 Authorization

4.3.2 Main program window

4.3.3 Main menu

4.3.4 "Reporting"

Chapter Conclusion

5. Ensuring life safety of work in the showroom of a cellular operator

5.1 Organization of an automated workstation for store employees

5.2 Dangerous and harmful production factors accompanying the activities of PC users in a store

5.3 Ways to protect store personnel from occupational hazards

5.4 Automotive technical calculation of lighting in a showroom-shop providing services of a cellular operator

Chapter Conclusion

Conclusion

List of sources used

Introduction

It is difficult to imagine the modern world of information technology without the use of databases.

Almost all systems are, to one degree or another, associated with the functions of long-term storage and processing of information.

In fact, information becomes a factor determining the effectiveness of any field of activity.

Information flows have increased and requirements for data processing speed have increased, and now most operations cannot be performed manually; they require the use of the most promising computer technologies.

Any administrative decisions require a clear and accurate assessment of the current situation and possible prospects for its change.

Databases reflect a certain part of the real world. This information should, if possible, be recorded in the database once, and all users who need this information should be able to work with it

The purpose of this final qualifying work is to develop an automated information system for managing the services of a telephone operator.

Automation of the store for the provision of telephone operator services will allow employees to get rid of many routine processes, which will ensure the fastest, most complete and high-quality service for subscribers.

Main goals:

- Conducting an analysis of the activities of the store in providing telephone operator services.

- Development of an information database.

- Program development.

- Conducting an analysis to ensure the life safety of a store providing services of a cellular operator.

1. Domain analysis

1.1 Description of the store for the provision of mobile operator services

The main activity of the store is the provision of mobile communication services

This is a legal entity that has a registered trademark, brand name, current and other accounts in rubles in banking institutions.

The salon store includes administration, accounting, personnel department, and management department. The general management of the enterprise is carried out by the General Director. Subordinate to him are the Deputy Director for Economics and Finance. Direct management is exercised by the General Director.

The main divisions supporting the activities of the store are:

1. accounting - calculation and issuance of salaries, tax reporting;

2. management department - registration of clients and connections, reporting;

1.2 Technical means

Shops providing telephone services use information technologies that automate administrative and commercial activities. The salons have a modern material base, including computer equipment and peripherals, as well as a local computer network (LAN), which allows for centralized storage and processing of information. The network covers all departments.

The enterprise uses the following software and hardware.

Software:

Ш Windows 7 is an operating system of the Windows NT family of Microsoft Corporation.

Ш Windows Server 2008 is an operating system of the Windows NT family from Microsoft, which is designed to work on servers.

Ш 1С: Enterprise 8.3.

Ш Kaspersky Anti-Virus 2012 - the program provides anti-virus protection, protection against spam and hacker attacks.

Hardware:

The enterprise departments have computers with the following configuration:

Ш Processor INTEL Core i3 3240 LGA 1155 OEM

Ш Memory module HYNIX DDR3- 2GB 1333 DIMM OEM

Ш Hard drive WD Caviar Blue WD5000AAKX 500GB HDD SATA III

All computers are connected into a single local area network and have access to the Internet.

Information systems and application software systems:

Ш 1С: Accounting 8.3 - an automated information system created to automate accounting and tax accounting, including the preparation of mandatory (regulated) reporting.

Ш 1С: Enterprise 8.3 - is a set of software modules designed for the development and use of solutions (configurations) for accounting and automation of business activities of enterprises, and configurations or a set of configurations.

Ш MS OFICCE 2010 - a set of programs for preparing documentation.

1.3 Description of accounting for sales of goods and services of a cellular operator

The management department performs the following functions:

- client connection

- organizing the acceptance of an order for connecting the services of a cellular operator from a client;

- accepting payments from clients;

- monitoring the status of connections;

- drawing up a report on connections and payments;

Salon director - provides leadership for development and operation, conducts internal audits, analyzes their results, and monitors the implementation of corrective measures.

Sales Manager - implements connection of services.

1.3.1 Description of business - processes

To implement the services of a cellular operator, the following business processes are required:

1. Connecting a new subscriber - first a new subscriber is registered, then his data is entered into the database, the client selects a tariff plan, then an agreement for a new connection is concluded, payment is accepted and the client is given a payment receipt;

2. Connection of the selected service - after selecting the service, an agreement is drawn up, payment is accepted and a payment receipt is issued

3. Registration of payment - after depositing funds into the subscriber’s personal account, a payment receipt is issued;

4. Generation of reporting documents:

Ш Generation of the “Price List” report - generation of information on prices for current tariffs and services;

Ш Generation of the “Sales Analysis” report - generation of a list of debtor clients whose debt amount exceeds the specified amount;

Ш Generation of the "Payment Status" report - generation of information about payments for each client.

Business rules are a set of conditions that govern a business event so that it occurs as desired for the business or customer.

Let's consider the Business rules that are necessary for the implementation of services:

1. When ordering a service, the payment established by the store must be paid.

2. The conclusion of an agreement to connect a new client occurs after full payment of the cost of the selected tariff and after the client provides an identification document.

3. Before depositing funds into the subscriber’s account, it is necessary that payment be made and the subscriber be registered in the store’s database.

1.3.2 Data analysis

It is necessary to determine the data that will be used in the designed database. This information can be divided into the following types:

- information about the contract;

- information about subscribers;

- information about tariffs and services;

- information about payments;

- sales information.

Information about the agreement includes: subscriber code, subscriber personal account number, agreement number, subscriber number, name of the tariff or service, cost of the tariff or service, date of conclusion and amount of payment.

Information about subscribers includes: subscriber's full name, passport details, address and date of birth.

Information about tariffs and services includes: name of the tariff or service, cost.

Payment information includes: buyer's full name, subscriber number, payment amount, payment date.

Information about the sale includes: information about the tariff or individual service, full name of the buyer, passport details of the buyer, price of the tariff or service, date of sale.

1.3.3 Research of information flows

Work with the system There will be only store employees, namely:

Sales consultants who will register new connections, change or add subscriber data, as well as deposit funds into subscribers’ accounts

A manager who will make various kinds of changes related to the catalog of services and tariffs.

The administrator, in turn, will view the list of debtors and generate reports.

The following information will serve as input information:

About clients, the following information will be entered: full name, series and number of passport, by whom and when issued, date of birth, address.

About the tariffs: name of the tariff, cost of incoming and outgoing calls, SMS and Internet traffic.

About the services: name, cost, description of the service and notes.

The following reports will be generated by the client program as output information:

- "Price List" report - this report will display a list of prices for current tariffs and services;

- “Sales Analysis” report - this report will display a list of services and connections sold for the year;

Report "Payment status" - this report displays a list of subscribers to whose account funds were deposited by the operator over the last 2 days.

1.4 Review of existing analogues

Today, there are enough automated systems created for cellular operators, but in most cases they are designed for a specific operator, have limited capabilities, or are part of a large set of programs.

1.4.1 AIS "Mobile operators"

Description: The "Mobile Operators" program allows you to get information by phone number:

Mobile operator

Date of registration (company)

Official website of the Operator

Page for free SMS sending

Thanks to such information, the subscriber will always know who called him or wrote an SMS and from where.

Before calling a mobile phone, we recommend that the subscriber use this program to find out which region and mobile operator the specified number belongs to.

Otherwise, it may happen that a call to another region will cost the subscriber too much.

In addition, this AIS allows you to quickly and easily send free SMS to any number.

The program does not require installation and can be launched directly from a USB drive or CD.

The program is free, no registration required. The appearance of the AIS "Mobile Operators" is presented in Figure 1.

Fig.1. "Appearance of AIS Mobile operators"

1.4.2 AIS " MTS Service 1.15.45 "

Description: This is an application developed for iOS, with the help of which a subscriber can quickly find out about the status of his mobile account, connect and disconnect services, change his tariff plan and much more.

The main menu and search are shown in Figure 2.

Rice. 2. "Main menu AIS MTS Service"

1.4.3 AIS " ETC: Personal account 1.3 "

Description: The program provides a convenient tool for managing the personal account of a subscriber of the cellular operator CJSC "ETK" (Yeniseitelecom). The program consists of three modules: personal account, SMS service, help.

- Your personal account allows you to manage both your personal account and others (your own accounts, corporate, etc.). Works only when connected to the Internet (Wi-Fi, GPRS, 3G). The following operations are available:

Changing the list of services;

Replenishment of balance;

Block/unblock a number, etc.

The SMS service allows you to manage the personal account of only the active SIM card. No internet connection required. Operations such as managing the list of services and replenishing the balance are available.

Help is a short reference guide for the subscriber, built into the program. No internet connection required.

The main program window is shown in Figure 3.

Fig.3. "Main window of AIS ETC: Personal Account 1.3"

1.5 Rationale for the development of the automated information system "Operator"

The following disadvantages were identified in existing analogues:

There are no flexible mechanisms for restricting access to data

Lack of functionality

No multi-user access

High price

Suitable new technologies

A modern solution to the above problems is the development of the AIS "Operator", since:

Flexible interface

Possibility of creating a distributed information base

Low price for the final product

Relevance - the ability to quickly reflect changes.

Completeness of information, that is, providing the most complete information about orders, payments, and cars.

Convenience - clear interface.

Consistency and reliability of data.

Chapter Conclusion

The creation of this automated information system will allow us to take into account all the features for the implementation of services of a cellular operator.

Expected effect from implementation:

Ш Relevance - the ability to quickly reflect changes.

Ш Completeness of information, that is, providing the most complete information about the compiled estimate.

Ш Convenience - clear interface.

Ш Consistency and reliability of data.

Ш Consolidation of information at the enterprise.

2. Review of development tools

2 .1 Selecting a DBMS

Database management system (DBMS) ? a set of software designed for creating, maintaining and using a database.

Based on capabilities, there are two groups of DBMS:

1. Full-featured DBMS? the most powerful, multi-user, with data protection, copying and recovery systems (Oracle, Microsoft SQL Server, Informix, DB/2), but more complex DBMS.

2. Personal DBMS? with limited capabilities, but easier to use (Access, Visual FoxPro, Paradox, Clipper, dBase, Clarion, DataEase, DataFlex, R: BASE).

2 .1.1 Oracle Database

Oracle is one of the most powerful modern DBMSs designed for implementing corporate-level databases, which places severe demands on the server. It can run on most operating systems: Windows-NT, -2000, Linux, UNIX, AIX, Nowell Netware. And this, in turn, allows you to choose the most convenient server platform for corporate tasks. For example, if an organization prefers to use non-Windows operating systems, then it can easily afford it. Some organizations may focus on solutions based on UNIX systems, which are renowned for their reliability and stability as a server platform, while continuing to use the Windows familiar to users on client computers.

The main advantages of Oracle include support for very large databases (up to 64 GB), powerful development and administration tools, support for multiprocessing and two language environments, as well as integration with the Web. At the same time, the program imposes serious hardware requirements and a high price.

2 .1 .2 DBMS MS SQL Server-2008

MS SQL Server-2008 has become widespread both in our country and abroad, since it offers a wide range of administration services and is easily scalable. This allows it to be used in information systems for medium-sized businesses and large computer information systems (CIS).

The MS SQL Server platform is based on the Windows environment.

The main advantage of the program is its close integration with Microsoft software products and the ability to export/import data into most common data formats, which allows you to use MS SQL Server as a central data storage.

Server 2008 Express is a free edition of SQL Server. It is ideal for database training, for building small server applications, and for distribution by independent software vendors. This release includes a number of powerful features, including SQL Server 2008 Reporting Services, a server-based platform for creating and sending classic and interactive reports, and SQL Server 2008 Management Studio Express, a graphical environment that simplifies database management.

Power

Ability to develop high-performance applications that rely on the security, reliability, and scalability of the SQL Server engine.

Performance

SQL Server Express's tight integration with Visual Studio designers and SQL Server Management Studio helps you develop applications faster.

Flexibility

Create lightly coupled applications that can run offline and automatically synchronize with a central database.

Key Applications:

Entry-level databases, educational databases

Building powerful desktop applications

Free distribution rights for independent software developers.

2 .1.3 DBMS Firebird 2.1

Firebird (FirebirdSQL) is a compact, cross-platform, free database management system (DBMS) running on Linux, Microsoft Windows and a variety of Unix platforms.

The advantages of Firebird include a multi-version architecture (parallel processing of operational and analytical queries: reading users do not block writers), compactness (5Mb distribution), high efficiency and powerful language support for stored procedures and triggers.

Firebird has been used in a variety of industrial systems (warehouse and utility, financial and government sectors) since 2001. It is a commercially independent project of C and C++ programmers, technical advisors and developers of multi-platform database management systems, based on the source code released by Borland Corporation on July 25 2000 as a free version of Interbase 6.0.

Firebird fully supports SQL-92 Entry Level 1 and implements most of the SQL-99 standard with some very useful additions. This includes DML/DDL expressions, FULL/LEFT/RIGHT JOIN syntax, UNION, DISTINCT expressions, subqueries (IN, EXISTS), built-in functions (AVG, SUM, MIN, MAX, COALESCE, CASE, ..), integrity constraints ( PRIMARY KEY, UNIQUE, FOREIGN KEY), and all common SQL data types.

Firebird supports a variety of access methods, including: native component sets for C/C++, Delphi, classes for ADO, ODBC, JDBC (Jaybird), drivers for Python, PHP, OLE DB driver, dbExpress, .NET data provider and direct access using server client library (fbclient.dll or GDS32.dll)

Firebird supports large databases. Databases can be located in several files, the size limit of which depends on the operating system. The theoretical limit is currently 64TB for a single database file, so the main limitations are imposed by the file system and hard drive space.

Firebird is a database server. A single Firebird server can handle several hundred independent databases, each with multiple user connections. It is completely royalty free even for commercial use.

2 .2 Selecting a database development environment

2 .2.1 IBExpert 2009

IBExpert is a GUI shell designed for developing and administering InterBase and Firebird databases, as well as for selecting and changing data stored in the databases.

The developers point out the main advantages of IBExpert:

Ш support for InterBase versions 4.x, 5.x, 6.x, 7.x; Firebird 1.x, 2.x, 3.x; Yaffil 1.x;

Ш auto-completion of SQL code (names of tables, fields, etc.)

Ш search in metadata;

Ш metadata reports;

IBExpert has many components that make your work easier: a visual editor for all database objects, a SQL editor and script executor, a debugger for stored procedures and triggers, a scope builder, a tool for importing data from various sources, its own scripting language, and a database designer.

2 .2.2 Microsoft Access

Microsoft Access is a relational DBMS from Microsoft Corporation. Has a wide range of features including linked queries, communication with external tables and databases. Thanks to the built-in VBA language, you can write applications that work with databases in Access itself.

Ш Main components of MS Access:

Ш table builder;

Ш screen form builder;

Ш SQL query builder (SQL language in MS Access does not comply with the ANSI standard);

Ш builder of reports for printing.

They can call scripts in VBA, so MS Access allows you to develop applications and databases practically from scratch or write a wrapper for an external database.

Microsoft Jet Database Engine, which is used as the MS Access database engine, is a file-server DBMS and therefore is applicable only to applications that work with small amounts of data and with a small number of users simultaneously working with this data . Access itself lacks a number of mechanisms needed in multi-user databases, such as triggers.

Built-in means of interaction between MS Access and external DBMSs using the ODBC interface remove the limitations inherent in the Microsoft Jet Database Engine. MS Access tools that allow you to implement such interaction are called “linked tables” (a connection with a DBMS table) and “queries to the server” (a query in a SQL dialect that the DBMS “understands”).

To build full-fledged client-server applications based on MS Access, Microsoft Corporation recommends using MS SQL Server DBMS as a database engine. At the same time, it is possible to combine database management tools and development tools with the inherent simplicity of MS Access.

There are also known implementations of client-server applications based on Access 2003 with other DBMSs, in particular MySQL

2 .3 Selecting a Software Development Environment

2 .3.1 Delphi 2010

Delphi is an integrated software development environment for Microsoft Windows, Mac OS, iOS and Android in the Delphi language (formerly called Object Pascal), originally created by Borland and currently owned and developed by Embarcadero Technologies. Embarcadero Delphi is part of the Embarcadero RAD Studio suite and comes in four editions: Starter, Professional, Enterprise and Architect.

The environment is designed for rapid development (RAD) of application software for operating systems Windows, Mac OS X, as well as IOS and Android. Thanks to the unique combination of language simplicity and machine code generation, it allows you to directly, and, if desired, at a fairly low level interact with the operating system, as well as with libraries written in C/C++. The created programs are not dependent on third-party software, such as Microsoft .NET Framework, or Java Virtual Machine. The allocation and release of memory is controlled mainly by user code, which, on the one hand, tightens the requirements for code quality, and on the other hand, makes it possible to create complex applications with high requirements for responsiveness (working in real time). Cross-compilers for mobile platforms provide automatic counting of references to objects, making it easier to manage their lifetime.

2 . 3 .2 Eclipse

Eclipse is a free integrated development environment for modular cross-platform applications. Developed and supported by the Eclipse Foundation.

The most well-known applications based on the Eclipse Platform are the various "Eclipse IDEs" for software development in a variety of languages ​​(for example, the most popular "Java IDE", which was supported initially, does not rely on any proprietary extensions, uses a standard open API to access Eclipse platform)

Eclipse was originally developed by IBM as a successor to the IBM VisualAge development environment, as a corporate IDE standard for development in various languages ​​for IBM platforms. According to IBM, design and development cost $40 million. The source code was completely open sourced and made available after Eclipse was released to a community independent of IBM for further development.

Eclipse 3.0 (2003) adopted the OSGi service platform specifications as the runtime architecture. Since version 3.0, Eclipse has ceased to be a monolithic IDE that supports extensions, and itself has become a collection of extensions. It is based on the OSGi and SWT/JFace framework, on the basis of which the next layer is developed - RCP (Rich Client Platform, a platform for developing full-fledged client applications). RCP serves as the basis not only for Eclipse, but also for other RCP applications such as Azureus and File Arranger. The next layer is Eclipse itself, which is a set of RCP extensions - editors, panels, perspectives, the CVS module and the Java Development Tools (JDT) module.

Since 2006, the Eclipse Foundation has coordinated an annual Simultaneous Release, which occurs in June. Each release includes the Eclipse platform as well as a number of other Eclipse projects.

Eclipse primarily serves as a platform for developing extensions, which is why it has gained popularity: any developer can extend Eclipse with his own modules. There are already Java Development Tools (JDT), C/C++ Development Tools (CDT), developed by QNX engineers together with IBM, and tools for Ada languages ​​(GNATbench, Hibachi), COBOL, FORTRAN, PHP, etc. from various developers. Many extensions complement the Eclipse environment with managers for working with databases, application servers, etc.

Eclipse JDT (Java Development Tools) is the most famous module aimed at group development: the environment is integrated with version control systems - CVS, GIT in the main package, there are plugins for other systems (for example, Subversion, MS SourceSafe). Also offers support for communication between the IDE and the task (error) management system. The main package includes support for the Bugzilla bug tracker, and there are also many extensions to support other trackers (Trac, Jira, etc.). Because it is free and of high quality, Eclipse is the corporate standard for application development in many organizations.

Eclipse is written in Java, therefore it is a platform-independent product, with the exception of the SWT library, which is developed for all common platforms (see below). The SWT library is used instead of the standard Java Swing library. It relies entirely on the underlying platform (operating system), which provides a fast and natural-looking user interface, but sometimes causes compatibility and application stability issues across platforms.

The basis of Eclipse is the rich client platform (RCP). It consists of the following components:

Ш OSGi (standard bundles delivery environment);

Ш SWT (portable widget toolkit);

Ш JFace (file buffers, working with text, text editors);

Ш Eclipse working environment (panels, editors, projections, wizards).

The GUI in Eclipse is written using the SWT toolkit. The latter, unlike Swing (which independently emulates graphical controls), uses the graphical components of this operating system. The Eclipse user interface also depends on a GUI middleware called JFace, which makes it easy to build an SWT-based user interface.

Eclipse's flexibility is ensured by plug-ins, which makes it possible to develop not only in Java, but also in other languages, such as C/C++, Perl, Groovy, Ruby, Python, PHP, Erlang, Component Pascal, Zonnon and others.

2 .3.3 Microsoft Visual Studio

Microsoft Visual Studio is a line of Microsoft products that includes an integrated software development environment and a number of other tools. These products allow you to develop both console applications and applications with a graphical interface, including those with support for Windows Forms technology, as well as websites, web applications, web services in both native and managed code for all platforms, supported by Microsoft Windows, Windows Mobile, Windows CE, .NET Framework, Xbox, Windows Phone .NET Compact Framework and Microsoft Silverlight.

Visual Studio includes a source code editor with support for IntelliSense technology and the ability to easily refactor code. The built-in debugger can work as a source-level debugger or as a machine-level debugger. Other built-in tools include a form editor to make it easy to create an application's GUI, a web editor, a class designer, and a database schema designer. Visual Studio allows you to create and connect third-party add-ons (plugins) to extend functionality at almost every level, including adding support for source code version control systems (such as Subversion and Visual SourceSafe), adding new toolkits (for example, for editing and visual design of code in domain-specific programming languages ​​or tools for other aspects of the software development process (for example, the Team Explorer client for working with Team Foundation Server).

Chapter Conclusion

Among the vast number of existing DBMSs, Firebird 2.1 was chosen. since one of its advantages is support for multiple access methods, including: own sets of components for

C/C++ and Delphi. Firebird also supports large databases that can be located in several files. Another advantage of Firebird is its multi-version architecture, which provides parallel processing of operational and analytical queries (this is possible because reading users do not block writers), compactness (5Mb distribution), high efficiency and powerful language support for stored procedures and triggers.

The IBExpert 2009 shell was chosen as the database development environment because it has a number of advantages, such as:

Ш support for InterBase versions 4.x, 5.x, 6.x, 7.x; Firebird 1.x, 2.x; Yaffil 1.x;

Ш work simultaneously with several databases;

Ш separate editors for all database objects with syntax highlighting;

Ш powerful SQL editor with query history and the ability to run queries in the background;

Ш debugger of stored procedures and triggers;

Ш search in metadata;

Ш full and partial extraction of data and metadata;

Ш database object dependency analyzer;

Ш metadata reports;

Ш managers of users and user privileges;

Ш export data to various formats.

IBExpert has many components that make your work easier: a visual editor for all database objects, a SQL editor and script executor, a debugger for stored procedures and triggers, a scope builder, its own scripting language, and a database designer, etc.

Delphi 2010 was used as a software development environment because it has the following advantages:

Ш Speed ​​of application development.

Ш High performance of the developed application.

Ш Low requirements of the developed application for computer resources.

Ш Extensibility by integrating new components and tools into the Delphi environment.

Ш Possibility of developing new components and tools using Delphi’s own tools (existing components and tools are available in source code)

Ш Successful development of the object hierarchy

Ш De facto, a huge number of visual components from third companies are already available, some of which are freeware, some are shareware, some are commercial.

3. Relational database design

This database is designed based on the role model.

Role-based access control is a development of a policy of selective access control, in which the access rights of system subjects to objects are grouped taking into account the specifics of their application, forming roles.

Role-based access control allows you to implement flexible access control rules that change dynamically during the operation of a computer system.

This approach is used in DBMS security systems, and individual elements are implemented in network operating systems. The role-based approach is often used in systems for which users have a clearly defined range of their job duties and responsibilities, as in a given database.

Despite the fact that a Role is a set of access rights to objects of a computer system, role-based access control is by no means a special case of selective access control, since its rules determine the procedure for granting access to subjects of a computer system depending on the roles they have (or do not have) in every moment in time, which is typical for mandatory access control systems. On the other hand, the rules for role-based access control are more flexible than with the mandatory approach to control.

Since privileges are not assigned to users directly, and are acquired only through their role (or roles), managing individual user rights essentially comes down to assigning roles to them. This simplifies operations such as adding a user or changing a department by a user.

3.1 Development of table structure

The structure of the database for the AIS "Operator" is presented in Figure 4.

The database consists of 6 entities such as:

Ш Abonenti - This entity stores information about subscribers and includes the following attributes: subscriber code, last name, first name, patronymic, date of birth, passport data, residential address.

Ш Uslugi - this entity includes the following attributes: service code, description, note, cost.

Ш Tarifi - this entity includes the following attributes: tariff name, cost of incoming calls within the network, cost of outgoing calls within the network, cost of incoming calls from another operator, cost of outgoing calls to another operator, cost of incoming calls from a landline phone, cost of outgoing calls to a landline phone cost of SMS and cost of Internet traffic.

Ш Abonentskie_uslugi - this entity includes the following attributes: service code, contract number, connection date, expiration date of this service.

Ш Licevoi_schet - this entity includes the following attributes: id, personal account number, date, time, amount, contract number

Ш Zakluchenie_dogovora - this entity includes the following attributes: subscriber code, contract number, conclusion date, subscriber number, tariff, personal account number.

3.2 Table normalization

Normalization is the process of checking the structure of tables for anomalies, if there are any, then the tables are split into smaller tables. The normalization structure is presented in Figure 5.

Anomalies are situations when working with a database that can lead to ambiguous interpretation of data or inconsistent data. Anomalies occur in tables containing redundant data

Rice. 5. "Table normalization structure"

At the initial stage of database design, first normal form (1NF) is constructed: A table is in 1NF if there is an atomic value at the intersection of each row and column.

A relation is in 2NF if and only if the relation is in 1NF, and no, there are no key attributes that depend on the complex key part. In order to eliminate the dependence of attributes on part of a complex key, it is necessary to decompose the relationship into several relationships. In this case, those attributes that depend on part of the complex key are placed in a separate relation.

A relation is in 3NF if and only if the relation is in 2NF and all non-key attributes are mutually independent.

Attributes are said to be mutually independent if none of them is functionally dependent on the other.

A table is in BCNF (Normal Form Bays Code) if the determinants of all functional dependencies are potential key tables

A relation is in 4NF if the relation contains 2 multivalued dependencies.

A multi-valued dependency is a logical relationship between the values ​​of columns A and B in which for value A we can determine a set of values ​​for column B.

5NF is applied to tables that have several multivalued dependencies, and the attributes included in these dependencies are interconnected in meaning, that is, they are dependent on each other.

Relations are in DKNF (Domain Key Normal Form) if each integrity constraint imposed on this relation is a logical consequence of the definition of domains and keys.

Let's normalize the tables of the "Operator" database.

To do this, we select functional dependencies for each table and check for normal forms as shown in Figure 1. A functional dependency (FD) between columns means a logical “Many to One” relationship between the values ​​of these columns.

Abonenti table:

Functional dependencies:

1. Kod_abonenta > (Familiy, name, otchestvo, data_rogdeniy, seriy_pasporta, nomer_pasporta, kem_vidan, kogda_vidan, address)

2. (seriy_pasporta, nomer_pasporta) > (Kod_abonenta ,familiy, name, otchestvo, data_rogdeniy, kem_vidan, kogda_vidan, address)

3. (Familiy, name, otchestvo, data_rogdeniy, address) > (Kod_abonenta, seriy_pasporta, nomer_pasporta, kem_vidan, kogda_vidan)

Test for normal forms (NF):

1NF passed, 2NF passed, NFBC passed. There are no multivalued dependencies. The table is in DKNF.

Uslugi table

Functional dependencies:

1. Kod_uslugi > (Opisanie, primechanie, stoimost)

Table Abonentskie_uslugi

Functional dependencies:

1. Kod_uslugi > (Nomer_dogovora, data_podklucheniy, data_okonchaniy)

2. Nomer_dogovora > (Data_podklucheniy, data_okonchaniy)

3. (Nomer_dogovora, data_podklucheniy > (Data_okonchaniy)

1NF passed, 2NF passed, 3NF passed. There are no multivalued dependencies. The table is in DKNF.

Tarifi table

Functional dependencies:

1. Nazvanie_tarifa > (St_vh_vn_s, st_ish_vn_s, st_vh_dr_op, St_ish_na_dr_op, st_vh_s_gor_tel, st_ish_na_gor_tel, st_sms, internet_trafic)

1NF passed, 2NF passed, 3NF passed. There are no multivalued dependencies. The table is in DKNF.

Table Licevoi_schet

Functional dependencies:

1. Id > (Nom_licevogo_scheta, data, vremya, summa, nomer_dogovora)

2. Nom_licevogo_scheta > (Id, data, vremya, summa, nomer_dogovora)

3. (Nom_licevogo_scheta, data) > (vremya, summa)

4. Nomer_dogovora > Nom_licevogo_scheta

1NF passed, 2NF passed, 3NF passed. There are no multivalued dependencies. The table is in DKNF.

Table Zakluchenie_dogovora

Functional dependencies:

1. Kod_abonenta > (Nom_dogovora, data_zaklucheniy, abonents_nom, tariff, nom_licevogo_sheta)

2. Nom_dogovora > (Kod_abonenta, data_zaklucheniy, abonents_nom, tariff, nom_licevogo_sheta)

3. Subscribers_nom > Nom_licevogo_sheta

1NF passed, 2NF passed, 3NF passed. There are no multivalued dependencies. The table is in DKNF.

Thus, all detected update anomalies are eliminated. The relational model, consisting of relations in third normal form, is adequate to the described domain model.

3 .3 Design of integrity constraints

Table 1. "Abonenti"

Column name			Primary key/unique			Notes
						Subscriber code
						Subscriber's last name
						Subscriber name
						Subscriber's middle name
						Subscriber's date of birth
						Passport Series
						Passport ID
						Issued by
						When issued
						Subscriber address

Table 2. "Uslugi"

Table 3. "Subscriber_uslugi"

Column name		Null/	Primary key/unique			Notes
						Service code
						Contract number
Data_Podklucheniy						Service activation date
						Service end date

Table 4. "Zakluchenie_dogovora"

Column name		Null/	Primary key/unique			Notes
						Subscriber code
						Contract number
Data_zaklucheniy						Date of conclusion of the contract
						Subscriber number
						Tariff plan
No._Licevogo account						Subscriber's personal account number

Table 5. "Licevoi_schet"

Column name			Primary key/unique			Notes
						Serial number
Number_licevogo_scheta						Account number
						Contract number

Table 6. "Tarifi"

Column name		Null/	Primary key/unique			Notes
	Varchar					Tariff name
						Cost of incoming calls within the network
						Cost of outgoing calls within the network
						Cost of incoming calls from another mobile operator
						Cost of outgoing calls to another mobile operator
						Cost of incoming calls from a landline phone number
St_ish_na_gor_tel						Cost of outgoing calls to a landline phone number
						SMS cost
						Internet traffic cost per megabyte

3.4 Design of data sampling operations

The design of the data sampling operation is presented in Table 7.

Table 7. "Development of data sampling operations"

	Description of action	Input parameters (name, type)	Output parameters (name, type)	Execution algorithm
	Adding a new subscriber (procedure ADD_NEW_ABONENT)	KOD_ABONENTA integer FAMILIY varchar(25) NAME varchar(15), OTCHESTVO varchar(25), DATA_ROGDENIYA date, SERIY_PASPORTA integer, NOMER_PASPORTA integer, KEM_VIDAN varchar(35), KOGDA_VIDAN date, ADDRESSvarchar		Check whether there is a person with the same subscriber code in the Abonenti table, if so, then exit with error code 0, if not, then add a new row with data about the new client to the table and send the values ​​of the output parameters to exit with code 1
	Editing subscriber data (UPDATE_DANNIE_OB_ABONENTE procedure)	KOD_ABONENTA integer FAMILIY varchar(25) NAME varchar(15), OTCHESTVO varchar(25),DATA_ROGDENIYA date, SERIY_PASPORTAinteger,NOMER_PASPORTA integer,KEM_VIDAN varchar(35), KOGDA_VIDAN date,ADDRESSvarchar(85)	Error code - integer: 0 - error	Check whether there is a person with the same subscriber code in the Abonenti table, then change the necessary data and exit with parameter 1, if not, then exit with error code o.
	Deleting a subscriber (DELETE_ABONENT procedure)	KOD_ABONENTA integer	Error code - integer: 0 - error	Check whether there is a person with the same subscriber number in the Abonenti table, if so, delete the line with his data, if not, then exit with error code 0.
	Adding a new contract (procedure ADD_DOGOVOR)	KOD_ABONENTA integer, NOM_DOGOVORA integer, DATA_ZAKLUCHENIY date, ABONENTS_NOM bigint, TARIF varchar(45), NOM_LICEVOGO_SCHETA integer	Error code - integer: 0 - error	Check whether there is a contract number in the Zakluchenie_dogovora table that matches the one entered, if yes, then exit with error code 0, if not, then add a new row with all the data to the table and send the values ​​of the output parameters to exit with code 1
	Deleting a contract (procedure DELETE_DOGOVOR)	NOM_DOGOVORA integer	Error code - integer: 0 - error	Check whether there is a contract number in the Zakluchenie_dogovora table that matches the one entered, if so, then delete the row from the table, if not, then exit with error code 0.
	Adding a new tariff plan (procedure ADD_NEW_TARIF)	NAZVANIE_TARIFA varchar(45), ST_VH_VN_S float,ST_ISH_VN_S float,ST_VH_DR_OPfloat,ST_ISH_NA_DR_OP float, ST_VH_S_GOR_TEL float, ST_ISH_NA_GOR_TEL float ST_SMS float, NTERNET_TRAFIC float	Error code - integer:	Check whether a tariff with the same name exists in the Tarifi table, if so, exit with error code 0, if not, add a line with information about the tariff to the table and send the values ​​of the output parameters to exit with code 1
	Changing tariff data (UPDATE_DANNIE_O_TARIFE procedure)	NAZVANIE_TARIFA varchar(45), ST_VH_VN_S float,ST_ISH_VN_S float,ST_VH_DR_OPfloat,ST_ISH_NA_DR_OP float, ST_VH_S_GOR_TEL float, ST_ISH_NA_GOR_TEL float ST_SMS float, NTERNET_TRAFIC float	Error code - integer:	Check if there is a tariff with the same name in the Tarifi table, if yes, then change the data and send the values ​​of the output parameters to the output with code 1, if not, then exit with error code 0
	Deleting a tariff (DELETE_TARIF procedure)	NAZVANIE_TARIFA varchar(45)	Error code - integer: 0 - error	Check whether a tariff with the same name exists in the Tarifi table; if so, then delete the row from the table, otherwise we exit with error code 0.
	Adding a new service (procedure ADD_NEW_USLUGA)		Error code - integer: 0 - error	Check whether a service with the same service code exists in the Uslugi table, if so, then exit with error code 0, if not, then add a line with information about the service to the table and send the values ​​of the output parameters to exit with code 1
	Changing information about services (procedure UPDATE_DANNIE_OB_USLUGAH)	KOD_USLUGI integer, OPISANIE varchar(150), PRIMECHANIE varchar(150), STOIMOST float,SPOSOB_PODKLUCHENIY varchar(200)	Error code - integer:	Check whether a service with the same service code exists in the Uslugi table, if yes, then change the data and send the values ​​of the output parameters to the output with code 1, if not, then exit with error code 0
	Deleting a service (procedure DELETE_USLUGA)	KOD_USLUGI integer	Error code - integer: 0 - error	Check whether a resource with the same service code exists in the Uslugi table; if so, then delete the row with the data, otherwise we exit with error code 0
	Adding a personal account (procedure ADD_NEW_LIC_SCHET)	ID integer, NOM_LICEVOGO_SCHETA integer, DATA date VREMYA time, SUMMA float, NOMER_DOGOVORA integer	Error code - integer:	Check whether a client with the requested id exists in the Licevoi_schet table, if so, then we exit with error code 0, otherwise we add data to the table and send the values ​​of the output parameters to the exit with code 1
	Deleting a personal account (DELETE_LIC_SCHET procedure)		Error code - integer: 0 - error	Check whether a client with the requested id exists in the Licevoi_schet table, if so, delete the row with the data, otherwise exit with error code 0
	Changing the deposited amount (UPDATE_SUMMA procedure)	NOM_LICEVOGO_SCHETA integer, SUMMA float,	Error code - integer: 0 - error	Check whether a client with the requested id exists in the Licevoi_schet table, if so, then change the amount and send the value 1 to the output, otherwise we exit with error code 0

3.5 Issue of access rights

Access rights to database objects are given in Table 8. Horizontal - database objects. Vertically - users or roles. In the cells - a combination of letters indicating access rights:

s - read permission (select);

i - the right to add rows (insert);

u - right to edit lines (update);

d - right to delete rows (delete);

e - the right to run stored procedures (execute).

Table 8. "Issuing access rights"

Similar documents

Information in the modern world is one of the most important resources. Consideration of the features of developing an information system for automating the workplace of a telephone company operator for the provision of services. Stages of creating an information base.

course work, added 03/13/2013


Development of an automated control system for a mobile operator. Data modification operators Insert, Update, Delete in the MS SQL Server environment. Database structure. Scheme of the user's dialogue with the application, the order of using views.

course work, added 04/21/2015


Terms of reference for the development of an automated system and warehouse accounting for the management of a universal trading base. Designing an information system and choosing an environment for creating a software product. Interface creation and user manual.

thesis, added 07/11/2015


Analysis of the design of an automated information system for the Jay computer store. Development of a database in the Transact-SQL language in the Microsoft SQL Server 2000 database management system. Calculation of the cost and price of the software product.

course work, added 08/16/2012


Selecting a design methodology and developing an information system "Payroll calculation" for the enterprise OJSC RTP "Avtoremontnik". Architectural design of the information system database and development of its interface. Testing the software module.

thesis, added 05/25/2014


Detailed system functions and requirements for the information system. Analysis of user categories. Stages of implementation of an automated information system in an enterprise. Description of database tables. Data protection from unauthorized access.

thesis, added 07/22/2015


Analysis of existing database management systems and selection of the optimal one. Creation of an automated information system "Polyclinic", definition of entities and relationships, description of a physical model, interface design, program algorithm.

course work, added 11/21/2009


Justification for the choice of software used. Input and output information. Relational model of a domain database. Creating an information system model using Run All Fusion Process Modeler r7. Test results.

course work, added 04/12/2014


Studying the technological process of a billing company. Infrastructure for providing communication services. Basic business processes. Goals and objectives of the designed information system "Working with subscribers of a cellular operator." Stages of project development.

course work, added 01/17/2009


Analysis of the automation area. User interface and database design. Selecting a platform for creating an information system. Interaction of the application with data sources. Estimating the duration and cost of software development.

In order to ensure interdepartmental information interaction and provide access to information systems and resources of the city of Moscow, the Moscow Government decides:

1. Approve the Regulations on the automated information system "System for monitoring information systems of the city of Moscow" (appendix).

2. Establish that the Moscow Department of Information Technologies is the operator and state customer of the creation, development, and operation of the automated information system “Moscow City Information Systems Monitoring System.”

3. Control over the implementation of this resolution shall be entrusted to the Minister of the Moscow Government, Head of the Department of Information Technologies of the City of Moscow Ermolaev A.V.

Mayor of Moscow S.S. Sobyanin

REGULATIONS ON THE AUTOMATED INFORMATION SYSTEM "MONITORING SYSTEM FOR INFORMATION SYSTEMS OF THE CITY OF MOSCOW"

1. These Regulations on the automated information system "System for monitoring information systems of the city of Moscow" (hereinafter - the Regulations) define the purpose, structure, functions, rules for using the automated information system "System for monitoring information systems of the city of Moscow" (hereinafter - SMIS).

2. SMIS is an automated information system of the city of Moscow, containing information, software and hardware that ensures the automation of interaction processes between the SMIS operator, suppliers of information processed in SMIS, and users of information for the purpose of management and operational quality control of the operation of information systems of the city of Moscow and provision provision of communication services for the needs of executive authorities of the city of Moscow and government agencies of the city of Moscow subordinate to them.

3. SMIS is the property of the city of Moscow.

4. The objectives of SMIS are:

4.1. Automation of the process of organizing and ensuring the continuous and high-quality functioning of information systems and resources of the city of Moscow, as well as communication services provided to the executive authorities of the city of Moscow and their subordinate government agencies of the city of Moscow.

4.2. Providing a unified information space and organizing centralized management of access to services and functionality of SMIS within the framework of the corporate multiservice network of the Moscow Government.

4.3. Improving the quality of operation of information systems and resources of the city of Moscow through prompt identification and response to technical failures in the performance of information systems of the city of Moscow and the provision of communication services for executive authorities of the city of Moscow and government agencies of the city of Moscow subordinate to them.

4.4. Control of the quality, volume and timeliness of fulfillment of obligations by contractors under government contracts concluded by the Moscow Department of Information Technologies in order to ensure the operation of information systems and resources of the city of Moscow and the provision of communication services for the executive authorities of the city of Moscow and government agencies of the city of Moscow subordinate to them.

4.5. Taking the process of quality control of the operation of information systems of the city of Moscow, as well as ensuring the provision of communication services for executive authorities of the city of Moscow and their subordinate government agencies of the city of Moscow to a new level by creating functionality for conducting analysis on several parameters with the ability to use criteria for selecting and aggregating data , as well as justified handling of claims with contractors under government contracts concluded by the Moscow Department of Information Technologies.

4.6. Automation of the process of collecting information on the functioning of information systems and resources of the city of Moscow and increasing the efficiency of its processing in order to ensure the stable functioning of information systems of the city of Moscow and high-quality provision of communication services for the needs of executive authorities of the city of Moscow and government agencies of the city of Moscow subordinate to them.

4.7. Increasing the efficiency of using funds from the budget of the city of Moscow, provided for financial support for the operation of information systems of the city of Moscow and the provision of communication services to executive authorities of the city of Moscow and government institutions of the city of Moscow subordinate to them.

5. SMIS consists of the following subsystems:

5.1. Unified Directory Service.

5.2. Monitoring information systems and resources of executive authorities of the city of Moscow.

5.3. Unified system for monitoring and administering telecommunication services of executive authorities of the city of Moscow.

6. The main functions of SMIS are:

6.1. Administration of user accounts and rights for access to information systems of the city of Moscow, ensuring authorization of users at workplaces and in information systems of the city of Moscow using a single account.

6.2. Prompt collection and analysis of information on the performance of information systems of the city of Moscow, informing executive authorities of the city of Moscow and government agencies of the city of Moscow subordinate to them about failures in the operation of information systems and the provision of communication services.

6.3. Collection of statistical information on the functioning of information systems in the city of Moscow.

6.4. Accounting, monitoring and management of communication services provided to the executive authorities of the city of Moscow and government agencies of the city of Moscow subordinate to them, as well as information resources used to ensure the provision of communication services.

6.5. Processing applications from the executive authorities of the city of Moscow for connecting and/or disconnecting communication services, changing the conditions for their provision.

6.6. Collection and synthesis of information about the incorrect operation of information systems of the city of Moscow, failures in the provision of communication services, received from participants in information interaction using SMIS, which is the basis for conducting claims work.

6.7. Automated interaction with the information systems of telecom operators providing communication services in the interests of the executive authorities of the city of Moscow and their subordinate government agencies of the city of Moscow on the basis of government contracts concluded by the Department of Information Technologies of the city of Moscow, in order to ensure control of the quality, volumes and timing of the provision of communication services.

6.8. Generation of statistical and operational reports on the functioning of information systems of the city of Moscow and the quality of communication services provided in the interests of the executive authorities of the city of Moscow and the government institutions of the city of Moscow subordinate to them.

7. Participants in information interaction using SMIS are users and suppliers of information, performers of services (work) provided for the operation of information systems of the city of Moscow, communication services, and the SMIS operator.

8. Users of information are the executive authorities of the city of Moscow.

9. Information providers are the executive authorities of the city of Moscow, government agencies of the city of Moscow and providers of services (work) for the operation of information systems of the city of Moscow and the provision of communication services.

10. Information providers:

10.1. Place in SMIS information about the equipment of information and telecommunication systems used and its configuration parameters, about the required communication services and their parameters, about failures that have arisen, malfunctions in the operation of information systems and resources of the city of Moscow, about the inadequate quality of provision of communication services and then update it in the following manner and deadlines established by the Moscow Department of Information Technologies.

10.2. Appoint persons authorized to carry out operations for posting information in SMIS, and arrange for authorized persons to receive identifiers (logins) and passwords for working in SMIS.

10.3. Ensure the completeness, reliability and relevance of the information provided in the SMIS, as well as the entry of the specified information into the SMIS within the time limits established by the Moscow Department of Information Technologies.

11. The procedure for information interaction between its participants, the regulations for access and work in SMIS, the timing of providing information to SMIS are determined by the Department of Information Technologies of the city of Moscow.

12. SMIS operator:

12.1. Provides methodological guidance for the use of SMIS, including providing consultations to users and information providers on technical support and operation of SMIS.

12.2. Provides operation and technical support for SMIS operation around the clock.

12.3. Organizes the implementation of work on the development (modernization) and operation of SMIS.

12.4. Connects information systems of the city of Moscow to SMIS that meet the technical requirements established by the Department of Information Technologies of the city of Moscow.

12.5. Provides interaction with the information systems of those performing work on the operation of information systems of the city of Moscow and the provision of communication services.

12.6. Provides differentiation of access rights to SMIS, keeps records and statistics of user activity in accordance with the regulations for access and work in SMIS.

12.7. Organizes work to ensure the safety of information posted in SMIS.

12.8. Provides consulting support to participants in information interaction on the use of SMIS.

13. Connection and interaction of information systems of the city of Moscow using SMIS is carried out in accordance with the requirements for such connection and interaction approved by the Department of Information Technologies of the city of Moscow.

14. The SMIS operator is not responsible for the content, quality and reliability of information transmitted to SMIS by information providers.

15. Certain functions of the operator may be transferred to a subordinate government agency of the city of Moscow or another organization by decision of the Department of Information Technologies of the city of Moscow in accordance with the legislation of the Russian Federation and the city of Moscow.

• Guidelines on the procedure for submitting application documents for registration of information resources... Guidelines on the procedure for entering application documents for registration of information resources and systems in the Register of state and municipal information resources and systems of the Moscow region
• Order of the Moscow Department of Information Technologies dated March 11, 2012 N 64-16-157/12 On approval of the regulations for connecting information systems to the state information system "Unified Data Storage and Processing Center", regulations for access to information processed in the state information system "Unified Data Storage and Processing Center", and the procedure for maintaining a register of information suppliers to the state information system "Unified data storage and processing center"
• Order of the Ministry of Economy of the Moscow Region dated May 14, 2010 N 30-RM On amendments to the List of information resources and information systems of the Ministry of Economy of the Moscow Region, approved by order of the Ministry of Economy of the Moscow Region dated November 5, 2008 N 49-RM "On approval of the Regulations for the provision of information from information resources and information systems of the Ministry of Economy of the Moscow Region"
• Order of the Main Directorate of the Civil Registry Office of the Moscow Region dated August 27, 2013 N 42 On amendments to the Administrative Regulations for the provision of public services for providing users with information from state information resources and information systems of the Moscow Region, administered by the Main Directorate of Civil Registry of the Moscow Region, and the List of information resources and information systems of the Main Directorate of Civil Registry Office of the Moscow Region
• Order of the Moscow Government dated December 20, 2007 N 2858-RP On the commissioning of the automated information system "Unified City Environmental Monitoring Data Fund. Collection, analysis and forecast of the environmental situation in the city of Moscow and the provision of environmental information to government authorities and the population. GIS "City Ecology" and the first stage of the automated information system "Register of Greens" plantings
• Order of the Moscow Department of Information Technologies dated November 22, 2012 N 64-16-1048/12 On approval of the regulations for the functioning of the automated information system "Standard solution for the portal of the executive authority of the city of Moscow" and the requirements for connection and interaction with users of the automated information system "Standard solution for the portal of the executive authority of the city of Moscow"
• Decree of the Moscow Government dated December 9, 2014 N 722-PP About the automated information system "Information and analytical system for monitoring the crime situation and public safety in the city of Moscow"