July 14, 2019 at 21:58GOST R 57100-2016. What was it?
In September 2017, the National Standard of the Russian Federation was introduced, which received the designation GOST R 57100-2016 (the status is indicated here , the text can be found here ) (I will call it “hundred” for simplicity, recognizing the risk of tomatoes being thrown over such a gag). Since now we have to deal with the real requirements of customers regarding adherence to this standard even when describing the concept of an information system, it seems that it is time to look at this standard more closely.
No one is even going to hide the fact that behind GOST R there is a completely non-guest approach, described in ISO / IEC / IEEE 42010: 2011 Systems and software engineering - Architecture description. Moreover, this approach is not Gost's from the word at all, because GOST R 57100-2016 is not only in no way connected with any GOST, but also introduces its own philosophy, which is alien to the traditional GOST (I will not speak about the quality of the text of the standard, because there’s even a link to other standards are given either in Russian “ISO / IEC 10746”, or in English “ISO 15704” - apparently, it was difficult for the authors of “hundred” to agree on this among themselves).
Frankly, it is somewhat discouraging that the National Standard was not introduced in conjunction with other related national standards, but directly refers to foreign standards, albeit adopted by reputable international organizations.
Let me remind you that, according to paragraph 3 of Article 26 of the Federal Law “On Standardization in the Russian Federation”, “the application of a national standard is mandatory for the manufacturer and (or) the contractor in the case of a public statement on the conformity of products to the national standard, including in the case of applying the national designation standard in labeling, in operational or other documentation, and (or) labeling of products with a sign of the national standardization system. ”
In other words, the customer prescribing the requirement to follow this standard in his Terms of Reference obliges both the contractor and himself to follow not only domestic GOSTs, but also a whole bunch of international standards, in a package with which the ISO / IEC / IEEE 42010 standard was adopted at one time : 2011. And if the requirements of GOSTs conflict with international standards, it is necessary to follow the requirements of international standards. What will happen if their text is changed, the authors of the "hundred" are silent.
Terrifying translation of terms. For example, the “framework” in the translation turned into a “structure”, losing its original meaning: the term “structure” refers more to the template of a certain document, and the term “framework” is more often understood as a base, a frame. What is it, in fact, and is in accordance with ISO / IEC / IEEE 42010: 2011. Indeed, this standard does not describe the structure of architecture, but approaches, principles and practices that can be used as a basis for describing architecture.
The term “concern” turned into “interest”, and everything would be fine if it were not for the decoding in “weave”: it turns out that interest is “benefit or problems in the system related to one or more interested parties”. In the original, it looked like this: "concern (system) - interest in a system relevant to one or more of its stakeholders." Where did the GOST authors get the problems for their definition?
In general, in my opinion, it is impossible to use the text of GOST R 57100-2016 in the form that is submitted to us by its authors. Use the original text of ISO / IEC / IEEE 42010: 2011.
And avoid specifying GOST in your documents, this only imposes additional obligations on you under the law. However, you will not receive any dividends. It’s better to refer to the ISO right away.
PS No, I am not at all against the approaches outlined in the ISO / IEC / IEEE 42010: 2011 standard, do not get me wrong. I myself always use these approaches. But you must admit that you expect more from the National Standard than just an unprofessional translation of the text of the international standard.
No one is even going to hide the fact that behind GOST R there is a completely non-guest approach, described in ISO / IEC / IEEE 42010: 2011 Systems and software engineering - Architecture description. Moreover, this approach is not Gost's from the word at all, because GOST R 57100-2016 is not only in no way connected with any GOST, but also introduces its own philosophy, which is alien to the traditional GOST (I will not speak about the quality of the text of the standard, because there’s even a link to other standards are given either in Russian “ISO / IEC 10746”, or in English “ISO 15704” - apparently, it was difficult for the authors of “hundred” to agree on this among themselves).
Frankly, it is somewhat discouraging that the National Standard was not introduced in conjunction with other related national standards, but directly refers to foreign standards, albeit adopted by reputable international organizations.
Let me remind you that, according to paragraph 3 of Article 26 of the Federal Law “On Standardization in the Russian Federation”, “the application of a national standard is mandatory for the manufacturer and (or) the contractor in the case of a public statement on the conformity of products to the national standard, including in the case of applying the national designation standard in labeling, in operational or other documentation, and (or) labeling of products with a sign of the national standardization system. ”
In other words, the customer prescribing the requirement to follow this standard in his Terms of Reference obliges both the contractor and himself to follow not only domestic GOSTs, but also a whole bunch of international standards, in a package with which the ISO / IEC / IEEE 42010 standard was adopted at one time : 2011. And if the requirements of GOSTs conflict with international standards, it is necessary to follow the requirements of international standards. What will happen if their text is changed, the authors of the "hundred" are silent.
Terrifying translation of terms. For example, the “framework” in the translation turned into a “structure”, losing its original meaning: the term “structure” refers more to the template of a certain document, and the term “framework” is more often understood as a base, a frame. What is it, in fact, and is in accordance with ISO / IEC / IEEE 42010: 2011. Indeed, this standard does not describe the structure of architecture, but approaches, principles and practices that can be used as a basis for describing architecture.
The term “concern” turned into “interest”, and everything would be fine if it were not for the decoding in “weave”: it turns out that interest is “benefit or problems in the system related to one or more interested parties”. In the original, it looked like this: "concern (system) - interest in a system relevant to one or more of its stakeholders." Where did the GOST authors get the problems for their definition?
In general, in my opinion, it is impossible to use the text of GOST R 57100-2016 in the form that is submitted to us by its authors. Use the original text of ISO / IEC / IEEE 42010: 2011.
And avoid specifying GOST in your documents, this only imposes additional obligations on you under the law. However, you will not receive any dividends. It’s better to refer to the ISO right away.
PS No, I am not at all against the approaches outlined in the ISO / IEC / IEEE 42010: 2011 standard, do not get me wrong. I myself always use these approaches. But you must admit that you expect more from the National Standard than just an unprofessional translation of the text of the international standard.