BS ISO IEC 24744-2014 Software engineering Metamodel for development methodologies《软件工程 开发方法体系用元模型》.pdf

1、BSI Standards Publication BS ISO/IEC 24744:2014 Software engineering Metamodel for development methodologiesBS ISO/IEC 24744:2014 BRITISH STANDARD National foreword This British Standard is the UK implementation of ISO/IEC 24744:2014. It supersedes BS ISO/IEC 24744:2007+A1:2010 which is withdrawn. T

2、he UK participation in its preparation was entrusted to Technical Committee IST/15, Software and systems engineering. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a cont

3、ract. Users are responsible for its correct application. The British Standards Institution 2014. Published by BSI Standards Limited 2014 ISBN 978 0 580 82003 8 ICS 35.080 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was published under the a

4、uthority of the Standards Policy and Strategy Committee on 30 November 2014. Amendments issued since publication Date Text affectedBS ISO/IEC 24744:2014Reference number ISO/IEC 24744:2014(E) ISO/IEC 2014INTERNATIONAL STANDARD ISO/IEC 24744 Second edition 2014-11-15 Software engineering Metamodel for

5、 development methodologies Ingnierie du logiciel Mtamodle pour les mthodologies de dveloppement BS ISO/IEC 24744:2014 ISO/IEC 24744:2014(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2014 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise i

6、n any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case p

7、ostale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2014 All rights reservedBS ISO/IEC 24744:2014 ISO/IEC 24744:2014(E) ISO/IEC 2014 All rights reserved iiiContents Page Foreword . v Introduction vi 1 Sc

8、ope 1 2 Conformance . 1 3 Terms and definitions . 1 4 Naming, diagramming and definition conventions, and abbreviated terms . 3 4.1 Naming, diagramming and definition conventions 3 4.2 Abbreviations . 4 5 Basic Concepts 4 5.1 Method Engineering 5 5.2 Dual-Layer Modelling 5 5.3 Powertypes and Clabjec

9、ts 5 5.4 Uniting Process and Product . 6 5.5 Process Assessment 6 6 Introduction to the SEMDM 7 6.1 Highly Abstract View . 7 6.2 Abstract View and Core Classes . 7 6.3 Process Classes 8 6.4 Producer Classes 10 6.5 Product Classes 11 6.6 Connection between Process and Product 12 6.7 Support Classes 1

10、3 7 Metamodel Elements . 14 7.1 Classes . 14 7.2 Enumerated Types 61 8 Using the Metamodel 62 8.1 Usage Rules . 62 8.2 Usage Guidelines 63 9 Extending the Metamodel . 64 9.1 Extension Rules . 64 9.2 Extension Guidelines 65 Annex A (informative) Worked Example . 66 A.1 SimpleMethod Description . 66 A

11、.2 Construction of Process Components 66 A.3 Construction of Producer Components 68 A.4 Construction of Product Components 68 A.5 Connection Between Process and Product Components . 70 Annex B (informative) Mappings to Other Metamodelling Approaches 72 B.1 OMG SPEM 1.1 . 72 B.2 OOSPICE . 73 B.3 OPEN

12、 . 73 B.4 LiveNet 74 B.5 ISO/IEC 12207 and 15288 74 B.6 ISO/IEC 15504 (SPICE). 75 B.7 ISO/IEC 19501 (UML 1.4.2) 75 Annex C (informative) Graphical Notation 76 C.1 Introduction 76 BS ISO/IEC 24744:2014 ISO/IEC 24744:2014(E) iv ISO/IEC 2014 All rights reservedC.2 Notation Elements 77 C.3 Diagram Types

13、 88 C.4 Abbreviation Tables .94 Bibliography 96 Table of Figures Figure 1 The three areas of expertise, or domains, which act as a context for SEMDM. Arrows mean “is represented by“. . 4 Figure 2 Example of a powertype pattern and clabject. The Document class is partitioned by the DocumentKind power

14、type. The RequirementsSpecificationDocument class plus the rsd object represent a particular kind of document, making up a clabject. The rsd1 object represents a particular requirements specification document. 6 Figure 3 Highly abstract view of the SEMDM . 7 Figure 4 Abstract view of the SEMDM, show

15、ing the core classes in the metamodel 8 Figure 5 Work units . 9 Figure 6 Stages . 10 Figure 7 Producers . 11 Figure 8 Work product and modelling classes 12 Figure 9 Actions and constraints 13 Figure 10 Support classes 13 Figure C.1 A lifecycle diagram showing the temporal structure of a complete met

16、hod . 89 Figure C.2 A lifecycle diagram showing the content structure as well as the temporal structure of a method90 Figure C.3 An enactment diagram for the “Construction” phase kind of Figure C.2 91 Figure C.4 A dependency diagram based on a refinement of Figure C.2 92 Figure C.5 A process diagram

17、 showing the details of the “Requirements Engineering” and “Requirements Quality Assurance” processes 93 Figure C.6 An action diagram showing the interaction between some task kinds pertaining to the “Requirements Engineering” and “Requirements Quality Assurance” processes and some related document

18、kinds . 94 BS ISO/IEC 24744:2014 ISO/IEC 24744:2014(E) ISO/IEC 2014 All rights reserved vForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are membe

19、rs 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 activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international orga

20、nizations, 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 committee, ISO/IEC JTC 1. The procedures used to develop this document and those intended for its further main

21、tenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives). Attentio

22、n is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introdu

23、ction and/or on the ISO list of patent declarations received (see www.iso.org/patents). Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement. For an explanation on the meaning of ISO specific terms and expressions related to co

24、nformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information The committee responsible for this document is ISO/IEC JTC 1, Information technology, SC 7, Systems and Software

25、 engineering. This second edition cancels and replaces the first edition (ISO/IEC 24744:2007), which has been technically revised. It also incorporates the Amendment ISO/IEC 24744:2007/Amd.1:2010. BS ISO/IEC 24744:2014 ISO/IEC 24744:2014(E) vi ISO/IEC 2014 All rights reservedIntroduction Development

26、 methodologies may be described in the context of an underpinning metamodel, but the precise mechanisms that permit them to be defined in terms of their metamodels are usually difficult to explain and do not cover all needs. For example, it is difficult to devise a practice that allows the definitio

27、n of properties of the elements that compose the methodology and, at the same time, of the entities (such as work products) created when the methodology is applied. This document introduces, as a (potential) standard, the Software Engineering Metamodel for Development Methodologies, a comprehensive

28、metamodel that makes use of a new approach to defining methodologies based on the concept of powertype. The SEMDM is aimed to the definition of methodologies in information-based domains, i.e. areas characterized by their intensive reliance on information management and processing, such as software,

29、 business or systems engineering. The SEMDM combines key advantages of other metamodelling approaches with none of their known drawbacks, allowing the seamless integration of process, modelling and people aspects of methodologies. Refer to Annex B where other metamodels are mapped to SEMDM and a bri

30、ef synopsis of problems is provided. Various methodologies are defined, used, or implied by a growing number of standards and it is desirable that the concepts used by each methodology be harmonized. A vehicle for harmonization is the SEMDM. Conformance to this metamodel will ensure a consistent app

31、roach to defining each methodology with consistent concepts and terminology. This document also presents a proposed notation for the ISO/IEC 24744 standard metamodel. The notation presented here is mainly graphical and supports most of the classes found in ISO/IEC 24744. Purpose The SEMDM follows an

32、 approach that is minimalist in depth but very rich in width (encompassing domains that are seldom addressed by a single approach). It therefore includes only those higher-level concepts truly generic across a wide range of application areas and at a higher level of abstraction than other extant met

33、amodels. The major aim of the SEMDM is to deliver a highly generic metamodel that does not unnecessarily constrain the resulting methodologies, while providing for the creation of rich and expressive instances. In order to achieve this objective, the SEMDM incorporates ideas from several metamodel a

34、pproaches plus some results of recent research (see 4, 5, 6, 7, 9, 10, 17 for details). This will facilitate: The communication between method engineers, and between method engineers and users of methodology (i.e. developers). The assembly of methodologies from pre-existing repositories of method fr

35、agments. The creation of methodology metamodels by extending the standard metamodel via the extension mechanisms provided to this effect. The comparison and integration of methodologies and associated metamodels. The interoperability of modelling and methodology support tools. The relation of SEMDM

36、to some existing methodologies and metamodels is illustrated in Annex B. Audience Since many classes in the SEMDM represent the endeavour domain (as opposed to the methodology domain), it might look like developers enacting the methodology would be direct users of the metamodel. This is not true. Cl

37、asses in the SEMDM that model endeavour-level elements serve for the method engineer to establish the structure and behaviour of the endeavour domain, and are not used directly during enactment. Only BS ISO/IEC 24744:2014 ISO/IEC 24744:2014(E) ISO/IEC 2014 All rights reserved viimethodology elements

38、, i.e. classes and objects created by the method engineer from the metamodel, are used by developers at the endeavour level, thus supporting both the creation of “packaged” methodologies as well as tailored, project-specific methodologies. Here the term “method engineer” refers collectively to eithe

39、r a person constructing a methodology on site for a particular purpose or a person creating a “packaged“ methodology as a “shrink-wrapped“ process product. BS ISO/IEC 24744:2014BS ISO/IEC 24744:2014 INTERNATIONAL STANDARD ISO/IEC 24744:2014(E) ISO/IEC 2014 All rights reserved 1Software engineering M

40、etamodel for development methodologies 1 Scope This International Standard defines the Software Engineering Metamodel for Development Methodologies (SEMDM), which establishes a formal framework for the definition and extension of development methodologies for information-based domains (IBD), such as

41、 software, business or systems, including three major aspects: the process to follow, the products to use and generate, and the people and tools involved. This metamodel can serve as a formal basis for the definition and extension of any IBD development methodology and of any associated metamodel, a

42、nd will be typically used by method engineers while undertaking such definition and extension tasks. The metamodel does not rely upon nor dictate any particular approach to IBD development and is, in fact, sufficiently generic to accommodate any specific approach such as object-orientation, agent-or

43、ientation, component-based development, etc. 2 Conformance A metamodel is defined in accordance with this International Standard if it: a. Describes the scope of the concepts in the metamodel in relation to the scope of the elements defined in clause 7. b. Defines the mapping between the concepts th

44、at are addressed in the metamodel, and that are within the scope of this International Standard, and the corresponding elements of this Standard (i.e. the elements of the standard cannot be substituted by others of identical intent but different construction). A development methodology is defined in

45、 accordance with this International Standard if it is generated from a conformant metamodel as defined in the first paragraph of this clause (2 Conformance). A development or engineering tool is developed in accordance with this International Standard if it implements a conformant metamodel as defin

46、ed in the first paragraph of this clause (2 Conformance). If the purpose of the tool involves the creation of methodologies, then it is developed in accordance with this Standard if it also implements the necessary features so as to make the mechanisms described in sub-clause 8.1 available to the to

47、ols users. If the purpose of the tool involves the extension of the metamodel, then it is developed in accordance with this Standard if it also implements the necessary features so as to make the mechanisms described in sub-clause 9.1 available to the tools users. NOTE 1 The metamodel thus defined d

48、oes not necessarily have to include all the elements defined in clause 7 only those that are relevant to the purpose of the said metamodel are required. NOTE 2 Conformance for methodologies or conformance for tools can be established without any necessity of explicitly including the detailed metamod

49、el for any relevant work product kind or model unit kind. It is adequate to define the mappings of any such work products to the WorkProductKind and ModelUnitKind classes of the SEMDM. 3 Terms and definitions For the purposes of this document, the following terms and definitions apply. NOTE This Standard uses a self-consistent set of core concepts that is as compatible as possible with other standards (such as ISO/IEC 12207, ISO/IEC 15504, etc.). BS ISO/IEC 24744:2014 ISO/IEC 24744:2014(E) 2 ISO