Difference between revisions of "Systems Engineering Plan Outline"

From SEBoK
Jump to: navigation, search
(Created page with '<blockquote>Complete Bibliographic Entry</blockquote> Please note: bibliographic entries should follow Chicago Manual of Style (15th ed.). Please see [http://www.bkcase.org/fi...')
 
m (Text replacement - "<center>'''SEBoK v. 2.0, released 1 June 2019'''</center>" to "<center>'''SEBoK v. 2.1, released 31 October 2019'''</center>")
(14 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<blockquote>Complete Bibliographic Entry</blockquote>
+
<blockquote>DoD. 2011. ''Systems Engineering Plan Outline''. Washington, D.C., USA: Office of the Undersecretary of Defense (AT&L), U.S. Department of Defense (DoD).</blockquote>
  
Please note:  bibliographic entries should follow Chicago Manual of Style (15th ed.).  Please see [http://www.bkcase.org/fileadmin/bkcase/files/Wiki_Files__for_linking_/BKCASE_Reference_Guidance.pdf BKCASE Reference Guidance] for formatting.
+
==Usage==
 +
This source is considered a primary reference for the [[Procurement and Acquisition]] article.
  
==Annotation==
+
<center>'''SEBoK v. 2.1, released 31 October 2019'''</center>
A primary reference has been identified as the author team as a "key" reference, which is critically important to understanding a given topic. Each article will define a set of no more than 5-10 primary references. The general concept is that if a SEBoK user were to read the article on a topic and the Primary References, he or she would have a firm grasp on the principle concepts related to that article.
 
 
 
'''All primary reference pages will follow these guidelines:'''
 
*Article title is the title of reference. This may be the title of the book, article, etc.
 
*First item listed will be the complete bibliographic reference.  Please see [http://www.bkcase.org/fileadmin/bkcase/files/Wiki_Files__for_linking_/BKCASE_Reference_Guidance.pdf BKCASE Reference Guidance] for descriptions and examples of complete references.
 
*All primary reference articles will contain a 1-2 paragraph annotation with a description and explanation of value for the related topic(s).
 
 
 
'''Authors submitting primary references are responsible for providing the bibliographic entry and annotation.'''  If multiple authors use the same primary reference, ''each'' author must explain the value proposition to a user for that resource in terms of his/her own topics.  In this instance, there will be a heading for each article. 
 
 
 
EXAMPLE:  If this is a primary reference for three articles, the below will be:
 
 
 
===Article 1===
 
Annotation for Article 1.
 
 
 
===Article 2===
 
Annotation for Article 2.
 
 
 
===Article 3===
 
Annotation for Article 3.
 
  
 
[[Category:Primary Reference]]
 
[[Category:Primary Reference]]

Revision as of 08:55, 28 October 2019

DoD. 2011. Systems Engineering Plan Outline. Washington, D.C., USA: Office of the Undersecretary of Defense (AT&L), U.S. Department of Defense (DoD).

Usage

This source is considered a primary reference for the Procurement and Acquisition article.

SEBoK v. 2.1, released 31 October 2019