Process-data diagram: Difference between revisions

Revision as of 00:24, 11 April 2008

Revision as of 01:10, 11 April 2008

Line 1:

[[Image:PDD.jpg|thumb|320px280px|right|The process data diagram]]

A '''process-data diagram''' is a [[diagram]] that describes [[process]]es and [[data]] that act as output of these processes. On the left side the [[meta-process model]] can be viewed and on the right side the meta concept model can be viewed. A process-data diagram is a combination of an [[activity diagram]] or [[process diagram]] and a [[flowchart]].

== Overview ==

The process-data diagram that is depicted at the right, gives an overview of all of these activities/processes and deliverables. The four gray boxes depict the four main [[implementation]] phases, which each contain several processes that are in this case all sequential. [[Image:SAP_Implementation_process-data_diagram.png|320px280px|right|thumbnail|SAP Implementation process-data diagram]] The boxes at the right show all the deliverables/[[concept]]s that result from the processes. Boxes without a shadow have no further sub-concepts. Boxes with a black shadow depict complex closed concepts, so concepts that have sub-concepts, which however will not be described in any more detail. Boxes with a white shadow (a box behind it) depict open closed concepts, where the sub-concepts are expanded in greater detail. The lines with diamonds show a has-a relationship between concepts.

The [[SAP implementation]] process is made up out of four main phases, i.e. the project preparation where a vision of the future-state of the SAP solution is being created, a sizing and blueprinting phase where the solution stack is created and [[training]] is being performed, a functional development phase and finally a final preparation phase, when the last [[Software testing|tests]] are being performed before the actual go live. For each phase, the vital activities are addressed and the [[deliverable]]s/[[Product (business)|product]]s are explained.

Line 48:

The integration of both types of diagrams is quite straightforward. Each action or activity results in a concept. They are connected with a dotted arrow to the produced artifacts, as is demonstrated in Figure 9. The concepts and activities are abstract in this picture.

::[[Image:Mm41.gif|frame|left|Figure 9: Process-Data Diagram]]<br clear=left>

In Table 1 a generic table is presented with the description of activities, sub-activities and their relations to the concepts. In section 5 examples are given of both process-data diagram and activity table.

::{| class="wikitable"

:'''Table 1: Activity table'''

:{| class="wikitable"

|- bgcolor="#ccccff"

|'''Activity'''

Line 64 ⟶ 63:

|-

|}

::'''Table 1: Activity table'''

== Example of a process-data diagram ==

Line 70:

Notable is the use of open and closed concepts. Since project management is actually not within the scope of this research, the concept CONTROL MANAGEMENT has not been expanded. However, in a complex project is RISK MANAGEMENT of great importance. Therefore, the choice is made to expand the RISK MANAGEMENT concept.

::[[Image:Mm42.gif|frame|left|Figure 10: Example Process-Data Diagram - Orientation phase in a complex project]]<br clear=left>

In Table 2 the activities and sub-activities, and relation to the concepts are described.

::{| class="wikitable"

:'''Table 2: Activities and sub-activities in a complex orientation phase'''

:{| class="wikitable"

|- bgcolor="#ccccff"

|'''Activity'''

Line 126 ⟶ 125:

|-

|}

::'''Table 2: Activities and sub-activities in a complex orientation phase'''

== See also ==