Software engineering - Metamodel for development methodologies
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 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. This document introduces, as a (potential) standard, the Software Engineering Metamodel for Development Methodologies, a comprehensive 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, 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 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 con
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 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, and 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-orientation, component-based development, etc. 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 that 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 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 defined 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 tool’s 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 impl
Contents:
- Foreword
- Introduction
- Scope