dido:public:ra:1.4_req:2_nonfunc:28_manageability
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 [2020/11/20 21:03] nick ↷ Links adapted because of a move operation |
dido:public:ra:1.4_req:2_nonfunc:28_manageability [2021/06/11 14:50] (current) char |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== 4.2.5 Manageability ====== | + | ====== 4.3.5 Manageability ====== |
| [[dido:public:ra:1.4_req:2_nonfunc| Return to Non-Functional Requirements]] | [[dido:public:ra:1.4_req:2_nonfunc| Return to Non-Functional Requirements]] | ||
| - | * **<color #FF0000><todo @char>Please Review</todo></color>** | + | [[dido:public:ra:xapend:xapend.a_glossary:m:manageability]] is most important during the second half of [[dido:public:ra:xapend:xapend.a_glossary:s:syslifecycle|System Lifecycle]] phases (i.e. operation, maintenance, support). Manageability can greatly influence the recurring costs and can increase the chances of a failure. Often a system that is hard to manage is described as fragile since the smallest change can have dire consequences on the system's functionality. |
| - | [[dido:public:ra:xapend:xapend.a_glossary:m:manageability]] is most important during the second half of a [[dido:public:ra:xapend:xapend.a_glossary:s:syslifecycle|System Lifecycle]] phases (i.e. operation, maintenance, support). Manageability can greatly influence the recurring costs and can increase the chances of a failure. Often a system that hard to manage is described as fragile since the smallest of changes can have dire consequences on the systems functionality. | + | : //Manageability directly influences a system's [[dido:public:ra:1.4_req:2_nonfunc:14_reliability | reliability]], [[dido:public:ra:1.4_req:2_nonfunc:14_reliability:02_availability | availability]], [[dido:public:ra:1.4_req:2_nonfunc:25_security| security]], and safety; therefore, it is a key ingredient of system dependability.// |
| - | + | ||
| - | : //Manageability directly influences a system's [[dido:public:ra:1.4_req:2_nonfunc:14_reliability | reliability]], [[dido:public:ra:1.4_req:2_nonfunc:14_reliability:02_availability | availability]], [[dido:public:ra:1.4_req:2_nonfunc:25_security| security]], and safety, thus being a key ingredient of system dependability.// | + | |
| | | ||
| - | : //Just like security and safety, manageability is generally hard to retrofit in complex systems—it is always easier to build it in from day one. However, in the absence of means to measure manageability and to quantify the various tradeoffs, it is difficult to get the design right. We proposed a manageability metric that combines management workloads and weightings based on real world studies with direct measurement of the number of steps involved in management tasks and their duration. (( | + | : //Just like security and safety, manageability is generally hard to retrofit in complex systems—it is always easier to build it in from day one. However, in the absence of means to measure manageability and quantify the various tradeoffs, it is difficult to get the design right. We proposed a manageability metric that combines management workloads and weightings based on real world studies with direct measurement of the number of steps involved in management tasks and their duration. (( |
| __Toward Quantifying System Manageability__, George Cadea, École Polytechnique Fédérale de Lausanne (EPFL), Switzerland, Accessed 20 July 2020, [[https://www.usenix.org/legacy/event/hotdep08/tech/full_papers/candea/candea_html/index.html]] | __Toward Quantifying System Manageability__, George Cadea, École Polytechnique Fédérale de Lausanne (EPFL), Switzerland, Accessed 20 July 2020, [[https://www.usenix.org/legacy/event/hotdep08/tech/full_papers/candea/candea_html/index.html]] | ||
| ))// | ))// | ||
| Line 16: | Line 14: | ||
| * [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:06_system]] | * [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:06_system]] | ||
| * [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:08_software]] | * [[dido:public:ra:1.4_req:2_nonfunc:28_manageability:08_software]] | ||
| + | ===== DIDO Specifics ===== | ||
| + | [[dido:public:ra:1.4_req:2_nonfunc:28_manageability| Return to the Top]] | ||
| - | + | : <wrap hi><color red> To be added/expanded in future revisions of the DIDO RA </color></wrap> | |
| - | ===== DDS Specifics ===== | + | |
| - | [[dido:public:ra:1.4_req:2_nonfunc:08_manageability | Return to the Top]] | + | |
| - | + | ||
| - | [[dido:public:ra:xapend:xapend.a_glossary:d:dds]] can not solve all of a systems(or projects) [[dido:public:ra:xapend:xapend.a_glossary:m:maintainability]] issues, however, by DDS's design, it can eliminate or reduce the Manageability issues that could arrise from using DDS. | + | |
| - | + | ||
| - | <table managefunc> | + | |
| - | <caption>DDS role in helping Manageability</caption> | + | |
| - | ^ Kinds of Management ^ Description ^ | + | |
| - | ^ **Health Monitoring, Logging, and Alerting** | Although there are currently no [[dido:public:ra:xapend:xapend.a_glossary:d:dds|DDS]] standards for that directly supports System Monitoring, each of the DDS Vendors have sets of tools which can be used for that purpose. These tools include <WRAP> | + | |
| - | * Development and troubleshooting including specialized network sniffers, modeling tools, and code generators | + | |
| - | * System monitoring and administration including terminals, shared memory management tools, recorders and replayers | + | |
| - | * Functional, systems and performance testing | + | |
| - | * Federated [[dido:public:ra:xapend:xapend.a_glossary:d:discovery|Discovery]] | + | |
| - | * Bridges to other [[dido:public:ra:xapend:xapend.a_glossary:m:mom]] products | + | |
| - | * Topic aggregators | + | |
| - | </WRAP> | | + | |
| - | ^ **Configuration and Control** | DDS uses a standardized Discovery process which eliminates most of need for configuration. Some [[ddsf:private:cookbook:06_append:05_vendors | DDS Vendors]] offer specialized or advanced tools that aid in tuning DDS configurations and discovering performance issues| | + | |
| - | ^ **Deployment and Updates** | DDS [[ddsf:private:cookbook:06_append:01_family_of_standards:01_core:dds_extensible_types_dds-xtypes | Extensible and Dynamic Topic Types for DDS (DDS-XTypes)]] allows for planned evolution of the [[dido:public:ra:xapend:xapend.a_glossary:d:datatype | Datatypes]] within a [[dido:public:ra:xapend:xapend.a_glossary:d:ddsapplication]]. For example, adding or removing fields in a [[dido:public:ra:xapend:xapend.a_glossary:d:datastructure]], changing the basic type from an int16 to an int32, etc. | | + | |
| - | ^ **Asset Discovery and Inventory** | DDS automatically registers all [[dido:public:ra:xapend:xapend.a_glossary:d:data_writer | Data Writer]] and [[dido:public:ra:xapend:xapend.a_glossary:d:data_reader | Data Reader]] allowing them to be discovered. It is possible| | + | |
| - | </table> | + | |
| /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
dido/public/ra/1.4_req/2_nonfunc/28_manageability.1605924230.txt.gz · Last modified: 2020/11/20 21:03 by nick
