Tuesday, September 24, 2013

Special Features of GOMA Modeling

In my previous posts I mentioned a new methodology to model goal-oriented management systems. It is being actively developed today. The reasons to start creating it became the new goal-oriented approach, and, consequently, the new demands that appeared in front of us. As we can see, the focus of modern automation is moving from the simple execution of a sequence of functions toward the achievement of non-trivial business goals. There are needs for wider, more comprehensive automation. Of course, all classical modeling methods can still be applied, but our small experience shows that the modeling of goal-oriented systems using classical methods can be quite hard.

Problems start immediately with the goal meaning, which in many classic methodologies is missing completely. For GOMA it is absolutely crucial and, to work around this problem, we have to introduce special tweaks and bend standard notation to correctly describe a system in our desired terms. Such work looks more like torture than modeling.

It became clear that the requirements for modern modeling methodologies are significantly higher today than a decade ago. The Systems scale of comprehensive automation increases the complexity of models a lot. Today, the size of models is reaching thousands of elements with tens of thousands of relations. Modeling complexity increases exponentially. And, if yesterday modeling using classical methods was not an easy task, tomorrow it may become completely impossible.

Besides the presence of explicit goals, GOMA modeling differs from classical methods in many other ways. Here are just few of those:

  • Specialization in automation of multi-level socio-economical management systems. Many methodologies used today were created to solve specific problems. IDEF/SADT, for instance, was created for the functional analysis of large business systems. RUP/UML initially was focused on the design of object-oriented software. That is a more general problem than management automation. A computer game, for example, is a piece of software that can be described using UML, but it is not a management automation system. There is also SysML, a slightly twisted version of UML, which is marketed as a system analysis tool. However, it didn’t go far from it’s predecessor. BPML is focused on business processes and is almost entirely ignorant about goals, which the processes shall achieve. There are methodologies created to model automation in technical systems like SCADA, but they are too low-level to describe multi-level socio-economical systems full of fuzzy human interactions. The list goes on and on.

The key differentiator of GOMA modeling is in its focus on management automation. The terms used in GOMA models are management automation terms. They naturally fit the problem domain and were not pulled from other areas. In GOMA modeling, the world consists of Elements that are in Relations to each other (system theory approach). Elements can form a management System and start playing specific management Roles (human--a worker, client, or supplier; Hummer--a product or tool; and so on). System management is done via execution of management Functions. The work of the functions is determined by input and output Information Flows (or just Information). Automation is done by the integration of various Components into Management Automation Systems. The Components are responsible for the execution of Management Functions and the enhancement or replacement of manual work of Decision Makers. As you can see, there are no such abstract things like classes, actors, use cases, and other abstractions, which are quite far from real life.

  • Scaling. Scaling is the ability to change the level of abstractions from a higher-level description of entire organization down to a low-level description of individual workers and elements. To scale up, models shall become more inclusive and minor details shall disappear. To scale down, models shall be restricted to a smaller area and show it with fine-granular details. While changing abstraction levels, all external relations between a scaled part of the model and the rest shall be preserved.

In existing methodologies scaling is either not possible, or supported only by one main dimension. For instance, the IDEF0 model is focused on functional description and allows to easily enlarge or break down functional blocks. UML is focused on software and allows to enlarge or break down software implementation using packages and components. However, scaling by other modeling dimensions is nearly possible.

In GOMA, modeling scalability is possible by the following supported modeling dimensions:
    • Scaling of system and environment structure is supported via context hierarchy.
    • Scaling of element roles is done via hierarchical group roles. One such role represents a “superhuman” who can do the work of an entire organization, department or group, depending on selected abstraction level.
    • Functional scaling is done via functional groups, which represent coarse-granular functional blocks, similar to IDEF0.
    • Information scaling is done through information hierarchies. Goals are broken down into subgoals. Basic facts (observations) are aggregated into higher-level facts (interpretations).
    • And, finally, scaling of automation, similar to the real world, is done as a hierarchical decomposition of automation systems into subsystems and then down to elementary components.

  • Synthesis - matching the model to the real world. Analysis, performed in system modeling, forces us to simplify and break down complex things into much smaller and simpler abstractions. However, with that simplification we can often miss something important or unintentionally distort the reality. If an incorrect model goes into development it results in a poor automation system. We can constantly see many big or small failures that have their root cause in poor models. To avoid that, before developing something we shall take our model and recreate a whole from abstract pieces. Then we shall see how it matches the reality. If there is a discrepancy, we shall fix it and try it again. That operation is called Synthesis and is the opposite to Analysis. To do that, GOMA modeling has few interesting capabilities:
    • Synthesis of system structure is performed through assignment of responsibilities/roles to elements in a real system. That way we can show how one logical system structure can accommodate multiple physical structures.
    • Synthesis of management functions can be done using the OODA Loop model. Work of any Active Element can be considered as information processing in 4 distinct states: Observe, Orient, Decide, Act.
    • Synthesis of management goals is performed through linking individual goals to their higher-level organization goals. Then we can match higher-level goals in our model to the real business goals and objectives of the modeled organization.

  • Verification. The larger and more complex a model, the more important it is to verify and easily correct it. If the verification is not supported by the methodology, then automation can’t help. In that case the verification process depends entirely on human skills and judgement. This is the main factor of fast growth in modeling complexity. When the number of model elements is within a few tens, manual verification is quite simple. When numbers go up to a few hundreds, that work requires a significant amount of effort. For models with thousands of elements, manual verification within a practical time-frame is nearly possible, and there is a big chance of critical mistakes.

Unfortunately, classical methodologies have serious issues with verifications. In many cases it is limited to simple checks for cycle references and the presence or absence of specific references or properties. There are nearly no formal ways to verify models from a meaning/semantic point of view.

In GOMA modeling, besides simple structural checks, there are many semantic verifications. Here are just few of those:
  • Verification of goal breakdown completeness, performed top-to-bottom -- check all subgoals listed for a goal
  • Verification of goal breakdown completeness, performed bottom-up -- check all super-goals mentioned for a specific goal
  • Verification of function breakdown completeness, performed top-to-bottom and bottom-up
  • Verification of function breakdown completeness, performed using OODA Loop -- check planned actions, check interpretation facts that are required to formulate goals and plans, check elementary observations used to formulate interpretations
  • Verification of correspondence between information flows and functions and vis versa -- check that each function (except Act) produces at least 1 information flow, check that each function (except observation) consumes at least 1 information flow, check that each information flow is consumed and produced by at least 1 function
  • Verification of information interdependencies -- to formulate goals there must be super-goals and facts, facts must be based on elementary observations, goals must lead to actions
  • Active elements must be responsible for reaching specific goals -- must contribute to overall organization achievements, perform their OODA Loop and all functions associated with it, obtain and generate all necessary information flows, and so on

  • Completeness. If we list everything that a real management system consists of, we can get the following:
    • Elements to compose a system and environment (The elements can produce and consume information, act as destinations for actions, and may have relations with each other.)
    • Functions executed by management system in order to perform its work and achieve organizational goals
    • Data, or information, used by a management system to function, and…
    • Automations required to enhance or replace manual work of human decision makers (The automations can represent a newly developed management automation system, or existing systems which our system shall integrate with.)

If we compare existing methodologies by their completeness, we can see that not all of them are able to represent the entire system. For example, the popular SADT includes only two models -- one for activity (functions) and one for data (information). In the world structure, automation tools are not completely represented . Only few methodologies, mostly those which are based on UML, can considered as “complete.”

GOMA models contain not only all required elements but also all possible relations between them--links between elements, data, functions, elements and data, data and functions, and so on.

  • Clarity. As it was mentioned above, GOMA uses terminology that naturally represents the management automation. The modeler doesn’t need to think hard to figure out what class, object, actor, or use case, for example, shall be used in his model. Information, element, function, automation--that’s the list of key terms used in GOMA models. As we can see, they perfectly match everything that automation specialists have to deal with. The naturalness of GOMA concepts is the key to clarity and ease of understanding not just for analysts but, especially, for model users.

On the other hand, there is a modeled domain with its own special terminology. Sometimes terms used in those domains may be unknown to automation specialists. Or even worse, they may not have a standard meaning, and can be interpreted by different people differently. Obviously, situations like that often lead to a mess. Digging through such models becomes an extremely difficult and unpleasant task. Pretty soon they turn into expensive piles of paper or garbage on a computer disk.

In GOMA modeling there is a special conceptual or semantic model, which describes all key concepts, terms, what they mean, and how they relate to each other and other model elements. In GOMA, any modeling process starts from a glossary definition and semantic structure.

  • Tooling. The majority of modeling methodologies used today are relatively old. They were created primarily for manual modeling, and automation tools were developed after the fact. That approach introduced serious limitations into the modeling process. First of all, there is a practical limit that any paper model can have. Second, old modeling techniques were not optimized for computer processing. Because of that, the models tend to be small and ugly, and the computerized modeling process is inconvenient and limited. Automation of manual modeling methodology cannot solve all fundamental problems there.

Since the beginning, GOMA modeling was created for automated tooling. One GOMA modeling tool is being developed in parallel with the methodology with the methodology and tool influencing each other. It even reaches the point of being unclear with what is primary and what is secondary. Manual modeling, of course, is possible in GOMA. However, besides just academical interest, it is not considered from practical point of view.

GOMA modeling probably has more features that are worth mentioning here. If something else comes up, I will definitely write about it in my next posts. So...watch the blog and keep reading.

See you later!

32 comments:

  1. Nice blog. Thank you for sharing. The information you shared is very effective for learners I have got some important suggestions from it.Best Embedded Systems Training in Chennai | C & C++ Training Institute in Chennai | No.1 Embedded Training in Chennai

    ReplyDelete
  2. This comment has been removed by the author.

    ReplyDelete
  3. Wow, superb blog structure! How lengthy have you been blogging for? you made blogging glance easy. The entire glance of your website is magnificent, as neatly as the content material! Excellent Photoshop Training Institute in Chennai | Best Multimedia Training Institute in Velachery

    ReplyDelete
  4. The best thing is that your blog really informative thanks for your great information! I have got some important suggestions from it. Multimedia Technical Boot Camp in Chennai | Best Vacation Class in Guindy

    ReplyDelete
  5. РугулярноС ΠΏΠΎΠΏΠΎΠ»Π΅Π½Π΅Π½ΠΈΠ΅ Π½Π° рСсурсС ΠΏΠΎΠ·Π²ΠΎΠ»ΠΈΡ‚ Π’Π°ΠΌ ΡΠ»Π΅Π΄ΠΈΡ‚ΡŒ Π·Π° ΠΊΡ€ΡƒΡ‚Ρ‹ΠΌΠΈ ΠΌΠΎΠ΄Π½Ρ‹ΠΌΠΈ пополСнСниями нашСго ΠΈΠ½Ρ‚Π΅Ρ€Π½Π΅Ρ‚-ΠΌΠ°Π³Π°Π·ΠΈΠ½Π°, Π½Π°ΠΉΡ‚ΠΈ Ρ‚ΠΎ, Ρ‡Ρ‚ΠΎ Π²Π°ΠΌ Π½ΡƒΠΆΠ½ΠΎ ΠΈ постоянно Π±Ρ‹Ρ‚ΡŒ Π² курсС самых Π½ΠΎΠ²Ρ‹Ρ… Ρ‚Π΅Π½Π΄Π΅Π½Ρ†ΠΈΠΉ ΠΌΠΎΠ΄Ρ‹. Π’ ΠΌΠ°Π³Π°Π·ΠΈΠ½Π΅ Ρ‚Ρ‹ ΠΎΠ±Π½Π°Ρ€ΡƒΠΆΠΈΡˆΡŒ классныС соврСмСнныС сумлочки ΠΈΠ· настоящСй ΠΊΠΎΠΆΠΈ Ρ€Π°Π·Π»ΠΈΡ‡Π½Ρ‹Ρ… Ρ†Π²Π΅Ρ‚ΠΎΠ² Π½Π° любой вкус. Π£ нас ТСнскиС сумки ΠΈΠ· ΠΊΠΎΠΆΠΈ Ρ‚Π°ΠΊΠΆΠ΅ Π²Ρ‹ смоТСтС Π²Ρ‹Π±Ρ€Π°Ρ‚ΡŒ сумочку люксового Ρ„ΠΎΡ€ΠΌΠ°Ρ‚Π° ΠΈΠ»ΠΈ ΠΏΠΎΠ²ΡΠ΅Π΄Π½Π΅Π²Π½ΡƒΡŽ, сумки Π½Π° ΠΊΠΎΠΆΠ°Π½ΠΎΠΌ Ρ€Π΅ΠΌΠ½Π΅ ΠΈΠ»ΠΈ Ρ†Π΅ΠΏΠΈΠΈ Π΅Ρ‰Π΅ ΠΊΡƒΠΏΠΈΡ‚ΡŒ сумку ΠΈΠ· ΠΊΠΎΠΆΠΈ для повсСднСвных ΠΈΠ»ΠΈ Π΄Π΅Π»ΠΎΠ²Ρ‹Ρ… бизнСс встрСч.

    ReplyDelete
  6. ΠŸΡ€ΠΈΡ€ΠΎΠ΄Π½Ρ‹Π΅ ΠΊΠ°Ρ‚Π°ΠΊΠ»ΠΈΠ·ΠΌΡ‹ ΠΈΠ»ΠΈ Ρ€ΠΈΡ‚ΡƒΠ°Π»ΡŒΠ½Ρ‹Π΅ ΠΆΠ΅Ρ€Ρ‚Π²ΠΎΠΏΡ€ΠΈΠ½ΠΎΡˆΠ΅Π½ΠΈΡ со Π²Ρ€Π΅ΠΌΠ΅Π½Π΅ΠΌ обосновали Ρ‚ΠΎΡ‡Π½ΠΎΠ΅ ΠΈΠ½Ρ‚Π΅Ρ€ΠΏΡ€Π΅Ρ‚Π°Ρ†ΠΈΡŽ ΠΎΠ±Π½Π°Ρ€ΡƒΠΆΠ΅Π½Π½ΠΎΠ³ΠΎ. Π’Π°ΠΆΠ½Π΅ΠΉΡˆΠΈΠ΅ срСдства гадания ΠΎΠ±Ρ€Π°Π·ΠΎΠ²Π°Π»ΠΈΡΡŒ тысячСлСтия Ρ‚ΠΎΠΌΡƒ Π½Π°Π·Π°Π΄ Π΄ΠΎ нашСй эры. Π“Π°Π΄Π°Π½ΠΈΠ΅ двойняшки ΠΎΠ½Π»Π°ΠΉΠ½ значится максимально Ρ‚ΠΎΡ‡Π½Ρ‹ΠΌ дСйствиСм ΠΎΠΏΡ€Π΅Π΄Π΅Π»ΠΈΡ‚ΡŒ ΡΡƒΠ΄ΡŒΠ±Ρƒ Ρ‡Π΅Π»ΠΎΠ²Π΅ΠΊΠ°.

    ReplyDelete
  7. Π‘ΠΎΠ»ΠΈΠ΄Π½Ρ‹ΠΉ ΠΈ ΠΏΡ€ΠΎΠ²Π΅Ρ€Π΅Π½Π½Ρ‹ΠΉ ΠΏΡ€ΠΎΠ΄Π°Π²Π΅Ρ† всСгда смоТСт ΠΏΡ€Π΅Π΄Π»ΠΎΠΆΠΈΡ‚ΡŒ многочислСнный ассортимСнт кСрамичСского покрытия для Π²Π°Π½Π½ΠΎΠΉ. Π‘Ρ€Π΅Π½Π΄ Π‘ΠΎΡ‚Π½ΠΈ.Ρ€Ρƒ ΠΏΡ€ΠΎΠ΄Π°Π΅Ρ‚ geotiles ΠΊΡƒΠΏΠΈΡ‚ΡŒ ΡƒΠΆΠ΅ ΡΠ²Ρ‹ΡˆΠ΅ 10 Π»Π΅Ρ‚.

    ReplyDelete
  8. Π—Π°Π±Ρ€ΠΎΠ½ΠΈΡ€ΠΎΠ²Π°Ρ‚ΡŒ Ρ‚Ρ€Π΅Π±ΡƒΠ΅ΠΌΡƒΡŽ сумму Π½Π° ΠΊΠ°Ρ€Ρ‚ΠΎΡ‡Π½Ρ‹ΠΉ счСт Π½Π° ΡƒΠ΄ΠΈΠ²Π»Π΅Π½ΠΈΠ΅ просто. Онлайн Π·Π°ΠΉΠΌ Ρ‡Π΅Ρ€Π΅Π· систСму ΠΊΠΎΠ½Ρ‚Π°ΠΊΡ‚ – это Π½Π°Π΄Π΅ΠΆΠ½Ρ‹ΠΉ Π²Π°Ρ€ΠΈΠ°Π½Ρ‚ Π²Π·ΡΡ‚ΡŒ Π½Π°Π»ΠΈΡ‡Π½ΠΎΡΡ‚ΡŒ Π² ΠΌΠΈΠ½ΠΈΠΌΠ°Π»ΡŒΠ½Ρ‹Π΅ сроки. Π’ΠΎΠΏΠΎΠ²Ρ‹ΠΉ сайт Π²Ρ‹Π±ΠΎΡ€Π° коммСрчСских ΠΏΡ€ΠΎΠ΄ΡƒΠΊΡ‚ΠΎΠ² Ρ€Π°Π·Ρ€Π΅ΡˆΠ°Π΅Ρ‚ ΠΏΠΎΠ»ΡƒΡ‡ΠΈΡ‚ΡŒ Π½Π΅ΠΎΠ±Ρ…ΠΎΠ΄ΠΈΠΌΡ‹ΠΉ Π·Π°ΠΉΠΌ.

    ReplyDelete
  9. КомплСкс ΠΎΠΏΠ΅Ρ€Π°Ρ†ΠΈΠΉ, Π½Π°ΠΏΡ€Π°Π²Π»Π΅Π½Π½Ρ‹Ρ… Π½Π° ΠΏΡ€Π΅Π΄Π²ΠΈΠ΄Π΅Π½ΠΈΠ΅ Π±ΡƒΠ΄ΡƒΡ‰Π΅Π³ΠΎ, Π½Π°Π·Ρ‹Π²Π°ΡŽΡ‚ Π³Π°Π΄Π°Π½ΠΈΠ΅. Π‘Π²Π΅Ρ€Ρ…ΡŠΠ΅ΡΡ‚Π΅ΡΡ‚Π²Π΅Π½Π½Ρ‹Π΅ силы ΠΈ ΠΌΠ½ΠΎΠ³ΠΎΠΎΠ±Ρ€Π°Π·Π½Ρ‹Π΅ условия вороТСния Π½Π°ΡƒΡ‡Π½ΠΎ Π½Π΅ Π΄ΠΎΠΊΠ°Π·Π°Π½Ρ‹, ΠΏΡ€ΠΈ Ρ‚ΠΎΠΌ Ρ€Π°Π·Π»ΠΈΡ‡Π½Ρ‹Π΅ люди вСрят Π² это. Π’Π°Ρ€ΠΎΠ»ΠΎΠ³ ΠΎΡ‚Π·Ρ‹Π²Ρ‹ - это Π½Π°Π΄Π΅ΠΆΠ½Ρ‹ΠΉ порядок ΡƒΠ·Π½Π°Ρ‚ΡŒ ΡΡƒΠ΄ΡŒΠ±Ρƒ с ΠΏΡ€ΠΈΠΌΠ΅Π½Π΅Π½ΠΈΠ΅ΠΌ Ρ€Π°Π·Π½ΠΎΠΎΠ±Ρ€Π°Π·Π½Ρ‹Ρ… Π°Ρ‚Ρ€ΠΈΠ±ΡƒΡ‚ΠΎΠ² ΠΈ ΠΌΠ΅Ρ‚ΠΎΠ΄ΠΎΠ².

    ReplyDelete
  10. ΠŸΡ€ΠΎΠΉΠ΄ΠΈΡ‚Π΅ Ρ€Π΅Π³ΠΈΡΡ‚Ρ€Π°Ρ†ΠΈΡŽ Π½Π° ΠΏΠ»Π°Ρ‚Ρ„ΠΎΡ€ΠΌΠ΅ ΠΈ ΡƒΠ²ΠΈΠ΄ΠΈΡ‚Π΅ приятныС вознаграТдСния Π² ΡƒΡ‡Π΅Ρ‚Π½ΠΎΠΉ записи. Π”ΠΎΠΏΠΎΠ»Π½ΠΈΡ‚Π΅Π»ΡŒΠ½Ρ‹ΠΉ счСт даст Π²ΠΎΠ·ΠΌΠΎΠΆΠ½ΠΎΡΡ‚ΡŒ сгрСсти ΠΌΠ½ΠΎΠ³ΠΎ Π±Π°Π±ΠΎΠΊ. Π’Π°ΠΆΠ½ΠΎ Π½Π΅ Π·Π°Π±Ρ‹Π²Π°Ρ‚ΡŒ, Ρ‡Ρ‚ΠΎ ΠΏΡ€ΠΎΠ΅ΠΊΡ‚ ΠΊΠ°Π·ΠΈΠ½ΠΎ Ρ… ΠΊΠ°Π·ΠΈΠ½ΠΎ ΠΎΠ½Π»Π°ΠΉΠ½ ΠΎΡ„ΠΈΡ†ΠΈΠ°Π»ΡŒΠ½Ρ‹ΠΉ ΠΏΡ€Π΅Π΄Π»Π°Π³Π°Π΅Ρ‚ своим ΠΏΠΎΠ»ΡŒΠ·ΠΎΠ²Π°Ρ‚Π΅Π»ΡΠΌ ΡΠΏΠ΅Ρ†ΠΈΠ°Π»ΡŒΠ½Ρ‹Π΅ бонусы.

    ReplyDelete
  11. Π Π°Π·Π²ΠΈΡ‚ΠΈΠ΅ соврСмСнных Ρ‚Π΅Ρ…Π½ΠΎΠ»ΠΎΠ³ΠΈΠΉ позволяСт ΠΈΠ½Ρ‚Π΅Ρ€Π°ΠΊΡ‚ΠΈΠ²Π½Ρ‹ΠΌ сайтам ΠΊΠΎΠ½ΠΊΡ€Π΅Ρ‚Π½ΠΎ ΠΎΠΏΡ‚ΠΈΠΌΠΈΠ·ΠΈΡ€ΠΎΠ²Π°Ρ‚ΡŒ ΠΏΡ€Π΅Π΄Π»Π°Π³Π°Π΅ΠΌΡ‹Π΅ сСрвисы. Π˜Π½Ρ‚Π΅Ρ€Π½Π΅Ρ‚-ΠΈΠ³Ρ€Ρ‹ ΠΎΠ±Ρ€Π΅Π»ΠΈ ΡΡƒΡ‰Π΅ΡΡ‚Π²Π΅Π½Π½ΡƒΡŽ Ρ€Π°ΡΠΏΡ€ΠΎΡΡ‚Ρ€Π°Π½Π΅Π½Π½ΠΎΡΡ‚ΡŒ ΠΏΠΎ всСму ΠΌΠΈΡ€Ρƒ. Казино Ρ… сайт – Π²ΠΎΡΠΏΠΎΠ»ΡŒΠ·ΡƒΠΉΡ‚Π΅ΡΡŒ прСимущСством Π·Π°Ρ‰ΠΈΡ‰Π΅Π½Π½ΠΎΠΉ ΠΈΠ³Ρ€Ρ‹ ΠΈ Π·Π°Ρ€Π°Π±ΠΎΡ‚Π°ΠΉΡ‚Π΅ сущСствСнныС Π±Π°Π±ΠΊΠΈ.

    ReplyDelete
  12. Волько лишь Π½Π° ΠΏΠΎΡ€Ρ‚Π°Π»Π΅ casino mister bit ΠΊΠ»ΠΈΠ΅Π½Ρ‚Ρ‹ ΠΎΡ‡Π΅Π½ΡŒ просто ΡΠΊΠ°Ρ‡Π°ΡŽΡ‚ Π»ΡŽΠ±ΠΈΠΌΡƒΡŽ ΠΈΠ½Ρ‚Π΅Ρ€Π°ΠΊΡ‚ΠΈΠ²Π½ΡƒΡŽ ΠΈΠ³Ρ€ΡƒΡˆΠΊΡƒ для Ρ€Π°Π·Π²Π»Π΅Ρ‡Π΅Π½ΠΈΠΉ. ΠŸΡ€ΠΈΡ…ΠΎΠ΄Ρ Π² ΠΈΠ½Ρ‚Π΅Ρ€Π°ΠΊΡ‚ΠΈΠ²Π½Ρ‹ΠΉ ΠΊΠ»ΡƒΠ±, ΠΏΠΎΠ»ΡŒΠ·ΠΎΠ²Π°Ρ‚Π΅Π»ΡŒ ΠΌΠΎΠΆΠ΅Ρ‚ ΠΎΠΊΡƒΠ½ΡƒΡ‚ΡŒΡΡ Π² Π½Π΅Π·Π°Π±Ρ‹Π²Π°Π΅ΠΌΡ‹Π΅ Π°Π²Π°Π½Ρ‚ΡŽΡ€Ρ‹. Π˜Π³Ρ€Π°Ρ‚ΡŒΡΡ Π² Π³Ρ€ΡƒΠΏΠΏΠ΅ Π΅Π΄ΠΈΠ½ΠΎΠΌΡ‹ΡˆΠ»Π΅Π½Π½ΠΈΠΊΠΎΠ² Π² Π·Π½Π°Ρ‡ΠΈΡ‚Π΅Π»ΡŒΠ½ΠΎΠΉ стСпСни ΡƒΠ²Π»Π΅ΠΊΠ°Ρ‚Π΅Π»ΡŒΠ½Π΅Π΅, Ρ‡Π΅ΠΌ сам ΠΏΠΎ сСбС Π΄ΠΎΠΌΠ°.

    ReplyDelete
  13. ΠœΠ½ΠΎΠΆΠ΅ΡΡ‚Π²ΠΎ ΡƒΠ·ΠΎΡ€ΠΎΠ² ΠΈ Ρ€Π°Π·ΠΌΠ΅Ρ€ΠΎΠ². Π¦Π΅Π½ΠΎΠ²ΠΎΠΉ Π΄ΠΈΠ°ΠΏΠ°Π·ΠΎΠ½ ΠΏΠ»ΠΈΡ‚ΠΊΠΈ Ρ‚ΠΎΠΆΠ΅ отличаСтся. ΠšΠ°Ρ„Π΅Π»ΡŒ ΠΏΠ»ΠΈΡ‚ΠΊΠ° porto rose dual gres ΠΈΠ·Π³ΠΎΡ‚Π°Π²Π»ΠΈΠ²Π°ΡŽΡ‚ Π² большом количСствС, Π° всякая ΠΊΠΎΠ½Ρ‚ΠΎΡ€Π° стрСмится Π²Ρ‹ΡΡ‚Π°Π²ΠΈΡ‚ΡŒ свой Π½Π΅ΠΏΠΎΠ²Ρ‚ΠΎΡ€ΠΈΠΌΡ‹ΠΉ ΠΏΡ€ΠΎΠ΅ΠΊΡ‚.

    ReplyDelete
  14. Π’ΠΎΡ‚ Π΅Ρ‰Ρ‘ нСсколько Π³Π»Π°Π²Π½Ρ‹Ρ… ΠΏΡ€ΠΈΠΎΡ€ΠΈΡ‚Π΅Ρ‚ΠΎΠ² http://environmental-physiology-research.hk/home.php?mod=space&uid=51478, ΠΊΠΎΡ‚ΠΎΡ€Ρ‹ΠΌΠΈ ΠΎΠ±Π»Π°Π΄Π°Π΅Ρ‚ кСрамичСская ΠΏΠ»ΠΈΡ‚ΠΊΠ°. ΠšΠ΅Ρ€Π°ΠΌΠΎΠ³Ρ€Π°Π½ΠΈΡ‚ Π΄Π΅Π»Π°ΡŽΡ‚ ΠΈΡΠΊΠ»ΡŽΡ‡ΠΈΡ‚Π΅Π»ΡŒΠ½ΠΎ ΠΈΠ· ΠΏΡ€ΠΈΡ€ΠΎΠ΄Π½Ρ‹Ρ… исходников. ΠšΠ΅Ρ€Π°ΠΌΠΈΠΊΡƒ Π²ΠΎΠ·ΠΌΠΎΠΆΠ½ΠΎ ΠΌΠΎΠ½Ρ‚ΠΈΡ€ΠΎΠ²Π°Ρ‚ΡŒ Π² Π·Π°Π»Π°Ρ… Π·Π°Π²Π΅Π΄Π΅Π½ΠΈΠΉ общСствСнного питания, Π² ΡˆΠΊΠΎΠ»Π°Ρ… ΠΈ Π΄ΠΎΡˆΠΊΠΎΠ»ΡŒΠ½Ρ‹Ρ… ΡƒΡ‡Π΅Π±Π½Ρ‹Ρ… завСдСниях. НСтоксичСский ΠΌΠ°Ρ‚Π΅Ρ€ΠΈΠ°Π», ΡΠΎΠ²Π΅Ρ€ΡˆΠ΅Π½Π½ΠΎ бСзопасСн для ΠΏΡ€ΠΎΠΆΠΈΠ²Π°ΡŽΡ‰ΠΈΡ….

    ReplyDelete
  15. Π‘ΠΎΡΡ€Π΅Π΄ΠΎΡ‚ΠΎΡ‡ΡŒΡ‚Π΅ΡΡŒ Π½Π΅ Ρ‚ΠΎΠ»ΡŒΠΊΠΎ Π½Π° кСрамичСской ΠΏΠ»ΠΈΡ‚ΠΊΠ΅ иностранного производства, Π½ΠΎ ΠΈ Π½Π° наши Π²ΠΈΠ΄Ρ‹. Выбирая качСствСнный стройматСриал ΠΊΠ°ΠΊ Π½Π°ΠΏΡ€ΠΈΠΌΠ΅Ρ€ http://portal.prolisok.org/index.php?subaction=userinfo&user=axonige Π² любом случаС придСтся Ρ€Π°ΡΡΠΌΠΎΡ‚Ρ€Π΅Ρ‚ΡŒ мноТСствСнноС количСство ΠΌΠ°Ρ‚Π΅Ρ€ΠΈΠ°Π»ΠΎΠ². ΠšΠ΅Ρ€Π°ΠΌΠΈΡ‡Π΅ΡΠΊΠ°Ρ прСвосходно ΠΏΠΎΠ΄ΠΎΠΉΠ΄Π΅Ρ‚ ΠΊ ΠΊΠ°ΠΆΠ΄ΠΎΠΌΡƒ ΠΈΠ½Ρ‚Π΅Ρ€ΡŒΠ΅Ρ€Ρƒ. ΠžΠΏΡ‚ΠΈΠΌΠ°Π»ΡŒΠ½Ρ‹ΠΉ Π²Ρ‹Π±ΠΎΡ€ настСнного покрытия способСн ΠΎΠ±Π»Π°Π³ΠΎΡ€ΠΎΠ΄ΠΈΡ‚ΡŒ ΠΊΠ°ΠΆΠ΄ΡƒΡŽ ΠΊΡƒΡ…Π½ΡŽ ΠΈΠ»ΠΈ санузСл.

    ReplyDelete
  16. Доставка выполняСтся ΠΊΠ°ΠΊ Ρ€Π°Π· Π½Π° Π΄Π°Ρ‚Ρƒ Π·Π°ΠΊΠ°Π·Π°. ΠšΡƒΠΏΠΈΡ‚ΡŒ Π΄Π°Ρ€Ρ‹ моря http://wiki.schellackplatten-forum.de/index.php?title=%D0%9F%D1%80%D0%B8%D0%BE%D0%B1%D1%80%D0%B5%D1%82%D0%B0%D0%B9%D1%82%D0%B5%20%D0%BC%D0%BE%D0%BB%D0%BB%D1%8E%D1%81%D0%BA%D0%BE%D0%B2%20%D1%83%20%D0%BF%D1%80%D0%BE%D0%B2%D0%B5%D1%80%D0%B5%D0%BD%D0%BD%D1%8B%D1%85%20%D0%BF%D0%BE%D1%81%D1%82%D0%B0%D0%B2%D1%89%D0%B8%D0%BA%D0%BE%D0%B2%20%D0%B2%20%D0%BB%D1%83%D1%87%D1%88%D0%B5%D0%BC%20%D0%B8%D0%BD%D1%82%D0%B5%D1%80%D0%BD%D0%B5%D1%82-%D0%BC%D0%B0%D0%B3%D0%B0%D0%B7%D0%B8%D0%BD%D0%B5%20%D0%B4%D0%B0%D1%80%D0%BE%D0%B2%20%D0%BC%D0%BE%D1%80%D1%8F%20%C2%AB%D0%9A%D1%80%D0%B0%D1%81%D0%BD%D1%8B%D0%B9%20%D0%B6%D0%B5%D0%BC%D1%87%D1%83%D0%B3%C2%BB ΠΌΠΎΠΆΠ½ΠΎ Π² Ρ€ΠΎΠ·Π½ΠΈΡ†Ρƒ ΠΈΠ»ΠΈ ΠΌΠ΅Π»ΠΊΠΈΠΌ ΠΎΠΏΡ‚ΠΎΠΌ. Π‘ Ρ†Π΅Π»ΡŒΡŽ оформлСния Π·Π°ΠΊΠ°Π·Π° Π½Π° ΠΌΠΎΡ€Π΅ΠΏΡ€ΠΎΠ΄ΡƒΠΊΡ‚Ρ‹ Π² ΡΠΎΠΎΡ‚Π²Π΅Ρ‚ΡΡ‚Π²ΡƒΡŽΡ‰Π΅ΠΌ числС Π½Π΅ΠΎΠ±Ρ…ΠΎΠ΄ΠΈΠΌΠΎ ΠΎΠ±Ρ€Π°Ρ‚ΠΈΡ‚ΡŒΡΡ ΠΊ ΠΌΠ΅Π½Π΅Π΄ΠΆΠ΅Ρ€Ρƒ ΠΈΠ»ΠΈ ΠΎΡ„ΠΎΡ€ΠΌΠΈΡ‚ΡŒ ΡƒΠ΄Π°Π»Π΅Π½Π½Ρ‹ΠΉ Π·Π°ΠΊΠ°Π· ΠΈΠΌΠ΅Π½Π½ΠΎ Π½Π° сайтС «ΠšΡ€Π°ΡΠ½Ρ‹ΠΉ ΠΆΠ΅ΠΌΡ‡ΡƒΠ³».

    ReplyDelete
  17. Π›ΡŽΠ±ΠΈΡ‚ Π»ΠΈ мСня ΠΌΡƒΠΆΡ‡ΠΈΠ½Π° Π³Π°Π΄Π°Π½ΠΈΠ΅ Π½Π° ΠΊΠ°Ρ€Ρ‚Π°Ρ… Π’Π°Ρ€ΠΎ позволяСт ΡƒΠ²ΠΈΠ΄Π΅Ρ‚ΡŒ, Ρ‡Ρ‚ΠΎ вас ΠΆΠ΄Π΅Ρ‚ Π² блиТайшСм Π²Ρ€Π΅ΠΌΠ΅Π½ΠΈ. ΠŸΠΎΠΏΡ‹Ρ‚ΠΊΠ° Ρ€Π°ΡΡΠΌΠΎΡ‚Ρ€Π΅Ρ‚ΡŒ грядущиС явлСния Π½Π΅ΠΏΡ€Π΅Ρ€Ρ‹Π²Π½ΠΎ ΠΌΠ°Π½ΠΈΠ» Ρ‡Π΅Π»ΠΎΠ²Π΅ΠΊΠ°. Всякий ΠΌΠ΅Ρ‡Ρ‚Π°Π΅Ρ‚ ΠΏΡ€Π΅Π΄ΡƒΠ³Π°Π΄Π°Ρ‚ΡŒ своС Π±ΡƒΠ΄ΡƒΡ‰Π΅Π΅ ΠΈ воспринимаСт ΠΎΠΏΡ€Π΅Π΄Π΅Π»Π΅Π½Π½Ρ‹Π΅ способы Π²ΠΎΡ€ΠΎΠΆΠ±Ρ‹ Π±ΠΎΠ»Π΅Π΅ дСйствСнными.

    ReplyDelete
  18. Really an amazing blog with useful information you have shared. Thanks for sharing such an nice article..
    Final Year Project Center in Chennai | Final Year Projects in Velachery

    ReplyDelete
  19. I am really happy to read your blog. Your article is awesome with impressive content. Keep updating..
    IELTS Test Center in Chennai | IELTS Test Center in Velachery

    ReplyDelete
  20. Nice post... Really you are done a wonderful job. Thanks for sharing such wonderful information with us. Please keep on updating...
    MBA Project Center in Chennai | MBA Projects in Velachery

    ReplyDelete
  21. "I visited your blog you have shared amazing information, i really like the information provided by you, You have done a great work. I appreciate your work.
    Thanks"

    ReplyDelete
  22. Alltechzsolutions Pvt ltd java Full Stack Developer Training in Chennai
    Technology is growing a rapid pace. In such a situation, developers can no longer be complacent with developing, but should catch up with the cropping trends in web development in a regular basis. They have to keep updating their skills from ground level from designing to the actual deployment. This ongoing course of action gives way to a new role of developers known as Full Stack Developers.
    Being advanced development professionals, full stack developers are capable of framing and building challenging and appealing websites and applications. They are multi-talented professionals who have proficiency in working on all the aspects of development ranging from front end to backend. They also take care of database and can even move towards dealing with debugging and testing applications. Do you want to a well qualified Full Stack professional? Then it’s time to enroll in Chennai's Best JAVA Full Stack Training Institute.Alltechzsolutions Here you will learn all the important concepts from the scratch.We offer both offline and online courses with well experienced Trainers

    ReplyDelete
  23. Alltechzsolutions provides 100% real-time, practical and placement focused CCNA training in Chennai. Our CCNA course concentrates from basic level training to advanced level training. Our CCNA® training in completely focused to get placement in MNC in Chennai and certification on CCNA after completion of our course. Our team of CCNA trainers are CCNA certified professionals with more real-time experience in live projects. Our CCNA® Course syllabus is enough for anyone who wants to get CCNA certification which meets industry expectations. In our course plan, you will learn Networking concepts,OSI – Model,TCP/IP Model & Ipv4 Addressing, with practical exercises and live examples.Alltechzsolutions offer both off line and online courses.

    ReplyDelete