dido:public:ra:1.4_req:2_nonfunc:10_portability:04_install
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:04_install [2021/06/09 00:07] char |
dido:public:ra:1.4_req:2_nonfunc:10_portability:04_install [2021/08/18 10:45] (current) murphy |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== About ===== | ===== About ===== | ||
| - | [[dido:public:ra:1.4_req:2_nonfunc:10_portability:04_install | Return to the Top]] | ||
| - | |||
| [[dido:public:ra:xapend:xapend.a_glossary:i:installability]] and its mirror [[dido:public:ra:xapend:xapend.a_glossary:r:requirement|requirement]] of un-installability allows for an individual product or an entire system to be installed and uninstalled on a system easily, efficiently and with a minimum number of side effects. A side effect occurs when removing a product or system has adverse effects on other products or systems running on the same computer or network. For example, when a product was installed, it installed a [[dido:public:ra:xapend:xapend.a_glossary:s:swlib|library]] to access a particular [[dido:public:ra:xapend:xapend.a_glossary:d:dbms]] but, in so doing, removed a library required to access a different DBMS. These side effects can also occur when a product or system is un-installed. For example, when a product is un-installed, it removes a library used to access a particular DBMS; however, this library is required by other products or systems on the computer or network. | [[dido:public:ra:xapend:xapend.a_glossary:i:installability]] and its mirror [[dido:public:ra:xapend:xapend.a_glossary:r:requirement|requirement]] of un-installability allows for an individual product or an entire system to be installed and uninstalled on a system easily, efficiently and with a minimum number of side effects. A side effect occurs when removing a product or system has adverse effects on other products or systems running on the same computer or network. For example, when a product was installed, it installed a [[dido:public:ra:xapend:xapend.a_glossary:s:swlib|library]] to access a particular [[dido:public:ra:xapend:xapend.a_glossary:d:dbms]] but, in so doing, removed a library required to access a different DBMS. These side effects can also occur when a product or system is un-installed. For example, when a product is un-installed, it removes a library used to access a particular DBMS; however, this library is required by other products or systems on the computer or network. | ||
| Line 12: | Line 10: | ||
| * The target system has the correct system resources available \\ | * The target system has the correct system resources available \\ | ||
| - | • Hardware architecture ([[dido:public:ra:xapend:xapend.a_glossary:00-9:32-bit]] or [[dido:public:ra:xapend:xapend.a_glossary:00-9:64-bit]] [[dido:public:ra:xapend:xapend.a_glossary:c:cpu]] etc) \\ | + | • Hardware architecture ([[dido:public:ra:xapend:xapend.a_glossary:00-9:32bit]] or [[dido:public:ra:xapend:xapend.a_glossary:00-9:64bit]] [[dido:public:ra:xapend:xapend.a_glossary:c:cpu]] etc) \\ |
| - | • [[dido:public:ra:xapend:xapend.a_glossary:o:os]] such as Android, IOS, Linux, MacOS, Windows, Unix, etc.) \\ | + | • [[dido:public:ra:xapend:xapend.a_glossary:o:os]] such as Android, IOS, Linux, MacOS, Windows, [[dido:public:ra:xapend:xapend.a_glossary:u:unix|Unix]], etc.) \\ |
| • Network connectivity \\ | • Network connectivity \\ | ||
| • Hardware resources such as memory, disk space, etc. \\ | • Hardware resources such as memory, disk space, etc. \\ | ||
| Line 30: | Line 28: | ||
| ^ Kind of Installer ^ Description ^ | ^ Kind of Installer ^ Description ^ | ||
| ^ **Attended installation** | This generally requires a user to attend the installation process to answer questions about where to do the install on the target system, provide information about the user, accept any terms and conditions, etc. <sup>[(notes:>**Note:** It is possible to have hybrids of these kinds of installers. For example, an installer is **Attended** for the first part of an installation and then unattended for the remainder of the installation)] </sup>| | ^ **Attended installation** | This generally requires a user to attend the installation process to answer questions about where to do the install on the target system, provide information about the user, accept any terms and conditions, etc. <sup>[(notes:>**Note:** It is possible to have hybrids of these kinds of installers. For example, an installer is **Attended** for the first part of an installation and then unattended for the remainder of the installation)] </sup>| | ||
| - | ^ **Silent installation** | This allows installation of a system or program on a target system without any notification to the user. This is often the backdoor used by malware. It differs from **Attended** and **Unattended** installations only in that the user may be completely unaware of the installation. | | + | ^ **Silent installation** | This allows installation of a system or program on a target system without any notification to the user. This is often the backdoor used by dido:public:ra:xapend:xapend.a_glossary:m:malware. It differs from **Attended** and **Unattended** installations only in that the user may be completely unaware of the installation. | |
| ^ **Unattended installation** | This installation is similar to the **Attended Installation** but does not require any human interaction, thus allowing for systems or programs to be installed with the user just monitoring the installation rather than interacting with it. | | ^ **Unattended installation** | This installation is similar to the **Attended Installation** but does not require any human interaction, thus allowing for systems or programs to be installed with the user just monitoring the installation rather than interacting with it. | | ||
| ^ **Headless installation** | This refers to the graphics head usually used to drive a monitor. If there is no graphics head, there are only command line interfaces and logs for detailing the installation process. Often these installations use Telnet where the installation on one computer (or machine) is being done from another computer (or machine). **Note:** could be a [[dido:public:ra:xapend:xapend.a_glossary:v:vm|virtual machine]]. | | ^ **Headless installation** | This refers to the graphics head usually used to drive a monitor. If there is no graphics head, there are only command line interfaces and logs for detailing the installation process. Often these installations use Telnet where the installation on one computer (or machine) is being done from another computer (or machine). **Note:** could be a [[dido:public:ra:xapend:xapend.a_glossary:v:vm|virtual machine]]. | | ||
| Line 49: | Line 47: | ||
| [[dido:public:ra:1.4_req:2_nonfunc:10_portability:04_install | Return to the Top]] | [[dido:public:ra:1.4_req:2_nonfunc:10_portability:04_install | Return to the Top]] | ||
| + | : <wrap hi><color red> To be added/expanded in future revisions of the DIDO RA </color></wrap> | ||
dido/public/ra/1.4_req/2_nonfunc/10_portability/04_install.1623211632.txt.gz · Last modified: 2021/06/09 00:07 by char
