SEBOK Panel Discussion NDIA SE Conference 25-28 October 2010
18
SEBOK Panel Discussion NDIA SE Conference 25-28 October 2010 Dr. Don Gelosh, CSEP-Acq ODDR&E/Systems Engineering Mr Garry Roedler, ESEP Lockheed Martin Corporation Dr. John R. Snoderly, D.P.A., CSEP Defense Acquisition University 13th Annual NDIA Systems Engineering Conference San Diego, CA | October 27, 2010
Transcript of SEBOK Panel Discussion NDIA SE Conference 25-28 October 2010
SEBOK Panel DiscussionNDIA SE Conference25-28 October 2010
Dr. Don Gelosh, CSEP-AcqODDR&E/Systems Engineering
Mr Garry Roedler, ESEPLockheed Martin Corporation
Dr. John R. Snoderly, D.P.A., CSEPDefense Acquisition University
13th Annual NDIA Systems Engineering ConferenceSan Diego, CA | October 27, 2010
Dr. John SnoderlyProfessor of Systems Engineering Management
• 17 years Civilian Navy• Major Systems include:
– Sea Hawk SH-60, AH-1J, UH-1E, SH-2F • Highlights
– 3 years in Flight Test NATC– 2 years Flight Restrictions Office– 6 years Stability & Control Engineer– 6 years LAMPS MK III Program Office
• 1 year PM-15 Chief Engineer• 4 years Aircraft/Engine Manager• 1 year Deputy PM Lamps Mk III
• Aerospace Engineer• 30 years @ DSMC/DAU• West Virginia University BSAE• University of Southern California MSSM, MPA,
DPA (1996) • 2002-2004 - President INCOSE, CSEP March, 2008
Office: Rm 105, Bldg 208Phone: 805-5258 (DSN 655)EMAIL: [email protected]
SEBOK OCEAN
SEBOK Oceans
Software OCEAN
SE Design OCEAN
SE Tech MgmtOCEANSE Process
OCEAN
Hardware OCEAN
What is BKCASE?• Project to create:
– Systems Engineering Body of Knowledge
– Graduate Reference Curriculum in Systems Engineering (GRCSETM – pronounced “Gracie”)
• Started in September 2009 by Stevens Institute of Technology and Naval Postgraduate School with primary support from Department of Defense
• Project will run through 2012
• Intended for world-wide use
5
What is the SEBoK?
6
Describes the boundaries, terminology, content, and structure of SE that are needed to systematically and consistently support:
Guide to the literature, not all the content of the literature
http://www.BKCASE.org/about-bkcase/bkcase-story/ 7
Authorsas of
10/2010
8
Author Organization SEBOK GRCSE
Rick Adcock Cranfield University in the UK X X
Erik Aslaksen Sinclair Knight Merz in Australia X
John Baras University of Maryland
Richard Beasley Rolls Royce in the UK X
Barry Boehm University of Southern California X
John Brackett University of Boston X
Aaron Eng Seng Chia National University of Singapore X
Edmund Conrow Management and Technology Associates
X
Paul Croll CSC X
Cihan Dagli Missouri University of Science and Technology
X
Heidi Davidz UTC Pratt & Whitney X
Joseph J. Ekstrom Brigham Young University X
Marcia Enos Lockheed Martin in the US X
Dick Fairley Institute of Electrical and Electronics Engineering (IEEE)
Alain Faisandier Association Francaise d‘lingeniereSysteme
X
Tim Ferris University of South Australia X
Kevin Forsberg Center for Systems Management X
G. Richard Freeman Air Force Institute of Technology X X
Sanford Friedenthal Lockheed Martin X
Richard Frost General Motors Corporation
Authors, cont.as of
10/2010
9
Author Organization SEBOK GRCSE
Brian Gallagher Northrup Grumman X
Edward Ghafari ICES Corporation
Tom Hilburn Embry-Riddle Aeronautical University X X
Nicole Hutchison Stevens Institute of Technology X X
Scott Jackson University of Southern California X
Ken Kepchar Federal Aviation Administration X
Naohiko Kohtake Keio University in Japan X
Mike Krueger ASE Consulting X
Harold “Bud” Lawson Lawson Konsult AB X
Yeaw lip “Alex” Lee Defence Science and Technology Agency
X
Ray Madachy Naval Postgraduate School X
James Martin Aerospace Corporation X
Greg Mayhew The Boeing Company X
Andrew McGettrick Association for Computing Machinery
X
Ken NiDiffer Software Engineering Institute X 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
Seiko Shiraska Keio University in Japan X
Hillary Sillitto Thales Group X
Authors, cont.as of
10/2010
10
Author Organization SEBOK GRCSE
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 Content1. The definition of fundamental terms and concepts and primary
relationships between those concepts
2. A statement of the principles of SE
3. A description of generally accepted activities, practices, technologies, processes, methods, and artifacts of SE and how they relate to one another
4. How the knowledge of SE varies within individual application domains such as medicine, transportation, and telecommunications
5. References to books, articles, websites, and other sources that elaborate on the information in the SEBoK
Version 0.25 released for limited review on September 15, 2010
11
Agile MethodsAgile methods generally promote a disciplined
project management process that encourages:1. Frequent inspection and adaptation,2. A leadership philosophy that encourages
teamwork, self-organization and accountability, 3. A set of engineering best practices intended to
allow for rapid delivery of high-quality software 4. A business approach that aligns development with
customer needs and company goals.
Comparison of SEBOK and AGILE TeamsSEBOK Team
1. Broke into sub teams of 4 to 5 Authors with a team lead
2. Authors were invited based on experience and reputation in their SE area
3. SEBOK has had 4 workshops reviewing progress and pushing ahead with V 0.25
4. Communication is by face to face at Workshops, WEB-X in-between
5. Stevens centralized database is available to everyone of the authors
AGILE Team*1. Minimize team size, maximize
team talent (FIST Manifesto)(Fast, Inexpensive, Simple, Tiny)
2. Agile teams are more successful with more experienced and skilled team members SC
3. Documents and meetings must be short. Have as many as necessary, as few as possible.
4. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation
*Considerations for Using Agile in DoD Acquisition, SEI Report CMU/SEI-2010-TN-002 April, 2010
Bounding the Problem• In our attempt to define the boundaries of the subject, the team
defined what is meant by “Technical Knowledge” and how it should best be presented in the SEBOK. If the technical portion of SE is not properly defined and organized then it follows that the development of the system is not going to be successful. Organizing “Technical Knowledge” into its key process components is key to the successful work of systems engineering.
• The organization of technical knowledge processes is very important in the design of the products of a system. The processes must include the operational products and the supporting or enabling products required to produce, support, operate or dispose of a system. Technical processes are also used to realize these system products. These processes, organized and tailored as needed, will apply to the type of system being developed.
15
Mapping: ISO/IEC 15288 Technical processes – Technical KA
8.1 Stakeholders Requirements KA
8.2 System Requirements KA
8.5 Implementation of technological components KA
8.6 System Integration KA
8.7 Verification & Validation KA
8.8 Transfer for use KA
8.9 Operation KA
8.10 Maintenance & Logistic Support KA
8.11 Disposal KA
Stakeholders Req Definition Process
Requirements Analysis Process
Architectural Design Process
Implementation Process
Integration Process
Transition Process
Operation Process
Maintenance Process
Disposal Process
(System) Validation Process
(System)Verification Process
8.0 Mission Analysis KA
Stakeholders Needs
Stakeholder Req V&V
Syst Req V&V
Design V&V
8.4 System analysis KA
8.3 Architectural Design KA
Design considerations KA including 8.8, 8.9, 8.10, 8.11 topics or under 8.3 KA?
Realization
Integration
Needs
Stakeholders
Requirements
Syst. Element
Requirements
Component
Requirements
HW/SW
Requirements
HW/SW
Development
HW/SW
Verification
Syst. Element
Integration
Systems
Integration
System Verification
Specifcation
System Validation
Specifcation
You built the right system
You built the system right
Verify System against Stakeholders Requirements
Verify System against System Requirements
Validate Requirements
Validate Requirements
Validate Requirements
Systems Requirements
The Validation “V”
For Additional Information:Dr. John R. Snoderly
Defense Acquisition [email protected]
Mr. Garry RoedlerLockheed Martin Corporation
Dr. Don GeloshODDR&E/Systems Engineering
