Difference between revisions of "Modularity (glossary)"
m (Text replacement - "SEBoK v. 2.9, released 13 November 2023" to "SEBoK v. 2.9, released 20 November 2023") |
|||
| (28 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | <blockquote>''(1) Degree to which a system or computer program is composed of discrete components such that a change to one component has minimal impact on other components.'' (ISO/IEC 2011)</blockquote> | |
| − | ==== | + | <blockquote>(2) Software attributes that provide a structure of highly independent components.'' (ISO/IEC/IEEE 2010)</blockquote> |
| − | + | ||
| + | (3) In a resilience context modularity is a system resilience principle that states that the functionality of a system should be distributed through various nodes of that system so that if a single node is damaged or destroyed, the remaining nodes will continue to function. Jackson (2016)Modularity is a component principle in the tolerance attribute grouping. Jackson (2016)'' | ||
| + | |||
| + | ===Sources=== | ||
| + | (1) ISO/IEC. 2011. ''Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - System and software quality models.'' Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC). ISO/ISO 25010:2011. | ||
| + | |||
| + | (2) ISO/IEC/IEEE. 2009. ''Systems and Software Engineering - System and Software Engineering Vocabulary (SEVocab).'' Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/ Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 24765:2009. | ||
| + | |||
| + | (3)Jackson, Scott. 2016. "Principles for Resilient Design - A Guide for Understanding and Implementation." In IRGC Resource Guide on Resilience, edited by I. Linkov. University of Lausanne, Switzerland: International Risk Governance Council (IRGC). | ||
===Discussion=== | ===Discussion=== | ||
| − | + | also called localized capacity | |
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
| + | |||
| + | <center>'''SEBoK v. 2.9, released 20 November 2023'''</center> | ||
Revision as of 22:58, 18 November 2023
(1) Degree to which a system or computer program is composed of discrete components such that a change to one component has minimal impact on other components. (ISO/IEC 2011)
(2) Software attributes that provide a structure of highly independent components. (ISO/IEC/IEEE 2010)
(3) In a resilience context modularity is a system resilience principle that states that the functionality of a system should be distributed through various nodes of that system so that if a single node is damaged or destroyed, the remaining nodes will continue to function. Jackson (2016)Modularity is a component principle in the tolerance attribute grouping. Jackson (2016)
Sources
(1) ISO/IEC. 2011. Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - System and software quality models. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC). ISO/ISO 25010:2011.
(2) ISO/IEC/IEEE. 2009. Systems and Software Engineering - System and Software Engineering Vocabulary (SEVocab). Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/ Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 24765:2009.
(3)Jackson, Scott. 2016. "Principles for Resilient Design - A Guide for Understanding and Implementation." In IRGC Resource Guide on Resilience, edited by I. Linkov. University of Lausanne, Switzerland: International Risk Governance Council (IRGC).
Discussion
also called localized capacity