Difference between revisions of "Design (glossary)"

From SEBoK
Jump to: navigation, 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 - "<center>'''SEBoK v. 2.3, released 30 October 2020'''</center>" to "<center>'''SEBoK v. 2.4, released 17 May 2021'''</center>")
 
(22 intermediate revisions by 6 users not shown)
Line 1: Line 1:
<blockquote>''DEFINITION'' (Citation)</blockquote>
+
<blockquote>''(System) design includes activities to create concepts and models, and/or to conceive something (a system / a solution that answers an intended purpose) based on or using principles and concepts; the outcome of design activities is a coherent and purposeful set of models or representations using defined constructs and patterns (that implement principles and concepts).'' (ISO/IEC/IEEC 2009)</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.’’’
+
===Sources===
 +
ISO/IEC/IEEE. 2009. ''Systems and Software Engineering - System and Software Engineering Vocabulary''. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/ Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 24765:2009.
  
====Source(s)====
+
===Discussion===
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.
+
The definition provided above is a synthesis and adapted to systems of several understanding to the term "Design" as found in the sources cited.
 
 
If there is more than one definition, the source for each definition must be provided.  Sources should be listed in alphabetical order by author.
 
  
===Discussion===
+
In ISO/IEC/IEEE 24765:2010 - ''Systems and software engineering – Vocabulary'', "design" means:
'''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.
 
  
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?
+
#the process of defining the architecture, components, interfaces, and other characteristics of a system or component;
 +
#the result of the process in (1);
 +
#the process of defining the software architecture, components, modules, interfaces, and data for a software system to satisfy specified requirements;
 +
#the process of conceiving, inventing, or contriving a scheme for turning a computer program specification into an operational program;
 +
#activity that links requirements analysis to coding and debugging; or
 +
#stage of documentation development that is concerned with determining what documentation will be provided in a product and what the nature of the documentation will be (ISO/IEC 26514:2008 Systems and software engineering--requirements for designers and developers of user documentation, 4.13)
  
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]
 +
 +
<center>'''SEBoK v. 2.4, released 17 May 2021'''</center>

Latest revision as of 08:00, 6 May 2021

(System) design includes activities to create concepts and models, and/or to conceive something (a system / a solution that answers an intended purpose) based on or using principles and concepts; the outcome of design activities is a coherent and purposeful set of models or representations using defined constructs and patterns (that implement principles and concepts). (ISO/IEC/IEEC 2009)

Sources

ISO/IEC/IEEE. 2009. Systems and Software Engineering - System and Software Engineering Vocabulary. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/ Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 24765:2009.

Discussion

The definition provided above is a synthesis and adapted to systems of several understanding to the term "Design" as found in the sources cited.

In ISO/IEC/IEEE 24765:2010 - Systems and software engineering – Vocabulary, "design" means:

  1. the process of defining the architecture, components, interfaces, and other characteristics of a system or component;
  2. the result of the process in (1);
  3. the process of defining the software architecture, components, modules, interfaces, and data for a software system to satisfy specified requirements;
  4. the process of conceiving, inventing, or contriving a scheme for turning a computer program specification into an operational program;
  5. activity that links requirements analysis to coding and debugging; or
  6. stage of documentation development that is concerned with determining what documentation will be provided in a product and what the nature of the documentation will be (ISO/IEC 26514:2008 Systems and software engineering--requirements for designers and developers of user documentation, 4.13)
SEBoK v. 2.4, released 17 May 2021