dido:public:ra:1.4_req:2_nonfunc:28_manageability:04_costs
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:28_manageability:04_costs [2020/11/20 21:03] nick ↷ Page moved from dido:public:ra:1.4_req:2_nonfunc:08_manageability:04_costs to dido:public:ra:1.4_req:2_nonfunc:28_manageability:04_costs |
dido:public:ra:1.4_req:2_nonfunc:28_manageability:04_costs [2021/08/18 10:49] (current) murphy |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== 4.2.5.2 Manageability Costs ====== | + | ====== 4.3.5.2 Manageability Costs ====== |
| - | [[dido:public:ra:1.4_req:2_nonfunc:08_manageability | Return to the Manageability]] | + | [[dido:public:ra:1.4_req:2_nonfunc:28_manageability| Return to the Manageability]] |
| - | : //It is no longer necessary to argue that managing enterprise computing systems is complex and time-consuming, or that the cost of managing Information Technology (IT) infrastructures far exceeds the hardware and software costs—numbers speak for themselves: IT operations account for 50%-80% of today's IT budgets, amounting to tens of billions of dollars yearly. Besides the bottom line, poor manageability also impacts reliability, availability, and security in harder-to-quantify ways. As human error becomes the dominant cause of unscheduled [[dido:public:ra:xapend:xapend.a_glossary:d:downtime|downtime]], we desire systems that are easier, cheaper, and quicker to manage.<sup>[[dido:public:ra:1.4_req:2_nonfunc:08_manageability#fnt__1 | 1)]]</sup> // | + | ===== About ===== |
| + | : //It is no longer necessary to argue that managing enterprise computing systems is complex and time-consuming, or that the cost of managing [[dido:public:ra:xapend:xapend.a_glossary:i:infotech]] infrastructures far exceeds the hardware and software costs—numbers speak for themselves: IT operations account for 50%-80% of today's IT budgets, amounting to tens of billions of dollars yearly. Besides the bottom line, poor [[dido:public:ra:xapend:xapend.a_glossary:m:manageability|manageability]] also impacts reliability, [[dido:public:ra:xapend:xapend.a_glossary:a:availability|availability]], and security in harder-to-quantify ways. As human error becomes the dominant cause of unscheduled [[dido:public:ra:xapend:xapend.a_glossary:d:downtime|downtime]], we desire systems that are easier, cheaper, and quicker to manage.<sup>[[dido:public:ra:1.4_req:2_nonfunc:28_manageability#fnt__1| 1)]]</sup> // | ||
| The cost of managing systems is expensive and is getting more expensive. This is particularly true when using [[dido:public:ra:xapend:xapend.a_glossary:s:server|servers]] that are aging. | The cost of managing systems is expensive and is getting more expensive. This is particularly true when using [[dido:public:ra:xapend:xapend.a_glossary:s:server|servers]] that are aging. | ||
| Line 14: | Line 15: | ||
| </figure> | </figure> | ||
| - | Although these are the costs of owning and operating physical servers, the trend is relevant to almost all IT systems including software. The costs of managing the software is analogous to maintenance of the hardware but is probably worse since application software is dependent on many more layers of hardware and software. For example, a software system sitting on multiple Operating Systems (i.e, Linux, Unix, Windows, MacOS, IOS and Android), using a [[dido:public:ra:xapend:xapend.a_glossary:d:dbms]], a Web Server and using Java, Python, JavaScript, HTML, CSS, and supporting multiple browser (i.e., Firefox, Chrome and Safari) soon is overwhelmed by just keeping each system up-to-date and working. Distributed systems can compound that problem because each node in the System Network needs to be managed as well. | + | Although these are the costs of owning and operating physical servers, the trend is relevant to almost all IT systems including software. The costs of managing the software is analogous to maintenance of the hardware but is probably worse since [[dido:public:ra:xapend:xapend.a_glossary:a:application|application]] software is dependent on many more layers of hardware and software. For example, a software system sitting on multiple [[dido:public:ra:xapend:xapend.a_glossary:o:os|Operating Systems]] (i.e, Linux, [[dido:public:ra:xapend:xapend.a_glossary:u:unix|Unix]], Windows, MacOS, IOS and Android), using a [[dido:public:ra:xapend:xapend.a_glossary:d:dbms]], a Web Server and using Java, Python, [[dido:public:ra:xapend:xapend.a_glossary:j:javascript|JavaScript]], HTML, CSS, and supporting multiple browser (i.e., Firefox, Chrome and Safari) soon is overwhelmed by just keeping each system up-to-date and working. [[dido:public:ra:xapend:xapend.a_glossary:d:distsystem|Distributed systems]] can compound that problem because each [[dido:public:ra:xapend:xapend.a_glossary:n:node|node]] in the System Network needs to be managed as well. |
| Granted, there are products and tools that can reduce the complexity of managing the various platforms easier and this is a big step towards helping manageability. But the overall [[dido:public:ra:xapend:xapend.a_glossary:g:goal|goal]] is always to have systems that are easier, cheaper, and quicker to manage. There is another way to think about manageability called the Bathtub Curve. Although Figure {{ref>bathtub1}} is targeted at hardware, there are similar things that effect software. Probably one of the biggest problems is that as the number of components in the system increase, the number of [[dido:public:ra:xapend:xapend.a_glossary:e:eol]] or [[dido:public:ra:xapend:xapend.a_glossary:e:eol | End of Sales(EoS)]] issues need to be addressed. For example, a system that runs on an Operating System, has to worry about the EoL of the operating system. If it uses a database, it has a similar problem. These are generally not a problem in the early stags of the a system's lifcycle and hopefully of minimum problem during its "useful Life" phase. But as the system ages, more and more EoL problems arise. The more [[dido:public:ra:xapend:xapend.a_glossary:c:cots]], [[dido:public:ra:xapend:xapend.a_glossary:g:gots]], [[dido:public:ra:xapend:xapend.a_glossary:m:mots]], and [[dido:public:ra:xapend:xapend.a_glossary:n:nots]] products used by the system, the longer the system exists there is an increase in risk to the system because each subsystem, component or modular need to be managed. | Granted, there are products and tools that can reduce the complexity of managing the various platforms easier and this is a big step towards helping manageability. But the overall [[dido:public:ra:xapend:xapend.a_glossary:g:goal|goal]] is always to have systems that are easier, cheaper, and quicker to manage. There is another way to think about manageability called the Bathtub Curve. Although Figure {{ref>bathtub1}} is targeted at hardware, there are similar things that effect software. Probably one of the biggest problems is that as the number of components in the system increase, the number of [[dido:public:ra:xapend:xapend.a_glossary:e:eol]] or [[dido:public:ra:xapend:xapend.a_glossary:e:eol | End of Sales(EoS)]] issues need to be addressed. For example, a system that runs on an Operating System, has to worry about the EoL of the operating system. If it uses a database, it has a similar problem. These are generally not a problem in the early stags of the a system's lifcycle and hopefully of minimum problem during its "useful Life" phase. But as the system ages, more and more EoL problems arise. The more [[dido:public:ra:xapend:xapend.a_glossary:c:cots]], [[dido:public:ra:xapend:xapend.a_glossary:g:gots]], [[dido:public:ra:xapend:xapend.a_glossary:m:mots]], and [[dido:public:ra:xapend:xapend.a_glossary:n:nots]] products used by the system, the longer the system exists there is an increase in risk to the system because each subsystem, component or modular need to be managed. | ||
| Line 21: | Line 22: | ||
| {{ :dido:public:ra:1.4_req:2_nonfunc:bathtubecurve.png?600 |}} | {{ :dido:public:ra:1.4_req:2_nonfunc:bathtubecurve.png?600 |}} | ||
| <caption>The Bathtub Curve<sup> | <caption>The Bathtub Curve<sup> | ||
| - | [[dido:public:ra:1.4_req:2_nonfunc:08_manageability#fn__1 | 1)]]</sup></caption> | + | [[dido:public:ra:1.4_req:2_nonfunc:28_manageability#fn__1| 1)]]</sup></caption> |
| </figure> | </figure> | ||
| + | |||
| + | ===== DIDO Specifics ===== | ||
| + | [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:04_costs | Return to Top]] | ||
| + | |||
| + | : <wrap hi><color red> To be added/expanded in future revisions of the DIDO RA </color></wrap> | ||
| + | |||
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||
| + | |||
dido/public/ra/1.4_req/2_nonfunc/28_manageability/04_costs.1605924202.txt.gz · Last modified: 2020/11/20 21:03 by nick
