dido:public:ra:1.4_req:2_nonfunc:14_reliability:01_matuity
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:14_reliability:01_matuity [2020/11/14 12:52] nick [Communities] |
dido:public:ra:1.4_req:2_nonfunc:14_reliability:01_matuity [2021/11/09 15:51] (current) char ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== 4.2.2.1 Maturity ====== | + | ====== 4.3.2.1 Maturity ====== |
| - | [[dido:public:ra:xapend:xapend.a_glossary | Return to Glossary ]] | + | [[dido:public:ra:xapend:xapend.a_glossary:start| Return to Glossary ]] |
| - | + | ||
| - | * **<color darkblue><todo @nick #char:2020-10-22>Char's review done</todo></color>** | + | |
| ===== About ===== | ===== About ===== | ||
| Line 15: | Line 13: | ||
| Product or System maturity is an assessment (sometimes quantifiable) of how well a product or system meets its requirements for reliability under normal operations. | Product or System maturity is an assessment (sometimes quantifiable) of how well a product or system meets its requirements for reliability under normal operations. | ||
| - | Maturity of the components selected for inclusion in a system can play a significant role in the overall success of a system. Components that are mature are more likely to be stable and reliable; qualities that directly translate to stable and reliable integrations, which are thereby robust and resilient when inevitable changes to the system are made. This holds true as long as the components are not coming close to [[dido:public:ra:xapend:xapend.a_glossary:e:eol]]. See [[dido:public:ra:1.4_req:2_nonfunc:08_manageability#manageability_costs | Manageability Costs ]]. | + | Maturity of the components selected for inclusion in a system can play a significant role in the overall success of a system. Components that are mature are more likely to be stable and reliable; qualities that directly translate to stable and reliable integrations, which are thereby robust and resilient when inevitable changes to the system are made. This holds true as long as the components are not coming close to [[dido:public:ra:xapend:xapend.a_glossary:e:eol]]. See [[dido:public:ra:1.4_req:2_nonfunc:28_manageability#manageability_costs| Manageability Costs ]]. |
| Rafa E. Al-Qutaish and Alain Abran have proposed a maturity model based on [[dido:public:ra:xapend:xapend.a_glossary:s:6sigma]].((Rafa E. Al-Qutaish and Alain Abran, __A Maturity Model of Software Product Quality__, Journal of Research and Practice in [[dido:public:ra:xapend:xapend.a_glossary:i:infotech|Information Technology]], 43(4):307-327, November 2011, Accessed 27 July 2020, [[https://www.researchgate.net/publication/260835325_A_Maturity_Model_of_Software_Product_Quality]] | Rafa E. Al-Qutaish and Alain Abran have proposed a maturity model based on [[dido:public:ra:xapend:xapend.a_glossary:s:6sigma]].((Rafa E. Al-Qutaish and Alain Abran, __A Maturity Model of Software Product Quality__, Journal of Research and Practice in [[dido:public:ra:xapend:xapend.a_glossary:i:infotech|Information Technology]], 43(4):307-327, November 2011, Accessed 27 July 2020, [[https://www.researchgate.net/publication/260835325_A_Maturity_Model_of_Software_Product_Quality]] | ||
| Line 64: | Line 62: | ||
| * [[dido:public:ra:xapend:xapend.a_glossary:i:iso15288]] | * [[dido:public:ra:xapend:xapend.a_glossary:i:iso15288]] | ||
| * [[dido:public:ra:xapend:xapend.a_glossary:i:iso90003]] | * [[dido:public:ra:xapend:xapend.a_glossary:i:iso90003]] | ||
| + | * [[dido:public:ra:xapend:xapend.b_stds:tech:iso:customer_satisfaction]] | ||
| + | * [[dido:public:ra:xapend:xapend.b_stds:tech:iso:customer_complaints]] | ||
| + | * [[dido:public:ra:xapend:xapend.b_stds:tech:iso:customer_dispute]] | ||
| + | * [[dido:public:ra:xapend:xapend.b_stds:tech:iso:quality_monitor_and_measure]] | ||
| + | * [[dido:public:ra:xapend:xapend.b_stds:tech:omg:cmmn]] | ||
| * [[dido:public:ra:xapend:xapend.a_glossary:c:cmmi]] | * [[dido:public:ra:xapend:xapend.a_glossary:c:cmmi]] | ||
| - | See also: [[dido:public:ra:xapend:xapend.b_stds:defact:todo]]. | + | See also: [[dido:public:ra:xapend:xapend.b_stds:defact:todo:start]]. |
| - | ===== DDS Specifics ===== | + | ===== DIDO Specifics ===== |
| [[dido:public:ra:1.4_req:2_nonfunc:14_reliability:01_matuity | Return to Top]] | [[dido:public:ra:1.4_req:2_nonfunc:14_reliability:01_matuity | Return to Top]] | ||
| - | There are several aspects to reviewing DDS for maturity: | ||
| - | |||
| - | * The maturity of the parent [[dido:public:ra:xapend:xapend.a_glossary:s:stdorg]] (i.e., the [[dido:public:ra:xapend:xapend.a_glossary:o:omg]]) -- OMG has been creating standard specifications for 35 years. | ||
| - | * The maturity of the standards themselves -- The [[dido:public:ra:xapend:xapend.a_glossary:d:data_distribution_service_dds]] is a family of specifications (i.e., [[ddsf:private:cookbook:06_append:01_family_of_standards | DDS Family of Standards]]). The DDS family of standards started in 2001 (see [[ddsf:private:cookbook:02_body:01_intro:00_history | History of DDS]]) with the release of DDS 1.0. The base DDS specification has been updated about every 3 to 4 years and has been extended to encompass just under 20 specifications, covering areas such as [[dido:public:ra:xapend:xapend.a_glossary:w:wireproro]], type systems, security and language bindings. | ||
| - | * The maturity of the [[ddsf:private:cookbook:06_append:05_vendors |DDS Vendors]] -- Two vendors have had DDS product offerings for about 20 years. [[ddsf:private:cookbook:06_append:05_vendors:rti |Real-Time Innovations (RTI)]] and [[ddsf:private:cookbook:06_append:05_vendors:thales|THALES]] (their original product was spun off to PrismTech, which has recently become part of [[ddsf:private:cookbook:06_append:05_vendors:adlink |Adlink]]). | ||
| - | * The maturity of the vendor's products -- In addition to the two original DDS vendors, there are a number of DDS products being offered by other DDS vendors; each product has its own maturity level. **Note:** just because a product is newer does not mean it is not as mature in terms of maturity metrics. Newer products have an advantage: not only are they starting from a more mature set of specifications, they are also able to use other products as reference implementations. | ||
| - | |||
| - | Each Vendor and each vendor product needs to be assessed independently. | ||
| /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
dido/public/ra/1.4_req/2_nonfunc/14_reliability/01_matuity.1605376323.txt.gz · Last modified: 2020/11/14 12:52 by nick
