Difference between revisions of "IEEE 1471"
(Created page with 'also referred to as ANSI/IEEE 1471. <blockquote>ANSI/IEEE. 2000. Recommended practice for architectural description for software-intensive systems. New York, NY: American Nation...') |
|||
| Line 4: | Line 4: | ||
===Annotation=== | ===Annotation=== | ||
| + | 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 19:07, 22 July 2011
also referred to as ANSI/IEEE 1471.
ANSI/IEEE. 2000. Recommended practice for architectural description for software-intensive systems. New York, NY: American National Standards Institute (ANSI)/Institute of Electrical and Electronics Engineers (IEEE), ANSI/IEEE 1471-2000.
Annotation
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 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.