Business Process Specification

USER VERSION #
SUBJECT MATTER EXPERT

<<Enter Project Name>> <<Enter Doc Ver #>> <<Enter SME>> <<Enter SME2>>

BUSINESS PROCESS DESCRIPTION BUSINESS PROCESS REFERENCE #

LAST MODIFIED DATE BUSINESS PROCESS SPECIFICATION STATUS

<<Enter Document Title>> <<Enter Reference Number>> 8/22/2005 <<Enter Document Status>>

WRITTEN BY

<<Enter Author>>

DATE APPROVED

Program Title
Business Process Specification: <<Enter Document Title>>
Version <<Enter Doc Ver #>>

<<Enter Document Title>> <<Enter Reference Number>>

Version: Date:

<<Enter Doc Ver #>> 8/22/2005

TABLE OF CONTENTS Program Title..................................................................................................................................1 Business Process Specification: <<Enter Document Title>>.......................................................1 Version <<Enter Doc Ver #>>.......................................................................................................1 TABLE OF CONTENTS.................................................................................................................2 1. Process Mission, Scope, and Summary.....................................................................................3 2. Stakeholders................................................................................................................................4 3. Business Actors...........................................................................................................................4 4. Inputs...........................................................................................................................................4 5. Outputs........................................................................................................................................4 6. Business Measurements.............................................................................................................5 7. Process Flow Diagrams .............................................................................................................6 8. Business Process Spec Sign-Off................................................................................................7 9. Open Issues.................................................................................................................................7 10. Revision History.........................................................................................................................7 11. Appendix....................................................................................................................................8

Confidential

Page 2

<<Enter Document Title>> <<Enter Reference Number>>

Version: Date:

<<Enter Doc Ver #>> 8/22/2005

1.

Process Mission, Scope, and Summary

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer in wisi id ligula consectetuer vehicula. Suspendisse ut quam. Quisque posuere, pede sed varius vestibulum, felis leo congue leo, ac pulvinar dui turpis eu massa.

1.1

Mission
Brief Mission Statement (i.e. This document details the processes that comprise the daily activities surrounding the hedging of loan assets and management of the resulting P/L impact.)

1.2

Scope
1. 2. 3. 4. 5. 6. 7. Overview of data covered by document. Mention related functionality that is not included State assumptions (i.e. all legal documents are relationships exist) State that document covers business, not systems Scope is not tied directly to one use case BPS may tie to multiple use cases Use cases are not yet defined but may fall out of this document

1.3

Summary
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer in wisi id ligula consectetuer vehicula. Suspendisse ut quam. Quisque posuere, pede sed varius vestibulum, felis leo congue leo, ac pulvinar dui turpis eu massa. Main body of document Detailed business level narrative Should cover all points mentioned in the scope

No reference to existing technical solution or specific manual process unless integral to the success of the business result 1.3.1 Small chucks on detail May be organized into areas that will later relate to use cases Should be sunny-day view Heading 3 1.3.1.1 1.3.1.2 1.3.1.3 1.3.2 Heading 4 Heading 4 Heading 4

Heading 3 Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer in wisi id ligula consectetuer vehicula. Suspendisse ut quam. Quisque posuere, pede sed varius vestibulum, felis leo congue leo, ac pulvinar dui turpis eu massa.

Confidential

Page 3

<<Enter Document Title>> <<Enter Reference Number>>

Version: Date:

<<Enter Doc Ver #>> 8/22/2005

1.3.3

Heading 3 Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer in wisi id ligula consectetuer vehicula. Suspendisse ut quam. Quisque posuere, pede sed varius vestibulum, felis leo congue leo, ac pulvinar dui turpis eu massa. Integer scelerisque dolor non est. Vestibulum dolor ipsum, euismod vitae, varius sit amet, dapibus ac, sem. Sed commodo lobortis leo. Donec lacinia dignissim dolor. Maecenas mi. In sit amet lorem ac velit auctor hendrerit. Proin sapien velit, accumsan eget, mattis et, gravida non, erat. Aenean malesuada nibh at dui.

1.3.4

Heading 4

2.

Stakeholders
All individuals, groups, or entities that rely on the success of the functionality May or may not play a direct role in the process

3.

Business Actors
All individuals, groups, or entities that pay a direct role in the success of the process. May be primary or secondary

4.

Inputs
Detail required for the process to be handled correctly Example For a shopping cart the list might be as follows Item Quantity Shipping Detail Billing Detail Shipping Type Payment Detail

5.

Outputs
Expected outcome for successful completion of the process Shopping Cart Example Confirmation Email Confirmation Number UPS Tracking Slip Order report
Page 4

Confidential

<<Enter Document Title>> <<Enter Reference Number>>

Version: Date:

<<Enter Doc Ver #>> 8/22/2005

6.

Business Measurements
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer in wisi id ligula consectetuer vehicula. Suspendisse ut quam. Quisque posuere, pede sed varius vestibulum, felis leo congue leo, ac pulvinar dui turpis eu massa. Shopping Cart Example Order stored and scheduled for shipping Credit Card payment processed Purchaser detail recorded Confirmation number sent to User and managed internally Daily report summary created by 4 p.m. Issue of how specific these should be

6.1

Criteria used to measure business success

6.1.1 Heading 3 6.1.1.1 6.1.1.2 6.1.1.3 6.1.2 6.1.3 Heading 4 Heading 4 Heading 4

Heading 3 Heading 3

Confidential

Page 5

<<Enter Document Title>> <<Enter Reference Number>>

Version: Date:

<<Enter Doc Ver #>> 8/22/2005

7.

Process Flow Diagrams

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Integer in wisi id ligula consectetuer vehicula. Suspendisse ut quam. Quisque posuere, pede sed varius vestibulum, felis leo congue leo, ac pulvinar dui turpis eu massa. Use UML Activity Diagram Model May tied to eventual use case models Should include both high-level overview and more specific flows

7.1 7.2

Main Flow Diagrams Sub/Alternative Process Flow Diagrams

Confidential

Page 6

<<Enter Document Title>> <<Enter Reference Number>>

Version: Date:

<<Enter Doc Ver #>> 8/22/2005

8.

Business Process Spec Sign-Off

8.1 Subject Matter Experts:
SME Signature: _______________________________ Date: _____________ <<Enter SME>> SME Signature: _______________________________ Date: _____________ <<Enter SME2>>

9.

Open Issues
# 1 2 3 4 Date Opened Description Resolution Date Resolved

10. Revision History

Date Version Description Author

Confidential

Page 7

<<Enter Document Title>> <<Enter Reference Number>>

Version: Date:

<<Enter Doc Ver #>> 8/22/2005

11. Appendix
11.1 Appendix A Business Rules (if applicable)
Business Rule 1 example All associated business rules Should tie to rules defined in use cases

Is not an exhaustive list but high-level rules, use case development will add more Should this document be continually updated

11.2

Appendix B Definitions (if applicable)

Term Definition

11.3

Appendix C Enhancement Requests (if applicable)

Known future business expansion Not technical enhancements

11.4

Appendix D Reports (if applicable)

Detail on report output Name Content Related Processes

Confidential

Page 8