Difference between revisions of "Baseline (glossary)"
(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") |
||
| (32 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
| − | <blockquote>'' | + | <blockquote>''A specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change control procedures.'' (ISO/IEEE 2008)</blockquote> |
| − | + | ===Sources=== | |
| − | + | ISO/IEEE. 2008. ''Systems and Software Engineering — Software Life Cycle Processes''. Geneva, Switzerland: International Organization for Standards (ISO)/Institute of Electrical & Electronics Engineers (IEEE) Computer Society, ISO/IEEE 12207:2008(E). | |
| − | === | ||
| − | |||
| − | |||
| − | |||
===Discussion=== | ===Discussion=== | ||
| − | + | There are 7 definitions of baseline in the standards covered by the IEEE sevocab database. The included definition seems most appropriate for SEBoK use. See http://www.computer.org/sevocab for more detail. | |
| − | + | The [http://pascal.computer.org/sev_display/index.action SEVOCAB] entry provides 7 definitions followed by this note: ''A baseline should be changed only through formal configuration management procedures. Some baselines may be project deliverables while others provide the basis for further work. Baselines, plus approved changes from those baselines, constitute the current configuration identification.'' | |
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
| + | |||
| + | <center>'''SEBoK v. 2.9, released 20 November 2023'''</center> | ||
Revision as of 22:35, 18 November 2023
A specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change control procedures. (ISO/IEEE 2008)
Sources
ISO/IEEE. 2008. Systems and Software Engineering — Software Life Cycle Processes. Geneva, Switzerland: International Organization for Standards (ISO)/Institute of Electrical & Electronics Engineers (IEEE) Computer Society, ISO/IEEE 12207:2008(E).
Discussion
There are 7 definitions of baseline in the standards covered by the IEEE sevocab database. The included definition seems most appropriate for SEBoK use. See http://www.computer.org/sevocab for more detail.
The SEVOCAB entry provides 7 definitions followed by this note: A baseline should be changed only through formal configuration management procedures. Some baselines may be project deliverables while others provide the basis for further work. Baselines, plus approved changes from those baselines, constitute the current configuration identification.