Difference between revisions of "Modularity (glossary)"

From SEBoK
Jump to navigation Jump to search
(Created page with '<blockquote>''DEFINITION'' (Citation)</blockquote> If more than one definition, please copy/paste the code for the definition (above) and insert a number in parentheses at the b...')
 
m (Text replacement - "SEBoK v. 2.9, released 13 November 2023" to "SEBoK v. 2.9, released 20 November 2023")
(29 intermediate revisions by 7 users not shown)
Line 1: Line 1:
−
<blockquote>''DEFINITION'' (Citation)</blockquote>
+
<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>  
  
−
If more than one definition, please copy/paste the code for the definition (above) and insert a number in parentheses at the beginning of each definition (i.e. (1), (2), (3), etc.)  ‘’’Make sure to include the source citation at the end of the definition.’’’
+
<blockquote>(2) Software attributes that provide a structure of highly independent components.'' (ISO/IEC/IEEE 2010)</blockquote>
  
−
====Source(s)====
+
(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)''  
−
Please include the source(s) for the definition(s) above. The sources should be formatted using Chicago Manual of Style (15th ed.). Please see the [http://www.bkcase.org/fileadmin/bkcase/files/Wiki_Files__for_linking_/BKCASE_Reference_Guidance.pdf BKCASE Reference Guidance] for formatting.
 
  
−
If there is more than one definition, the source for each definition must be provided. Sources should be listed in alphabetical order by author.
+
===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===
−
'''This area is for the ''Glossary Term Owner'' to provide discussion on the context and uses of the term.  This is ''not'' where you should provide comments. '''  Please use the “Discussion” tab (above) to provide feedback if you are not the term owner.
+
also called localized capacity
  
−
Please note that if there is more than one definition, it is very important to provide information on the context of the different terms and to explain to the user why it is not possible to identify only one definition.  For example, is this an emerging concept for which there is still much research to be done?  Or have two different definitions emerged as the result of two different disciplines interacting with systems engineering?
+
[[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

SEBoK v. 2.9, released 20 November 2023
Retrieved from "https://sandbox.sebokwiki.org/index.php?title=Modularity_(glossary)&oldid=69867"