Difference between revisions of "A Case for Service Systems Engineering"

From SEBoK
Jump to navigation Jump to 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...')
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
<blockquote>Complete Bibliographic Entry</blockquote>
+
<blockquote>Tien, J,M. and Berg, D. 2003. A Case for Service Systems Engineering. Journal of Systems Science and Systems Engineering 12 (1): 13-38.
  
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.
+
</blockquote>
  
 
==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.
 
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:'''
+
EXAMPLE:   If this is a primary reference for three articles, the below will be:
*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:
+
===The Service View of Engineered Systems===
 +
The authors examine services and service systems engineering. They defined a number of unique aspects of services that must be considered when defining and implementing the systems engineering methods for services.
  
===Article 1===
 
Annotation for Article 1.
 
  
===Article 2===
+
===Service Systems Engineering===
 
Annotation for Article 2.
 
Annotation for Article 2.
  
===Article 3===
+
===Fundamentals of Services===
 
Annotation for Article 3.
 
Annotation for Article 3.
 +
 +
===Properties of Services===
 +
Annotation for Article 4.
  
 
[[Category:Primary Reference]]
 
[[Category:Primary Reference]]

Revision as of 02:58, 19 August 2011

Tien, J,M. and Berg, D. 2003. A Case for Service Systems Engineering. Journal of Systems Science and Systems Engineering 12 (1): 13-38.

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.

EXAMPLE: If this is a primary reference for three articles, the below will be:

The Service View of Engineered Systems

The authors examine services and service systems engineering. They defined a number of unique aspects of services that must be considered when defining and implementing the systems engineering methods for services.


Service Systems Engineering

Annotation for Article 2.

Fundamentals of Services

Annotation for Article 3.

Properties of Services

Annotation for Article 4.