Mapping Business Process (Business Requirements Modelling) ensures traceability from the Business Processes to the implementation.

1. Business Process mapping to Epic and User Stories
Business Processes
Mapping Business Process (Business Requirements Modelling) ensures traceability from the Business Processes to
the implementation.
Business Objectives are the goal that
an organization wants to achieve, or
the goal set for a business process.
It highlights the features in a Business
Process to be improved.
Business Objectives
Business Requirements
Business Requirements are the expression of
the needs to be fulfilled by the system. They
are issued from Business Objectives.
There are two types of Business Requirements:
 Functional Business Requirements
 Non-functional Business Requirements
Functional Business Requirement is the
necessary task, action or activity that must be
accomplished. It deal with what the system
should do or provide for users, what it does to
have an effect on the outside domain and what
the user requires to complete tasks.
A Non-functional Business Requirement details
constraints, targets or control mechanisms for
the. It describes standard, regulation, service
level, interfaces and the quality attributes that
affect how the system must run.
Functional
Business
Requirements
Non-functional
Business
Requirements
Business
Process
Message
Business
ProcessMessage Message
Actor1Actor2Actor3
Operation 1
Operation 2
Operation 3Business Objectives
Epics
Epic 1
An epic is a partition in the functional domain which realizes a
business value addition and consists of the functionalities
(stories) expected by the users for the completion of a
business process flow.
It is possible to create an epic within other.
Epic 2
Epic 4
Epic 5 Epic 6
User Stories
A user story is a defined action that
provide an observable result of to a
particular actor. It is a self-contained unit
User
Story 1
User
Story 2
User
Story nEpic 3