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!
Thanks for your great information. Its interesting and informative,keep sharing your valuable Blog.
ReplyDeleteAndroid Training institute in Chennai | IOS Training Institute in Chennai | Mobile Application Training Institute in Chennai
The best thing is that your blog really informative thanks for your great information!
ReplyDeletecashew nuts suppliers and exporters in dubai
onion suppliers and exporters in dubai
A4 paper copier suppliers and exporters in dubai
potato suppliers and exporters in dubai
spices&grains suppliers and exporters in dubai
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
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteThanks for posting your excellent article..
ReplyDeleteNo.1 VLSI Project Center in Chennai | No.1 VLSI Project Center in Velachery
really i enjoyed your post..thanks for updating your bog..
ReplyDeleteNo.1 IOS Training Institute in Velachery | Best Android Training Institute in Velachery | Core Java Training Institute in Chennai
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
ReplyDeleteI am happy to read your blog,its really useful for me..
ReplyDeleteImage Processing Project Center in Chennai | Image Processing Project Center in Velachery
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
ReplyDeletethanks for giving that type of information. ielts coaching in gurgaon
ReplyDeleteΠ ΡΠ³ΡΠ»ΡΡΠ½ΠΎΠ΅ ΠΏΠΎΠΏΠΎΠ»Π΅Π½Π΅Π½ΠΈΠ΅ Π½Π° ΡΠ΅ΡΡΡΡΠ΅ ΠΏΠΎΠ·Π²ΠΎΠ»ΠΈΡ ΠΠ°ΠΌ ΡΠ»Π΅Π΄ΠΈΡΡ Π·Π° ΠΊΡΡΡΡΠΌΠΈ ΠΌΠΎΠ΄Π½ΡΠΌΠΈ ΠΏΠΎΠΏΠΎΠ»Π΅Π½Π΅Π½ΠΈΡΠΌΠΈ Π½Π°ΡΠ΅Π³ΠΎ ΠΈΠ½ΡΠ΅ΡΠ½Π΅Ρ-ΠΌΠ°Π³Π°Π·ΠΈΠ½Π°, Π½Π°ΠΉΡΠΈ ΡΠΎ, ΡΡΠΎ Π²Π°ΠΌ Π½ΡΠΆΠ½ΠΎ ΠΈ ΠΏΠΎΡΡΠΎΡΠ½Π½ΠΎ Π±ΡΡΡ Π² ΠΊΡΡΡΠ΅ ΡΠ°ΠΌΡΡ Π½ΠΎΠ²ΡΡ ΡΠ΅Π½Π΄Π΅Π½ΡΠΈΠΉ ΠΌΠΎΠ΄Ρ. Π ΠΌΠ°Π³Π°Π·ΠΈΠ½Π΅ ΡΡ ΠΎΠ±Π½Π°ΡΡΠΆΠΈΡΡ ΠΊΠ»Π°ΡΡΠ½ΡΠ΅ ΡΠΎΠ²ΡΠ΅ΠΌΠ΅Π½Π½ΡΠ΅ ΡΡΠΌΠ»ΠΎΡΠΊΠΈ ΠΈΠ· Π½Π°ΡΡΠΎΡΡΠ΅ΠΉ ΠΊΠΎΠΆΠΈ ΡΠ°Π·Π»ΠΈΡΠ½ΡΡ ΡΠ²Π΅ΡΠΎΠ² Π½Π° Π»ΡΠ±ΠΎΠΉ Π²ΠΊΡΡ. Π£ Π½Π°Ρ ΠΆΠ΅Π½ΡΠΊΠΈΠ΅ ΡΡΠΌΠΊΠΈ ΠΈΠ· ΠΊΠΎΠΆΠΈ ΡΠ°ΠΊΠΆΠ΅ Π²Ρ ΡΠΌΠΎΠΆΠ΅ΡΠ΅ Π²ΡΠ±ΡΠ°ΡΡ ΡΡΠΌΠΎΡΠΊΡ Π»ΡΠΊΡΠΎΠ²ΠΎΠ³ΠΎ ΡΠΎΡΠΌΠ°ΡΠ° ΠΈΠ»ΠΈ ΠΏΠΎΠ²ΡΠ΅Π΄Π½Π΅Π²Π½ΡΡ, ΡΡΠΌΠΊΠΈ Π½Π° ΠΊΠΎΠΆΠ°Π½ΠΎΠΌ ΡΠ΅ΠΌΠ½Π΅ ΠΈΠ»ΠΈ ΡΠ΅ΠΏΠΈΠΈ Π΅ΡΠ΅ ΠΊΡΠΏΠΈΡΡ ΡΡΠΌΠΊΡ ΠΈΠ· ΠΊΠΎΠΆΠΈ Π΄Π»Ρ ΠΏΠΎΠ²ΡΠ΅Π΄Π½Π΅Π²Π½ΡΡ ΠΈΠ»ΠΈ Π΄Π΅Π»ΠΎΠ²ΡΡ Π±ΠΈΠ·Π½Π΅Ρ Π²ΡΡΡΠ΅Ρ.
ReplyDeleteΠΡΠΈΡΠΎΠ΄Π½ΡΠ΅ ΠΊΠ°ΡΠ°ΠΊΠ»ΠΈΠ·ΠΌΡ ΠΈΠ»ΠΈ ΡΠΈΡΡΠ°Π»ΡΠ½ΡΠ΅ ΠΆΠ΅ΡΡΠ²ΠΎΠΏΡΠΈΠ½ΠΎΡΠ΅Π½ΠΈΡ ΡΠΎ Π²ΡΠ΅ΠΌΠ΅Π½Π΅ΠΌ ΠΎΠ±ΠΎΡΠ½ΠΎΠ²Π°Π»ΠΈ ΡΠΎΡΠ½ΠΎΠ΅ ΠΈΠ½ΡΠ΅ΡΠΏΡΠ΅ΡΠ°ΡΠΈΡ ΠΎΠ±Π½Π°ΡΡΠΆΠ΅Π½Π½ΠΎΠ³ΠΎ. ΠΠ°ΠΆΠ½Π΅ΠΉΡΠΈΠ΅ ΡΡΠ΅Π΄ΡΡΠ²Π° Π³Π°Π΄Π°Π½ΠΈΡ ΠΎΠ±ΡΠ°Π·ΠΎΠ²Π°Π»ΠΈΡΡ ΡΡΡΡΡΠ΅Π»Π΅ΡΠΈΡ ΡΠΎΠΌΡ Π½Π°Π·Π°Π΄ Π΄ΠΎ Π½Π°ΡΠ΅ΠΉ ΡΡΡ. ΠΠ°Π΄Π°Π½ΠΈΠ΅ Π΄Π²ΠΎΠΉΠ½ΡΡΠΊΠΈ ΠΎΠ½Π»Π°ΠΉΠ½ Π·Π½Π°ΡΠΈΡΡΡ ΠΌΠ°ΠΊΡΠΈΠΌΠ°Π»ΡΠ½ΠΎ ΡΠΎΡΠ½ΡΠΌ Π΄Π΅ΠΉΡΡΠ²ΠΈΠ΅ΠΌ ΠΎΠΏΡΠ΅Π΄Π΅Π»ΠΈΡΡ ΡΡΠ΄ΡΠ±Ρ ΡΠ΅Π»ΠΎΠ²Π΅ΠΊΠ°.
ReplyDeleteΠ‘ΠΎΠ»ΠΈΠ΄Π½ΡΠΉ ΠΈ ΠΏΡΠΎΠ²Π΅ΡΠ΅Π½Π½ΡΠΉ ΠΏΡΠΎΠ΄Π°Π²Π΅Ρ Π²ΡΠ΅Π³Π΄Π° ΡΠΌΠΎΠΆΠ΅Ρ ΠΏΡΠ΅Π΄Π»ΠΎΠΆΠΈΡΡ ΠΌΠ½ΠΎΠ³ΠΎΡΠΈΡΠ»Π΅Π½Π½ΡΠΉ Π°ΡΡΠΎΡΡΠΈΠΌΠ΅Π½Ρ ΠΊΠ΅ΡΠ°ΠΌΠΈΡΠ΅ΡΠΊΠΎΠ³ΠΎ ΠΏΠΎΠΊΡΡΡΠΈΡ Π΄Π»Ρ Π²Π°Π½Π½ΠΎΠΉ. ΠΡΠ΅Π½Π΄ Π‘ΠΎΡΠ½ΠΈ.ΡΡ ΠΏΡΠΎΠ΄Π°Π΅Ρ geotiles ΠΊΡΠΏΠΈΡΡ ΡΠΆΠ΅ ΡΠ²ΡΡΠ΅ 10 Π»Π΅Ρ.
ReplyDeleteΠΠ°Π±ΡΠΎΠ½ΠΈΡΠΎΠ²Π°ΡΡ ΡΡΠ΅Π±ΡΠ΅ΠΌΡΡ ΡΡΠΌΠΌΡ Π½Π° ΠΊΠ°ΡΡΠΎΡΠ½ΡΠΉ ΡΡΠ΅Ρ Π½Π° ΡΠ΄ΠΈΠ²Π»Π΅Π½ΠΈΠ΅ ΠΏΡΠΎΡΡΠΎ. ΠΠ½Π»Π°ΠΉΠ½ Π·Π°ΠΉΠΌ ΡΠ΅ΡΠ΅Π· ΡΠΈΡΡΠ΅ΠΌΡ ΠΊΠΎΠ½ΡΠ°ΠΊΡ – ΡΡΠΎ Π½Π°Π΄Π΅ΠΆΠ½ΡΠΉ Π²Π°ΡΠΈΠ°Π½Ρ Π²Π·ΡΡΡ Π½Π°Π»ΠΈΡΠ½ΠΎΡΡΡ Π² ΠΌΠΈΠ½ΠΈΠΌΠ°Π»ΡΠ½ΡΠ΅ ΡΡΠΎΠΊΠΈ. Π’ΠΎΠΏΠΎΠ²ΡΠΉ ΡΠ°ΠΉΡ Π²ΡΠ±ΠΎΡΠ° ΠΊΠΎΠΌΠΌΠ΅ΡΡΠ΅ΡΠΊΠΈΡ ΠΏΡΠΎΠ΄ΡΠΊΡΠΎΠ² ΡΠ°Π·ΡΠ΅ΡΠ°Π΅Ρ ΠΏΠΎΠ»ΡΡΠΈΡΡ Π½Π΅ΠΎΠ±Ρ ΠΎΠ΄ΠΈΠΌΡΠΉ Π·Π°ΠΉΠΌ.
ReplyDeleteΠΠΎΠΌΠΏΠ»Π΅ΠΊΡ ΠΎΠΏΠ΅ΡΠ°ΡΠΈΠΉ, Π½Π°ΠΏΡΠ°Π²Π»Π΅Π½Π½ΡΡ Π½Π° ΠΏΡΠ΅Π΄Π²ΠΈΠ΄Π΅Π½ΠΈΠ΅ Π±ΡΠ΄ΡΡΠ΅Π³ΠΎ, Π½Π°Π·ΡΠ²Π°ΡΡ Π³Π°Π΄Π°Π½ΠΈΠ΅. Π‘Π²Π΅ΡΡ ΡΠ΅ΡΡΠ΅ΡΡΠ²Π΅Π½Π½ΡΠ΅ ΡΠΈΠ»Ρ ΠΈ ΠΌΠ½ΠΎΠ³ΠΎΠΎΠ±ΡΠ°Π·Π½ΡΠ΅ ΡΡΠ»ΠΎΠ²ΠΈΡ Π²ΠΎΡΠΎΠΆΠ΅Π½ΠΈΡ Π½Π°ΡΡΠ½ΠΎ Π½Π΅ Π΄ΠΎΠΊΠ°Π·Π°Π½Ρ, ΠΏΡΠΈ ΡΠΎΠΌ ΡΠ°Π·Π»ΠΈΡΠ½ΡΠ΅ Π»ΡΠ΄ΠΈ Π²Π΅ΡΡΡ Π² ΡΡΠΎ. Π’Π°ΡΠΎΠ»ΠΎΠ³ ΠΎΡΠ·ΡΠ²Ρ - ΡΡΠΎ Π½Π°Π΄Π΅ΠΆΠ½ΡΠΉ ΠΏΠΎΡΡΠ΄ΠΎΠΊ ΡΠ·Π½Π°ΡΡ ΡΡΠ΄ΡΠ±Ρ Ρ ΠΏΡΠΈΠΌΠ΅Π½Π΅Π½ΠΈΠ΅ΠΌ ΡΠ°Π·Π½ΠΎΠΎΠ±ΡΠ°Π·Π½ΡΡ Π°ΡΡΠΈΠ±ΡΡΠΎΠ² ΠΈ ΠΌΠ΅ΡΠΎΠ΄ΠΎΠ².
ReplyDeleteΠΡΠΎΠΉΠ΄ΠΈΡΠ΅ ΡΠ΅Π³ΠΈΡΡΡΠ°ΡΠΈΡ Π½Π° ΠΏΠ»Π°ΡΡΠΎΡΠΌΠ΅ ΠΈ ΡΠ²ΠΈΠ΄ΠΈΡΠ΅ ΠΏΡΠΈΡΡΠ½ΡΠ΅ Π²ΠΎΠ·Π½Π°Π³ΡΠ°ΠΆΠ΄Π΅Π½ΠΈΡ Π² ΡΡΠ΅ΡΠ½ΠΎΠΉ Π·Π°ΠΏΠΈΡΠΈ. ΠΠΎΠΏΠΎΠ»Π½ΠΈΡΠ΅Π»ΡΠ½ΡΠΉ ΡΡΠ΅Ρ Π΄Π°ΡΡ Π²ΠΎΠ·ΠΌΠΎΠΆΠ½ΠΎΡΡΡ ΡΠ³ΡΠ΅ΡΡΠΈ ΠΌΠ½ΠΎΠ³ΠΎ Π±Π°Π±ΠΎΠΊ. ΠΠ°ΠΆΠ½ΠΎ Π½Π΅ Π·Π°Π±ΡΠ²Π°ΡΡ, ΡΡΠΎ ΠΏΡΠΎΠ΅ΠΊΡ ΠΊΠ°Π·ΠΈΠ½ΠΎ Ρ ΠΊΠ°Π·ΠΈΠ½ΠΎ ΠΎΠ½Π»Π°ΠΉΠ½ ΠΎΡΠΈΡΠΈΠ°Π»ΡΠ½ΡΠΉ ΠΏΡΠ΅Π΄Π»Π°Π³Π°Π΅Ρ ΡΠ²ΠΎΠΈΠΌ ΠΏΠΎΠ»ΡΠ·ΠΎΠ²Π°ΡΠ΅Π»ΡΠΌ ΡΠΏΠ΅ΡΠΈΠ°Π»ΡΠ½ΡΠ΅ Π±ΠΎΠ½ΡΡΡ.
ReplyDeleteΠ Π°Π·Π²ΠΈΡΠΈΠ΅ ΡΠΎΠ²ΡΠ΅ΠΌΠ΅Π½Π½ΡΡ ΡΠ΅Ρ Π½ΠΎΠ»ΠΎΠ³ΠΈΠΉ ΠΏΠΎΠ·Π²ΠΎΠ»ΡΠ΅Ρ ΠΈΠ½ΡΠ΅ΡΠ°ΠΊΡΠΈΠ²Π½ΡΠΌ ΡΠ°ΠΉΡΠ°ΠΌ ΠΊΠΎΠ½ΠΊΡΠ΅ΡΠ½ΠΎ ΠΎΠΏΡΠΈΠΌΠΈΠ·ΠΈΡΠΎΠ²Π°ΡΡ ΠΏΡΠ΅Π΄Π»Π°Π³Π°Π΅ΠΌΡΠ΅ ΡΠ΅ΡΠ²ΠΈΡΡ. ΠΠ½ΡΠ΅ΡΠ½Π΅Ρ-ΠΈΠ³ΡΡ ΠΎΠ±ΡΠ΅Π»ΠΈ ΡΡΡΠ΅ΡΡΠ²Π΅Π½Π½ΡΡ ΡΠ°ΡΠΏΡΠΎΡΡΡΠ°Π½Π΅Π½Π½ΠΎΡΡΡ ΠΏΠΎ Π²ΡΠ΅ΠΌΡ ΠΌΠΈΡΡ. ΠΠ°Π·ΠΈΠ½ΠΎ Ρ ΡΠ°ΠΉΡ – Π²ΠΎΡΠΏΠΎΠ»ΡΠ·ΡΠΉΡΠ΅ΡΡ ΠΏΡΠ΅ΠΈΠΌΡΡΠ΅ΡΡΠ²ΠΎΠΌ Π·Π°ΡΠΈΡΠ΅Π½Π½ΠΎΠΉ ΠΈΠ³ΡΡ ΠΈ Π·Π°ΡΠ°Π±ΠΎΡΠ°ΠΉΡΠ΅ ΡΡΡΠ΅ΡΡΠ²Π΅Π½Π½ΡΠ΅ Π±Π°Π±ΠΊΠΈ.
ReplyDeleteΠ’ΠΎΠ»ΡΠΊΠΎ Π»ΠΈΡΡ Π½Π° ΠΏΠΎΡΡΠ°Π»Π΅ casino mister bit ΠΊΠ»ΠΈΠ΅Π½ΡΡ ΠΎΡΠ΅Π½Ρ ΠΏΡΠΎΡΡΠΎ ΡΠΊΠ°ΡΠ°ΡΡ Π»ΡΠ±ΠΈΠΌΡΡ ΠΈΠ½ΡΠ΅ΡΠ°ΠΊΡΠΈΠ²Π½ΡΡ ΠΈΠ³ΡΡΡΠΊΡ Π΄Π»Ρ ΡΠ°Π·Π²Π»Π΅ΡΠ΅Π½ΠΈΠΉ. ΠΡΠΈΡ ΠΎΠ΄Ρ Π² ΠΈΠ½ΡΠ΅ΡΠ°ΠΊΡΠΈΠ²Π½ΡΠΉ ΠΊΠ»ΡΠ±, ΠΏΠΎΠ»ΡΠ·ΠΎΠ²Π°ΡΠ΅Π»Ρ ΠΌΠΎΠΆΠ΅Ρ ΠΎΠΊΡΠ½ΡΡΡΡΡ Π² Π½Π΅Π·Π°Π±ΡΠ²Π°Π΅ΠΌΡΠ΅ Π°Π²Π°Π½ΡΡΡΡ. ΠΠ³ΡΠ°ΡΡΡΡ Π² Π³ΡΡΠΏΠΏΠ΅ Π΅Π΄ΠΈΠ½ΠΎΠΌΡΡΠ»Π΅Π½Π½ΠΈΠΊΠΎΠ² Π² Π·Π½Π°ΡΠΈΡΠ΅Π»ΡΠ½ΠΎΠΉ ΡΡΠ΅ΠΏΠ΅Π½ΠΈ ΡΠ²Π»Π΅ΠΊΠ°ΡΠ΅Π»ΡΠ½Π΅Π΅, ΡΠ΅ΠΌ ΡΠ°ΠΌ ΠΏΠΎ ΡΠ΅Π±Π΅ Π΄ΠΎΠΌΠ°.
ReplyDeleteΠΠ½ΠΎΠΆΠ΅ΡΡΠ²ΠΎ ΡΠ·ΠΎΡΠΎΠ² ΠΈ ΡΠ°Π·ΠΌΠ΅ΡΠΎΠ². Π¦Π΅Π½ΠΎΠ²ΠΎΠΉ Π΄ΠΈΠ°ΠΏΠ°Π·ΠΎΠ½ ΠΏΠ»ΠΈΡΠΊΠΈ ΡΠΎΠΆΠ΅ ΠΎΡΠ»ΠΈΡΠ°Π΅ΡΡΡ. ΠΠ°ΡΠ΅Π»Ρ ΠΏΠ»ΠΈΡΠΊΠ° porto rose dual gres ΠΈΠ·Π³ΠΎΡΠ°Π²Π»ΠΈΠ²Π°ΡΡ Π² Π±ΠΎΠ»ΡΡΠΎΠΌ ΠΊΠΎΠ»ΠΈΡΠ΅ΡΡΠ²Π΅, Π° Π²ΡΡΠΊΠ°Ρ ΠΊΠΎΠ½ΡΠΎΡΠ° ΡΡΡΠ΅ΠΌΠΈΡΡΡ Π²ΡΡΡΠ°Π²ΠΈΡΡ ΡΠ²ΠΎΠΉ Π½Π΅ΠΏΠΎΠ²ΡΠΎΡΠΈΠΌΡΠΉ ΠΏΡΠΎΠ΅ΠΊΡ.
ReplyDeleteGood article! Thank you so much for sharing this great post, it was so good to read.
ReplyDeletedevops engineer responsibilities
7habits
mobile app testing tools
benefits of web development
basic excel interview questions
Wonderful..! I was really impressed by your excellent post and Keep doing well...
ReplyDeleteMicrosoft Dynamics CRM Training in Chennai
Node JS Training in Chennai
Node JS Course in Chennai
ΠΠΎΡ Π΅ΡΡ Π½Π΅ΡΠΊΠΎΠ»ΡΠΊΠΎ Π³Π»Π°Π²Π½ΡΡ ΠΏΡΠΈΠΎΡΠΈΡΠ΅ΡΠΎΠ² http://environmental-physiology-research.hk/home.php?mod=space&uid=51478, ΠΊΠΎΡΠΎΡΡΠΌΠΈ ΠΎΠ±Π»Π°Π΄Π°Π΅Ρ ΠΊΠ΅ΡΠ°ΠΌΠΈΡΠ΅ΡΠΊΠ°Ρ ΠΏΠ»ΠΈΡΠΊΠ°. ΠΠ΅ΡΠ°ΠΌΠΎΠ³ΡΠ°Π½ΠΈΡ Π΄Π΅Π»Π°ΡΡ ΠΈΡΠΊΠ»ΡΡΠΈΡΠ΅Π»ΡΠ½ΠΎ ΠΈΠ· ΠΏΡΠΈΡΠΎΠ΄Π½ΡΡ ΠΈΡΡ ΠΎΠ΄Π½ΠΈΠΊΠΎΠ². ΠΠ΅ΡΠ°ΠΌΠΈΠΊΡ Π²ΠΎΠ·ΠΌΠΎΠΆΠ½ΠΎ ΠΌΠΎΠ½ΡΠΈΡΠΎΠ²Π°ΡΡ Π² Π·Π°Π»Π°Ρ Π·Π°Π²Π΅Π΄Π΅Π½ΠΈΠΉ ΠΎΠ±ΡΠ΅ΡΡΠ²Π΅Π½Π½ΠΎΠ³ΠΎ ΠΏΠΈΡΠ°Π½ΠΈΡ, Π² ΡΠΊΠΎΠ»Π°Ρ ΠΈ Π΄ΠΎΡΠΊΠΎΠ»ΡΠ½ΡΡ ΡΡΠ΅Π±Π½ΡΡ Π·Π°Π²Π΅Π΄Π΅Π½ΠΈΡΡ . ΠΠ΅ΡΠΎΠΊΡΠΈΡΠ΅ΡΠΊΠΈΠΉ ΠΌΠ°ΡΠ΅ΡΠΈΠ°Π», ΡΠΎΠ²Π΅ΡΡΠ΅Π½Π½ΠΎ Π±Π΅Π·ΠΎΠΏΠ°ΡΠ΅Π½ Π΄Π»Ρ ΠΏΡΠΎΠΆΠΈΠ²Π°ΡΡΠΈΡ .
ReplyDeleteΠ‘ΠΎΡΡΠ΅Π΄ΠΎΡΠΎΡΡΡΠ΅ΡΡ Π½Π΅ ΡΠΎΠ»ΡΠΊΠΎ Π½Π° ΠΊΠ΅ΡΠ°ΠΌΠΈΡΠ΅ΡΠΊΠΎΠΉ ΠΏΠ»ΠΈΡΠΊΠ΅ ΠΈΠ½ΠΎΡΡΡΠ°Π½Π½ΠΎΠ³ΠΎ ΠΏΡΠΎΠΈΠ·Π²ΠΎΠ΄ΡΡΠ²Π°, Π½ΠΎ ΠΈ Π½Π° Π½Π°ΡΠΈ Π²ΠΈΠ΄Ρ. ΠΡΠ±ΠΈΡΠ°Ρ ΠΊΠ°ΡΠ΅ΡΡΠ²Π΅Π½Π½ΡΠΉ ΡΡΡΠΎΠΉΠΌΠ°ΡΠ΅ΡΠΈΠ°Π» ΠΊΠ°ΠΊ Π½Π°ΠΏΡΠΈΠΌΠ΅Ρ http://portal.prolisok.org/index.php?subaction=userinfo&user=axonige Π² Π»ΡΠ±ΠΎΠΌ ΡΠ»ΡΡΠ°Π΅ ΠΏΡΠΈΠ΄Π΅ΡΡΡ ΡΠ°ΡΡΠΌΠΎΡΡΠ΅ΡΡ ΠΌΠ½ΠΎΠΆΠ΅ΡΡΠ²Π΅Π½Π½ΠΎΠ΅ ΠΊΠΎΠ»ΠΈΡΠ΅ΡΡΠ²ΠΎ ΠΌΠ°ΡΠ΅ΡΠΈΠ°Π»ΠΎΠ². ΠΠ΅ΡΠ°ΠΌΠΈΡΠ΅ΡΠΊΠ°Ρ ΠΏΡΠ΅Π²ΠΎΡΡ ΠΎΠ΄Π½ΠΎ ΠΏΠΎΠ΄ΠΎΠΉΠ΄Π΅Ρ ΠΊ ΠΊΠ°ΠΆΠ΄ΠΎΠΌΡ ΠΈΠ½ΡΠ΅ΡΡΠ΅ΡΡ. ΠΠΏΡΠΈΠΌΠ°Π»ΡΠ½ΡΠΉ Π²ΡΠ±ΠΎΡ Π½Π°ΡΡΠ΅Π½Π½ΠΎΠ³ΠΎ ΠΏΠΎΠΊΡΡΡΠΈΡ ΡΠΏΠΎΡΠΎΠ±Π΅Π½ ΠΎΠ±Π»Π°Π³ΠΎΡΠΎΠ΄ΠΈΡΡ ΠΊΠ°ΠΆΠ΄ΡΡ ΠΊΡΡ Π½Ρ ΠΈΠ»ΠΈ ΡΠ°Π½ΡΠ·Π΅Π».
ReplyDeleteΠΠΎΡΡΠ°Π²ΠΊΠ° Π²ΡΠΏΠΎΠ»Π½ΡΠ΅ΡΡΡ ΠΊΠ°ΠΊ ΡΠ°Π· Π½Π° Π΄Π°ΡΡ Π·Π°ΠΊΠ°Π·Π°. ΠΡΠΏΠΈΡΡ Π΄Π°ΡΡ ΠΌΠΎΡΡ 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ΠΡΠ±ΠΈΡ Π»ΠΈ ΠΌΠ΅Π½Ρ ΠΌΡΠΆΡΠΈΠ½Π° Π³Π°Π΄Π°Π½ΠΈΠ΅ Π½Π° ΠΊΠ°ΡΡΠ°Ρ Π’Π°ΡΠΎ ΠΏΠΎΠ·Π²ΠΎΠ»ΡΠ΅Ρ ΡΠ²ΠΈΠ΄Π΅ΡΡ, ΡΡΠΎ Π²Π°Ρ ΠΆΠ΄Π΅Ρ Π² Π±Π»ΠΈΠΆΠ°ΠΉΡΠ΅ΠΌ Π²ΡΠ΅ΠΌΠ΅Π½ΠΈ. ΠΠΎΠΏΡΡΠΊΠ° ΡΠ°ΡΡΠΌΠΎΡΡΠ΅ΡΡ Π³ΡΡΠ΄ΡΡΠΈΠ΅ ΡΠ²Π»Π΅Π½ΠΈΡ Π½Π΅ΠΏΡΠ΅ΡΡΠ²Π½ΠΎ ΠΌΠ°Π½ΠΈΠ» ΡΠ΅Π»ΠΎΠ²Π΅ΠΊΠ°. ΠΡΡΠΊΠΈΠΉ ΠΌΠ΅ΡΡΠ°Π΅Ρ ΠΏΡΠ΅Π΄ΡΠ³Π°Π΄Π°ΡΡ ΡΠ²ΠΎΠ΅ Π±ΡΠ΄ΡΡΠ΅Π΅ ΠΈ Π²ΠΎΡΠΏΡΠΈΠ½ΠΈΠΌΠ°Π΅Ρ ΠΎΠΏΡΠ΅Π΄Π΅Π»Π΅Π½Π½ΡΠ΅ ΡΠΏΠΎΡΠΎΠ±Ρ Π²ΠΎΡΠΎΠΆΠ±Ρ Π±ΠΎΠ»Π΅Π΅ Π΄Π΅ΠΉΡΡΠ²Π΅Π½Π½ΡΠΌΠΈ.
ReplyDeleteReally an amazing blog with useful information you have shared. Thanks for sharing such an nice article..
ReplyDeleteFinal Year Project Center in Chennai | Final Year Projects in Velachery
I am really happy to read your blog. Your article is awesome with impressive content. Keep updating..
ReplyDeleteIELTS Test Center in Chennai | IELTS Test Center in Velachery
Nice post... Really you are done a wonderful job. Thanks for sharing such wonderful information with us. Please keep on updating...
ReplyDeleteMBA Project Center in Chennai | MBA Projects in Velachery
Excellent blog...
ReplyDeleteEthical Hacking Training Institute in Chennai | Ethical Hacking Training Institute in Velachery | Ethical Hacking Training Institute in Thiruvanmiyur | Ethical Hacking Training Institute in Tharamani | Ethical Hacking Training Institute in Medavakkam
"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.
ReplyDeleteThanks"
Alltechzsolutions Pvt ltd java Full Stack Developer Training in Chennai
ReplyDeleteTechnology 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
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