Slide 1

Charles Bozonier, CBAP Principal Business Analyst, REI Business Analysis Certificate Instructor charlesbozonier@gmail.com Slide 2 1. Establish a standard business rule method 2. Leverage business rules with decision modeling 3. Utilize decision models to support agile development. Slide 3 Rule Structure Define Rule Relationships CollectRefineReview Slide 4 $44.40 on Amazon $40.46 on Amazon Slide 5 Solid foundational structure down to the sentence structure of the individual rule We are building an asset that will: Endure for years Enable agile development There is an optimal way to work Slide 6 Focus on highest value Focus on rules buried in system logic Slide 7 Current State Review Rules captured offline in declarative statements Confirmed and refined with business present Reviewed in final form at the user level Declarative Structure - The 4 Rule Types Basic List Enumerative Quantitative Slide 8 Basic constraint pattern: Most business rules will fit in this basic pattern: (must | should) [ not ] [(if | unless) ]. Example of basic pattern: A customer must provide the Card Identification number of the credit card used when purchasing online. Slide 9 Appropriately accessible by defined roles Readily shared with the enterprise Readily updated by Business Analysts Relational structure is supported Slide 10 Designated individuals who understand the rule structure, and can be held responsible for their quality Typically supported by the BA in alignment with the business owners designates. Slide 11 In the order of the related processes criticality or value High value rules first High volume or high risk processes rank over lower volume or lower risk processes. Slide 12 Rules are individual statements. However, rules are applied in combination with other rules Rules may be organized in families Rule families are best understood when modeled These combinations are referred to as business logic Slide 13 1. Defines the business logic asset 2. Simple structure, declarative nature and optimal integrity 3. Easily implemented in technology 4. Neither language nor a grammar It is a model 5. Effectively manage business logic and rules not as lists referenced in a model but in a model of their own. Slide 14 Business people readily engaged Decision models are pre-work Other models are simplified Decision models are reusable Test scripts can be developed sooner Better business logic quality means less errors Slide 15 Lets capture some business rules, model a decision, write an agile story and model a decision in the time we have left. Slide 16 The Business Rules An online customer is only sent business service information messages to their mobile device. Business Service Information is defined as communications needed to inform a customer about the status of orders, product recalls and availability of backordered items. An online customer without a mobile device must notified via email about order status. Slide 17 The Decision Model Mobile device messaging rule family Condition Conclusion Business Service Information Mobile Contact Number IsYesIsYesSend message to mobile device IsNoIsYesDo not send message to mobile device IsYesIsNoSend email message Slide 18 User Story I am a customer and I want a message to be sent to my mobile device when my order is available for pick up so that I will be able to pick it up when I am on the go. Slide 19 Conclusion Condition Business Decision Condition Send message to mobile device Business Service Information is YES Mobile device messaging Mobile Contact Number is YES Slide 20 S eparate the business decisions from all other aspects including process T race the business logic from motivation to code and to manual processes E xpress the business logic plainly P osition the business logic for change Slide 21 So much more to talk about! Questions?