dido:public:ra:1.4_req:2_nonfunc:28_manageability:06_system
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:06_system [2021/01/14 20:32] ian |
dido:public:ra:1.4_req:2_nonfunc:28_manageability:06_system [2022/01/22 16:24] (current) 50.19.247.197 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== 4.2.5.3 System Manageability Issues ====== | + | ====== 4.3.5.3 System Manageability Issues ====== |
| [[dido:public:ra:1.4_req:2_nonfunc:28_manageability| Return to the Manageability]] | [[dido:public:ra:1.4_req:2_nonfunc:28_manageability| Return to the Manageability]] | ||
| ===== About ===== | ===== About ===== | ||
| - | [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:06_system | Return to Top]] | ||
| ==== Subsystem, Component and Module Lifecycle Issues ==== | ==== Subsystem, Component and Module Lifecycle Issues ==== | ||
| //"Studies have shown the average software program lifespan over the last 20 years to be around 6-8 years. Longevity increases somewhat for larger programs, so for extremely large complex programs (i.e., over a million Lines of Code – LOC) the average climbs as high as 12-14 years."//((__Software Evolution__, Blog Post, Mitopia Technologies, [[https://mitosystems.com/software-evolution/]] | //"Studies have shown the average software program lifespan over the last 20 years to be around 6-8 years. Longevity increases somewhat for larger programs, so for extremely large complex programs (i.e., over a million Lines of Code – LOC) the average climbs as high as 12-14 years."//((__Software Evolution__, Blog Post, Mitopia Technologies, [[https://mitosystems.com/software-evolution/]] | ||
| - | )) Obviously, there is not just the lifespan of the target system, but there are independent lifespans for each version for each subsystem, module or component that is developed externally. For example, the Windows [[dido:public:ra:xapend:xapend.a_glossary:o:os]] first appeared in the mid 1980s with version 1.0.(( | + | )) Obviously, there is not just the lifespan of the target system, but there are independent lifespans for each version for each subsystem, [[dido:public:ra:xapend:xapend.a_glossary:m:module|module]] or component that is developed externally. For example, the Windows [[dido:public:ra:xapend:xapend.a_glossary:o:os]] first appeared in the mid 1980s with version 1.0.(( |
| __The History of Windows Operating Systems__, Vengie Beal, Webopedia, 2 Sugust 2018, Accessed 16 July 2020, [[https://www.webopedia.com/DidYouKnow/Hardware_Software/history_of_microsoft_windows_operating_system.html#windows-1]] | __The History of Windows Operating Systems__, Vengie Beal, Webopedia, 2 Sugust 2018, Accessed 16 July 2020, [[https://www.webopedia.com/DidYouKnow/Hardware_Software/history_of_microsoft_windows_operating_system.html#windows-1]] | ||
| )) and the current version is 10. About every 10 years, Microsoft release another major release of Windows. (( | )) and the current version is 10. About every 10 years, Microsoft release another major release of Windows. (( | ||
| __When will Microsoft end support for your version of Windows or Office?__, Ed Bott, 10 April 2018, ZDNet, Accessed 16 July 2020, [[https://www.zdnet.com/article/when-will-microsoft-pull-the-plug-on-your-version-of-windows-or-office/]] | __When will Microsoft end support for your version of Windows or Office?__, Ed Bott, 10 April 2018, ZDNet, Accessed 16 July 2020, [[https://www.zdnet.com/article/when-will-microsoft-pull-the-plug-on-your-version-of-windows-or-office/]] | ||
| - | )). IPV4 was originally available in 1883. Windows 7 was release in October 2009 and IPV4 was the dominate [[dido:public:ra:xapend:xapend.a_glossary:i:ip]]. By 2012, IPV6 gained dominance(( | + | )). [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:ipv4 | IPV4]] was originally available in 1883. Windows 7 was release in October 2009 and IPV4 was the dominate [[dido:public:ra:xapend:xapend.a_glossary:i:ip]]. By 2012, IPV6 gained dominance(( |
| - | __Six Years Since World Launch, IPv6 Now Dominant Internet Protocol for Many__, Internet Society, 6 June 2018, Accessed 16 July 2020, [[https://www.internetsociety.org/news/press-releases/2018/six-years-since-world-launch-ipv6-now-dominant-internet-protocol-for-many/]] | + | __Six Years Since World Launch, [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:ipv6 | IPv6]] Now Dominant Internet Protocol for Many__, Internet Society, 6 June 2018, Accessed 16 July 2020, [[https://www.internetsociety.org/news/press-releases/2018/six-years-since-world-launch-ipv6-now-dominant-internet-protocol-for-many/]] |
| )). Therefore, if your system was released in 20010 using IPV4 and Windows 7, by 2012 the network protocol needed to be upgraded which can have cascading maintenance effects throughout your system. By 2015, Windows 10 was released again having a cascading effect on upgrades. | )). Therefore, if your system was released in 20010 using IPV4 and Windows 7, by 2012 the network protocol needed to be upgraded which can have cascading maintenance effects throughout your system. By 2015, Windows 10 was released again having a cascading effect on upgrades. | ||
| Line 26: | Line 25: | ||
| </caption> | </caption> | ||
| </figure> | </figure> | ||
| + | |||
| + | : **Note:** Also see [[dido:public:ra:1.2_views:3_taxonomic:4_data_tax:02_state_taxonomy:data_in_motion]] for a further discussion of the DIDO Layers. | ||
| Line 31: | Line 32: | ||
| [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:06_system| Return to the Top]] | [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:06_system| Return to the Top]] | ||
| - | The fundamental [[dido:public:ra:xapend:xapend.a_glossary:r:requirement|requirement]] for manageability of any system is the collection of data about the system. This is often done with [[dido:public:ra:xapend:xapend.a_glossary:m:monitorsw]] specifically designed for this task. However, the task of monitoring complex, [[dido:public:ra:xapend:xapend.a_glossary:d:distsystem|distributed systems]] is often difficult and beyond the scope of any particular product. The best place to start is to think of the monitoring in terms of layers. There are considered three layers(( | + | The fundamental [[dido:public:ra:xapend:xapend.a_glossary:r:requirement|requirement]] for [[dido:public:ra:xapend:xapend.a_glossary:m:manageability|manageability]] of any system is the collection of data about the system. This is often done with [[dido:public:ra:xapend:xapend.a_glossary:m:monitorsw]] specifically designed for this task. However, the task of monitoring complex, [[dido:public:ra:xapend:xapend.a_glossary:d:distsystem|distributed systems]] is often difficult and beyond the scope of any particular product. The best place to start is to think of the monitoring in terms of layers. There are considered three layers(( |
| __Tools for Distributed Systems Monitoring__, Kufel, Łukasz, 1 December 2016, Foundations of Computing and Decision Sciences, Vol 41: 10.1515/fcds-2016-0014, [[https://www.researchgate.net/publication/311863266_Tools_for_Distributed_Systems_Monitoring/citation/download]] | __Tools for Distributed Systems Monitoring__, Kufel, Łukasz, 1 December 2016, Foundations of Computing and Decision Sciences, Vol 41: 10.1515/fcds-2016-0014, [[https://www.researchgate.net/publication/311863266_Tools_for_Distributed_Systems_Monitoring/citation/download]] | ||
| )). | )). | ||
| Line 43: | Line 44: | ||
| [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:06_system| Return to the Top]] | [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:06_system| Return to the Top]] | ||
| - | The Data Monitoring is the use of [[dido:public:ra:xapend:xapend.a_glossary:d:datalog]] to collect and store data for analysis to discover trends or record the events and actions of a application, a system, network. This allows for tracking of interactions using messages. Some of the commonly used logging levels are: | + | The Data Monitoring is the use of [[dido:public:ra:xapend:xapend.a_glossary:d:datalog]] to collect and store data for analysis to discover trends or record the events and actions of an [[dido:public:ra:xapend:xapend.a_glossary:a:application|application]], a system, or a network. This allows for tracking of interactions using messages. Some of the commonly used logging levels are: |
| <table debuglevel> | <table debuglevel> | ||
| Line 61: | Line 62: | ||
| [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:06_system| Return to the Top]] | [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:06_system| Return to the Top]] | ||
| - | [[dido:public:ra:xapend:xapend.a_glossary:p:projmansw]] is software used for project planning, scheduling, resource allocation and change management. It allows project managers (PMs), stakeholders and users to control costs and manage budgeting, quality management and documentation and also may be used as an administration system. Project management software is also used for collaboration and communication between project stakeholders. These tools can help throughout the system lifecycle from requirements analysis through to sun-setting the system. However, in a distributed system, these tools can play a significant role in determining the health of the each of the nodes, the network and the overall system of nodes. | + | [[dido:public:ra:xapend:xapend.a_glossary:p:projmansw]] is software used for project planning, scheduling, resource allocation and change management. It allows project managers (PMs), stakeholders and users to control costs and manage budgeting, quality management and documentation and also may be used as an administration system. Project management software is also used for collaboration and communication between project stakeholders. These tools can help throughout the system lifecycle, from requirement analysis through sun-setting the system. However, in a distributed system, these tools can play a significant role in determining the health of each node, the network and the overall system of nodes. |
| Although the publication on __Software Metrics for Predicting Maintainability__ (( | Although the publication on __Software Metrics for Predicting Maintainability__ (( | ||
| Line 114: | Line 115: | ||
| - | Not recognizing or managing the risks due this kind of unfortunate occurrence to the system (or project) might be expedient, but is in many ways irresponsible for systems (or projects) with a long lifespan. An alternative to the risks of OSS or proprietary vendor lock-in is the selection components that are standards based from a [[dido:public:ra:xapend:xapend.a_glossary:s:stdorg]] that offers a wider spectrum of vendors to chose from. | + | Not recognizing or managing the risks due this kind of unfortunate occurrence to the system (or project) might be expedient, but is in many ways irresponsible for systems (or projects) with a long lifespan. An alternative to the risks of OSS or proprietary vendor lock-in is the selection components that are standards based from a [[dido:public:ra:xapend:xapend.a_glossary:s:stdorg]] that offers a wider spectrum of vendors to choose from. |
| ===== DIDO Specifics ===== | ===== DIDO Specifics ===== | ||
| - | [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:06_system | Return to Top]] | + | [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:06_system | Return to the Top]] |
| - | <color #FF0000><todo>TBD</todo></color> | + | : <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/28_manageability/06_system.1610674366.txt.gz · Last modified: 2021/01/14 20:32 by ian
