Difference between revisions of "Traceability (glossary)"

From SEBoK
Jump to navigation Jump to search
(Created a new page due to a new term request by the Co-EIC for v. 1.1.)
 
Line 1: Line 1:
<blockquote>''Definition.'' (Citation)</blockquote>
+
<blockquote>The degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or master-subordinate relationship to one another (IEEE 1233-1998 (R2002) IEEE Guide for Developing System Requirements Specifications, 3.1.9) </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)) ‘Make sure to include the source citation at the end of the definition.’
 
  
 
====Source[s]====
 
====Source[s]====
Please include the source(s) for the definition(s) aboveThe 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.
+
IEEE1998''IEEE Guide for Developing System Requirements Specifications.'' New York, NY: Institute of Electrical and Electronics Engineers (IEEE), IEEE 1233-1998.
 
 
If there is more than one definition, the source for each definition must be provided. Sources should be listed in the same order as the definitions, with the same identifier (i.e. (1), (2), (3))
 
  
 
===Discussion===
 
===Discussion===
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?
+
SEVOCAB lists other, similar definitions.   
 
 
'''This area is for the ''Glossary Term Owner'' to provide discussion on the context and uses of the termThis is ''not'' where you should provide comments. Please use the DISQUS feature (below) to provide feedback if you are not the term owner.'''
 
  
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]
  
 
{{DISQUS}}
 
{{DISQUS}}

Revision as of 19:17, 18 April 2013

The degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or master-subordinate relationship to one another (IEEE 1233-1998 (R2002) IEEE Guide for Developing System Requirements Specifications, 3.1.9)


Source[s]

IEEE. 1998. IEEE Guide for Developing System Requirements Specifications. New York, NY: Institute of Electrical and Electronics Engineers (IEEE), IEEE 1233-1998.

Discussion

SEVOCAB lists other, similar definitions.


SEBoK v. 1.9.1 released 30 September 2018

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