IEEE 42010-2011 en Systems and software engineering Architecture description.pdf

1、 Reference numberISO/IEC/IEEE 42010:2011(E)ISO/IEC 2011IEEE 2011INTERNATIONAL STANDARD ISO/IEC/IEEE42010First edition2011-12-01Systems and software engineering Architecture description Ingnierie des systmes et des logiciels Description de larchitectureISO/IEC/IEEE 42010:2011(E) COPYRIGHT PROTECTED D

2、OCUMENT 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 respecti

3、ve address below. ISO copyright office Institute of Electrical and Electronics Engineers, Inc. Case postale 56 g120 CH-1211 Geneva 20 3 Park Avenue, New York g120 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.

4、iso.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 ivg3Introduction . vg31g3 Scope 1g32g3 Conformance . 1g33g3 Terms and definitions . 1g

5、34g3 Conceptual foundations . 3g34.1g3 Introduction 3g34.2g3 Conceptual model of architecture description . 3g34.3g3 Architecting in the life cycle . 8g34.4g3 Uses of architecture descriptions . 8g34.5g3 Architecture frameworks and architecture description languages . 9g35g3 Architecture description

6、s . 11g35.1g3 Introduction 11g35.2g3 Architecture description identification and overview . 12g35.3g3 Identification of stakeholders and concerns 12g35.4g3 Architecture viewpoints 13g35.5g3 Architecture views . 13g35.6g3 Architecture models 13g35.7g3 Architecture relations . 14g35.8g3 Architecture r

7、ationale . 15g36g3 Architecture frameworks and architecture description languages . 16g36.1g3 Architecture frameworks 16g36.2g3 Adherence of an architecture description to an architecture framework . 17g36.3g3 Architecture description languages 17g37g3 Architecture viewpoints 17g3Annex A (informativ

8、e) Notes on terms and concepts . 19g3Annex B (informative) Guide to architecture viewpoints . 27g3Annex C (informative) Relationship to other standards . 31g3Bibliography 35g3ISO/IEC/IEEE 42010:2011(E) iv ISO/IEC 2011 All rights reserved IEEE 2011 All rights reservedForeword ISO (the International O

9、rganization for Standardization) and IEC (the International Electrotechnical 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

10、 respective organization to deal with particular fields of technical activity. 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 inf

11、ormation technology, ISO and IEC have established a joint technical committee, 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 throug

12、h a consensus development process, approved by the American National Standards 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

13、 administers the process and establishes rules to promote fairness in the 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

14、 in the ISO/IEC Directives, Part 2. The main task of ISO/IEC JTC 1 is to prepare 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 % o

15、f the national bodies casting a vote. Attention is called to the possibility 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 co

16、nnection therewith. ISO/IEEE is not responsible for identifying essential 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 connectio

17、n with submission of a Letter of Assurance or a Patent Statement and Licensing 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 infringe

18、ment of such rights, is entirely their own responsibility. Further information 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 coope

19、ration with the Software and Systems Engineering Standards Committee of the 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

20、technically revised. ISO/IEC/IEEE 42010:2011(E) ISO/IEC 2011 All rights reserved 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 a

21、nd utilize systems. Concepts, principles and procedures of architecting are 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

22、and key properties pertaining to its behaviour, composition and evolution, 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 c

23、o-operation, enabling them to work in an integrated, coherent fashion. Architecture 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 dom

24、ains of application. This International Standard addresses the creation, analysis 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

25、Standard serve to enforce desired properties of architecture descriptions. 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 architect

26、ure descriptions. This International Standard provides a basis on which to 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 descrip

27、tions, architecture frameworks and architecture description languages within 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,

28、 of an architecture description language, or of an architecture viewpoint 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

29、 All rights reserved IEEE 2011 All rights reserved 1Systems and software engineering 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 viewpoi

30、nts, architecture frameworks and architecture description languages for use 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 Standar

31、d with other standards. 2 Conformance The requirements in this International 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. g127 When conformance is claimed for an architecture des

32、cription, the claim shall demonstrate that the architecture description meets the requirements listed in Clause 5. g127 When conformance is claimed for an architecture viewpoint, the claim shall demonstrate that the architecture viewpoint meets the requirements listed in Clause 7. g127 When conforma

33、nce is claimed for an architecture framework, the claim shall demonstrate that the architecture framework meets the requirements listed in 6.1. g127 When conformance is claimed for an architecture description language, the claim shall demonstrate that the architecture description language meets the

34、requirements listed in 6.3. Requirements of this International Standard are marked by the use 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

35、takes precedence. Please report any apparent conflicts. NOTE This International Standard is designed 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

36、 apply. 3.1 architecting process of conceiving, defining, expressing, documenting, communicating, 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 reserved

37、NOTE Architecting takes place in the context of an organization (“person or a group of people 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 accor

38、dance with specified resources and requirements”) ISO/IEC 12207, ISO/IEC 15288. 3.2 architecture g162systemg178 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

39、 work product used to express an architecture 3.4 architecture framework conventions, principles and practices for the description of architectures established within a specific domain of application and/or community of stakeholders EXAMPLE 1 Generalised Enterprise Reference Architecture and Methodo

40、logies (GERAM) ISO 15704 is an architecture framework. EXAMPLE 2 Reference Model of Open Distributed Processing (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 archite

41、cture viewpoint work product establishing the conventions for the construction, interpretation and use of architecture views to frame specific system concerns 3.7 concern g162systemg178 interest in a system relevant to one or more of its stakeholders NOTE A concern pertains to any influence on a sys

42、tem in its environment, including developmental, technological, business, operational, organizational, political, economic, legal, regulatory, ecological and social influences. 3.8 environment g162systemg178 context determining the setting and circumstances of all influences upon a system NOTE The e

43、nvironment of a system includes developmental, technological, business, operational, organizational, political, economic, 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, P

44、etri nets, balance sheets, organization charts and state transition models. 3.10 stakeholder g162systemg178 individual, team, 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 found

45、ations 4.1 Introduction This clause introduces the conceptual foundations of architecture description comprising a conceptual 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 an

46、d architecture description languages (see 4.5). The concepts introduced in this clause are used in Clauses 5 through 7 to express 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 mo

47、del of architecture description 4.2.1 Context of architecture description Figure 1 depicts key concepts pertaining to systems 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 19

48、501. Figure 1 Context of architecture description The term system is used in this International Standard to refer to entities whose architectures are of interest. The term is intended to encompass, but is not limited to, entities within the following domains: g127 systems as described in ISO/IEC 152

49、88: “systems that are man-made and may be configured with one or more of the following: hardware, software, data, humans, processes (e.g., processes for providing service to users), procedures (e.g. operator instructions), facilities, materials and naturally occurring entities”; g127 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 reservedg127 software-intensive systems as described in IEEE Std 1471:2000