https://sebokwiki.org/w/api.php?action=feedcontributions&user=Dhenry&feedformat=atomSEBoK - User contributions [en]2024-03-28T13:25:42ZUser contributionsMediaWiki 1.35.13https://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=49145SEBoK Review and Adjudication2013-11-15T19:04:46Z<p>Dhenry: /* Adjudication Process */</p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is included in the adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under a [[Acknowledgements#BKCASE_Governance|new governance structure]]. The adjudication process described here is not applicable to these releases (versions 1.1. and beyond). Also, with every new release of the SEBoK since v. 1.1.2, the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] is also opened to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1 and beyond===<br />
Beginning in January 2013, the SEBoK is operating under a new governance structure led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). The SEBoK wiki continues to accept comments at the bottom of every page, but comments and various other types of contributions are also accepted through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox]. Adjudication matrices are no longer prepared or published.<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs, and contributions are being received in a variety of ways. The [[Meet_the_Editors |BKCASE associate and assistant editors]] actively adjudicate comments received, incorporating necessary changes in the next release of the SEBoK. The adjudication process described here is not applicable to releases v. 1.1 and beyond. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=49144SEBoK Review and Adjudication2013-11-15T19:02:45Z<p>Dhenry: /* SEBoK v. 1.1 and beyond */</p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is included in the adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under a [[Acknowledgements#BKCASE_Governance|new governance structure]]. The adjudication process described here is not applicable to these releases (versions 1.1. and beyond). Also, with every new release of the SEBoK since v. 1.1.2, the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] is also opened to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1 and beyond===<br />
Beginning in January 2013, the SEBoK is operating under a new governance structure led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). The SEBoK wiki continues to accept comments at the bottom of every page, but comments and various other types of contributions are also accepted through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox]. Adjudication matrices are no longer prepared or published.<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs, and contributions are being received in a variety of ways. The adjudication process described here is not applicable to releases v. 1.1 and beyond. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=49143SEBoK Review and Adjudication2013-11-15T19:02:17Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is included in the adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under a [[Acknowledgements#BKCASE_Governance|new governance structure]]. The adjudication process described here is not applicable to these releases (versions 1.1. and beyond). Also, with every new release of the SEBoK since v. 1.1.2, the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] is also opened to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1 and beyond===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). The SEBoK wiki continues to accept comments at the bottom of every page, but comments and various other types of contributions are also accepted through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox]. Adjudication matrices are no longer prepared or published.<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs, and contributions are being received in a variety of ways. The adjudication process described here is not applicable to releases v. 1.1 and beyond. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=49142SEBoK Review and Adjudication2013-11-15T19:01:41Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is included in the adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under a [[Acknowledgements#BKCASE_Governance|new governance structure]]. The adjudication process described here is not applicable to these releases (versions 1.1. and beyond). Also, since SEBoK v. 1.1.2, with every new release of the SEBoK the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] is also opened to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1 and beyond===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). The SEBoK wiki continues to accept comments at the bottom of every page, but comments and various other types of contributions are also accepted through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox]. Adjudication matrices are no longer prepared or published.<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs, and contributions are being received in a variety of ways. The adjudication process described here is not applicable to releases v. 1.1 and beyond. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=49141SEBoK Review and Adjudication2013-11-15T18:58:46Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is included in the adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under a [[Acknowledgements#BKCASE_Governance|new governance structure]]. The adjudication process described here is not applicable to these releases (versions 1.1. and beyond). Also, since SEBoK v. 1.1.2, with every new release of the SEBoK the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] is also opened to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1 and beyond===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). The SEBoK wiki continues to accept comments at the bottom of every page, but comments and various other types of contributions are also accepted through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox]. <br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=49140SEBoK Review and Adjudication2013-11-15T18:55:50Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is included in the adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under a [[Acknowledgements#BKCASE_Governance|new governance structure]]. The adjudication process described here is not applicable to these releases (versions 1.1. and beyond). Also, since SEBoK v. 1.1.2, during every new release of the SEBoK the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] is also opened to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1 and beyond===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox].<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=49139SEBoK Review and Adjudication2013-11-15T18:54:51Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is included in the adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under a [[Acknowledgements#BKCASE_Governance|new governance structure]]. The adjudication process described here is not applicable to these releases (version 1.1. and beyond). Along with SEBoK v. 1.1.2, the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] has been setup to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1 and beyond===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox].<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=49138SEBoK Review and Adjudication2013-11-15T18:54:10Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is included in the adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under a [[Acknowledgements#BKCASE_Governance|new governance structure]]. The adjudication process described here is not applicable to for these releases. Along with SEBoK v. 1.1.2, the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] has been setup to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1 and beyond===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox].<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=49137SEBoK Review and Adjudication2013-11-15T18:53:34Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is included in the adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under a [[Acknowledgements#New_Governance|new governance structure]]. The adjudication process described here is not applicable to for these releases. Along with SEBoK v. 1.1.2, the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] has been setup to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1 and beyond===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox].<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=49136SEBoK Review and Adjudication2013-11-15T18:53:08Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is included in the adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under a new governance structure. The adjudication process described here is not applicable to for these releases. Along with SEBoK v. 1.1.2, the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] has been setup to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1 and beyond===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox].<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=49135SEBoK Review and Adjudication2013-11-15T18:52:52Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is included in adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under a new governance structure. The adjudication process described here is not applicable to for these releases. Along with SEBoK v. 1.1.2, the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] has been setup to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1 and beyond===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox].<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=49132SEBoK Review and Adjudication2013-11-15T18:47:33Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is also included in adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under a new governance structure. The adjudication process described here is not applicable to for these releases. Along with SEBoK v. 1.1.2, the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] has been setup to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1 and beyond===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox].<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=49131SEBoK Review and Adjudication2013-11-15T18:46:43Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is also included in adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under a [[Acknowledgements#New_Governance|new governance structure]]. The adjudication process described here is not applicable to for these releases. Along with SEBoK v. 1.1.2, the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] has been setup to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1, v. 1.1.1, and v. 1.1.2===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox].<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=49130SEBoK Review and Adjudication2013-11-15T18:46:05Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is also included in adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under a [[www.sebokwiki.org/wiki/Acknowledgements#New_Governance|| new governance structure]. The adjudication process described here is not applicable to for these releases. Along with SEBoK v. 1.1.2, the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] has been setup to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1, v. 1.1.1, and v. 1.1.2===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox].<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=49129SEBoK Review and Adjudication2013-11-15T18:44:09Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is also included in adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under a new governance structure. The adjudication process described here is not applicable to for these releases. Along with SEBoK v. 1.1.2, the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] has been setup to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1, v. 1.1.1, and v. 1.1.2===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox].<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Systems_Engineering_Plan_(SEP)_(glossary)&diff=48945Systems Engineering Plan (SEP) (glossary)2013-11-06T14:33:17Z<p>Dhenry: /* Discussion */</p>
<hr />
<div>''<blockquote>A systems engineering plan (SEP) is a "living" document that captures a program's current and evolving systems engineering strategy and its relationship with the overall program management effort. The SEP purpose is to guide all technical aspects of the program. It should be established early in the Materiel Solution Analysis phase and updated continually.'' (DAU 2012)</blockquote><br />
<br />
===Source===<br />
DAU 2012. "Systems Engineering Plan (SEP)." (online). Virginia, USA: ACQuipedia. Your Online Acquisition Encyclopedia. Accessed on 11 September 2012. Available at: https://acc.dau.mil/ILC_SEP.<br />
<br />
===Discussion===<br />
In many contexts, the Systems Engineering Plan (SEP) and Systems Engineering Management Plan (SEMP) are used interchangeably, to refer to the highest level technical plan. However, in the context of the U.S. Department of Defense the context, intent, and content of these documents are quite different:<br />
* The SEP is a high-level plan that is made before the system acquisition and development begins. It is written by the government customer. <br />
*The SEMP is the specific development plan written by the developer (or contractor).<br />
<br />
[[Category:Glossary of Terms]]<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Decision_Management&diff=48901Decision Management2013-11-05T16:48:44Z<p>Dhenry: /* Developing Objectives and Measures */</p>
<hr />
<div>Many systems engineering decisions are difficult because they include numerous stakeholders, multiple competing objectives, substantial uncertainty, and significant consequences. In these cases, good decision making requires a formal [[Decision Management (glossary)| decision management]] process. The purpose of the decision management process is:<br />
<blockquote>“…to provide a structured, analytical framework for identifying, characterizing and evaluating a set of alternatives for a decision at any point in the life-cycle and select the most beneficial course of action.” (ISO/IEC 15288:2008)</blockquote> <br />
<br />
Decision situations ([[Opportunity (glossary)|opportunities]]) are commonly encountered throughout a [[Life Cycle (glossary)|system’s lifecycle]]. The decision management method most commonly employed by systems engineers is the trade study. Trade studies aim to define, measure, and assess shareholder and [[stakeholder (glossary)|stakeholder]] [[Value (glossary) | value]] to facilitate the decision maker’s search for an alternative that represents the best balance of competing objectives. By providing techniques for decomposing a trade decision into logical segments and then synthesizing the parts into a coherent whole, a decision management process allows the decision maker to work within human cognitive limits without oversimplifying the problem. Furthermore, by decomposing the overall decision problem, experts can provide assessments of alternatives in their area of expertise. <br />
<br />
==Decision Management Process==<br />
The decision analysis process is depicted in Figure 1 below. The decision management process is based on several best practices, including:<br />
*Utilizing sound mathematical technique of decision analysis for trade off studies (Parnell, 2009) provided a list of decision analysis concepts and techniques).<br />
*Developing one master decision model, followed by its refinement, update, and use, as it required for trade studies throughout the system life cycle.<br />
*Using Value-Focused Thinking (Keeney, 1992) to create better alternatives. <br />
*Identifying uncertainty and assessing risks for each decision.<br />
<br />
[[File:Decision_Mgt_Process_DM.png|thumb|center|650px|center|'''Figure 1. Decision Management Process (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
The center of the diagram shows the five trade space objectives. The ten blue arrows represent the decision management process activities and the white text within the green ring represents SE process elements. Interactions are represented by the small, dotted green or blue arrows. The decision analysis process is an iterative process. <br />
A hypothetical UAV decision problem is used to illustrate each of the activities in the following sections. <br />
<br />
===Framing and Tailoring the Decision===<br />
To ensure the decision team fully understands the decision context, the analyst should describe the system baseline, boundaries and interfaces. The decision context includes: the system definition, the life cycle stage, decision milestones, a list of decision makers and stakeholders, and available resources. The best practice is to identify a decision problem statement that defines the decision in terms of the system life cycle.<br />
<br />
===Developing Objectives and Measures===<br />
Defining how an important decision will be made is difficult. As Keeney puts it:<br />
<blockquote>''Most important decisions involve multiple objectives, and usually with multiple-objective decisions, you can't have it all. You will have to accept less achievement in terms of some objectives in order to achieve more on other objectives. But how much less would you accept to achieve how much more?'' (Keeney 2002)</blockquote><br />
The first step is to develop objectives and measures using interviews and focus groups with subject matter experts (SMEs) and stakeholders.<br />
For systems engineering trade-off analyses, stakeholder value often includes competing objectives of performance, development schedule, unit cost, support costs, and growth potential. For corporate decisions, shareholder value would also be added to this list. For performance, a functional decomposition can help generate a thorough set of potential objectives. Test this initial list of fundamental objectives by checking that each fundamental objective is essential and controllable and that the set of objectives is complete, non-redundant, concise, specific, and understandable (Edwards et al. 2007). Figure 2 provides an example of an objectives hierarchy.<br />
<br />
[[File:Fund_Obj_Hierarchy_DM.png|thumb|center|650px|center|'''Figure 2. Fundamental Objectives Hierarchy (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
For each objective, we define a measure to assess the value of each alternative for that objective. A measure (attribute, criterion, and metric) must be unambiguous, comprehensive, direct, operational, and understandable (Keeney & Gregory 2005).<br />
A defining feature of multi-objective decision analysis is the transformation from measure space to value space. This transformation is performed by a value function which shows returns to scale on the measure range. When creating a value function, we ascertain the walk-away point on the measure scale (x-axis) and map it to a 0 value on the value scale (y-axis). A walk-away point is the measure score where regardless of how well an alternative performs in other measures, the decision maker will walk away from the alternative. He or she does this through working with the user, finding the measure score beyond, at which point an alternative provides no additional value, and labeling it "stretch goal" (ideal) and then mapping it to 100 (or 1 and 10) on the value scale (y-axis). Figure 3 provides the most common value curve shapes. The rationale for the shape of the value functions should be documented for traceability and defensibility (Parnell et al. 2011).<br />
<br />
[[File:Value_Function_Example_DM.png|thumb|center|750px|center|'''Figure 3. Value Function Examples (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
The mathematics of multiple objective decision analysis (MODA) requires that the weights depend on importance of the measure and the range of the measure (walk away to stretch goal). A useful tool for determining priority weighting is the swing weight matrix (Parnell et al. 2011). For each measure, consider its importance through determining whether the measure corresponds to a defining, critical, or enabling function and consider the gap between the current capability and the desired capability; finally, put the name of the measure in the appropriate cell of the matrix (Figure 4). The highest priority weighting is placed in the upper-left corner and assigned an unnormalized weight of 100. The unnormalized weights are monotonically decreasing to the right and down the matrix. Swing weights are then assessed by comparing them to the most important value measure or another assessed measure. The swing weights are normalized to sum to one for the additive value model used to calculate value in a subsequent section. <br />
<br />
[[File:Swing_Weight_Matrix_DM.png|thumb|center|750px|center|'''Figure 4. Swing Weight Matrix (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
===Generating Creative Alternatives===<br />
<br />
To help generate a creative and comprehensive set of alternatives that span the decision space, consider developing an alternative generation table (also called a morphological box) (Buede, 2009; Parnell et al. 2011). It is a best practice to establish a meaningful product structure for the system and to be reported in all decision presentations (Figure 5). <br />
<br />
[[File:Descript_of_Alt_DM.png|thumb|center|750px|center|'''Figure 5. Descriptions of Alternatives (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
===Assessing Alternatives via Deterministic Analysis===<br />
<br />
With objectives and measures established and alternatives having been defined, the decision team should engage SMEs, equipped with operational data, test data, simulations, models, and expert knowledge. Scores are best captured on scoring sheets for each alternative/measure combination which document the source and rationale. Figure 6 provides a summary of the scores. <br />
<br />
[[File:ALT_Scores_DM.png|thumb|center|750px|center|'''Figure 6. Alternative Scores (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
Note that in addition to identified alternatives, the score matrix includes a row for the ideal alternative. The ideal is a tool for value-focused thinking, which will be covered later.<br />
<br />
===Synthesizing Results===<br />
<br />
Next, one can transform the scores into a value table, by using the value functions developed previously. A color heat map can be useful to visualize value tradeoffs between alternatives and identify where alternatives need improvement (Figure 7).<br />
<br />
[[File:Value_Scorecard_w_Heat_Map_DM.png|thumb|center|850px|center|'''Figure 7. Value Scorecard with Heat Map (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
The additive value model uses the following equation to calculate each alternative’s value:<br />
<br />
EQUATION HERE<br />
<br />
where<br />
<br />
EQUATION VALUES HERE<br />
<br />
The value component chart (Figure 8) shows the total value and the weighted value measure contribution of each alternative (Parnell et al. 2011). <br />
<br />
[[File:Value_Comp_Graph_DM.png|thumb|center|700px|center|'''Figure 8. Value Component Graph (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
The heart of a decision management process for system engineering trade off analysis is the ability to assess all dimensions of shareholder and stakeholder value. The stakeholder value scatter plot in Figure 9 shows five dimensions: unit cost, performance, development risk, growth potential, and operation and support costs for all alternatives.<br />
<br />
[[File:Ex_Stakeholder_Value_Scat_DM.png|thumb|center|700px|center|'''Figure 9. Example of a Stakeholder Value Scatterplot (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
Each system alternative is represented by a scatter plot marker (Figure 9). An alternative’s unit cost and performance value are indicated by x and y positions respectively. An alternative’s development risk is indicated by the color of the marker (green = low, yellow= medium, red = high), while the growth potential is shown as the number of hats above the circular marker (1 hat = low, 2 hats = moderate, 3 hats = high).<br />
<br />
===Identifying Uncertainty and Conducting Probabilistic Analysis===<br />
<br />
As part of the assessment, the SME should discuss the potential uncertainty of the independent variables. The independent variables are the variables that impact one or more scores; the scores that are independent scores. Many times the SME can assess an upper, nominal, and lower bound by assuming low, moderate, and high performance. Using this data, a Monte Carlo Simulation summarizes the impact of the uncertainties and can identify the uncertainties that have the most impact on the decision.<br />
<br />
===Accessing Impact of Uncertainty - Analyzing Risk and Sensitivity===<br />
<br />
Decision analysis uses many forms of sensitivity analysis including line diagrams, tornado diagrams, waterfall diagrams and several uncertainty analyses including Monte Carlo Simulation, decision trees, and influence diagrams (Parnell et al. 2013). A line diagram is used to show the sensitivity to the swing weight judgment (Parnell et al. 2011). Figure 10 shows the results of a Monte Carlo Simulation of performance value. <br />
<br />
[[File:Uncertainty_on_Perf_Value_from_Monte_DM.png|thumb|center|700px|center|'''Figure 10. Uncertainty on Performance Value from Monte Carlo Simulation (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
===Improving Alternatives===<br />
<br />
Mining the data generated for the alternatives will likely reveal opportunities to modify some design choices to claim untapped value and/or reduce risk. Taking advantage of initial findings to generate new and creative alternatives starts the process of transforming the decision process from "alternative-focused thinking" to "value-focused thinking" (Keeney 1993).<br />
<br />
===Communicating Tradeoffs===<br />
<br />
This is the point in the process where the decision analysis team identifies key observations about tradeoffs and the important uncertainties and risks.<br />
<br />
===Presenting Recommendations and Implementing Action Plan===<br />
<br />
It is often helpful to describe the recommendation(s) in the form of a clearly-worded, actionable task-list in order to increase the likelihood of the decision implementation. Reports are important for historical traceability and future decisions. Take the time and effort to create a comprehensive, high-quality report detailing study findings and supporting rationale. Consider static paper reports augmented with dynamic hyper-linked e-reports.<br />
<br />
==References== <br />
<br />
===Works Cited===<br />
Buede, D.M. 2009. The Engineering Design of Systems: Models and Methods, Wiley.<br />
<br />
Edwards, W., Miles Jr, R.F. & Von Winterfeldt, D. 2007. Advances In Decision Analysis: From Foundations to Applications, Cambridge University Press.<br />
<br />
Keeney, R.L. and Raiffa H. 1976. Decisions with Multiple Objectives - Preferences and Value Tradeoffs. New York: Wiley.<br />
<br />
Keeney, R.L. 1992. Value-Focused Thinking: A Path to Creative Decision-making. Cambridge, Massachusetts: Harvard University Press.<br />
<br />
Keeney, R.L. 1993. Creativity in MS/OR: Value-focused thinking—Creativity directed toward decision making. Interfaces, 23(3), pp.62–67.<br />
<br />
Parnell, G. S. 2009. Decision Analysis in One Chart, Decision Line, Newsletter of the Decision Sciences Institute.<br />
<br />
Parnell, G. S., Driscoll, P. J., and Henderson D. L., (eds). 2011. Decision Making for Systems Engineering and Management, 2nd Edition, Wiley Series in Systems Engineering, Wiley & Sons Inc. <br />
<br />
Parnell, G., Bresnick, T., Tani, S., & Johnson, E. 2013. Handbook of Decision Analysis, Wiley & Sons.<br />
<br />
===Primary References===<br />
Buede, D.M. 2004. On Trade Studies, INCOSE.<br />
<br />
Keeney, R.L. 2004. Making Better Decision Makers. Decision Analysis, 1(4), pp.193–204.<br />
<br />
Keeney, R.L. & Gregory, R.S. 2005. Selecting Attributes to Measure the Achievement of Objectives. Operations Research, 53(1), pp.1–11.<br />
<br />
Kirkwood, C. W. 1197. Strategic Decision Making: Multiobjective Decision Analysis with Spreadsheets, Belmont, California: Duxbury Press.<br />
<br />
===Additional References===<br />
Buede, D.M. & Choisser, R.W. 1992. Providing an Analytic Structure for Key System Design Choices. Journal of Multi-Criteria Decision Analysis, 1(1), pp.17–27.<br />
<br />
Felix, A. 2004. Standard Approach to Trade Studies, INCOSE.<br />
<br />
Felix, A. 2005. How the Pro-Active Program (Project) Manager Uses a Systems Engineer’s Trade Study as a Management Tool, and not just a Decision Making Process, INCOSE.<br />
<br />
Miller, G.A. 1956. The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information. Psychological Review, 63(2), p.81.<br />
<br />
Ross, A.M. and Hastings, D.E. 2005. Tradespace Exploration Paradigm, INCOSE.<br />
<br />
Sproles, N. 2002. Formulating Measures of Effectiveness, INCOSE.<br />
<br />
Silletto, H. 2005. Some Really Useful Principles: A new look at the scope and boundaries of systems engineering, INCOSE.<br />
<br />
Ullman, D.G. and Spiegel, B.P. 2006. Trade Studies with Uncertain Information, INCOSE.<br />
<br />
----<br />
<center>[[Measurement|< Previous Article]] | [[Systems Engineering Management|Parent Article]] | [[Configuration Management|Next Article >]]</center><br />
<br />
{{DISQUS}}<br />
<br />
[[Category: Part 3]][[Category:Topic]]<br />
[[Category:Systems Engineering Management]]</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Decision_Management&diff=48900Decision Management2013-11-05T16:47:59Z<p>Dhenry: /* Developing Objectives and Measures */</p>
<hr />
<div>Many systems engineering decisions are difficult because they include numerous stakeholders, multiple competing objectives, substantial uncertainty, and significant consequences. In these cases, good decision making requires a formal [[Decision Management (glossary)| decision management]] process. The purpose of the decision management process is:<br />
<blockquote>“…to provide a structured, analytical framework for identifying, characterizing and evaluating a set of alternatives for a decision at any point in the life-cycle and select the most beneficial course of action.” (ISO/IEC 15288:2008)</blockquote> <br />
<br />
Decision situations ([[Opportunity (glossary)|opportunities]]) are commonly encountered throughout a [[Life Cycle (glossary)|system’s lifecycle]]. The decision management method most commonly employed by systems engineers is the trade study. Trade studies aim to define, measure, and assess shareholder and [[stakeholder (glossary)|stakeholder]] [[Value (glossary) | value]] to facilitate the decision maker’s search for an alternative that represents the best balance of competing objectives. By providing techniques for decomposing a trade decision into logical segments and then synthesizing the parts into a coherent whole, a decision management process allows the decision maker to work within human cognitive limits without oversimplifying the problem. Furthermore, by decomposing the overall decision problem, experts can provide assessments of alternatives in their area of expertise. <br />
<br />
==Decision Management Process==<br />
The decision analysis process is depicted in Figure 1 below. The decision management process is based on several best practices, including:<br />
*Utilizing sound mathematical technique of decision analysis for trade off studies (Parnell, 2009) provided a list of decision analysis concepts and techniques).<br />
*Developing one master decision model, followed by its refinement, update, and use, as it required for trade studies throughout the system life cycle.<br />
*Using Value-Focused Thinking (Keeney, 1992) to create better alternatives. <br />
*Identifying uncertainty and assessing risks for each decision.<br />
<br />
[[File:Decision_Mgt_Process_DM.png|thumb|center|650px|center|'''Figure 1. Decision Management Process (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
The center of the diagram shows the five trade space objectives. The ten blue arrows represent the decision management process activities and the white text within the green ring represents SE process elements. Interactions are represented by the small, dotted green or blue arrows. The decision analysis process is an iterative process. <br />
A hypothetical UAV decision problem is used to illustrate each of the activities in the following sections. <br />
<br />
===Framing and Tailoring the Decision===<br />
To ensure the decision team fully understands the decision context, the analyst should describe the system baseline, boundaries and interfaces. The decision context includes: the system definition, the life cycle stage, decision milestones, a list of decision makers and stakeholders, and available resources. The best practice is to identify a decision problem statement that defines the decision in terms of the system life cycle.<br />
<br />
===Developing Objectives and Measures===<br />
Defining how an important decision will be made is difficult. As Keeney puts it:<br />
<blockquote>''Most important decisions involve multiple objectives, and usually with multiple-objective decisions, you can't have it all. You will have to accept less achievement in terms of some objectives in order to achieve more on other objectives. But how much less would you accept to achieve how much more?'' (Keeney 2002)</blockquote><br />
The first step is to develop objectives and measures using interviews and focus groups with subject matter experts (SMEs) and stakeholders.<br />
For systems engineering trade-off analyses, stakeholder value often includes competing objectives of performance, development schedule, unit cost, support costs, and growth potential. For corporate decisions, shareholder value would also be added to this list. For performance, a functional decomposition can help generate a thorough set of potential objectives. Test this initial list of fundamental objectives by checking that each fundamental objective is essential and controllable and that the set of objectives is complete, non-redundant, concise, specific, and understandable. (Edwards et al. 2007) Figure 2 provides an example of an objectives hierarchy.<br />
<br />
[[File:Fund_Obj_Hierarchy_DM.png|thumb|center|650px|center|'''Figure 2. Fundamental Objectives Hierarchy (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
For each objective, we define a measure to assess the value of each alternative for that objective. A measure (attribute, criterion, and metric) must be unambiguous, comprehensive, direct, operational, and understandable (Keeney & Gregory 2005).<br />
A defining feature of multi-objective decision analysis is the transformation from measure space to value space. This transformation is performed by a value function which shows returns to scale on the measure range. When creating a value function, we ascertain the walk-away point on the measure scale (x-axis) and map it to a 0 value on the value scale (y-axis). A walk-away point is the measure score where regardless of how well an alternative performs in other measures, the decision maker will walk away from the alternative. He or she does this through working with the user, finding the measure score beyond, at which point an alternative provides no additional value, and labeling it "stretch goal" (ideal) and then mapping it to 100 (or 1 and 10) on the value scale (y-axis). Figure 3 provides the most common value curve shapes. The rationale for the shape of the value functions should be documented for traceability and defensibility (Parnell et al. 2011).<br />
<br />
[[File:Value_Function_Example_DM.png|thumb|center|750px|center|'''Figure 3. Value Function Examples (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
The mathematics of multiple objective decision analysis (MODA) requires that the weights depend on importance of the measure and the range of the measure (walk away to stretch goal). A useful tool for determining priority weighting is the swing weight matrix (Parnell et al. 2011). For each measure, consider its importance through determining whether the measure corresponds to a defining, critical, or enabling function and consider the gap between the current capability and the desired capability; finally, put the name of the measure in the appropriate cell of the matrix (Figure 4). The highest priority weighting is placed in the upper-left corner and assigned an unnormalized weight of 100. The unnormalized weights are monotonically decreasing to the right and down the matrix. Swing weights are then assessed by comparing them to the most important value measure or another assessed measure. The swing weights are normalized to sum to one for the additive value model used to calculate value in a subsequent section. <br />
<br />
[[File:Swing_Weight_Matrix_DM.png|thumb|center|750px|center|'''Figure 4. Swing Weight Matrix (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
===Generating Creative Alternatives===<br />
<br />
To help generate a creative and comprehensive set of alternatives that span the decision space, consider developing an alternative generation table (also called a morphological box) (Buede, 2009; Parnell et al. 2011). It is a best practice to establish a meaningful product structure for the system and to be reported in all decision presentations (Figure 5). <br />
<br />
[[File:Descript_of_Alt_DM.png|thumb|center|750px|center|'''Figure 5. Descriptions of Alternatives (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
===Assessing Alternatives via Deterministic Analysis===<br />
<br />
With objectives and measures established and alternatives having been defined, the decision team should engage SMEs, equipped with operational data, test data, simulations, models, and expert knowledge. Scores are best captured on scoring sheets for each alternative/measure combination which document the source and rationale. Figure 6 provides a summary of the scores. <br />
<br />
[[File:ALT_Scores_DM.png|thumb|center|750px|center|'''Figure 6. Alternative Scores (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
Note that in addition to identified alternatives, the score matrix includes a row for the ideal alternative. The ideal is a tool for value-focused thinking, which will be covered later.<br />
<br />
===Synthesizing Results===<br />
<br />
Next, one can transform the scores into a value table, by using the value functions developed previously. A color heat map can be useful to visualize value tradeoffs between alternatives and identify where alternatives need improvement (Figure 7).<br />
<br />
[[File:Value_Scorecard_w_Heat_Map_DM.png|thumb|center|850px|center|'''Figure 7. Value Scorecard with Heat Map (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
The additive value model uses the following equation to calculate each alternative’s value:<br />
<br />
EQUATION HERE<br />
<br />
where<br />
<br />
EQUATION VALUES HERE<br />
<br />
The value component chart (Figure 8) shows the total value and the weighted value measure contribution of each alternative (Parnell et al. 2011). <br />
<br />
[[File:Value_Comp_Graph_DM.png|thumb|center|700px|center|'''Figure 8. Value Component Graph (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
The heart of a decision management process for system engineering trade off analysis is the ability to assess all dimensions of shareholder and stakeholder value. The stakeholder value scatter plot in Figure 9 shows five dimensions: unit cost, performance, development risk, growth potential, and operation and support costs for all alternatives.<br />
<br />
[[File:Ex_Stakeholder_Value_Scat_DM.png|thumb|center|700px|center|'''Figure 9. Example of a Stakeholder Value Scatterplot (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
Each system alternative is represented by a scatter plot marker (Figure 9). An alternative’s unit cost and performance value are indicated by x and y positions respectively. An alternative’s development risk is indicated by the color of the marker (green = low, yellow= medium, red = high), while the growth potential is shown as the number of hats above the circular marker (1 hat = low, 2 hats = moderate, 3 hats = high).<br />
<br />
===Identifying Uncertainty and Conducting Probabilistic Analysis===<br />
<br />
As part of the assessment, the SME should discuss the potential uncertainty of the independent variables. The independent variables are the variables that impact one or more scores; the scores that are independent scores. Many times the SME can assess an upper, nominal, and lower bound by assuming low, moderate, and high performance. Using this data, a Monte Carlo Simulation summarizes the impact of the uncertainties and can identify the uncertainties that have the most impact on the decision.<br />
<br />
===Accessing Impact of Uncertainty - Analyzing Risk and Sensitivity===<br />
<br />
Decision analysis uses many forms of sensitivity analysis including line diagrams, tornado diagrams, waterfall diagrams and several uncertainty analyses including Monte Carlo Simulation, decision trees, and influence diagrams (Parnell et al. 2013). A line diagram is used to show the sensitivity to the swing weight judgment (Parnell et al. 2011). Figure 10 shows the results of a Monte Carlo Simulation of performance value. <br />
<br />
[[File:Uncertainty_on_Perf_Value_from_Monte_DM.png|thumb|center|700px|center|'''Figure 10. Uncertainty on Performance Value from Monte Carlo Simulation (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
===Improving Alternatives===<br />
<br />
Mining the data generated for the alternatives will likely reveal opportunities to modify some design choices to claim untapped value and/or reduce risk. Taking advantage of initial findings to generate new and creative alternatives starts the process of transforming the decision process from "alternative-focused thinking" to "value-focused thinking" (Keeney 1993).<br />
<br />
===Communicating Tradeoffs===<br />
<br />
This is the point in the process where the decision analysis team identifies key observations about tradeoffs and the important uncertainties and risks.<br />
<br />
===Presenting Recommendations and Implementing Action Plan===<br />
<br />
It is often helpful to describe the recommendation(s) in the form of a clearly-worded, actionable task-list in order to increase the likelihood of the decision implementation. Reports are important for historical traceability and future decisions. Take the time and effort to create a comprehensive, high-quality report detailing study findings and supporting rationale. Consider static paper reports augmented with dynamic hyper-linked e-reports.<br />
<br />
==References== <br />
<br />
===Works Cited===<br />
Buede, D.M. 2009. The Engineering Design of Systems: Models and Methods, Wiley.<br />
<br />
Edwards, W., Miles Jr, R.F. & Von Winterfeldt, D. 2007. Advances In Decision Analysis: From Foundations to Applications, Cambridge University Press.<br />
<br />
Keeney, R.L. and Raiffa H. 1976. Decisions with Multiple Objectives - Preferences and Value Tradeoffs. New York: Wiley.<br />
<br />
Keeney, R.L. 1992. Value-Focused Thinking: A Path to Creative Decision-making. Cambridge, Massachusetts: Harvard University Press.<br />
<br />
Keeney, R.L. 1993. Creativity in MS/OR: Value-focused thinking—Creativity directed toward decision making. Interfaces, 23(3), pp.62–67.<br />
<br />
Parnell, G. S. 2009. Decision Analysis in One Chart, Decision Line, Newsletter of the Decision Sciences Institute.<br />
<br />
Parnell, G. S., Driscoll, P. J., and Henderson D. L., (eds). 2011. Decision Making for Systems Engineering and Management, 2nd Edition, Wiley Series in Systems Engineering, Wiley & Sons Inc. <br />
<br />
Parnell, G., Bresnick, T., Tani, S., & Johnson, E. 2013. Handbook of Decision Analysis, Wiley & Sons.<br />
<br />
===Primary References===<br />
Buede, D.M. 2004. On Trade Studies, INCOSE.<br />
<br />
Keeney, R.L. 2004. Making Better Decision Makers. Decision Analysis, 1(4), pp.193–204.<br />
<br />
Keeney, R.L. & Gregory, R.S. 2005. Selecting Attributes to Measure the Achievement of Objectives. Operations Research, 53(1), pp.1–11.<br />
<br />
Kirkwood, C. W. 1197. Strategic Decision Making: Multiobjective Decision Analysis with Spreadsheets, Belmont, California: Duxbury Press.<br />
<br />
===Additional References===<br />
Buede, D.M. & Choisser, R.W. 1992. Providing an Analytic Structure for Key System Design Choices. Journal of Multi-Criteria Decision Analysis, 1(1), pp.17–27.<br />
<br />
Felix, A. 2004. Standard Approach to Trade Studies, INCOSE.<br />
<br />
Felix, A. 2005. How the Pro-Active Program (Project) Manager Uses a Systems Engineer’s Trade Study as a Management Tool, and not just a Decision Making Process, INCOSE.<br />
<br />
Miller, G.A. 1956. The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information. Psychological Review, 63(2), p.81.<br />
<br />
Ross, A.M. and Hastings, D.E. 2005. Tradespace Exploration Paradigm, INCOSE.<br />
<br />
Sproles, N. 2002. Formulating Measures of Effectiveness, INCOSE.<br />
<br />
Silletto, H. 2005. Some Really Useful Principles: A new look at the scope and boundaries of systems engineering, INCOSE.<br />
<br />
Ullman, D.G. and Spiegel, B.P. 2006. Trade Studies with Uncertain Information, INCOSE.<br />
<br />
----<br />
<center>[[Measurement|< Previous Article]] | [[Systems Engineering Management|Parent Article]] | [[Configuration Management|Next Article >]]</center><br />
<br />
{{DISQUS}}<br />
<br />
[[Category: Part 3]][[Category:Topic]]<br />
[[Category:Systems Engineering Management]]</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Decision_Management&diff=48899Decision Management2013-11-05T16:44:54Z<p>Dhenry: </p>
<hr />
<div>Many systems engineering decisions are difficult because they include numerous stakeholders, multiple competing objectives, substantial uncertainty, and significant consequences. In these cases, good decision making requires a formal [[Decision Management (glossary)| decision management]] process. The purpose of the decision management process is:<br />
<blockquote>“…to provide a structured, analytical framework for identifying, characterizing and evaluating a set of alternatives for a decision at any point in the life-cycle and select the most beneficial course of action.” (ISO/IEC 15288:2008)</blockquote> <br />
<br />
Decision situations ([[Opportunity (glossary)|opportunities]]) are commonly encountered throughout a [[Life Cycle (glossary)|system’s lifecycle]]. The decision management method most commonly employed by systems engineers is the trade study. Trade studies aim to define, measure, and assess shareholder and [[stakeholder (glossary)|stakeholder]] [[Value (glossary) | value]] to facilitate the decision maker’s search for an alternative that represents the best balance of competing objectives. By providing techniques for decomposing a trade decision into logical segments and then synthesizing the parts into a coherent whole, a decision management process allows the decision maker to work within human cognitive limits without oversimplifying the problem. Furthermore, by decomposing the overall decision problem, experts can provide assessments of alternatives in their area of expertise. <br />
<br />
==Decision Management Process==<br />
The decision analysis process is depicted in Figure 1 below. The decision management process is based on several best practices, including:<br />
*Utilizing sound mathematical technique of decision analysis for trade off studies (Parnell, 2009) provided a list of decision analysis concepts and techniques).<br />
*Developing one master decision model, followed by its refinement, update, and use, as it required for trade studies throughout the system life cycle.<br />
*Using Value-Focused Thinking (Keeney, 1992) to create better alternatives. <br />
*Identifying uncertainty and assessing risks for each decision.<br />
<br />
[[File:Decision_Mgt_Process_DM.png|thumb|center|650px|center|'''Figure 1. Decision Management Process (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
The center of the diagram shows the five trade space objectives. The ten blue arrows represent the decision management process activities and the white text within the green ring represents SE process elements. Interactions are represented by the small, dotted green or blue arrows. The decision analysis process is an iterative process. <br />
A hypothetical UAV decision problem is used to illustrate each of the activities in the following sections. <br />
<br />
===Framing and Tailoring the Decision===<br />
To ensure the decision team fully understands the decision context, the analyst should describe the system baseline, boundaries and interfaces. The decision context includes: the system definition, the life cycle stage, decision milestones, a list of decision makers and stakeholders, and available resources. The best practice is to identify a decision problem statement that defines the decision in terms of the system life cycle.<br />
<br />
===Developing Objectives and Measures===<br />
Defining how an important decision will be made is difficult. As Keeney puts it:<br />
<blockquote>Most important decisions involve multiple objectives, and usually with multiple-objective decisions, you can't have it all. You will have to accept less achievement in terms of some objectives in order to achieve more on other objectives. But how much less would you accept to achieve how much more? (Keeney 2002)</blockquote><br />
The first step is to develop objectives and measures using interviews and focus groups with subject matter experts (SMEs) and stakeholders.<br />
For systems engineering trade-off analyses, stakeholder value often includes competing objectives of performance, development schedule, unit cost, support costs, and growth potential. For corporate decisions, shareholder value would also be added to this list. For performance, a functional decomposition can help generate a thorough set of potential objectives. Test this initial list of fundamental objectives by checking that each fundamental objective is essential and controllable and that the set of objectives is complete, non-redundant, concise, specific, and understandable. (Edwards et al. 2007) Figure 2 provides an example of an objectives hierarchy.<br />
<br />
[[File:Fund_Obj_Hierarchy_DM.png|thumb|center|650px|center|'''Figure 2. Fundamental Objectives Hierarchy (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
For each objective, we define a measure to assess the value of each alternative for that objective. A measure (attribute, criterion, and metric) must be unambiguous, comprehensive, direct, operational, and understandable (Keeney & Gregory 2005).<br />
A defining feature of multi-objective decision analysis is the transformation from measure space to value space. This transformation is performed by a value function which shows returns to scale on the measure range. When creating a value function, we ascertain the walk-away point on the measure scale (x-axis) and map it to a 0 value on the value scale (y-axis). A walk-away point is the measure score where regardless of how well an alternative performs in other measures, the decision maker will walk away from the alternative. He or she does this through working with the user, finding the measure score beyond, at which point an alternative provides no additional value, and labeling it "stretch goal" (ideal) and then mapping it to 100 (or 1 and 10) on the value scale (y-axis). Figure 3 provides the most common value curve shapes. The rationale for the shape of the value functions should be documented for traceability and defensibility (Parnell et al. 2011).<br />
<br />
[[File:Value_Function_Example_DM.png|thumb|center|750px|center|'''Figure 3. Value Function Examples (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
The mathematics of multiple objective decision analysis (MODA) requires that the weights depend on importance of the measure and the range of the measure (walk away to stretch goal). A useful tool for determining priority weighting is the swing weight matrix (Parnell et al. 2011). For each measure, consider its importance through determining whether the measure corresponds to a defining, critical, or enabling function and consider the gap between the current capability and the desired capability; finally, put the name of the measure in the appropriate cell of the matrix (Figure 4). The highest priority weighting is placed in the upper-left corner and assigned an unnormalized weight of 100. The unnormalized weights are monotonically decreasing to the right and down the matrix. Swing weights are then assessed by comparing them to the most important value measure or another assessed measure. The swing weights are normalized to sum to one for the additive value model used to calculate value in a subsequent section. <br />
<br />
[[File:Swing_Weight_Matrix_DM.png|thumb|center|750px|center|'''Figure 4. Swing Weight Matrix (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
===Generating Creative Alternatives===<br />
<br />
To help generate a creative and comprehensive set of alternatives that span the decision space, consider developing an alternative generation table (also called a morphological box) (Buede, 2009; Parnell et al. 2011). It is a best practice to establish a meaningful product structure for the system and to be reported in all decision presentations (Figure 5). <br />
<br />
[[File:Descript_of_Alt_DM.png|thumb|center|750px|center|'''Figure 5. Descriptions of Alternatives (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
===Assessing Alternatives via Deterministic Analysis===<br />
<br />
With objectives and measures established and alternatives having been defined, the decision team should engage SMEs, equipped with operational data, test data, simulations, models, and expert knowledge. Scores are best captured on scoring sheets for each alternative/measure combination which document the source and rationale. Figure 6 provides a summary of the scores. <br />
<br />
[[File:ALT_Scores_DM.png|thumb|center|750px|center|'''Figure 6. Alternative Scores (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
Note that in addition to identified alternatives, the score matrix includes a row for the ideal alternative. The ideal is a tool for value-focused thinking, which will be covered later.<br />
<br />
===Synthesizing Results===<br />
<br />
Next, one can transform the scores into a value table, by using the value functions developed previously. A color heat map can be useful to visualize value tradeoffs between alternatives and identify where alternatives need improvement (Figure 7).<br />
<br />
[[File:Value_Scorecard_w_Heat_Map_DM.png|thumb|center|850px|center|'''Figure 7. Value Scorecard with Heat Map (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
The additive value model uses the following equation to calculate each alternative’s value:<br />
<br />
EQUATION HERE<br />
<br />
where<br />
<br />
EQUATION VALUES HERE<br />
<br />
The value component chart (Figure 8) shows the total value and the weighted value measure contribution of each alternative (Parnell et al. 2011). <br />
<br />
[[File:Value_Comp_Graph_DM.png|thumb|center|700px|center|'''Figure 8. Value Component Graph (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
The heart of a decision management process for system engineering trade off analysis is the ability to assess all dimensions of shareholder and stakeholder value. The stakeholder value scatter plot in Figure 9 shows five dimensions: unit cost, performance, development risk, growth potential, and operation and support costs for all alternatives.<br />
<br />
[[File:Ex_Stakeholder_Value_Scat_DM.png|thumb|center|700px|center|'''Figure 9. Example of a Stakeholder Value Scatterplot (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
Each system alternative is represented by a scatter plot marker (Figure 9). An alternative’s unit cost and performance value are indicated by x and y positions respectively. An alternative’s development risk is indicated by the color of the marker (green = low, yellow= medium, red = high), while the growth potential is shown as the number of hats above the circular marker (1 hat = low, 2 hats = moderate, 3 hats = high).<br />
<br />
===Identifying Uncertainty and Conducting Probabilistic Analysis===<br />
<br />
As part of the assessment, the SME should discuss the potential uncertainty of the independent variables. The independent variables are the variables that impact one or more scores; the scores that are independent scores. Many times the SME can assess an upper, nominal, and lower bound by assuming low, moderate, and high performance. Using this data, a Monte Carlo Simulation summarizes the impact of the uncertainties and can identify the uncertainties that have the most impact on the decision.<br />
<br />
===Accessing Impact of Uncertainty - Analyzing Risk and Sensitivity===<br />
<br />
Decision analysis uses many forms of sensitivity analysis including line diagrams, tornado diagrams, waterfall diagrams and several uncertainty analyses including Monte Carlo Simulation, decision trees, and influence diagrams (Parnell et al. 2013). A line diagram is used to show the sensitivity to the swing weight judgment (Parnell et al. 2011). Figure 10 shows the results of a Monte Carlo Simulation of performance value. <br />
<br />
[[File:Uncertainty_on_Perf_Value_from_Monte_DM.png|thumb|center|700px|center|'''Figure 10. Uncertainty on Performance Value from Monte Carlo Simulation (INCOSE DAWG 2013).''' Permission granted by INCOSE Decision Analysis Working Group (DAWG). All other rights are reserved by the copyright owner.]]<br />
<br />
===Improving Alternatives===<br />
<br />
Mining the data generated for the alternatives will likely reveal opportunities to modify some design choices to claim untapped value and/or reduce risk. Taking advantage of initial findings to generate new and creative alternatives starts the process of transforming the decision process from "alternative-focused thinking" to "value-focused thinking" (Keeney 1993).<br />
<br />
===Communicating Tradeoffs===<br />
<br />
This is the point in the process where the decision analysis team identifies key observations about tradeoffs and the important uncertainties and risks.<br />
<br />
===Presenting Recommendations and Implementing Action Plan===<br />
<br />
It is often helpful to describe the recommendation(s) in the form of a clearly-worded, actionable task-list in order to increase the likelihood of the decision implementation. Reports are important for historical traceability and future decisions. Take the time and effort to create a comprehensive, high-quality report detailing study findings and supporting rationale. Consider static paper reports augmented with dynamic hyper-linked e-reports.<br />
<br />
==References== <br />
<br />
===Works Cited===<br />
Buede, D.M. 2009. The Engineering Design of Systems: Models and Methods, Wiley.<br />
<br />
Edwards, W., Miles Jr, R.F. & Von Winterfeldt, D. 2007. Advances In Decision Analysis: From Foundations to Applications, Cambridge University Press.<br />
<br />
Keeney, R.L. and Raiffa H. 1976. Decisions with Multiple Objectives - Preferences and Value Tradeoffs. New York: Wiley.<br />
<br />
Keeney, R.L. 1992. Value-Focused Thinking: A Path to Creative Decision-making. Cambridge, Massachusetts: Harvard University Press.<br />
<br />
Keeney, R.L. 1993. Creativity in MS/OR: Value-focused thinking—Creativity directed toward decision making. Interfaces, 23(3), pp.62–67.<br />
<br />
Parnell, G. S. 2009. Decision Analysis in One Chart, Decision Line, Newsletter of the Decision Sciences Institute.<br />
<br />
Parnell, G. S., Driscoll, P. J., and Henderson D. L., (eds). 2011. Decision Making for Systems Engineering and Management, 2nd Edition, Wiley Series in Systems Engineering, Wiley & Sons Inc. <br />
<br />
Parnell, G., Bresnick, T., Tani, S., & Johnson, E. 2013. Handbook of Decision Analysis, Wiley & Sons.<br />
<br />
===Primary References===<br />
Buede, D.M. 2004. On Trade Studies, INCOSE.<br />
<br />
Keeney, R.L. 2004. Making Better Decision Makers. Decision Analysis, 1(4), pp.193–204.<br />
<br />
Keeney, R.L. & Gregory, R.S. 2005. Selecting Attributes to Measure the Achievement of Objectives. Operations Research, 53(1), pp.1–11.<br />
<br />
Kirkwood, C. W. 1197. Strategic Decision Making: Multiobjective Decision Analysis with Spreadsheets, Belmont, California: Duxbury Press.<br />
<br />
===Additional References===<br />
Buede, D.M. & Choisser, R.W. 1992. Providing an Analytic Structure for Key System Design Choices. Journal of Multi-Criteria Decision Analysis, 1(1), pp.17–27.<br />
<br />
Felix, A. 2004. Standard Approach to Trade Studies, INCOSE.<br />
<br />
Felix, A. 2005. How the Pro-Active Program (Project) Manager Uses a Systems Engineer’s Trade Study as a Management Tool, and not just a Decision Making Process, INCOSE.<br />
<br />
Miller, G.A. 1956. The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information. Psychological Review, 63(2), p.81.<br />
<br />
Ross, A.M. and Hastings, D.E. 2005. Tradespace Exploration Paradigm, INCOSE.<br />
<br />
Sproles, N. 2002. Formulating Measures of Effectiveness, INCOSE.<br />
<br />
Silletto, H. 2005. Some Really Useful Principles: A new look at the scope and boundaries of systems engineering, INCOSE.<br />
<br />
Ullman, D.G. and Spiegel, B.P. 2006. Trade Studies with Uncertain Information, INCOSE.<br />
<br />
----<br />
<center>[[Measurement|< Previous Article]] | [[Systems Engineering Management|Parent Article]] | [[Configuration Management|Next Article >]]</center><br />
<br />
{{DISQUS}}<br />
<br />
[[Category: Part 3]][[Category:Topic]]<br />
[[Category:Systems Engineering Management]]</div>Dhenryhttps://sebokwiki.org/w/index.php?title=An_Enterprise_Framework_for_Operationally_Effective_System_of_Systems_Design&diff=48738An Enterprise Framework for Operationally Effective System of Systems Design2013-09-25T15:42:38Z<p>Dhenry: </p>
<hr />
<div><blockquote>Bobinis, J. and T. Herald. 2012. “An Enterprise Framework for Operationally Effective System of Systems Design.” Journal of Enterprise Architecture, 8(2), May 2012.</blockquote><br />
<br />
==Usage==<br />
This source is considered a primary reference for the [[Logistics]] article.<br />
<br />
<br />
{{DISQUS}}<br />
<br />
[[Category:Primary Reference]]</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=48737SEBoK Review and Adjudication2013-09-25T15:06:22Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is also included in adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under the new governance structure. The adjudication process described here is not applicable to for these releases. Along with SEBoK v. 1.1.2, the [http://www.sebokwiki.org/sandbox SEBoK Sandbox] has been setup to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1, v. 1.1.1, and v. 1.1.2===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox].<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=48736SEBoK Review and Adjudication2013-09-25T15:05:42Z<p>Dhenry: /* SEBoK v. 1.1, v. 1.1.1, and v. 1.1.2 */</p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is also included in adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under the new governance structure. The adjudication process described here is not applicable to for these releases. Along with SEBoK v. 1.1.2, the [http://www.sebokwiki.org/sandbox| SEBoK Sandbox] has been setup to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1, v. 1.1.1, and v. 1.1.2===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the [http://www.sebokwiki.org/sandbox SEBoK Sandbox].<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=48735SEBoK Review and Adjudication2013-09-25T15:04:43Z<p>Dhenry: /* Adjudication Matrices */</p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is also included in adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under the new governance structure. The adjudication process described here is not applicable to for these releases. Along with SEBoK v. 1.1.2, the [http://www.sebokwiki.org/sandbox| SEBoK Sandbox] has been setup to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1, v. 1.1.1, and v. 1.1.2===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the [http://www.sebokwiki.org/sandbox| SEBoK Sandbox].<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/downloads/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/downloads/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/downloads/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Main_Page&diff=48729Main Page2013-08-01T23:40:07Z<p>Dhenry: Redirected page to DraftLoginPage</p>
<hr />
<div>#REDIRECT [[DraftLoginPage]]<br />
<br />
<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=DraftLoginPage&diff=48728DraftLoginPage2013-08-01T23:39:40Z<p>Dhenry: Redirected page to Guide to the Systems Engineering Body of Knowledge (SEBoK)</p>
<hr />
<div>#REDIRECT [[Guide to the Systems Engineering Body of Knowledge (SEBoK)]]</div>Dhenryhttps://sebokwiki.org/w/index.php?title=DraftLoginPage&diff=48727DraftLoginPage2013-08-01T23:39:03Z<p>Dhenry: Created page with "#REDIRECT"</p>
<hr />
<div>#REDIRECT</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Main_Page&diff=48726Main Page2013-08-01T23:37:52Z<p>Dhenry: Redirected page to Guide to the Systems Engineering Body of Knowledge (SEBoK)</p>
<hr />
<div>#REDIRECT [[Guide to the Systems Engineering Body of Knowledge (SEBoK)]]<br />
<br />
<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Main_Page&diff=48725Main Page2013-08-01T23:36:18Z<p>Dhenry: Redirected page to SEBoK Table of Contents</p>
<hr />
<div>#REDIRECT [[SEBoK Table of Contents]]<br />
<br />
<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Guide_to_the_Systems_Engineering_Body_of_Knowledge_(SEBoK)&diff=48724Guide to the Systems Engineering Body of Knowledge (SEBoK)2013-08-01T23:18:32Z<p>Dhenry: </p>
<hr />
<div>__NOTOC__<br />
<br />
<center> <span style="color: red; text-decoration;"><br />
<br />
'''This is the DRAFT version of the SEBoK. Editing is ongoing in preparation for the next version of SEBoK.'''<br />
<br />
'''To visit the current version of the SEBoK, please go to</span> [http://www.sebokwiki.org SEBoK].'''</center> <br />
<br />
<br />
==Welcome to SEBoK version 1.1.2==<br />
On behalf of [[Acknowledgements|the more than 70 authors]], the editors, and the three SEBoK steward organizations – the International Council on Systems Engineering (INCOSE), the Institute of Electrical and Electronics Engineers Computer Society (IEEE-CS), and the Systems Engineering Research Center (SERC) – welcome to the ''Guide to the Systems Engineering Body of Knowledge (SEBoK)'' version 1.1.2. This version was released 1 August 2013, and contains [[Release History|a small number of content changes]] and wiki additions to version 1.1.1, which was released in June 2013. In addition to the release of v. 1.1.2, the authors are also releasing the first iteration of the SEBoK Sandbox, a collaborative space for members of the community to provide more detailed feedback on and input to the SEBoK. Please '''[http://www.sebokwiki.org/sandbox/ visit the Sandbox]''' for more information.<br />
<br />
The SEBoK provides a compendium of the [[Primary References|key knowledge sources and references]] of systems engineering, organized and explained to assist a wide variety of users. It is a living document, accepting [[SEBoK Review and Adjudication |community input]] continuously, and [[Editors' Note|regularly refreshed and updated]].<br />
<br />
==About Systems Engineering== <br />
<br />
[[Systems Engineering (glossary)|Systems engineering]] is an interdisciplinary approach and means to enable the realization of successful systems. Separate articles in [[SEBoK Introduction|Part 1]] provide an [[Systems Engineering Overview|overview of systems engineering]], place it in [[Systems Engineering: Historic and Future Challenges|historical context]], and discuss its [[Economic Value of Systems Engineering| economic value]].<br />
<br />
Systems engineering has roots in [[Systems |systems science]]. Major sections (called knowledge areas (KAs)) in [[Systems |Part 2]] discuss [[Systems Fundamentals]], [[Systems Thinking]], [[Representing Systems with Models]], and the [[Systems Approach Applied to Engineered Systems]].<br />
<br />
==About the SEBoK==<br />
The SEBoK is organized into [[SEBoK Table of Contents|7 parts]], with a [[Glossary of Terms]] and a list of [[Primary References]]. <br />
<br />
* [[SEBoK Introduction|Part 1]] discusses the [[Scope of the SEBoK]], and its [[Structure of the SEBoK|structure]], including its hierarchy of parts, [[:Category:Knowledge_Area|knowledge areas]], and [[:Category:Topic|topics]]. Part 1 also includes a lengthy discussion of [[SEBoK Users and Uses]], including five [[:Category:Use_Case|use cases]]. <br />
<br />
The other parts include: <br />
* Part 2 [[Systems]]<br />
* Part 3 [[Systems Engineering and Management]]<br />
* Part 4 [[Applications of Systems Engineering]]<br />
* Part 5 [[Enabling Systems Engineering]]<br />
* Part 6 [[Related Disciplines]]<br />
* Part 7 [[Systems Engineering Implementation Examples]]<br />
<br />
As a compendium, much of the content has restricted intellectual property rights. This [[Bkcase Wiki:Copyright |copyright information]] is placed on each page, and must be respected. The SEBoK copyright is held by the Trustees of the Stevens Institute of Technology, and plans for the transfer of the copyright are discussed in the [[Editors' Note]].<br />
<br />
As a living document, at the bottom of each page, version identification can be found in a link called "[[About the SEBoK]]."<br />
<br />
A PDF of SEBoK v. 1.1 and the older SEBoK v. 1.0 may be downloaded at [[Download SEBoK PDF]]. Please note that a new PDF is not generated for micro releases, such as v. 1.1.2.<br />
<br />
There is a link in the left margin under ''Quicklinks'' explaining how to [[Cite the SEBoK]] correctly.<br />
<br />
==About the Sandbox==<br />
<br />
When BKCASE began, the editors struggled to balance the open access and constant change of a wiki with the archival integrity of a journal. To satisfy both the need for a stable baseline and the desire for broader community involvement, we have implemented a new collaborative space. The '''SEBoK Sandbox''' is a copy of the SEBoK that is separate from the baseline version where anyone in the community can edit articles, recommend new content, or provide comments on existing articles. It is important to note that while anyone in the community can gain access to the Sandbox, all submissions must still be approved by the Editorial Board before they will be folded into a new baseline version of the SEBoK. For more information on how this works, please '''[http://www.sebokwiki.org/sandbox visit the Sandbox]'''.<br />
<br />
You may also still contribute to the SEBoK by using the comments feature on the bottom of each page.<br />
<br />
==Using the SEBoK==<br />
Articles in the SEBoK can be found by using the ''Search'' field in the upper right corner of each page, as well as through the ''Quicklinks'', ''Outline'', and ''Navigation'' menus in the left margin of each page.<br />
Detailed instructions about the page layout and features are found in [[How to Read the SEBoK]].<br />
<br />
==Contact the Editors==<br />
Comments can be left on any page by using the [http://help.disqus.com/ DISQUS] feature. These are periodically reviewed. Comments can be flagged in DISQUS, which will result in a faster review by the editors. <br />
<br />
Email may be sent to [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
----<br />
<br />
<center>[[SEBoK Introduction|Go to Part 1 >]]</center><br />
<br />
<br />
<center><br />
{|<br />
|-<br />
|style="background-color: #ffffff"|[[File:INCOSE-logo-.jpg]]<br />
|style="background-color: #ffffff"|[[File:CSlogo.png|350px|center|Institute of Electrical and Electronics Engineers Computer Society]]<br />
|-<br />
|colspan="2" style="background-color: #ffffff"|[[File:SERC_logo.jpg|350px|center|Systems Engineering Research]]<br />
<br />
|}<br />
</center><br />
<br />
<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Governance_and_Editorial_Boards&diff=48718Governance and Editorial Boards2013-08-01T18:18:25Z<p>Dhenry: </p>
<hr />
<div>{|style="width:100%"<br />
!colspan="2"|BKCASE Editors-in-Chief<br />
|-<br />
|style="background-color: #ffffff"|<br />
[[File:ArtPyster.jpg|200px]]<br />
<br />
'''Editor in Chief'''<br />
<br />
Art Pyster<br />
<br />
''Stevens Institute of Technology (US)''<br />
<br />
[mailto:art.pyster@stevens.edu art.pyster@stevens.edu]<br />
<br />
|style="background-color: #ffffff"|<br />
[[File:DaveOlwell.jpg|136px]]<br />
<br />
'''Co-Editor in Chief'''<br />
<br />
David H. Olwell<br />
<br />
''Naval Postgraduate School (US)''<br />
<br />
[mailto:dholwell@nps.edu dholwell@nps.edu]<br />
|-<br />
<br />
|}<br />
<br />
<br />
<br />
<br />
{|style="width:100%"<br />
!colspan="2"|BKCASE Associate Editors<br />
<br />
|-<br />
|'''Richard Adcock'''<br />
<br />
''Cranfield University and INCOSE UK (UK)''<br />
<br />
[mailto:r.d.adcock@cranfield.ac.uk r.d.adcock@cranfield.ac.uk]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Cihan Dagli.<br />
<br />
|'''Michael Henshaw'''<br />
<br />
''Loughborough University (UK)''<br />
<br />
<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Judith Dahmann.<br />
|-<br />
|'''Barry Boehm'''<br />
<br />
''University of Southern California (US)''<br />
<br />
[mailto:boehm@usc.edu boehm@usc.edu]<br />
<br />
Responsible for the Systems Engineering Management knowledge area with Greg Parnell and Life Cycle Models knowledge area; both are in Part 3: Systems Engineering and Management.<br />
|'''Chris Paredis'''<br />
<br />
''Georgia Institute of Technology (US)''<br />
<br />
[mailto:chris.paredis@me.gatech.edu chris.paredis@me.gatech.edu]<br />
<br />
Responsible for working across the SEBoK adding material on the theoretical underpinnings of systems engineering, including mathematical foundations.<br />
|-<br />
|'''Cihan Dagli'''<br />
<br />
''Missouri University of Science & Technology (US)''<br />
<br />
<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Rick Adcock.<br />
|'''Gregory Parnell'''<br />
<br />
''University of Arkansas (US)''<br />
<br />
[mailto:greg.parnell@gmail.com greg.parnell@gmail.com]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Dov Dori in Part 2: Systems and Systems Engineering and Management with Barry Boehm in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Judith Dahmann'''<br />
<br />
''MITRE Corporation (US)''<br />
<br />
[mailto:jdahmann@mitre.org jdahmann@mitre.org]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Mike Henshaw.<br />
|'''Garry Roedler'''<br />
<br />
''Lockheed Martin (US)''<br />
<br />
<br />
<br />
Responsible for the Concept Definition and System Definition knowledge areas in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Heidi Davidz'''<br />
<br />
''Aerojet Rocketdyne (US)''<br />
<br />
[mailto:heidi.davidz@rocket.com heidi.davidz@rocket.com]<br />
<br />
Responsible for the Enabling Individuals knowledge area with Tim Ferris and the Enabling Teams knowledge area in Part 5: Enabling Systems Engineering.<br />
|'''Samuel Seymour'''<br />
<br />
''Johns Hopkins University Applied Physics Lab (APL) (US)''<br />
<br />
[mailto:sam.seymour@jhuapl.edu sam.seymour@jhuapl.edu]<br />
<br />
Responsible for the Service Systems Engineering knowledge area in Part 4: Applications of Systems Engineering.<br />
|-<br />
|'''Dov Dori'''<br />
<br />
''Technion Israel Institute of Technology (Israel)''<br />
<br />
[mailto:dori@ie.technion.ac.il dori@ie.technion.ac.il]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Greg Parnell. Dov is also developing a new article on Model-Based Systems Engineering.<br />
|'''Ariela Sofer'''<br />
<br />
''George Mason University (US)''<br />
<br />
[mailto:asofer@gmu.edu asofer@gmu.edu]<br />
<br />
Responsible for Part 1, including an overview of systems engineering and an overview of the SEBoK.<br />
|-<br />
|'''Timothy Ferris'''<br />
<br />
''University of South Australia (Australia)''<br />
<br />
[mailto:timothy.ferris@unisa.edu.au timothy.ferris@unisa.edu.au]<br />
<br />
Responsible for the Enabling Individuals knowledge area in Part 5: Enabling Systems Engineering with Heidi Davidz. Tim is also developing a new article on Systems Engineering Education.<br />
|'''Ricardo Valerdi'''<br />
<br />
''University of Arizona (US)''<br />
<br />
[mailto:rvalerdi@email.arizona.edu rvalerdi@email.arizona.edu]<br />
<br />
Responsible for the System Realization knowledge area in Part 3: Systems Engineering and Management. Ricardo is also developing a new article on Systems Engineering References.<br />
|-<br />
|}<br />
<br />
<br />
{|style="width:100%"<br />
!colspan="2"|BKCASE Assistant Editors<br />
|-<br />
<br />
|'''Stephanie Enck'''<br />
<br />
''Naval Postgraduate School''<br />
<br />
[mailto:smenck@nps.edu smenck@nps.edu]<br />
|'''Nicole Hutchison'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:nicole.hutchison@stevens.edu nicole.hutchison@stevens.edu]<br />
|-<br />
|'''Devanandham Henry'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:dhenry@stevens.edu dhenry@stevens.edu]<br />
|<br />
|}<br />
<br />
<br />
<br />
==Interested in Editing?==<br />
The Editor in Chief and Co-Editor in Chief are looking for additional editors to support the evolution of the SEBoK. Editors are responsible for maintaining and updating two to four knowledge areas, including incorporating community feedback. We are specifically interested in support for the following knowledge areas:<br />
*System Deployment and Use<br />
*Product and Service Life Management<br />
*Systems Engineering Standards<br />
*Enabling Businesses and Enterprises<br />
*Systems Engineering and Software Engineering<br />
*Systems Engineering and Project Management<br />
*Systems Engineering and Industrial Engineering<br />
*Systems Engineering and Procurement/Acquisition<br />
*Systems Engineering and Specialty Engineering<br />
*Case Studies<br />
*Vignettes<br />
If you are interested in being considered for participation on the Editorial Board, please contact the BKCASE Staff at [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=About_the_SEBoK&diff=48712About the SEBoK2013-08-01T15:41:57Z<p>Dhenry: </p>
<hr />
<div>For questions about the SEBoK or about BKCASE or to report issues with the wiki, please email [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
For information about the copyright and what you are allowed to do with the content of the SEBoK, please see [[Bkcase Wiki:Copyright|Copyright Information]].<br />
<br />
This work was in part supported under Department of Defense Contract Number: H98230-08-D-0171 to Stevens Institute of Technology for research conducted by the Systems Engineering Research Center (SERC).<br />
<br />
This wiki is built using MediaWiki v. 1.18.1, supported by PHP 5.3.3-7+squeeze15 (cgi-fcgi) and MySQL 5.1.66-0+squeeze1.<br />
<br />
[https://www.youtube.com/embed/q23H2fS5sgI?feature=player_embedded Here you can find a brief BKCASE Video.]<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Governance_and_Editorial_Boards&diff=48711Governance and Editorial Boards2013-08-01T15:26:12Z<p>Dhenry: </p>
<hr />
<div>{|<br />
!colspan="2"|BKCASE Editors-in-Chief<br />
|-<br />
|style="background-color: #ffffff"|<br />
[[File:ArtPyster.jpg|200px]]<br />
<br />
'''Editor in Chief'''<br />
<br />
Art Pyster<br />
<br />
''Stevens Institute of Technology (US)''<br />
<br />
[mailto:art.pyster@stevens.edu art.pyster@stevens.edu]<br />
<br />
|style="background-color: #ffffff"|<br />
[[File:DaveOlwell.jpg|136px]]<br />
<br />
'''Co-Editor in Chief'''<br />
<br />
David H. Olwell<br />
<br />
''Naval Postgraduate School (US)''<br />
<br />
[mailto:dholwell@nps.edu dholwell@nps.edu]<br />
|-<br />
<br />
|}<br />
<br />
<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Associate Editors<br />
<br />
|-<br />
|'''Richard Adcock'''<br />
<br />
''Cranfield University and INCOSE UK (UK)''<br />
<br />
[mailto:r.d.adcock@cranfield.ac.uk r.d.adcock@cranfield.ac.uk]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Cihan Dagli.<br />
<br />
|'''Michael Henshaw'''<br />
<br />
''Loughborough University (UK)''<br />
<br />
<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Judith Dahmann.<br />
|-<br />
|'''Barry Boehm'''<br />
<br />
''University of Southern California (US)''<br />
<br />
[mailto:boehm@usc.edu boehm@usc.edu]<br />
<br />
Responsible for the Systems Engineering Management knowledge area with Greg Parnell and Life Cycle Models knowledge area; both are in Part 3: Systems Engineering and Management.<br />
|'''Chris Paredis'''<br />
<br />
''Georgia Institute of Technology (US)''<br />
<br />
[mailto:chris.paredis@me.gatech.edu chris.paredis@me.gatech.edu]<br />
<br />
Responsible for working across the SEBoK adding material on the theoretical underpinnings of systems engineering, including mathematical foundations.<br />
|-<br />
|'''Cihan Dagli'''<br />
<br />
''Missouri University of Science & Technology (US)''<br />
<br />
<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Rick Adcock.<br />
|'''Gregory Parnell'''<br />
<br />
''University of Arkansas (US)''<br />
<br />
[mailto:greg.parnell@gmail.com greg.parnell@gmail.com]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Dov Dori in Part 2: Systems and Systems Engineering and Management with Barry Boehm in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Judith Dahmann'''<br />
<br />
''MITRE Corporation (US)''<br />
<br />
[mailto:jdahmann@mitre.org jdahmann@mitre.org]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Mike Henshaw.<br />
|'''Garry Roedler'''<br />
<br />
''Lockheed Martin (US)''<br />
<br />
<br />
<br />
Responsible for the Concept Definition and System Definition knowledge areas in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Heidi Davidz'''<br />
<br />
''Aerojet Rocketdyne (US)''<br />
<br />
[mailto:heidi.davidz@rocket.com heidi.davidz@rocket.com]<br />
<br />
Responsible for the Enabling Individuals knowledge area with Tim Ferris and the Enabling Teams knowledge area in Part 5: Enabling Systems Engineering.<br />
|'''Samuel Seymour'''<br />
<br />
''Johns Hopkins University Applied Physics Lab (APL) (US)''<br />
<br />
[mailto:sam.seymour@jhuapl.edu sam.seymour@jhuapl.edu]<br />
<br />
Responsible for the Service Systems Engineering knowledge area in Part 4: Applications of Systems Engineering.<br />
|-<br />
|'''Dov Dori'''<br />
<br />
''Technion Israel Institute of Technology (Israel)''<br />
<br />
[mailto:dori@ie.technion.ac.il dori@ie.technion.ac.il]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Greg Parnell. Dov is also developing a new article on Model-Based Systems Engineering.<br />
|'''Ariela Sofer'''<br />
<br />
''George Mason University (US)''<br />
<br />
[mailto:asofer@gmu.edu asofer@gmu.edu]<br />
<br />
Responsible for Part 1, including an overview of systems engineering and an overview of the SEBoK.<br />
|-<br />
|'''Timothy Ferris'''<br />
<br />
''University of South Australia (Australia)''<br />
<br />
[mailto:timothy.ferris@unisa.edu.au timothy.ferris@unisa.edu.au]<br />
<br />
Responsible for the Enabling Individuals knowledge area in Part 5: Enabling Systems Engineering with Heidi Davidz. Tim is also developing a new article on Systems Engineering Education.<br />
|'''Ricardo Valerdi'''<br />
<br />
''University of Arizona (US)''<br />
<br />
[mailto:rvalerdi@email.arizona.edu rvalerdi@email.arizona.edu]<br />
<br />
Responsible for the System Realization knowledge area in Part 3: Systems Engineering and Management. Ricardo is also developing a new article on Systems Engineering References.<br />
|-<br />
|}<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Assistant Editors<br />
|-<br />
<br />
|'''Stephanie Enck'''<br />
<br />
''Naval Postgraduate School''<br />
<br />
[mailto:smenck@nps.edu smenck@nps.edu]<br />
|'''Nicole Hutchison'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:nicole.hutchison@stevens.edu nicole.hutchison@stevens.edu]<br />
|-<br />
|'''Devanandham Henry'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:dhenry@stevens.edu dhenry@stevens.edu]<br />
|<br />
|}<br />
<br />
<br />
<br />
==Interested in Editing?==<br />
The Editor in Chief and Co-Editor in Chief are looking for additional editors to support the evolution of the SEBoK. Editors are responsible for maintaining and updating two to four knowledge areas, including incorporating community feedback. We are specifically interested in support for the following knowledge areas:<br />
*System Deployment and Use<br />
*Product and Service Life Management<br />
*Systems Engineering Standards<br />
*Enabling Businesses and Enterprises<br />
*Systems Engineering and Software Engineering<br />
*Systems Engineering and Project Management<br />
*Systems Engineering and Industrial Engineering<br />
*Systems Engineering and Procurement/Acquisition<br />
*Systems Engineering and Specialty Engineering<br />
*Case Studies<br />
*Vignettes<br />
If you are interested in being considered for participation on the Editorial Board, please contact the BKCASE Staff at [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Governance_and_Editorial_Boards&diff=48710Governance and Editorial Boards2013-08-01T03:32:53Z<p>Dhenry: </p>
<hr />
<div>{|<br />
!colspan="2"|BKCASE Editors-in-Chief<br />
|-<br />
|style="background-color: #ffffff"|<br />
[[File:ArtPyster.jpg|200px]]<br />
<br />
'''Editor in Chief'''<br />
<br />
Art Pyster<br />
<br />
''Stevens Institute of Technology (US)''<br />
<br />
[mailto:art.pyster@stevens.edu art.pyster@stevens.edu]<br />
<br />
|style="background-color: #ffffff"|<br />
[[File:DaveOlwell.jpg|136px]]<br />
<br />
'''Co-Editor in Chief'''<br />
<br />
David H. Olwell<br />
<br />
''Naval Postgraduate School (US)''<br />
<br />
[mailto:dholwell@nps.edu dholwell@nps.edu]<br />
|-<br />
<br />
|}<br />
<br />
<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Associate Editors<br />
<br />
|-<br />
|'''Richard Adcock'''<br />
<br />
''Cranfield University and INCOSE UK (UK)''<br />
<br />
[mailto:r.d.adcock@cranfield.ac.uk r.d.adcock@cranfield.ac.uk]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Cihan Dagli.<br />
<br />
|'''Michael Henshaw'''<br />
<br />
''Loughborough University (UK)''<br />
<br />
[mailto:m.j.d.henshaw@lboro.ac.uk m.j.d.henshaw@lboro.ac.uk]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Judith Dahmann.<br />
|-<br />
|'''Barry Boehm'''<br />
<br />
''University of Southern California (US)''<br />
<br />
[mailto:boehm@usc.edu boehm@usc.edu]<br />
<br />
Responsible for the Systems Engineering Management knowledge area with Greg Parnell and Life Cycle Models knowledge area; both are in Part 3: Systems Engineering and Management.<br />
|'''Chris Paredis'''<br />
<br />
''Georgia Institute of Technology (US)''<br />
<br />
[mailto:chris.paredis@me.gatech.edu chris.paredis@me.gatech.edu]<br />
<br />
Responsible for working across the SEBoK adding material on the theoretical underpinnings of systems engineering, including mathematical foundations.<br />
|-<br />
|'''Cihan Dagli'''<br />
<br />
''Missouri University of Science & Technology (US)''<br />
<br />
[mailto:dagli@mst.edu dagli@mst.edu]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Rick Adcock.<br />
|'''Gregory Parnell'''<br />
<br />
''University of Arkansas (US)''<br />
<br />
[mailto:greg.parnell@gmail.com greg.parnell@gmail.com]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Dov Dori in Part 2: Systems and Systems Engineering and Management with Barry Boehm in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Judith Dahmann'''<br />
<br />
''MITRE Corporation (US)''<br />
<br />
[mailto:jdahmann@mitre.org jdahmann@mitre.org]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Mike Henshaw.<br />
|'''Garry Roedler'''<br />
<br />
''Lockheed Martin (US)''<br />
<br />
[mailto:garry.j.roedler@lmco.com garry.j.roedler@lmco.com]<br />
<br />
Responsible for the Concept Definition and System Definition knowledge areas in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Heidi Davidz'''<br />
<br />
''Aerojet Rocketdyne (US)''<br />
<br />
[mailto:heidi.davidz@rocket.com heidi.davidz@rocket.com]<br />
<br />
Responsible for the Enabling Individuals knowledge area with Tim Ferris and the Enabling Teams knowledge area in Part 5: Enabling Systems Engineering.<br />
|'''Samuel Seymour'''<br />
<br />
''Johns Hopkins University Applied Physics Lab (APL) (US)''<br />
<br />
[mailto:sam.seymour@jhuapl.edu sam.seymour@jhuapl.edu]<br />
<br />
Responsible for the Service Systems Engineering knowledge area in Part 4: Applications of Systems Engineering.<br />
|-<br />
|'''Dov Dori'''<br />
<br />
''Technion Israel Institute of Technology (Israel)''<br />
<br />
[mailto:dori@ie.technion.ac.il dori@ie.technion.ac.il]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Greg Parnell. Dov is also developing a new article on Model-Based Systems Engineering.<br />
|'''Ariela Sofer'''<br />
<br />
''George Mason University (US)''<br />
<br />
[mailto:asofer@gmu.edu asofer@gmu.edu]<br />
<br />
Responsible for Part 1, including an overview of systems engineering and an overview of the SEBoK.<br />
|-<br />
|'''Timothy Ferris'''<br />
<br />
''University of South Australia (Australia)''<br />
<br />
[mailto:timothy.ferris@unisa.edu.au timothy.ferris@unisa.edu.au]<br />
<br />
Responsible for the Enabling Individuals knowledge area in Part 5: Enabling Systems Engineering with Heidi Davidz. Tim is also developing a new article on Systems Engineering Education.<br />
|'''Ricardo Valerdi'''<br />
<br />
''University of Arizona (US)''<br />
<br />
[mailto:rvalerdi@email.arizona.edu rvalerdi@email.arizona.edu]<br />
<br />
Responsible for the System Realization knowledge area in Part 3: Systems Engineering and Management. Ricardo is also developing a new article on Systems Engineering References.<br />
|-<br />
|}<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Assistant Editors<br />
|-<br />
<br />
|'''Stephanie Enck'''<br />
<br />
''Naval Postgraduate School''<br />
<br />
[mailto:smenck@nps.edu smenck@nps.edu]<br />
|'''Nicole Hutchison'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:nicole.hutchison@stevens.edu nicole.hutchison@stevens.edu]<br />
|-<br />
|'''Devanandham Henry'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:dhenry@stevens.edu dhenry@stevens.edu]<br />
|<br />
|}<br />
<br />
<br />
<br />
==Interested in Editing?==<br />
The Editor in Chief and Co-Editor in Chief are looking for additional editors to support the evolution of the SEBoK. Editors are responsible for maintaining and updating two to four knowledge areas, including incorporating community feedback. We are specifically interested in support for the following knowledge areas:<br />
*System Deployment and Use<br />
*Product and Service Life Management<br />
*Systems Engineering Standards<br />
*Enabling Businesses and Enterprises<br />
*Systems Engineering and Software Engineering<br />
*Systems Engineering and Project Management<br />
*Systems Engineering and Industrial Engineering<br />
*Systems Engineering and Procurement/Acquisition<br />
*Systems Engineering and Specialty Engineering<br />
*Case Studies<br />
*Vignettes<br />
If you are interested in being considered for participation on the Editorial Board, please contact the BKCASE Staff at [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=48709SEBoK Review and Adjudication2013-08-01T03:22:17Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is also included in adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under the new governance structure. The adjudication process described here is not applicable to for these releases. Along with SEBoK v. 1.1.2, the [http://www.sebokwiki.org/sandbox| SEBoK Sandbox] has been setup to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1, v. 1.1.1, and v. 1.1.2===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the [http://www.sebokwiki.org/sandbox| SEBoK Sandbox].<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/1.1/PDF/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/1.1/PDF/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/1.1/PDF/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/1.1/PDF/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=48708SEBoK Review and Adjudication2013-08-01T03:21:53Z<p>Dhenry: /* SEBoK v. 1.1, v. 1.1.1, and v. 1.1.2 */</p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is also included in adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under the new governance structure. The adjudication process described here is not applicable to for these releases. Along with SEBoK v. 1.1.2, the SEBoK Sandbox has been setup to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1, v. 1.1.1, and v. 1.1.2===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the [http://www.sebokwiki.org/sandbox| SEBoK Sandbox].<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/1.1/PDF/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/1.1/PDF/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/1.1/PDF/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/1.1/PDF/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=48707SEBoK Review and Adjudication2013-08-01T03:20:32Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is also included in adjudication matrices. <br />
<br />
Since January 2013, versions 1.1 and beyond are being released under the new governance structure. The adjudication process described here is not applicable to for these releases. Along with SEBoK v. 1.1.2, the SEBoK Sandbox has been setup to receive comments and other contributions. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1, v. 1.1.1, and v. 1.1.2===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the SEBoK Sandbox at www.sebokwiki.org/sandbox.<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/1.1/PDF/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/1.1/PDF/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/1.1/PDF/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/1.1/PDF/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=48706SEBoK Review and Adjudication2013-08-01T03:15:45Z<p>Dhenry: </p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that was followed to solicit and adjudicate review comments that have been received on versions 0.25, 0.5, 0.75, 1.0 and 1.0.1 of the SEBoK . A comprehensive list of all comments received and the authors’ response to those comments is also included in adjudication matrices. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1, v. 1.1.1, and v. 1.1.2===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.2. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2. With the publishing of SEBoK v. 1.1.2, contributions will also be possible through the SEBoK Sandbox at www.sebokwiki.org/sandbox.<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/1.1/PDF/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/1.1/PDF/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/1.1/PDF/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/1.1/PDF/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Governance_and_Editorial_Boards&diff=48705Governance and Editorial Boards2013-08-01T03:13:23Z<p>Dhenry: </p>
<hr />
<div>{|<br />
!colspan="2"|BKCASE Editors-in-Chief<br />
|-<br />
|style="background-color: #ffffff"|<br />
[[File:ArtPyster.jpg|200px]]<br />
<br />
'''Editor in Chief'''<br />
<br />
Art Pyster<br />
<br />
''Stevens Institute of Technology (US)''<br />
<br />
[mailto:art.pyster@stevens.edu art.pyster@stevens.edu]<br />
<br />
|style="background-color: #ffffff"|<br />
[[File:DaveOlwell.jpg|136px]]<br />
<br />
'''Co-Editor in Chief'''<br />
<br />
David H. Olwell<br />
<br />
''Naval Postgraduate School (US)''<br />
<br />
[mailto:dholwell@nps.edu dholwell@nps.edu]<br />
|-<br />
<br />
|}<br />
<br />
<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Associate Editors<br />
<br />
|-<br />
|'''Richard Adcock'''<br />
<br />
''Cranfield University and INCOSE UK (UK)''<br />
<br />
[mailto:r.d.adcock@cranfield.ac.uk r.d.adcock@cranfield.ac.uk]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Cihan Dagli.<br />
<br />
|'''Michael Henshaw'''<br />
<br />
''Loughborough University (UK)''<br />
<br />
[mailto:m.j.d.henshaw@lboro.ac.uk m.j.d.henshaw@lboro.ac.uk]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Judith Dahmann.<br />
|-<br />
|'''Barry Boehm'''<br />
<br />
''University of Southern California (US)''<br />
<br />
[mailto:boehm@usc.edu boehm@usc.edu]<br />
<br />
Responsible for the Systems Engineering Management knowledge area with Greg Parnell and Life Cycle Models knowledge area; both are in Part 3: Systems Engineering and Management.<br />
|'''Chris Paredis'''<br />
<br />
''Georgia Institute of Technology (US)''<br />
<br />
[mailto:chris.paredis@me.gatech.edu chris.paredis@me.gatech.edu]<br />
<br />
Responsible for working across the SEBoK adding material on the theoretical underpinnings of systems engineering, including mathematical foundations.<br />
|-<br />
|'''Cihan Dagli'''<br />
<br />
''Missouri University of Science & Technology (US)''<br />
<br />
[mailto:dagli@mst.edu dagli@mst.edu]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Rick Adcock.<br />
|'''Gregory Parnell'''<br />
<br />
''University of Arkansas (US)''<br />
<br />
[mailto:greg.parnell@gmail.com greg.parnell@gmail.com]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Dov Dori in Part 2: Systems and Systems Engineering and Management with Barry Boehm in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Judith Dahmann'''<br />
<br />
''MITRE Corporation (US)''<br />
<br />
[mailto:jdahmann@mitre.org jdahmann@mitre.org]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Mike Henshaw.<br />
|'''Garry Roedler'''<br />
<br />
''Lockheed Martin (US)''<br />
<br />
[mailto:garry.j.roedler@lmco.com garry.j.roedler@lmco.com]<br />
<br />
Responsible for the Concept Definition and System Definition knowledge areas in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Heidi Davidz'''<br />
<br />
''Aerojet Rocketdyne (US)''<br />
<br />
[mailto:heidi.davidz@rocket.com heidi.davidz@rocket.com]<br />
<br />
Responsible for the Enabling Individuals knowledge area with Tim Ferris and the Enabling Teams knowledge area in Part 5: Enabling Systems Engineering.<br />
|'''Samuel Seymour'''<br />
<br />
''Johns Hopkins University Applied Physics Lab (APL) (US)''<br />
<br />
[mailto:sam.seymour@jhuapl.edu sam.seymour@jhuapl.edu]<br />
<br />
Responsible for the Service Systems Engineering knowledge area in Part 4: Applications of Systems Engineering.<br />
|-<br />
|'''Dov Dori'''<br />
<br />
''Technion Israel Institute of Technology (Israel)''<br />
<br />
[mailto:dori@ie.technion.ac.il dori@ie.technion.ac.il]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Greg Parnell. Dov is also developing a new article on Model-Based Systems Engineering.<br />
|'''Ariela Sofer'''<br />
<br />
''George Mason University (US)''<br />
<br />
[mailto:asofer@gmu.edu asofer@gmu.edu]<br />
<br />
Responsible for Part 1, including an overview of systems engineering and an overview of the SEBoK.<br />
|-<br />
|'''Timothy Ferris'''<br />
<br />
''University of South Australia (Australia)''<br />
<br />
[mailto:timothy.ferris@unisa.edu.au timothy.ferris@unisa.edu.au]<br />
<br />
Responsible for the Enabling Individuals knowledge area in Part 5: Enabling Systems Engineering with Heidi Davidz. Tim is also developing a new article on Systems Engineering Education.<br />
|'''Ricardo Valerdi'''<br />
<br />
''University of Arizona (US)''<br />
<br />
[mailto:rvalerdi@email.arizona.edu rvalerdi@email.arizona.edu]<br />
<br />
Responsible for the System Realization knowledge area in Part 3: Systems Engineering and Management. Ricardo is also developing a new article on Systems Engineering References.<br />
|-<br />
|}<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Assistant Editors<br />
|-<br />
<br />
|'''Stephanie Enck'''<br />
<br />
''Naval Postgraduate School''<br />
<br />
[mailto:smenck@nps.edu smenck@nps.edu]<br />
|'''Devanandham Henry'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:dhenry@stevens.edu dhenry@stevens.edu]<br />
|-<br />
|'''Nicole Hutchison'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:nicole.hutchison@stevens.edu nicole.hutchison@stevens.edu]<br />
|<br />
|}<br />
<br />
<br />
<br />
==Interested in Editing?==<br />
The Editor in Chief and Co-Editor in Chief are looking for additional editors to support the evolution of the SEBoK. Editors are responsible for maintaining and updating two to four knowledge areas, including incorporating community feedback. We are specifically interested in support for the following knowledge areas:<br />
*System Deployment and Use<br />
*Product and Service Life Management<br />
*Systems Engineering Standards<br />
*Enabling Businesses and Enterprises<br />
*Systems Engineering and Software Engineering<br />
*Systems Engineering and Project Management<br />
*Systems Engineering and Industrial Engineering<br />
*Systems Engineering and Procurement/Acquisition<br />
*Systems Engineering and Specialty Engineering<br />
*Case Studies<br />
*Vignettes<br />
If you are interested in being considered for participation on the Editorial Board, please contact the BKCASE Staff at [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Governance_and_Editorial_Boards&diff=48704Governance and Editorial Boards2013-08-01T03:10:53Z<p>Dhenry: </p>
<hr />
<div>{|<br />
!colspan="2"|BKCASE Editors-in-Chief<br />
|-<br />
|style="background-color: #ffffff"|<br />
[[File:ArtPyster.jpg|200px]]<br />
<br />
'''Editor in Chief'''<br />
<br />
Art Pyster<br />
<br />
''Stevens Institute of Technology (US)''<br />
<br />
[mailto:art.pyster@stevens.edu art.pyster@stevens.edu]<br />
<br />
|style="background-color: #ffffff"|<br />
[[File:DaveOlwell.jpg|136px]]<br />
<br />
'''Co-Editor in Chief'''<br />
<br />
David H. Olwell<br />
<br />
''Naval Postgraduate School (US)''<br />
<br />
[mailto:dholwell@nps.edu dholwell@nps.edu]<br />
|-<br />
<br />
|}<br />
<br />
<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Associate Editors<br />
<br />
|-<br />
|'''Richard Adcock'''<br />
<br />
''Cranfield University and INCOSE UK (UK)''<br />
<br />
[mailto:r.d.adcock@cranfield.ac.uk r.d.adcock@cranfield.ac.uk]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Cihan Dagli.<br />
<br />
|'''Michael Henshaw'''<br />
<br />
''Loughborough University (UK)''<br />
<br />
[mailto:m.j.d.henshaw@lboro.ac.uk m.j.d.henshaw@lboro.ac.uk]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Judith Dahmann.<br />
|-<br />
|'''Barry Boehm'''<br />
<br />
''University of Southern California (US)''<br />
<br />
[mailto:boehm@usc.edu boehm@usc.edu]<br />
<br />
Responsible for the Systems Engineering Management knowledge area with Greg Parnell and Life Cycle Models knowledge area; both are in Part 3: Systems Engineering and Management.<br />
|'''Chris Paredis'''<br />
<br />
''Georgia Institute of Technology (US)''<br />
<br />
[mailto:chris.paredis@me.gatech.edu chris.paredis@me.gatech.edu]<br />
<br />
Responsible for working across the SEBoK adding material on the theoretical underpinnings of systems engineering, including mathematical foundations.<br />
|-<br />
|'''Cihan Dagli'''<br />
<br />
''Missouri University of Science & Technology (US)''<br />
<br />
[mailto:dagli@mst.edu dagli@mst.edu]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Rick Adcock.<br />
|'''Gregory Parnell'''<br />
<br />
''University of Arkansas (US)''<br />
<br />
[mailto:greg.parnell@gmail.com greg.parnell@gmail.com]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Dov Dori in Part 2: Systems and Systems Engineering and Management with Barry Boehm in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Judith Dahmann'''<br />
<br />
''MITRE Corporation (US)''<br />
<br />
[mailto:jdahmann@mitre.org jdahmann@mitre.org]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Mike Henshaw.<br />
|'''Garry Roedler'''<br />
<br />
''Lockheed Martin (US)''<br />
<br />
[mailto:garry.j.roedler@lmco.com garry.j.roedler@lmco.com]<br />
<br />
Responsible for the Concept Definition and System Definition knowledge areas in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Heidi Davidz'''<br />
<br />
''Aerojet Rocketdyne (US)''<br />
<br />
[mailto:heidi.davidz@rocket.com heidi.davidz@rocket.com]<br />
<br />
Responsible for the Enabling Individuals knowledge area with Tim Ferris and the Enabling Teams knowledge area in Part 5: Enabling Systems Engineering.<br />
|'''Samuel Seymour'''<br />
<br />
''Johns Hopkins University Applied Physics Lab (APL) (US)''<br />
<br />
[mailto:sam.seymour@jhuapl.edu sam.seymour@jhuapl.edu]<br />
<br />
Responsible for the Service Systems Engineering knowledge area in Part 4: Applications of Systems Engineering.<br />
|-<br />
|'''Dov Dori'''<br />
<br />
''Technion Israel Institute of Technology (Israel)''<br />
<br />
[mailto:dori@ie.technion.ac.il dori@ie.technion.ac.il]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Greg Parnell. Dov is also developing a new article on Model-Based Systems Engineering.<br />
|'''Ariela Sofer'''<br />
<br />
''George Mason University (US)''<br />
<br />
[mailto:asofer@gmu.edu asofer@gmu.edu]<br />
<br />
Responsible for Part 1, including an overview of systems engineering and an overview of the SEBoK.<br />
|-<br />
|'''Timothy Ferris'''<br />
<br />
''University of South Australia (Australia)''<br />
<br />
[mailto:timothy.ferris@unisa.edu.au timothy.ferris@unisa.edu.au]<br />
<br />
Responsible for the Enabling Individuals knowledge area in Part 5: Enabling Systems Engineering with Heidi Davidz. Tim is also developing a new article on Systems Engineering Education.<br />
|'''Ricardo Valerdi'''<br />
<br />
''University of Arizona (US)''<br />
<br />
[mailto:rvalerdi@email.arizona.edu rvalerdi@email.arizona.edu]<br />
<br />
Responsible for the System Realization knowledge area in Part 3: Systems Engineering and Management. Ricardo is also developing a new article on Systems Engineering References.<br />
|-<br />
|}<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Assistant Editors<br />
|-<br />
<br />
|'''Stephanie Enck'''<br />
<br />
''Naval Postgraduate School''<br />
<br />
[mailto:smenck@nps.edu smenck@nps.edu]<br />
|'''Devanandham Henry'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:dhenry@stevens.edu dhenry@stevens.edu]<br />
|-<br />
|'''Nicole Hutchison'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:nicole.hutchison@stevens.edu nicole.hutchison@stevens.edu]<br />
|<br />
|}<br />
<br />
<br />
<br />
==Interested in Editing?==<br />
The Editor in Chief and Co-Editor in Chief are looking for additional editors to support the evolution of the SEBoK. Editors are responsible for maintaining and updating two to four knowledge areas, including incorporating community feedback. We are specifically interested in support for the following knowledge areas:<br />
*System Deployment and Use<br />
*Product and Service Life Management<br />
*Systems Engineering Standards<br />
*Enabling Businesses and Enterprises<br />
*Systems Engineering and Software Engineering<br />
*Systems Engineering and Project Management<br />
*Systems Engineering and Industrial Engineering<br />
*Systems Engineering and Procurement/Acquisition<br />
*Systems Engineering and Specialty Engineering<br />
*Case Studies<br />
*Vignettes<br />
If you are interested in being considered for participation on the Editorial Board, please contact the BKCASE Staff at [mailto:bkcase@stevens.edu bkcase@stevens.edu].</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Governance_and_Editorial_Boards&diff=48703Governance and Editorial Boards2013-08-01T03:09:59Z<p>Dhenry: </p>
<hr />
<div>{|<br />
!colspan="2"|BKCASE Editors-in-Chief<br />
|-<br />
|style="background-color: #ffffff"|<br />
[[File:ArtPyster.jpg|200px]]<br />
<br />
'''Editor in Chief'''<br />
<br />
Art Pyster<br />
<br />
''Stevens Institute of Technology (US)''<br />
<br />
[mailto:art.pyster@stevens.edu art.pyster@stevens.edu]<br />
<br />
|style="background-color: #ffffff"|<br />
[[File:DaveOlwell.jpg|136px]]<br />
<br />
'''Co-Editor in Chief'''<br />
<br />
David H. Olwell<br />
<br />
''Naval Postgraduate School (US)''<br />
<br />
[mailto:dholwell@nps.edu dholwell@nps.edu]<br />
|-<br />
<br />
|}<br />
<br />
<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Associate Editors<br />
<br />
|-<br />
|'''Richard Adcock'''<br />
<br />
''Cranfield University and INCOSE UK (UK)''<br />
<br />
[mailto:r.d.adcock@cranfield.ac.uk r.d.adcock@cranfield.ac.uk]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Cihan Dagli.<br />
<br />
|'''Michael Henshaw'''<br />
<br />
''Loughborough University (UK)''<br />
<br />
[mailto:m.j.d.henshaw@lboro.ac.uk m.j.d.henshaw@lboro.ac.uk]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Judith Dahmann.<br />
|-<br />
|'''Barry Boehm'''<br />
<br />
''University of Southern California (US)''<br />
<br />
[mailto:boehm@usc.edu boehm@usc.edu]<br />
<br />
Responsible for the Systems Engineering Management knowledge area with Greg Parnell and Life Cycle Models knowledge area; both are in Part 3: Systems Engineering and Management.<br />
|'''Chris Paredis'''<br />
<br />
''Georgia Institute of Technology (US)''<br />
<br />
[mailto:chris.paredis@me.gatech.edu chris.paredis@me.gatech.edu]<br />
<br />
Responsible for working across the SEBoK adding material on the theoretical underpinnings of systems engineering, including mathematical foundations.<br />
|-<br />
|'''Cihan Dagli'''<br />
<br />
''Missouri University of Science & Technology (US)''<br />
<br />
[mailto:dagli@mst.edu dagli@mst.edu]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Rick Adcock.<br />
|'''Gregory Parnell'''<br />
<br />
''University of Arkansas''<br />
<br />
[mailto:greg.parnell@gmail.com greg.parnell@gmail.com]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Dov Dori in Part 2: Systems and Systems Engineering and Management with Barry Boehm in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Judith Dahmann'''<br />
<br />
''MITRE Corporation (US)''<br />
<br />
[mailto:jdahmann@mitre.org jdahmann@mitre.org]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Mike Henshaw.<br />
|'''Garry Roedler'''<br />
<br />
''Lockheed Martin (US)''<br />
<br />
[mailto:garry.j.roedler@lmco.com garry.j.roedler@lmco.com]<br />
<br />
Responsible for the Concept Definition and System Definition knowledge areas in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Heidi Davidz'''<br />
<br />
''Aerojet Rocketdyne (US)''<br />
<br />
[mailto:heidi.davidz@rocket.com heidi.davidz@rocket.com]<br />
<br />
Responsible for the Enabling Individuals knowledge area with Tim Ferris and the Enabling Teams knowledge area in Part 5: Enabling Systems Engineering.<br />
|'''Samuel Seymour'''<br />
<br />
''Johns Hopkins University Applied Physics Lab (APL) (US)''<br />
<br />
[mailto:sam.seymour@jhuapl.edu sam.seymour@jhuapl.edu]<br />
<br />
Responsible for the Service Systems Engineering knowledge area in Part 4: Applications of Systems Engineering.<br />
|-<br />
|'''Dov Dori'''<br />
<br />
''Technion Israel Institute of Technology (Israel)''<br />
<br />
[mailto:dori@ie.technion.ac.il dori@ie.technion.ac.il]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Greg Parnell. Dov is also developing a new article on Model-Based Systems Engineering.<br />
|'''Ariela Sofer'''<br />
<br />
''George Mason University (US)''<br />
<br />
[mailto:asofer@gmu.edu asofer@gmu.edu]<br />
<br />
Responsible for Part 1, including an overview of systems engineering and an overview of the SEBoK.<br />
|-<br />
|'''Timothy Ferris'''<br />
<br />
''University of South Australia (Australia)''<br />
<br />
[mailto:timothy.ferris@unisa.edu.au timothy.ferris@unisa.edu.au]<br />
<br />
Responsible for the Enabling Individuals knowledge area in Part 5: Enabling Systems Engineering with Heidi Davidz. Tim is also developing a new article on Systems Engineering Education.<br />
|'''Ricardo Valerdi'''<br />
<br />
''University of Arizona (US)''<br />
<br />
[mailto:rvalerdi@email.arizona.edu rvalerdi@email.arizona.edu]<br />
<br />
Responsible for the System Realization knowledge area in Part 3: Systems Engineering and Management. Ricardo is also developing a new article on Systems Engineering References.<br />
|-<br />
|}<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Assistant Editors<br />
|-<br />
<br />
|'''Stephanie Enck'''<br />
<br />
''Naval Postgraduate School''<br />
<br />
[mailto:smenck@nps.edu smenck@nps.edu]<br />
|'''Devanandham Henry'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:dhenry@stevens.edu dhenry@stevens.edu]<br />
|-<br />
|'''Nicole Hutchison'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:nicole.hutchison@stevens.edu nicole.hutchison@stevens.edu]<br />
|<br />
|}<br />
<br />
<br />
<br />
==Interested in Editing?==<br />
The Editor in Chief and Co-Editor in Chief are looking for additional editors to support the evolution of the SEBoK. Editors are responsible for maintaining and updating two to four knowledge areas, including incorporating community feedback. We are specifically interested in support for the following knowledge areas:<br />
*System Deployment and Use<br />
*Product and Service Life Management<br />
*Systems Engineering Standards<br />
*Enabling Businesses and Enterprises<br />
*Systems Engineering and Software Engineering<br />
*Systems Engineering and Project Management<br />
*Systems Engineering and Industrial Engineering<br />
*Systems Engineering and Procurement/Acquisition<br />
*Systems Engineering and Specialty Engineering<br />
*Case Studies<br />
*Vignettes<br />
If you are interested in being considered for participation on the Editorial Board, please contact the BKCASE Staff at [mailto:bkcase@stevens.edu bkcase@stevens.edu].</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Governance_and_Editorial_Boards&diff=48702Governance and Editorial Boards2013-08-01T03:07:34Z<p>Dhenry: </p>
<hr />
<div>{|<br />
!colspan="2"|BKCASE Editors-in-Chief<br />
|-<br />
|style="background-color: #ffffff"|<br />
[[File:ArtPyster.jpg|200px]]<br />
<br />
'''Editor in Chief'''<br />
<br />
Art Pyster<br />
<br />
''Stevens Institute of Technology (US)''<br />
<br />
[mailto:art.pyster@stevens.edu art.pyster@stevens.edu]<br />
<br />
|style="background-color: #ffffff"|<br />
[[File:DaveOlwell.jpg|136px]]<br />
<br />
'''Co-Editor in Chief'''<br />
<br />
David H. Olwell<br />
<br />
''Naval Postgraduate School (US)''<br />
<br />
[mailto:dholwell@nps.edu dholwell@nps.edu]<br />
|-<br />
<br />
|}<br />
<br />
<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Associate Editors<br />
<br />
|-<br />
|'''Richard Adcock'''<br />
<br />
''Cranfield University and INCOSE UK (UK)''<br />
<br />
[mailto:r.d.adcock@cranfield.ac.uk r.d.adcock@cranfield.ac.uk]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Cihan Dagli.<br />
<br />
|'''Chris Paredis'''<br />
<br />
''Georgia Institute of Technology (US)''<br />
<br />
[mailto:chris.paredis@me.gatech.edu chris.paredis@me.gatech.edu]<br />
<br />
Responsible for working across the SEBoK adding material on the theoretical underpinnings of systems engineering, including mathematical foundations.<br />
|-<br />
|'''Barry Boehm'''<br />
<br />
''University of Southern California (US)''<br />
<br />
[mailto:boehm@usc.edu boehm@usc.edu]<br />
<br />
Responsible for the Systems Engineering Management knowledge area with Greg Parnell and Life Cycle Models knowledge area; both are in Part 3: Systems Engineering and Management.<br />
|'''Michael Henshaw''<br />
<br />
''Loughborough University (UK)''<br />
<br />
[mailto:m.j.d.henshaw@lboro.ac.uk m.j.d.henshaw@lboro.ac.uk]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Judith Dahmann.<br />
|-<br />
|'''Cihan Dagli'''<br />
<br />
''Missouri University of Science & Technology (US)''<br />
<br />
[mailto:dagli@mst.edu dagli@mst.edu]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Rick Adcock.<br />
|'''Gregory Parnell'''<br />
<br />
''University of Arkansas''<br />
<br />
[mailto:greg.parnell@gmail.com greg.parnell@gmail.com]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Dov Dori in Part 2: Systems and Systems Engineering and Management with Barry Boehm in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Judith Dahmann'''<br />
<br />
''MITRE Corporation (US)''<br />
<br />
[mailto:jdahmann@mitre.org jdahmann@mitre.org]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Mike Henshaw.<br />
|'''Garry Roedler'''<br />
<br />
''Lockheed Martin (US)''<br />
<br />
[mailto:garry.j.roedler@lmco.com garry.j.roedler@lmco.com]<br />
<br />
Responsible for the Concept Definition and System Definition knowledge areas in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Heidi Davidz'''<br />
<br />
''Aerojet Rocketdyne (US)''<br />
<br />
[mailto:heidi.davidz@rocket.com heidi.davidz@rocket.com]<br />
<br />
Responsible for the Enabling Individuals knowledge area with Tim Ferris and the Enabling Teams knowledge area in Part 5: Enabling Systems Engineering.<br />
|'''Samuel Seymour'''<br />
<br />
''Johns Hopkins University Applied Physics Lab (APL) (US)''<br />
<br />
[mailto:sam.seymour@jhuapl.edu sam.seymour@jhuapl.edu]<br />
<br />
Responsible for the Service Systems Engineering knowledge area in Part 4: Applications of Systems Engineering.<br />
|-<br />
|'''Dov Dori'''<br />
<br />
''Technion Israel Institute of Technology (Israel)''<br />
<br />
[mailto:dori@ie.technion.ac.il dori@ie.technion.ac.il]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Greg Parnell. Dov is also developing a new article on Model-Based Systems Engineering.<br />
|'''Ariela Sofer'''<br />
<br />
''George Mason University (US)''<br />
<br />
[mailto:asofer@gmu.edu asofer@gmu.edu]<br />
<br />
Responsible for Part 1, including an overview of systems engineering and an overview of the SEBoK.<br />
|-<br />
|'''Timothy Ferris'''<br />
<br />
''University of South Australia (Australia)''<br />
<br />
[mailto:timothy.ferris@unisa.edu.au timothy.ferris@unisa.edu.au]<br />
<br />
Responsible for the Enabling Individuals knowledge area in Part 5: Enabling Systems Engineering with Heidi Davidz. Tim is also developing a new article on Systems Engineering Education.<br />
|'''Ricardo Valerdi'''<br />
<br />
''University of Arizona (US)''<br />
<br />
[mailto:rvalerdi@email.arizona.edu rvalerdi@email.arizona.edu]<br />
<br />
Responsible for the System Realization knowledge area in Part 3: Systems Engineering and Management. Ricardo is also developing a new article on Systems Engineering References.<br />
|-<br />
|}<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Assistant Editors<br />
|-<br />
<br />
|'''Stephanie Enck'''<br />
<br />
''Naval Postgraduate School''<br />
<br />
[mailto:smenck@nps.edu smenck@nps.edu]<br />
|'''Devanandham Henry'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:dhenry@stevens.edu dhenry@stevens.edu]<br />
|-<br />
|'''Nicole Hutchison'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:nicole.hutchison@stevens.edu nicole.hutchison@stevens.edu]<br />
|<br />
|}<br />
<br />
<br />
<br />
==Interested in Editing?==<br />
The Editor in Chief and Co-Editor in Chief are looking for additional editors to support the evolution of the SEBoK. Editors are responsible for maintaining and updating two to four knowledge areas, including incorporating community feedback. We are specifically interested in support for the following knowledge areas:<br />
*System Deployment and Use<br />
*Product and Service Life Management<br />
*Systems Engineering Standards<br />
*Enabling Businesses and Enterprises<br />
*Systems Engineering and Software Engineering<br />
*Systems Engineering and Project Management<br />
*Systems Engineering and Industrial Engineering<br />
*Systems Engineering and Procurement/Acquisition<br />
*Systems Engineering and Specialty Engineering<br />
*Case Studies<br />
*Vignettes<br />
If you are interested in being considered for participation on the Editorial Board, please contact the BKCASE Staff at [mailto:bkcase@stevens.edu bkcase@stevens.edu].</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Governance_and_Editorial_Boards&diff=48701Governance and Editorial Boards2013-08-01T03:03:16Z<p>Dhenry: </p>
<hr />
<div>{|<br />
!colspan="2"|BKCASE Editors-in-Chief<br />
|-<br />
|style="background-color: #ffffff"|<br />
[[File:ArtPyster.jpg|200px]]<br />
<br />
'''Editor in Chief'''<br />
<br />
Art Pyster<br />
<br />
''Stevens Institute of Technology (US)''<br />
<br />
[mailto:art.pyster@stevens.edu art.pyster@stevens.edu]<br />
<br />
|style="background-color: #ffffff"|<br />
[[File:DaveOlwell.jpg|137px]]<br />
<br />
'''Co-Editor in Chief'''<br />
<br />
David H. Olwell<br />
<br />
''Naval Postgraduate School (US)''<br />
<br />
[mailto:dholwell@nps.edu dholwell@nps.edu]<br />
|-<br />
<br />
|}<br />
<br />
<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Associate Editors<br />
<br />
|-<br />
|'''Richard Adcock, Associate Editor'''<br />
<br />
''Cranfield University and INCOSE UK (UK)''<br />
<br />
[mailto:r.d.adcock@cranfield.ac.uk r.d.adcock@cranfield.ac.uk]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Cihan Dagli.<br />
<br />
|'''Chris Paredis, Associate Editor'''<br />
<br />
''Georgia Institute of Technology (US)''<br />
<br />
[mailto:chris.paredis@me.gatech.edu chris.paredis@me.gatech.edu]<br />
<br />
Responsible for working across the SEBoK adding material on the theoretical underpinnings of systems engineering, including mathematical foundations.<br />
|-<br />
|'''Barry Boehm, Associate Editor'''<br />
<br />
''University of Southern California (US)''<br />
<br />
[mailto:boehm@usc.edu boehm@usc.edu]<br />
<br />
Responsible for the Systems Engineering Management knowledge area with Greg Parnell and Life Cycle Models knowledge area; both are in Part 3: Systems Engineering and Management.<br />
|'''Michael Henshaw, Associate Editor'''<br />
<br />
''Loughborough University (UK)''<br />
<br />
[mailto:M.J.d.Henshaw@lboro.ac.uk M.J.d.Henshaw@lboro.ac.uk]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Judith Dahmann.<br />
|-<br />
|'''Cihan Dagli, Associate Editor'''<br />
<br />
''Missouri University of Science & Technology (US)''<br />
<br />
[mailto:dagli@mst.edu dagli@mst.edu]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Rick Adcock.<br />
|'''Gregory Parnell, Associate Editor'''<br />
<br />
''University of Arkansas''<br />
<br />
[mailto:greg.parnell@gmail.com greg.parnell@gmail.com]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Dov Dori in Part 2: Systems and Systems Engineering and Management with Barry Boehm in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Judith Dahmann, Associate Editor'''<br />
<br />
''MITRE Corporation (US)''<br />
<br />
[mailto:jdahmann@mitre.org jdahmann@mitre.org]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Mike Henshaw.<br />
|'''Garry Roedler, Associate Editor'''<br />
<br />
''Lockheed Martin (US)''<br />
<br />
[mailto:garry.j.roedler@lmco.com garry.j.roedler@lmco.com]<br />
<br />
Responsible for the Concept Definition and System Definition knowledge areas in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Heidi Davidz, Associate Editor'''<br />
<br />
''Aerojet Rocketdyne (US)''<br />
<br />
[mailto:heidi.davidz@rocket.com heidi.davidz@rocket.com]<br />
<br />
Responsible for the Enabling Individuals knowledge area with Tim Ferris and the Enabling Teams knowledge area in Part 5: Enabling Systems Engineering.<br />
|'''Samuel Seymour, Associate Editor'''<br />
<br />
''Johns Hopkins University Applied Physics Lab (APL) (US)''<br />
<br />
[mailto:sam.seymour@jhuapl.edu sam.seymour@jhuapl.edu]<br />
<br />
Responsible for the Service Systems Engineering knowledge area in Part 4: Applications of Systems Engineering.<br />
|-<br />
|'''Dov Dori, Associate Editor'''<br />
<br />
''Technion Israel Institute of Technology (Israel)''<br />
<br />
[mailto:dori@ie.technion.ac.il dori@ie.technion.ac.il]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Greg Parnell. Dov is also developing a new article on Model-Based Systems Engineering.<br />
|'''Ariela Sofer, Associate Editor'''<br />
<br />
''George Mason University (US)''<br />
<br />
[mailto:asofer@gmu.edu asofer@gmu.edu]<br />
<br />
Responsible for Part 1, including an overview of systems engineering and an overview of the SEBoK.<br />
|-<br />
|'''Timothy Ferris, Associate Editor'''<br />
<br />
''University of South Australia (Australia)''<br />
<br />
[mailto:timothy.ferris@unisa.edu.au timothy.ferris@unisa.edu.au]<br />
<br />
Responsible for the Enabling Individuals knowledge area in Part 5: Enabling Systems Engineering with Heidi Davidz. Tim is also developing a new article on Systems Engineering Education.<br />
|'''Ricardo Valerdi, Associate Editor'''<br />
<br />
''University of Arizona (US)''<br />
<br />
[mailto:rvalerdi@email.arizona.edu rvalerdi@email.arizona.edu]<br />
<br />
Responsible for the System Realization knowledge area in Part 3: Systems Engineering and Management. Ricardo is also developing a new article on Systems Engineering References.<br />
|-<br />
|}<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Assistant Editors<br />
|-<br />
<br />
|'''Stephanie Enck, Assistant Editor'''<br />
<br />
''Naval Postgraduate School''<br />
<br />
[mailto:smenck@nps.edu smenck@nps.edu]<br />
|'''Deva Henry, Assistant Editor'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:dhenry@stevens.edu dhenry@stevens.edu]<br />
|-<br />
|'''Nicole Hutchison, Assistant Editor'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:nicole.hutchison@stevens.edu nicole.hutchison@stevens.edu]<br />
|<br />
|}<br />
<br />
<br />
<br />
==Interested in Editing?==<br />
The Editor in Chief and Co-Editor in Chief are looking for additional editors to support the evolution of the SEBoK. Editors are responsible for maintaining and updating two to four knowledge areas, including incorporating community feedback. We are specifically interested in support for the following knowledge areas:<br />
*System Deployment and Use<br />
*Product and Service Life Management<br />
*Systems Engineering Standards<br />
*Enabling Businesses and Enterprises<br />
*Systems Engineering and Software Engineering<br />
*Systems Engineering and Project Management<br />
*Systems Engineering and Industrial Engineering<br />
*Systems Engineering and Procurement/Acquisition<br />
*Systems Engineering and Specialty Engineering<br />
*Case Studies<br />
*Vignettes<br />
If you are interested in being considered for participation on the Editorial Board, please contact the BKCASE Staff at [mailto:bkcase@stevens.edu bkcase@stevens.edu].</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Governance_and_Editorial_Boards&diff=48700Governance and Editorial Boards2013-08-01T02:52:01Z<p>Dhenry: </p>
<hr />
<div>{|<br />
!colspan="2"|BKCASE Editors-in-Chief<br />
|-<br />
|style="background-color: #ffffff"|<br />
[[File:ArtPyster.jpg|200px]]<br />
<br />
'''Editor in Chief'''<br />
<br />
Art Pyster<br />
<br />
''Stevens Institute of Technology (US)''<br />
<br />
[mailto:art.pyster@stevens.edu art.pyster@stevens.edu]<br />
<br />
|style="background-color: #ffffff"|<br />
[[File:DaveOlwell.jpg|150px]]<br />
<br />
'''Co-Editor in Chief'''<br />
<br />
David H. Olwell<br />
<br />
''Naval Postgraduate School (US)''<br />
<br />
[mailto:dholwell@nps.edu dholwell@nps.edu]<br />
|-<br />
<br />
|}<br />
<br />
<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Associate Editors<br />
<br />
|-<br />
|'''Richard Adcock, Associate Editor'''<br />
<br />
''Cranfield University and INCOSE UK (UK)''<br />
<br />
[mailto:r.d.adcock@cranfield.ac.uk r.d.adcock@cranfield.ac.uk]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Cihan Dagli.<br />
<br />
|'''Chris Paredis, Associate Editor'''<br />
<br />
''Georgia Institute of Technology (US)''<br />
<br />
[mailto:chris.paredis@me.gatech.edu chris.paredis@me.gatech.edu]<br />
<br />
Responsible for working across the SEBoK adding material on the theoretical underpinnings of systems engineering, including mathematical foundations.<br />
|-<br />
|'''Barry Boehm, Associate Editor'''<br />
<br />
''University of Southern California (US)''<br />
<br />
[mailto:boehm@usc.edu boehm@usc.edu]<br />
<br />
Responsible for the Systems Engineering Management knowledge area with Greg Parnell and Life Cycle Models knowledge area; both are in Part 3: Systems Engineering and Management.<br />
|'''Michael Henshaw, Associate Editor'''<br />
<br />
''Loughborough University (UK)''<br />
<br />
[mailto:M.J.d.Henshaw@lboro.ac.uk M.J.d.Henshaw@lboro.ac.uk]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Judith Dahmann.<br />
|-<br />
|'''Cihan Dagli, Associate Editor'''<br />
<br />
''Missouri University of Science & Technology (US)''<br />
<br />
[mailto:dagli@mst.edu dagli@mst.edu]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Rick Adcock.<br />
|'''Gregory Parnell, Associate Editor'''<br />
<br />
''University of Arkansas''<br />
<br />
[mailto:greg.parnell@gmail.com greg.parnell@gmail.com]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Dov Dori in Part 2: Systems and Systems Engineering and Management with Barry Boehm in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Judith Dahmann, Associate Editor'''<br />
<br />
''MITRE Corporation (US)''<br />
<br />
[mailto:jdahmann@mitre.org jdahmann@mitre.org]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Mike Henshaw.<br />
|'''Garry Roedler, Associate Editor'''<br />
<br />
''Lockheed Martin (US)''<br />
<br />
[mailto:garry.j.roedler@lmco.com garry.j.roedler@lmco.com]<br />
<br />
Responsible for the Concept Definition and System Definition knowledge areas in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Heidi Davidz, Associate Editor'''<br />
<br />
''Aerojet Rocketdyne (US)''<br />
<br />
[mailto:heidi.davidz@rocket.com heidi.davidz@rocket.com]<br />
<br />
Responsible for the Enabling Individuals knowledge area with Tim Ferris and the Enabling Teams knowledge area in Part 5: Enabling Systems Engineering.<br />
|'''Samuel Seymour, Associate Editor'''<br />
<br />
''Johns Hopkins University Applied Physics Lab (APL) (US)''<br />
<br />
[mailto:sam.seymour@jhuapl.edu sam.seymour@jhuapl.edu]<br />
<br />
Responsible for the Service Systems Engineering knowledge area in Part 4: Applications of Systems Engineering.<br />
|-<br />
|'''Dov Dori, Associate Editor'''<br />
<br />
''Technion Israel Institute of Technology (Israel)''<br />
<br />
[mailto:dori@ie.technion.ac.il dori@ie.technion.ac.il]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Greg Parnell. Dov is also developing a new article on Model-Based Systems Engineering.<br />
|'''Ariela Sofer, Associate Editor'''<br />
<br />
''George Mason University (US)''<br />
<br />
[mailto:asofer@gmu.edu asofer@gmu.edu]<br />
<br />
Responsible for Part 1, including an overview of systems engineering and an overview of the SEBoK.<br />
|-<br />
|'''Timothy Ferris, Associate Editor'''<br />
<br />
''University of South Australia (Australia)''<br />
<br />
[mailto:timothy.ferris@unisa.edu.au timothy.ferris@unisa.edu.au]<br />
<br />
Responsible for the Enabling Individuals knowledge area in Part 5: Enabling Systems Engineering with Heidi Davidz. Tim is also developing a new article on Systems Engineering Education.<br />
|'''Ricardo Valerdi, Associate Editor'''<br />
<br />
''University of Arizona (US)''<br />
<br />
[mailto:rvalerdi@email.arizona.edu rvalerdi@email.arizona.edu]<br />
<br />
Responsible for the System Realization knowledge area in Part 3: Systems Engineering and Management. Ricardo is also developing a new article on Systems Engineering References.<br />
|-<br />
|}<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Assistant Editors<br />
|-<br />
<br />
|'''Stephanie Enck, Assistant Editor'''<br />
<br />
''Naval Postgraduate School''<br />
<br />
[mailto:smenck@nps.edu smenck@nps.edu]<br />
|'''Deva Henry, Assistant Editor'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:dhenry@stevens.edu dhenry@stevens.edu]<br />
|-<br />
|'''Nicole Hutchison, Assistant Editor'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:nicole.hutchison@stevens.edu nicole.hutchison@stevens.edu]<br />
|<br />
|}<br />
<br />
<br />
<br />
==Interested in Editing?==<br />
The Editor in Chief and Co-Editor in Chief are looking for additional editors to support the evolution of the SEBoK. Editors are responsible for maintaining and updating two to four knowledge areas, including incorporating community feedback. We are specifically interested in support for the following knowledge areas:<br />
*System Deployment and Use<br />
*Product and Service Life Management<br />
*Systems Engineering Standards<br />
*Enabling Businesses and Enterprises<br />
*Systems Engineering and Software Engineering<br />
*Systems Engineering and Project Management<br />
*Systems Engineering and Industrial Engineering<br />
*Systems Engineering and Procurement/Acquisition<br />
*Systems Engineering and Specialty Engineering<br />
*Case Studies<br />
*Vignettes<br />
If you are interested in being considered for participation on the Editorial Board, please contact the BKCASE Staff at [mailto:bkcase@stevens.edu bkcase@stevens.edu].</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Governance_and_Editorial_Boards&diff=48699Governance and Editorial Boards2013-08-01T02:50:22Z<p>Dhenry: </p>
<hr />
<div><br />
{|<br />
!colspan="2"|BKCASE Editors-in-Chief<br />
|-<br />
|style="background-color: #ffffff"|<br />
[[File:ArtPyster.jpg|200px]]<br />
<br />
'''Editor in Chief'''<br />
<br />
Art Pyster<br />
<br />
''Stevens Institute of Technology (US)''<br />
<br />
[mailto:art.pyster@stevens.edu art.pyster@stevens.edu]<br />
<br />
|style="background-color: #ffffff"|<br />
[[File:DaveOlwell.jpg|150px]]<br />
<br />
'''Co-Editor in Chief'''<br />
<br />
David H. Olwell<br />
<br />
''Naval Postgraduate School (US)''<br />
<br />
[mailto:dholwell@nps.edu dholwell@nps.edu]<br />
|-<br />
|}<br />
<br />
<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Associate Editors<br />
<br />
|-<br />
|'''Richard Adcock, Associate Editor'''<br />
<br />
''Cranfield University and INCOSE UK (UK)''<br />
<br />
[mailto:r.d.adcock@cranfield.ac.uk r.d.adcock@cranfield.ac.uk]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Cihan Dagli.<br />
<br />
|'''Chris Paredis, Associate Editor'''<br />
<br />
''Georgia Institute of Technology (US)''<br />
<br />
[mailto:chris.paredis@me.gatech.edu chris.paredis@me.gatech.edu]<br />
<br />
Responsible for working across the SEBoK adding material on the theoretical underpinnings of systems engineering, including mathematical foundations.<br />
|-<br />
|'''Barry Boehm, Associate Editor'''<br />
<br />
''University of Southern California (US)''<br />
<br />
[mailto:boehm@usc.edu boehm@usc.edu]<br />
<br />
Responsible for the Systems Engineering Management knowledge area with Greg Parnell and Life Cycle Models knowledge area; both are in Part 3: Systems Engineering and Management.<br />
|'''Michael Henshaw, Associate Editor'''<br />
<br />
''Loughborough University (UK)''<br />
<br />
[mailto:M.J.d.Henshaw@lboro.ac.uk M.J.d.Henshaw@lboro.ac.uk]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Judith Dahmann.<br />
|-<br />
|'''Cihan Dagli, Associate Editor'''<br />
<br />
''Missouri University of Science & Technology (US)''<br />
<br />
[mailto:dagli@mst.edu dagli@mst.edu]<br />
<br />
Responsible for the Systems Fundamentals, Systems Science, Systems Thinking, and Systems Approach Applied to Engineered Systems knowledge areas in Part 2: Systems along with Rick Adcock.<br />
|'''Gregory Parnell, Associate Editor'''<br />
<br />
''University of Arkansas''<br />
<br />
[mailto:greg.parnell@gmail.com greg.parnell@gmail.com]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Dov Dori in Part 2: Systems and Systems Engineering and Management with Barry Boehm in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Judith Dahmann, Associate Editor'''<br />
<br />
''MITRE Corporation (US)''<br />
<br />
[mailto:jdahmann@mitre.org jdahmann@mitre.org]<br />
<br />
Responsible for Product Systems Engineering, Enterprise Systems Engineering, and System of Systems Engineering in Part 4: Applications of Systems Engineering with Mike Henshaw.<br />
|'''Garry Roedler, Associate Editor'''<br />
<br />
''Lockheed Martin (US)''<br />
<br />
[mailto:garry.j.roedler@lmco.com garry.j.roedler@lmco.com]<br />
<br />
Responsible for the Concept Definition and System Definition knowledge areas in Part 3: Systems Engineering and Management.<br />
|-<br />
|'''Heidi Davidz, Associate Editor'''<br />
<br />
''Aerojet Rocketdyne (US)''<br />
<br />
[mailto:heidi.davidz@rocket.com heidi.davidz@rocket.com]<br />
<br />
Responsible for the Enabling Individuals knowledge area with Tim Ferris and the Enabling Teams knowledge area in Part 5: Enabling Systems Engineering.<br />
|'''Samuel Seymour, Associate Editor'''<br />
<br />
''Johns Hopkins University Applied Physics Lab (APL) (US)''<br />
<br />
[mailto:sam.seymour@jhuapl.edu sam.seymour@jhuapl.edu]<br />
<br />
Responsible for the Service Systems Engineering knowledge area in Part 4: Applications of Systems Engineering.<br />
|-<br />
|'''Dov Dori, Associate Editor'''<br />
<br />
''Technion Israel Institute of Technology (Israel)''<br />
<br />
[mailto:dori@ie.technion.ac.il dori@ie.technion.ac.il]<br />
<br />
Responsible for the Representing Systems with Models knowledge area with Greg Parnell. Dov is also developing a new article on Model-Based Systems Engineering.<br />
|'''Ariela Sofer, Associate Editor'''<br />
<br />
''George Mason University (US)''<br />
<br />
[mailto:asofer@gmu.edu asofer@gmu.edu]<br />
<br />
Responsible for Part 1, including an overview of systems engineering and an overview of the SEBoK.<br />
|-<br />
|'''Timothy Ferris, Associate Editor'''<br />
<br />
''University of South Australia (Australia)''<br />
<br />
[mailto:timothy.ferris@unisa.edu.au timothy.ferris@unisa.edu.au]<br />
<br />
Responsible for the Enabling Individuals knowledge area in Part 5: Enabling Systems Engineering with Heidi Davidz. Tim is also developing a new article on Systems Engineering Education.<br />
|'''Ricardo Valerdi, Associate Editor'''<br />
<br />
''University of Arizona (US)''<br />
<br />
[mailto:rvalerdi@email.arizona.edu rvalerdi@email.arizona.edu]<br />
<br />
Responsible for the System Realization knowledge area in Part 3: Systems Engineering and Management. Ricardo is also developing a new article on Systems Engineering References.<br />
|-<br />
|}<br />
<br />
<br />
{|<br />
!colspan="2"|BKCASE Assistant Editors<br />
|-<br />
<br />
|'''Stephanie Enck, Assistant Editor'''<br />
<br />
''Naval Postgraduate School''<br />
<br />
[mailto:smenck@nps.edu smenck@nps.edu]<br />
|'''Deva Henry, Assistant Editor'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:dhenry@stevens.edu dhenry@stevens.edu]<br />
|-<br />
|'''Nicole Hutchison, Assistant Editor'''<br />
<br />
''Stevens Institute of Technology''<br />
<br />
[mailto:nicole.hutchison@stevens.edu nicole.hutchison@stevens.edu]<br />
|<br />
|}<br />
<br />
<br />
<br />
==Interested in Editing?==<br />
The Editor in Chief and Co-Editor in Chief are looking for additional editors to support the evolution of the SEBoK. Editors are responsible for maintaining and updating two to four knowledge areas, including incorporating community feedback. We are specifically interested in support for the following knowledge areas:<br />
*System Deployment and Use<br />
*Product and Service Life Management<br />
*Systems Engineering Standards<br />
*Enabling Businesses and Enterprises<br />
*Systems Engineering and Software Engineering<br />
*Systems Engineering and Project Management<br />
*Systems Engineering and Industrial Engineering<br />
*Systems Engineering and Procurement/Acquisition<br />
*Systems Engineering and Specialty Engineering<br />
*Case Studies<br />
*Vignettes<br />
If you are interested in being considered for participation on the Editorial Board, please contact the BKCASE Staff at [mailto:bkcase@stevens.edu bkcase@stevens.edu].</div>Dhenryhttps://sebokwiki.org/w/index.php?title=How_to_Read_the_SEBoK&diff=48591How to Read the SEBoK2013-06-14T20:26:56Z<p>Dhenry: </p>
<hr />
<div>The SEBoK is implemented as a ''wiki'' with more than 100 articles about various [[Systems Engineering (glossary)|systems engineering]] (SE) topics, such as [[Emergence|emergence]] and [[System Requirements|system requirements]]. Those articles are grouped into 26 knowledge areas, which are further grouped into 7 parts. The underlying engine for the SEBoK wiki, mediawiki, is the same engine used by wikipedia (see http://www.wikipedia.org), but many customizations have been made for the SEBoK. This article explains the special features of the SEBoK wiki implementation and also suggests how you can navigate the SEBoK to find SE information of interest.<br />
<br />
==Wiki Features==<br />
<br />
Most of the features of the SEBoK are self-evident to anyone familiar with normal website navigation mechanisms or who has ever used a common wiki such as wikipedia (see http://www.wikipedia.org). Nevertheless, it is worthwhile highlighting the content on the left-hand side of each page, which is always the same and always has four sections:<br />
<br />
*Quicklinks<br />
*Outline<br />
*Navigation<br />
*Toolbox<br />
<br />
<font size=3>'''Quicklinks'''</font><br />
<br />
The seven quicklinks are hotlinks that are likely to be of main interest to new SEBoK users. You are now looking at one of them, ''How to Read the SEBoK''. The purpose of most of the quicklinks is self-apparent, but of special note is [[Bkcase Wiki:Copyright|copyright information]], which explains what you may do with the information found on the SEBoK. All of the information contained in the SEBoK is copyright protected, but can be accessed and viewed without cost by anyone through the Internet. On the other hand, there are restrictions on what you can do with that information beyond access and viewing. Please look at the [[Bkcase Wiki:Copyright|Copyright Information]] article for complete information.<br />
<br />
<font size=3>'''Outline'''</font><br />
<br />
The SEBoK is divided into seven major ''parts'', each of which is further divided into ''knowledge areas''; these are in turn divided into related ''topics''. The hierarchical structure of the SEBoK is represented in the outline. Conveniently, the outline auto-expands to show the article you are currently reading.<br />
<br />
<font size=3>'''Navigation'''</font><br />
<br />
A webpage containing each of the structural elements of the SEBoK can be accessed by clicking the element name; .e.g., clicking on [[Glossary of Terms]] takes you to a webpage containing all glossary entries.<br />
<br />
<font size=3>'''Toolbox'''</font><br />
<br />
The [[Toolbox]] contains two features. ''Cite this page'' provides full information to cite the specific article that you are currently viewing; this information is provided in various common citation styles including APA, MLA and Chicago. ''What Links Here'' takes you to a webpage that shows all the other pages within the SEBoK that link to the page you were just viewing. Readers should rarely need to use the toolbox links.<br />
<br />
===Breadcrumbs===<br />
In addition to the features listed above, the wiki also contains a feature for tracking the path you navigate. As you move through the wiki, the last 5 pages you have visited will be listed at the top of the page. These "breadcrumbs" provide an easy way for you to return to articles you've recently viewed.<br />
<br />
==Finding Information==<br />
If you are new to SE, we suggest you begin by visiting Part 1, [[SEBoK v. 1.1.1 Introduction]]. It provides an excellent overview of the SE discipline, the history of SE, and other useful insights. Note that every topic has one or more primary references, which are those generally available readings the SEBoK authors believe have the best coverage of that topic. For example, the topic [[Systems Engineering Overview]] suggests the INCOSE Systems Engineering Handbook as an excellent introduction to SE, and the topic [[Economic Value of Systems Engineering]] recommends three articles by authors Boehm, Honour, and Valerdi as "must reads". Each primary reference has its own webpage which provides full citation information, indicates all the articles that cite it, and in many cases, elaborates on its content. You can browse through the entire set of more than 200 primary references at [[Primary References]]. Similarly, the SEBoK defines more than 350 important glossary terms, such as [[Architecture (glossary)|architecture]] and [[Verification (glossary)|verification]]. When you read an article that uses one of these terms, it will generally be a hotlink that will take you to a separate webpage which contains one or more definitions for the term, the source for each definition, and other places in the SEBoK that also link to that webpage. You can browse the entire glossary at [[Glossary of Terms]].<br />
<br />
If you are already familiar with SE and want to look for a specific topic, you have several options available. First, you can type the word or phrase in the search box at the top right hand corner of any page, hit "Go", and view the results to see where in the SEBoK you can find the sought after information. You can also use the outline structure of the SEBoK, shown on the left-hand side of every page, to select a specific part, knowledge area, or topic. Still another approach is to read the use cases called out in [[SEBoK Users and Uses]] in Part 1, which suggest ways in which you might find valuable information for different purposes.<br />
<br />
==Article Format==<br />
Each article has the same basic structure.<br />
<br />
At the top is an introduction to the article content, followed by the table of contents of the article, followed by sections containing the main body of information in the article. To promote readability, articles are generally no longer than 2000 words. Most articles contain hyperlinks to other articles, glossary terms, primary references, and even to external websites outside the SEBoK. <br />
<br />
Towards the bottom of each article are the references, which are divided into ''works cited'', ''primary references'', and ''additional references''. Works cited, as the name implies, are simply the full citations for articles, books, and websites found in the article. As described earlier, primary references are works that the SEBoK authors recommend anyone who wishes to know about the topic read. Finally, additional references are works that the SEBoK authors think are worthwhile for you to read beyond the primary references if you want to learn about the topic in greater depth. ''Works cited'' may also appear in the ''primary references'' or ''additional references,'' and when that occurs, it signals to the reader that they are encouraged to read beyond the actual cited portion of the work. Citation formats largely follow the Chicago Manual of Style; however this manual does not provide a format for citing standards. Because of this, standards are formatted as reports with the standard number replacing the report number.<br />
<br />
At the end of each article is a DISQUS segment where you can enter comments about the article, such as possible improvements or corrections or where you can simply state your opinion about what you read. Because DISQUS supports threaded comments, you can also reply to previously posted comments.<br />
<br />
You can also vote whether you ''like'' the article, using the familiar Facebook interface.<br />
<br />
The SEBoK editors will monitor all of your comments and suggestions to use when planning periodic updates to the SEBoK.<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=SEBoK_Review_and_Adjudication&diff=48502SEBoK Review and Adjudication2013-06-13T02:15:31Z<p>Dhenry: /* SEBoK v. 1.1 */</p>
<hr />
<div>The participation of the worldwide systems engineering community in the open collaboration process played a significant role in shaping the development versions of SEBoK leading to release of v. 1.0 in September 2012 (see [[Release History]]). It is expected that community participation and review of the content will continue to keep the content of the SEBoK useful, current, and relevant.<br />
<br />
This article outlines the process that is followed to solicit and adjudicate review comments that have been received on all versions of the SEBoK till the current release (i.e. versions 0.25, 0.5, 0.75, 1.0 and 1.0.1). A comprehensive list of all comments received and the authors’ response to those comments is also included in adjudication matrices. <br />
<br />
==Reviewers and Review Comments==<br />
<br />
===SEBoK v. 0.25===<br />
The first version of the SEBoK, version 0.25, was released as a document for limited review in September 2010. A list of potential reviewers was compiled based on <br />
*direct requests to professional societies, corporations, and academic institutions; and<br />
*volunteers who responded to requests during SEBoK related presentations and talks at conferences and other events.<br />
The SEBoK v. 0.25 document, along with a review form with over thirty questions and detailed instructions were distributed to the potential reviewers. <br />
<br />
Reviews were received from 114 reviewers who provided over 3000 comments by December 2010.<br />
<br />
===SEBoK v. 0.5===<br />
A number of changes in the structure and content of the SEBoK was made in response to the review comments received for SEBoK v. 0.25. The next version of the SEBoK, version 0.5, was released in September 2011, as a wiki. In addition to providing easy access and navigation of the SEBoK, the wiki platform also enabled broader review by the worldwide systems engineering community. Release information and requests for review were sent out to an updated list of reviewers. Review comments on individual articles were predominantly received on the wiki. A review form was also distributed to receive overarching comments on the SEBoK as a whole and on the wiki implementation. Comments were also received in various other formats including emails, spreadsheets and marked-up documents until December 2011.<br />
<br />
===SEBoK v. 0.75===<br />
Though not originally planned, the third interim version of the SEBoK, version 0.75, was released in March 2012 for a short limited period review until April 2012. Not all of the review comments were addressed in SEBoK v. 0.75. The wiki platform was well received by the worldwide SE community and so was retained for future releases of the SEBoK. More features for reviewing and navigating were added to the SEBoK wiki. The wiki remained open for review, though it was stated that the adjudication of those comments may not be addressed for SEBoK v. 1.0.<br />
<br />
===SEBoK v. 1.0 and v. 1.0.1===<br />
The first production version of the SEBoK, version 1.0, was released in September 2012. In November 2012, version 1.0.1, a micro update was released to correct a few errors but with no significant change in the content. Unlike previous developmental versions of the SEBoK, public review of SEBoK v. 1.0 and v. 1.0.1 was not intentionally solicited but users were strongly encouraged to provide their comments and feedback.<br />
<br />
===SEBoK v. 1.1 and v. 1.1.1===<br />
Beginning in January 2013, the SEBoK began operating under a new governance structure, led by INCOSE, IEEE-CS, and the SERC acting jointly as stewards (see [[Acknowledgements]]). Version 1.1 was the first SEBoK release under this new governance structure and the newly formed BKCASE Editorial Board that is still evolving. As a result, adjudication of some comments received on versions 1.0 and 1.0.1 is being deferred to future versions of the SEBoK.<br />
<br />
The wiki continues to remain open to review comments on the latest release, SEBoK v. 1.1.1. Comments received will be adjudicated and reported in the next minor version of the SEBoK, version 1.2.<br />
<br />
==Adjudication Process==<br />
A thorough process involving the authors and Part Team Leads (PTLs) was used to address every review comment received on the SEBoK. This process largely remained the same for all versions of the SEBoK that were released. Since January 2013, a new governance structure is in place where there are no PTLs. However, the overall process was retained for adjudicating comments received on versions 1.0 and 1.0.1. <br />
<br />
The following broad steps were followed for adjudication:<br />
#All comments received in various formats were all compiled in matrices as spreadsheets, segregated by SEBoK parts. When warranted, compound comments were broken down into individual comments to support effective response to the comments. <br />
#The comments were then distributed to the respective PTLs and authors.<br />
#The authors responded to every review comment by choosing one of the adjudication actions listed in Table 1 below. Where required, authors provided reasons and rationale for their decision on particular review comments.<br />
#Adjudication matrices were then re-compiled incorporating author responses as spreadsheets for further use and distribution.<br />
<br />
<br />
<center><br />
{|<br />
|+'''Table 1. Types of Adjudication Actions.''' (SEBoK Original)<br />
! Action <br />
! Description<br />
|-<br />
|'''Accepted'''<br />
|<br />
*The comment from the reviewer has been accepted in '''whole''', and suggested action has been taken. <br />
|-<br />
| '''Modified'''<br />
|<br />
*The comment from the reviewer has been accepted in '''part''' and suggested action has been taken with some modification(s).<br />
*Details of the modification is provided. <br />
|-<br />
|'''Declined'''<br />
|<br />
*Suggestion recommended by the reviewer has been declined.<br />
*Rationale for this decision is provided<br />
|-<br />
|''' Noted'''<br />
|<br />
*The comment made by the reviewer requires no further action. <br />
|-<br />
| '''Copy'''<br />
|<br />
*This comment is similar to a comment already received and adjudicated (in this or earlier version of the SEBoK). <br />
|-<br />
| '''Deferred'''<br />
|<br />
*Response to the comment is deferred to a future version of the SEBoK. <br />
|}<br />
</center><br />
<br />
==Adjudication Matrices==<br />
<br />
A detailed adjudication report was prepared based on the reviews received on SEBoK v. 0.25. For the review comments on the 0.5 and 0.75 versions of the SEBoK, the adjudication matrices have been prepared. Adjudication of comments received on the 1.0 and 1.0.1 versions are included in a single matrix. All matrices be may be downloaded (in PDF format) from the following links:<br />
<br />
* [http://sebokwiki.org/1.1/PDF/SEBOKVersion0.25AdjudicationReportFINAL1.pdf SEBoK v. 0.25 Adjudication Report]<br />
* [http://sebokwiki.org/1.1/PDF/SEBoK05_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.5 Adjudication Matrix]<br />
* [http://sebokwiki.org/1.1/PDF/SEBoK075_AdjudicationMatrix_FINAL.pdf SEBoK v. 0.75 Adjudication Matrix]<br />
* [http://sebokwiki.org/1.1/PDF/SEBoK1.0_1.0.1_Adjudication%20Matrix.pdf SEBoK v. 1.0 & 1.0.1 Adjudication Matrix]<br />
<br />
It may be noted that some review comments may be relevant only to the SEBoK version on which the comments were made; content may have changed since then. Names of individual reviewers have not been included in any of the above adjudication matrices. If you reviewed an earlier version of the SEBoK and would like to know your reviewer number and see the responses to your comments, please contact [mailto:bkcase@stevens.edu bkcase@stevens.edu].<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Bkcase_Wiki:Copyright&diff=48501Bkcase Wiki:Copyright2013-06-13T02:03:20Z<p>Dhenry: /* Attribution */</p>
<hr />
<div>'''Please read this page which contains information about how and on what terms you may use, copy, share, quote or cite the Systems Engineering Body of Knowledge (SEBoK):'''<br />
<br />
==Copyright and Licensing==<br />
<br />
A compilation copyright to the SEBoK is held by The Trustees of the Stevens Institute of Technology 2012 (“Stevens”) and copyright to most of the content within the SEBoK is also held by Stevens. Prominently noted throughout the SEBoK are other items of content for which the copyright is held by a third party. These items consist mainly of tables and figures. In each case of third party content, such content is used by Stevens with permission and its use by third parties is limited. <br />
<br />
Stevens is publishing those portions of the SEBoK to which it holds copyright under a Creative Commons Attribution-NonCommercial ShareAlike 3.0 Unported License. See http://creativecommons.org/licenses/by-nc-sa/3.0/deed.en_US for details about what this license allows. This license does not permit use of third party material but gives rights to the systems engineering community to freely use the remainder of the SEBoK within the terms of the license. Stevens is publishing the SEBoK as a compilation including the third party material under the terms of a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported (CC BY-NC-ND 3.0). See http://creativecommons.org/licenses/by-nc-nd/3.0/ for details about what this license allows. This license will permit very limited noncommercial use of the third party content included within the SEBoK and only as part of the SEBoK compilation. Additionally, the U.S. government has limited data rights associated with the SEBoK based on their support for the SEBoK development.<br />
<br />
==Attribution==<br />
<br />
When '''using material from the SEBoK''', users who have accepted one of the Creative Commons Licenses described above terms noted below must attribute the work as follows:<br />
<br />
This material is used under a Creative Commons Attribution-NonCommercial ShareAlike 3.0 Unported License from The Trustees of the Stevens Institute of Technology. See the Stevens Terms for Publication at http://www.sebokwiki.org/index.php/Bkcase_Wiki:Copyright for details.<br />
<br />
When '''citing the SEBoK in general''', users must cite in the following manner:<br />
<br />
Pyster, A. and D. Olwell (eds). 2013. ''The Guide to the Systems Engineering Body of Knowledge (SEBoK)'', v. 1.1.1. Hoboken, NJ: The Trustees of the Stevens Institute of Technology. Accessed DATE. www.sebokwiki.org/<br />
<br />
To '''cite a specific article''' within the SEBoK, please use:<br />
<br />
[[Acknowledgements#Authors|SEBoK Authors]]. "Article Title." in A. Pyster and D. Olwell (eds). 2013. ''The Guide to the Systems Engineering Body of Knowledge (SEBoK)'', v. 1.1.1. Hoboken, NJ: The Trustees of the Stevens Institute of Technology. Accessed DATE. www.sebokwiki.org/<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Download_SEBoK_PDF&diff=48500Download SEBoK PDF2013-06-13T02:02:02Z<p>Dhenry: </p>
<hr />
<div>For those readers who would like to access the SEBoK offline, the editors have generated a set of PDFs. The first PDF listed - "SEBoK v. 1.1" - is a PDF of this version of the SEBoK. <br />
<br />
New PDFs will be generated with each minor and major refresh (e.g. versions 1.1, 1.2, 2.0, etc.). PDFs are ''not'' generated for micro releases (e.g. v. 1.0.1), as these updates are intended to be "bug fix" versions and do not change content. Therefore, PDFs have not been generated for the latest release (v. 1.1.1); the PDFs listed below are from version 1.1.<br />
<br />
==Version 1.1 PDFs==<br />
<br />
In addition to the PDF of all the SEBoK articles, the Editorial Board has also developed individual PDFs for each part. This will enable reviewers who are interested in viewing just one specific part easier access to the information.<br />
<br />
<html><br />
<ul><br />
<li><a href='PDF/SEBoKv1.1_Full.pdf' target='_blank' onclick='var that=this;_gaq.push(['_trackEvent','DownloadFull','PDF',this.href]);setTimeout(function(){location.href=that.href;},200);return false;'>SEBoK v. 1.1 (not including Glossary or Primary Reference pages)</a></li><br />
<br />
<li><a href='PDF/SEBoKv.1.1_Part1.pdf' target='_blank' onclick='var that=this;_gaq.push(['_trackEvent','DownloadPart1','PDF',this.href]);setTimeout(function(){location.href=that.href;},200);return false;'>Part 1 - Introduction</a></li><br />
<br />
<li><a href='PDF/SEBoKv.1.1_Part2.pdf' target='_blank' onclick='var that=this;_gaq.push(['_trackEvent','DownloadPart1','PDF',this.href]);setTimeout(function(){location.href=that.href;},200);return false;'>Part 2 - Systems</a></li><br />
<br />
<li><a href='PDF/SEBoKv.1.1_Part3.pdf' target='_blank' onclick='var that=this;_gaq.push(['_trackEvent','DownloadPart1','PDF',this.href]);setTimeout(function(){location.href=that.href;},200);return false;'>Part 3 - Systems Engineering and Management</a></li><br />
<br />
<li><a href='PDF/SEBoKv.1.1_Part4.pdf' target='_blank' onclick='var that=this;_gaq.push(['_trackEvent','DownloadPart1','PDF',this.href]);setTimeout(function(){location.href=that.href;},200);return false;'>Part 4 - Applications of Systems Engineering</a></li><br />
<br />
<li><a href='PDF/SEBoKv.1.1_Part5.pdf' target='_blank' onclick='var that=this;_gaq.push(['_trackEvent','DownloadPart1','PDF',this.href]);setTimeout(function(){location.href=that.href;},200);return false;'>Part 5 - Enabling Systems Engineering</a></li><br />
<br />
<li><a href='PDF/SEBoKv.1.1_Part6.pdf' target='_blank' onclick='var that=this;_gaq.push(['_trackEvent','DownloadPart1','PDF',this.href]);setTimeout(function(){location.href=that.href;},200);return false;'>Part 6 - Related Disciplines</a></li><br />
<br />
<li><a href='PDF/SEBoKv.1.1_Part7.pdf' target='_blank' onclick='var that=this;_gaq.push(['_trackEvent','DownloadPart1','PDF',this.href]);setTimeout(function(){location.href=that.href;},200);return false;'>Part 7 - Systems Engineering Implementation Examples</a></li><br />
<br />
</ul><br />
</html><br />
<br />
==Archive==<br />
Older versions of the SEBoK are archived as PDFs. To access a previous version, please select a download link from the list below.<br />
<br />
*[http://www.sebokwiki.org/1.0/PDF/SEBoKv1.0_Final.pdf SEBoK v. 1.0]<br />
<br />
<center>'''Note: The complete SEBoK is almost 850 pages and over 11 MB, so may take some time to download depending on your connection speed.''' </center><br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=How_to_Read_the_SEBoK&diff=48499How to Read the SEBoK2013-06-13T01:55:36Z<p>Dhenry: /* Finding Information */</p>
<hr />
<div>The SEBoK is implemented as a ''wiki'' with more than 100 articles about various [[Systems Engineering (glossary)|systems engineering]] (SE) topics, such as [[Emergence|emergence]] and [[System Requirements|system requirements]]. Those articles are grouped into 26 knowledge areas, which are further grouped into 7 parts. The underlying engine for the SEBoK wiki, mediawiki, is the same engine used by wikipedia (see http://www.wikipedia.org), but many customizations have been made for the SEBoK. This article explains the special features of the SEBoK wiki implementation and also suggests how you can navigate the SEBoK to find SE information of interest.<br />
<br />
==Wiki Features==<br />
<br />
Most of the features of the SEBoK are self-evident to anyone familiar with normal website navigation mechanisms or who has ever used a common wiki such as wikipedia (see http://www.wikipedia.org). Nevertheless, it is worthwhile highlighting the content on the left-hand side of each page, which is always the same and always has four sections:<br />
<br />
*Quicklinks<br />
*Outline<br />
*Navigation<br />
*Toolbox<br />
<br />
<font size=3>'''Quicklinks'''</font><br />
<br />
The seven quicklinks are hotlinks that are likely to be of main interest to new SEBoK users. You are now looking at one of them, ''How to Read the SEBoK''. The purpose of most of the quicklinks is self-apparent, but of special note is [[Bkcase Wiki:Copyright|copyright information]], which explains what you may do with the information found on the SEBoK. All of the information contained in the SEBoK is copyright protected, but can be accessed and viewed without cost by anyone through the Internet. On the other hand, there are restrictions on what you can do with that information beyond access and viewing. Please look at the [[Bkcase Wiki:Copyright|Copyright Information]] article for complete information.<br />
<br />
<font size=3>'''Outline'''</font><br />
<br />
The SEBoK is divided into seven major ''parts'', each of which is further divided into ''knowledge areas''; these are in turn divided into related ''topics''. The hierarchical structure of the SEBoK is represented in the outline. Conveniently, the outline auto-expands to show the article you are currently reading.<br />
<br />
<font size=3>'''Navigation'''</font><br />
<br />
A webpage containing each of the structural elements of the SEBoK can be accessed by clicking the element name; .e.g., clicking on [[Glossary of Terms]] takes you to a webpage containing all glossary entries.<br />
<br />
<font size=3>'''Toolbox'''</font><br />
<br />
Finally, the [[Toolbox]] contains links to less commonly accessed features; e.g., as the name implies, ''What Links Here'', takes you to a webpage that shows all the other pages within the SEBoK that link to the page you were just viewing. Readers should rarely need to use the toolbox links.<br />
<br />
===Breadcrumbs===<br />
In addition to the features listed above, the wiki also contains a feature for tracking the path you navigate. As you move through the wiki, the last 5 pages you have visited will be listed at the top of the page. These "breadcrumbs" provide an easy way for you to return to articles you've recently viewed.<br />
<br />
==Finding Information==<br />
If you are new to SE, we suggest you begin by visiting Part 1, [[SEBoK v. 1.1.1 Introduction]]. It provides an excellent overview of the SE discipline, the history of SE, and other useful insights. Note that every topic has one or more primary references, which are those generally available readings the SEBoK authors believe have the best coverage of that topic. For example, the topic [[Systems Engineering Overview]] suggests the INCOSE Systems Engineering Handbook as an excellent introduction to SE, and the topic [[Economic Value of Systems Engineering]] recommends three articles by authors Boehm, Honour, and Valerdi as "must reads". Each primary reference has its own webpage which provides full citation information, indicates all the articles that cite it, and in many cases, elaborates on its content. You can browse through the entire set of more than 200 primary references at [[Primary References]]. Similarly, the SEBoK defines more than 350 important glossary terms, such as [[Architecture (glossary)|architecture]] and [[Verification (glossary)|verification]]. When you read an article that uses one of these terms, it will generally be a hotlink that will take you to a separate webpage which contains one or more definitions for the term, the source for each definition, and other places in the SEBoK that also link to that webpage. You can browse the entire glossary at [[Glossary of Terms]].<br />
<br />
If you are already familiar with SE and want to look for a specific topic, you have several options available. First, you can type the word or phrase in the search box at the top right hand corner of any page, hit "Go", and view the results to see where in the SEBoK you can find the sought after information. You can also use the outline structure of the SEBoK, shown on the left-hand side of every page, to select a specific part, knowledge area, or topic. Still another approach is to read the use cases called out in [[SEBoK Users and Uses]] in Part 1, which suggest ways in which you might find valuable information for different purposes.<br />
<br />
==Article Format==<br />
Each article has the same basic structure.<br />
<br />
At the top is an introduction to the article content, followed by the table of contents of the article, followed by sections containing the main body of information in the article. To promote readability, articles are generally no longer than 2000 words. Most articles contain hyperlinks to other articles, glossary terms, primary references, and even to external websites outside the SEBoK. <br />
<br />
Towards the bottom of each article are the references, which are divided into ''works cited'', ''primary references'', and ''additional references''. Works cited, as the name implies, are simply the full citations for articles, books, and websites found in the article. As described earlier, primary references are works that the SEBoK authors recommend anyone who wishes to know about the topic read. Finally, additional references are works that the SEBoK authors think are worthwhile for you to read beyond the primary references if you want to learn about the topic in greater depth. ''Works cited'' may also appear in the ''primary references'' or ''additional references,'' and when that occurs, it signals to the reader that they are encouraged to read beyond the actual cited portion of the work. Citation formats largely follow the Chicago Manual of Style; however this manual does not provide a format for citing standards. Because of this, standards are formatted as reports with the standard number replacing the report number.<br />
<br />
At the end of each article is a DISQUS segment where you can enter comments about the article, such as possible improvements or corrections or where you can simply state your opinion about what you read. Because DISQUS supports threaded comments, you can also reply to previously posted comments.<br />
<br />
You can also vote whether you ''like'' the article, using the familiar Facebook interface.<br />
<br />
The SEBoK editors will monitor all of your comments and suggestions to use when planning periodic updates to the SEBoK.<br />
<br />
{{DISQUS}}</div>Dhenryhttps://sebokwiki.org/w/index.php?title=Principles_of_Systems_Thinking&diff=48490Principles of Systems Thinking2013-06-11T20:53:02Z<p>Dhenry: /* Summary of Systems Principles */</p>
<hr />
<div>This topic forms part of the [[Systems Thinking]] knowledge area (KA). It identifies systems [[Principle (glossary)|principles]] as part of the basic ideas of [[Systems Thinking (glossary)|systems thinking]]. <br />
<br />
Some additional [[Concept (glossary) | concepts]] more directly associated with [[Engineered System (glossary)|engineered systems]] are described, and a summary of system [[Principle (glossary)|principles]] associated with the concepts already defined is provided. A number of additional “laws” and [[Heuristic (glossary) | heuristics]] are also discussed. <br />
<br />
==Systems Principles, Laws, and Heuristics==<br />
A principle is a general rule of conduct or behavior (Lawson and Martin 2008). It can also be defined as a basic generalization that is accepted as true and that can be used as a basis for reasoning or conduct (WordWeb 2012c). Thus, systems principles can be used as a basis for reasoning about [[System (glossary) | systems]] thinking or associated conduct ([[Systems Approach (glossary)|systems approaches]]).<br />
<br />
==Separation of Concerns==<br />
<br />
A systems approach is focused on a [[System-of-Interest (glossary)| systems-of-interest]] (SoI) of an [[Open System (glossary)|open system]]. This SoI consists of open, interacting subsystems that as a whole interact with and adapt to other systems in an [[Environment (glossary) | environment]]. The systems approach also considers the SoI in its environment to be part of a larger, wider, or containing system (Hitchins 2009). <br />
<br />
In the [[What is Systems Thinking?]] topic, a “systems thinking paradox” is discussed. How is it possible to take a holistic system view while still being able to focus on changing or creating systems? <br />
<br />
Separation of concerns describes a balance between considering parts of a system [[Problem (glossary)|problem]] or [[Solution (glossary)|solution]] while not losing sight of the whole (Greer 2008). [[Abstraction (glossary)|Abstraction]] is the process of taking away characteristics from something in order to reduce it to a set of base characteristics (SearchCIO 2012). In attempting to understand [[Complex (glossary)|complex]] situations it is easier to focus on [[Boundary (glossary) | bounded]] problems, whose [[Solution (glossary)|solutions]] still remain agnostic to the greater problem (Erl 2012). This process sounds [[Reductionism (glossary)|reductionist]], but it can be applied effectively to systems. The key to the success of this approach is ensuring that one of the selected problems is the concerns of the system as a whole. Finding balance between using abstraction to focus on specific concerns while ensuring we continue to consider the whole is at the center of [[Systems Approach (glossary)|systems approaches]].<br />
<br />
A [[View (glossary)|view]] is a subset of information observed of one or more entities, such as systems. The physical or conceptual point from which a view is observed is the [[Viewpoint (glossary)|viewpoint]], which can be motivated by one or more observer concerns. Different views of the same target must be both separate, to reflect separation of concerns, and integrated such that all views of a given target are consistent and form a coherent whole (Hybertson 2009). Some sample views of a system are internal (What does it consist of?); external (What are its properties and [[Behavior (glossary)|behavior]] as a whole?); static (What are its parts or structures?); and dynamic (interactions).<br />
<br />
[[Encapsulation (glossary)]], which encloses [[System Element (glossary)|system elements]] and their interactions from the external environment, is discussed in [[Concepts of Systems Thinking]]. Encapsulation is associated with [[Modularity (glossary)|modularity]], the degree to which a system's [[Component (glossary)|components]] may be separated and recombined (Griswold 1995). Modularity applies to systems in natural, social, and engineered domains. In [[Engineering (glossary)|engineering]], encapsulation is the isolation of a system [[Function (glossary)|function]] within a module and provides precise specifications for the module (IEEE Std. 610.12-1990).<br />
<br />
[[Dualism (glossary)|Dualism]] is a characteristic of systems in which they exhibit seemingly contradictory characteristics that are important for the system (Hybertson 2009). The yin yang concept in Chinese philosophy emphasizes the interaction between dual [[Element (glossary) | elements]] and their harmonization, ensuring a constant dynamic balance through a cyclic dominance of one element and then the other, such as day and night (IEP 2006). <br />
<br />
From a systems perspective the interaction, harmonization, and balance between system properties is important. Hybertson (2009) defines '''leverage''' as the duality between <br />
*'''Power''', the extent to which a system solves a specific problem, and <br />
*'''Generality''', the extent to which a system solves a whole class of problems. <br />
<br />
While some systems or elements may be optimized for one extreme of such dualities, a dynamic balance is needed to be effective in solving complex problems.<br />
<br />
===Summary of Systems Principles===<br />
A set of systems principles is given in Table 1 below. The "Names" segment points to concepts underlying the principle. (See [[Concepts of Systems Thinking]]). Following the table, two additional sets of items related to systems principles are noted and briefly discussed: prerequisite laws for [[Design (glossary)|design science]], and [[Heuristic (glossary)|heuristics]] and pragmatic principles.<br />
<br />
<center>'''Table 1. A Set of Systems Principles.''' (SEBoK Original)</center><br />
{| align="center"<br />
! Name <br />
! Statement of Principle<br />
|-<br />
|[[Abstraction (glossary)|Abstraction]]<br />
|A focus on essential characteristics is important in problem solving because it allows problem solvers to ignore the nonessential, thus simplifying the problem. (Sci-Tech Encyclopedia 2009; SearchCIO 2012; Pearce 2012)<br />
|-<br />
|[[Boundary (glossary)|Boundary]]<br />
|A boundary or membrane separates the system from the external world. It serves to concentrate interactions inside the system while allowing exchange with external systems. (Hoagland, Dodson, and Mauck 2001)<br />
|-<br />
|'''Change'''<br />
|Change is necessary for growth and adaptation, and should be accepted and planned for as part of the natural order of things rather than something to be ignored, avoided, or prohibited (Bertalanffy 1968; Hybertson 2009).<br />
|-<br />
|[[Dualism (glossary)|Dualism]]<br />
| Recognize dualities and consider how they are, or can be, harmonized in the [[Context (glossary) | context]] of a larger whole (Hybertson 2009)<br />
|-<br />
|'''Encapsulation'''<br />
|Hide internal parts and their interactions from the external environment. (Klerer 1993; IEEE 1990)<br />
|-<br />
|'''Equifinality'''<br />
|In open systems, the same final state may be reached from different initial conditions and in different ways (Bertalanffy 1968). This principle can be exploited, especially in systems of purposeful agents.<br />
|-<br />
|[[Holism (glossary)|Holism]]<br />
|A system should be considered as a single entity, a whole, not just as a set of parts. (Ackoff 1979; Klir 2001)<br />
|-<br />
|'''Interaction'''<br />
|The properties, [[Capability (glossary)|capabilities]], and behavior of a system are derived from its parts, from interactions between those parts, and from interactions with other systems. (Hitchins 2009 p. 60)<br />
|-<br />
|'''Layer Hierarchy'''<br />
|The evolution of complex systems is facilitated by their hierarchical structure (including stable intermediate forms) and the understanding of complex systems is facilitated by their hierarchical description. (Pattee 1973; Bertalanffy 1968; Simon 1996)<br />
|-<br />
|[[Leverage (glossary)|Leverage]]<br />
|Achieve maximum leverage (Hybertson 2009). Because of the power versus generality tradeoff, leverage can be achieved by a complete solution (power) for a narrow class of problems, or by a partial solution for a broad class of problems (generality).<br />
|-<br />
|[[Modularity (glossary)|Modularity]]<br />
|Unrelated parts of the system should be separated, and related parts of the system should be grouped together. (Griswold 1995; Wikipedia 2012a)<br />
|-<br />
|[[Network (glossary)|Network]]<br />
|The network is a fundamental topology for systems that forms the basis of togetherness, connection, and dynamic interaction of parts that yield the behavior of complex systems (Lawson 2010; Martin et al. 2004; Sillitto 2010)<br />
|-<br />
|'''Parsimony'''<br />
|One should choose the simplest explanation of a phenomenon, the one that requires the fewest assumptions (Cybernetics 2012). This applies not only to choosing a design, but also to operations and [[Requirement (glossary) | requirements]].<br />
|-<br />
|[[Regularity (glossary)|Regularity]]<br />
|[[Systems Science (glossary)|Systems science]] should find and capture regularities in systems, because those regularities promote systems understanding and facilitate systems practice. (Bertalanffy 1968)<br />
|-<br />
|'''Relations'''<br />
|A system is characterized by its relations: the interconnections between the elements. Feedback is a type of relation. The set of relations defines the [[Network (glossary)|network]] of the system. (Odum 1994)<br />
|-<br />
|'''Separation of Concerns'''<br />
|A larger problem is more effectively solved when decomposed into a set of smaller problems or concerns. (Erl 2012; Greer 2008)<br />
|-<br />
|'''Similarity/ Difference'''<br />
|Both the similarities and differences in systems should be recognized and accepted for what they are. (Bertalanffy 1975 p. 75; Hybertson 2009). Avoid forcing one size fits all, and avoid treating everything as entirely unique.<br />
|-<br />
|'''Stability/ Change'''<br />
|Things change at different rates, and entities or concepts at the stable end of the spectrum can and should be used to provide a guiding context for rapidly changing entities at the volatile end of the spectrum (Hybertson 2009). The study of complex adaptive systems can give guidance to system behavior and design in changing environments (Holland 1992).<br />
|-<br />
|[[Synthesis (glossary)|Synthesis]]<br />
|Systems can be created by choosing (conceiving, designing, selecting) the right parts, bringing them together to interact in the right way, and in orchestrating those interactions to create requisite properties of the whole, such that it performs with optimum effectiveness in its operational [[Environment (glossary)|environment]], so solving the problem that prompted its creation” (Hitchins 2008: 120).<br />
|-<br />
|[[View (glossary)|View]]<br />
|Multiple views, each based on a system aspect or concern, are essential to understand a complex system or problem situation. One critical view is how concern relates to properties of the whole. (Edson 2008; Hybertson 2009)<br />
|}<br />
<br />
The principles are not independent. They have synergies and tradeoffs. Lipson (2007), for example, argued that “[[Scalability (glossary)|scalability]] of open-ended evolutionary processes depends on their ability to exploit functional modularity, structural regularity and hierarchy.” He proposed a formal [[Model (glossary)|model]] for examining the properties, dependencies, and tradeoffs among these principles. Edson (2008) related many of the above principles in a structure called the conceptagon, which he modified from the work of Boardman and Sauser (2008). Edson also provided guidance on how to apply these principles. Not all principles apply to every system or engineering decision. Judgment, experience, and heuristics (see below) provide understanding into which principles apply in a given situation.<br />
<br />
Several principles illustrate the relation of view with the dualism and yin yang principle; for example, holism and separation of concerns. These principles appear to be contradictory but are in fact dual ways of dealing with [[Complexity (glossary)|complexity]]. Holism deals with complexity by focusing on the whole system, while separation of concerns divides a problem or system into smaller, more manageable elements that focus on particular concerns. They are reconciled by the fact that both views are needed to understand systems and to engineer systems; focusing on only one or the other does not give sufficient understanding or a good overall solution. This dualism is closely related to the systems thinking paradox described in [[What is Systems Thinking?]]. <br />
<br />
Rosen (1979) discussed “false dualisms” of systems paradigms that are considered incompatible but are in fact different aspects or views of reality. In the present context, they are thus reconcilable through yin yang harmonization. Edson (2008) emphasized viewpoints as an essential principle of systems thinking; specifically, as a way to understand opposing concepts.<br />
<br />
Derick Hitchins (2003) produced a systems life cycle theory described by a set of seven principles forming an integrated set. This theory describes the creation, manipulation and demise of engineered systems. These principles consider the factors which contribute to the stability and survival of man made systems in an environment. Stability is associated with the principle of '''connected variety''', in which stability is increased by variety plus the '''cohesion''' and '''adaptability''' of that variety. Stability is limited by allowable relations, resistance to change, and patterns of interaction. Hitchins describes how interconnected systems tend toward a '''cyclic progression''', in which variety is generated, dominance emerges to suppress variety, dominant modes decay and collapse and survivors emerge to generate new variety.<br />
<br />
Guidance on how to apply many of these principles to engineered systems is given in the topic [[Synthesizing Possible Solutions]], as well as in [[System Definition]] and other knowledge areas in Part 3 of the SEBoK.<br />
<br />
===Prerequisite Laws of Design Science===<br />
John Warfield (1994) identified a set of laws of generic design science that are related to systems principles. Three of these laws are stated here:<br />
<br />
#‘’Law of Requisite Variety’’: A design situation embodies a variety that must be matched by the specifications. The variety includes the diversity of [[Stakeholder (glossary)|stakeholders]]. This law is an application of the design science of the Ashby (1956) Law of Requisite Variety, which was defined in the context of [[Cybernetics (glossary)|cybernetics]] and states that to successfully regulate a system, the variety of the regulator must be at least as large as the variety of the regulated system.<br />
#‘’Law of Requisite Parsimony’’: Information must be organized and presented in a way that prevents human information overload. This law derives from Miller’s findings on the limits of human information processing capacity (Miller 1956). Warfield’s structured dialog method is one possible way to help achieve the requisite parsimony.<br />
#‘’Law of Gradation’’: Any conceptual body of knowledge can be graded in stages or varying degrees of complexity and scale, ranging from simplest to most comprehensive, and the degree of knowledge applied to any design situation should match the complexity and scale of the situation. A corollary, called the Law of Diminishing Returns, states that a body of knowledge should be applied to a design situation to the stage at which the point of diminishing returns is reached.<br />
<br />
===Heuristics and Pragmatic Principles===<br />
A heuristic is a common sense rule intended to increase the probability of solving some problem (WordWeb 2012b). In the present context it may be regarded as an informal or pragmatic principle. Maier and Rechtin (2000) identified an extensive set of heuristics that are related to systems principles. A few of these heuristics are stated here.<br />
<br />
*Relationships among the elements are what give systems their added value. This is related to the ‘’Interaction’’ principle.<br />
*Efficiency is inversely proportional to universality. This is related to the ‘’Leverage’’ principle.<br />
*The first line of defense against complexity is simplicity of design. This is related to the ‘’Parsimony’’ principle.<br />
*In order to understand anything, you must not try to understand everything (attributed to Aristotle). This is related to the ‘’Abstraction’’ principle.<br />
An International Council on Systems Engineering (INCOSE) working group (INCOSE 1993) defined a set of “pragmatic principles” for systems engineering (SE). They are essentially best practice heuristics for engineering a system. For example:<br />
<br />
*Know the problem, the customer, and the consumer <br />
*Identify and assess alternatives so as to converge on a solution <br />
*Maintain the integrity of the system<br />
<br />
Hitchins defines a set of SE principles which include principles of holism and synthesis as discussed above, as well as principles describing how systems problems should be resolved that are of particular relevance to a [[Systems Approach Applied to Engineered Systems]] (Hitchins 2009).<br />
<br />
==References==<br />
===Works Cited===<br />
Ackoff, R. 1979. "The Future of Operational Research is Past." ''Journal of the Operational Research Society.'' 30(2): 93–104, Pergamon Press.<br />
<br />
Ashby, W.R. 1956. "Requisite variety and its implications for the control of complex systems." ''Cybernetica.'' 1(2):1–17.<br />
<br />
Bertalanffy, L. von. 1968. ''[[General System Theory: Foundations, Development, Applications]]''. Revised ed. New York, NY: Braziller.<br />
<br />
Bertalanffy, L. von. 1975. ''Perspectives on General System Theory''. E. Taschdjian, ed. New York: George Braziller.<br />
<br />
Boardman, J. and B. Sauser. 2008. ''Systems Thinking: Coping with 21st Century Problems''. Boca Raton, FL: Taylor & Francis.<br />
<br />
Cybernetics (Web Dictionary of Cybernetics and Systems). 2012. "Principle of Parsimony or Principle of Simplicity." http://pespmc1.vub.ac.be/ASC/PRINCI_SIMPL.html <br />
<br />
Edson, R. 2008. ''Systems Thinking. Applied. A Primer''. Arlington, VA, USA: Applied Systems Thinking (ASysT) Institute, Analytic Services Inc.<br />
<br />
Erl, T. 2012. "SOA Principles: An Introduction to the Service Orientation Paradigm." http://www.soaprinciples.com/p3.php <br />
<br />
Greer, D. 2008. "The Art of Separation of Concerns." http://aspiringcraftsman.com/tag/separation-of-concerns/ <br />
<br />
Griswold, W. 1995. "Modularity Principle." http://cseweb.ucsd.edu/users/wgg/CSE131B/Design/node1.html<br />
<br />
Hitchins D. K. 2003. ''Advanced systems thinking engineering and management.'' Boston, MA, USA: Artech House.<br />
<br />
Hitchins, D. 2009. "What are the General Principles Applicable to Systems?" INCOSE ''Insight''. 12(4): 59-63. <br />
<br />
Hoagland, M., B. Dodson, and J. Mauck. 2001. ''Exploring the Way Life Works''. Burlington, MA, USA: Jones and Bartlett Publishers, Inc.<br />
<br />
Holland, J. 1992. ''Adaptation in Natural and Artificial Systems: An Introductory Analysis with Applications to Biology, Control, and Artificial Intelligence''. Cambridge, MA: MIT Press.<br />
<br />
Hybertson, D. 2009. ''[[Model-Oriented Systems Engineering Science]]: A Unifying Framework for Traditional and Complex Systems''. Boca Raton, FL, USA: Auerbach/CRC Press.<br />
<br />
IEEE. 1990. ''IEEE Standard Glossary of Software Engineering Terminology''. Geneva, Switzerland: Institute of Electrical and Electronics Engineers. IEEE Std 610.12-1990.<br />
<br />
IEP (Internet Encyclopedia of Philosophy). 2006. "Yinyang (Yin-yang)." http://www.iep.utm.edu/yinyang/<br />
<br />
INCOSE 1993. ''An Identification of Pragmatic Principles - Final Report''. SE Principles Working Group, January 21, 1993. http://www.incose.org/productspubs/pdf/techdata/pitc/principlespragmaticdefoe_1993-0123_prinwg.pdf<br />
<br />
Klerer, S. “System Management Information Modeling.” ''IEEE Communications''. 31(5)May 1993: 38-44.<br />
<br />
Klir, G. 2001. ''[[Facets of Systems Science]]'', 2nd ed. New York, NY: Kluwer Academic/Plenum Publishers. <br />
<br />
Lawson, H. 2010. ''A Journey Through the Systems Landscape''. London, UK: College Publications, Kings College, UK.<br />
<br />
Lawson, H. and J. Martin. 2008. "On the Use of Concepts and Principles for Improving Systems Engineering Practice." INCOSE International Symposium 2008, 15-19 June 2008, The Netherlands.<br />
<br />
Lipson, H. 2007. "Principles of modularity, regularity, and hierarchy for scalable systems." ''Journal of Biological Physics and Chemistry.'' 7: 125–128.<br />
<br />
Maier, M. and E. Rechtin. 2000. ''The Art of Systems Architecting, 2nd ed''. Boca Raton, FL: CRC Press.<br />
<br />
Martin, R., E. Robertson, and J. Springer. 2004. ''Architectural Principles for Enterprise Frameworks''. Technical Report No. 594, Indiana University, April 2004. http://www.cs.indiana.edu/cgi-bin/techreports/TRNNN.cgi?trnum=TR594.<br />
<br />
Miller, G. 1956. "The magical number seven, plus or minus two: some limits on our capacity for processing information." ''The Psychological Review.'' 63: 81–97.<br />
<br />
Odum, H. 1994. ''Ecological and General Systems: An Introduction to Systems Ecology (Revised Edition).'' Boulder, CO: University Press of Colorado.<br />
<br />
Pattee, H. (ed.) 1973. ''Hierarchy Theory: The Challenge of Complex Systems''. New York, NY: George Braziller.<br />
<br />
Pearce, J. 2012. "The Abstraction Principle." Posting date unknown; accessed June 2012. http://www.cs.sjsu.edu/~pearce/modules/lectures/ood/principles/Abstraction.htm<br />
<br />
Rosen, R. 1979. "Old trends and new trends in general systems research." ''International Journal of General Systems.'' 5(3): 173-184.<br />
<br />
Sci-Tech Encyclopedia. 2009. "Abstract Data Type." ''McGraw-Hill Concise Encyclopedia of Science and Technology, Sixth Edition'', The McGraw-Hill Companies, Inc. http://www.answers.com/topic/abstract-data-type. <br />
<br />
SearchCIO. 2012. "Abstraction." http://searchcio-midmarket.techtarget.com/definition/abstraction<br />
<br />
Sillitto, H. 2010. "Design principles for Ultra-Large-Scale (ULS) Systems." 'Proceedings of INCOSE International Symposium 2010', 12-15 July 2010, Chicago, IL.<br />
<br />
Simon, H. 1996. ''The Sciences of the Artificial, 3rd ed''. Cambridge, MA: MIT Press.<br />
<br />
Volk, T., and J.W. Bloom. (2007). "The use of metapatterns for research into complex systems of teaching, learning, and schooling. Part I: Metapatterns in nature and culture." ''Complicity: An International Journal of Complexity and Education.'' 4(1): 25—43 (http://www.complexityandeducation.ualberta.ca/COMPLICITY4/documents/Complicity_41d_Volk_Bloom.pdf).<br />
<br />
Warfield, J.N. 1994. ''A Science of Generic Design''. Ames, IA: Iowa State University Press.<br />
<br />
Wikipedia. 2012a. "Modularity." http://en.wikipedia.org/wiki/Modularity <br />
<br />
WordWeb. 2012b. "Dualism." http://www.wordwebonline.com/en/DUALISM.<br />
<br />
WordWeb. 2012c. "Heuristic." http://www.wordwebonline.com/en/HEURISTIC. <br />
<br />
WordWeb. 2012d. "Principle." http://www.wordwebonline.com/en/PRINCIPLE.<br />
<br />
===Primary References===<br />
Bertalanffy, L. von. 1968. ''[[General System Theory: Foundations, Development, Applications]]''. Revised ed. New York, NY: Braziller.<br />
<br />
Hybertson, D. 2009. ''[[Model-Oriented Systems Engineering Science]]: A Unifying Framework for Traditional and Complex Systems''. Auerbach/CRC Press, Boca Raton, FL.<br />
<br />
Klir, G. 2001. ''[[Facets of Systems Science]], 2nd ed.'' New York: Kluwer Academic/Plenum Publishers.<br />
<br />
===Additional References===<br />
Francois, F. (ed.). 2004. ''International Encyclopedia of Systems and Cybernetics,'' 2nd ed. Munich, Germany: K. G. Saur Verlag.<br />
<br />
Meyers, R. (ed.). 2009. ''Encyclopedia of Complexity and Systems Science.'' New York, NY: Springer.<br />
<br />
Midgley, G. (ed.). 2003. ''Systems Thinking.'' Thousand Oaks, CA: Sage Publications Ltd.<br />
<br />
----<br />
<center> [[Concepts of Systems Thinking|< Previous Article]] | [[Systems Thinking|Parent Article]] | [[Patterns of Systems Thinking|Next Article >]] </center><br />
<br />
[[Category:Part 2]][[Category:Topic]][[Category:Systems Thinking]]<br />
{{DISQUS}}</div>Dhenry