When looking at the technology of the distribution of the software, it is necessary to investigate the systematic input, which is not the transfer of the problem of software distribution, but the problem as a whole. The system pidhid is realized in space and in hours.

System response at the time of viewing until the moment is allowed and a supervisor in the exploitation of the discarded software product.

System pidhid in "space" transferє view is distributed software, as part of the system. At the same time, on the basis of the information system requirements, the software will be included and developed, the set of software functions will be formulated, and the prototypes of the software will be analyzed. It is formed and documented vimogi before software.

modern technology Software distributions for viewing the program, as one of the stages of the distribution in the last stages of the production cycle. All stages of life are to be understood by the understandings of the life cycle of software and guilt but also by means of various instrumental software and apparatus.

According to the international standard ISO / IEC 12207 "Information technology - Processes of the life cycle of software", the process of developing software to compensate for the onset of stages of the life cycle of software:

1) analysis systemic vimogsі areas of storage;

2) design of the architecture of the system;

3) analysis of vimog to PZ (specificity, call interface,);

4) design of the architecture of the PZ;

5) detailed design of the skin software unit;

6) software coding (programming)

7) testing one software;

8) Integration (software integration) and testing of software unit;

9) quality testing software (complex testing);

10) Integration of the system and one structure of software to be guilty of being connected with one unit of equipment;

11) the quality of the vip testing system;

12) software installation.

In such a rank, the process of developing the software can be found in the system;

Writing the stages of development in the life cycle of PZ followed by the stage of exploitation of the superconductor during exploitation. One of the changes in the stages of the life cycle of the software is guided by the actions of the public (enlargement) of the 12 stages. For example, the stages of designing the system and the designation of the software to the PZ, the design of the software complex, the design of the software algorithms, the programming (code), the autonomous software application, the integrated software implementation, the operation of the PZ.

The anger of the stages of software design, the practice of immediately reading the software without sufficient optimization of algorithms and power between the structural units of software often lead to a chaotic software development process with little chances of success.

Spiral model of the life cycle of software. "Important and Polegsheni"

The model of the life cycle (life cycle) is considered to be a model of the cascade type. This type of lifecycle model is good for software, for any on the very cob of the rosette you can more and more accurately formulate all the options to software.

Scheme of the spiral life cycle of software. However, the real process of establishing the PZ is not expected to be invested in such a rigorous scheme, and it is often the case that it is necessary to turn in front of the front steps to clarify or re-glance at the decisions taken.

For software as well as for other folding systems, cobs, and for any lack of reason, the characteristic iterative process of crafting. With a whole lot for the types of PO navit bazhano, go to the offensive stage of yakomog shvidshe. With a whole lot of inevitability, with such a quick robot, it is not enough to get used to the onset of the iteration, or to become overwhelmed.

The main task yakomog shvidshe reach the original software, activates the very process of clarifying and updating the software. This is the name of the spiral model of the life cycle of software.

On the skin turn of the spiral, the current version of the product is to be determined, and the robots of the offensive turn are planned to be clarified before the software. The spinal model of the life cycle of software represents an objectively flowing process of iterative software development (Fig. 8.2).

It should be noted that the spinal diagram of the life cycle of software is not designated as styling for high-end products, but for software, as for some of the first versions of software that are permissible for the functional characteristics of software.

We will provide software distribution (Agile Software Development) directly from the "Shy technologies", so that even ideologically we will look at it, we will link it to the life cycle model. This technology is based on the following ideas:

Interactive interaction of individuals is more important than formal procedures and tools,

Simple software is more important than the explicitness of the documentation on the new one,

Spіvpratsya with a deputy is important more than formal agreements,

A quick response to new changes is more important than strict attention to our plans.

Small. 8.2 - Scheme of the Spiral Life Cycle Software

In other words, advanced technologies are directed to the replacement of formal and labor-intensive documentary procedures of interaction in the process of development on interactive, as it is possible with small sizes of the project, the changes in the quality of sportsmen, development

The correctness of these principles in the singing world, if the distribution of the software is small, the number of qualified and well-known “fanatics”) for the development of certain types of software is important. However, Agile technologies and ideologists are stagnant in software projects of the singing class and scale, as well as the spiritual model of the life cycle, and it’s there that it’s not enough to make them do something wrong, or at a fraction of the compensation.

There, it’s not so easy to make a human life to the point of contamination, or to the great material costs of the blame for the victorious efforts to think over the technology, so as to ensure the need for the software product.

On the larger scale of the software project, the larger scale of the software project, the bigger the number of people who need the hard technology of the development, how to create a cascading software lifecycle, grows. Documentation is needed here, so as at any moment there can be involved in any development, formalization of interprogram links is required, management of software changes and so on. At the same time, it also allows the implementation of the iterative process of development for the transfer of stages of design of STS and software for them.

For two great software projects (a team of over 100 projects), the technology of packaging is a key factor, which is not only infused into the quality of the production plant, but also into the very possibility of its opening.

"Important and lodging" technologies for the production of PZ . The dealers of bagatokh vid_v software vvazayut a cascade model of the life cycle, backwardly regulated, backwardly documented and important and unreasonable. There is a simple "smart technologies" (light technologies) software development (Agile Software Development), which gives an ideological basis for a glance. This technology is based on the following ideas:

1.Interactive interaction of individuals is more important than formal procedures and tools,

2.Practice is more important than the explicitness of the documentation on the new one,

3. Sp_vpratsya with the deputy is important more than formal agreements with him,

4. The quick response to new changes is more important than strict attention to our plans.

The correctness of these principles is the third in the singing world (there is a small number of qualified programs - "fanatics", which may be consumed in continuous control and additional motivation) for the development of the importance of recognition. However, Agile technologies and ideologists are stagnant in the program projects of the singing class and scale, as it is the spiritual model of the life cycle, and it’s there that it’s worthwhile to make up for some inconveniences, or at a fraction of the cost of collecting before and after the post. , so as the bully went back to the nasty value, and the adaptation is required to the cich zmin.

Shvidkі technologies - try to reach the compromise between the supreme discipline of the development and increase the efficiency of the day in the process of changing the flow of papers, which supervise the development.

Agile technology application є "Extreme Programming" (XP). Іteratsii in XP are even short and are stored in choter operations: kodvannya, testuvannya, vislukhovvannya deputy, project. The principles of XP - minimity, simplicity, the fate of a deputy, a short cycle, a lot of people in the same room

An analysis of unrelenting software projects, showing how advanced technologies, how to promote the principle of self-organizing, how to accentuate the development of individual health care professionals, short ideas for working out in a wide range of robotic models,

There, it’s not so easy to make people's life to the point of contamination, but to the great material costs, the fault of the victors will be in order, I have thought through and predicted the formalized “important” technology, so that I will forget about the need for the software project of the software project There are a number of dancers in new people who need a sharp and formal technology of production, physical flexibility of the skin participant of production, warehouse cascade life cycle software, growth. The cascade model of the life cycle itself is not a gift in the standard of software distribution.

For the great collectives of development, the problem of management is to come to the fore.

For two great software projects, nutrition of an orderly coordinated structure: structure of bathing, integration, ensuring the correct interaction of the program, organizing the correct and coordinated implementation of inevitable snakes are key and pour into the very power of their stem.

In small software projects, algorithmic visualization, injecting some talented specialties, play an initial role, while in great projects, factories do not develop and do not infuse an initial inflow into the market.

Razrobniki PZ, which volodyyut average capabilities, and such a lot, and the technological discipline is approached within the framework of the correct technology, are responsible for the development of the necessary quality. "Take the order and see you".

abstract: Look at the nasty pidhid until the end software security, The main principle of nasty rozrobka. Guided by a change of techniques, such as in the singing world, adhere to the principles of the dull distribution of software security. Analyze the keys of value and the principle of nasty distribution.

You can add a presentation before this lecture.

Meta lectures:

Otrimat the statement about the recognition of that basic principle of the nasty distribution of software security.

Entry

Gnuchka methodology for the development of software security orієntovana on the occasion of the iterative entrance, with software product turn out step by step, in small crocs, to include the implementation of the singing set of vimogs. When you transfer it, you can change it. The team, scho vikoristovuyu nasty methodology, are formed from universal development, as vikonuyut development in the process of the development of the software product.

With the victorious nasty methodologies of minimizing the risks, go by the way of building the box to a series of short cycles, iterations, Trivial 2 -3 tizhni. Iteratsiya is a collection of works planned for the performance at the singing period of the hour. The skin iteration has a first-time version of the software system, in which the most priority is implemented (for this iteration) vimogi of the deputy... At the skin iteration, all the staff that are necessary for the start of the programmed security: planning, analysis, design, coding, testing and documenting... If you want okrema iteration, as a rule, there is not enough for a release new version product, rely on respect, software product ready to be issued in the end of the skin iteration. After completing the skin iteration, the team will reassess the priorities of the software to the software product, it is possible to add correctives to the system distribution.

Principles and meanings of a naughty outlet

For the methodology of dull development, the declared keys of the postulate, which allow teams to reach high productivity:

• people і їх interaction;
• delivery of great software security;
• sp_vpratsya with a deputy;
• reaction to change.

People and interaction. People are the warehouse part of success. Some of the team members and good communities are important for high-performing teams. To create a communal nasty method, allow for parts of the negotiation of the results of the robot and the introduction of changes into the solution. The negotiation can be carried out every day with a trickle of quilin and after the completion of the skin iteration with an analysis of the results in a robotic and retrospective. For effective communes during the collection, the team members blame the onset of the key behavioral rules:

• povagu dumki of the skin member of the command;
• we will be truthful in any spilkuvanni;
• the insight of all the tributes, the day and the decision;
• vpevnen_st, who the skinny participant pidtrimaє command;
• the keenness of the team and the goals.

For the establishment of highly productive teams in the dull methodologies of an effective team and good communication, the necessary thoroughness of software tools is required.

A simple program of securing is more important than all-inclusive documentation. All the naughty methodology is scandalous about the need to deliver small fragments of efficient software security to the deputy through the specified intervals. Secure program As a rule, you can pass the level of unit testing, testing on the level of the system. With a whole lot of documentation, he is guilty but the minimum. In the process of designing, the team is guilty of creating a short document in the current standard, to avenge the structure's definition and description of the structure.

Spіvpratsya with the deputy is important more than formal housekeeping for the contract. If the project is successfully completed, it is necessary to regularly and often co-operate with the deputy. The deputy is guilty of regularly taking part in the negotiated decision, how to get on with the software security, and his own enthusiasm and respect. The assignment of the deputy in the process of developing the software security is necessary to establish the original product.

Prompt response to changes is important to the plan. The state of the art responds to the changes in abundance, which is the reason for the success of the software project. During the process of software product development, it often changes vimogi of the deputy... The substitutes often don’t know exactly what they want, until they’re quiet, as long as they don’t pamper themselves. programmatically secure... Gnuchkі methodology whisper Zvorotn_y zv'yazyk from the assistants in the process of launching the software product. Prompt response to changes is necessary for the product to be satisfied, in order to satisfy the deputy and to ensure the value for the business.

The postulates of a nasty rozrobok are adopted by 12 principles. Specific methods of dull development have processes and rules that, in a large number of the world, adapt to these principles. Gnuchkі methodology of establishment software products primed on offensive principles:

1. We are looking for the priority to be satisfied with the support of the deputy for the help of the supply of the coris software security in the terms of the term with further continuous updates. Gnuchkі methods may on the basis of the supply of cob version and part of the update. By the command є delivery of a pre-printed version with a broach of decal documents for the moment of the cob to the project. Nadal software systems The functionality of the supply of leather goods is gradually expanded. The deputy can help the promislovu exploitation of the system, as long as it is more functional. Also, the deputy can simply get acquainted with the stream version of the software security, get his own messages from the respect.
2. Don't ignore the change, don't know how to navigate through the various stages of the retail. Gnuchkі processes allow vrahovuvati zmіni for the protection of the competing candidates of the deputy. Commands, scho vikoristovuyu nasty methods, prying the structure of programs yakіsoї, with the smallest infusion of changes on the system as a whole.
3. Post a new version of the PZ often, with an interval from one month to two months, which are used in smaller terms. At the same time, they rely on me to deliver a program that will satisfy the needs of the corystuvach, with a minimum of supervised documentation.
4. The contributors and developers are guilty of pratsyuvati spіlno in opposition to the whole project. To get involved, for a successful project, deputies, distributors, and all individuals who are guilty are often priced at a high price for a highly detailed software product.
5. Design people to blame for the life. Create teams of the project with normal minds of the robots, without a need for additional help, so that the members of the team bring the right to the end.
6. The most effective and productive method of transmitting information to the team of developers and sharing ideas all over the place is the rozmova vich-na-vich. In nasty projects, the main way of communion is simple human spilkuvannya. Letters and documents are created and updated step by step in the world of software distribution and only as needed.
7. The programme's performance is the main indicator of the progress in the project. About the approach of a nasty project to its completion is judged by the fact that it is obvious at the given moment of the program to be given to the deputy's deputy.
8. Gnuchkі processes take pre-construction rozrobtsі. The contributors, the distributors and the guilty ones are guilty of being in the cold, and the constant pace is always the same.
9. I don’t respect the technical perfection and the clear design of advancing in the output of nasty technologies. The members of the nasty command are forced to turn off the code, refactoring regularly.
10. Simplicity is a mystery to reach more, shy less. The members of the command will display the flow of data as simply and clearly as possible. If there is a problem in the future, then in a low-quality product it is possible to make a change without great vitrates.
11. sami beautiful architects, Vimogi that projects see self-organizing commands. For nasty teams, the staff must not be awarded to members, but to teams as a whole. The team itself is virishuє, as the best way to implement vimogi of the deputy. The members of the command are mentally working on the aspects of the project. The skin participant is allowed to make his own contribution to the home right. There is no such member of the command, which is uniaxially giving bi for architecture, vimogi abo testi.
12. The team is guilty of regularly obsessing over the team, as it is more effective, and then, as a matter of fact, correcting and adjusting their behavior. Gnuchka team is constantly correcting its organization, rules, please and reciprocity.

We introduce the principles, the singing world, we introduce a number of methodologies for the development of software security:

Infection in software engineering two main approaches to the development of PZ ІС in different ways decomposition of systems: functional-modular (structural) pidhid, which is based on the principle of functional decomposition, in which the structure of the system is described in terms of the structure of the system and is described in terms of the structure of the system and the transfer of information and information Objectively organizing pidhid, I will describe the structure of the IC in terms of objects and connections between them, and the behavior of the system - in terms of interchange between different objects.

From the same time, the day of the structural approach to the development of the PZ ІС polyaga in the decomposition of the automated functions: the system breaks down on the functional pidsystems, which in its own way can go on the functions, the stink - at the establishment of procedures, and so on until At the same time, the IC secures the integrity of the declaration, all warehouses are interconnected. With the development of the system "from the bottom up", from the building to the whole system, the complexity is involved, problems in the inventory information relations okremikh components.

Basic principles of structural approach є:

o principle " razdіlyay i volodaryuy ";

o principle the architectural ordering - the principle of organizing storage systems in the structure of the tree-like structure with the addition of new parts on the skin. The vision of the two basic principles does not mean, but of the other principle, the examples of skin ignorance from them can lead to non-transferable inheritance.

The main principles are:

o abstract - seeing the exact aspects of the system;

o inconsistency - Rudging and narrowing of elements of the system;

o structure - the given are structured and structured and organized.

Methodical fundamentals of software security technology

Vizualne model. The software model is called a formalized description of the PZ system on a singing level of abstraction. The skin model is based on a specific aspect of the system, vicariously typing diagrams and documents in a given format, as well as visualizing thoughts and ideas about the activity of young people with specific interests, roles, or employees.

Graphic (visual) models є in ways for visualization, description, design and documentation of the architecture of the system. Warehouse of models that can be used in a specific skin project, and the steps of detail in the backward look are among the offensive factors:

o difficult project systems;

o the necessary description;

o knowledge and a quick tip of the participants in the project;

o the hour brought into the project.

Visually, the model dwelled into the branch of CASE-zokrem. The understanding of CASE (Computer Aided Software Engineering) is a broad sense. The foremost importance of the understanding, surrounded only by the staff of the automation of the production of the PZ, in this hour a new change has come up, which is looking for more processes in the life cycle of the PZ.

CASE-technology is a supreme method of software design, as well as a set of instrumental inputs, which allows you to model the subject area in a specific form, to analyze the model at all stages of the process and to the supervisor. Most of the useful CASE-inputs are based on the methods of structural, but also objectively-organized, analysis and design, as well as the specificity of the visualization of diagrams and texts for describing the specific models of the systems, sounds

On the current day in the software engineering, there are two main steps to the development of the EIS PZ, the principle view of them is summarized in different ways of decomposition of systems. The first pidhid is called functional-modular or structural. It is based on the principle of functional decomposition, in which the structure of the system is described in terms of the structure of the system and the transfer of information with the same functional elements. Another, ob'yntno-organizing pidhid vikoristovu ob''kktnu decomposition. At the same time, the structure of the system is described in terms of objects and links between them, and the behavior of the system is described in terms of exchanges between objects.

From the same time, the day of the structural approach to the development of the PZ EIS field in its decomposition (development) on the automated function: the system breaks down on the functional pid systems, which, in its turn, go on to the specific functions, that is, to the end of the procedure. At the same time, the system has been automated for securing the system, in all warehouses, components are interconnected. With the development of the system "from the bottom up", from the level of the building to the entire system, the complexity of being involved in, identifying problems in the description of information interconnection of the components.

All the most advanced methods of structural approach are based on a number of foreign principles... Basic principles є:

the principle of "distribute and volodaryuy" (div. pidrozdil 2.1.1);

the principle of the hierarchical ordering - the principle of organization warehouse parts systems in the structure of the tree-like structure with the addition of new parts on the skin.

The vision of the two basic principles does not mean, but the principles are different in number, the fragments of skin ignorance from them can lead to non-transferable inheritance (including the failure of the whole project). The main principles are:

the principle of abstraction - the vision of the absolute aspects of the systems and the visibility of the systems;

the principle of inconsistency - the priming and the narrowness of the elements of the system;

principle of structure

In the structural approach, it is possible to become vicious in the main group of groups, to describe the functional structure of the system and to provide information. Skin groups include different types of models (diagrams), the most extended middle є:

DFD (Data Flow Diagrams) - data flow diagrams;

SADT (Structured Analysis and Design Technique - method of structural analysis and design) - models and general functional diagrams;

ERD (Entity-Relationship Diagrams) - diagrams of "essence-links".

Diagrams of streams of data and diagrams of "day-to-word" - the most often victorious in CASE-types of models.

The specific type of reworked diagrams and interpretations of their constructions are found in the life cycle stage of the software.

At the stage of formulating the SADT-models and DFDs to the PZ, they must act in order to induce the "AS-IS" models and the "TO-BE" models, which are rendered in such a rank, because the structure of the business processes in organizing them and in the , as a rule, it is only a given stage, the odd odor was not assigned to the design of the software). For the help of ERD, one should look at the description of the vicarists in the organization of tributes on the conceptual level, but not in the fallow ones in the implementation of the base danikh (SKBD).

At the stage of DFD design, one needs to learn to describe the structure of the design software system; Similarly, ERD will be refined and updated with new constructions, which describe the presentation of the tribute in a logical way, which is attached to the subgeneration of the scheme of the base of the tribute. These models can be supplemented with diagrams, which add to the system architecture of the software, the structural schemes of the programs, the architecture of the early forms and the menu and in.

Reinsured models in sukupnost give redescribe The EIS software is indispensable for the fact that the system is either current or known. Warehouse diagrams in a specific skin type should be stored due to the foldability of the system and the necessary work and description.

The subject area for large applications of diagrams, guided in a wide distribution, is the tax system of the Russian Federation, the best description of what can be found in the Tax Code of the Russian Federation. Information technologies It will become stagnant in the subtle systems of the Russian Federation, perhaps the singularity.

From the same time, the day of the structural approach to the development of the PZ EIS field in the decomposition (development) on the automated function: the system breaks down on the functional pid systems, which, in its turn, go on to the end of the operation, until the specific procedures. At the same time, the system is taken care of, in all warehouses, components are interconnected. With the development of the system "from the bottom up", from the level of the building to the whole system, the complexity of being involved, identifying problems in the description of information interconnection of the components.

All the most advanced methods of structural approach are based on a number of foreign principles:

1. The principle "distribute and volodaryuy";

2. The principle of "hierarchical ordering" - the principle of organizing storage parts of the system in the "hierarchical tree-like structure" with the addition of new parts on the skin.

The vision of the two basic principles does not mean that the principles are different, so the ignorance of any of them can lead to non-transferable inheritance (including the failure of the whole project). The main principles are:

1. The principle of abstraction - the vision of the absolute aspects of the system and the visibility of everything.

2. The principle of inconsistency, priming and narrowing of elements of the system.

3. The principle of bath structure danih-dani guilty but structured and organized.

In the structural approach in the main two groups, there are several factors, which describe the functional structure of the system and the data. Skin groups include different types of models (diagrams), the most extended middle of them є:

DFD (Data Flow Diagrams) - flow diagrams;

SADT (Structured Analysis and Design Technique - methodology of structural analysis and design) - models and types of functional diagrams: notations IDEF0 (functional model of systems), IDEF1x (conceptual model of data bases of storage systems) describe the flow of processes, interactions between processes and processes, which are changed by processes);

· ERD (Entity - Relationship Diagrams) - diagrams of "day-to-day".

Practically in all methods of structural approach (structural analysis), at the stage of formation of the model to the PZ, two groups are used to form the model:

1. Diagrams, which are instrumental in functions, as the system is guilty of viconuvati, and the connection between these functions is DFD or SADT (IDEF0).

2. Diagrams for modeling data and information (ERD).

The specific type of reworked diagrams and interpretations of their constructions are found in the life cycle stage of the software.

At the stage of the formation of the SADT-models and DFD, to induce the models "AS-IS" and the models "TO-BE" as a rule, only this stage is interspersed, some of the stench was not assigned to the design of the software). For the help of ERD, one should describe the victors in the organization of tribute on the conceptual level, not in the past in the implementation of the base of tribute (SKBD).