Difference between revisions of "Design (glossary)"

From SEBoK
Jump to navigation Jump to search
m (Text replacement - "<center>'''SEBoK v. 2.4, released 17 May 2021'''</center>" to "<center>'''SEBoK v. 2.5, released 15 October 2021'''</center>")
 
(15 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<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).'' </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>
  
====Source(s)====
+
===Sources===
ISO/IEC/IEEE 24765:2010 - Systems and software engineering – Vocabulary
+
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.
 
 
English dictionaries
 
  
 
===Discussion===
 
===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.
 
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:
+
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
 
 
 
(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)
 
 
 
Design covers several meanings in the English dictionaries:
 
 
 
1) to work out the structure or form of (something), as by making a sketch, outline, pattern, or plans
 
 
 
2) to plan and make (something) artistically or skillfully
 
 
 
3) to form or conceive in the mind; invent
 
 
 
4) to intend, as for a specific purpose; plan
 
 
 
5) a plan, sketch, or preliminary drawing
 
 
 
6) the arrangement or pattern of elements or features of an artistic or decorative work
 
 
 
7) a finished artistic or decorative creation
 
 
 
8) an end aimed at or planned for; intention; purpose
 
 
 
9) a coherent or purposeful pattern, as opposed to chaos
 
 
 
Origin: latin designare = to mark out, describe (with signs)
 
 
 
In French dictionaries the term has 2 main meanings:
 
 
 
a) an artistic view very similar to nb 2, 6, 7 above
 
 
 
b) the translation of "concevoir" = nb 1, 3, 4, 9 above
 
 
 
  
 +
#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.5, released 15 October 2021'''</center>
{{5comments}}
 

Latest revision as of 08:00, 15 October 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.5, released 15 October 2021