Difference between revisions of "Splitting & merging"
m |
(→Merging: Middleware analysts are developers with a specialisation in products that connect two different computer systems together) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{glossary}} | + | <noinclude>{{glossary}}</noinclude>[[Platform]] organisations use Biological [[Spontaneous Evolution|cell]]s as an example by splitting into two to create new organisations, or by [[deployment|deploy]]ing a [[seed]] to be installed in another location. Merging is the opposite [[process]] and is used to [[unification|unify]] different organisations into a single harmonious whole when they are seen to be fully [[alignment|aligned]] with the same [[values]] and [[vision]]. |
| + | <noinclude> | ||
| + | == Splitting == | ||
| + | This [[process]] involves increasing the local Platforms scale of operation, for example building up stock and sourcing available [[worker]]s to fill [[role]]s. When it's scaled to an appropriate size some of the local resources are migrated to the remote Platforms location and continue operation there. | ||
| + | |||
| + | == Merging == | ||
| + | Sometimes things that split at one point in time will later merge back together. Other times things that appeared to be different are found to have the same goals and values... | ||
| + | |||
| + | [[w:Middleware analysts|Middleware analysts]] are developers with a specialisation in products that connect two different computer systems together. As the term implies, the software, tools, and technologies used by Middleware analysts sit "in-the-middle", between two or more systems; the purpose being to enable two systems to communicate and share information. Middleware analysts look at the [[w:system of systems|system of systems]]. They solve technical problems which involve large scale [[w:inter-disciplinary|inter-disciplinary]] objectives with multiple, heterogeneous, distributed systems that are embedded in networks at multiple levels. | ||
== Notes == | == Notes == | ||
| Line 7: | Line 15: | ||
== See also == | == See also == | ||
| − | |||
*[[Unification]] | *[[Unification]] | ||
*[[Trust group]] | *[[Trust group]] | ||
| + | *[[XMPP]] | ||
| + | *[[Wikipedia:Message-oriented middleware]] | ||
[[Category:Philosophy]] | [[Category:Philosophy]] | ||
| + | </noinclude> | ||
Latest revision as of 10:14, 28 July 2011
|
Platform organisations use Biological cells as an example by splitting into two to create new organisations, or by deploying a seed to be installed in another location. Merging is the opposite process and is used to unify different organisations into a single harmonious whole when they are seen to be fully aligned with the same values and vision.
Contents
Splitting
This process involves increasing the local Platforms scale of operation, for example building up stock and sourcing available workers to fill roles. When it's scaled to an appropriate size some of the local resources are migrated to the remote Platforms location and continue operation there.
Merging
Sometimes things that split at one point in time will later merge back together. Other times things that appeared to be different are found to have the same goals and values...
Middleware analysts are developers with a specialisation in products that connect two different computer systems together. As the term implies, the software, tools, and technologies used by Middleware analysts sit "in-the-middle", between two or more systems; the purpose being to enable two systems to communicate and share information. Middleware analysts look at the system of systems. They solve technical problems which involve large scale inter-disciplinary objectives with multiple, heterogeneous, distributed systems that are embedded in networks at multiple levels.
Notes
Members can work from anywhere geographically, so they work in new premises like a missionary to help it grow, but still handle some of their own Platforms work remotely.
Bifurcation: Division of a Platform into two...
