Introduction

The title under consideration is written on the basis of Donetsk Donetsk Manufactory for the Cleonelly Store.

One of the leading activities of OAO Donetsk manufactory produces sewing products in a wide range, mostly bathrobes, sheets and towels. In addition, the company produces painted cotton yarn for weaving and knitted production.

The development of automated information technologies is in parallel with the emergence of new types of technical means of processing and transmitting information, improving the organizational forms of computer use, infrastructure saturation with new means of communications. The development of market relations led to the emergence of new types of entrepreneurship and, above all, to the creation of firms engaged in information business, the development of information technologies, their improvement, the spread of components of automated information technologies, in particular software products that automate informational and computing processes. Also include computing equipment, communications, office equipment and specific types of services - information, technical and consulting services, training, etc. This contributed to the rapid dissemination and efficient use of information technologies in managerial and industrial processes, virtually widespread applications and a large manifold.

Enterprises engaged in the design and development of devices for various purposes, currently use various means of both automated design - CAPR (CAD) and monitoring production processes - ASUTP (SCADA / DCS). However, for own development devices, it is necessary to develop their own means of controlling their performance and product quality analysis.

The technological process of taking into account products in the warehouse in the Cleanelly store includes a stage of keeping the goods sold.

The purpose of the present graduation project is the implementation of an automated workplace (AWA) allowing the product accounting in the store's warehouse.

To achieve the above goal, the following tasks must be solved:

¾ to conduct an analysis of the store business processes;

¾ Explore information flows arising at the stage of the developed product being developed;

¾ Develop a conceptual and logical data model;

¾ Develop software for promoting products

¾ Conduct an assessment of the economic efficiency of the information system.

1 Development of software requirements

1.1 Analysis of existing solutions

Currently, there is a wide range of companies that combine both the direct development of products, so the development of systems for managing these products. Such systems are developed as such widely well-known companies as 1: with the enterprise and the "star". In such systems, monitoring materials and processing of the information obtained are monitored.

"1C: Enterprise" is a system of applied solutions built according to the unified principles and on a single technological platform. The head can choose a solution that meets the current needs of the enterprise and will continue to develop as the enterprise or expand automation tasks.

The program "1C: Enterprise" program is designed to solve a wide range of accounting and management automation tasks facing dynamically developing modern enterprises. Solving topical accounting and management tasks The composition of the program "1C: Enterprise" is focused on current needs of enterprises. The company "1C" produces circulation software solutions designed to automate typical accounting and management tasks in enterprises. A distinctive feature of the circulation solutions of the company "1C" is the careful study of the composition of functionality included in typical solutions. The company "1C" analyzes the experience of users using the program "1C: Enterprise" and tracks the change in their needs.

The main advantages of my system, the wholesale base can be attributed to the relative low cost of introducing this system, as well as a number of advantages:

¾ Reliability of the applications created. The software package (PC) must be stable not only to user errors, but also to failures in the system of communications.

¾ ease of use of the interface;

¾ High security level of the system, which implies not only control of the availability of certain system resources and the security of information at all stages of operation, but also tracking actions with a high degree of reliability.

1.2 Analysis of the subject area

The peculiarity of the analysis of the subject area is that it allows you to see the entire set of operations of the organization.

For analysis and reorganization of business processes, Case is intended – Top Level Tool All Fusion Process Modeler (BPWIN), supporting IDEF0 methodologies (functional model), DFD (DataFlow Diagram) and IDEF3 (Workflow Diagram). BPWIN is a powerful software product to create models that allow you to analyze, document and plan changes in complex business processes. BPWIN offers a tool to collect all the necessary information about the work of the enterprise and the graphic image of this information in the form of a holistic and consistent model.

From the point of view of the functionality of the system. As part of IDEF0 methodology (Integration Definition for Function Modeling), the business process is presented in the form of a set of elements-works that interact with each other, and also shows information, human and production resources consumed by each work. The functional model is designed to describe existing business processes in the enterprise (the so-called AS-IS model) and the ideal position of things – What you need to strive for (model TO-BE). IDEF0 methodology prescribes the construction of a hierarchical diagram system, i.e. Single descriptions of system fragments. First, the system describes the system as a whole and its interaction with the outside world (contextual diagram), after which a functional decomposition is held – The system is divided into subsystems and each system is described separately (decomposition diagrams). Then each subsystem is divided into smaller and so on to achieve the desired degree details.

If in the process of modeling it is necessary to illuminate the specific sides of the enterprise technology, BPWin allows you to switch to any branch of the model of DFD or IDEF3 notation. DFD diagrams (Data Flow diagramming) may add something that is already reflected in the IDEF3 model, as they describe the data streams, allowing you to trace how information is exchanged between business functions inside the system. At the same time, the DFD diagram is disregarding the interaction between business functions.

From the point of view of the sequence of work performed. And even more accurate picture can be obtained by adding the model by IDEF3 diagrams. This method draws attention to the order of events. The IDEF3 includes logic elements, which allows you to simulate and analyze alternative business process development scenarios.

To consider business processes running in the store store, it is necessary to use only two IDEF0 and DFD methodologies. The process of modeling any system in IDEF0 begins with the definition of context, i.e. The most abstract level of the description of the system or business processes in general.

IDEF0 model . To explore the business processes "Formation of the supplier's order", "Getting goods", "Vacation of goods", consider the charts that are presented in the form of IDEF0 diagram. IDEF0 The system is represented as a set of interacting works or functions.

The IDEF0 methodology is based on four basic concepts.

The first of them is the concept functional block (Activity Box) . The function block is graphically portrayed as a rectangle and personifies some specific function within the framework of the system under consideration.

Each of the four sides of the function block has its own definite value (role), while:

The top side has the "Control" value;

The left side is "input" (INPUT);

The right side has a "output" (OUTPUT);

The lower side has the value "Mechanism".

The second "whale" IDEF0 methodology is the concept of an interface arc (arrow). The graphical display of the interface arc is a unidirectional arrow. Each interface arc must have its name (arrow label). Using interface arcs, various objects display, to one degree or another, the defining processes occurring in the system. At the same time, the arrows, depending on which the edge of the rectangle of work they enter or from which edge go out, are divided into:

Input arrows (included in the left side of the function block) - data or objects changeable during operation;

Management arrow (included in the upper facet of the function block) - depict the rules and limitations, thanks to which work is performed;

The exit arrows (come out of the right side of the function block) - depict data or objects that appear as a result of work;

The arrow of the mechanism (included in the bottom face of the function block) - depict resources (for example, equipment, human resources).

The third basic concept of IDEF0 is decomposition (Decomposition). The principle of decomposition is used when splitting the complex process to the components of its function.

Decomposition allows you to gradually and structured to represent the system model in the form of a hierarchical structure of individual diagrams, which makes it less overloaded and easily absorbed.

The last of the concepts IDEF0 is a glossary (Glossary). For each of IDEF0 elements: diagrams, function blocks, interface arcs The existing standard involves creating and maintaining a set of appropriate definitions, keywords, narrative presentations, etc., which characterize an object displayed by this element. This set is called glossary and is a description of the essence of this item.

Consider the chart of business processes flowing at the store of the store DMM, Cleonelly:

For the general visibility of the system, it is necessary to build the context of the "Activities of the enterprise warehouse" (see Figure 1.1).

Figure 1.1 - Diagram "Warehouse Activities"

After the context is installed, decomposition is carried out, i.e. Building the following charts in the hierarchy.

Each subsequent diagram is a more detailed description of one of the works on the higher chart. An example of decomposition of contextual work is shown in Figure 1.2. Thus, the entire system is divided into subsystems to the desired level of detail, this system is divided into three levels.

Figure 1.2 - First-Level Decomposition Chart

Figure 1.3 - Diagram "Product Design"

Figure 1.4 - Diagram "Vacation of goods"

Figure 1.5 - Diagram "Calling goods"

DFD. The basis of this methodology is the construction of the model of the analyzed IC - projected or actually existing. In accordance with the methodology, the system model is defined as a hierarchy of data stream diagrams (DFD), describing the asynchronous process of converting information from its input to the system before issuing the user. DFD diagrams are usually built for a visual image of the current work of the organization document management system. Most often, the DFD diagram is used as an addition to the model of business processes made in IDEF0.

The main components of the data stream diagrams are:

External entities (graphically depicted by a square) - indicate a material subject or an individual, which is a source or receiver of information. For example: customers, staff, suppliers, customers, warehouse;

Systems / subsystems (graphically looks like a rectangle with rounded corners) - work indicating functions or processes that processed and change the information;

Data drives - are an abstract device for storing information, which can be placed at any time in the drive and after some time to extract, and the ways of room and extraction can be any. The data storage device in general is the prototype of the future database and the description of the data stored in it must be linked to the information model;

Data streams - determines the information transmitted after a connection from the source to the receiver. The data stream on the diagram is depicted with a line of an end arrow that shows the flow direction.

Consider a data stream diagram (DFD) "Vacation of goods" Figure 1.6. This diagram shows the movement of documents when entering the organization "Applications for goods".

Figure 1.6 - DFD diagram "Vacation of goods"

Consider the following diagram of data streams "Product Design" (see Figure 1.7). Here, the process of performing work and the movement of documents at the "issue of goods" is shown.

Figure 1.7 - DFD diagram "Product registration"

In data stream diagrams, all the characters used are folded into the common picture, which gives a clear idea of \u200b\u200bwhich data is used, and what functions are performed by the document management system. It often finds out that existing information flows, important for the company's activities, are realized unreliable and need to be reorganized. *******

The organizational structure of an enterprise engaged in the sale of terry products is considered on the example of the company "Donetsk Manufactory M" of the Cleonelly store:

In the direction of development of control systems and accounting materials, problems can be successfully solved:

1. This is control over the goods supplied and stored in stock.

2. Information about suppliers and consumers

3. Also contains information Information and operations for the product.

4. Contains the report log of released goods.

5. Certificate of goods

6. Automation of warehouse functions (arrival, consumption, write-off, product reservation)

7. Registration and storage of accounts for purchased and sold goods and services, as well as an extract for prepayment accounts, with a delay of payment and delivery of goods

8. Creating overhead and accounting of issued goods

9. Conducting inventory of warehouses with the creation of a sidewater, an act of shortage of shortage and surplus

10. Creating sets of goods

As indicated by the main area of \u200b\u200bactivity of this enterprise is the sale of cotton products. The design process includes many steps of carefully worked out by the management structures of project enterprises during the entire lifetime of this enterprise. This process cannot be changed at the same time, since it involves many divisions of the enterprise itself, external subcontractors and customers of the project company. Therefore, enterprises with caution relate to the implementation of information systems related to design and development management processes. As a rule, Russian enterprises use their own developments in this area.

1.3 Collecting requirements

When designing an information system (IP) "ARTS Wholesale store", it was necessary to collect requirements that would help create an interface in such a way that the end user (store employee) was convenient to work with the developed IP.

Development of requirements is a process that includes the activities necessary to create and approve a document containing the specification of system requirements.

To implement the process of accounting and monitoring materials, it is necessary that the information system can perform the following functional requirements:

¾ Documenting results.

¾ The information system must be implemented as a program based on an integrated Visual Fox Pro environment.

The program is executed in the Windows 2000 / NT / XP operating system.

There are four main stages of the process of developing requirements (Figure 1.8):

Analysis of the technical feasibility of creating a system;

Formation and analysis of requirements;

Specifications of requirements and the creation of relevant documentation;

Certification of requirements.

Collecting requirements is an important step in design design, since it is here that all the requirements of the customer must be correct and are correctly formulated.

1.4 Specification of requirements

Definition of correct requirements is probably the most responsible stage of the software project. It is very important that the project format is consistent with the requirements for software collected by the developer team, otherwise these requirements will not be able to be supported and presented in the software product. Software Software Requirements Software Requirements Specification (SRS) is key to the entire software development life cycle. This is not only a derivative document in which the specifications of the program project, but also the main document applied to conduct certification and acceptance tests. Certification is an assessment of the quality of the work of project managers. It determines the degree of compliance of the software product established requirements. The SRS specification acts as a kind of mechanism for fixing system requirements, which are used as criteria for certification.

Based on SRS, consent is achieved between customers and software manufacturers. The SRS specification fully describes the functions that the software product has been developed. This allows potential users to determine the degree of product compliance with their needs, as well as the product modification paths in order for it as much as possible in solving their tasks.

Development of temporary development costs. The preparation of SRS specifications involved various groups in the organization of the Customer. They carefully examine all the requirements even before the direct development of the project begins. This reduces the likelihood of subsequent re-development of the project, encoding and testing.

With a thorough study of the requirements presented in the SRS specification, it is possible to detect overdocks, misunderstandings and contradictions in the early stages of the development cycle when problems are much easier than in later stages.

SRS specification becomes the basis for estimating the cost and preparation of the work schedule. Product Description is a real basis for estimating the cost of the project. In an environment where there is a concept of formal proposal, SRS is used to approve the assessment of the offer or price.

With the help of proposed SRS specifications at the organization level, the organization may develop much more productive plans of certification and inspections. As a part of the development contract, SRS provides a reference point to assess compliance with specifications.

Thanks to the SRS specification, the program product is facilitated by new users, as well as its installation on other computers. Thus, it becomes easier for customers to transfer the software product to other units of the organization, and to developers to transmit to other customers.

SRS Specification serves as the basis for upgrading. This document discusses the product itself, and not the project development process, therefore it is possible to expand the completed product on its basis.

After the definition process and specifications are completed, it is necessary to carry out certification of requirements.

The specification of the requirements for the software project must be presented in Appendix A.

1.5 Certification of requirements

Certification should demonstrate that the requirements really define the system that the customer wants to have. Checking the requirements is important, since the error in the requirements specification can lead to a system alteration and high costs, if they are detected during the system of system development or after its commissioning.

During the certification process, various types of documentation checks must be performed:

1. Check the correctness of the requirements.

2. Check for consistency.

3. Check for completeness.

4. Check for feasibility.

There are a number of certification methods of requirements that can be used together or each separately:

1. Review of the requirements.

2. Prototyping.

3. Generation of test scenarios.

4. Automated consistency analysis.

The most visual for the customer system is prototyping.

Before you start creating prototypes, you can create a user interface stream diagram. This diagram is used to explore the relationship between the main elements of the user interface.

The next step of certification of requirements is the direct creation of prototypes.

The prototype of software is a partial or possible implementation of the proposed new product. Prototypes allow you to solve three main tasks: clarification and completion of the formulation of the requirements, research of alternative solutions and the creation of the final product.

The prototype of the main menu of this module is shown in Figure 1.9.

1.6 Choosing the Information System Design Methodology

The essence of a structural approach to the development of IP is its decomposition (partition) on automated functions: the system is divided into functional subsystems, which in turn are divided into subfunctions divided into tasks and so on. The partitioning process continues to specific procedures. Pi this automated system retains a holistic representation in which all components are interconnected.

All the most common methodologies of the structural approach are based on a number of general principles. The following principles are used as two basic principles:

The principle of "divide and conquer" is the principle of solving complex problems by dividing the many smaller independent tasks, easy to understand and solve;

The principle of hierarchical ordering is the principle of organizing the components of the problem into hierarchical tree structures with the addition of new parts at each level.

In structural analysis, there are mainly two groups of funds illustrating the functions performed by the system and the relationship between the data. Each group of funds correspond to certain types of models (diagrams), the most common, among which are the following:

SADT (STRUCTUD ANALYSIS AND DESIGN TECHNIQUE) Models and corresponding functional diagrams;

DFD (Data Flow Diagrams) data stream diagrams;

ERD (Entity-Relationship Diagrams) Chart "Essence-Communication".

At the design stage of the IC model expands, refineed and complemented by diagrams reflecting the software structure: architecture of software, structural schemes of programs and on-screen diagrams.

The listed models in the aggregate give a complete description of the IC regardless of whether it exists or newly developed. The composition of the charts in each specific case depends on the required completeness of the system description.

2 Designing information system

2.1 Architectural design

When creating any complex information system, a critical aspect is its architecture, where it is a conceptual vision of the structure of future functional processes and technologies at the system level and in relationships. Typically, complex information systems of organizations are designed as a composition of components that interact at a high level, which can be systems themselves. The architecture of the organization information system makes an understanding of the system easier by defining its functionality and structure in a manner that reveals the design solutions and allows the browser to ask questions about the satisfaction of the design requirements, the distribution of functionality and the implementation of components.

The architecture of the organization information system is a model of how information technology will support the main objectives and strategy for the development of an automated object. It allows you to critically think and clearly express the view of how integrated sets of information systems should be structured to implement these purposes. The architecture of the information system describes how information systems, applications and people work within the whole organization in a uniform unified manner.

Thus, the information system architecture includes a generally accepted set of components that provide "building blocks" of the information system. These "building blocks" and their characteristics are defined at the appropriate level of detail to meet the needs performed by planning solutions.

When designing modern information systems of organizations, their architecture should be developed taking into account many stakeholders, it must be understandable to users, to make the developers to make a plan and graphs of the system, allow you to determine key interfaces, functions and technologies, and also allow you to evaluate the schedule and the project execution budget. At the same time, the architects of modern information systems requires responsibility for creating a satisfactory and implementing system concept at the earliest stage of its development, support for the integrity of this concept throughout the development and determination of the resulting the resulting system for use by the client. On the other hand, the development of the architecture of the information system is the process of describing the architectures of information systems in sufficient detail to make them more useful for the development of information systems.

The study of foreign experience shows that in developed countries, when developing an architecture of an information system requires compliance with the following conditions:

¾ focus on the mission of the organization;

¾ focus on the requirements;

¾ focus on development;

¾ the ability to adapt;

¾ The need for flexibility.

Compliance with all these conditions allows you to develop the architecture of the information system of the organization more perfect and effective.

The main software architectures currently implemented are:

¾ file-server;

¾ client-server;

¾ Multi-level.

File server. . This architecture of centralized databases with network access involves the assignment of one of the network computers as a dedicated server on which the central database files will be stored. In accordance with user requests, files from the server file are transmitted to user workstations, where the main part of the data processing is carried out. The central server mainly performs the role of file repository, without participating in the processing of the data themselves. After completing the users, users copy files with processed data back to the server, from where they can take and process other users. Such a data organization has a number of disadvantages, for example, while simultaneously handling a set of users to one and the same data, the performance of the work has sharply, as it is necessary to wait until the user working with the data will complete the work. Otherwise, it is possible to strengthen the corrections made by one users, changes made by other users.

Client-server. . This concept is based on the idea that in addition to storing database files, the central server must perform the main part of the data processing. Users refer to the central server using the Special Language of Structured Queries (SQL, Structured Query Language), which describes a list of tasks performed by the server. User requests are accepted by the server and generate data processing processes. In response, the user receives an already processed data set. Not the entire data set is transmitted between the client and the server, as is the file-server technology, but only the data that the client is needed. User request in the length of just a few lines is capable of generating a data processing process affecting multiple tables and millions of lines. In response, the client can only get a few numbers. The client-server technology allows you to avoid transmission over a network of huge amounts of information by shifting all data processing on the central server. In addition, the approach in question allows you to avoid conflicts of changes in the same data by many users who are characteristic of the file-server technology. Technology Client-server implements a consistent data change in multiple clients, providing automatic compliance with the integrity of the data. These and some other benefits made the client-server technology very popular. The disadvantages of this technology include high requirements for the performance of the central server. The more customers refer to the server, and the more the amount of data being processed, the more powerful there should be a central server.

Based on these reasoning in the design of the architecture of the AWP as a basis, the technology client-server was adopted. The placement charts reflect the physical relationships between the software and hardware components of the system).

2.2 Designing the information system interface

Under the user interface, only the appearance of the program is often understood. However, in fact, the user perceives through it the entire system as a whole, which means that his understanding is too narrow. In fact, the user interface includes all the aspects of the design that affect the user interaction and system. This is not just a screen that the user sees. The user interface consists of a variety of components, such as:

a set of user tasks that it solves using the system;

system management elements;

navigation between system blocks;

Visual design of program screens.

We highlight some of the most significant advantages of a good user interface in terms of business:

Reducing the number of user errors;

reducing the cost of system support;

reduction of losses of productivity of workers in the implementation of the system and faster recovery of lost productivity;

improving the moral condition of the staff;

reducing the cost of changing the user interface on the request of users;

Accessibility of the system functionality for the maximum number of users.

AWP Wholesale base is developed as an application using client-server technology.

2.2.1 User Interface Management Program

The main module "ARTS Wholesale base" is the Luck.exe module, which ensures the implementation of the main functionality of the use options diagram shown in Figure 1.9 of section 1.4.

When developing an information system of one of the main tasks, it is the creation of the most simple and unloaded interface. It is the program product interface that helps "communicate" with the information system, speaking as a user communication dialog and system.

Program Interface, Administrator:

1. The start form of the program. This form launches when the software is started forming, thus, the start of the user dialog with the system (Figure 2.3);

2. Administrator shape. In this form, the information system is fully controlled, i.e. Adding, deleting, changing data in the database, as well as if necessary, view and print reports (Figure 2.4);

3. The form "Customers", thanks to this form you can see complete information about the customers of the enterprise (Figure 2.7);

4. Form "Suppliers", thanks to this form you can see complete information about the customers of the enterprise (Figure 2.8).

Program interface Custom part:

In the window the arrival of the goods is the design of the goods. When this tab is selected, the user must first

In the Consumption menu, there are operations of the work warehouse on vacation and sale of goods.

In the residue menu, the product counts, the name of the stored in the warehouse.

In the Cashier menu, information on parish orders and expendable cash orders are stored. (Screenshots)

2.2.2 User Interfaces Control Components

Figure 2.0 Main menu of the program

The main window of the program is shown in Fig. 1.9. As can be seen from the figure, in addition to the main menu, already described above, it will also contain a control panel ("arrival" buttons, "Consumption", "Access", "Remains", "Cashier", "Revaluation", "Analytics", " References "," Service "and" Exit from the Program ").

Figure 2.1 Window of the coming menu or admission to the warehouse.

Figure 2.2 Flow menu window

Figure 2.2 Menu window Adjusting access rights to the program.

Figure 2.3 Window Menu Residue of goods.

Figure 2.4 Cash Menu window.

Figure 2.4 Window Menu Revaluation.

2.3 Database Design

Erwin 4.0 from Computer Associates Int was used to design the database.

Erwin is a powerful and easy-to-use database design tool that has gained widespread recognition and popularity. It provides the highest productivity of labor when developing and maintaining applications using databases. Throughout the process, from logical modeling requirements for information and business rules that determine the database, before optimizing the physical model in accordance with the specified characteristics - ERWIN allows you to visually display the structure and basic elements of the database.

ERWIN is not only the best tool for designing databases, but also means for quickly creating them. ERWIN optimizes the model in accordance with the physical characteristics of the target database. Unlike other tools, ERWIN automatically maintains the coherence of logical and physical schemes and transforms logical structures, such as relations by many-to-many, in their implementation at the physical level. Facilitates design databases. To do this, it is enough to create a graphic E-R model (object-attitude) that meets all data requirements and enter business rules to create a logical model that displays all elements, attributes, attitudes and groupings. ERWIN has two levels of model presentation - logical and physical. The logical level is an abstract view of the data, it is presented on it, as they look in the real world, and may be called as they are called in the real world, for example, "Permanent Client", "Department" or "Familier of the employee". The objects of the model represented on the logical level are called entities and attributes. The logical level of the data model is universal and in no way associated with the specific implementation of the DBMS. There are three subcoisers of the logical level of the data model, differ in the depth of presentation of data information:

Diagram Entity - Communication (ENTITY Relationships Diagram (ERD));

Key based data model (KEY BASED MODEL (KB));

Full attributed model (FA).

Diagram Essence - Communication includes entities and relationships reflecting basic business areas of the subject area. This diagram is not too detailed, it includes the main entities and relationships between them, which satisfy the basic requirements. Diagram Essence - Communication may include "many to many" communications and do not include key descriptions. As a rule, ERD is used for presentations and discuss the data structure with the experts of the subject area. The key-based data model is a more detailed view of the data. It includes a description of all entities and primary keys and is intended to represent the data structure and keys that correspond to the subject area.

The logical model is the most detailed representation of the data structure: represents the data in the third normal form and includes all entities, attributes and communications (see Appendix B).

Physical data model On the contrary, it depends on a specific DBMS, actually being a display of the system directory. The physical level of the model contains information about all database objects. Since there are no standards for database objects (for example, there is no standard for data types), the physical level of the model depends on the specific implementation of the DBMS. Consequently, the same logical level of the model can correspond to several different physical levels of different models. If the model does not have a greater value on the logical level, which specifically the data type at the attribute (although abstract data types are supported), then it is important to describe all the information about specific physical objects - tables, columns, indexes, procedures, etc. . Separating the data model to logical and physical levels allows you to solve several important tasks.

The physical data model is presented in Appendix V.

2.4 Justification of the selection of the information system creation platform

Visual FoxPro is a visual environment for developing relational database management systems currently produced by Microsoft Corporation. The last version is 9.0. Uses FoxPro programming language. The version of the 7.0 system can operate in Windows 9X operating systems and nt kernel, version 8.0 and 9.0 - only in Windows XP, 2000, 2003.

FoxPro (Fox-Pro?) Is one of the XBase programming language dialects. It is used mainly to develop relational DBMS, although it is possible to apply for the development and other classes of programs. As already noted above, the VFP language is a strongly awarded and advanced XBASE language. In Visual Foxpro, the programming language, that is, the basic design of the language is the concept of class. The original XBase version is the purest structure, with the basic concept of procedures and functions. Thus, the modern programming language Visual FoxPro allows you to combine both the programming "in the old manner" describing the mass of procedures and in the style of the OOP, creating a complex hierarchy of classes.

I chose this language programming because it contains a number of the following advantages:

¾ A widely known format of database tables, which makes it easy to organize information sharing with other Microsoft Windows applications.

Modern organization of relational databases that allows you to store information about the tables of the base, their properties, indexes and links, set the conditions for compliance with reference integrity, create local and remote views (Views), communications with servers, stored procedures executable at the occurrence of more than 50 different types of events. (VFP 7.0-9.0).

High speed with large databases.

High casualties with databases: Multifunctional Data Session window allows you to see a list of open database tables, their links, filters, procedure for indexes, buffering modes, move to the modification modifications modes, to work with table information, etc.

High Application Development Speeds using Masters (Wizard), Designers, Builders (Builder), IntelliSense Tips Mode When writing text text, debugging and program testing systems.

The ability to develop applications using the client-server technology with data posted on Oracle and Microsoft SQL Server database servers and with other Microsoft Windows applications using ODBC and OLE

The VFP system is designed to use by professional programmers, therefore there is no point in Russification of its menu and language - for any programmer, the English syntax of the algorithmic language is more accustomed than Russian.

2.5 Designing modules

Let us dwell on the design of one of the program modules and consider the steps to create the project on its example.

As an example, I will consider the design of a module that implements the use option "makes an application for admission."

To begin with, we describe the streams of events that occur in this embodiment.

Prepala to use the application from the client.

5. The use option begins when the client sends an application.

6. The manager opens the form of arrival.

7. The manager puts the date of the application.

8. The manager puts the name of the goods.

9. The manager contributes the amount of commercial goods.

10. The manager contributes the amount of the application.

11. The manager closes the form.

12. The use option ends.

The payment for use is the design of the application in the system and the emergence of a new client in the magazine of the main form.

Consider the sequence diagram of this use. As you can see from this diagram, the manager, opening the form, causes several actions - automatically (from the point of view of the manager) the date of the application is filled. List of customers when making an application is filled from the base with primary information. After that, the manager contributes all the necessary data and clicks the "Accept" button. The following actions are performed. All data is transmitted to the stored procedure.

3 Implementation and certification of the information system

3.1 Application implementation

The implementation of the application is inherently one of the time-consuming stages for the developer of the information system, because the requirements that the customer puts forward should be clearly and correctly integrated into the system. So far there are no such software products that could "adapt" under the requirements of the so-called customer and give a certain set of functions for the implementation of the system that will meet these requirements. Therefore, each developer should choose for itself the optimal environment for the development of the system, but it should be noted that when implementing the application does not do without writing a program code. It is when writing a program code that will be implemented by some functions that the system must perform. Depending on the selected system implementation environment, the program code will look different, in such a medium as Microsoft Visual FoxPro will be one program code, in Visual Basic another, etc.

In this case, the application was implemented in Microsoft Visual FoxPro.

The main functions of the system will be described below:

1. Start form of the system. This form is a push-button form and, accordingly, each button performs its function. Administrator registration button is shown in Figure 3.1. The button will execute the function that opens the admin panel if the user has such rights to this system

2. The coming menu button. The pump allows you to record the incoming goods to the store store Figure 3.2.

3. In the Menu button, the consumption is made of the released goods from the warehouse Figure 3.3.

4. The access menu button adjusts the rights of using this program Figure 3.4.

5. The residual residual menu button stores information about stored materials in the store store Figure 3.5.

6. The Casso menu button stores information about the arrival cash registers and expenditure cash orders. 3.6.

7. In the menu button, the revaluation changes passes the price of the new price of goods Fig.3.7.

Figure 3.1 - Startout System

Figure 3.2 - Form of accounting for material receipts to the warehouse.

Figure 3.3- The form of accounting of the released goods.

Figure 3.4- form Adjusting access rights to the program.

Figure 3.5- Form of goods balances in stock.

Figure 3.5-form about profitable cash orders and expendable cash regulations.

Figure 3.6-form of operations by the goods.

Testing applications

Testing is the program execution process in order to detect errors. Testing provides:

Error detection;

Demonstration of conformity of the program functions of its purpose;

Demonstration of the implementation of requirements for the characteristics of the program;

Displays reliability as a program quality indicator.

Figure 3.2 presents information flows of the testing process.

At the entrance process of testing three streams:

Program text;

Source data for starting the program;

Expected results.

Tests are performed, all the results obtained are estimated. This means that the actual test results are compared with the expected results. When the mismatch is detected, an error is fixed - debugging begins.

After collecting and evaluating test results, the quality and reliability of software begins. If there are serious errors that require design changes, the quality and reliability are suspicious, it is stated by the need to gain testing.

The results accumulated during testing may be estimated and a more formal way. This uses the software reliability models that perform reliability forecast for real data in the intensity of errors.

There are 2 program testing principles:

Functional testing (testing "black box");

Structural testing (testing of a "white box").

When testing using the "white box" method, the internal structure of the program is known. An object of testing here is not external, but the internal behavior of the program. The correctness of building all the program elements and the correctness of their interaction with each other is checked.

Testing a "black box" (functional testing) allows you to get combinations of input data providing full check of all functional requirements for the program //. The software product here is viewed as a "black box", whose behavior can only be determined by the study of its inputs and appropriate outputs.

The principle of "black box" is not alternative to the principle of the "white box". Rather, this is an complementary approach that detects another error class.

Testing a "black box" provides the search for the following categories of errors:

Incorrect or missing functions;

Interface errors;

Errors in external data structures or access to the external database;

Characteristics errors (required memory capacity, etc.);

Initialization and completion errors.

Unlike the testing of the "white box", which is performed at the early stage of the test process, the testing of the "black box" is used in the later stages of testing. When testing a "black box" neglected the control structure of the program. Here, attention is focused on the information field of the definition of the software system. When testing at this stage, the focus of the suitability of the solution to work under living conditions is given. The focus is paid to the correction of errors and the definition of their importance, as well as the preparation of the product to issue.

At the test stage, two main tasks are solved:

Testing solutions - testing plans created at the planning stage and extended and tested during the development phase;

Point operation - deploying a solution in a test environment and testing with the involvement of future users and the implementation of real system use scenarios. This task is performed before the start of the deployment stage.

The purpose of the testing stage is to reduce the risk that occurs when entering the solution into industrial operation.

For the success of the testing stage, it is necessary that the relationship has occurred to the project and the developer has switched from the development of new features to ensure proper quality solutions.

At this stage of the information system, the following types of testing must be carried out:

Basic testing - low-level technical testing. It is conducted by the developer himself in the process of writing the program code. The white drawer method is used, the high risk of errors.

Testing for suitability to use - high-level testing, performed by a tester and future product users. The "black box" method applies.

Alpha and beta testing - in terms MSF Alfa-code - this is basically all the source texts created at the stage of developing the MSF process model, and the beta code is the code that has been tested during the testing phase. Therefore, at the stage of development of the MSF process model, the alpha code is tested, and at the test stage - beta code.

Compatibility Testing - From the Developed Solution, the ability to integrate and the ability to interact with existing systems and software solutions is required. This form of testing is focused on checking the integrability and the ability of the developed solution to interact with existing systems. In this case, the correctness of the application operation on the user equipment and the user used by the user will be checked.

Performance testing - oriented to check whether the application satisfies the performance requirements and level of speed of speed.

Testing documentation and reference system - all developed accompanying documents and reference systems are tested.

Pilot operation is testing solutions in an industrial environment. The main task of the pilot operation is to demonstrate that the solution is able to work stably work industrial exploitation and satisfies the requirements of the business. In the process of pilot operation, the solution is tested in real conditions. Point operation allows users to express their opinion about the product work. Guided by this opinion, the developer eliminates all possible problems or a plan of action is created in case of unforeseen circumstances. Ultimately, pilot operation allows you to decide whether to start a full-scale deployment or postpone before troubleshooting capable of disrupting deployment.

The pilot operating process plan for the information system being developed is given in Table 3.2.

Table 3.2 - Pilot Operation Plan

Act		Description
1. Selection of success criteria		The developer and participants in experienced testing determine the criteria of success and coordinate them
2. Selection of users and installation sites		A team of participants in experienced testing from users and developers is formed. The location of the pilot process is determined.
3. Preparation of users and installation sites		User training is conducted - test participants. The installation location is prepared.
4. Deploying the experienced version		An experienced version is installed and is included in the work.
5. Support and monitoring of the experienced version		Control of the work of users and the system, assistance in operation, collecting information about the operation of the system
6. Feedback with users and evaluation of results		Users express their opinion about the operation of the system, indicate the shortcomings and errors.
7. Amendments and additions	The detected errors are corrected, changes are made in design or process. Fixed results are provided to work and evaluate users.
8. Decisions on deployment	If the results of the work of experienced testing satisfy users is made a decision on the deployment of the system.

3.2 Application Deployment Method

At this stage, the developer (or team) deploys the technologies and components necessary for solving the solution, the project goes to the stage of accompaniment and support, and the customer finally approves it. After deployment, the command is evaluating the project and a user survey to find out the degree of their satisfaction.

Deployment stage objectives:

¾  transfer the solution to the industrial environment;

¾  Recognition by the Customer's fact of completion of the project.

The deployment of components characteristic of a particular installation site consists of several stages: preparation, installation, training and formal approval.

The results of the system deployment phase are escort and support systems, document repository, where all versions of documents and code developed during the project are placed.

To deploy the developed system, an action plan was drawn up, which is shown in Table 3.1.

Table 3.1 - application deployment plan

Act	Description of action
1. Backup	A backup of user data is made with its participation and coordination by transferring information to interchangeable media (CD, DVD)
2. Setting the basic components of the solution	Application of technologies that ensure the operation of the decision. In this case, installing the Visual FoxPro component
3. Installing a client application	Transfer to the user's computer and setting the final version of the developed and database
4. Training	User training is made to work with the system, the developer is convinced of the correctness and understanding of the work of IP by customers
5. Transfer of the Knowledge Base of the Project Client	The customer is transmitted all project documentation
6. Closing the project	A report on the closure of the project is drawn up. The customer signs the act of acceptance.

For the normal functioning, AWS requires Microsoft WindowsXP operating system.

4 Information Project Management

4.1 Selection of development life cycle

One of the basic concepts of the IP design methodology is the concept of the life cycle of its software (LCC software). The LCC is a continuous process that begins with the moment of making a decision on the need to create it and ends at the time of its complete seizure.

The main regulatory document regulating the LCH software is the international standard ISO / IEC 12207 (ISO - International Organization of Standardization - International Organization for Standardization, IEC - International Electro Technical Commission - International Commission for Electrical Engineering). It defines the ELC structure containing processes, actions and tasks that must be performed during the creation of software.

The ISO / IEC 12207 standard does not offer a specific LC model and software development methods. Under the ZHC model, you can understand the structure that defines the sequence of the implementation and interconnection of the processes, actions and tasks performed during the LCC. The LCD model depends on the specifics of the IC and the specifics of the conditions in which it is created and functions.

To date, there are many models of the software life cycle, but two models are most popular and distributed:

Spiral model (see Figure 4.1);

Iterative model.

Figure 4.1 - Spiral model LC

To create an information system, i.e. "Automated workplace of the warehouse employee Wholesale base", it was selected iterative. The distinctive feature of the iterative model can be called what it is a formal method, it consists of independent phases performed in series and is subject to frequent review (Figure 4.2). The iterative approach has proven itself in constructing IP, for which at the very beginning of development, it is possible to definitely and fully formulate all the requirements, in order to provide developers with freedom to realize them as much as possible from a technical point of view.

The advantages of the iterative model:

the model is well known to consumers who are not related to software development and end users.

Convenience and simplicity of use, because All work is performed in stages (by phases of the model);

Stability of requirements;

The model is available for understanding;

The structure of the model can be guided by even weakly prepared personnel (inexperienced user);

The model can orderly copes with difficulties and works well for those projects that are quite understandable;

The model contributes to the implementation of strict controlling project management;

Facilitates the work of the project manager for the preparation of the plan and configuration of the developer team.

Figure 4.2 - Iterative model ZHC

Phases model:

At the analysis stage, the functions that the system must perform are identifying the most priorities, which require elaboration primarily describe information needs;

At the design stage, the system processes are considered in more detail. Analyzed and, if necessary, a functional model is adjusted. System prototypes are built;

At the implementation stage there is a system development;

At the implementation stage, the finished product is introduced into the already current organization system. Users are trained;

At the accompaniment stage, the software product is maintained (any addition or change, for more functional product operation).

The choice of a model of software development life cycle is an important step. Therefore, for the project, the choice of the software development model can be carried out during the use of the following processes.

Analysis of distinctive categories of the project placed in tables.

Answer questions listed for each category by emphasizing the words "yes" and "no".

Locate the category of category or questions related to each category relative to the project for which an acceptable model is selected.

Developer team . Based on the possibilities, the selection of personnel in the developer team passes before the moment the model of the software development life cycle will be chosen. Characteristics of such a team (see Appendix W Table W.1) Play an important role in the process of choosing a model of life cycle, which means that the team can provide significant assistance in choosing a model of a software product life cycle, since it is responsible for the successful implementation of the developed model of life cycle .

Team team . At the initial stages of the project, you can get a complete picture of the team of users (see Appendix and Table and.1), which will work with the developed software, and its future relationship with the developer team throughout the project. Such a presentation helps when choosing a suitable model, since some models require the enhanced user participation in the process of developing and studying the project, since the requirements may slightly change the user during the development process, the developer needs to know these changes and how these changes are in the software.

4.2 Definition of the purpose and area of \u200b\u200bthe program project

The program product is developed on the goods in stock, will allow you to automate the process of receipt, structuring and storing product data in stock, as well as simplify the process of issuing reports.

The objectives of the program project will be - creating and deploying a product accounting system. This system is designed for internal use by the "Cleonelly" personnel, in most part employees of the enterprise warehouse.

To determine the scope of the software product, it will be described below, which should not be a software project.

The program project should be:

For internal use in the organization;

Project for the implementation of multiplayer access;

A project that has the ability to enlarge, change and storing information about the product of the enterprise;

A project that has the ability to enable, change and storing information about the system users;

A project that has the ability to enable, change and storing information about customers and suppliers of organizations that are subjects of concluded transactions;

A project that will implement the formation of external reporting.

4.3 Creating the Structure of the Operational List of Works

To create a unique product or service (project result), it is necessary to carry out some sequence of work. The project planning task is to accurately accurate the execution time and the cost of these works. More precisely, the assessment is given, the higher the quality of the project plan. To give an accurate assessment, you need to present the composition of the work of the project, that is, to know which it is necessary to fulfill what kind of work. Only after a list of design work is drawn up, the duration of each of them is estimated, and the resources necessary for their execution are allocated. And only then you can estimate the cost and timing of the execution of each task and, as a result of the addition, the total cost and period of the project. That is why the definition of the composition of work is the first step when planning the project. The definition of design work begins with the definition of the stages (or phases) of the project. For example, in the project, the creation of a system "Accounting in stock" phases can be highlighted:

Development of software requirements;

Design information system;

Implementation and certification of the information system;

System implementation.

After the composition of the phases and their results are defined, it is necessary to determine the sequence of these phases relative to each other and the deadline for their execution. Then you need to determine which files will consist of a phase, in which sequence these works are performed and at what time it is necessary to meet when they are executed.

The opening list of works (Figure 4.3) was designed using a software product such as MS Project 2003.

Figure 4.3 - Recommended List of Works

4.4 Evaluation of the duration and cost of development

Evaluation of duration. It is determined after the construction of the opening list of works (Figure 4.3, paragraph 4.3). This duration estimate can be seen using the Ganta chart (application K).

Charts are a graphic display of information contained in the project file. From the charts you can get a visual idea of \u200b\u200bthe sequence of tasks, their relative duration and the duration of the project as a whole.

The Gantt Chart is one of the most popular methods of graphic presentation of the project plan, used in many project management programs.

In MS Project, the Gantt diagram is the main means of visualizing the project plan. This diagram is a graph on which the time scale is placed horizontally, and the task is located vertically. In this case, the length of segments that indicate the tasks is proportional to the duration of tasks.

On the Ganta diagram next to the segments, additional information may be displayed (the names of the resources involved in them and their download are displayed during the task).

Estimation of costs

The project consists of tasks , That is, the activities aimed at achieving a certain result. So that the task can be performed on it resources .

An important property of resources is the cost (cost (costs)) of their use in the project. In MS Project there are two types of resource costs: a time-based rate and cost of use.

The time-based rate (rate) is expressed in the cost of using the resource per unit of time, for example 100 rubles per hour or 1000 rubles per day. In this case, the cost of resource participation in the project will be the time during which it works in the project multiplied by the hourly rate.

In this case, a time-based rate was used (Figure 4.4) The total costs of using resources can be in Figure 4.5.

Figure 4.4 - time-based rate in the use of the resource

In this picture, you can see that the developer of the system when performing a project receives 50 rubles per hour; The business analyst receives 45 rubles per hour, the tester is 38 rubles per hour. The overtime rate is not taken into account.

Figure 4.5 - General costs for using project resources

4.5 Distribution of project resources

Fragment of the distribution of resources for the system of "Accounting in stock" can be seen in Figure 4.6

Figure 4.6 - Fragment of the distribution of project resources

For each work performed in the project, a resource is compared to perform this work. The figure shows the total number of labor costs each of the resources and the specific number of hours spent on a specific day.

4.6 Evaluation of the economic efficiency of the project

Calculation of economic efficiency of the project is an important step. It is here that the economic efficiency of the project will be calculated. This calculation will show how much the project is beneficial or the project is completely loss. When calculating the economic efficiency of the project, it will be necessary to calculate the payback period for the project. The payback period will show the period for which the project will pay off.

Input data.

Additional profits from project implementation (DP) \u003d 38000 rubles. Additional profit was predicted by enterprise experts.

Starting investments (IC) \u003d 39396.47 rubles. Starting investments comply with the total costs of using project resources (Figure 4.5 of paragraph 4.6)

Discount rate (I) \u003d 12%.

The deadline for which the project is calculated (n) \u003d 2 years.

Additional profits from project implementation (DP) \u003d 38000 rubles.

The annual costs of project implementation (Z 1) \u003d 15,000 rubles.

Annual project implementation costs (Z 2) \u003d 10,000 rubles.

Annual cash receipts (R 1) \u003d 23000 rubles.

Annual cash receipts (R 2) \u003d 28000 rubles.

When evaluating investment projects, a method for calculating a net listed income is used, which involves discounting cash flows: all income and costs are given to one time.

The central indicator in the method under consideration is the NPV (Net Present Value) - the current value of cash flows. This is a generalized final result of investment activities in absolute measurement.

An important point is the choice of discount rate, which should reflect the expected average loan percentage level in the financial market.

Pure reduced income (NPV) is calculated by formula 4.2

(4.2)

R k - annual cash receipts during N years.

k - the number of years as much as the project is calculated.

IC - starting investment.

i - discount rate.

According to the calculations of this formula NPV \u003d. 3460,67 rubles.

The NPV indicator is an absolute increase, since it evaluates how much the income overlaps the costs. Since NPV\u003e 0, the project should be taken.

Investment return ratio (ROI) is calculated by Formula 4.3

(4.3)

ON CALCULATIONS (ROI) \u003d 108.78%

Table 4.1  auxiliary table calculation of the draft payback period

= 1,84

Payback period N OK \u003d 1.84 years (1 year and 11 months)

Since ROI \u003d\u003e 100% (namely \u003d 108.78%), the project is considered profitable.

(4.4)

Thus, the profitability index is equal to (PI) \u003d 1.2

Automated jobs

Requirements for functional characteristics

List of generated reports

4.4.2. Requirements for the planning and management system

The information system should ensure the planning of enterprise resources and the management of bypass production.

Requirements for IP functionality:

1. Management of finished product configuration (GP):

Maintaining regulatory information on the composition of GP with the possibility of specifying the period of the relevance of the specification and with the possibility of finding in the production of GP with several different specifications;

Maintaining regulatory information on the technology of manufacturing products included in the GP with the possibility of specifying the technology relevance period and with the possibility of finding in the production of GP with several different technologies;

2. Sales Management:

Viewing the history of customer relationships;

Registration / Adjustment of the Application of the Client with an indication of the list of GP, volumes, shipping date, sales price and any additional conditions;

View current economic indicators (calculation) ordered by GP;

3. Production planning:

Formation of equipment availability schedule indicating the number of available norm-hours for each day of the planned period;

The formation of a production plan with an indication of the manufactured product, its number, used equipment, divisions for each day of the planned period;

Formation of a plan for the need for production in materials and components;

Monitoring and managing loading equipment for the generated production plan;

Make adjustments to the production plan during its implementation;

A factory analysis of the production plan;

4. Production management:

Formation of replaceable tasks (outfits) for the manufacture of products;

Purpose / reassignment of outfits of performers and fixation of the execution of outfits indicating the number of products issued, the number of defective products and the causes of marriage;

Management of storage and movement of commodity values \u200b\u200b(TMC) in production;

5. Supply management:

Formation on the basis of a plan of need for materials and components of the purchase requests with an indication of the supplier, the nomenclature of the TMC, the number and deadlines of the supply;

The formation of applications for the purchase on the basis of one-time orders for TMC from divisions;

Monitoring and tracking the implementation of purchase applications;

Operational control of residues;

Plan-Fact Analysis of Supplies;

6. Cost management:

The formation of a planned (regulatory) cost of GP;

Fixation of the actual costs of production;

Calculation of the actual cost of GP;

Plan-fact cost analysis.

Requirements for the calculation of the regulatory cost of the order

The regulatory cost of the product and the entire order is calculated according to the following procedure:

1. The direct material component of the regulatory cost of the product is formed on the basis of information on the regulatory framework of this product (specifications) and established accounting prices for the TMC included in this specification. For the specification, the use of several articles of material costs is allowed.

2. The value of direct wages is calculated on the basis of the regulatory performance of the product. Set: the regulatory duration of each operation, the profession of the worker required for this operation, as well as the discharge of the worker. Also, the system is introduced with cash rates of normo hours by the professions of workers and their discharges.

3. The regulatory value of indirect costs is calculated as the percentage of the specified base (the values \u200b\u200bof direct costs according to this article).

To implement this calculation, you must have the following data in the information system:

1. The specification of the manufacture of the product (as well as the specifications of the manufacture of all partners of the semi-finished products included in this product);

2. Product manufacturing technology and semi-finished products included in it: what operations must be completed and for what time. In addition, each operation is given by the profession and the discharge of the workers necessary for its execution (for the release of this particular product);

3. The protocol of accounting prices for the TMC used;

4. Cash rates of normo hours for professions and discharges.

Requirements for the calculation of the actual order cost

The actual cost of the product and the entire order is calculated according to the following procedure:

1. The direct material costs for the production of products are calculated based on the actual data on the expenditure of the workshop of materials on production conversion. At the same time, the value of all semi-finished products included in this product is calculated. The sum estimate is carried out according to the methodology adopted in the company's accounting policy.

2. The salary of direct production workers is calculated on the basis of data on the closure of workshops. In the event that the accounting of outfits in the IP is not conducted, the salary refers to direct costs to be distributed, i.e. It is distributed to the released products according to some database.

3. The depreciation of direct production equipment is included in the composition of direct spending if the equipment (machine) used on this frontier is specified for each converter.

4. Direct costs to be distributed:

The main materials consumed less frequently than each conversion (for example, chemicals whose norm per unit of production is so small that it makes sense to take into account their seal even for this norm);

Wages of workers in the absence of information on its campeagly distribution;

Depreciation of direct equipment in the case of only its total monthly amount without breaking over the redistribution.

Such expenses are distributed on manufactured products according to the selected distribution base (for example, in proportion to direct material costs).

1. Protective costs (25 account BU): are distributed to manufactured products proportional to the selected distribution base. The share of such expenses may remain or not in the composition of the incomplete production according to the accounting policy adopted at the enterprise.

2. The general costs and sales costs (26 and 44 accounts bu) are recognized by the costs of the current period and relate to expenditures on the implementation. The distribution of such expenses for the cost of finished products can be seen using a special report.

Information System Performance Requirements

<Раздел должен содержать требования к производительности Информационной системы. Вводится в шаблон>.

Requirements for reliability

<Раздел должен содержать требования к надежности Информационной системы. Например:>

Requirements to ensure reliable (sustainable) functioning of the information system

Reliable (sustainable) functioning of the information system should be ensured by the customer of the set of organizational and technical measures, the list of which is shown below:

1. Organization of uninterrupted power supply;

2. Using licensed software;

3. Regular fulfillment of the recommendations of the Ministry of Labor and Social Development of the Russian Federation, set out in the decision of July 23, 1998. "On approval of intersectoral model standards of time on working on service maintenance of PEVM and office equipment and supporting software";

4. Regular fulfillment of the requirements of GOST 51188-98. "Protection of information. Testing software for computer viruses ";

5. Regular reservation of the database of the information system by means of the information system itself or the means of the database management system used.

1. Relevance and need for research

With the appearance of recently in the Russian Federation of the new real estate management in the form of the owner of housing (HOA), the Association of Housing owners (Hoa - Homeowners Assotiations) and Condominiums (later - Real Estate Management Organizations) The tenants (owners) of housing appeared the opportunity to influence tenants (owners) The quality of the maintenance of real estate, on the improvement of the adjacent territory and to some extent on the cost of utilities.

In accordance with Article 161 of the Housing Code of the Russian Federation, the management of an apartment building should ensure favorable and safe living conditions of citizens, the proper maintenance of common property in an apartment building, solving issues of use of the specified property, as well as the provision of utilities to citizens living in such a house.

b) educational process

Development of scientific and educational courses, as well as scientific and popular materials

	Course name/ material	Quick description/ material
Scientific and educational courses	Tutorial "Information Systems Management of Apartment Houses"	The functionality of the real estate management information systems used in the Russian Federation and abroad are given. Functional features are compared with recommendations for the choice of an information system. Designed to train students in the areas of 080100.62 "Economics" and 080500.62 "Business-Informatics"
Laboratory workshop "Business Rules Management System of the MKD Management Organization"	Step-by-step instructions for generating business rules management module using IBM ILOG. The algorithm for managing business rules of the HOA is given. Designed to train students in the direction of 080500.62 "Business Informatics"
Laboratory workshop "Multi-agent modeling of real estate management organization activities"	Step-by-step instructions for the formation of agents and the formation of a real estate management organization model using AnyLogic. Designed to train students in the direction of 080500.62 "Business Informatics"
Tutorial "Development of a constituent database of an apartment building using MS Access 2010 DBMS"	There are step-by-step instructions for the formation of database tables, establishing links between them, building forms, requests, reports and macros using MS Access 2010 DBMS capabilities.
Laboratory workshop "Analysis of the business processes of the Organization for Real Estate Management"	Diagrams designed using an object-oriented UML modeling language are given. Designed to train students in the areas of 080100.62 "Economics" and 080500.62 "Business-Informatics"
Scientific Popular Materials	Monograph "Factory and cluster analysis of the organizations of the Region in the field of real estate management"	Recommendations on factor and cluster analysis of parameters characterizing the HOA selected region are given. Information on real estate management organizations with the same sets of business processes and determining the main factors affecting their activities
Monograph "Information exchange algorithms in real estate management organization"	The general algorithm of the work of the IP, the algorithms of the operation of software modules implementing information services for subscribers, the algorithms for the interaction of software modules are given. User interfaces of the information system. Features of the development of software code modules using the MS Visual 2010 development environment
Article "Classification of subscribers and information systems in MKD management organizations"	The patterns of information exchange within the Organization of Real Estate Management, the estimated composition and volume of data during information exchange, alleged data transformation during information exchange, the form of submission of input and output data
Article "Development of a multi-age imitation model for modeling activities of HOA"	Approaches to the formation of agents for the subject area, as well as the development of a simulation model. The results of modeling activities of the HOA with different sets of source data are given.
Article "Forming a set of business rules for HOA"	Approaches to the formation of a business rules set. The possibilities of implementing the business rules management system using IBM Ilog are considered. An example of using business rules for making a decision is given.
Article "Formation of algorithms for the information system of the Organization for Real Estate Management"	The structure of the algorithm of the information system, the structure of algorithms of software modules, implementing information services and information exchange with the organization's database is considered.
	Article "Application of a holistic approach to form a complex key performance indicators of the activities of HOA"	The application of the provisions of a holistic approach to the formation of a complex of indicators, allowing the creation of an assessment system to achieve strategic and tactical (operating) objectives for the organization of real estate management, assessing the state of the organization and control of the business activity of the subscribers of the information system in real time is considered.
Article "Information services for managing apartment buildings"	Information services provided by foreign information systems owners (tenants) of real estate in apartment buildings are considered.
Article "Forming a database for the information system HOA"	Data models, data storage and processing technology, data composition, data formats for reflecting in user interfaces and output documents, data types, intended composition of tables, as well as circuit connections between tables
Article "Organizational analysis and model of business processes of HOA"	The development of a complex of models is considered: a strategic model of the goal-setting, organizational and functional model, a functional-technological model, a process-role model of a quantitative model, a data structure model (in what form the regulations of the HOA and the objects of the outside environment are described), business processes

Based on the assignment of the information system being developed, we will design further the modular structure of the application. To determine the modular structure, we use the diagram of the notation components UML 2.0 (Fig. 3.4).

Fig. 3.4.

The information system consists of three components:

• 1. Interface. Implementation of user interaction with the information system. Contains the following modules:
  • · Introduction / output - organization of entering and withdrawing information when working with IP;
  • · Reporting is the organization of reporting in accordance with the established forms of documentation on various areas of the personnel agency;
  • · Search - organization of searching for candidates and vacancies for the specified parameters;
• 2. Data processing. Implementation of information processing functions: search for data in the database, mathematical model for the task of primary analysis of documents, etc.;
• 3. DB. Implementing a data warehouse containing customer information.

Development of the database structure

As mentioned earlier, in the information system all information is stored in a single database. To simulate the logical structure of the database, IDEF1X methodology was applied. According to this methodology, the process of building an information model consists of the following steps:

• · Definition of entities; determination between entities between entities;
• · Setting primary and alternative keys;
• · Determination of attributes of entities;
• · Determining the model to the required level of normal form;
• · Transition to the physical description of the model: Purpose of the correspondences The name of the entity is the name of the table, the attribute of the entity - the attribute of the table;
• · Setting triggers, procedures and restrictions;
• · Database generation.

Diagram Essence-bond describing the database in the terms IDEF1.X is built of three main blocks - entities, attributes and connections. If we consider the chart as a graphical representation of the provisions of the subject area, the entities and attributes are nouns, and the links are verbs.

Since future ICs on this database will search, the following are selected as the main attributes for the document:

• - document's name;
• - Date of receipt of the document to the archive (law firms that carry out archival services are followed by the storage periods of the documentation. Each document has its own shelf life. Many securities are losing their relevance over time, and their value is reduced to zero. Such documents should be destroyed. The timely selection of such papers and the destruction of documents is included in the package of archival services provided by law firms. When making a storage to each document, after conducting a special examination, the shelf life is determined. After this period, the document is filed for destruction);
• - accessory (type) of the document (since all documents were divided into 7 species for which ranking is important);
• - a column;
• - regiment number;
• - Salazki number (these 3 parameters are needed to determine the location of the document in the archive);
• - Presence of a document in its cell (you need to know the document in the archive, or it is issued to the friend).

The result of a request to select all documents belonging to one client should look like this. Figure 3.5. In the example submitted, the number of documents was intended limited to 20.

Now consider in more detail the logical data model of the developed information system shown in Figure 3.6.

Fig. 3.5

Fig. 3.6.

From the data model presented it is clear that it contains three entities each with its set of attributes, and two of them are dependent, and one is not.

The Employee Essence, which is an independent entity has attributes:

• · Employee identification number - is the primary key of this entity;
• · FULL NAME;
• · The area of \u200b\u200bspecialization;
• · Rating;
• · Additional Information.

The essence of the "client" is a dependent essence from the entity of the "employee", which indicates that each employee can serve a lot of customers. The essence of the client has attributes:

• · Series and passport number - is the primary key of this entity;
• · Employee identification number - is the secondary key of this entity;
• · FULL NAME;
• · The area of \u200b\u200bspecialization;
• · Rating;
• · Additional Information.

The entity "Document" is the dependent essence from the entity "client", which indicates that each client can store many different documents in the archive. Essence Document has attributes:

• · The document identifier is the primary key of this entity;
• · Series and passport number - is the secondary key of this entity;
• · Document's name;
• · Receipt date;
• · Belonging to the group;
• · Column number;
• · Shelves number;
• · Salace number;
• · Presence of a document in the cell.

Created from a variety of modules information system allowed the Nizhny Novgorod Automobile Plant "Chaika-Service" to realize the idea of \u200b\u200bproduction, the most fully taking into account the wishes of customers who have placed their orders in the enterprise

The information system created from a variety of modules allowed the Nizhny Novgorod Automobile Plant "Chaika-Service" to realize the idea of \u200b\u200bproduction, the most fully taking into account the wishes of customers who put their orders in the enterprise

The main task of the company's IT service, leading business in the current difficult time, is to reduce IT costs and provide instruments to leadership that will help successfully overcome the test of the crisis. So, Alexey Ghanin, head of the IT department of the Nizhny Novgorod Automobile Plant "Chaika-Service", specializing in the production of serial and unique autophectechnics.

The company burly in 2006, when the ownership of the old plant was acquired and the development of the second territory began. Naturally, the task of combining both territories into a single information field. We started with the creation of a VPN network, but when the number of users has increased, the bandwidth of the channel has not been missed. Then the fiber optic cable was laid between the two territories.

With the onset of the crisis, the need for network resources decreased, this made it possible to reduce the procurement of active equipment for the telecommunications infrastructure of the enterprise. Another significant source of cost reduction was the refusal of outsourcing and the implementation of IT tasks on its own forces.

In addition, the company optimizes the Internet costs, analyzes and limits traffic flow. The company has branches in Krasnodar and Moscow, all sites are combined into an IP network with a single numbering. And now it is this internal network for calls inside the enterprise, which is significantly more economical than calls by long-distance telephone communication.

From the tools that will soon be granted to the leadership, Ganin called primarily a system for calculating the cost. It has already been developed and will serve as a general global goal - reduction in costs. The refined calculation of the cost of products is planned on the basis of the engineering data management system. This will provide detailed and operational information on the cost (previously they were calculated on the basis of accounting data). The company produces sufficiently complex products, only finite versions of vehicles with different modifications are about one and a half thousand. Naturally, the details from which they are going, two orders of magnitude more.

From accounting - to production

The first step on the path of automation was the acquisition in 2002 of the product "1C: Accounting 6.0" and the CAPR system "Compass" Askon. The next step was the automation of production activities. The company "Rarus NN" on request of the enterprise began adaptation of the ERP system "1C: Management of the manufacturing enterprise 8" ("1C: UPP 8") to the needs and peculiarities of the enterprise. The purpose of the project was to build a single database and the implementation of the management of all business processes on the basis of a unified information system. The decisive success factor in its implementation was the immediate support of the supreme leadership of the enterprise - the Director General, which initiated and supported the project at all its stages.

When automation of production activities, special attention was paid to the adequacy of the display in the system of the production process. Specialists of the implementation team developed a technical task with a detailed description, which car in which configuration the client should get and what is needed to do for each order. The document was entered into the type of car, its model, a list of required technological operations, their sequence, a list of control operations, etc. This approach made it possible to make a company more customer-oriented, since the technical tasks were formed by the managers of the Commercial Department, which were trying to maximize the wishes of the client, and then the tasks came into production.

IT department specialists together with technologists have developed a block of specifications of industrial and technological maps. On their basis and on the basis of a monthly plan for the production of finished products, the need for materials was determined for a certain period, taking into account current residues. All this allowed to competently plan the work of the supply department.

IT department employees have developed a module for "1C: UPP 8" to import "wood" products from the Compass system, which is used by the enterprise designers. The work algorithm turned out the following: The design bureau of the "Compass" develops the drawing and creates a 3D model of the object, then the structure of the product using the developed module is imported into the ERP system, after which the product specification is based on imported data. If designers make changes to any node, then these changes are automatically displayed in all systems.

At first, as Ganin admitted, he and his specialists wanted to make a system of engineering data management on their own, but soon they found out that the Appius Group of Companies, a partner "1C", develops its own replicable PDM solution (it received the name "1C: PDM management engineering data ").

Feedback

The next task was to obtain operational feedback from production, it is important because the production cycle of the product can occupy one or two weeks. Previously, the order status was visible simply by phone, now the relevant information is obtained by means of the information system.

The first step in this direction was the development of a system for monitoring the status of a technical assignment. Some production processes have been changed, in particular SC officers obliged to pass reports on the work accepted by the operator, and he entered the data about them in the ERP system. As a result, the system began to show the passage of production order in stages with the indication of responsible persons, this allowed managers to provide customers with the true information on what stage their orders are and when they are ready.

The next step was the introduction of a production planning module. Previously, planning was carried out by means of Excel, unpleasant, errors often occurred. After the ERP-module of production planning has earned, managers have at their disposal actual data formed on the basis of the technical assignments received. This made it possible to quickly monitor the loading of each site. As a result, the accuracy and efficiency of production planning increased.

Soon there was a need for more operational information on the state of production processes, in particular about downtime. To solve this problem, I implemented a system that allows you to track the course of production processes based on bar coding: each technological operation, each technical task and each employee assigned their barcode, installed terminals equipped with a barcode scanner.

The production process is now being built as follows. Before starting work, the brigadier or worker is approaching the terminal, reads its barcode, barcode of the technical task and technological operation. From the point of view of the system, this means that the employee has begun work. After its completion, the employee repeats its actions with barcode.

"This is a universal solution, besides, it does not require work of computer literacy, - Ganin notes. "The car is the main and most expensive component of our production, the reduction of downtime made it possible to sharply speed up the execution of orders." The company has a convenient and simple loss analysis tool: the system works are automatically generated in the system for each vehicle, allowing to track when work began on this car, when it ended up how much time the car simply stood waiting for another operation. If the permissible time is exceeded, the causes of the causes and the search for the perpetrators of such a long downtime. As a result, the personal responsibility of the performers has improved.

Based on "1C: UPP 8" enterprise specialists implemented a block planning unit for the design office. The technical tasks created in the system are coming to the chief designer, they analyzes them, distributes them to their designers through their designers and determines the time for each task. Such an organization of work gives the chief designer and managers, which form the base of orders, the ability to track the degree of workload of the design bureau, and this, in turn, allows you to compare the production of production and designers and rationally allocate existing human and production resources.

Data on the work performed, obtained by barcodes, enter the calculation unit of the executors' salary. The system records the time of work, facilitating the calculation of the output and overtime clock. All this contributes to the rapid and accurate payroll.

It is important to emphasize that the company went along the expansion path

The basic configuration of the ERP system with additional blocks without changing its internal structure. It became possible, in particular, to conduct its updates without any problems.

To manage the archive of design documentation in the enterprise introduced the system "1C: PDM engineering data" (development of Appius GK) and integrated it with "1C: UPP 8". In addition to the creation of new products, the engineering data management system is planned to be used to more accurately calculate the cost of products.

Multiple integration

The enterprise introduced GPS navigation to track supply of supply and commercial vehicles that move over long distances. This allows you to optimize routes, reduce fuel costs, more clearly withstand the discipline of supplies.

"Chaika-Service" plans to associate on the video conferencing system in a single network all branches - two in Nizhny Novgorod and one in Moscow, Krasnodar and Naberezhnye Chelny. Thus, the efficiency of decision making top management will improve and financial and temporary business costs will significantly reduce.

"We also plan to introduce a decision based on" 1C: UKP 8 "to interact with the traffic police, preparation and printing of TCP, transit numbers, - Ganin notes. - All data will be grouped in a single storage place of information - a car card, where all its identification numbers, color, body number, etc. will be entered, then this data will be used in the technical task, when printing PTS, numbers, certificates, accounts " Such integration will give customers an enterprise the opportunity to get ready-made TCP and transit numbers along with the car, thanks to which it will be possible to raise cars into account in the traffic police.