Short summary of the methodology used to link requirements, issues and changes modeled with UML language, to the standard SAP Change and Transport System

1. Tracking, requirements, work elements and
change requests on SAP with UML
Massimo Coletti
July 2012
Quest'opera è stata rilasciata con licenza Creative Commons Attribuzione - Non commerciale - Condividi allo stesso modo 3.0 Unported. Per leggere una
copia della licenza visita il sito web http://creativecommons.org/licenses/by-nc-sa/3.0/ o spedisci una lettera a Creative Commons, 171 Second Street, Suite
300, San Francisco, California, 94105, USA.

2. Tracking, requirements, work elements and
change requests on SAP with UML

3. What's this?
Informal and short slideshow
Based on field experience
Non introduction to UML or SAP change and transport
system → out of scope :-)

4. step 1 - requirements
a requirement models the
goal of the system
change:
using business terms
what is expected from the
system

5. multiple requirements
independent or related (as
in the depicted case)

6. each requirement is
numbered, tool feature
status: requirement
lifecycle
Keywords: requirement
source (person,
organizational unit, etc.)
Other attributes:
priority, version, type, etc.

7. step 2 – work item
the requirement is “validated” (blue edge):
this means analysis drafted and shared with the key user
color coding for status
represent a possible solution/implementation strategy, to
address one or more requirements
<address> stereotype links the work item to the
requirement

8. alternatives:
one validated
others “rejected”
documentation of
development decisions
each work item can be developed internally, or
committed to external consultants
diagram = specifications

9. step 3 - development
CR are generated in ECC
dveel. system
Each CR is tagged with a
custom attribute:
work item number or
requirement number (simpler
case) or
issue number

10. 4 – model deliverables for future use
usage:
issue tracking
impact analysis for future
developments

11. step 5 - issues
an issue may be related to a work item or not
it is always related to an artifact

12. results...

13. find issues related to a deliverable
issues related to artifact “V07 – Incassi nel periodo”
(BW Query)

14. find CR related to an issue or work item
SE03 (find CR) output

15. issues status report – project deliverable
Example:
on a single BW project : 180
pages report, generated from
the UML tool, with the full
documentation of issues,
arranged by project module

16. references
the UML tool used is Enterprise Architect, windows,
cost-effective application. Any other tool is suitable