Systems Engineering Standards

"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.

"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.

"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 (http://arxiv.org/abs/1502.00121).

"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.

«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.

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.