bkcase: body of knowledge and curriculum to advance systems
DESCRIPTION
TRANSCRIPT
BKCASE:Body of Knowledge and Curriculum to
Advance Systems Engineering
Panel Discussion
2010 EUSEC Academic Forum, StockholmRick Adcock, Bud Lawson, Dave Olwell, Art Pyster, Jean
Claude Roussel
www.bkcase.org
01/27/2010 2
Agenda
• What is BKCASE and SEBoK?
• What are the challenges raised by the SEBoK, an INCOSE perspective.
• What is the value of SEBoK to the Systems Engineering community, an authors perspective
• Questions and floor discussion
(10 mins)
(20 mins)
(15 mins)
(45 mins)
What is BKCASE?
• Project led by Stevens Institute of Technology and Naval Postgraduate School who are creating two primary products:
– Body of Knowledge in systems engineering (SEBoK)
– Graduate Reference Curriculum in Systems Engineering (GRCSE)
• Started in September 2009 and will run through 2012
• Intended for world-wide use
• A GUIDE to the Body of Knowledge
• A FRAMEWORK for curriculum development
301/27/2010
BKCASE Vision and Objectives
4
“Systems Engineering competency models, certification programs, textbooks, graduate programs, and related workforce development
initiatives around the world align with BKCASE.”
Vision
1. Create a SEBoK that is globally recognized by the SE community as the authoritative BoK for the SE discipline.
2. Create a graduate reference curriculum for SE (GRCSE – pronounced “Gracie”) that is globally recognized by the SE community as the authoritative guidance for graduate programs in SE.
3. Facilitate the global alignment of related workforce development initiatives with SEBoK and GRCSE.
4. Transfer stewardship of SE BoK and GRCSE to INCOSE and the IEEE after BKCASE publishes version 1.0 of those products, including possible integration into their certification, accreditation, and other workforce development and education initiatives.
Objectives
01/27/2010 4
Our Partners
30-31 March 20105
01/27/2010 6
Author Organization SEBOK GRCSE
Rick Adcock Cranfield University X X
Johann Amsenga Eclipse RDC X
Erik Aslaksen Sinclair Knight Merz X
John Baras University of Maryland
Barry Boehm University of California X
Edmund Conrow Management and Technology Associates X
Paul Croll CSC X
Cihan Dagli Missouri University of Science and Technology
X
Joseph J. Ekstrom Brigham Young University X
Marcia Enos Lockheed Martin X
Alain Faisandier Association Francaise d‘lingeniere Systeme X
Tim Ferris University of South Australia X
Kevin Forsberg Center for Systems Management X
Richard Freeman Air Force Institute of Technology X
Sanford Friedenthal Lockheed Martin X
Richard Frost General Motors Corporation
Don Gelosh US Department of Defense X
Edward Ghafari ICES Corporation
Richard Grzybowski Corning Incorporated
Tom Hilburn Embry-Riddle Aeronautical University X
Scott Jackson University of Southern California X
Ken Kepchar Federal Communications Commissions X
Authors as of
May 2010
01/27/2010 7
Authors,cont. as of
May 2010
Author Organization SEBOK GRCSE
Mike Krueger ASE Consulting X
Harold “Bud” Lawson Lawson Konsult AB X
Yeaw lip “Alex” Lee Defence Science and Technology Agency
Ray Madachy Naval Postgraduate School X
Andrew McGettrick Association for Computing Machinery X
Ken NiDiffer Software Engineering Institute X
Dave Olwell Naval Postgraduate School X X
Daniel Prun Ecole Nationale de l’Aviation Civile (ENAC) X
Art Pyster Stevens Institute of Technology X X
Garry Roedler Lockheed Martin X
Jean-Claude Roussel EADS X
Sven-Olaf Schulze Berner & Mattner
Hillary Sillitto Thales Group X
John Snoderly Defense Acquisition University X
Alice Squires Stevens Institute of Technology X X
Massood Towhidnejad Embry-Riddle Aeronautical University X
Guilherme Horta Travassos Federal University of Rio de Janeiro (UFRJ) X
Mary VanLeer Arkansas Scholarship Lottery X
Qing Wang Institute of Software Chinese Academy of Sciences
Brian Wells Raytheon X
SEBoK Value Proposition
8
1. There is no authoritative source that defines and organizes the knowledge of the SE discipline, including its methods, processes, practices, and tools. The resulting knowledge gap creates unnecessary inconsistency and confusion in understanding the role of SE in projects and programs; and in defining SE products and processes. SEBOK will fill that gap, becoming the “go to” SE reference.
2. The process of creating the SEBoK will help to build community consensus on the boundaries and context of SE thinking and to use this to help understand and improve the ability of management, science and engineering disciplines to work together.
3. Having a common way to refer to SE knowledge will facilitate communication among systems engineers and provide a baseline for competency models, certification programs, educational programs, and other workforce development initiatives around the world. Having common ways to identify metadata about SE knowledge will facilitate search and other automated actions on SE knowledge.
01/27/2010 8
01/27/2010 http://www.BKCASE.org/about-bkcase/bkcase-story/ 9
Table of Contents as of April 2010 1. Executive Summary2. Introduction (Overview)
• Purpose of BoK• Scope
3. System Concepts & Systems Thinkinga. System Definition – what is a systemb. Systems Thinking
4. Fundamentalsa. Value of SEb. Core Principles of SEc. SE applied to Lifecycle, Service and Enterprised. Integration with software engineering and project managemente. Application domains (including Socio-technical Issues)f. SE Standards
5. SE Approach and Practicesa. Life Cyclesb. Organizationc. Managementd. Technicale. Agreement
6. Specialty Engineering/Design Considerations7. SE Competency (ethics, statistical modeling, …)8. SE Applications/Case Studies9. Glossary
An INCOSE ViewJean-Claude Roussel
BKCASETM
Body of Knowledge and Curriculumto Advance Systems Engineering
Panel at EUSEC, Stockholm , 26th May 2010
3 - BKCASE and INCOSE
What are the challenges raised by the SEBoK, an INCOSE perspective
a) Why should INCOSE be involved in BKCASE ?
b) How might INCOSE use and support the SEBoK ?
c) Thought on the impact of the SEBoK on INCOSE Handbook, Certification, Education,…
Share, promote and advance the best of systems engineering from across
the globe for the benefit of humanity and the planet.
Mission of INCOSE
Why should INCOSE be involved in BKCASE ?
• To provide a focal point for the dissemination of systems engineering knowledge
• To promote international collaboration in systems engineering practice, education, and research
• To assure the establishment of competitive, scalable professional standards in the practice of systems
• To improve the professional status of all persons engaged in the practice of systems engineering
• To encourage governmental and industrial support for research and educational programs that will improve the systems engineering process and its practice
INCOSE Goals
Why should INCOSE be involved in BKCASE ?
BKCASE Vision
“Systems Engineering competency models, certification programs, textbooks, graduate programs, and related workforce development
initiatives around the world align with BKCASE.”
1. Create a SEBoK that is globally recognized by the SE community as the authoritative BoK for the SE discipline.
2. Create a graduate reference curriculum for SE (GRCSE – pronounced “Gracie”) that is globally recognized by the SE community as the authoritative guidance for graduate programs in SE.
3. Facilitate the global alignment of related workforce development initiatives with SEBoK and GRCSE.
4. Transfer stewardship of SE BoK and GRCSE to INCOSE and the IEEE after BKCASE publishes version 1.0 of those products, including possible integration into their certification, accreditation, and other workforce development and education initiatives.
Why should INCOSE be involved in BKCASE ?
BKCASE Objectives
How might INCOSE use and support the SEBoK ?
• INCOSE, IEEE Systems Council, IEEE Computer Society Educational Activities Board, the NDIA Systems Engineering Division, and ACM are all participants
• Explicitly seek INCOSE and the IEEE to become sponsors and assume maintenance and revision responsibilities after Version 1.0 is published
• INCOSE has agreed to participate and fund 3 authors
• Specific sessions of BKCASE scheduled during INCOSE International Workshops and International Symposia, including regional conference (such as this EUSEC event)
• Support of INCOSE Technical Operations and Working Groups to participate in writing and reviewing the SEBoK and GRCSE
• How can INCOSE member get involved?– INCOSE members on the author team– Regular updates via INSIGHT etc.– Technical papers and other communications– Sessions at INCOSE Events (like this one)
• BKASE reviews:– Version 0.25 will be reviewed by authors and invited
reviewers– Version 0.5 and beyond will be open for general review
** the review process is a key opportunity for INCOSE members to directly influence the direction**
How might INCOSE use and support the SEBoK ?
• Currently, INCOSE CSEP/ASEP Certification examination is based on the INCOSE SE Handbook
• As the SEBoK evolves, it should be evaluated as a way to replace/augment the INCOSE SE Handbook
• Eventually, the SEBoK may become the basis for the INCOSE certification exams
• It may also help refine the “scope” of systems engineering experience for CSEP and ESEP
Potential Impact to INCOSE Certification
Representation of Evolved INCOSE Graduate Reference Curriculum
Expected Impact on Undergraduate SE Programs
SEBoK should directly influence what is taught in undergraduate SE programs by providing community-based consensus on the boundaries, principles, content, and key references of SE
GRCSE should help to better distinguish between graduate and undergraduate education in SE and influence undergraduate education by guiding what is taught in graduate programs
BKCASETM
Body of Knowledge and Curriculumto Advance Systems Engineering
Panel at EUSEC, Stockholm , 26th May 2010
Harold “Bud” Lawson
An Author’s Perspective
www.bkcase.org
“It is in the nature of systemic thinking to yield many different views of the same thing and the same view of many different
things.”
- Rusell L. Ackoff
7 April 2010 23
EACH HAS THEIR OWN VIEWPOINTS AND VIEWSCONCERNING SYSTEMS AND SYSTEMS
ENGINEERING
A Unique Collection of Experienced Systems Engineers and Systems Engineering Educators
7 April 2010 24
7 April 2010 25
Rick Adcock, Cranfield University and INCOSE, UK Bud Lawson, Lawson Konsult AB, Sweden
Johann Amsenga, Eclipse RDC, South Africa Alex Lee, Defence Science and Technology Agency, Singapore
Erik Aslaksen, Sinclair Knight Merz, Australia Ray Madachy, Naval Postgraduate School, US
John Baras, IEEE Systems Council and University of Maryland, USAndrew McGettrick, Association for Computing Machinery (ACM) Education Board and Education Council
Barry Boehm, University of Southern California, USKen Nidiffer, Software Engineering Institute and IEEE Systems Council, US
Cihan Dagli, Missouri University of Science and Technology, USDave Olwell, Naval Postgraduate School and BKCASE Co-Principal Investigator, US
J. Ekstrom, Brigham Young University, USArt Pyster, Stevens Institute of Technology and BKCASE Principal Investigator, US
Alain Faisandier, Map Systeme, FranceGarry Roedler, Lockheed Martin and National Defense Industrial Association Systems Engineering Division, US
Tim Ferris, University of South Australia and INCOSE, Australia Jean-Claude Roussel, EADS, France
Kevin Forsberg, Center for Systems Management and INCOSE, USSven-Olaf Schulze, Berner & Mattner Systemtechnik GmbH, Germany
Richard Freeman, Air Force Center for Systems Engineering, US Jon Gye Shin, Seoul National University, South Korea
Sandy Friedenthal, Lockheed Martin, US Hillary Sillitto, Thales Group and INCOSE, UKRichard Frost, General Motors, US John Snoderly, Defense Acquisition University, USEdward Ghafari, ICES Corporation and Defense Information Systems Agency, US
Alice Squires, Stevens Institute of Technology, US
Richard Grzybowski, Corning Incorporated, US Massood Towhidnejad, Embry-Riddle University, US
Tom Hilburn, IEEE Computer Society and Embry-Riddle University, US Guilherme Travassos, Federal University of Rio de Janeiro, Brazil
Scott Jackson, University of Southern California, US Mary VanLeer, Arkansas Scholarship Lottery, USMichael Krueger, ASE Consulting, US Brian Wells, Raytheon, US
Expanding List of Authors
A FACILITATIVE ORGANIZATIONAL STRUCTURE IS REQUIRED TO PROMOTE THESE SKILLS.
THE BKCASE PROJECT PROVIDES THIS STRUCTURE
In a learning organization, people are able to test many mental models – their own as well as those of colleagues.
Peter Senge
7 April 2010 26
A Personal Example
7 April 2010 27
In explaining the Role of Systems as part of the System Conceptsand Systems Thinking Chapter , I presented the following model
The System-Coupling Diagram
Base model: System Coupling Diagram (Fig 3.4 from Chapter 3 – Lawson 2010)
Problem owners (Community or organisation or individual)
Problem owners (Community or organisation or individual)
Organisations that provide systems engineering capabilities, skills, expertise, resources and enablers:Consultancies, service providers (architecture, requirements,analysis, support, assurance, change management)Resource providers (contract staff etc) ; Training and education providers, research organisations, tool vendors
Organisations that provide systems engineering capabilities, skills, expertise, resources and enablers:Consultancies, service providers (architecture, requirements,analysis, support, assurance, change management)Resource providers (contract staff etc) ; Training and education providers, research organisations, tool vendors
Organisations responsible for the respondent system:
Funding, Specification, Acquisition, Integration,
Operation, Retiral
Organisations responsible for the respondent system:
Funding, Specification, Acquisition, Integration,
Operation, Retiral
Organisations that develop, support, operate, and dispose of
the system assets
Organisations that develop, support, operate, and dispose of
the system assets
Or for “delivering the respondent
capability”
Extended supply chain
Extended supply chain
Reuse and Adaptation
Hillary Sillitto used the following in explaining the role of Systems Engineering Organization in Chapter 6
Contributing Authors Rewards
7 April 2010 29
• Personally and for Sweden – Providing a Small Country Input to a major International Project
• A Meeting Point for Colleagues (Physically and by Internet)
• Learning from Others
• Adding Value to the Body of Knowledge
• Having Fun
