Practice: Business Process Sketching
A Business Process Diagram is a sketch that uses graphical elements and semantics that support these elements as defined in the Object Management Group Business Process Modeling Notation specification.
Purpose

The purpose of this practice is to accelerate re-use and creation of a Business Process Diagram (or multiple) to drive requirements clarity, context and consensus across the software delivery lifecycle.

As this practice evolves it will be adapted to be a more encompassing and will include how it fits in a larger business architecture context.

Main Description

Though the purpose of this practice is to accelerate re-use and creation of Business Process Diagram to drive requirements clarity, context and consensus across the software delivery lifecycle, it should be noted that any planning, funding determination, or how Business Process Diagrams fits into an enterprise analysis to strategically determine future business, is beyond the scope of this practice. 

It is assumed that there already has been some determination that there is a business need and a problem statement describing the scope.

 This problem statement can be an e-mail (from a senior member of the enterprise), a problem report, requested customer need or a formal vision document (Business Vision). The person sketching the diagrams has already been determined and funded, and may be part of a funded project or as part of some pre-project analysis.

How to read this practice

The best way to read this practice is to first familiarize yourself with its overall structure -- what it is in it and how it is organized. 

The best place to start is with the Key Concepts for the practice -- those concepts that are critical to understand in order to adopt the practice.  Once you understand the key concepts, you can turn your attention to the Work Products produced by the practice.   Then you can review the practices Tasks.  From the work products and the tasks, you can access applicable guidance -- guidelines and tool mentors associated with each task provide details of how to perform the task. Templates and checklists associated with the work products guide you in their completion and evaluation. You can also access the guidance provided by the practice directly by using the Guidance folder.

Additional Information
For more information on this practice,  see the practice resource page on IBM® DeveloperWorks®.
Relationships