ISO/IEC 42010

ISO/IEC 42010
Title	ISO/IEC 42010
Status	Published
Year	2011
Organization	International Organization for Standardization, International Electrotechnical Commission
Domain	Systems and software architecture

ISO/IEC 42010 ISO/IEC 42010 is an international standard for architecture descriptions of systems and software, providing a framework for documenting, communicating, and governing architectures across disciplines. It establishes concepts, conventions, and requirements intended to align stakeholders, viewpoints, and concerns in complex projects spanning industrial, governmental, and academic sectors. The standard informs practices used by organizations such as IBM, Microsoft, Siemens, NASA, and European Space Agency in concert with bodies like IEEE and The Open Group.

Overview

ISO/IEC 42010 defines requirements for architecture descriptions that support decision-making among stakeholders such as Project Management Institute, Department of Defense (United States), European Commission, World Health Organization, and United Nations agencies acting in systems engineering programs. It formalizes the use of stakeholders and concerns found in work by Barbara Liskov, Edgar F. Codd, Grady Booch, Ivar Jacobson, and James Rumbaugh influencing modeling practices alongside notations like Unified Modeling Language and organizations like Object Management Group. The standard interacts with methodologies promoted by PRINCE2, Agile Alliance, SAFe, and CMMI adopters across large-scale initiatives.

Scope and Purpose

The purpose of the standard is to ensure that architecture descriptions are consistent, repeatable, and useful across contexts including aerospace programs overseen by European Space Agency and NASA, telecommunications projects led by ITU-T and 3GPP, and infrastructure undertakings involving World Bank funding or Asian Development Bank oversight. It scopes the practice of creating architecture descriptions that capture stakeholder concerns for systems delivered by companies such as Boeing, Airbus, Lockheed Martin, and Raytheon Technologies. The standard aims to enable traceability and governance compatible with legal frameworks like Sarbanes–Oxley Act, General Data Protection Regulation, and procurement rules used by United States Department of Defense.

Key Concepts and Terminology

Key concepts include stakeholders, concerns, viewpoints, models, architecture descriptions, and correspondences; these notions echo prior work by John Zachman and Simon S. Peyton Jones. Stakeholders may be roles from organizations such as National Institute of Standards and Technology, European Medicines Agency, Food and Drug Administration, and Transport for London. Viewpoints reference modeling concerns addressed using languages related to Unified Modeling Language, Systems Modeling Language, and taxonomies used by ISO committees and IEC technical groups. Terminology aligns with systems engineering sources like INCOSE and historical architectures seen in projects run by Bell Labs and AT&T.

Architecture Description Framework

The architecture description framework in the standard prescribes how to define viewpoints that produce views addressing concerns expressed by stakeholders such as those in United Kingdom Ministry of Defence, Australian Department of Defence, and Canadian Armed Forces. It defines rules for correspondences among model elements similar to practices in TOGAF and modeling ecosystems maintained by The Open Group. The framework supports architectural rationale used in programs by NASA, European Space Agency, CERN, and Large Hadron Collider collaborations, and supports tool interoperability with platforms from IBM Rational, Sparx Systems, Atlassian, and Microsoft Azure DevOps.

Compliance and Conformance

Conformance clauses specify requirements for architecture description contents, the use of viewpoints, and traceability mechanisms relevant to certification regimes such as those from Underwriters Laboratories and Det Norske Veritas. Organizations seeking alignment include ISO member bodies and industry consortia like IEEE Computer Society and IETF, which often reference these conformance practices in procurements involving European Investment Bank or national procurement agencies. Auditing and assessment may draw on processes used by KPMG, Deloitte, PricewaterhouseCoopers, and Ernst & Young for governance and risk assurance.

History and Development

ISO/IEC 42010 evolved from national and international efforts in the late 20th and early 21st centuries influenced by practitioners at Carnegie Mellon University, Massachusetts Institute of Technology, Stanford University, and Imperial College London. It consolidates ideas from the Zachman Framework, IEEE 1471 and community input from stakeholders including The Open Group, Object Management Group, and academia represented by conferences such as International Conference on Software Engineering and Architecting Critical Systems. Revisions and maintenance involve working groups within ISO/IEC JTC 1 and liaison with professional bodies like INCOSE and ACM.

Related Standards and Applications

ISO/IEC 42010 relates to standards such as ISO 12207, ISO 15288, ISO/IEC 24765, and industry specifications like TOGAF, CMMI, and IEEE 1471 predecessors, and it is applied in sectors overseen by ICAO, IMO, European Medicines Agency, and Federal Aviation Administration. Practical applications include enterprise architecture practice at Goldman Sachs, Walmart, and Procter & Gamble; infrastructure projects funded by European Investment Bank and World Bank; and defense systems delivered to agencies like NATO and United States Department of Defense. The standard underpins academic curricula at institutions such as Massachusetts Institute of Technology, University of California, Berkeley, and University of Oxford.

Category:ISO standards