Difference between revisions of "Governance and Editorial Boards"
| Line 31: | Line 31: | ||
[mailto:richard.adcock@incose.org richard.adcock@incose.org] | [mailto:richard.adcock@incose.org richard.adcock@incose.org] | ||
| − | SEBoK | + | Responsible for the appointment of SEBoK Editors and for the overall content and coherence of the SEBoK. |
|} | |} | ||
| Line 73: | Line 73: | ||
''MITRE (USA)'' | ''MITRE (USA)'' | ||
| − | + | Jointly responsible for the [[Systems Fundamentals]], [[Systems Science]] and [[Systems Thinking]] knowledge areas | |
|'''Janet Singer''' (USA) | |'''Janet Singer''' (USA) | ||
| − | + | Jointly responsible for the [[Systems Fundamentals]], [[Systems Science]] and [[Systems Thinking]] knowledge areas | |
|- | |- | ||
|colspan=2|'''Mike Yearworth''' | |colspan=2|'''Mike Yearworth''' | ||
| Line 83: | Line 83: | ||
''University of Bristol (UK)'' | ''University of Bristol (UK)'' | ||
| − | + | Jointly responsible for the [[Systems Fundamentals]], [[Systems Science]] and [[Systems Thinking]] knowledge areas | |
|} | |} | ||
| Line 97: | Line 97: | ||
[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''' | |width="50%"|'''Kevin Forsberg''' | ||
| Line 103: | Line 103: | ||
''OGR Systems'' | ''OGR Systems'' | ||
| − | + | Jointly responsible for the [[Systems Engineering Management]] and [[Life Cycle Models]] knowledge areas | |
|- | |- | ||
| Line 120: | Line 120: | ||
[mailto:garry.j.roedler@lmco.com garry.j.roedler@lmco.com] | [mailto:garry.j.roedler@lmco.com garry.j.roedler@lmco.com] | ||
| − | Responsible for the [[Concept Definition]] and [[System Definition]] knowledge areas | + | Responsible for the [[Concept Definition]] and [[System Definition]] knowledge areas. |
|- | |- | ||
| Line 129: | Line 129: | ||
[mailto:rvalerdi@email.arizona.edu rvalerdi@email.arizona.edu] | [mailto:rvalerdi@email.arizona.edu rvalerdi@email.arizona.edu] | ||
| − | Responsible for the [[System Realization]] knowledge. | + | Responsible for the [[System Realization]] knowledge area. |
|'''Ken Zemrowski''' | |'''Ken Zemrowski''' | ||
| Line 151: | Line 151: | ||
[mailto:jdahmann@mitre.org jdahmann@mitre.org] | [mailto:jdahmann@mitre.org jdahmann@mitre.org] | ||
| − | + | Jointly responsible for [[Product Systems Engineering]] and [[Systems of Systems (SoS)]] knowledge areas | |
|width="50%"|'''Michael Henshaw''' | |width="50%"|'''Michael Henshaw''' | ||
| Line 159: | Line 159: | ||
[mailto:M.J.d.Henshaw@lboro.ac.uk M.J.d.Henshaw@lboro.ac.uk] | [mailto:M.J.d.Henshaw@lboro.ac.uk M.J.d.Henshaw@lboro.ac.uk] | ||
| − | + | Jointly responsible for [[Product Systems Engineering]] and [[Systems of Systems (SoS)]] knowledge areas | |
|- | |- | ||
| Line 181: | Line 181: | ||
[mailto:heidi.davidz@rocket.com heidi.davidz@rocket.com] | [mailto:heidi.davidz@rocket.com heidi.davidz@rocket.com] | ||
| − | + | Jointly responsible for the [[Enabling Individuals]] and [[Enabling Teams]] knowledge area | |
|width="50%"|'''Emma Sparks''' | |width="50%"|'''Emma Sparks''' | ||
| Line 187: | Line 187: | ||
''Cranfield University'' | ''Cranfield University'' | ||
| − | + | Jointly responsible for the [[Enabling Individuals]] and [[Enabling Teams]] knowledge area | |
|} | |} | ||
| Line 200: | Line 200: | ||
[mailto:alice.squires@wsu.edu alice.squires@wsu.edu] | [mailto:alice.squires@wsu.edu alice.squires@wsu.edu] | ||
| + | Responsible for Part 6 | ||
|} | |} | ||
Revision as of 14:03, 5 December 2014
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 from Jan 2015)
- IEEE Computer Society
- Richard Fairley, Ken Nidiffer
- SERC
- David Olwell, Art Pyster (Past Governing Board Chair)
Past INCOSE governors Kevin Forsberg, David Newbern, David Walden, and Courtney Wright. 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 | |
|---|---|
| Heidi Davidz
Aerojet Rocketdyne (USA) Jointly responsible for the Enabling Individuals and Enabling Teams knowledge area |
Emma Sparks
Cranfield University Jointly responsible for the Enabling Individuals and Enabling Teams knowledge area |
| SEBoK Part 6 Related Disciplines |
|---|
| Alice Squires
Washington State University (USA) Responsible for Part 6 |
| 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 |
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) |
The Editorial Board is further supported by the BKCASE staff.
| BKCASE Staff |
|---|
| Kate Guillemette
IEEE Computer Society (USA) |
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
- Systems Engineering and Procurement/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