Open Library is an open library of educational information. The life cycle of the automated information system Cascading model AIS

Canonical design AIS.


Development and design AIS Starts with the creation of a conceptual model use of the system. First of all, the feasibility of creating a system, its specific functions and tasks to be automatized. There must be an estimate of not only goals, but also the possibilities of creating a system. The following analysis of the requirements for AIS, detailed design, interconnection of stages, programming and testing, minimizing losses during the transition from one level of information presentation to another, integration into an existing system, implementation and support is carried out.

There are three class design methodologies AIS:
· Conceptual modeling of the subject area;
· Detection of requirements and specification information system through her pointing;
· System architecture softwareSupported tools CASE-TECHNOLOGIES (CASE - Computer Aided Software Engineering - technology of creating and maintaining various systems).

Stage of creating an automated system -part of the creation of the AC, installed regulatory documents and the ending release of the NASA documentation, which should contain a system model at the level of this stage, the manufacture of non-relocated components or an acceptance acceptance acceptance.
Each stage is allocated for reasons of rational planning and organization of work and must end with a certain result. The content of the documentation at each stage is determined by the composition and specifics of the work.
In GOST 34.601-90, eight stages of creating automated systems are defined:

  1. Formation of the requirements for speakers.
  2. Development of the AC concept.
  3. Technical task.
  4. Preliminary design.
  5. Technical project.
  6. Working documentation.
  7. Entering.
  8. Accompanying speakers.
Three periods of creation period can be distinguished: pre-project, design, commissioning.
Stages 1, 2, 3 refer to the first period, stage 4, 5, 6 - to the second period, stage 7, 8 to the third.
The pre-targeted period is developed by a feasibility study (TEO) and the technical task (TK) on the design of the system. During this period, three stages of work are carried out at the stage of formation of requirements:
  • survey of the subject area object and the rationale for the need to create a system;
  • formation of user requirements for the system;
  • drawing up a report on the work performed and the application for the development of the system.
At the stage of development of the AU concept, four stages of work are carried out:
  • study of the object;
  • conducting research and development;
  • selection of the System Concept option from several developed;
  • drawing up a report on the work performed.
At the 3rd stage, we develop and approve the technical task for the creation of the AU.
Technical task (TK) -this list of the main operational, technological economic and other requirements that the designed object should satisfy at all stages of its existence. After the statement of the TK, the second period of creating the AC is the period of designing the system begins.
Design -the process of a reasonable choice of system characteristics, the formation of logical and mathematical and economic and mathematical models, documentation development.
At the stage of creating a draft design at the 1st stage, preliminary design solutions on the system and its parts are developed, on the 2nd - documentation of NAS and its parts.
At the 5th stage, when creating a technical project, four stages are developed:
  • design solutions on the system and its parts;
  • documentation NAS and its parts;
  • documentation for the supply of products for recruiting AC and TK on their development;
  • tasks N # Designing in related parts of the automation object project.
The third period - commissioning of the AU.Provide the development of non-standard equipment, a complete set of equipment, materials, purchased products, installation, commissioning, implementation.
At the 7th stage, the system is commissioned in eight stages:
  • preparation of an automation facility to enter speakers;
  • training personnel;
  • complete set by software, technical, information funds and products;
  • construction and installation work;
  • commissioning works;
  • preliminary tests;
  • experienced operation;
  • acceptance tests.
Content of stages of creating ac at various stages
In order to improve the management of the design of the design, each stage is detailed, i.e., is divided into steps.
Stage of creating an automated system -part of the creation stage, determined by the nature of the work, its result or specialization of the performers.
Modern methodologies System designs should provide a description of automation objects, a description of the AIS functionality, the project specification, which guarantees the achievement of the specified system characteristics, a detailed plan for creating a system with an assessment of the development time, description of the implementation of a specific system.

Life cycle AIS.
At the heart of creating and use AIS Lies the concept of life cycle (ZHC).
The life cycle is a model of creating and using AIS, which reflects the various states of the system from the moment there is funds in this complex until it is completely out of use.

For AIS, the following main stages of their life cycle are suspended:
1. Analysis - determination of what system should do;
2. Designing - determining how the system will function: first of all the specification subsystems, functional components and methods of their interaction in the system;
3. Development - the creation of functional components and individual subsystems, the compound of subsystems into a single whole;
4. Testing - checking the functional and parametric conformity of the system by indicators defined during the analysis stage;
5. Implementation - installation and commissioning of the system;
6. Support - provision of a regular process of operation of the system at the customer's enterprise.

Stages of development, testing and implementing AIS are indicated by a single term - implementation.
At each stage of the life cycle, a certain set of technical solutions and reflecting their documents is generated, while for each stage, the initial documents and decisions adopted at the previous stage are generated.
The existing models of the life cycle define the procedure for executing the steps in the process of creating a system, as well as the criteria for the transition from stage to step. The following models received the greatest distribution.

Cascading model Presses the transition to the next step after the complete completion of the previous steps. This model is used in constructing AIS, for which at the very beginning of development can be quite accurate and fully formulated all the requirements. This gives developers freedom to realize them as much as possible from a technical point of view. In this category, complex settlement systems are falling, real-time systems and others. However, this approach has a number of shortcomings caused primarily by the fact that the real system of creating a system is never fully fit into a rigid circuit. For example, in the process of creating software, a need to return to previous steps and clarification or revision of previously accepted decisions.

Spiral model based on start steps life cycle: analysis, preliminary and detailed design.
Each round of the spiral corresponds to the phased model for creating a fragment or version of the system, the goals and characteristics of the project are specified on it, its quality is determined, the work of the next spiral turn is planned. The main problem is to determine the time of transition to the next step. To solve it, it is necessary to introduce temporary restrictions on each of the ELC steps. The transition is carried out in accordance with the plan, which is compiled on the basis of statistical data obtained in previous projects, and personal experience of developers. The disadvantage of this approach are unsolved issues and errors made at the stages of analysis and design. They can lead in subsequent stages to problems and even the failure of the entire project. For this reason, the analysis and design must be carried out particularly thorough

The phase of physical modeling should provide at the experimental level to test the real efficiency of the created AIS models and their adequacy. To implement this stage, a physical (home) model AIS is being developed. Physical model AIS. - This is a combination of structure, methods and means of the reduction in the formation of AIS, intended for verification in real conditions for the efficiency of the future system and the adequacy of its models.

In a certain respect, the physical model AIS has the properties of the real system. EUM, peripheral devices, documents, files, databases, data processing programs, and other components needed to create AIS are attracted to build it. Physical model AIS reduced, i.e. This is its reduced mapping. The decrease here is not mechanical, not arbitrary, but harmonized. It presents only those properties that developers attributed to the category of basic, essential.

3. Design AIS

Based on the principles, provisions, models, methods and means of building AIS, obtained at the study stage, system design is carried out.

The design stage consists of the following steps:

1) subject survey (pro) of existing (traditional) IP;

2) Development technical task to create a system;

3) development of a technical project to create a system;

4) Development of a working project on the creation of the system.

Provided that the existing IP is an automated possibility of two ways to design: the modernization of the AIS or its complete replacement of the newly created AIS. With relatively small volumes design work Steps 2 and 3 can be combined.

Stage pro It is carried out to study and analyze the features of the object - the existing traditional IP. Materials are collected for design - definition of requirements, learning object design. The conditions for the functioning of the future AIS is conducted, certain restrictions on the development conditions are established - the deadlines for the implementation of the design stages, available and missing resources, procedures and measures to protect information and other, taking into account the previously performed research, the development and selection of the AIS concept is carried out.

Stage of development TZ. - Logical continuation of the stage of pro. The materials obtained at the Pro Stage are used to develop TK. An analysis and development of fundamental requirements imposed on AIS on the part of a specific customer or a potential group of consumers are being analyzed. Requirements for hardware, software, information and organizational and legal components of AIS, etc. are formulated.

On the stage of Technical Design Search for the most acceptable solutions for all AIS design tasks. The purpose of this design is the specification of common, sometimes fuzzy knowledge of the requirements for the future system. At this stage are determined:

The goal, tasks, AIS functions, also consider the external conditions for the functioning of the system, the distribution of functions between its components;

system parameters AIS - interfaces and distribution of functions between the operator and the system;

The configuration of all subsystems AIS, forming its structure - documentation and information, technical, software and mathematical and legal components of the system structure;

structure and control system of the database, linguistic means, composition of information and search languages, classifiers and codifiers, procedures for indexing documents and requests;

The statement of the configuration of the complex of technical means AIS and their specification;

Composition and characteristics of mathematical models, algorithms and AIS programs;

The scheme of the functioning of AIS, the processing of data processing, etc.;

Official and working instructions for AIS staff;

Refined technical and economic justification of the project.

The bulk of the working capacity of working design is the work on the development of algorithms and relevant programs.

On the stage of work design The final finishing of those issues, which at the technical design stage for applied reasons could not be fully resolved. At this stage, a set of programs based on algorithms drawn up at the technical design phase. The database structure is specified, the unified formats of documents processed in AIS technologies are adjusted.

At this stage, programs are tested, a series of test tests with the processing of real documents, analyzes the results of testing and experimental processing, the necessary adjustments of programs.

Methods and means of design AIS. The design of AIS can be performed:

By third-party developer. This firm has a staff of highly qualified professionals. Work is carried out on the basis of an agreement between the developer and the customer company;

Forces of full-time customer specialists.

It is possible a compromise solution: the customer can invite a consultant to develop AIS on a contract basis.

A specific choice is determined by many factors, in particular the financial condition of the Customer's company, the presence of regular specialists of the appropriate profile and level, the terms of the establishment of AIS, the presence of the relevant developer company in this or nearby region, the company's secrecy regime, etc.

Approve the appropriate methods and means to solve design tasks. Among them should find such methods that radically solved the tasks of developing AIS. One of these methods is a structural analysis. This is a method of studying the system, which considers the system as a hierarchical structure from its general level to the required lower.

At the pre-project survey, methods of studying the actual state of the existing (traditional) IP are used:

oral or written survey;

written survey;

observation, measurement and evaluation;

discussion of intermediate results;

analysis of tasks;

Analysis of production, managerial and information

processes.

Methods for the formation of a given state are associated with the theoretical substantiation of all components of the AIS, taking into account the goals, requirements and conditions of the Customer. These include:

modeling data processing processes;

structural design;

decomposition;

Analysis of information technology.

For a visual representation of objects and processes of AIS, the methods of graphic display of actual and specified states are used - block diagrams, graphs, drawings, drawings, sketches, diagrams, etc.

4. Automation of the design of AIS.

Automated systems Design - an effective means of improving the design of AIS. In the area of \u200b\u200bdesign, a special direction was formed - software engineering or CASE technology (Computer-Aided Software / System Engineering - Software Computer Development System). Case technologies are a set of methods for analyzing, designing, developing and conducting AIS, supported by a complex of interrelated automation tools. Case-technologies are a means for system analysts, developers and programmers, providing automation of the design processes of AIS of various classes and values.

The main goal of the CASE technology is to automate the process of developing and separate the design of the design of the AIS software encoding.

Structural methods for building models of enterprises. It is structural to call this method of studying the system or process, which begins with a general review of the object of the study, and then implies its consistent detail. Structural methods have three main features:

The dismemberment of the complex system on the part, represented as "black boxes", each "black box" implements a specific function of the control system;

Hierarchical streamlining of the selected elements of the system with the definition of relationships between them;

Use the graphical representation of the relationship of the system elements.

The model, built using structural methods, is a hierarchical set of diagrams, graphically representing the function performed by the system and the relationship between them.

As part of structural analysis methodologies, the most common can be attributed as follows:

SADT - Structural analysis technology and design, and subset - IDEFO standard.

DFD - data stream diagrams.

ERD - Diagrams "Essence - Communication".

STD - status transition charts.

IN iDEFO methodology Four basic concepts are used: function block, interface arc, decomposition, glossary.

The IDEFO model always begins with the representation of the process of a single functional block with interface arcs, which beyond the limits of the area under consideration. Sometimes such diagrams are supplied with contextual help.

The goal allocates the areas of activity of the enterprise to be considered primarily. The goal establishes the direction and level of decomposition of the model being developed.

IN dFD methodology The process under study is divided into subprocesses and is represented as a network related data streams. Externally, DFD is similar to SADT, but differs in the set of elements used. These include processes, data streams and storage.

Methodology ERD. It is used to build DB models, provides a standardized method for describing data and identifying links between them. The main elements of the methodology - the concept of "essence", "attitude" and "Communication". Entity set the basic types of information, and the relationship indicate how these data types interact with each other. Communications unite entities and relationships.

STD methodology Most convenient to simulate certain parties to functioning a system caused by time and response to events, for example, to implement the user's request to AIPS within a real-scale time. The deferences of STD are the concepts of "state", "initial state", "transition", "condition" and "action". Through concepts, a description of the functioning of the system in time is carried out and depending on the events. The STD model is a graphic image - a system transition diagram from one state to another.

Object-oriented methods for building control system models. These methods differ from the structural level of abstraction. They are based on the system representation in the form of a set of objects interacting with each other by exchanging data. Specific objects or abstracted entities can be used as objects of the subject area - the order, client, etc. Most significant method of Bucha. This is an object design technique with object analysis elements, having four stages:

1) Development of hardware diagrams displaying processes, devices, networks and their connections;

2) the definition of a class structure describing communication between classes and objects;

3) development of charts of objects that show the relationship of an object with other objects;

4) Developing an architecture of software describing the physical project of the system being created.

The overwhelming part of the existing methods of object-oriented analysis and design includes both modeling language and means of describing modeling processes.

The object-oriented approach is not opposed to the structural, and can serve its addition.

5. Building and implementing AIS

After the complete completion of the design of the design, the stage of building AIS begins. Building AIS. - This is a combination of organizational and technical measures to implement the AIS project. Among such events, the measures of financial, information, technical, software, right, organizational nature:

Determination of sources of financing and the allocation of funds for the purchase of the necessary equipment provided for by the project - "Statement of the Specification of Equipment AIS";

The choice of suppliers and conclusion of contracts for the supply of equipment;

Selection of premises for the AIS dislocation and its preparation for the installation of equipment;

Accommodation, assembly, installation, setting up equipment AIS in accordance with the project;

Selection, organization and training categories of the staff of AIS to fulfill the relevant work on ensuring the functioning of AIS;

Perform work on checking the quality of equipment (control, testing). When detecting defects - registration and presentation of advertising to suppliers;

Installation of software and work on testing the AIS software package. Subject to the detection of defects - the adoption of measures to eliminate them;

Filling the database, the solution of control examples throughout the complex of AIS tasks in accordance with the project. If deficiencies are found - take action to their elimination. If the disadvantages are not detected - preparation of documents for the passage of AIS into trial operation.

The composition of the measures and their sequence reflect the main control points in the construction of AIS. The construction of each specific system will have its own specifics both by the nature of the tasks and in their sequence. The design features are determined by the nature of the AIS, the organizational level of AIS, the functioning mode, the amount of financing, etc.

One of the important conditions for the effectiveness of AIS is to carry out a complex of work on its implementation. The introduction of AIS begins with the fact that the head of the Customer's company issues an order to implement the system with the indication of the main stages, the timing of their implementation, responsible performers, resource provision, the form of submission of the implementation results responsible for controlling the execution of order and others. Order may comprise an implementation plan with An indication of work at the following steps:

1) documentary registration of the results of commissioning of equipment, as well as control tests of the system tasks;

2) training AIS technology and learning the relevant sections project documentation;

3) conducting experienced operation of the system, analysis and adjustment of project errors and registration of documentation on the results of trial operation;

4) Submission of AIS into production operation with the design of relevant documentation.

Thus, the first stage is the development of the AIS control test program as a whole. At the second stage, the developer and the customer organizes training personnel involved in the operation of AIS. At the third stage, an experienced operation of the system is carried out. Depending on the content and volume of tasks AIS, an experimental operation lasts from three to six months.

The introduction of AIS is a fairly difficult task in both organizational and technical aspects. The customer must prepare the implementation of the system. This condition requires certain organizational, professional and psychological efforts by the staff of the Customer's company, to one way or another participating in the operation of AIS. The administration of the company must provide such conditions under which the team of the company will have a positive effect on the implementation of the system and help its implementation, development and development. Then it will be possible to assume that the purpose of the implementation and operation of AIS in the enterprise will be achieved.

6. Methods for calculating the technical and economic efficiency of automated information processing

One of the principal sections of the AIS project is a feasibility study of AIS in general and the processes of automated processing of economic information in particular. This requires the implementation of appropriate calculations of technical and economic efficiency.

The economic efficiency of automated data processing is provided at the expense of the following main factors:

High speed of operations on collecting, transferring, processing and issuing information, performance of technical means;.

Maximum reduction in time to perform individual operations;

Improve the quality of data processing and received information.

The overall efficiency of automated problem solving is directly dependent on reducing data processing costs and is direct economic efficiency. The achievement of the effect of system-wide solutions to improve the quality of user information services provides indirect economic efficiency.

Indicators of direct economic efficiency are determined by comparing data processing costs with several design solutions. Essentially, this comparison of two options is basic and designed. For the basic option, an existing system of automated or traditional (manual) data processing is taken, and for the designed version - the result of the upgrade system or the newly developed AIS.

The absolute indicator of the economic efficiency of the AIS project developed is a decrease in the annual cost and labor costs on the technological process of data processing compared to the basic version of the Ctern.

Saving financial costs through automation of data processing is determined based on the calculation of the difference in the cost of basic and projected data processing options by the formula:

With e \u003d s b - with n (1)

where with e is the value of reduced data processing costs;

With b - costs for the basic version;

With P - costs in the designed version.

The relative indicator of the economic efficiency of the AIS project is the effectiveness coefficient (K e) costs and the cost changes in the cost (I s).

To e \u003d with e / s b * 100% (2)

Cost efficiency ratio shows which part of the cost will be saved in the design version of the AIS, or how many percent costs will be reduced.

The value of the cost change index can be determined by the formula:

I z \u003d with e / s b. (3)

This index indicates how many times the cost of data processing during the implementation of the AIS project will be reduced.

When implementing the AIS project, it is necessary to take into account additional capital costs, whose value (K 3) can be determined by the formula:

K 3 \u003d k n - k b (4)

where k n and k b is the capital costs of the projected and basic data processing systems, respectively.

The effectiveness of capital costs is determined by the payback period (T) of additional capital expenditures on the modernization of IP:

T \u003d K 3 / C e (5)

E \u003d C e / k 3 \u003d 1 / T. (6)

Along with the calculation of cost costs, it is useful to obtain indicators of reduced labor costs for data processing. The absolute indicator of the reduction of labor costs (T) is the difference between the annual labor costs of the basic and projected data processing options:

t \u003d T b. - T P (7)

where t b. and T P is the annual labor intensity of operation of the base and projected data processing options, respectively.

The value of the relative indicator of the reduction in labor costs can be displayed by the labor cost reduction ratio (K):

K t \u003d t / t b. (eight)

The labor cost changes index (I t) characterizes the growth of labor productivity by mastering a more labor-saving version of the data processing project, it can be determined by the formula:

I t \u003d t b / t n. (9)

The absolute rate of reduction of labor costs (P) is used to determine the potential release. labor resources (performers) from data processing system:

P \u003d (T / T f) * F (10)

where t f - the annual travel fund of one performer engaged in data processing technology;

f - the coefficient that reflects the possibility of a complete release of employees, due to the time fund of which the value T is calculated.

The definition of direct savings from the implementation of the projected (upgraded) data processing system is carried out on the basis of comparison of indicators displaying labor and cost costs for operations of both the traditional and projected data processing system.

Saving labor costs (e TK) with the automated processing of information on the project can be determined by the formula

E TZ \u003d T O6CH - T OV (11)

where T o6st is the laboriousness of data processing in the traditional way under the basic version;

T SOV is the complexity of automated data processing during the design version.

Cost of financial costs from the implementation of a design variant of data processing in comparison with the manual basis option can be defined in a similar way.

The collection of source data for substitution to the above formulas and the execution of calculations to determine economic efficiency is carried out by registering and measurements of the corresponding parameters in the stages of the processing data processing. In addition, the initial data for a long period can be obtained by analyzing the registration (technological) journals of the AIS dispatcher and other registration forms.

Models LCC AIS -The structure that defines the sequential implementation of processes, actions, tasks performed during the LCC and the relationship between these processes.

Cascading model.The transition to the next step means full completion of the work at the previous stage. The requirements defined in the formation stage of the requirements are strictly documented in the form of a technical task and recorded for the development of the project. Each stage is completed by the release of a full documentation set, sufficient to ensure that the development can be continued by another developer team.

Stages of the project in accordance with the cascadal model:

1. Formation of requirements;

2. Design;

3. Development;

4. Testing;

5. Implementation;

6. Operation and maintenance.

Benefits:

- Full and consistent documentation at each stage;

- determined procedure for the sequence of work;

- It becomes clearly planning the timing and costs.

Disadvantages:

-A significant delay in obtaining ready-made results;

- errors on any of the stages are detected at subsequent stages, which leads to the need to return and renew the project documentation;

-Suppost project management.

Spiral model. Each iteration corresponds to the creation of a fragment or version of software, it specifies the objectives and characteristics of the project, the quality of the results obtained is estimated and the work of the next iteration is planned.

Each iteration is the completed development cycles in the form of the 1st version of AIS.

Stages of iterations:

1. Forming requirements

3. Projecting

4. Development

5. Integration

Each iteration is estimated:

The risk of exceeding the timing and cost of the project;

The need to fulfill another iteration;

The degree of completeness and accuracy of understanding the requirements for the system;

The feasibility of termination of the project.

Benefits:

- Operates the process of making changes to the project;

- Advises greater flexibility in project management;

-Thability to obtain a reliable and sustainable system, because Errors and inconsistencies are detected at each iteration;

"Customer's performance to work in the process of checking each iteration.

Disadvantages:

- planning-keeping;

- driven mode for developers;

- Working work is carried out on the basis of existing experience and not enough metrics for measuring the quality of each version.

Requirements for the technology of design, developing and maintaining AIS

Design technology - determines the combination of the three components:



-poshago procedure determining the sequence of technological design operations;

-Evil used to assess the results of technological operations;

-Replacing project development for examination and approval.

Technological instructions that make up the main content of technology should consist of a description of the sequence of technological operations, conditions, depending on which one or another operation is performed, and the descriptions of the operations themselves.

The technology of design, development and maintenance of IP should meet the following general requirements:

The technology must maintain a complete LCD;

The technology should ensure the guaranteed achievement of IP development objectives with specified quality and at the set time;

The technology should provide the possibility of conducting work on the design of individual subsystems in small groups (3-7 people). This is due to the principles of manageability of the team and improving productivity by minimizing the number of external relations;

The technology should provide for the possibility of managing the configuration of the project, conducting versions of the project and its components, the ability to automatically issue project documentation and synchronization of its versions with project versions;

The application of any technology for designing, developing and maintaining IP in a particular organization and a specific project is impossible without the development of a number of standards (rules, agreements), which must be respected by all project participants. To such standards The following are:

- Standard design;

-standard design documentation;

- Standard user interface.

Development requirement

- Execution of work on the creation of software;

Preparation for the implementation of AIS;



Control, testing of the main indicators of the project.

Requirements for accompaniment

Completion of the introduction of KIR must be accompanied by the publication of the system administrative regulations and job descriptions that determine the procedure for the functioning of the organization. Since the input of the information system, operation occurs on the basis of the "Regulations of the Information System" and a number of regulatory acts. Support of the system and its uninterrupted work is carried out by a division of the organization authorized by the relevant order. The refinement of the information system after commissioning is carried out according to individual projects and technical specifications.

In the process of escorting Ki, the task of maintaining its viability is set. The viability of kitty is largely defined as far as it corresponds to the real tasks and the needs of the university, which are varying during the life cycle of the kit.

Introduction

1. Architecture of automated information systems and problems of its improvement 13

1.1. Architecture and main components of AIS 13

1.2. Problems of development AIS 47

1.3. Platforms for the implementation of the new architecture AIS EP 53

1.4. Conclusions on chapter 1 57

2. Model architecture AIS pack 58

2.1. Basic requirements for AIS EP 59

2.2. AIS architecture 66

2.3. Components AIS PA 89

2.4. Conclusions on chapter 2 102

3. Methods of practical implementation AIS 104

3.1. Tools Development AIS EP 104

3.2. Experience of practical implementation of the AIS model 111

3.3. Conclusions on chapter 3 123

4. Conclusion 125.

5. Terminology and abbreviations 128

6. Literature

Introduction to work

The activities of modern enterprises are associated with the movement of interdependent and volumetric flows of material, financial, labor and information resources. The processes of production and commercial cycle in the conditions of a dynamically changing political and economic environment requires prompt decision-making in a short time. The solution to this task in modern conditions is impossible without the use of automated processing of technical and economic information.

Over the past 40 years, automated information technologies (IT) are actively used to solve accounting, planning and analysis tasks. economic activity enterprises various shapes property, sectoral accessories, organizational structure And the scale of activity. During this time accumulated big practical experience Creation of automated information management systems for enterprises (AIS EP), developed and received universal recognition of management methodology, the use of which is impossible outside the computer environment. It is fully responsible to argue that AIS EP has become an integral component of the business infrastructure. Theoretical and practical problems of automation of economic processes are deeply investigated in the works of Glushkova V.M., Volkova Si., Isakova V.I., Ostrovsky O.M., Podolsky V.I., Ratmirova Yu.A., Romanova A.N. , Nonshova E.N., Bradie R., Zakhman J., Cook M., Finkelstein K., Hammer M. and other authors. The approaches proposed by them became the base for the use of computing equipment at enterprises in solving the tasks of accounting, planning and analysis of financial and economic activities. but

the models offered by them did not take into account the realities of the economy of the information society and the current level of IT development.

The development of communications facilities contributes to increasingly close interaction of manufacturers with consumers, suppliers with buyers, strengthens competition in the market, expands the boundaries of local markets to national and transnational, accelerates the time of economic operations and financial transactions. Implementation of global computer networks in economic processes led to the emergence of new concepts: information society economy, e-business (e-business), e-commerce (e-commerce), electronic marketplace (E-Marketplace) and others. The trends in the globalization of the economy were reflected in the new business organization methodology, in which there is a problem of improving the flexibility of building business processes and the effectiveness of customer relations and suppliers.

The existing concepts of the AIS EF organization are based on a functional approach to the distribution of tasks between its subsystems. However, the AIS, built as a complex of subsystems oriented on individual management functions, does not mostly comply with the demands of the continuity of the end-to-end business processes of the enterprise. Therefore, in recent years, an approach becomes increasingly popular in which business processes are put at the head of the corner, and not individual functions of the management system executing them. This requires development new concept Architecture AIS pack. At the same time, it is obvious that the transition to the new AIS architecture cannot be implemented simultaneously, since over many years by enterprises and organizations implemented a large number of software tools implementing the solution of important management tasks, from which it is impossible to refuse immediately. Unfortunately, most of them are focused on offline functioning, which significantly complicates the integrated integration of information flows. Many existing software productsproviding support for the solution of new problems of managing the enterprise that emerged in the context of globalization of the economy are also developed without sufficient study of interfaces of interaction with software complexesimplementing the solution of related tasks. Under these conditions, the objective of the synthesis of integrated enterprises management systems is acquired by integrating the ready-made components of third-party manufacturers, custom solutions and their own developments.

In the publications of scientists and practitioners, the idea of \u200b\u200bimplementing the standard system integration standards supplied by various manufacturers has long been discussed. The progress of the systemic toolkit led to the emergence of object-oriented and component software development technologies (software), which allow building large-scale systems from finished blocks. Leading Suppliers of hardware and system software (Intel, Microsoft, Sun, Oracle, IBM, etc.), Communication Tools (Cisco, Nortel, Ericsson, Motorola), Applied Solutions (SAP, Peoplesoft, Siebel, etc.), authoritative states, International, commercial and non-commercial organizations and Association (ISO, IEEE, ASCII, APICs, Rosstandard, etc.) have now developed and actively implement in the practice of technology integration and software integration, allowing you to create open systems based on standards and data exchange protocols and interaction components in a heterogeneous environment in Real-time mode.

However, these proposals give only a system-wide platform, which requires significant refinements in relation to a specific subject area. In the context of the practical implementation of AIS, the design and development of information systems (IP) mechanisms using component multi-part architectures on the basis of standards and protocols of open systems are not developed.

In this regard, the problem of developing the theoretical platform and the development of practical recommendations aimed at building AIS, providing comprehensive automation of all information procedures to enterprises and organizations.

The need to develop a holistic approach to solving issues of system integration of AIS EP and through automation of microeconomic processes on the basis of modern IT determined the choice of theme and directions this study.

The purpose of the study is to develop an AIS architecture model that provides comprehensive automation and information support for cross-cutting business processes, and the rationale for the choice of tools for its system integration from the standpoint of modern information technologies.

Based on the target target, the following scientific and practical tasks were solved:

Conduct analysis and summarize existing approaches to designing, developing and implementing AIS UE;

Classify varieties of software used in the practice of management of enterprises;

Explore existing technologies and standards that ensure the integration of heterogeneous software;

Identify problems arising from the integration of the software used in the AIS UE;

Systematize the requirements imposed by enterprises to AIS EP to ensure information support for cross-cutting economic processes;

Develop a model of architecture AIS EP and allocate its main components;

Develop the principles of interaction and exchange of data components of the AIS EP;

The subject of the study is methods and tools for the development of economic information systems.

The object of research is the management of enterprises.

The study methodology is based on specific applications of the methodology of scientific knowledge in the applied directions of informatics and mathematics.

The objectives and objectives of the study were formulated in accordance with the main direction of work on the further development and improvement of mathematical methods and means of computing equipment used in economic subject areas.

Along with a general scientific approach based on system theory, the dissertation provides experience in the development, implementation and operation of software tools of domestic and foreign manufacturers, methods.

implementation of international open standards for building information systems. On this basis, a complex of methodological and practical recommendations that have been tested in Russian and foreign enterprises are offered.

The work used theoretical provisions of the works of domestic and foreign authors in the region:

Automated processing of economic information and modeling economic processes;

Planning methodologies I. operational management production and material reserves;

Reengineering and computer design of business processes;

Modern standards in information technology.

The study analyzed and developed by the developments made by scientific groups and individual scientists in the financial academy under the Government of the Russian Federation, the All-Russian Interior of the Finance and Economics Institute, Moscow State University of Economics, Statistics and Informatics, St. Petersburg University of Economics and Finance. Voznesensky, Research Financial Institute and other organizations.

The information base of the study amounted to software products of Russian and foreign manufacturers, publications in economic and computer publications, research of international research groups Gartner Group, Aberdeen, IDC, Metagroup, DataQuest, etc., Methodical materials of leading domestic and international consulting and audit companies, research results of the Association Software developers in the field of economics,

studies of the Software Market of Russia and CIS countries CIES "Business Program-Service".

The scientific novelty of the thesis is to develop a model of architecture AIS EP, focused on the integrated automation of cross-cutting business processes, and proposals for its implementation by systemic integration of heterogeneous software in a distributed heterogeneous network medium based on object and component technologies.

The scientific novelty contains the following results obtained in dissertation:

Definition and classification of requirements for functionality for organizational and economic management of enterprises;

Model of AIS architecture, focused on comprehensive automation of through business processes;

Principles of integration of software tool solutions to the tasks of enterprise functional services with basic management of business processes, data exchange and document flow;

Offers for the organization of a single information space of an enterprise, accessible to employees and partners of an enterprise through a corporate web portal;

Proposals for the implementation of a unified system of formation and classification of reporting with the use of analytical tools;

Principles of implementing the interaction of subsystems AIS based on object-oriented and component technologies and interaction of the software component in a distributed network

medium in accordance with industrial standards and Internet protocols;

The mechanism for implementing the adaptive properties of the architecture model for AIS UE in accordance with the requirements of a particular enterprise based on the capabilities of setting up the basic subsystems to existing and projected work processes.

The practical significance of the dissertation work is that the implementation of the proposals extended allows to create AIS EP, which ensures effective support for the information procedures for the management of the enterprise in the context of globalization of the economy and the formation of the information society.

The model of architecture AIS EP and the recommendations for its use have sufficient flexibility and versatility, which ensures their applicability in building management of enterprises of various forms of ownership, industry specifics and scope of activity.

An independent practical importance is:

Proposals for the selection and application of standards, protocols and other mechanisms used in the system integration of AIS UE;

Suggestions for the integrated automation of cross-cutting business processes and document management;

Proposals for the creation of a single information space of the enterprise using the web portal mechanism;

Proposals for the adaptation of a spiral-iterative approach when developing and implementing AIS.

The practical significance of the work is appreciated in specific projects of implementing the proposed problem-oriented model of the enterprise automation system:

Comprehensive enterprise management system "Flagman" of InfoSoft,

Customer Relationship Management Systems "Pivotal Software" Customer Relationships (Canada)

MONARCH ES Corporate Reporting Systems of DataWatch (USA),

Project of integration of information systems of companies "Sovintel" and "Body Ross".

The Educational Center for News-Metathechnology applies materials prepared by the author based on the approach proposed during this study, when conducting courses on the development of information management information systems (see http://www.vest.msk.ru).

The dissertation research materials are used in the research and practical activities of the executive bodies of the Association of Software Developers in the Economy (ARPEP) and members of it.

The main provisions of the work were reported and discussed on:

Conference "IBM solutions in the field of business integration for telecommunication companies", IBM representative office in Eastern Europe (Moscow, June 18, 2002);

Symposium "Call Center CRM Solutions 2002 / Call Centers and Customer Relationship Management" (Moscow, March 2002);

Conferences of information systems based on Centra Software Corp Corporation Toolkit. (Berlin, Germany, November 17-19, 1999);

Conference "Infozhod: Practice and Problems of Informatization of Cities" (Moscow, October 1999);

Scientific and practical conferences of the firm "InfoSoft" (Moscow, 1995-1999);

Conferences of specialists in the field of ACS and KIS "Corporate Systems" (Moscow, April 1998 and April 28-30, 1997, organizers: SoftService and representative offices Oracle, Informix, Sybase, Borland and Centura);

The 3rd annual conference "Corporate databases 98" (Moscow, March 31 - April 3, 1998 and 26-29, 1996, the organizers of the Information Technology Center with the participation of the Open Systems ID);

Conferences "Technician-97" (Moscow, November 24-26, 1997, organizers: Firm "SoftService", Russian Association of Users Oracle, Microsoft, Borland, Computer Associates, Lucent Software).

Problems of development AIS.

The introduction of information technology into the economy, the penetration of computer and communication funds into the management of the enterprise at all levels, the increase in interest in the interaction of companies via the Internet requires conceptual changes in the approaches to the construction of AIS EP. This applies not only to the pure technological problems of creating and operating IP, but also approaches to business management in the conditions of the economy of the information society.

AIS UE should provide need for automation and informatization on the basis of the organization, which puts before developers in the task: development of a platform capable of ensuring the work of a large number of users; support for communications and industrial data exchange standards and component interaction protocols; integration of existing developments into a single system.

Integration of heterogeneous applications within the Unified AIS should provide support: cross-cutting business processes; single user interface (portal); common information space.

In our opinion, the essence of the problems delivered is not so much in the technical aspects of the implementation, as in the need to use a fundamentally new model of the AIS EP architecture.

Summarizing the pros and cons of various variants of the IP architecture in terms of the possibilities of building an integrated solution.

Centralization of data processing places high requirements for servers. With an increase in the number of simultaneously running users (which inevitably, when automating processes on the scale of the entire enterprise), the load becomes excessive for the hardware platform and used by software. Applying various hardware solutions (clustering, multiprocessing and other forms of combining computing resources), as well as distributed processing using transaction monitors, application servers and powerful industrial DBMS, you can create really scalable solutions, unloading central nodes not only by increasing the power of hardware, But even at the expense of the corresponding construction of the system component of the system.

However, even if the central database server is able to provide the required performance, with such a construction of ISP, the problems of supporting the unified structure of the common database are inevitably arise if individual software components are developed by various companies or even developer teams within the same organization. Installing a common database with access from solving various applied tasks allows you to provide a general information space listed above technology allow you to access the database by a large number of users, but this does not guarantee proper work with divided data. The problem of the logical integrity of the data remains. When using programs of various manufacturers, the division of data on subsystems becomes inevitable, possibly by their denormalization and the creation of excess structures. A schematic architecture with a common base is presented in the following figure (Figure 1-14). As follows from the following scheme, the modules do not interact, that is, there is no calling of one module to others in real time, there is no operational support of the through process. Data is stored in the database from which they are available to other modules that need to contain the tracking functions in it, and the relevance of the data depends on the update frequency. An example of a pass-through process may be an account as an employee of the Sales Department. If it uses the CRM system for this, the formed account in parallel with the discharge must be processed in the logistics module of the ERP system to reduce goods, and immediately after that - a financial module to increase the buyer's debt. For this, the corresponding modules must check for the availability of a new account. If this is not done in a timely manner, an account may be discharged on the actual reserved goods.

In order for different modules to work with general structure DB, they should be initially designed by calculating a specific data structure or use the agreed metadata mechanism (repository).

When using other architecture, when heterogeneous databases are conducted on different computers (and, perhaps in different networks) and are used by autonomous modules (Figure 1-15), maintaining the logical integrity of the data is even more employed task. In this case, it is necessary to regulate and implement replication (synchronization) of data, the unification of reference books, coding and classification rules, develop or implement the replication mechanism itself. All this requires organizational measures to synchronize the database. There remains the problem of automatic continuation of the process (an example from a discharge account).

Platforms for the implementation of the new architecture AIS

By the beginning of the XXI century, the following decisions were developed and developed at the industrial level, ensuring the widespread introduction of IT into economic processes:

the personal computing tool consisting in many types of work disappeared the need for intermediaries between the formulation of the task and its performer, that is, employees of the enterprise functional services are able to comply with the information procedures that are in their competence using computers without attracting or with minimal support for accompanying technical personnel. ;

means of automated support for the agreed joint work of the Group ("teams") of workers over one project, document, task, etc.;

the mechanism of electronic communications that allowed in many cases to eliminate the need to transfer paper documents to minimize the need for meetings, which is especially important in the territorial remoteness of the participants in a particular business process.

Thanks to these decisions, the automation of most workers' processes occurring both inside the enterprise in its financial and economic, production and commercial activities and related functions. The combination of software and technical means that automate various functions and jobs allows you to link technological (on the basis of equipment and technical devices) and workflows (with the participation of employees of all units of enterprises) into through business processes. Thus, it is a fundamental ability to solve the problem of the conclusion of the items of data from the centers of their storage and processing, separation of jobs from each other.

Solving the problem of integrating the AIS modules and the choice of a centralized or decentralized approach in organizing their interaction is also possible due to the latest developments of leading system software manufacturers: operating systems, web servers, application servers, DBMS and middle-level platforms (Middleware Platforms). An application integration becomes possible by applying object-oriented development technology and component multi-part architecture. The key principle here is the concept of programming interfaces and the regulations of their changes and expansion (IDL language).

To work in a distributed heterogeneous environment, which is the Internet, Web Services (Web Services) specification are actively developed, each of which can implement one or more business procedures or functions (Business Procedures, Functions). Organization Oasis, Institute of BPMI and IBM, Microsoft and Wea published specifications for controlling workflows in BPEL4WS business processes, Xveng and WSFL web services languages \u200b\u200b(Web Services Flow Language), and WFML coalition - XPDL (XML Process Definition Language).

The trend is to combine subsystems from the open interfaces of web services that perform logically completed cycles of business processes. In this case, the components can be located on various application servers separated on the network and work with one or more database. By varying the number and interrelations of the component, the number and location of the network servers, the possibility of replacing the component or their displacement over the network without loss of compatibility, can be structured AIS, which maintains the balance of centralization and decentralization in the management of the enterprise.

There are no technical obstacles to the implementation of such architecture. Modern industrial application servers (for example, MTS / COM + /. NET, One or J2EE / EJB) allow you to build multi-part systems, provide a shared platform to access various web services, provide transactional integrity of operations, load balancing with competitive access tens of thousands of users Real-time, and also ensure fault tolerance and recovery after failures.

An important achievement of the IT industry is widespread and recognized by leading manufacturers according to standards: component interaction protocols (COM / DCOM, CORBA, Java RMI) and data exchange formats (EDI, XML,).

Standard EDI and its industry options (EDIFACT, XI2, HIPAA, etc.) are operated in the financial and industrial sector North America and Europe from the mid-70s and dominate today all over the world. With the increase in the popularity of XML on the Internet, the EDI was translated into XML.

On the basis of XML (DTD and XDR), data are developed, structured and formatted data in various economic spheres in the form of so-called subject dictionaries or types of documents, for example, WIDL, OFX, FPML, IFX, XBRL, CRML and numerous others in the West, as well as Commerceml.ru and XML Partnership / ARB in Russia. The American APICS Production Management Society, which is engaged in certification of ERP / MRP class systems, publishes the specification of economic entities in XML format, for example, the structure and format of the client data or the invoice. The self-documenting of XML provides an unambiguous understanding of data as a person and programs.

Architecture AIS PE

To build a model of the AIS architecture model, we will consider an enterprise as a set of labor, financial, material and information resources involved in business processes to achieve the business goals of the enterprise. Here, under the term business goals, strategic long-term tasks are understood by the owners and senior managers, as well as current tasks appointed by the heads of the upper and middle links. The business process or business process is the sequence of employees, operations in workplaces, as well as functions performed by and technical means in automatic mode. Each action or their sequence will be called the process step. Synonyms for action can also be operations, procedures. If the stage requires the actions of an employee (role-playing group, a representative or head of the unit, as well as a person who occupies a job position), then it is also called the task, and an employee is the performer. The sequence of actions in the business process may be ambiguous, that is, a process description in the form of a directed graph may include branching with the transition conditions from one stage to another. Typical chains of stages can be highlighted in subprocesses. The movement of the tasks to the specified stages of the process is called route. If the process cannot be described due to arbitrary transitions between the stages, the decision on which is made by the Contractor during the task at the current stage, then this case is called free routing.

The AIS UE should allow formally to describe business processes in graphical form in the form of a directional graph (orgraf), whose vertices are the steps, and the ribs are transitions between the steps. In a particular case, the business graph looks like a network schedule, where the vertices indicate work with the duration of their duration, and the oriented edges (arrows) show a sequence of work. In accordance with the description of the process, referred to as the process of the process, AIS UE should manage the resources (or, more precisely, to help manage the company managers), assign tasks and their performers, and also call (activate) software and hardware to run automated procedures.

The scale parameters of the enterprise affect the management of the Office at a particular enterprise, which is reflected in the requirements for AIS. On the other hand, the AIS PA affects the scale of the enterprise, for example, contributing to the growth of the business. The change in one of the parameters involves the AIS update in the same way as the introduction of AIS can change the management organization.

The purpose of the orientation to business processes in constructing AIS EP is to find a common platform, on the basis of which it will be possible to adequately modify the AIS, without requiring complete reorganization of the system. This platform is modeling business processes by software management software.

As a core AIS, it is necessary to develop a system that combines several functions discussed in the review of process management systems (paragraphs "1.1.7 of document management system" on page 31 and "1.1.8 of processes management systems" on page 34). Among them: Workflow is a subsystem of working and technological processes, providing predetermined and free routing of tasks between the performers; DOCFLOW - subsystem of document management and routing documents with tracking of their states; GroupWare - subsystem support for the functions of the operational assignment of tasks and free mashruitization (AD HOC) tasks between members of a group of performers; DataFlow - Routing data, data packages, messages between applications.

Unlike the adopted practices of the autonomous application of such a kind of systems, we consider the availability of a common process card, a common module for processing the stages of the process, the overall mechanism of destination of the performers and routing tasks and data.

Thus, the technological data generated by technical devices, the factographic data entered into the users in the workplace (including primary documents), as well as data generated by software applications, will be included in the AIS UE and are available to consumers of information in real-time time.

Schematically, the data processing life cycle in the AIS PE is presented in the following figure (Figure 2-2). Data entered manually or received from the software component is drawn up as a document, which is then processed by the document management module in accordance with the process map. The processing route (if the system setting requires this) the document management subsystem causes modules of functional subsystems to handle financial, economic and other types of operations. As a result, credentials are stored in structured databases. In turn, the documents themselves are stored in the repository or the database of unstructured data. All of these databases must be accessible to the analytical modules of the reporting subsystem to generate the necessary reports.

Experience of practical implementation of the AIS model

From 1995 to 1999, under the leadership of the author of the thesis, a system of comprehensive automation of the enterprise "Flagship" of InfoSoft enterprise was developed, which is currently implemented in more than one hundred large and secondary industrial, construction, commercial, agricultural enterprises and budgetary organizations of Russia and CIS countries. The system continues to develop on the basis of the kernel developed by the author, and by 2002 the flagship includes more than ten basic subsystems presented in the following figure (Figure 3-2):

The basis of the "flagship" system is the Basic Document Module, which is responsible for entering, processing, routing and printing all primary documents. Other basic modules are "administration" and "instrumental means" common to all functional modules. They allow you to customize role-playing groups and permissions, armor to menu items, document layouts and report templates.

The advantages of the implemented model were one-time input of primary documents, generation accounts In functional subsystems based on these documents, the unification of work with primary documents.

The rapid development of subsystems and insufficient standardization of their interaction led to the fact that integration was carried out around the central database and general tables. If you do not take into account the two-link architecture, the choice of which was due to the level of development of development tools in 1995, then the intersection dependence of the modules has become the main problem for the development of the system. The first of its implementation revealed the lack of functions of automation of document management by one only by the routing of documents and raised the need to implement the process control module (Workflow).

If we consider the implementation in more detail, the document management module is a library of objects included in all subsystems, as well as compiled as an autonomous module. The library includes means of setting up the species and document options, field composition, input and editing forms, a list of states, possible combinations of transitions from the state to a state, a list of operations with binding to functional modules, printing templates and blanks, as well as the rules for the formation of registries and documents logs .

Operations with documents change their condition, and also cause functions of applied subsystems. The list of functions is laid in each subsystem and specific for it. For accompanying programmers engaged in system settings, functions parameters and the possibility of binding to them fields of documents using formulas. This allows you to automate the majority of financial transactions, as well as logistics functions, recruitment and salary calculation, however, it remains the need for a script compilation language (Script).

The report generator shared for all subsystems is built into the system. Since the system is based on the principle of integration around the central database, the generator has access to all data regardless of the belonging to modules. Reports are classified into a hierarchical structure, each of the report layouts contains a template for previewing and printing, and SQL queries to form a resulting set of data. Generated reports can be processed further as documents.

It should also be noted that a unified appearance of subsystems is implemented in the flagship system. The general administration module of user interface elements, AWP functions, including menus and toolbar, allows you to configure the appearance uniformly.

At the moment, the development of IT requires the update of the "flagship" system platform. First of all, it is necessary to translate it into a three-star architecture and develop a document flow module to a full-featured process control system. It is also necessary to develop mechanisms for the integration of external applications, since the system has only import and export tools.

Nevertheless, numerous examples of the successful implementation and industrial operation of the flagship system, the increase in its sales in 2001-2002 indicate the economic efficiency of the decision to automate enterprises of various fields of activity, industries and scale.

In February 1999, the InfoSoft flagship system, created under the leadership of the author, was recognized as the best Russian development on the Centura TEAM Developer Toolkit CENTURA SOFTWARE CORP. (USA) and Interface Company (Russia). In 1999, 2000 and 2001 Kisa "Flagman" was certified as an enterprise information system by experts by the jury of the Business Software contest, conducted by the Software Developer Association in the Economy Software (ARPEP), CIES "Business Program-Service", the magazine "Accounting" and "Financial Newspaper" "

In almost any field, people use one or another type of modulated (mathematical, physical or computer) to have a clearer idea of \u200b\u200bwhat is happening in real processes.

There are 2 ways to describe models:

1) Static, considering the structure of the model, ᴛ.ᴇ. its aspects in which you can neglect time;

2) Dynamic, considering the flow of events, ᴛ.ᴇ. The change in the simulated phenomena in time, which cannot be neglected from the point of view of solved tasks.

Any firm and its activities can be viewed from the point of view of various people: the operator, the executive director, the customer, shareholder, partner, the seller, etc. Each category of people needs various models of the company.

Executive Director Must have a common picture: processes, products, finance, prospects, etc., ᴛ.ᴇ. Integrated picture as a whole. In order for the managing personnel to make the right decisions in any situations, it is extremely important to have a set of models describing the various parties to the company and their relationship. In the models used at the top level of control, most importantly - ϶ᴛᴏ brevity and clearer. Main points should be emphasized in them, and the details are hidden.

One of the most important models is currently a business model, with which the functions of the firm in the outside world are determined.

Figure 1 - model of hierarchically organized company

The existing models of the life cycle define the procedure for executing the steps in the process of creating a system, as well as the criteria for the transition from stage to step. The largest distribution was obtained by three following models.

Among the well-known models of the Life Cycle AIS can be distinguished cascade, iterative and spiral models.

Cascading model (up to 70 ᴦ.ᴦ.) involves the transition to the next step after the complete completion of the previous steps. This model is used in constructing AIS, for which at the very beginning of development can be quite accurate and fully formulated in all requirements. This gives developers freedom to realize them as much as possible from a technical point of view. In this category, complex settlement systems are falling, real-time systems and others.

Figure 2 - Cascading Model Scheme

Benefits Cascading model:

1) At each stage, a complete set of project documentation is formed, which meets the criteria of completeness and consistency;

2) The stages of work performed in the logical sequence allow you to plan the timing of their completion and the corresponding costs.

disadvantages Cascading model:

1) Destination with obtaining results;

2) Extremely important return to the previous stages.

For a cascade model of the AIS life cycle, the automation of individual unrelated tasks is characterized, which does not require information integration and compatibility, software, technical and organizational pairing. As part of the decision of the individual tasks, the cascade model of the life cycle in terms of development and reliability justified itself. The use of a cascade model of the AIS life cycle to large and complex projects due to the large duration of the design process and the variability of requirements during this time can lead to practical unrealizability.

Phased iterative model. This model of creating AIS assumes the presence of feedback cycles between the steps. The advantage of such a model is essentially that inter-stage adjustments provide greater flexibility and less complexity compared to the cascading model. At the same time, the lifetime of each of the steps can stretch for the entire period of creation of the system.

Figure 3 - Phased Scheme iterative model

Disadvantages: As a rule, due to a large number of iterations, mismatch arises in the design decisions and documentation. The confusion of the functional and systemic architecture of the created AIS, the difficulty in using project documentation is caused at the stages of introduction and operation immediately the importance of reflashing the system of the system. The life-long cycle of developing AIS ends with the step of the introduction, which begins the life cycle of the creation of a new AIS.

Spiral model (80-90 ᴦ.ᴦ.) - relies on the initial stages of the life cycle: analysis, preliminary and detailed design.

Each round of the spiral corresponds to a phased model of creating a fragment or version of the system, the goals and characteristics of the project are specified on it. It is determined by its quality, the work of the next spiral turn is planned. The main problem is the determination of the transition to the next stage. To solve it, it is extremely important to introduce temporary restrictions on each of the ELC steps. The transition is carried out in accordance with the plan, which is compiled on the basis of statistical data obtained in previous projects, and personal experience of developers. The disadvantage of this approach are unsolved issues and errors made at the stages of analysis and design. ʜᴎʜᴎ can lead at subsequent stages to problems and even to failure of the project. For this reason, analysis and design must be carried out particularly thorough

Figure 4 - Spiral Model Scheme

The basis of a spiral model of life cycle is the use of prototype technology or RAD technology ( Rapid Application Development -fast application development technologies). According to this technology, AIS is developed by expanding program prototypes, repeating the path from the details of the requirements for the detail of the program code. Naturally, with this technology, the number of iterations is reduced and fewer errors and inconsistencies occur, which is extremely important to correct in subsequent iterations. At the same time, the design of AIS is more quickly, the creation of project documentation is simplified. For more accurate compliance of the project documentation of the developed AIS, the system-wide repository and the use of SSE-technologies are becoming increasingly important.

The life cycle using RAD-technology involves the active participation of the end user and the future system on the development stages and includes 3 main stages of information reengineering:

1) analysis and planning information strategy : Users together with development specialists take part in identifying the problem area;

2) design : Users participate in technical design under the direction of developer specialists;

3) implementation : Specialists developers are trained by user and work in the New AIS environment.

The development and design of AIS begins with the creation of a conceptual model of using the system. Before this should be determined by the purpose of creating a system, its specific functions and task automation. An assessment must be made not only on, but also the possibilities of creating a system. The following analysis of the requirements for AIS, detailed design, interconnection of stages, programming and testing, minimizing losses during the transition from one level of information presentation to another, integration into an existing system, implementation and support is carried out.

There are three class AIS design methodologies:

Conceptual modeling of the subject area;

Identifying the requirements and the specification of the information system through its makety;

Systemic software architecture supported by CASE-technology tools (Case - Computer AIDED Software Engineering - technology of creating and maintaining various systems).

Modern systems design methodologies should provide a description of the automation objects, a description of the AIS functionality, the project specification. The guaranteeing achievement of the specified system characteristics, a detailed plan for creating a system with an assessment of the development time, description of the implementation of a specific system.

Specification - accurate, complete, clearly formulated descriptions for this task.

 

Perhaps it will be useful to read: