Systems Engineering Body of Knowledge

Last updated

The Systems Engineering Body of Knowledge (SEBoK), formally known as Guide to the Systems Engineering Body of Knowledge, is a wiki-based collection of key knowledge sources and references for systems engineering. [1] The SEBoK is a curated wiki meaning that the content is managed by an editorial board, and updated on a regular basis. This wiki is a collaboration of three organizations: 1) International Council on Systems Engineering (INCOSE), 2) IEEE Systems Council, and 3) Stevens Institute of Technology. The most recent version (v.2.9) was released on November 20, 2023. [2]

Contents

History

The Guide was developed over three years, from 2009 to 2012, through the contributions of 70 authors worldwide. During this period, three prototype versions were created. The first prototype (v.0.25) was a document that was released for review in September 2010. However, the final versions were all published online as agreed by the authors in January 2011. This switch to a wiki-based SEBoK began with v.0.50. [3]

The first version of the SEBoK for public use was published online in September 2012. The initial release was named 2012 product of the year by the International Council on Systems Engineering. [4] Since then, the guide had several revisions and minor updates leading to the 19th release, as of November 2018. [2] Version 1.7, released on October 27, 2016, added a new Healthcare Systems Engineering knowledge area. [5]

Knowledge areas

According to the site, the guide has a total of 26 knowledge areas distributed among the different parts. However, the majority of these knowledge areas can be grouped to form nine general knowledge areas. The general and specific knowledge areas are:

Related Research Articles

Software engineering is an engineering-based approach to software development. A software engineer is a person who applies the engineering design process to design, develop, test, maintain, and evaluate computer software. The term programmer is sometimes used as a synonym, but may emphasize software implementation over design and can also lack connotations of engineering education or skills.

<span class="mw-page-title-main">Systems engineering</span> Interdisciplinary field of engineering

Systems engineering is an interdisciplinary field of engineering and engineering management that focuses on how to design, integrate, and manage complex systems over their life cycles. At its core, systems engineering utilizes systems thinking principles to organize this body of knowledge. The individual outcome of such efforts, an engineered system, can be defined as a combination of components that work in synergy to collectively perform a useful function.

<span class="mw-page-title-main">Product lifecycle</span> Duration of processing of products from inception, to engineering, design & manufacture

In industry, product lifecycle management (PLM) is the process of managing the entire lifecycle of a product from its inception through the engineering, design and manufacture, as well as the service and disposal of manufactured products. PLM integrates people, data, processes, and business systems and provides a product information backbone for companies and their extended enterprises.

<span class="mw-page-title-main">V-model</span> Graphic of a systems development lifecycle

The V-model is a graphical representation of a systems development lifecycle. It is used to produce rigorous development lifecycle models and project management models. The V-model falls into three broad categories, the German V-Modell, a general testing model, and the US government standard.

Enterprise architecture (EA) is a business function concerned with the structures and behaviours of a business, especially business roles and processes that create and use business data. The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes."

<span class="mw-page-title-main">International Council on Systems Engineering</span> Internal engineering trades organisation

The International Council on Systems Engineering is a not-for-profit membership organization and professional society in the field of systems engineering with about 17,000 members including individual, corporate, and student members. INCOSE's main activities include conferences, publications, local chapters, certifications and technical working groups.

End-user development (EUD) or end-user programming (EUP) refers to activities and tools that allow end-users – people who are not professional software developers – to program computers. People who are not professional developers can use EUD tools to create or modify software artifacts and complex data objects without significant knowledge of a programming language. In 2005 it was estimated that by 2012 there would be more than 55 million end-user developers in the United States, compared with fewer than 3 million professional programmers. Various EUD approaches exist, and it is an active research topic within the field of computer science and human-computer interaction. Examples include natural language programming, spreadsheets, scripting languages, visual programming, trigger-action programming and programming by example.

<span class="mw-page-title-main">Enterprise modelling</span>

Enterprise modelling is the abstract representation, description and definition of the structure, processes, information and resources of an identifiable business, government body, or other large organization.

<span class="mw-page-title-main">Business architecture</span> Business discipline

In the business sector, business architecture is a discipline that "represents holistic, multidimensional business views of: capabilities, end‐to‐end value delivery, information, and organizational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders."

A body of knowledge is the complete set of concepts, terms and activities that make up a professional domain, as defined by the relevant learned society or professional association. It is a type of knowledge representation by any knowledge organization. Several definitions of BOK have been developed, for example:

<span class="mw-page-title-main">Enterprise life cycle</span> Process of changing an enterprise over time

Enterprise life cycle (ELC) in enterprise architecture is the dynamic, iterative process of changing the enterprise over time by incorporating new business processes, new technology, and new capabilities, as well as maintenance, disposition and disposal of existing elements of the enterprise.

There is a large body of knowledge that designers call upon and use during the design process to match the ever-increasing complexity of design problems. Design knowledge can be classified into two categories: product knowledge and design process knowledge.

<span class="mw-page-title-main">Industrial engineering</span> Branch of engineering which deals with the optimization of complex processes or systems

Industrial engineering is an engineering profession that is concerned with the optimization of complex processes, systems, or organizations by developing, improving and implementing integrated systems of people, money, knowledge, information and equipment. Industrial engineering is central to manufacturing operations.

Macroscope is an integrated set of methods aimed at enterprise IT activities. Macroscope was developed and is maintained by Fujitsu in Canada. It is primarily used as their core body of knowledge to support the consulting services that they provide to their clients and is also licensed as a commercial product to a number of their clients

The following outline is provided as an overview of and topical guide to applied science:

The following outline is provided as an overview of and topical guide to software development:

Philip Keith M'Pherson was a British systems engineer, consultant, Emeritus Professor of Systems Engineering & Management at the City University London, and founder of the Department of Systems Science at City University, also known as developer of the Inclusive Valuation Methodology.

Model-based systems engineering (MBSE), according to the International Council on Systems Engineering (INCOSE), is the formalized application of modeling to support system requirements, design, analysis, verification and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases. MBSE is a technical approach to systems engineering that focuses on creating and exploiting domain models as the primary means of information exchange, rather than on document-based information exchange. MBSE technical approaches are commonly applied to a wide range of industries with complex systems, such as aerospace, defense, rail, automotive, manufacturing, etc.

A digital twin is a digital model of an intended or actual real-world physical product, system, or process that serves as the effectively indistinguishable digital counterpart of it for practical purposes, such as simulation, integration, testing, monitoring, and maintenance. The digital twin has been intended from its initial introduction to be the underlying premise for Product Lifecycle Management and exists throughout the entire lifecycle of the physical entity it represents. Since information is granular, the digital twin representation is determined by the value-based use cases it is created to implement. The digital twin can and does often exist before there is a physical entity. The use of a digital twin in the creation phase allows the intended entity's entire lifecycle to be modeled and simulated. A digital twin of an existing entity may be used in real-time and regularly synchronized with the corresponding physical system.

References

  1. "Guide to the Systems Engineering Body of Knowledge".
  2. 1 2 "Development of SEBOK v2.5".
  3. "Development of SEBoK v.1.0".
  4. "Systems Engineering Body of Knowledge Honored with Prestigious INCOSE Award" (Press release). NAval Postgraduate School. 19 February 2013. Retrieved 6 December 2018.
  5. "Development of SEBoK v.1.7".