Effectively capturing and managing requirements is critical in any IT project. Business analysts and others gathering requirements know how to capture and document processes, data and user tasks. But what about the decisions at the heart of your business? How can you effectively identify, document and model the repeatable, operational decisions crucial to success with business rules and predictive analytics? In this webinar we will share practical advice developed from real-world customer projects.
3. AGENDA
1 2
Why Reinvent
Requirements?
Beginning with
Decisions
3
Putting Decisions
in Context
4 5 6
Detailed Questions and A Final Thought
Decision Answers
Requirements
24. Good Decision Requirements
Information Know-how
• What is needed? • How to make it
• Where does it come • How to improve it
from?
Precision Automation
• Exactly how? • All automated?
• How to avoid • If not, how much can
technical details? be and for whom?
27. Discovering Decisions From Process
• A business process model can be an effective
source for identifying high-level decisions
• Prioritize decisions to know where to start
29. Simple Supporting Decision
• Larger node is the subject
of the diagram
• Context established by
drilling down from high-
level decision
• Only the dependencies of
the subject decision are
shown
• All of the business logic is
defined in the supporting
decisions
30. A More Involved Example
• Multiple layers of
decision
dependencies
• Abstraction of full
story
• 3 different patterns
of how to handle
different states
• 1 state breaks all
patterns and has
separate diagram
32. A Tricky Decision Decomposition
• A seemingly simple decision was complicated
by lots of exceptions to the basic business
rules
• Discovering the proper decomposition was key
to defining a satisfactory solution
33. Initial Attempts
• Business rule requirements
initially gathered as an
unorganized list
• A manageable number of
business rules, but with lots
of seemingly complicated
exceptions
• 3 initial attempts to
synthesize a decision
structure from the bottom
up failed to support the
business rule requirements
34. Successful Decision Decomposition
• Partial solution by
eliminating
exceptions
• Switched analysis
from negative rules to
positive rules
• Complete solution
found after refocusing
on a top down
approach
35. Rule Family Template
• Business rules are defined in rule families
• Multiple conditions, one conclusion
• A message explaining each negative rule
36. Sample Business Rules
• Simplified version with exceptions removed
• Key elements are
– Negative rules contain business rule statements
– Positive rules complete full coverage