ISO IEC IEEE 42010-2011 Systems and software engineering - Architecture description《系统和软件工程 架构描述》.pdf

1、 Reference number ISO/IEC/IEEE 42010:2011(E) ISO/IEC 2011 IEEE 2011INTERNATIONAL STANDARD ISO/IEC/ IEEE 42010 First edition 2011-12-01 Systems and software engineering Architecture description Ingnierie des systmes et des logiciels Description de larchitectureISO/IEC/IEEE 42010:2011(E) COPYRIGHT PRO

2、TECTED DOCUMENT ISO/IEC 2011 IEEE 2011 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO or IEEE at the

3、respective address below. ISO copyright office Institute of Electrical and Electronics Engineers, Inc. Case postale 56 CH-1211 Geneva 20 3 Park Avenue, New York NY 10016-5997, USA Tel. + 41 22 749 01 11 E-mail stds.iprieee.org Fax + 41 22 749 09 47 Web www.ieee.org E-mail copyrightiso.org Web www.is

4、o.org Published in Switzerland ii ISO/IEC 2011 All rights reserved IEEE 2011 All rights reservedISO/IEC/IEEE 42010:2011(E) ISO/IEC 2011 All rights reserved IEEE 2011 All rights reserved iiiContents Page Foreword iv Introduction . v 1 Scope 1 2 Conformance . 1 3 Terms and definitions . 1 4 Conceptual

5、 foundations . 3 4.1 Introduction 3 4.2 Conceptual model of architecture description . 3 4.3 Architecting in the life cycle . 8 4.4 Uses of architecture descriptions . 8 4.5 Architecture frameworks and architecture description languages . 9 5 Architecture descriptions . 11 5.1 Introduction 11 5.2 Ar

6、chitecture description identification and overview . 12 5.3 Identification of stakeholders and concerns 12 5.4 Architecture view points 13 5.5 Architecture views . 13 5.6 Architecture models 13 5.7 Architecture relations . 14 5.8 Architecture rationale . 15 6 Architecture frameworks and architecture

7、 description languages . 16 6.1 Architecture frameworks 16 6.2 Adherence of an architecture description to an architecture framework . 17 6.3 Architecture description languages 17 7 Architecture view points 17 Annex A (informative) Notes on terms and concepts . 19 Annex B (informative) Guide to arch

8、itecture viewpoints . 27 Annex C (informative) Relationship to other standards . 31 Bibliography 35 ISO/IEC/IEEE 42010:2011(E) iv ISO/IEC 2011 All rights reserved IEEE 2011 All rights reservedForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnica

9、l Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activi

10、ty. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non- governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical commit

11、tee, ISO/IEC JTC 1. IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National Stand

12、ards Institute, which brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the

13、consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the information contained in its standards. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of ISO/IEC JTC 1 is to p

14、repare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is called to the possibili

15、ty that implementation of this standard may require the use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. ISO/IEEE is not responsible for identifying essential

16、patents or patent claims for which a license may be required, for conducting inquiries into the legal validity or scope of patents or patent claims or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance or a Patent Statement and Licen

17、sing Declaration Form, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further informa

18、tion may be obtained from ISO or the IEEE Standards Association. ISO/IEC/IEEE 42010 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering, in cooperation with the Software and Systems Engineering Standards Committee of th

19、e Computer Society of the IEEE, under the Partner Standards Development Organization cooperation agreement between ISO and IEEE. This first edition of ISO/IEC/IEEE 42010 cancels and replaces ISO/IEC 42010:2007, which has been technically revised. ISO/IEC/IEEE 42010:2011(E) ISO/IEC 2011 All rights re

20、served IEEE 2011 All rights reserved vIntroduction The complexity of man-made systems has grown to an unprecedented level. This has led to new opportunities, but also to increased challenges for the organizations that create and utilize systems. Concepts, principles and procedures of architecting ar

21、e increasingly applied to help manage the complexity faced by stakeholders of systems. Conceptualization of a systems architecture, as expressed in an architecture description, assists the understanding of the systems essence and key properties pertaining to its behaviour, composition and evolution,

22、 which in turn affect concerns such as the feasibility, utility and maintainability of the system. Architecture descriptions are used by the parties that create, utilize and manage modern systems to improve communication and co-operation, enabling them to work in an integrated, coherent fashion. Arc

23、hitecture frameworks and architecture description languages are being created as assets that codify the conventions and common practices of architecting and the description of architectures within different communities and domains of application. This International Standard addresses the creation, a

24、nalysis and sustainment of architectures of systems through the use of architecture descriptions. This International Standard provides a core ontology for the description of architectures. The provisions of this International Standard serve to enforce desired properties of architecture descriptions.

25、 This International Standard also specifies provisions that enforce desired properties of architecture frameworks and architecture description languages (ADLs), in order to usefully support the development and use of architecture descriptions. This International Standard provides a basis on which to

26、 compare and integrate architecture frameworks and ADLs by providing a common ontology for specifying their contents. This International Standard can be used to establish a coherent practice for developing architecture descriptions, architecture frameworks and architecture description languages with

27、in the context of a life cycle and its processes (not defined by this International Standard). This International Standard can further be used to assess conformance of an architecture description, of an architecture framework, of an architecture description language, or of an architecture viewpoint

28、to its provisions. Users of this International Standard are advised to consult Clause 4 to gain appreciation of the provided ontology, its concepts and principles. INTERNATIONAL STANDARD ISO/IEC/IEEE 42010:2011(E) ISO/IEC 2011 All rights reserved IEEE 2011 All rights reserved 1Systems and software e

29、ngineering Architecture description 1 Scope This International Standard specifies the manner in which architecture descriptions of systems are organized and expressed. This International Standard specifies architecture viewpoints, architecture frameworks and architecture description languages for us

30、e in architecture descriptions. This International Standard also provides motivations for terms and concepts used; presents guidance on specifying architecture viewpoints; and demonstrates the use of this International Standard with other standards. 2 Conformance The requirements in this Internation

31、al Standard are contained in Clauses 5, 6 and 7. There are four situations in which claims of conformance with the provisions of this International Standard can be made. When conformance is claimed for an architecture description, the claim shall demonstrate that the architecture description meets t

32、he requirements listed in Clause 5. When conformance is claimed for an architecture viewpoint, the claim shall demonstrate that the architecture viewpoint meets the requirements listed in Clause 7. When conformance is claimed for an architecture framework, the claim shall demonstrate that the archit

33、ecture framework meets the requirements listed in 6.1. When conformance is claimed for an architecture description language, the claim shall demonstrate that the architecture description language meets the requirements listed in 6.3. Requirements of this International Standard are marked by the use

34、of the verb “shall”. Recommendations are marked by the use of the verb “should”. Permissions are marked by the use of the verb “may”. In the event of a conflict between normative figures and text, the text takes precedence. Please report any apparent conflicts. NOTE This International Standard is de

35、signed such that “tailoring” is neither required nor permitted for its use when claims of conformance are made. 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 architecting process of conceiving, defining, expressing, documenting, communicati

36、ng, certifying proper implementation of, maintaining and improving an architecture throughout a systems life cycle ISO/IEC/IEEE 42010:2011(E) 2 ISO/IEC 2011 All rights reserved IEEE 2011 All rights reservedNOTE Architecting takes place in the context of an organization (“person or a group of people

37、and facilities with an arrangement of responsibilities, authorities and relationships”) and/or a project (“endeavour with defined start and finish criteria undertaken to create a product or service in accordance with specified resources and requirements”) ISO/IEC 12207, ISO/IEC 15288. 3.2 architectu

38、re system fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution 3.3 architecture description AD work product used to express an architecture 3.4 architecture framework conventions, principles and p

39、ractices for the description of architectures established within a specific domain of application and/or community of stakeholders EXAMPLE 1 Generalised Enterprise Reference Architecture and Methodologies (GERAM) ISO 15704 is an architecture framework. EXAMPLE 2 Reference Model of Open Distributed P

40、rocessing (RM-ODP) ISO/IEC 10746 is an architecture framework. 3.5 architecture view work product expressing the architecture of a system from the perspective of specific system concerns 3.6 architecture viewpoint work product establishing the conventions for the construction, interpretation and use

41、 of architecture views to frame specific system concerns 3.7 concern system interest in a system relevant to one or more of its stakeholders NOTE A concern pertains to any influence on a system in its environment, including developmental, technological, business, operational, organizational, politic

42、al, economic, legal, regulatory, ecological and social influences. 3.8 environment system context determining the setting and circumstances of all influences upon a system NOTE The environment of a system includes developmental, technological, business, operational, organizational, political, econom

43、ic, legal, regulatory, ecological and social influences. 3.9 model kind conventions for a type of modelling NOTE Examples of model kinds include data flow diagrams, class diagrams, Petri nets, balance sheets, organization charts and state transition models. 3.10 stakeholder system individual, team,

44、organization, or classes thereof, having an interest in a system ISO/IEC/IEEE 42010:2011(E) ISO/IEC 2011 All rights reserved IEEE 2011 All rights reserved 34 Conceptual foundations 4.1 Introduction This clause introduces the conceptual foundations of architecture description comprising a conceptual

45、model of architecture description (see 4.2); the role of architecting in the life cycle (see 4.3); uses of architecture descriptions (see 4.4); and architecture frameworks and architecture description languages (see 4.5). The concepts introduced in this clause are used in Clauses 5 through 7 to expr

46、ess requirements. NOTE Annex A provides further discussion of the terms and concepts used in this International Standard and presents examples of their use. 4.2 Conceptual model of architecture description 4.2.1 Context of architecture description Figure 1 depicts key concepts pertaining to systems

47、and their architectures as a context for understanding the practice of architecture description. NOTE The figure uses the conventions for class diagrams defined in ISO/IEC 19501. Figure 1 Context of architecture description The term system is used in this International Standard to refer to entities

48、whose architectures are of interest. The term is intended to encompass, but is not limited to, entities within the following domains: systems as described in ISO/IEC 15288: “systems that are man-made and may be configured with one or more of the following: hardware, software, data, humans, processes

49、 (e.g., processes for providing service to users), procedures (e.g. operator instructions), facilities, materials and naturally occurring entities”; software products and services as described in ISO/IEC 12207; ISO/IEC/IEEE 42010:2011(E) 4 ISO/IEC 2011 All rights reserved IEEE 2011 All rights reserved software-intensive systems as described in IEEE Std 1471:2000: “any system where software contributes essential inuences to the design, construction, deployment, and evo