1、 Collection of SANS standards in electronic format (PDF) 1. Copyright This standard is available to staff members of companies that have subscribed to the complete collection of SANS standards in accordance with a formal copyright agreement. This document may reside on a CENTRAL FILE SERVER or INTRA
2、NET SYSTEM only. Unless specific permission has been granted, this document MAY NOT be sent or given to staff members from other companies or organizations. Doing so would constitute a VIOLATION of SABS copyright rules. 2. Indemnity The South African Bureau of Standards accepts no liability for any
3、damage whatsoever than may result from the use of this material or the information contain therein, irrespective of the cause and quantum thereof. ISBN 978-0-626-21376-3 SANS 24744:2008Edition 1ISO/IEC 24744:2007Edition 1SOUTH AFRICAN NATIONAL STANDARD Software engineering Metamodel for development
4、methodologies This national standard is the identical implementation of ISO/IEC 24744:2007 and is adopted with the permission of the International Organization for Standardization and the International Electrotechnical Commission. Published by Standards South Africa 1 dr lategan road groenkloof priv
5、ate bag x191 pretoria 0001 tel: 012 428 7911 fax: 012 344 1568 international code + 27 12 www.stansa.co.za Standards South Africa SANS 24744:2008 Edition 1 ISO/IEC 24744:2007 Edition 1 Table of changes Change No. Date Scope National foreword This South African standard was approved by National Commi
6、ttee StanSA SC 71C, Information technology ICT systems and software engineering, in accordance with procedures of Standards South Africa, in compliance with annex 3 of the WTO/TBT agreement. This SANS document was published in May 2008. Reference numberISO/IEC 24744:2007(E)ISO/IEC 2007INTERNATIONAL
7、STANDARD ISO/IEC24744First edition2007-02-15Software Engineering Metamodel for Development Methodologies Ingnierie du logiciel Mtamodle pour les mthodologies de dveloppement SANS 24744:2008This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/I
8、EC 24744:2007(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downlo
9、ading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the G
10、eneral Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address gi
11、ven below. ISO/IEC 2007 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 at the address below or ISOs m
12、ember 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 copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2007 All rights reservedSANS 24744:2008This s tandard may only be used and print
13、ed by approved subscription and freemailing clients of the SABS .ISO/IEC 24744:2007(E) iiiContents Page 1 Scope 1 1.1 Purpose. 1 1.2 Audience. 1 2 Conformance . 2 3 Terms and definitions 2 4 Naming, diagramming and definition conventions, and abbreviated terms . 4 4.1 Naming, diagramming and definit
14、ion conventions. 4 4.2 Abbreviations 5 5 Basic Concepts . 5 5.1 Method Engineering . 6 5.2 Dual-Layer Modelling . 6 5.3 Powertypes and Clabjects. 6 5.4 Uniting Process and Product 7 5.5 Process Assessment 7 6 Introduction to the SEMDM . 8 6.1 Highly Abstract View 8 6.2 Abstract View and Core Classes
15、 8 6.3 Process Classes 9 6.4 Producer Classes 11 6.5 Product Classes 12 6.6 Connection between Process and Product 13 6.7 Support Classes 14 7 Metamodel Elements 15 7.1 Classes . 15 7.2 Enumerated Types 63 8 Using the Metamodel . 64 8.1 Usage Rules. 64 8.2 Usage Guidelines 65 9 Extending the Metamod
16、el 66 9.1 Extension Rules 66 9.2 Extension Guidelines . 67 Annex A (informative) Worked Example . 68 Annex B (informative) Mappings to Other Metamodelling Approaches 74 Bibliography 78 ISO/IEC 2007 All rights reservedSANS 24744:2008This s tandard may only be used and printed by approved subscription
17、 and freemailing clients of the SABS .iv Table of Figures Figure 1 The three areas of expertise, or domains, which act as a context for SEMDM . 5 Figure 2 Highly abstract view of the SEMDM 8 Figure 3 Abstract view of the SEMDM, showing the core classes in the metamodel. 9 Figure 4 Work units .10 Fig
18、ure 5 Stages .11 Figure 6 Producers 12 Figure 7 Work product and modelling classes 13 Figure 8 Actions and constraints 14 Figure 9 Support classes 14 ISO/IEC 24744:2007(E) ISO/IEC 2007 All rights reservedSANS 24744:2008This s tandard may only be used and printed by approved subscription and freemail
19、ing clients of the SABS .vForeword 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 Internationa
20、l 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 I
21、SO 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. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical comm
22、ittee 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 % of the national bodies casting a vote. Attention is drawn to t
23、he 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. ISO/IEC 24744 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, So
24、ftware and systems engineering. ISO/IEC 24744:2007(E) ISO/IEC 2007 All rights reservedSANS 24744:2008This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .vi Introduction Development methodologies may be described in the context of an underpinning
25、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,
26、at the same time, of the entities (such as work products) created when the methodology is applied. This International Standard introduces the Software Engineering Metamodel for Development Methodologies SEMDM, a comprehensive metamodel that makes use of a new approach to defining methodologies based
27、 on the concept of powertype. The SEMDM is aimed atthe definition of 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 othe
28、r 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 brief synopsis of problems is provided. Various methodologies are defined, use
29、d 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.
30、 ISO/IEC 24744:2007(E) ISO/IEC 2007 All rights reservedSANS 24744:2008This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .INTERNATIONAL STANDARD ISO/IEC 24744:2007(E) ISO/IEC 2007 All rights reserved 11 Scope This International Standard defines t
31、he 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 software, business or systems, including three major aspects: the process to follow
32、, the work 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, and will be typically used by method engineers while undertaking such definition
33、 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-orientation, component-based development, etc. 1.1 Purpose This International Sta
34、ndard follows an 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
35、other extant metamodels. 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 sev
36、eral metamodel approaches plus some results of recent research (see 1-7 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 frag
37、ments; 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; and The interoperability of modelling and methodology support tools. The relation of SEMD
38、M to some existing methodologies and metamodels is illustrated in Annex B. 1.2 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 tr
39、ue. Classes 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 Software Engineering Metamodel for Development Methodologies SANS 24744:2008This s tandard may
40、 only be used and printed by approved subscription and freemailing clients of the SABS .2 ISO/IEC 2007 All rights reservedmethodology elements, 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
41、 of “packaged” methodologies as well as tailored, project-specific methodologies. Here the term “method engineer” refers collectively to either a person constructing a methodology on site for a particular purpose or a person creating a “packaged“ methodology as a “shrink-wrapped“ process product. 2
42、Conformance A metamodel is defined in accordance with this International Standard if it: describes the scope of the concepts in the metamodel in relation to the scope of the elements defined in Clause 7; anddefines the mapping between the concepts that are addressed in the metamodel, and that are wi
43、thin the scope of this International Standard, and the corresponding elements of this International Standard (i.e. its elements cannot be substituted by others of identical intent but different construction). A development methodology is defined in accordance with this International Standard if it i
44、s 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 defined in the first paragraph of this clause (2 Conforma
45、nce). If the purpose of the tool involves the creation of methodologies, then it is developed in accordance with this International Standard if it also implements the necessary features so as to make the mechanisms described in 8.1 available to the tools users. If the purpose of the tool involves th
46、e extension of the metamodel, then it is developed in accordance with this International Standard if it also implements the necessary features so as to make the mechanisms described in 9.1 available to the tools users. NOTE 1 The metamodel thus defined does not necessarily have to include all the el
47、ements 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 metamodel for any relevant work product kind or model
48、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. Unless otherwise noted, the definitionsare specific to this
49、International Standard. The following concepts are defined only for their usage throughout this International Standard. NOTE This International Standard uses a self-consistent set of core concepts that is as compatible as possible with other International Standards (such as ISO/IEC 12207, ISO/IEC 15504, etc.). 3.1information-based domainIBD realm of activity for which information is the most valuable assetNOTE This means that information creation, manipulation and dissemination are the most import
