BS ISO/IEC 42010 offers recommended practice in the creation, analysis and sustainment of system architectures where software contributes essential influences to their design, construction, deployment and evolution.
It is intended to reflect generally accepted trends and provide a technical framework for further work in this area. The standard also defines the content of an architectural description and features annexes providing rationale for key concepts, terminology, how the standard relates to others, and examples of usage.
This includes architectural descriptions that are used for the following:
- Expression of the system and its evolution
- Communication among the system stakeholders
- Evaluation and comparison of architectures in a consistent manner
- Planning, managing, and executing the activities of system development
- Expression of the persistent characteristics and supporting principles of a system to guide acceptable change
- Verification of a system implementation’s compliance with an architectural description
- Recording contributions to the body of knowledge of software-intensive systems architecture
Who would use this standard?
It would be particular interest to system owners and developers, and other users including those involved in enterprise-wide infrastructure activities spanning multiple developments, including the following:
- System users, owners, and acquirers (or clients)
- Those that develop, describe, and document architectures (architects)
- Those that develop, deliver, and maintain the system (architects, designers, programmers, maintainers, testers, domain engineers, quality assurance staff, configuration management staff, suppliers, and project managers or developers)
- Anyone who oversee and evaluate systems and their development (chief information officers, auditors, and independent assessors)
Other users of this recommended practice comprises those involved in the enterprise-wide infrastructure activities that span multiple system developments, including methodologists, process and process-improvement engineers, researchers, producers of standards, tool builders, and trainers.
Contents of BS ISO/IEC 42010 includes:
Overview
Scope
Purpose
Intended users
Conformance to this recommended practice
References
Definitions
Conceptual framework
Architectural description in context
Stakeholders and their roles
Architectural activities in the life cycle
Uses of architectural descriptions
Architectural description practices
Architectural documentation
Identification of stakeholders and concerns
Selection of architectural viewpoints
Architectural views
Consistency among architectural views
Architectural rationale
Example use
Bibliography
Notes on terminology
Examples of viewpoints
Relationship to other standards
