ISO/IEC 24744:2014
(Main)Software engineering — Metamodel for development methodologies
Software engineering — Metamodel for development methodologies
Development 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 definition 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. ISO/IEC 24744:2014 introduces the Software Engineering Metamodel for Development Methodologies (SEMDM), a comprehensive metamodel that makes use of a new approach to defining methodologies based on the concept of powertype. The aim of SEMDM is to define methodologies in information-based domains, i.e. areas characterized by their intensive reliance on information management and processing, such as software, 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. Examples are given where other metamodels are mapped to SEMDM and a brief 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 approach to defining each methodology with consistent concepts and terminology.
Ingénierie du logiciel — Métamodèle pour les méthodologies de développement
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 24744
Second edition
2014-11-15
Software engineering — Metamodel for
development methodologies
Ingénierie du logiciel — Métamodèle pour les méthodologies de
développement
Reference number
©
ISO/IEC 2014
© ISO/IEC 2014
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in 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 ISO’s member body in the country of the requester.
ISO copyright office
Case postale 56 CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2014 – All rights reserved
Contents Page
Foreword . v
Introduction . vi
1 Scope . 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 Clabjects . 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 . 13
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.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 . 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
© ISO/IEC 2014 – All rights reserved iii
C.2 Notation Elements .77
C.3 Diagram Types .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 powertype. 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, showing 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 method . 89
Figure C.2 – A lifecycle diagram showing the content structure as well as the temporal structure of a method
.................................................................................................................................................................... 90
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 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 kinds . 94
iv © ISO/IEC 2014 – All rights reserved
Foreword
ISO (the International Organization 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 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 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 maintenance 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).
Attention 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 Introduction 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 conformity assessment,
as well as information about ISO's 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 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.
© ISO/IEC 2014 – All rights reserved v
Introduction
Development 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
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.