Call me back
We will call you back!

Systems Engineering Standards

International Organisation for Standardization
International Council on Systems Engineering (INCOSE)
OMG standards are driven by vendors, end-users, academic institutions and government agencies.
The methodology of the Systems Management School is based on generally accepted documents. Among these documents, there are variety of international standards and public documents that contain well-defined and collectively discussed wording and diagrams of various provisions of the systems approach.
ISO/IEC/IEEE 15288:2015(E)
"Systems and software engineering - System life cycle processes" is the basic standard of system engineering. It sets the concept of the system and life cycle itself, distinguishes between the system of interest and the enabling system, introduces the concept of life cycle practices.

Its latest version was adopted in May 2015, before this version, the version of 2008 was used.

In the new version of the standard, a list of practices (different version in comparison with the Russian official version) is formulated, which should be performed by system engineers and managers at all stages of the system's life. And here we talk not only about specific technical practices, but also about practices such as contractual relations, management of project and portfolios, risk management, human resources management.

Compared with the previous (or the one translated into Russian before) version of this standard, among the list of technical practices there appeared practices of business analysis, identification of needs and requirements of stakeholders, knowledge management and others.
ISO/IEC/IEEE 42010:2011
"Systems and software engineering - Architecture description": this is the standard that sets the multiplicity of descriptions within the framework of the activity approach. This standard sets the "turn of the brains" from the reductionist approach of one inclusive description to the system approach, implying multiplicity of related private descriptions documented in various information systems in accordance with various description methods. These methods of description outline the diverse interests of different stakeholders.
OMG Essence
"Kernel and Language for Software Engineering Methods": a description of the life cycle as a set of practices. This standard separates the abstract matters of disciplines (alpha) and specific matters of tools and documents (working products) in practice of the life cycle. The standard also considers changes in the state of alphas and work products during the life cycle. The standard explains further than its predecessors in the field of situational engineering methods (for example, ISO / IEC 24744, OMG SPEM 2.0). Meaning that it identifies a set of types of the main project matters, and also determines their initial set, including checklists to their states in the course of the life cycle. The standard also offers a facilitated format for presenting these control questions in the form of paper cards (although it does not exclude the electronic user format). The standard is focused on software engineering, and we use it for system engineering, adopted as the product of the Russian branch of INCOSE (
IEC 81346-1:2009
"Industrial systems, installations and equipment and industrial products - Structuring principles and reference designations - Part 1: Basic rules" - is used for a minimal description of the structure of the system in a variety of its hypostases (functional-component, product-module and location) and systems for designating complex engineering objects (principles of engineering coding, consistent with the concept of holon). This standard is the foundation for managing the configuration during the life cycle.
ISO 15926-2:2003
«Industrial automation systems and integration -Integration of life-cycle data for process plants including oil and gas production facilities -Part 2: Data model "- used to model the data of detailed (complete) descriptions of engineering objects. Provides the federation of detailed descriptions in various information systems of the life cycle. From this standard we use the idea of the physical nature of all systems. All systems are in the physical world, which implies their space-time extent. Therefore, standard represents systems as 4D objects.
OpenGroup ArchiMate 3.0 Specification
Specification of the architectural language for modeling of enterprises, including their business architecture, activity of the team, as well as the corporate software which supports this activity, a variety of hardware and computer networks required for the operation of this software, also taking into account physical equipment, as well as within the strategy of enterprise. Today this is the most modern and the most popular standard of the architectural approach and the language of the description of the enterprise architecture, i.e. the basic decisions considering organization of the enterprise, including decisions on the strategy, as well as decisions on the deployment of supporting IT activities and other (for example, machine tools) technology.
Other Standards and public documents
  • BKCASE, Body of Knowledge and Curriculum to Advance Systems Engineering (2014)
  • IEC 61355-1 (2008), Classification and designation of documents for plants, systems and equipment – Part 1: Rules and classification tables.
  • IEC 81346 (2009), Industrial systems, installations and equipment and industrial products — Structuring principles and reference designations — Part 1: Basic rules.26
  • ISO/IEC/IEEE 12207 (2008) Systems and software engineering — Software life cycle processes and ISO/IEC/IEEE 15288 (2008) Systems and software engineering — System life cycle processes.
  • ISO 15926-2 (2003), Industrial automation systems and integration — Integration of life-cycle data for process plants including oil and gas production facilities — Part 2:Data model.
  • ISO/IEC 24744 (2007), Software Engineering — Metamodel for Development Methodologies.
  • ISO/IEC TR 24774 (2010), Systems and software engineering — Life cycle management — Guidelines for process description.
  • ISO/IEC/IEEE 42010 (2011) Systems and software engineering – Architecture description.
  • OMG BMM (2014), Business Motivation Model
  • OMG SBVR (2013), Semantics of Business Vocabulary and Rules
  • OMG SPEM 2.0 (2008), Software & Systems Process Engineering Metamodel,
  • OMG SysML (2012), Systems Modeling Language
  • OpenGroupArchiMate 3.0 (2016)
  • SEH (2014), INCOSE Systems Engineering Handbook.
We get our students familiar with the most of these standards in the framework of our course "Systems Management and Strategy". For corporate clients, in addition to acquaintance with these standards, the best practices associated with their field of use are selected and recommended for development.
Not ready yet to enroll in our course? Well we created something very useful and absolutely free for you: project analysis check-list
Get the checklist and start applying it right now!
Do you want to make sure that your project is on the right track? Check-lists for project analysis - a convenient and effective way to diagnose the project at any stage.
Using check-lists, you can:
  • check whether all hypotheses, perspectives and risks are taken into account at the planning stage;
  • Structure available information on the project;
  • get feedback from the team;
  • establish a way forward;
  • be sure that there are no "blank spots" - the check-lists cover all possible aspects of project management.
The checklist is a document that helps to check ourselves. For example, a list of actions to be taken, or items that you need not to overlook taking with you. Check-lists are used in aviation, medicine, construction - places where errors are unacceptable. If you are responsible for project management, we suggest that you use checklists - a truly reliable method of control.
This is free of charge!
Other important articles