dido:public:ra:1.4_req:2_nonfunc:10_portability:01_adapt
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.4_req:2_nonfunc:10_portability:01_adapt [2021/08/11 13:31] murphy |
dido:public:ra:1.4_req:2_nonfunc:10_portability:01_adapt [2021/08/18 10:48] (current) murphy |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| Nary Subramanian & Lawrence Chung<sup>1</sup> describe software architectures as composed of two elements: components and connectors. Adaptability in software can occur when either the components of the software change or the connectors between the software change. | Nary Subramanian & Lawrence Chung<sup>1</sup> describe software architectures as composed of two elements: components and connectors. Adaptability in software can occur when either the components of the software change or the connectors between the software change. | ||
| - | [[dido:public:ra:xapend:xapend.a_glossary:s:swadapt]] is when a software component with a well-defined, stable [[dido:public:ra:xapend:xapend.a_glossary:a:api]] can be exchanged using another component with minimal effort, as long as that component adheres to the API. For example, SQL describes an API for a database component. As long as the software adheres to the standard SQL API, the [[dido:public:ra:xapend:xapend.a_glossary:d:dbms]] can be exchanged between, for example, [[https://www.oracle.com/database/technologies/| Oracle]] and [[https://www.postgresql.org/ | PostgreSQL]], with no to minimal impact. /* tried to phrase this better to communicate the idea that we're just using swapping out Oracle with PostgreSQL as an example only .. or that we're saying that Oracle and PostgreSQL can swapped out .. something I'm not even sure can be done. Also corrected the spelling of PostgreSQL -- you were missing a "g" .. :-)*/ | + | [[dido:public:ra:xapend:xapend.a_glossary:s:swadapt]] is when a software component with a well-defined, stable [[dido:public:ra:xapend:xapend.a_glossary:a:api]] can be exchanged using another component with minimal effort, as long as that component adheres to the API. For example, [[dido:public:ra:xapend:xapend.a_glossary:s:sql|SQL]] describes an API for a database component. As long as the software adheres to the standard SQL API, the [[dido:public:ra:xapend:xapend.a_glossary:d:dbms]] can be exchanged between, for example, [[https://www.oracle.com/database/technologies/| Oracle]] and [[https://www.postgresql.org/ | PostgreSQL]], with no to minimal impact. /* tried to phrase this better to communicate the idea that we're just using swapping out Oracle with PostgreSQL as an example only .. or that we're saying that Oracle and PostgreSQL can swapped out .. something I'm not even sure can be done. Also corrected the spelling of PostgreSQL -- you were missing a "g" .. :-)*/ |
| - | [[dido:public:ra:xapend:xapend.a_glossary:a:archdaptability]] is when the connectors between software components change without having to change the components. This again comes down to having well-defined, stable APIs for the connectors. For example, the Unix File System (UnixFS) is a connector between software components and the physical filesystem. The associated UnixFS library can be exchanged for the [[https://ipfs.io/ | InterPlanetary File System (IPFS) ]] UnixFS connector and the software component should have no to minimal impact. | + | [[dido:public:ra:xapend:xapend.a_glossary:a:archdaptability]] is when the connectors between software components change without having to change the components. This again comes down to having well-defined, stable APIs for the connectors. For example, the [[dido:public:ra:xapend:xapend.a_glossary:u:unix|Unix]] File System (UnixFS) is a connector between software components and the physical filesystem. The associated UnixFS library can be exchanged for the [[https://ipfs.io/ | InterPlanetary File System (IPFS) ]] UnixFS connector and the software component should have no to minimal impact. |
| Nary Subramanian & Lawrence Chung<sup>1</sup> further define the following adaptability indices. | Nary Subramanian & Lawrence Chung<sup>1</sup> further define the following adaptability indices. | ||
| Line 28: | Line 28: | ||
| : <wrap hi> To be added/expanded in future revisions of the DIDO RA </wrap> | : <wrap hi> To be added/expanded in future revisions of the DIDO RA </wrap> | ||
| - | | + | |
| /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| /* To add a discussion page to this page, comment out the line that says | /* To add a discussion page to this page, comment out the line that says | ||
dido/public/ra/1.4_req/2_nonfunc/10_portability/01_adapt.1628703077.txt.gz · Last modified: 2021/08/11 13:31 by murphy
