Legacy Issue Number: 4887
Source: France Telecom R&D ( Mariano Belaunde)
3. Capturing distinct kinds of WorkProducts in the metamodel.
In the metamodel there is no way to capture both the name and
the kind of a workproduct. In contrast, in the UML profile, the
kind of a work product can be provided using pre-defined stereotypes
(such as <<document>> and <<UMLmodel>>).
In order to solve this and also allow more flexibility to refer to distinct
kinds of work products (such as Text Documents, UML model,
SDL models, SQL Tables, executables, code librairies, and so on) a
WorkProductKind could be added in the metamodel (in the similar
manner as the GuidanceKind metaclass).
In addition a 'subKind' association between WorkProductKinds could
be useful to allow the structuring of allowable product kinds.
NOTA: No additional pre-defined UML stereotypes need to be
defined since these may depend on the process family being used.
Reported: SPEM 1.0b1 — Fri, 22 Feb 2002 05:00 GMT
Disposition: Resolved — SPEM 1.0
Updated: Fri, 6 Mar 2015 20:58 GMT