dido:public:ra:xapend:xapend.e_tools:oss
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:xapend:xapend.e_tools:oss [2021/08/11 13:34] murphy [Tools: Open Source Paradigm] |
dido:public:ra:xapend:xapend.e_tools:oss [2021/10/03 16:32] (current) 157.55.39.140 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Tools: Open Source Paradigm ====== | ====== Tools: Open Source Paradigm ====== | ||
| - | [[dido:public:ra:xapend:xapend.e_tools| Return to Tools Area]] | + | [[dido:public:ra:xapend:xapend.e_tools:start| Return to Tools Area]] |
| Using a DIDO is not just a simple shift in policies, procedures and practices. It is a change in the architectural paradigm -- from centralized control to distributed -- requiring a fundamental change in how a system is normalized into systems, subsystems, components, etc. It also requires a shift in the basic underlying principles of a system. DIDOs are generally: | Using a DIDO is not just a simple shift in policies, procedures and practices. It is a change in the architectural paradigm -- from centralized control to distributed -- requiring a fundamental change in how a system is normalized into systems, subsystems, components, etc. It also requires a shift in the basic underlying principles of a system. DIDOs are generally: | ||
| Line 10: | Line 10: | ||
| The DIDO architecture does not represent a single unified enterprise; rather it represents a loosely defined confederation of domains bound together by systems integration (SI)(( | The DIDO architecture does not represent a single unified enterprise; rather it represents a loosely defined confederation of domains bound together by systems integration (SI)(( | ||
| **System Integrator** - An individual or organization that builds systems from a variety of diverse components. With increasing complexity of technology, more customers want complete solutions to information problems, requiring hardware, software and networking expertise in a multivendor environment. [[https://www.pcmag.com/encyclopedia/term/52450/systems-integrator ]] | **System Integrator** - An individual or organization that builds systems from a variety of diverse components. With increasing complexity of technology, more customers want complete solutions to information problems, requiring hardware, software and networking expertise in a multivendor environment. [[https://www.pcmag.com/encyclopedia/term/52450/systems-integrator ]] | ||
| - | )). Although SI is not a new concept to enterprises, the granularity and kinds components associated with a DIDO architecture requires a rethink. Within the DIDO environment, the definition of a platform shifts from hardware, [[dido:public:ra:xapend:xapend.a_glossary:o:os|operating system]], software languages, and services (i.e., web, app, database, etc.) components to the DIDO Platform components. It is the responsibility of the [[dido:public:ra:xapend:xapend.a_glossary:d:dido_platform|DIDO Platform]] to isolate the enterprise from the traditional platform concerns. | + | )). Although SI is not a new concept to enterprises, the granularity and kinds components associated with a DIDO architecture requires a rethink. Within the DIDO environment, the definition of a [[dido:public:ra:xapend:xapend.a_glossary:p:platform|platform]] shifts from hardware, [[dido:public:ra:xapend:xapend.a_glossary:o:os|operating system]], software languages, and services (i.e., web, app, database, etc.) components to the DIDO Platform components. It is the responsibility of the [[dido:public:ra:xapend:xapend.a_glossary:d:dido_platform|DIDO Platform]] to isolate the enterprise from the traditional platform concerns. |
| - | The granularity of the data elements within an enterprise can also shift to smaller more isolated objects, which represent only a portion of the traditional [[dido:public:ra:xapend:xapend.a_glossary:d:dm]]. In other words, the enterprise's data model is not going to be deployed into a single DIDO, nor should it. Enterprise data stores will continue and will be augmented by the DIDO. Some data will reside completely within the Enterprise data stores, some data will reside completely within the DIDO, and some data will straddle both. Data that straddles both will need more procedures and policies to ensure data integrity. | + | The granularity of the data elements within an enterprise can also shift to smaller more isolated objects, which represent only a portion of the traditional [[dido:public:ra:xapend:xapend.a_glossary:d:dm]]. In other words, the enterprise's data model is not going to be deployed into a single DIDO, nor should it. Enterprise data stores will continue and will be augmented by the DIDO. Some data will reside completely within the Enterprise data stores, some data will reside completely within the DIDO, and some data will straddle both. Data that straddles both will need more [[dido:public:ra:xapend:xapend.a_glossary:p:p_p|procedures and policies]] to ensure data integrity. |
| ==== Relevant Open Source Standards ==== | ==== Relevant Open Source Standards ==== | ||
dido/public/ra/xapend/xapend.e_tools/oss.1628703252.txt.gz · Last modified: 2021/08/11 13:34 by murphy
