IS/ISO/IEC/IEEE 42010 : 2022 Software, Systems and Enterprise - Architecture Description
NATIONAL FOREWORD
This Indian Standard (First Revision) which is identical to ISO/IEC/IEEE 42010 : 2022 'Software, systems and enterprise - Architecture description' issued by the International Organization for Standardization and International Electrotechnical Commission was adopted by the Bureau of Indian Standards on the recommendation of the Software and System Engineering Sectional Committee, and approval of the Electronics and Information Technology Division Council.
This Standard was first published in 2018 and was identical to ISO/IEC/IEEE 42010 : 2011. This revision of this standard aligns this Indian Standard with latest version of ISO/IEC/IEEE 42010 : 2022.
The main changes are as follows:
a) The term used to refer to the subject of an architecture description is changed from 'system of interest' to 'entity of interest' (EoI) to be compatible with IS/ISO/IEC/IEEE 42020 and IS/ISO/IEC/IEEE 42030 standards and to allow for its application in non-system architecture situations. The term 'entity' is also used in this document when entities are considered as surrounding things in an environment of an EoI;
b) The term 'architecture description framework'(ADF) replaces 'architecture framework' in the previous edition. It is defined in order to differentiate ADFs from other kinds of architecting frameworks like architecture evaluation frameworks specified in IS/ISO/IEC/IEEE 42030;
c) Architecture description element, introduced in the 2011 edition(see IS/ISO/IEC/IEEE 42010 : 2011, 4.2.6, 5.7 and A.6) is now defined in 3 as identified or named part of an architecture description allowing representing at least stakeholders, concerns, perspectives, and aspects identified in an AD, and views, view components, viewpoints, and model kinds included in an AD;
d) Aspect and stakeholder perspective concepts ¯ Already introduced in the 2011 edition (see 3.5, Note 1 of 5.6, Annex A and B) are defined and described to accommodate current practice where these ideas are prevalent;
e) A correspondence defines an identified or named relation between AD elements, as in 4.2.6 of the 2011 edition. But, to clarify the relationship between AD and correspondence, a Note 1 to the definition is added to state that for the purpose of correspondences, an architecture description can be considered as an AD element in another architecture description. This correspondence between ADs is necessary because an architecture can be described by more than one AD and these alternatives of architectures have related for activities like tradeoff analysis and decision making;
f) The term 'architecture view component' is introduced as a separable portion of one or more Architecture views, replacing 'architecture model' in the 2011 edition. This change is to account for the fact that some parts of a view are model-based while others may not be. View components can be derived from an information source, which can sometimes be a model;
g) Model-based view components are governed by model kinds and documented by legends. Nonmodel-based view components are documented by legends;
h) Model kinds are identified as a new conformance case to encourage model-based architecting;
j) The concept of architecture viewpoint is updated to accommodate current practice where a View point governs one or more architecture views within an AD;
k) The definition of 'model kind' given by the 2011 edition is extended to include categories of models as used by ADF like UAF;
m) The figures use an informal entity-relationship diagram notation replacing UML class diagrams in the 2011 edition, to facilitate comprehension by users of this document. The multiplicities of the relationships are explained in the text when necessary;
n) Annex E illustrates a few concepts pertaining to architecture life cycles and architecture description life cycles; and
p) Annex F shows examples of how some architecture description frameworks can conform to requirements of this document.
The text of ISO/IEC standard has been approved as suitable for publication as an Indian Standard without deviations. Certain conventions are however not identical to those used in Indian Standards. Attention is particularly drawn to the following:
a) Wherever the words 'International Standard' appears referring to this standard, they should be read as 'Indian Standard'; and
b) Comma (,) has been used as a decimal marker while in Indian Standards, the current practice is to use a point (.) as the decimal marker.