Waterfall model Analysis of the design Design Implementation Integration Testing Building the product specification Building the product architecture Development of the output code Integration of four parts of the output code Testing and identifying defects

Unified software development process (USDP) The variation model describes the ways in which the software will be victorious. The analytical model determines the base class for stosuvannya. The design model describes the links and visibility between classes and objects seen. The implementation model determines the internal organization of the program code. The testing model is composed of components, test procedures and other test options.

Tipovі components arhіtekturi software product that tipovі vimogi to PZ Organіzatsіya prog Osnovnі Klas sistemi Organіzatsіya danih BIZNES rules Іnterfeys koristuvacha Upravlіnnya resources Bezpeka Produktivnіst Masshtabovanіst VZAYEMODIYA of іnshimi systems (іntegratsіya) Іnternatsіonalіzatsіya, lokalіzatsіya Introduction-vivedennya danih Obrobka pomilok

Typical components of the architecture of the software product and types of software to software. Vіdmovostіykіst - sukupnіst polіstіvnostі system, scho pіdvishuє її nadіynіst vіdіynіst vіvlennі pardons, vіdnovlennya іt localіzії vile naslіdkіv for the system. During the development of a real system to ensure the stability to safety, it is necessary to transfer all kinds of situations that can cause the system to fail and develop the mechanisms for processing failures. Reliability - the building of the system withstands various weather and failures. Vіdmova - tse transition of the system to the last pardon in the state of non-practical camp. Zbіy - a pardon for a robotic system, so as not to bring the system out of harmony. The less vidmov that zboїv for the same song interval of an hour, the system is vvazhaetsya nadіynishoy.

Typical components of the architecture of the software product and types of support to software Possibility of implementation of architecture, which is being developed. Overworld functionality. Overworld functionality. A decision has been made about the supply of ready-made components of the software. A decision has been made about the supply of ready-made components of the software. Change strategy. Change strategy.

Chi clearly describes the overall organization of the program; which includes the specification of an overview of the architecture and її priming. Chi clearly describes the overall organization of the program; which includes the specification of an overview of the architecture and її priming. Chi is adequately assigned to the main components of the program, their scope of compatibility and interaction with other components. Chi is adequately assigned to the main components of the program, their scope of compatibility and interaction with other components. All of the functions assigned to the specification can be implemented by a reasonable number of system components. All of the functions assigned to the specification can be implemented by a reasonable number of system components. Chi induced a description of the most important classes and their priming. Chi induced a description of the most important classes and their priming. Chi induced description of the organization of the database. Chi induced description of the organization of the database. Chi appointed business rules. Chi appointed business rules. Chi described їхній infusion on the system. Chi described їхній infusion on the system. A checklist of food that allows you to grow visnovok to the quality of architecture:

A checklist of food, which allows you to create vysnovki about the quality of architecture: Chi describes the strategy for designing the interface of the koristuvach. Chi describes the strategy for designing the interface of the koristuvach. Chi razrobleniy interface is modular, so that yoga change is not poured into the part of the system that is missing. Chi razrobleniy interface is modular, so that yoga change is not poured into the part of the system that is missing. Chi induced description of the strategy of introduction-visitation of data. Chi induced description of the strategy of introduction-visitation of data. Chi conducting an analysis of the productivity of the system, which can be implemented with the help of given architecture. Chi conducting an analysis of the productivity of the system, which can be implemented with the help of given architecture. Chi carried out an analysis of the reliability of the design system. Chi carried out an analysis of the reliability of the design system. Chi carrying out an analysis of the power of scalability and expansion of the system. Chi carrying out an analysis of the power of scalability and expansion of the system.

PP refactoring Code is repeated; the implementation of the method is great; the contribution of the cycles is too great, but the cycle itself is already great; the class may be filthy zv'yaznist (the authoritativeness of that method and the class is guilty of describing only 1 object); The class interface does not form a narrow abstraction; The method accepts a lot of parameters. It is necessary to apply, so that the number of parameters was reasonably minimal; Okremi parts of the class change independently from the other parts of the class; Refactoring transfers the adaptation of software to new hardware and to new operating systems, new development tools, new capabilities, as well as software architecture and functionality. The cost of changing the internal structure of software security without changing its internal behavior, or requiring the modification of software security. Reasonable reasons for refactoring:

PP refactoring when changing programs requires a parallel change of a number of classes. In times of such a situation, it is necessary to reorganize the classes with the method of minimization in the future place of possible changes; it is brought in parallel to change the kіlka ієrarchіy spadkuvannya; be brought to change the number of blocks in the case. It is necessary to carry out the modification of the program in such a way that the implementation of the case block is completed, and the calls are made in the required number of times for the program; The disputed elements of the data, which are victorious at once, are not organized in a class. If you repeatedly victorious one and the same set of data elements, then take a closer look at the combined data and operations that hover over them, place them in an okremium class;

PP refactoring method to overcome more elements of the lower class, lower class. Tse means that the method needs to be migrated to a new class and viklikati yogo zі old; the elementary type of data is overwhelmed. To describe the essence of the real world, it is better to vikoristovuvat the same class, lower perevantazhuvat the any-nebud іsnuyuchiy type of data; the class may need to be subdivided into functionality. Better than another class, you will be better off, transferring your functionality to another class; from the language of methods, “vagrant” data are transmitted. Data that are passed to the method only for the purpose of passing them to another method are called "stray". If you find yourself in such situations, try to change the architecture of classes and methods, so that you can find them.

Refactoring software security object-intermediary does not hurt anything. If the role of a class is to redirect calls to methods to other classes, then it is better to use such an object-intermediary to remove calls from other classes without any middle; one class too much knows about the other class. In this situation, it is necessary to encapsulate the suvorishoy, in order to ensure the minimum knowledge of depression about your father; the method may not be far away im'ya; data-members є vіdkrimi. This erases the line between the interface and implementation, inevitably destroys the encapsulation, that borders the flexibility of the program; rozm_schuvat komentari at the exit code;

Software refactoring is a subclass of Vikoristov's only a small part of the methods of its ancestors. Such a situation can be blamed if the new class is created only for the decline of a number of methods from the base class, and not in order to describe the new reality. In order to vanish, it is necessary to remake the base class, in such a way as to give access to the new class only to the necessary methods; code to replace global changes. Global mayut but tі zminnі, yakі really vikoristovuyutsya all software. Reshta zminnі may be either local, or may become the authorities of any objects; the program to clean up the code, which may be needed if necessary. Under the hour of the system’s creation, it’s time to transfer the time, where the future code can be given to the future.

Computer science, cybernetics and programming

Iteration N Unifications of the USDP software development process The analytical model determines the base class for stosuvannya. The design model describes the links and visibility between classes and objects seen.

Activity #20
General principles and approaches to the development of the PZ

Models of distribution software

1. Vodospadna
2. Cascade model
3. Spiral
4. Extreme programming
5. incremental
6. MSF Methodology

waterfall model

Spiral model

Incremental expansion

Wymog analysis

Project design

Implementation

Component not

testing

Integration

testuvannya

one whole

Iteration 1 Iteration 2 …. Iteration N

Unified Software Development Process (USDP)

1. The variation model describes the variations in which the program will be victorious.
2. The analytical model determines the base class for stosuvannya.
3. The design model describes the links and visibility between classes and visions of objects
4. The pharyngeal model determines the distribution of software on computers.
5. The implementation model determines the internal organization of the program code.
6. The testing model is composed of components, test procedures and other test options.

MSF Methodology

Typical components of the architecture of the software product and types of software to software

Vіdmovostіykіst- The succession of the authorities of the system, which promotes the arrogance of pardons, the restoration of that localization of filthy nasledkiv for the system. During the development of a real system to ensure the stability to safety, it is necessary to transfer all kinds of situations that can cause the system to fail and develop the mechanisms for processing failures.

arrogance – the building of the system is resistant to various weather and failures.

Vidmova – system transitionin the wake of a pardon in a povnistyu non-practical camp.

Zbіy - Pardon in the robotic system, so as not to cause trouble until the system exits.

The less vidmov that zboїv for the same song interval of an hour, the system is vvazhaetsya nadіynishoy.

When looking at the technology of software development, it is necessary to focus on system intelligence, which conveys not only a few aspects of the problem of software development, but the problem as a whole. The system pidhid is implemented in the open space and in the hour.

The system pidhіd at the hour considers the sequence of stages of the creation of the PZ in the moment of the formation of unsatisfied demand PZ until the moment of її cherry and support in the operation of the selected software product.

System pidhіd at "space" transmitting a view of the broken software as part of the system. At the same time, on the basis of the development of the information needs of the system, the software is expanded into the same, the goals and functions of the software are formulated, the prototypes of the software tools are analyzed. Formed and documented vimogi to PZ.

The current technology of software development is looking at programming as one of the stages of development in the last stages of the development cycle. All these stages will be explained by the understanding of the life cycle of the PZ and the faults of buttrimani in the form of instrumental software and hardware.

Conforming to the international standard ISO/IEC 12207 "Information technologies - Processes of the life cycle of PZ"

1) analysis of systemic symptoms and gallstones;

2) designing the architecture of the system;

3) analysis of the power to the software (specifications, external interfaces);

4) design of architecture;

5) detailed design of the skin unit;

6) software coding (programming)

7) testing of single software;

8) integration (integration of PZ) and testing the totality of one PZ;

9) qualification testing of PZ (complex testing);

10) integration of the system unit of the structure of the PZ is due to buti combined with units of the hardware;

11) qualification testing of the system;

12) installation of software.

In this way, the process of developing the PZ may be the beginning of the system, where the PZ will be reversed and completed anew in the system.

After the stages of expansion in the life cycle of the PZ, the stage of operation of the PZ and the support during operation are followed. In some cases, the stages of the life cycle of PZ are induced with some aggravations (enlargements) of inductions of 12 stages. For example, the stages of designing a system that could be assigned to software, designing a software package, designing software algorithms, programming (coding), autonomous software customization, integrated software customization, software operation.

The failure to step-by-step design of a software package, the execution of a software development program without a sufficient implementation of algorithms and the power of interdependence of software structural units often leads to a chaotic process of software development with little chance of success.

Spiral model of the life cycle of PZ. "Important and relieved" (shvidki) technologies for the development of software

The model of the life cycle is considered to be considered as a model of the cascade type. This type of model of the life cycle is good for the PZ, which can be completely and accurately formulated on the cob of development all the possibilities to the PZ.

Scheme of the spiral life cycle of PZ. The actual process of creating a PZ is not always invested in such a simple scheme and is often blamed for the need to turn forward steps for clarification or to review the decisions made.

For PZ yak і іnshih foldable systems, pochatkovі vymogi yakіh deficient povnі, typical iterative process of expansion. With this, for the deyaky types of PZ, it is necessary to proceed to the onset stage of yaknaishvidshe. At the same time, for such a hasty work, not enough shares are used up on the upcoming iteration, or they are left forever.

Golovne zavdannya yaknaishvidshe reach pratsezdatnogo PZ, aktivіzuyuchi tsim process clarification and dopovnennya could. This is the name of the spiral model of the life cycle of PZ.

On the skin coil of the spiral, the version of the product is conjugated; The spiral model of the life cycle of PZ reflects an objectively essential process of iterative development (Fig. 8.2).

It is important that the spiral scheme of the life cycle of the PZ is not recognized as such for the qualified retailers, as for the PZ, not the first versions of which are acceptable for the functional recognition of the PZ.

It is based directly on "Swiss technologies" of software development (Agile Software Development), which gives an ideological orientation to the views that are related to the spiral model of the life cycle. These technologies are based on several ideas:

Interactive interaction between individuals is important for formal procedures and tools,

PZ is more important for the availability of documentation for the new one,

Spіvpratsya from the deputy is important for formal agreements,

Shvidke response to the call is more important for suvor following our plans.

Rice. 8.2 - Scheme of the spiral life cycle of the PZ

In other words, smart technologies are directed at replacing formal and labor-intensive documenting procedures in conjunction with the development on an interactive basis, which is possible with small project sizes, choosing the capacities of spivrobitniks, locating retailers and lockers "in one small box".

The correctness of these principles in the singing world, if the distribution of the PZ is small, the number of qualifications and the evidence of the right "fans") for the development of such types of PZ is important to recount. However, Agile technologies also recognize their ideologies in software projects of the first class and scale, just like the spiral model of the life cycle, and in the same place, de forgiveness of software security leads to some kind of flimsy or costly losses.

There, it’s wrong to make PZ to threaten human life, but the great material costs are due to the exploitation of innovatively thought-out technologies, which will ensure the reliability of the software product.

For the increase in the scale of the software project - the increase in the number of people who need more technology for expansion, warehouse cascade software life cycle, growth. Here, documentation is needed, oskіlki be-yakoy mitі mozhliva vtrat whether-any of retailers, formalization of interprogrammnyh zv'yazkіv, management of changes in software is necessary. It is not for nothing that the standard for the development of PZ has a cascade model of the life cycle itself. If so, I will also be able to implement an iterative process of rozrobki for the rahunok of transferring the stage of designing STS and software for them.

For great software projects (a team of over 100 retailers), the development technology is a key factor that contributes not only to the quality of the software, but also to the very possibility of its creation.

"Important and easing" technologies of software development . The retailers of rich software views invest in a cascade model of the life cycle that is over-regulated, over-documented and important and therefore irrational. Directly using “Shvidkih tekhnologii” (light technologies) of software development (Agile Software Development), which gives an ideological overview of these. These technologies are based on several ideas:

1. Interactive interaction between individuals is important for formal procedures and tools,

2. PZ is more important for the availability of documentation for it,

3. contact with the deputy is important for formal agreements with him,

4. It is more important to respond quickly to new changes for the sake of following our plans.

The correctness of these principles in the Crimea of ​​the third world (the development of the software is not a large number of qualified programmers - "fans", which do not require control of that additional motivation) for the development of the software is important. However, Agile technologies and price recognize their ideologies of zastosovnі in software projects of the first class and scale, so the very same way the spiral model of the life cycle, and there, de pardons of the PZ lead to some kind of inconsistency, or the cost of the coded costs and de visibly to the PZ is constantly changing, to that the boulevards were badly appointed, and it is necessary to adapt to these changes.

Swedish technologies try to reach a compromise between the suvor discipline of the expansion and the full її in the daytime in the name of the change in the flow of papers that accompany the expansion. Shvidkі tekhnologii ї cannot secure the high quality of the software product itself through the minimization of papers, which legally confirms the reliability of the retailer.

The butt of Agile technologies is "Extreme Programming" (XP). Iterations in XP are also short and consist of several operations: coding, testing, listening to the master, designing. The principles of XP - minimality, simplicity, the fate of the deputy, a short cycle, closely related to the retailers - the stench is guilty of sitting in the same room, few operational teams at the same time from the deputy are seen as reasonable and have long been stagnant not only in Swedish technologies, but in XP the stench is brought to a high level.

Analiz Muchi programmatic projects showing, with the same technology, they pass the principles of self -organized, the accentuity of the vicoristani іndivіdalnaya of the roses, korotki іeretsky rods in St.

There, where it is wrong to produce software to threaten human life, or to great financial expenses, it is necessary to arrange, rethink and predict the formalization of "important" technology, which will ensure the reliability of the software product in different retailers in the middle qualification. To increase the scale of the software project - to increase the number of participants in new people, the need for more and more formal technologies of development, which fixes the viability of the skin development participant, to establish a cascade life cycle of PZ, grows. It is not without reason that the cascade model of the life cycle is introduced into the software development standard.

In great collectives of retailers, the problem of management comes to the fore.

For great software projects, the power in orderly coordinated development: structure, integration, ensuring the correct interaction of programs, organizing the correct and coordinated implementation of inevitable changes are the keys. and add to the possibility of their creation.

In small software projects, algorithmic development, having added a lot of talented features, play the primary role, while in large projects, the numbers of officials are reduced and injected into the head of development.

Rozrobniki PZ, yakі may have an average capacity, and there are more of them, and yakі technologic disciplines are supported within the framework of the correct technology, due to the rozrobljat PZ of the necessary quality. "Pidrimuy order and vin pidtrimaє you."

Software Development Models Waterfall Cascading Model Spiral Extreme Programming UI Prototyping Incremental W-Model Testing Unification Software Development Process (USDP) MSF Methodology

Waterfall model Analysis could Create product specification Design Design Architecture for product Implementation Development of output code Integration of four parts of the output code

Extreme Programming Weekend Analysis Designing Integration Implementing Testing New Developments Analyzing/Approving/Modifying the Sales Plan Product Release

UI Prototyping Product Release Software Development and Improvement Changes Clarification and Specification Changes to the Prototype and Additional Functionality Basic Functionality Interface Prototype Previous Specification

Incremental technology Iteration 1 Iteration 2 …. Analysis could Design Implementation Component testing Integration Testing of a single integer Iteration N

Unified software development process (USDP) Ø The variation model describes the ways in which the software will be victorious. Ø The analytical model determines the base class for stosuvannya. Ø The design model describes the links and visibility between classes and visions of objects. Ø The laryngeal model describes the distribution of software for computers. Ø The implementation model determines the internal organization of the program code. Ø The test model consists of components, test procedures and other test options.

Unification of software development process (USDP) Selection could be ITER 1…. Iter N Designing Iter 1. Iter N Implementation Iter 1. Iter N Designing Iter 1. Iter N Testing Iter 1…. Iter N

Typical components of the architecture of the software product and types of software to software Ø Ø Ø Ø Organization of the program Main class of the system

Typical components of the architecture of the software product and types of software to software. Vіdmovostіykіst - sukupnіst polіstіvnostі system, scho pіdvishuє її nadіynіst vіdіynіst vіvlennі pardons, vіdnovlennya іt localіzії vile naslіdkіv for the system. During the development of a real system to ensure the stability to safety, it is necessary to transfer all kinds of situations that can cause the system to fail and develop the mechanisms for processing failures. Reliability - the building of the system withstands various weather and failures. Vіdmova - tse transition of the system to the last pardon in the state of non-practical camp. Zbіy - a pardon for a robotic system, so as not to bring the system out of harmony. The less vidmov that zboїv for the same song interval of an hour, the system is vvazhaetsya nadіynishoy.

Typical components of the architecture of the software product and types of support up to PZ Curve nadіynіst N t 1 t Next, it would be more important to know a pardon. Why is the system folded, the greater is the ymovіrnіst vіdmov and zboїv.

Typical components of the architecture of the software product and types of support up to software Ø Possibility of implementing the architecture that is being developed. Ø Superfluous functionality. Ø Adoption of a decision about the supply of ready-made components of the PZ. Ø Change strategy.

A checklist of food that allows you to learn about the quality of architecture: Ø Chi clearly describes the overall organization of the program; Ø Ø Ø including specification of architectural review and sizing. Chi is adequately assigned to the main components of the program, their scope of compatibility and interaction with other components. All of the functions assigned to the specification can be implemented by a reasonable number of system components. Chi induced a description of the most important classes and their priming. Chi induced description of the organization of the database. Chi appointed business rules. Chi described їхній infusion on the system.

A checklist of nutrition, which allows the creation of drawings about the quality of the architecture: Ø The strategy for designing the interface of the core is described. Ø Chizrobleniy іinterfeys koristuvach modular, schob yogo zmіni not poured into the part of the system that was left out. Ø A description of the strategy for introducing and seeing data has been provided. Ø An analysis of the productivity of the system was carried out, which can be implemented with different architectures. Ø An analysis of the reliability of the design system was carried out. Ø An analysis of the power scalability and expansion of the system was carried out.

Software refactoring Refactoring transfers the adaptation of software to new hardware and to new operating systems, new development tools, new capabilities, as well as software architecture and functionality. The cost of changing the internal structure of software security without changing its internal behavior, or requiring the modification of software security. Reasonable reasons for refactoring: - The code is repeated; the implementation of the method is great; the contribution of the cycles is too great, but the cycle itself is already great; the class may be filthy zv'yaznist (the authoritativeness of that method and the class is guilty of describing only 1 object); The class interface does not form a narrow abstraction; The method accepts a lot of parameters. It is necessary to apply, so that the number of parameters was reasonably minimal; Okremi parts of the class change independently from the other parts of the class;

PP refactoring when changing programs requires a parallel change of a number of classes. In times of such a situation, it is necessary to reorganize the classes with the method of minimization in the future place of possible changes; it is brought in parallel to change the kіlka ієrarchіy spadkuvannya; be brought to change the number of blocks in the case. It is necessary to carry out the modification of the program in such a way that the implementation of the case block is completed, and the calls are made in the required number of times for the program; The disputed elements of the data, which are victorious at once, are not organized in a class. If you repeatedly victorious one and the same set of data elements, then take a closer look at the combined data and operations that hover over them, place them in an okremium class;

PP refactoring method to overcome more elements of the lower class, lower class. Tse means that the method needs to be migrated to a new class and viklikati yogo zі old; the elementary type of data is overwhelmed. To describe the essence of the real world, it’s better to win the class, to change it better, whether it’s the essential type of data; the class may need to be subdivided into functionality. Better than another class, you will be better off, transferring your functionality to another class; from the language of methods, “vagrant” data are transmitted. Data that are passed to the method only for the purpose of passing them to another method are called "stray". If you find yourself in such situations, try to change the architecture of classes and methods, so that you can find them.

Refactoring software security object-intermediary does not hurt anything. If the role of a class is to redirect calls to methods to other classes, then it is better to use such an object-intermediary to remove calls from other classes without any middle; one class too much knows about the other class. In this situation, it is necessary to encapsulate the suvorishoy, in order to ensure the minimum knowledge of depression about your father; the method may not be far away im'ya; data-members є vіdkrimi. This erases the line between the interface and implementation, inevitably destroys the encapsulation, that borders the flexibility of the program; rozm_schuvat komentari at the exit code;

Software refactoring is a subclass of Vikoristov's only a small part of the methods of its ancestors. Such a situation can be blamed if the new class is created only for the decline of a number of methods from the base class, and not in order to describe the new reality. In order to vanish, it is necessary to remake the base class, in such a way as to give access to the new class only to the necessary methods; code to replace global changes. Global mayut but tі zminnі, yakі really vikoristovuyutsya all software. Reshta zminnі may be either local, or may become the authorities of any objects; the program to clean up the code, which may be needed if necessary. Under the hour of the system’s creation, it’s time to transfer the time, where the future code can be given to the future.

1. Designated programming technology. History of the development of programming technology. Types of software projects Warehouse parts of programming technology. Project, product, process personnel

2. Life cycle of the program. The cyclical nature of the development. Basic understanding of programming technology. Processes and models. Phases and turns. Vіhi and artifacts. Zatsіkavlenі individuals and pratsіvniki.

3. Identification and analysis could not. Wimogi to software security. Wimog expansion scheme. Power management.

4. Architecture and detailed design. Implementation and coding. Testing and verification. Yakistyu control process. Methods of "white screen" and "black screen". Look at the inspection. Tsіlі testing. Verification, validation and system testing. Suprovіd i rozrobka, scho trivaє.

5. Models for the development process. Waterfall and conveyor models. Spiral and incremental models. Gnuchki models for the process of development.

6. Designing a process model. Viyavlennya vimog before the process. Vykoristovuvanі phases, vіhi and artifacts. Select the process of architecture. The procedure for carrying out a standard project. Documented procedures.

7. Models of the team of retailers. The collective nature of the development. Optimal command size. Order of participants in the project. Development of the team and development of the staff. Specialization, cooperation and interaction.

8. Models of the team of retailers. Hierarchical command model. Surgical team method. The team model is old.

9. The nature of programming. The Science of Programming. Programming art. Programming craft. programming paradigm. Structural programming. Logic programming. Object-oriented programming.

10. Software architecture. Get management. Architecture client/server. Services. Trisharov architecture. Software design. Conceptual design. Logical design. Detail design.

1. Noviks come to the development of the software » http://window. /window_catalog/files/r60368/itmo307.pdf.

2. Extreme programming. - St. Petersburg: Peter, 2002.

3. Technology of software development. - St. Petersburg. : Peter, 2004.

4. Brooks-mol. are designed and created software complexes. M: Nauka, 1975; I will translate the new vision: Mythical human-moon. St. Petersburg: SYMBOL +, 1999.

5. Algorithms + structures of data = programs. M., Svit, 1978.

6. Systematic programming. Intro. M: Light, 1977.

7. Structural programming. M: Light, 1975.

8. Programming discipline. M: Light, 1978.

9. Technology of software development. - St. Petersburg: Peter, 2002.

10. Terekhiv programming. M: BINOM, 2006.

11. Rambo J. Unification of software development process. St. Petersburg: Peter, 2002.

Economic theory for managers

Course of Economic Theory: Assistant for Universities / Ed. . - Kirov: "ACA", 2004. Kolemaev - mathematical modeling. Modeling of macroeconomic processes and systems: assistant. M.: UNITI-DANA, 2005. Bazhin cybernetics. Kharkiv: Consul, 2004. Leushin workshop on methods of mathematical modeling: manual. Nizhny Novgorod State tech. univ. - N. Novorod, 2007. To politicians about the economy: Lectures by Nobel laureates on the economy. M: Modern economy and law, 2005. Cheremnykh. Prosunutiy Riven: Handbook.-M: INFRA-M, 2008. Evolution of the institutes of mini-economics. Institute of Economics UB RAS, - M: Nauka, 2007.

Development technologies and acceptance of managerial decisions [Н]

I. Theory accepts a decision: a handyman. Moscow: Ispit, 2006. 573 p. I. Praise decision. Theory and methods of development of managerial decisions. Head helper. - M .: March, 2005. - 496 g. Development of the management decision - M .: Vidavnitstvo "Delo", 2004. – 392 p. G. Expert evaluation and decision. - M.: Patent, 1996. - 271 p. Taha // Introduction to follow-up operations = Operations Research: An Introduction. - 7th view. - M .: "Williams", 2007. - S. 549-594. G. Theil. Economical forecasts and decisions. M.: "Progress" 1970. K. D. Lewis. Methods of forecasting economic indicators. M .: "Finance and statistics" 1986. G. S. Kildishev, A. A. Frenkel. Analysis of hourly series and forecasting. Moscow: "Statistics" 1973. O. Kim, C. W. M'uller, W. R. Klekka et al. Factorial, discriminant and cluster analysis. M.: "Finance and statistics" 1989. Effective manager. Book 3 - МІМ LINK, 1999 Turevsky and management of motor transport business. - M: Vishcha school, 2005. , ; for red. . System analysis for management: a guidebook. - M.: Finance and statistics, 2006. , Tinkov: heading guide. - M.: KNORUS, 2006.

Modeling business processes in integrated management systems

"Modeling business processes with AllFusion Process Modeler (BPwin 4.1) Dialogue-MIFI" 2003 "Creating information systems with AllFusion Modeling Suite" view. "Dialogue-MIPHI" 2003 "Practice of functional modeling with AllFusion Process Modeler 4.1. (BPwin) What? New? Yak?" view. "Dialog-MIFI" 2004 Dubeikovsky modeling with AllFusion Process Modeler (BPwin). view. "Dialogue-MIPHI" 2007 D. Marka, K. McGowan "Methodology of structural analysis and design of SADT" 1993 Classical practice of SADT methodology. Cheremny analysis of systems: IDEF-technologies, Modeling and analysis of systems. IDEF technologies. Workshop. M.: Finance and statistics, 2001. , "Structural business models: DFD-technologies" http://www. /Level4.asp? ItemId=5810 "Theory and practice of reorganization of business processes"2003/P50.1.. Methodology of functional modeling. M: State Standard of Russia, 2000. http://www. IDEF0, IDEF3, DFD http://www. Business process modeling by BPwin http://www. /department/se/devis/7/ IDEF0 for business process management http:///content/view/21/27/ http://www. /dir/cat32/subj45/file1411/view1411.html http://www. http://www.

Evaluation of the effectiveness of software products

1. IT architecture

2. Domain management processes.

3. Transfer of processes to the domain Planning and Organization

4. Transfer of processes to the domain Predbannya and provazhennya

5. Transfer of processes to the domain Operation and Support

6. Transfer of processes to the domain Monitoring and Evaluation

7. Characteristics of the maturity model of processes

9. KPI and KGI їх interrelationships and recognition

1. 10. Go to the control of IT and go to the control of addons. Zones of compliance and obligations to business and IT.

Cobit 4.1 Russian knowledge.

Legal regulation of creation and achievement of intellectual authority

1. Reinstate the intellectual property rights to the results of intellectual activity and open your mind.

2. Re-arrange the agreements according to the wine law. Describe the skins from the designations of the contracts for the disposition of the exclusive right.

4. Describe the main provisions of the legal protection of the Program for EOM as an object of copyright.

5. Equalize the main provisions of the legal protection of data as an object of copyright and as an object of collective rights.

6. Describe the mind and patentability of the objects of patent rights: wine owners; brown models; promissory words.

7. Expand the criteria for the patentability of winemaking: novelty; wine riven; promissory zastosovnіst.

8. Describe the procedure for taking away a patent for wine, the basic model or the wording of the word, and also think about how to secure a patent for that term.

9. Give the ultimate know-how and rethink your mind, when such blames are created, the legal protection of the secrets of the trade will be established.

10. Perehrahute zab іndivіdііlіlіzії, scho are protected, and give їх equal characteristics.

1., The right of intellectual power in the Russian Federation, assistant // M, Prospect, 2007

2. , The right of intellectual power, heading help // M, RIOR, 2009

Project management and development of PZ [ І]

Kent Beck - Extreme programming Frederik Brooks - Mythical human-moon or how software systems are created. Tom de Marco - Deadline. A novel about keruvannya projects. Tom de Marco, Timothy Lister - Waltz with bears. Tom de Marco, Timothy Lister - Human factor - successful projects and teams. Alistair Cowburn – The skin project has its own methodology. Alistair Cowburn - People are non-linear and the most important components in the creation of software. Automator notes. Professional advice. Philip Krachten - Entry to the Rational Unified Process. Henrik Kniberg - Scrum and XP: notes from the front line. Presentations of lectures from the course