BUS 309 - Process Definition
Author: IBM
Owner: IBM
Document: [Link] Date: 08-26-2004
Path: /conversion/tmp/activity_task_scratch/[Link] Version: V1.0.0A
Owner: IBM Status: Draft
Subject: BUS 309 - Process Definition Page 1 of 10
Document History
Document Location
This is a snapshot of an on-line document. Paper copies are valid only on the day they are printed. Refer to
the author if you are in any doubt about the currency of this document.
Revision History
Date of this revision: 08-26-2004 Date of next revision (date)
Revision Revision Summary of Changes Changes
Number Date marked
(#) (-) (Describe change) (N)
Approvals
This document requires following approvals. Signed approval forms are filed in the Quality section of the
PCB.
Name Title
(name) (title)
Distribution
This document has been distributed to
Name Title
(name) (title)
Document: [Link] Date: 08-26-2004
Path: /conversion/tmp/activity_task_scratch/[Link] Version: V1.0.0A
Owner: IBM Status: Draft
Subject: BUS 309 - Process Definition Page 2 of 10
Contents
1. Introduction............................................................................................................. 4
1.1 Identification.................................................................................................................................. 4
1.2 References.................................................................................................................................... 4
1.3 Notation......................................................................................................................................... 4
2. Level 1 Process <Name>........................................................................................6
2.1 Level 2 Sub-Process <Name>....................................................................................................... 7
2.1.1 Level 3 Activity <Name>......................................................................................................... 8
2.1.2 Level 3 Activity <Name>......................................................................................................... 9
2.2 Level 2 Sub-Process <Name>....................................................................................................... 9
3. Level 1 Process <Name>......................................................................................10
Document: [Link] Date: 08-26-2004
Path: /conversion/tmp/activity_task_scratch/[Link] Version: V1.0.0A
Owner: IBM Status: Draft
Subject: BUS 309 - Process Definition Page 3 of 10
1. Introduction
Please note that:
Text in the “Editor’s comments” style (such as this) provides guidance to the editor, in
conjunction with the corresponding work product description, and should be removed from the
published version of the document.
The “Reader’s comments” style (in purple) provides guidance to the reader and should be
modified by the editor to reflect any customization of the template.
The “Normal” style in black should be used by the editor when adding the text, appropriate for
this work product, describing the business environment.
When using this template, refer to the Global Services Method work product description “BUS 309
Process Definition”.
This chapter identifies the document and the business environment to which it relates, describes the contents
of the document, and states its purpose.
1.1 Identification
Via the IBM menu, edit the document information, change “Subject” to include the type of description
(for example “BUS 309 - Current Logical Process Definition”), enter the name of the business
environment being described into the field “Text 2”, and press the “Update” button.
This document describes the Business Processes of in the current / future * environment. It is a logical
description, unconstrained by organization and technology / It is a physical description, constrained by
organization and technology. *
* Delete as appropriate. Processes are normally defined both for the current and future situations.
These two definitions should be produced as separate documents. However this template can be
used for both documents.
1.2 References
This document is based on and refers to the following documents:
[<no.>] <author>, <title>, <reference>, <version no.>, <date>{,<pages>}
where items in {} are optional.
e.g.,
[1] IBM Global Services, "Component Model for HAL", [Link], V1.0.0A, 19/02/2001.
Then in the body of the text refer to the document by: Reference [1].
1.3 Notation
Describe in this section the notation(s) used for the process model diagrams.
Document: [Link] Date: 08-26-2004
Path: /conversion/tmp/activity_task_scratch/[Link] Version: V1.0.0A
Owner: IBM Status: Draft
Subject: BUS 309 - Process Definition Page 4 of 10
Adopt one or more of the commonly used notations identified in section 3 (Notation), and illustrated
in section 4 (Example), of the work product description. For Custom Application Development (CAD)
engagements, use a Line of Visibility (LOVEM) diagram.
Describe the fields of the process tables if you think their meaning or purpose will not be clear to the
reader.
<Notation>
Document: [Link] Date: 08-26-2004
Path: /conversion/tmp/activity_task_scratch/[Link] Version: V1.0.0A
Owner: IBM Status: Draft
Subject: BUS 309 - Process Definition Page 5 of 10
2. Level 1 Process <Name>
Illustrate the process by means of one of the diagram types identified in section 3 (Notation) of the
work product description. For Custom Application Development (CAD) engagements, use a Line of
Visibility (LOVEM) diagram.
<Insert the process diagram here>
Describe the process by completing the table below, as shown in the example in section 4.12
(Process Definition template) of the work product description.
Process Name
Description
Starts with
(is triggered by)
Ends with
Includes
Excludes
Inputs
Outputs
Customer of
this process
Customers’
expectations of
this process
Suppliers
Measurements
Document: [Link] Date: 08-26-2004
Path: /conversion/tmp/activity_task_scratch/[Link] Version: V1.0.0A
Owner: IBM Status: Draft
Subject: BUS 309 - Process Definition Page 6 of 10
2.1 Level 2 Sub-Process <Name>
Illustrate the sub-process by means of one of the diagram types identified in section 3 (Notation) of
the work product description. For Custom Application Development (CAD) engagements, use a Line
of Visibility (LOVEM) diagram.
<Insert the sub-process diagram here>
Describe the sub-process by completing the table below, as shown in the example in section 4.12
(Process Definition template) of the work product description.
Sub-Process
Name
Description
Starts with
(is triggered by)
Ends with
Includes
Excludes
Inputs
Outputs
Customer of this
sub-process
Customers’
expectations of
this sub-process
Suppliers
Measurements
Document: [Link] Date: 08-26-2004
Path: /conversion/tmp/activity_task_scratch/[Link] Version: V1.0.0A
Owner: IBM Status: Draft
Subject: BUS 309 - Process Definition Page 7 of 10
2.1.1 Level 3 Activity <Name>
If the activity is further broken down into tasks, illustrate the activity by means of one of the diagram
types identified in section 3 (Notation) of the work product description. For Custom Application
Development (CAD) engagements, use a Line of Visibility (LOVEM) diagram.
<Insert the activity diagram here.>
Describe the activity by completing the table below, as shown in the example in section 4.12 (Process
Definition template) of the work product description.
Activity Name
Description
Starts with
(is triggered by)
Ends with
Includes
Excludes
Inputs
Outputs
Customer of
this activity
Customers’
expectations of
this activity
Suppliers
Measurements
Document: [Link] Date: 08-26-2004
Path: /conversion/tmp/activity_task_scratch/[Link] Version: V1.0.0A
Owner: IBM Status: Draft
Subject: BUS 309 - Process Definition Page 8 of 10
[Link] Level 4 Task <Name>
This level of detail is not always required. See section 1 (Description) of the work product description.
If tasks are defined, provide a description of the task using the table template. A diagram is never
required at the task level because this is the lowest level of detail.
Task Name
Description
Starts with
(is triggered by)
Ends with
Includes
Excludes
Inputs
Outputs
Customer of
this task
Customers’
expectations of
this task
Suppliers
Measurements
[Link] Level 4 Task <Name>
Repeat the above paragraph and table for each task which is part of the activity.
2.1.2 Level 3 Activity <Name>
Repeat the above “activity” paragraph (including task subparagraphs, if appropriate) for each activity
which is part of the sub-process.
2.2 Level 2 Sub-Process <Name>
Repeat the above “sub-process” paragraph (including activity and task sub-paragraphs) for each
sub-process of the process.
Document: [Link] Date: 08-26-2004
Path: /conversion/tmp/activity_task_scratch/[Link] Version: V1.0.0A
Owner: IBM Status: Draft
Subject: BUS 309 - Process Definition Page 9 of 10
3. Level 1 Process <Name>
Repeat the previous chapter for each additional process.
Document: [Link] Date: 08-26-2004
Path: /conversion/tmp/activity_task_scratch/[Link] Version: V1.0.0A
Owner: IBM Status: Draft
Subject: BUS 309 - Process Definition Page 10 of 10