dido:public:ra:1.2_views:1_stakeholder
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:1.2_views:1_stakeholder [2021/05/10 17:22] murphy ↷ Page moved and renamed from dido:public:ra:1.2_views:1_stakeholder:start to dido:public:ra:1.2_views:1_stakeholder |
dido:public:ra:1.2_views:1_stakeholder [2022/01/15 18:23] (current) nick |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| Within this context, the following definition of [[dido:public:ra:xapend:xapend.a_glossary:s:stakeholder]] is used: | Within this context, the following definition of [[dido:public:ra:xapend:xapend.a_glossary:s:stakeholder]] is used: | ||
| - | : //A **stakeholder** is a person, group or organization that has interest or concern in a __[target]__ organization. | + | : //A **[[dido:public:ra:xapend:xapend.a_glossary:s:stakeholder|stakeholder]]** is a person, group or organization that has interest or concern in a __[target]__ organization. |
| Stakeholders can affect or be affected by the __[target]__ organization's actions, objectives and policies. | Stakeholders can affect or be affected by the __[target]__ organization's actions, objectives and policies. | ||
| [[http://www.businessdictionary.com/definition/stakeholder.html]]// | [[http://www.businessdictionary.com/definition/stakeholder.html]]// | ||
| Line 14: | Line 14: | ||
| * the definition of data structures or data being distributed | * the definition of data structures or data being distributed | ||
| - | In contrast to distributed systems, centralized systems (i.e., mainframes) are the authority for computation and data. In essence, the only reality is the processes and data that reside in the centralized system. | + | In contrast to [[dido:public:ra:xapend:xapend.a_glossary:d:distsystem|distributed systems]], centralized systems (i.e., mainframes) are the authority for computation and data. In essence, the only reality is the processes and data that reside in the centralized system. |
| - | This is also in contrast to decentralized systems (i.e., traditional cloud servers), which rely on well-orchestrated and coordinated efforts of a few well connected and synchronized systems. Collective servers are the authority for the computation and data. In essence, the only reality is that which can be found on the decentralized servers; the infrastructure is expected to keep the software and data consistent and synchronized. However, this only needs to be concerned with servers that, although they are decentralized, still fall under a single authority thereby making the requirements, architecture, design, implementation, and maintenance relatively easy. | + | This is also in contrast to decentralized systems (i.e., traditional cloud servers), which rely on well-orchestrated and coordinated efforts of a few well-connected and synchronized systems. Collective servers are the authority for the computation and data. In essence, the only reality is that which can be found on the decentralized servers; the infrastructure is expected to keep the software and data consistent and synchronized. However, this only needs to be concerned with servers that, although they are decentralized, still fall under a single authority thereby making the requirements, architecture, design, implementation, and maintenance relatively easy. |
| - | Both centralized and decentralized systems often have extensive data models and functionality, which adds to the complexity of managing them. This generally requires a single governing body (i.e., enterprise) to be ultimately responsible for the entire ecosystem and the lifecycle of the systems and the integration of components including hardware, operating systems, database management systems, web servers, application servers, software languages, networking, and other protocols. These “stacks” often result in stovepipe solutions. | + | Both centralized and decentralized systems often have extensive data models and functionality, which adds to the complexity of managing them. This generally requires a single [[dido:public:ra:xapend:xapend.a_glossary:g:gov_body]] (i.e., enterprise) to be ultimately responsible for the entire ecosystem and the lifecycle of the systems and the integration of components including hardware, [[dido:public:ra:xapend:xapend.a_glossary:o:os|operating systems]], [[dido:public:ra:xapend:xapend.a_glossary:d:dbms|database management systems]], web servers, application servers, software languages, networking, and other protocols. These “stacks” frequently result in stovepipe solutions. |
| In distributed systems, much of the ecosystem and governance of the components is handled by various [[dido:public:ra:xapend:xapend.a_glossary:c:coi| Communities of Interest (CoIs)]]: each has a responsibility for different aspects of the distributed system. The traditional role of a corporation or enterprise is to participate in these communities. The following graphic illustrates the various communities considered to be "customers" of the DIDO RA. | In distributed systems, much of the ecosystem and governance of the components is handled by various [[dido:public:ra:xapend:xapend.a_glossary:c:coi| Communities of Interest (CoIs)]]: each has a responsibility for different aspects of the distributed system. The traditional role of a corporation or enterprise is to participate in these communities. The following graphic illustrates the various communities considered to be "customers" of the DIDO RA. | ||
| Line 28: | Line 28: | ||
| </figure> | </figure> | ||
| - | : **Platform** | + | * **[[dido:public:ra:xapend:xapend.a_glossary:p:platform|Platform]]** \\ |
| - | : is responsible for the software used to distribute and control data within the Node Network, for example Bitcoin, Ethereum, Iota, DDS, and IPFS. | + | <wrap> is responsible for the software used to distribute and control data within the [[dido:public:ra:xapend:xapend.a_glossary:n:node_network|Node Network]], for example [[dido:public:ra:xapend:xapend.a_glossary:b:bitcoin|Bitcoin]], [[dido:public:ra:xapend:xapend.a_glossary:e:ethereum|Ethereum]], Iota, DDS, and IPFS.</wrap> |
| - | : **Domain** | + | * **Domain** \\ |
| - | : is responsible for the use of the data distributed on the Node Network, for example currency, rewards programs, or certificates. | + | <wrap> is responsible for the use of the data distributed on the Node Network, for example currency, rewards programs, or certificates.</wrap> |
| - | : **Ecosystem** | + | * **Ecosystem** \\ |
| - | : is responsible for a collection of domains associated with a particular ares of interest, such as green groceries, interest rate swaps, a particular tank, or class of automobiles. | + | <wrap> is responsible for a collection of domains associated with a particular ares of interest, such as green groceries, interest rate swaps, a particular tank, or class of automobiles.</wrap> |
| - | : **Ecosphere** | + | * **Ecosphere** \\ |
| - | : is responsible for a collection of domains and ecosystems associated with a common governance, which crosses over multiple areas of interest, such as military, government, automotive, or finance. | + | <wrap> is responsible for a collection of domains and ecosystems associated with a common governance, which crosses over multiple areas of interest, such as military, government, automotive, or finance.</wrap> |
| - | : **Exchange** | + | * **Exchange** \\ |
| - | : is responsible for the exchange of data (tokens) from one domain or ecosystem with data in another domain or ecosystem, for example exchanging Bitcoins for U.S. dollars, or strawberries for jars of jam. | + | <wrap> is responsible for the exchange of data ([[dido:public:ra:xapend:xapend.a_glossary:t:tokens|tokens]]) from one domain or ecosystem with data in another domain or ecosystem, for example exchanging Bitcoins for U.S. dollars, or strawberries for jars of jam.</wrap> |
| - | : **Enterprise** | + | * **Enterprise** \\ |
| - | : is responsible for being the systems integrator of all the domains, ecosystems, and ecospheres needed to fulfill the mission and goals of a corporation or organization, such as an auto company, a chain of retail stores, or a bank. | + | <wrap> is responsible for being the systems integrator of all the domains, ecosystems, and ecospheres needed to fulfill the mission and goals of a corporation or organization, such as an auto company, a chain of retail stores, or a bank.</wrap> |
| Each of these areas is explained in more detail in the following views, concluding with a list of standards applicable to these Stakeholder Views: | Each of these areas is explained in more detail in the following views, concluding with a list of standards applicable to these Stakeholder Views: | ||
dido/public/ra/1.2_views/1_stakeholder.1620681759.txt.gz · Last modified: 2021/05/10 17:22 by murphy
