|
|
Line 1: |
Line 1: |
− | __NOTOC__
| + | <blockquote> ''A functional architecture is a set of functions and their sub-functions that defines the transformations of input flows into output flows performed by the system to achieve its mission.'' (Created for SEBoK)</blockquote> |
− | ==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.
| + | ===Source=== |
| + | This definition was developed for the SEBoK. |
| | | |
− | The BKCASE Governing Board includes: | + | ===Discussion=== |
− | *'''INCOSE'''
| + | The definition is adapted from ISO/IEC/IEEE 24748 - 4 (past IEEE 1220, ISO/IEC 26702) as functional architecture; but it is here modified to emphasize on transformations performed. See also definition of [[Behavioral Architecture (glossary) |behavioral architecture (glossary)]]. |
− | **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.
| + | '''Works Cited''' |
| + | ISO/IEC. 2010. ''Systems and Software Engineering, Part 1: Guide for Life Cycle Management''. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC), ISO/IEC 24748-1:2010. |
| | | |
− | The stewards appoint the BKCASE Editor in Chief to manage the SEBoK and GRCSE and oversee the Editorial Board.
| + | [[Category:Glossary of Terms]] |
| | | |
− | ==Editorial Board==
| + | <center>'''SEBoK v. 1.9.1, released 16 October 2018'''</center> |
− | The SEBoK Editorial Board is chaired by an Editor in Chief, supported by a group of Associate Editors.
| |
− | | |
− | {|style="width:100%"
| |
− | !colspan="2"|BKCASE Editor in Chief
| |
− | |-
| |
− | |style="background-color: #ffffff"|
| |
− | [[File:RickAdcock.png|center|150px]]
| |
− | |style="background-color: #ffffff"|
| |
− | '''Richard D. Adcock'''
| |
− | | |
− | ''Cranfield University (UK)'' | |
− | | |
− | [mailto:richard.adcock@incose.org richard.adcock@incose.org]
| |
− | | |
− | SEBoK v. 1.3.1 is the second iteration of the SEBoK published under Rick's leadership. | |
− | |}
| |
− | | |
− | | |
− | 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
| |
− | |-
| |
− | |'''Ariela Sofer'''
| |
− | | |
− | ''George Mason University (USA)''
| |
− | | |
− | [mailto:asofer@gmu.edu asofer@gmu.edu]
| |
− | | |
− | Responsible for Part 1
| |
− | |}
| |
− | | |
− | | |
− | {|style="width:100%"
| |
− | !colspan="2"|SEBoK Part 2: Systems
| |
− | |-
| |
− | |width="50%"|'''Cihan Dagli'''
| |
− | | |
− | ''Missouri University of Science & Technology (USA)''
| |
− | | |
− | [mailto:dagli@mst.edu dagli@mst.edu]
| |
− | | |
− | Responsible for the [[Systems Approach Applied to Engineered Systems]] knowledge areas
| |
− | | |
− | |width="50%"|'''Dov Dori'''
| |
− | | |
− | ''Massachusetts Institute of Technology (USA) and Technion Israel Institute of Technology (Israel)''
| |
− | | |
− | [mailto:dori@mit.edu dori@mit.edu]
| |
− | | |
− | Responsible for the [[Representing Systems with Models]] knowledge area
| |
− | |-
| |
− | |'''Duane Hybertson'''
| |
− | | |
− | ''MITRE (USA)''
| |
− | | |
− | Responsible for the [[Systems Fundamentals]], [[Systems Science]] and [[Systems Thinking]] knowledge areas
| |
− | | |
− | |'''Janet Singer''' (USA)
| |
− | | |
− | Responsible for the [[Systems Fundamentals]], [[Systems Science]] and [[Systems Thinking]] knowledge areas
| |
− | |-
| |
− | |colspan=2|'''Mike Yearworth'''
| |
− | | |
− | ''University of Bristol (UK)''
| |
− | | |
− | Responsible for the [[Systems Fundamentals]], [[Systems Science]] and [[Systems Thinking]] knowledge areas
| |
− | |}
| |
− | | |
− | | |
− | | |
− | {|style="width:100%"
| |
− | !colspan="2"|SEBoK Part 3: Systems Engineering and Management
| |
− | |-
| |
− | |width="50%"|'''Barry Boehm'''
| |
− | | |
− | ''University of Southern California (USA)''
| |
− | | |
− | [mailto:boehm@usc.edu boehm@usc.edu]
| |
− | | |
− | Responsible for the [[Systems Engineering Management]] and [[Life Cycle Models]] knowledge areas
| |
− | | |
− | |width="50%"|'''Kevin Forsberg'''
| |
− | | |
− | ''OGR Systems''
| |
− | | |
− | Responsible for the [[Systems Engineering Management]] and [[Life Cycle Models]] knowledge areas
| |
− | | |
− | |-
| |
− | |'''Gregory Parnell'''
| |
− | | |
− | ''University of Arkansas (USA)''
| |
− | | |
− | [mailto:gparnell@uark.edu gparnell@uark.edu ]
| |
− | | |
− | 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 in Part 3: Systems Engineering and Management.
| |
− | | |
− | |-
| |
− | |'''Ricardo Valerdi'''
| |
− | | |
− | ''University of Arizona (USA)''
| |
− | | |
− | [mailto:rvalerdi@email.arizona.edu rvalerdi@email.arizona.edu]
| |
− | | |
− | Responsible for the [[System Realization]] knowledge.
| |
− | | |
− | |'''Ken Zemrowski'''
| |
− | | |
− | ''TASC''
| |
− | | |
− | [mailto:kenneth.zemrowski@incose.org kenneth.zemrowski@incose.org]
| |
− | | |
− | Responsible for the [[Systems Engineering Standards]] knowledge area.
| |
− | |}
| |
− | | |
− | | |
− | | |
− | {|style="width:100%"
| |
− | !colspan="2"|SEBoK Part 4: Applications of Systems Engineering
| |
− | |-
| |
− | |width="50%"|'''Judith Dahmann'''
| |
− | | |
− | ''MITRE Corporation (USA)''
| |
− | | |
− | [mailto:jdahmann@mitre.org jdahmann@mitre.org]
| |
− | | |
− | Responsible for [[Product Systems Engineering]] and [[Systems of Systems (SoS)]] knowledge areas
| |
− | | |
− | |width="50%"|'''Michael Henshaw'''
| |
− | | |
− | ''Loughborough University (UK)''
| |
− | | |
− | [mailto:M.J.d.Henshaw@lboro.ac.uk M.J.d.Henshaw@lboro.ac.uk]
| |
− | | |
− | 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.
| |
− | |}
| |
− | | |
− | | |
− | | |
− | {|style="width:100%"
| |
− | !colspan="2"|SEBoK Part 5: Enabling Systems Engineering
| |
− | |-
| |
− | |width="50%"|'''Heidi Davidz'''
| |
− | | |
− | ''Aerojet Rocketdyne (USA)''
| |
− | | |
− | [mailto:heidi.davidz@rocket.com heidi.davidz@rocket.com]
| |
− | | |
− | Responsible for the [[Enabling Individuals]] and [[Enabling Teams]] knowledge area
| |
− | | |
− | |width="50%"|'''Emma Sparks'''
| |
− | | |
− | ''Cranfield University''
| |
− | | |
− | Responsible for the [[Enabling Individuals]] and [[Enabling Teams]] knowledge area
| |
− | |}
| |
− | | |
− | | |
− | {|style="width:100%"
| |
− | !colspan="1"|SEBoK Part 6 Related Disciplines
| |
− | |-
| |
− | |'''Alice Squires'''
| |
− | | |
− | ''Washington State University (USA)''
| |
− | | |
− | [mailto:alice.squires@wsu.edu alice.squires@wsu.edu]
| |
− | | |
− | |}
| |
− | | |
− | | |
− | {|style="width:100%"
| |
− | !colspan="2"|SEBoK Part 7 Systems Engineering Implementation Examples
| |
− | |-
| |
− | |width="50%"|'''Brian Sauser'''
| |
− | | |
− | ''University of North Texas (USA)''
| |
− | | |
− | [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]]
| |
− | | |
− | |width="50%"|'''Brian White'''
| |
− | | |
− | ''CAU>SE (USA)''
| |
− | | |
− | [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]]
| |
− | | |
− | |}
| |
− | | |
− | ==Editorial Board Support==
| |
− | 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
| |
− | |-
| |
− | |'''Claus Ballegaard Nielsen'''
| |
− | | |
− | ''Cranfield University (UK)''
| |
− | | |
− | [mailto:c.nielsen@cranfield.ac.uk c.nielsen@cranfield.ac.uk]
| |
− | |}
| |
− | | |
− | The Editorial Board is further supported by the BKCASE staff.
| |
− | | |
− | {|style="width:200px"
| |
− | !BKCASE Staff
| |
− | |-
| |
− | |'''Kate Guillemette'''
| |
− | | |
− | ''IEEE Computer Society (USA)''
| |
− | | |
− | [mailto:kguillemette@computer.org kguillemette@computer.org]
| |
− | | |
− | |}
| |
− | | |
− | ==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 [mailto:bkcase.incose.ieeecs@gmail.com bkcase.incose.ieeecs@gmail.com].
| |
− | | |
− | | |
− | {{DISQUS}}
| |