Path: Home > GB/T > Page216 > GB/T 45630-2025 Home > Standard_List > GB/T > Page216 > GB/T 45630-2025
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 45630-2025 | English | 1494 |
Add to Cart
|
9 days [Need to translate]
|
Systems and software engineering - Architecture description
| Valid |
GB/T 45630-2025
|
PDF similar to GB/T 45630-2025
Basic data | Standard ID | GB/T 45630-2025 (GB/T45630-2025) | | Description (Translated English) | Systems and software engineering - Architecture description | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | L77 | | Classification of International Standard | 35.080 | | Word Count Estimation | 74,726 | | Date of Issue | 2025-04-25 | | Date of Implementation | 2025-11-01 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 45630-2025: Systems and software engineering - Architecture description---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
ICS 35.080
CCSL77
National Standard of the People's Republic of China
System and software engineering architecture description
Released on 2025-04-25
2025-11-01 Implementation
State Administration for Market Regulation
The National Standardization Administration issued
Table of contents
Preface III
Introduction IV
1 Scope 1
2 Normative references 1
3 Terms and Definitions 1
4 Compliance 4
5 Basic Concepts 4
6 Architecture Description Specification 15
7 Architecture Description Framework and Architecture Description Language 20
8 Architecture perspectives and model types 21
Appendix A (Informative) Notes on terms and concepts 23
Appendix B (Informative) Architecture Perspective Specification Guidelines 32
Appendix C (Informative) Relationship with other standards 35
Appendix D (Informative) Use of Architecture Descriptions 41
Appendix E (Informative) Life Cycle of Architecture and Architecture Description 42
Appendix F (Informative) Architecture Description Framework 44
Appendix NA (Informative) Architecture description of an industry energy service system application case 47
Appendix NB (Informative) Application Case of TOGAF-based Architecture Description Framework 55
References 64
Foreword
This document is in accordance with the provisions of GB/T 1.1-2020 "Guidelines for standardization work Part 1.Structure and drafting rules for standardization documents"
Drafting.
This document is equivalent to ISO /IEC /IEEE42010.2022 "Software, System and Enterprise Architecture Description".
The following minimal editorial changes were made to this document.
a) To coordinate with existing standardization documents, the name of the standard is changed to "System and Software Engineering Architecture Description";
b) Corrected the reference number error in 5.1 of ISO /IEC /IEEE42010.2022, changing "5.4.3" to "5.4.4";
c) Corrected the reference number error in 5.2.2 of ISO /IEC /IEEE42010.2022, changing "5.2.10" to "5.2.9";
d) Corrected the formatting errors of 7.1.1 and 7.1.2 in ISO /IEC /IEEE42010.2022 and adjusted them to paragraph format;
e) Corrected the reference number error in Note 1 of 8.1 of ISO /IEC /IEEE42010.2022, changing "e)" to "d)";
f) Corrected the reference number error in B.2.5 of ISO /IEC /IEEE42010.2022, changing "b)" to "a)";
g) Corrected the reference error in C.4 of ISO /IEC /IEEE42010.2022, changing "latter" to "former";
h) To facilitate readers’ understanding, notes are added to A.5, C.5 and C.6 respectively;
i) Added Appendix NA (informative) and Appendix NB (informative) to enhance the application effect of the standard.
Please note that some of the contents of this document may involve patents. The issuing organization of this document does not assume the responsibility for identifying patents.
This document was proposed and coordinated by the National Information Technology Standardization Technical Committee (SAC/TC28).
This document was drafted by. Guangxi Dayi Technology Co., Ltd., Shenzhen CESI Information Technology Co., Ltd., China Electronics Technology Standardization Research Institute
Institute, Guangdong Yian Civil Air Defense Engineering Technology Co., Ltd., Ansem Asia Pacific Technology Co., Ltd., Beijing University of Technology, Guangxi Academy of Sciences, Zhongkong Technology
Technology Co., Ltd., Yunnan Power Grid Co., Ltd. Information Center, Inspur Software Technology Co., Ltd., Nanjing Youce Information Technology Co., Ltd.
Ltd., Lingyu Framework (Beijing) Software Co., Ltd., Beijing Nantian Software Co., Ltd., National Application Software Product Quality Inspection and Testing Center, Jiangsu
CESI Technology Development Co., Ltd., Runjian Co., Ltd., China Academy of Space Systems Science and Engineering, CRRC Dalian Electric Traction R&D
Center Co., Ltd., Xi'an Jiaotong University, Southwest Computer Co., Ltd., Chongqing Software Evaluation Center Co., Ltd., Beijing High-quality System
Technology Co., Ltd., Shandong Chuangen Information Technology Co., Ltd., University of Science and Technology Beijing, Shandong Zhengzhong Information Technology Co., Ltd., Xiamen
Institute of Technology, Inspur General Software Co., Ltd., Northern University for Nationalities, Beijing Guqi Data Technology Co., Ltd., Beijing University of Aeronautics and Astronautics, Guangdong University of Science and Technology
Xixunchi Information Technology Co., Ltd., Guangyu Mingdao Digital Technology Co., Ltd., Sany Heavy Industry Co., Ltd., Changzhou Bowoer Intelligent Technology
Co., Ltd., Hangzhou Yike Information Technology Co., Ltd., Shenzhen Tonglifang Technology Co., Ltd., Hangzhou Zhicheng Huitong Technology Co., Ltd.,
CRRC Dalian Locomotive and Rolling Stock Co., Ltd., Shandong Shanke Digital Economy Research Institute Co., Ltd., and China Post Information Technology (Beijing) Co., Ltd.
The main drafters of this document are. Deng Zixian, Zhang Yangyang, Huang Jiayu, Liu Beichen, Wang Gongtao, Duan Haibo, Liu Xiaojian, Li Wenpeng, Chen Jiangyi,
Li Lingfan, Li Zhaochuan, You Huimin, Cao Rui, Dai Min, Lou Li, Zhang Xingxing, Xu Ming, Li Shulin, Liu Chenxi, An Dou, Huang Xiaorong, Ding Xiaoming, Yan Liang,
Lv Yingsheng, Zhang Hanwen, Wang Xi, Xu Zhiguo, Xiao Lei, Wu Bai, Han Qiang, Shi Long, Ai Jun, Hu Zhichao, Zhao Yinhua, Lin Xiangyi, Zhou Changhuai, Liu Yimeng,
Yang Xiaodong, Sun Dongmei, Zhang Yibin, Lin Yiwei, Pang Yili, Meng Qing, Chen Bei, Hao Lin, Hu Yongle, Yan Chenjing, Liu Yuan, Wang Lei, Liu Yao, Liu Yongliang,
Ma Xiaohong, Deng Rijie, Qie Yongjun, Li Hong, Xu Keqiang, Ding Ding, Li Xiaocun, Yang Xiliang, Jia Xibin, Li Gang, Li Chuanbo.
Introduction
The complexity of artificial entities has increased to unprecedented levels, creating new opportunities and increasing
Organizations, teams, and individuals are increasingly using architecture to help manage the complexity faced by their entity’s stakeholders.
Examples of entities include. enterprise, organization, solution, system (including software system), subsystem, process, business, data (as data
item or data structure), application, information technology (as a collection), task, product, service, software item, hardware item, product line, system
A family, a system of systems, a collection of systems, a collection of applications.
The architecture of an entity is expressed as one or more architectural descriptions (ADs), which help understand the underlying structure, behavior, design, and evolution of the entity.
concepts and attributes such as feasibility, utility, and maintainability, and the basis for physical development, operation, employment, external impacts, use, and decommissioning
concept.
Architectural descriptions are used by all parties who create, use, and manage artificial entities to improve communication and collaboration, enabling all parties, organizations, teams, and individuals to
Ability to work together in a coherent manner.
Note. ISO /IEC /IEEE 42020 specifies a set of architectural processes to support the creation of one or more architectural descriptions.
The process of architecture refinement is closely related to the creation of the architecture description.
An architectural description is a tangible work product, whereas an architecture is intangible, abstract, and understood through its concepts, properties, and principles.
The Architecture Description Framework (ADF) is used to describe conventions and common practices for writing architecture descriptions. The Architecture Description Language (ADL) is used to write different
Description of the architecture in population and application domains.
Architectural descriptions have many uses, such as design, development, documentation, analysis, evaluation, maintenance, risk mitigation, downstream user specifications, engineering
Specification, communication, planning, guidance, life cycle support, decision support, review, training, design verification, solution transaction research, cost
Comparison and analysis, etc., are used by a variety of stakeholders throughout the life cycle of their Entity of Interest (EoI).
More uses for architecture descriptions.
This document provides the terminology, definitions, and relationships for best practices in architectural descriptions. The terms of this document are used to define the expected characteristics of architectural descriptions.
This document also specifies the expected characteristics of an architecture description framework and an architecture description language to effectively support the development and use of architecture descriptions.
This document provides a common ontology for specifying the content of architecture description frameworks and architecture description languages.
It provides the basis for structured description language.
This document is applicable to the provision of architecture descriptions, architecture description frameworks, and architecture description languages within an organization in the context of an entity of interest or its architecture.
The terms of this document apply to the evaluation of architecture descriptions, architecture description frameworks, architecture description languages, visual
Conformity with the specifications of the corner and model types.
This document aims to enable a coherent set of approaches to describing architecture, including both document-centric and model-based techniques.
This document also gives motivation for the use of architecture-related terms and concepts in other documents such as guidelines and standards.
It is recommended that users of this document refer to Chapter 5 for an understanding of foundational concepts and concepts and principles related to the architecture description work product.
This document makes no claims about the completeness or correctness of specific elements included in the architectural description. However, it can be used to
The integrity and correctness of the architecture are checked locally, such as whether the established architecture description elements are consistent, whether the relationships are transitive, and whether the architecture description is consistent.
Whether the element is displayed in the view. It can also define a relationship between the same specific architecture description element and the architecture description.
Furthermore, specifications that appear as elements in an architectural description are expected to be complete, accurate, and
The subject is verified.
System and software engineering architecture description
1 Scope
This document specifies the structure and expression requirements of various entity architecture descriptions (ADs), including software, systems, enterprises, and systems between them.
Systems, system families, products (goods or services), product lines, service lines, technologies, and business domains.
This document defines the distinction between the architecture of an Entity of Interest (EoI) and the architectural description that expresses that architecture.
This document specifies requirements for the use of architectural concepts and their relationships as captured in architectural descriptions. It does not specify requirements for any entity of interest.
or the requirements of its environment.
This document specifies requirements for the Architecture Description Framework (ADF), Architecture Description Language (ADL), architectural perspectives, and model types to effectively
Support the development and use of architectural descriptions.
This document specifies conformance requirements for architecture descriptions, architecture description frameworks, architecture description languages, architecture perspectives, and model categories.
This document does not address processes, architectural methodologies, models, notations, techniques, or tools for creating, utilizing, or managing architectural descriptions.
This document does not specify any format or medium for recording architectural descriptions.
This document applies to.
a) fundamental concepts or properties that aid in understanding the structure, behavior, design, and evolution of various entities;
b) Develop architectural descriptions, architecture description frameworks, and architecture description languages within the organization in the context of the entity of interest or its architectures.
Establish coherent structured practice;
c) Evaluate the conformity of architecture descriptions, architecture description frameworks, architecture description languages, architecture perspectives, and model categories to specifications.
2 Normative references
This document has no normative references.
3 Terms and definitions
The following terms and definitions apply to this document.
The URLs for the standardization terminology databases maintained by ISO, IEC and IEEE are as follows.
---IEEE Online Standards Dictionary, https.//dictionary.ieee.org/.
NOTE For more terms and definitions in the field of systems and software engineering, see ISO /IEC /IEEE 24765.This standard is published periodically as part of the
3.1
Architecting
conceive, define, express, document, communicate, and demonstrate an architecture (3.2) throughout the life cycle of the entity (3.12) of interest
Its proper implementation, maintenance and improvement.
3.2
Architecture
The fundamental concepts or attributes of an entity in its environment (3.13), and the management of the realization and evolution of that entity and its associated life cycle processes
Price & DeliveryUS$1494.00 · In stock
Delivery: <= 9 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 45630-2025: Systems and software engineering - Architecture description
Status: Valid
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 45630-2025_English be delivered?Answer: Upon your order, we will start to translate GB/T 45630-2025_English as soon as possible, and keep you informed of the progress. The lead time is typically 6 ~ 9 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of GB/T 45630-2025_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 45630-2025_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay. |