-
Key: SPEM2-11
-
Legacy Issue Number: 11082
-
Status: closed
-
Source: International Business Machines ( Dr. Peter Haumer)
-
Summary:
Meta-Model: Responsibility Assignment Maps shall be specific for the Work Product State In the current SPEM 2.0 meta-model responsibility assignment of roles to work products is a class that associates a role use with a work product use as well as a role definition with a work product definition. However, in many processes these responsibilities might be actually different based on the state of the work product. For example, a “work item” work product to fix a bug might be assigned to a developer in the state “open” and assigned to a tester role instance in the state “resolved”. In the current SPEM 2 specification this can only be modeled by defining different work product use and role use instances with different maps within the context/namespace of an activity, but not independent of activities. Often processes or method content wants to define such relationships independent of a specific activity scope. We therefore propose to turn the assignment maps into such a ternary relationship (still represented as a class) amongst the concepts of role, work products, and state and to package merge in the Process Behavior package an association from the Responsibility Assignment Maps in Sections 9.8 and 12.1 to State_ext.
-
Reported: SPEM 1.1 — Thu, 31 May 2007 04:00 GMT
-
Disposition: Resolved — SPEM 2.0b1
-
Disposition Summary:
- See changes for Issue 11081
- Added redefinitions of Default Responsibility Assignment and Process Responsibility Assignment (they have been renamed in Issue 11084 to not use the word Map anymore) that are associated to State_ext
-
Updated: Sat, 7 Mar 2015 04:18 GMT
SPEM2 — Responsibility Assignment Maps shall be specific for the Work Product State
- Key: SPEM2-11
- OMG Task Force: SPEM 2.0 FTF