Difference between revisions of "Design (glossary)"
Wikiexpert (talk | contribs) |
|||
| Line 1: | Line 1: | ||
| − | <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/IEEE 24765:2009)</blockquote> |
====Source(s)==== | ====Source(s)==== | ||
| − | ISO/IEC/IEEE | + | 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=== | ===Discussion=== | ||
| Line 11: | Line 9: | ||
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: | ||
| − | + | #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) | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Design covers several meanings in the English dictionaries: | Design covers several meanings in the English dictionaries: | ||
| − | + | #to work out the structure or form of (something), as by making a sketch, outline, pattern, or plans; | |
| − | + | #to plan and make (something) artistically or skillfully; | |
| − | + | #to form or conceive in the mind; invent; | |
| − | + | #to intend, as for a specific purpose; plan; | |
| − | + | #a plan, sketch, or preliminary drawing; | |
| − | + | #the arrangement or pattern of elements or features of an artistic or decorative work; | |
| − | + | #a finished artistic or decorative creation; | |
| − | + | #an end aimed at or planned for; intention; purpose; or | |
| − | + | #a coherent or purposeful pattern, as opposed to chaos. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
Revision as of 14:49, 25 July 2012
(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/IEEE 24765:2009)
Source(s)
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:
- 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)
Design covers several meanings in the English dictionaries:
- to work out the structure or form of (something), as by making a sketch, outline, pattern, or plans;
- to plan and make (something) artistically or skillfully;
- to form or conceive in the mind; invent;
- to intend, as for a specific purpose; plan;
- a plan, sketch, or preliminary drawing;
- the arrangement or pattern of elements or features of an artistic or decorative work;
- a finished artistic or decorative creation;
- an end aimed at or planned for; intention; purpose; or
- a coherent or purposeful pattern, as opposed to chaos.
SEBoK Discussion
Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.
If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.
blog comments powered by Disqus