SPEM
The Software Process Engineering Metamodel ( SPEM , metamodel for development processes in software technology ), approved by the Object Management Group (OMG) in June 2005 , was developed explicitly for the modeling and exchange of development processes in software technology. As of version 2.0 from April 2008, SPEM stands for Software & Systems Process Engineering Meta-Model ( meta-model for development processes in software and system technology ).
Origin and use
The reason for the creation of the metamodel was the variety of incompatible descriptive languages that had arisen in the preceding decades. No standardized process description for software development could be established in the industry.
The OMG therefore set to work to develop and standardize a clear set of rules with notation elements for industry and, above all, with industry.
The Unified Modeling Language Standard ( UML ) by OMG, published in 1997, served SPEM as a basis, which is why SPEM was also defined as a "subset" of UML. “Subset” means a “partial” reuse of UML metamodel elements in SPEM.
The difference between UML and SPEM is that UML is an industry standard for a modeling language (notation) of systems. SPEM, on the other hand, is an industry standard for a modeling language of processes and “process families”. SPEM does not describe what the planning or implementation of a process should look like; there are enough other project approach models for this (e.g. V-Modell XT (VXT)). However, the primary task of both standards (UML / SPEM) is to keep the exchange of processes and systems as simple as possible so that everyone who has knowledge of UML / SPEM can "read" it.