Difference between revisions of "Governance and Editorial Boards"
(36 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
==BKCASE Governing Board== | ==BKCASE Governing Board== | ||
− | |||
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) provide the funding and resources needed to sustain and evolve the SEBoK and make it available as a free and open resource to all. The stewards appoint the BKCASE Governing Board to be their primary agents to oversee and guide the SEBoK and its companion BKCASE product, GRCSE. | 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) provide the funding and resources needed to sustain and evolve the SEBoK and make it available as a free and open resource to all. The stewards appoint the BKCASE Governing Board to be their primary agents to oversee and guide the SEBoK and its companion BKCASE product, GRCSE. | ||
The BKCASE Governing Board includes: | The BKCASE Governing Board includes: | ||
− | *'''INCOSE''' | + | *'''INCOSE''' |
− | ** | + | **Paul Frenz, William Miller (Governing Board Chair) |
*'''IEEE Computer Society''' | *'''IEEE Computer Society''' | ||
− | ** | + | **Andy Chen, John Keppler |
*'''SERC''' | *'''SERC''' | ||
− | ** | + | **Art Pyster, Cihan Dagli |
− | The governors would also like to acknowledge John Keppler, IEEE Computer Society, who has been instrumental in helping the Governors to work within the IEEE CS structure. | + | Past INCOSE governors Kevin Forsberg, David Newbern, David Walden, Courtney Wright, Dave Olwell, Ken Nidiffer, Richard Fairley and Massood Towhidnejad. The governors would also like to acknowledge John Keppler, IEEE Computer Society, who has been instrumental in helping the Governors to work within the IEEE CS structure. |
The stewards appoint the BKCASE Editor in Chief to manage the SEBoK and GRCSE and oversee the Editorial Board. | The stewards appoint the BKCASE Editor in Chief to manage the SEBoK and GRCSE and oversee the Editorial Board. | ||
Line 19: | Line 18: | ||
The SEBoK Editorial Board is chaired by an Editor in Chief, supported by a group of Associate Editors. | The SEBoK Editorial Board is chaired by an Editor in Chief, supported by a group of Associate Editors. | ||
− | {|style="width:100%" | + | {| style="width:100%" |
− | !colspan="2"|BKCASE Editor in Chief | + | ! colspan="2" |BKCASE Editor in Chief |
|- | |- | ||
− | |style="background-color: #ffffff"| | + | | style="background-color: #ffffff" | |
[[File:RickAdcock.png|center|150px]] | [[File:RickAdcock.png|center|150px]] | ||
− | |style="background-color: #ffffff"| | + | | style="background-color: #ffffff" | |
'''Richard D. Adcock''' | '''Richard D. Adcock''' | ||
Line 31: | Line 30: | ||
[mailto:richard.adcock@incose.org richard.adcock@incose.org] | [mailto:richard.adcock@incose.org richard.adcock@incose.org] | ||
− | + | Responsible for the appointment of SEBoK Editors and for the overall content and coherence of the SEBoK. | |
|} | |} | ||
+ | Each Editor has his/her area(s) of responsibility, or shared responsibility, highlighted in the table below. | ||
− | + | {| style="width:100%" | |
− | + | ! colspan="1" |SEBoK Part 1 SEBoK Introduction | |
− | {|style="width:100%" | ||
− | !colspan="1"|SEBoK Part 1 SEBoK Introduction | ||
|- | |- | ||
|'''Ariela Sofer''' | |'''Ariela Sofer''' | ||
Line 46: | Line 44: | ||
[mailto:asofer@gmu.edu asofer@gmu.edu] | [mailto:asofer@gmu.edu asofer@gmu.edu] | ||
− | Responsible for | + | Responsible for Part 1 |
|} | |} | ||
− | + | {| style="width:100%" | |
− | {|style="width:100%" | + | ! colspan="2" |SEBoK Part 2: Systems |
− | !colspan="2"|SEBoK Part 2: Systems | ||
|- | |- | ||
− | |'''Cihan Dagli''' | + | | width="50%" |'''Cihan Dagli''' |
''Missouri University of Science & Technology (USA)'' | ''Missouri University of Science & Technology (USA)'' | ||
Line 59: | Line 56: | ||
[mailto:dagli@mst.edu dagli@mst.edu] | [mailto:dagli@mst.edu dagli@mst.edu] | ||
− | Responsible for the | + | Responsible for the [[Systems Approach Applied to Engineered Systems]] knowledge areas |
− | |'''Dov Dori''' | + | |
+ | | width="50%" |'''Dov Dori''' | ||
''Massachusetts Institute of Technology (USA) and Technion Israel Institute of Technology (Israel)'' | ''Massachusetts Institute of Technology (USA) and Technion Israel Institute of Technology (Israel)'' | ||
[mailto:dori@mit.edu dori@mit.edu] | [mailto:dori@mit.edu dori@mit.edu] | ||
− | Responsible for the [[Representing Systems with Models]] knowledge area | + | |
+ | Responsible for the [[Representing Systems with Models]] knowledge area | ||
|- | |- | ||
|'''Duane Hybertson''' | |'''Duane Hybertson''' | ||
− | '' | + | ''MITRE (USA)'' |
− | + | Jointly responsible for the [[Systems Fundamentals]], [[Systems Science]] and [[Systems Thinking]] knowledge areas | |
− | '' | + | |'''Janet Singer''' (USA) |
− | [ | + | Jointly responsible for the [[Systems Fundamentals]], [[Systems Science]] and [[Systems Thinking]] knowledge areas |
+ | |- | ||
+ | | colspan="2" |'''Mike Yearworth''' | ||
− | + | ''University of Bristol (UK)'' | |
− | |||
− | |||
− | + | Jointly responsible for the [[Systems Fundamentals]], [[Systems Science]] and [[Systems Thinking]] knowledge areas | |
− | |||
|} | |} | ||
− | + | {| style="width:100%" | |
− | {|style="width:100%" | + | ! colspan="2" |SEBoK Part 3: Systems Engineering and Management |
− | !colspan="2"|SEBoK Part | ||
|- | |- | ||
− | |'''Barry Boehm''' | + | | width="50%" |'''Barry Boehm''' |
''University of Southern California (USA)'' | ''University of Southern California (USA)'' | ||
Line 95: | Line 92: | ||
[mailto:boehm@usc.edu boehm@usc.edu] | [mailto:boehm@usc.edu boehm@usc.edu] | ||
− | + | Jointly responsible for the [[Systems Engineering Management]] and [[Life Cycle Models]] knowledge areas | |
− | |''' | + | |
+ | | width="50%" |'''Kevin Forsberg''' | ||
− | '' | + | ''OGR Systems'' |
− | [ | + | Jointly responsible for the [[Systems Engineering Management]] and [[Life Cycle Models]] knowledge areas |
− | |||
|- | |- | ||
− | |||
− | |||
− | |||
|'''Gregory Parnell''' | |'''Gregory Parnell''' | ||
Line 113: | Line 107: | ||
[mailto:gparnell@uark.edu gparnell@uark.edu ] | [mailto:gparnell@uark.edu gparnell@uark.edu ] | ||
− | Responsible for | + | Responsible for [[Systems Engineering Management]] knowledge area. |
+ | |||
+ | |'''Garry Roedler''' | ||
+ | |||
+ | ''Lockheed Martin (USA)'' | ||
+ | |||
+ | [mailto:garry.j.roedler@lmco.com garry.j.roedler@lmco.com] | ||
+ | |||
+ | Responsible for the [[Concept Definition]] and [[System Definition]] knowledge areas. | ||
|- | |- | ||
Line 122: | Line 124: | ||
[mailto:rvalerdi@email.arizona.edu rvalerdi@email.arizona.edu] | [mailto:rvalerdi@email.arizona.edu rvalerdi@email.arizona.edu] | ||
− | Responsible for the [[System Realization]] knowledge area | + | Responsible for the [[System Realization]] knowledge area. |
|'''Ken Zemrowski''' | |'''Ken Zemrowski''' | ||
Line 133: | Line 135: | ||
|} | |} | ||
− | + | {| style="width:100%" | |
− | + | ! colspan="2" |SEBoK Part 4: Applications of Systems Engineering | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | {|style="width:100%" | ||
− | !colspan="2"|SEBoK Part | ||
|- | |- | ||
− | |''' | + | | width="50%" |'''Judith Dahmann''' |
− | '' | + | ''MITRE Corporation (USA)'' |
− | [mailto: | + | [mailto:jdahmann@mitre.org jdahmann@mitre.org] |
− | + | Jointly responsible for [[Product Systems Engineering]] and [[Systems of Systems (SoS)]] knowledge areas | |
− | |||
− | '' | + | |'''Michael Henshaw''' |
− | '' | + | ''Loughborough University (UK)'' |
− | |||
− | |||
− | + | [mailto:M.J.d.Henshaw@lboro.ac.uk M.J.d.Henshaw@lboro.ac.uk] | |
− | |||
− | [mailto: | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | [ | + | Jointly responsible for [[Product Systems Engineering]] and [[Systems of Systems (SoS)]] knowledge areas |
− | |||
|- | |- | ||
− | |''' | + | | colspan="2" |'''James Martin''' |
+ | ''The Aerospace Corporation'' | ||
− | + | [mailto:james.martin@incose.org james.martin@incose.org] | |
− | + | Responsible for the [[Enterprise Systems Engineering]] knowledge area. | |
− | + | |} | |
− | Responsible for | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
+ | {| style="width:100%" | ||
+ | ! colspan="2" |SEBoK Part 5: Enabling Systems Engineering | ||
|- | |- | ||
− | | | + | | width="50%" |'''Emma Sparks''' |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |''' | ||
− | '' | + | ''Cranfield University'' |
− | [ | + | Jointly responsible for the [[Enabling Individuals]]<nowiki/>and[[Enabling Teams]] knowledge area |
− | + | | width="50%" |'''Rick Hefner''' | |
+ | ''California Institute of Technology'' | ||
|- | |- | ||
− | |''' | + | | width="50%" | '''Tim Ferris''' |
+ | ''Cranfield University'' | ||
− | '' | + | |width="50%" | '''Bernardo Delicado''' |
− | + | ''MBDA / INCOSE'' | |
− | + | |} | |
− | | | ||
− | |||
− | |||
− | |||
− | |||
− | + | {| style="width:100%" | |
+ | ! colspan="2" |SEBoK Part 6 Related Disciplines | ||
|- | |- | ||
− | | | + | | width="50%" |'''Alice Squires''' |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |'''Alice Squires''' | ||
''Washington State University (USA)'' | ''Washington State University (USA)'' | ||
− | [mailto:alice.squires@wsu.edu | + | [mailto:alice.squires@wsu.edu alice.squires@wsu.edu] |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | | width="50%" |'''Paul Phister''' | |
− | + | ''MANIAC Consulting'' | |
− | |||
− | + | [mailto:phisterp@juno.com phisterp@juno.com] | |
− | + | |} | |
− | [mailto: | ||
− | + | {| style="width:100%" | |
+ | ! colspan="2" |SEBoK Part 7 Systems Engineering Implementation Examples | ||
|- | |- | ||
− | |''' | + | | width="50%" |'''Brian Sauser''' |
− | '' | + | ''University of North Texas (USA)'' |
− | [mailto: | + | [mailto:brian.sauser@unt.edu brian.sauser@unt.edu] |
− | + | Responsible for [[Systems Engineering Implementation Examples|Part 7: Systems Engineering Implementation Examples]], which includes [[Case Studies]] and [[Vignettes]] | |
− | |'''Brian White''' | + | | width="50%" |'''Brian White''' |
''CAU>SE (USA)'' | ''CAU>SE (USA)'' | ||
Line 263: | Line 218: | ||
[mailto:bewhite71@gmail.com bewhite71@gmail.com] | [mailto:bewhite71@gmail.com bewhite71@gmail.com] | ||
− | Responsible for [[Systems Engineering Implementation Examples|Part 7: Systems Engineering Implementation Examples]], which includes [[Case Studies]] and [[Vignettes]] | + | Responsible for [[Systems Engineering Implementation Examples|Part 7: Systems Engineering Implementation Examples]], which includes [[Case Studies]] and [[Vignettes]] |
+ | |||
+ | |} | ||
+ | |||
+ | {| style="width:100%" | ||
+ | ! colspan="1" |''Graduate Reference Curriculum for Systems Engineering (GRCSE)'' | ||
|- | |- | ||
|''' David H. Olwell ''' | |''' David H. Olwell ''' | ||
Line 269: | Line 229: | ||
''Naval Postgraduate School (USA)'' | ''Naval Postgraduate School (USA)'' | ||
− | + | Senior Editor for GRCSE''.'' | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
Line 290: | Line 236: | ||
The Assistant Editor provide general editorial support across all topics and assist with both content improvement and production issues. | The Assistant Editor provide general editorial support across all topics and assist with both content improvement and production issues. | ||
− | {| | + | {| style="width:200px" |
!BKCASE Assistant Editor | !BKCASE Assistant Editor | ||
|- | |- | ||
Line 298: | Line 244: | ||
[mailto:c.nielsen@cranfield.ac.uk c.nielsen@cranfield.ac.uk] | [mailto:c.nielsen@cranfield.ac.uk c.nielsen@cranfield.ac.uk] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
Line 320: | Line 253: | ||
*[[Enabling Businesses and Enterprises]] | *[[Enabling Businesses and Enterprises]] | ||
*[[Systems Engineering and Software Engineering]] | *[[Systems Engineering and Software Engineering]] | ||
− | *[[ | + | *[[Procurement and Acquisition]] |
*[[Systems Engineering and Specialty Engineering]] | *[[Systems Engineering and Specialty Engineering]] | ||
Revision as of 11:12, 25 March 2016
BKCASE Governing Board
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) provide the funding and resources needed to sustain and evolve the SEBoK and make it available as a free and open resource to all. The stewards appoint the BKCASE Governing Board to be their primary agents to oversee and guide the SEBoK and its companion BKCASE product, GRCSE.
The BKCASE Governing Board includes:
- INCOSE
- Paul Frenz, William Miller (Governing Board Chair)
- IEEE Computer Society
- Andy Chen, John Keppler
- SERC
- Art Pyster, Cihan Dagli
Past INCOSE governors Kevin Forsberg, David Newbern, David Walden, Courtney Wright, Dave Olwell, Ken Nidiffer, Richard Fairley and Massood Towhidnejad. The governors would also like to acknowledge John Keppler, IEEE Computer Society, who has been instrumental in helping the Governors to work within the IEEE CS structure.
The stewards appoint the BKCASE Editor in Chief to manage the SEBoK and GRCSE and oversee the Editorial Board.
Editorial Board
The SEBoK Editorial Board is chaired by an Editor in Chief, supported by a group of Associate Editors.
BKCASE Editor in Chief | |
---|---|
Richard D. Adcock Cranfield University (UK) Responsible for the appointment of SEBoK Editors and for the overall content and coherence of the SEBoK. |
Each Editor has his/her area(s) of responsibility, or shared responsibility, highlighted in the table below.
SEBoK Part 1 SEBoK Introduction |
---|
Ariela Sofer
George Mason University (USA) Responsible for Part 1 |
SEBoK Part 2: Systems | |
---|---|
Cihan Dagli
Missouri University of Science & Technology (USA) Responsible for the Systems Approach Applied to Engineered Systems knowledge areas |
Dov Dori
Massachusetts Institute of Technology (USA) and Technion Israel Institute of Technology (Israel) Responsible for the Representing Systems with Models knowledge area |
Duane Hybertson
MITRE (USA) Jointly responsible for the Systems Fundamentals, Systems Science and Systems Thinking knowledge areas |
Janet Singer (USA)
Jointly responsible for the Systems Fundamentals, Systems Science and Systems Thinking knowledge areas |
Mike Yearworth
University of Bristol (UK) Jointly responsible for the Systems Fundamentals, Systems Science and Systems Thinking knowledge areas |
SEBoK Part 3: Systems Engineering and Management | |
---|---|
Barry Boehm
University of Southern California (USA) Jointly responsible for the Systems Engineering Management and Life Cycle Models knowledge areas |
Kevin Forsberg
OGR Systems Jointly responsible for the Systems Engineering Management and Life Cycle Models knowledge areas |
Gregory Parnell
University of Arkansas (USA) Responsible for Systems Engineering Management knowledge area. |
Garry Roedler
Lockheed Martin (USA) Responsible for the Concept Definition and System Definition knowledge areas. |
Ricardo Valerdi
University of Arizona (USA) Responsible for the System Realization knowledge area. |
Ken Zemrowski
TASC Responsible for the Systems Engineering Standards knowledge area. |
SEBoK Part 4: Applications of Systems Engineering | |
---|---|
Judith Dahmann
MITRE Corporation (USA) Jointly responsible for Product Systems Engineering and Systems of Systems (SoS) knowledge areas |
Michael Henshaw
Loughborough University (UK) Jointly responsible for Product Systems Engineering and Systems of Systems (SoS) knowledge areas |
James Martin
The Aerospace Corporation Responsible for the Enterprise Systems Engineering knowledge area. |
SEBoK Part 5: Enabling Systems Engineering | |
---|---|
Emma Sparks
Cranfield University Jointly responsible for the Enabling IndividualsandEnabling Teams knowledge area |
Rick Hefner
California Institute of Technology |
Tim Ferris
Cranfield University |
Bernardo Delicado
MBDA / INCOSE |
SEBoK Part 6 Related Disciplines | |
---|---|
Alice Squires
Washington State University (USA) |
Paul Phister
MANIAC Consulting |
SEBoK Part 7 Systems Engineering Implementation Examples | |
---|---|
Brian Sauser
University of North Texas (USA) Responsible for Part 7: Systems Engineering Implementation Examples, which includes Case Studies and Vignettes |
Brian White
CAU>SE (USA) Responsible for Part 7: Systems Engineering Implementation Examples, which includes Case Studies and Vignettes |
Graduate Reference Curriculum for Systems Engineering (GRCSE) |
---|
David H. Olwell
Naval Postgraduate School (USA) Senior Editor for GRCSE. |
Editorial Board Support
The Assistant Editor provide general editorial support across all topics and assist with both content improvement and production issues.
BKCASE Assistant Editor |
---|
Claus Ballegaard Nielsen
Cranfield University (UK) |
Interested in Editing?
The Editor in Chief is looking for additional editors to support the evolution of the SEBoK. Editors are responsible for maintaining and updating one to two knowledge areas, including recruiting and working with authors, ensuring the incorporation of community feedback, and maintaining the quality of SEBoK content. We are specifically interested in support for the following knowledge areas:
- System Deployment and Use
- Product and Service Life Management
- Enabling Businesses and Enterprises
- Systems Engineering and Software Engineering
- Procurement and Acquisition
- Systems Engineering and Specialty Engineering
If you are interested in being considered for participation on the Editorial Board, please visit the BKCASE website http://www.bkcase.org/join-us/ or contact the BKCASE Staff directly at bkcase.incose.ieeecs@gmail.com.
SEBoK Discussion
Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.
If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.
blog comments powered by Disqus