Business Rules 12 th Meeting Course Name: Business Intelligence Year: 2009.

Slides:



Advertisements
Similar presentations
Testing Workflow Purpose
Advertisements

IT Requirements Capture Process. Motivation for this seminar Discovering system requirements is hard. Formally testing use case conformance is hard. We.
Object-Oriented Analysis and Design
Planning and Strategic Management
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Fundamentals of Information Systems, Second Edition
Internal Control in a Financial Statement Audit
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
SYSTEMS ANALYSIS. Chapter Five Systems Analysis Define systems analysis Describe the preliminary investigation, problem analysis, requirements analysis,
The chapter will address the following questions:
MDC Open Information Model West Virginia University CS486 Presentation Feb 18, 2000 Lijian Liu (OIM:
Katanosh Morovat.   This concept is a formal approach for identifying the rules that encapsulate the structure, constraint, and control of the operation.
Implementation Yaodong Bi. Introduction to Implementation Purposes of Implementation – Plan the system integrations required in each iteration – Distribute.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
BSBPMG502A Manage Project Scope Manage Project Scope Project Scope Processes Part 1 Diploma of Project Management Qualification Code BSB51507 Unit.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Chapter 10 Information Systems Analysis and Design
Testing Workflow In the Unified Process and Agile/Scrum processes.
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 10 Use Case Design.
Management & Development of Complex Projects Course Code MS Project Management Perform Qualitative Risk Analysis Lecture # 25.
Using Publicly Available Data 20 th Meeting Course Name: Business Intelligence Year: 2009.
1 Introduction to Software Engineering Lecture 1.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
GRASP: Designing Objects with Responsibilities
Planning for Success 7 th - 8 th Meeting Course Name: Business Intelligence Year: 2009.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
9-1 © Prentice Hall, 2007 Chapter 9: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
1 What is OO Design? OO Design is a process of invention, where developers create the abstractions necessary to meet the system’s requirements OO Design.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
“A Truthful Evaluation Of Yourself Gives Feedback For Growth and Success” Brenda Johnson Padgett Brenda Johnson Padgett.
Requirement engineering Good Practices for Requirements Engineering
McGraw-Hill/Irwin © 2003 The McGraw-Hill Companies, Inc., All Rights Reserved. 6-1 Chapter 6 CHAPTER 6 INTERNAL CONTROL IN A FINANCIAL STATEMENT AUDIT.
PRJ566 Project Planning & Management Software Architecture.
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
7-1 © Prentice Hall, 2007 Topic 7: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
Information Integration 15 th Meeting Course Name: Business Intelligence Year: 2009.
Data Profiling 13 th Meeting Course Name: Business Intelligence Year: 2009.
Requirements Analysis
Data Warehouses, Online Analytical Processing, and Metadata 11 th Meeting Course Name: Business Intelligence Year: 2009.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
Knowledge Discovery and Data Mining 19 th Meeting Course Name: Business Intelligence Year: 2009.
Business Models and Information Flow 10 th Meeting Course Name: Business Intelligence Year: 2009.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
What is a software? Computer Software, or just Software, is the collection of computer programs and related data that provide the instructions telling.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
Modeling data in the Organization
Chapter 1 The Systems Development Environment
Analysis Classes Unit 5.
Chapter 1 The Systems Development Environment
Object-Oriented Software Engineering Using UML, Patterns, and Java,
Unified Modeling Language
Chapter 1 The Systems Development Environment
TechStambha PMP Certification Training
Chapter 1 The Systems Development Environment
Slides by Steve Armstrong LeTourneau University Longview, TX
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Vocabulary Algorithm - A precise sequence of instructions for processes that can be executed by a computer Low level programming language: A programming.
Information Analysis, Organization, and Presentation
Use Case Analysis – continued
Chapter 1 The Systems Development Environment
TECHNICAL REPORTS WRITING
Presentation transcript:

Business Rules 12 th Meeting Course Name: Business Intelligence Year: 2009

Bina Nusantara University 3 (2).Loshin, David (2003). Business Intelligence: The Savvy Manager’s Guide. Chapter 7 Source of this Material

The Business Case Sometimes business rules are applied by a data analyst sitting in front of a database front end, and sometimes rules have been documented as program logic. A business rules system is designed to capture the knowledge of all the assertions, constraints, guidelines, policies, regulations, etc. that drive a business process and manage that knowledge as a corporate asset. What follows are some of the major advantages of implementing business process using a business rules system. Encapsulation of Successful Business Logic Componentized Development Speed of Implementation Ease of Modification and Rapid Response to Change Reuse Persistence of Encapsulation of Business Knowledge Augmented Capabilities Bina Nusantara University 4

The business rules approach takes into consideration the encapsulation of business logic for the purpose of identifying or highlighting entities or events within a system. In essence, a business rules approach is meant to capture and subsequently automate the repetitive operations that have been properly vetted in term of business value so that analyst resources can be engaged in discovering new opportunities for improvement or adding value. A business rules approach integrates the following: Technology Workflow Information Bina Nusantara University 5 The Business Rules Approach

According to the business Rule Group, a business rule is a directive intended to command and influence or guide business behavior, in support of business policy that is formulated in response to an opportunity or threat. From the information system perspective, a business rule is a statement that defines or constrains some aspect of the business. It is intended to assert business structure or to control or influence the behavior of the business. From a practical standpoint, a business rule asserts a statement about the state of a business process or a directive describing changes in the state of a business process. More simply, a business rule dictates what happens when a sequence of inputs is applied to one or more well-described scenarios. Bina Nusantara University 6 What is a Business Rule?

Rule Basics In business system, rules form the programmed representation of business policies and practices. A rule is a statement that assert some truth about the system, along with optional actions to be performed, depending on the assertion’s truth value. Definitions and Specifications In system o rules, there must be a well-defined, agreed-upon “vocabulary” for rule specification; we can then enumerate the participants within the system along with the descriptive “nouns” and “verbs” that are used in describing the business process. Assertions Assertions are statement about entities within the system that express sensible observation about the business. Assertions describe relationships between entities and activities within the framework. Constraints Constraints express unconditional conformance to a business statement; compared to a constraint, a data instance either conforms to that constraint or violates it. Bina Nusantara University 7 What is a Business Rule? (cont…)

Guidelines A guideline expresses a desire about the state of the system or a warning about a potential change in the system. A violation of a guideline may indicate a change in business process that requires attention. Actions An action is any operation that changes the system state, typically as a result of the violation of some constraint or guideline. Triggers A trigger specifies a collection of conditions and the initiation of an action contingent upon the condition’s value. Triggers may combine constraints or guidelines with actions. Inference An inference specifies a collection of conditions establishing a fact that becomes true a by-product of changes within the states of the system. An inference is essentially a new piece of information derived from the system state; when an inference rule is executed, that new piece of information must be integrated into the system state. Bina Nusantara University 8 What is a Business Rule? (cont…)

A business rules system encapsulates sets of environment states, environment variables, and formally defined rules that reflect business policies, preferences, guidelines, triggers, etc. and how the environment is affected based on those rules. A business rules system incorporates the following components. A rule definition framework A persistent rule base A rule engine An execution framework Bina Nusantara University 9 What is a Business Rule System?

Rules Definition All rules-based system employ some kind of rules language as a descriptive formalism for describing all the aspects of the business process, including the system states, the actors, the inputs and events, the triggers, and the transitions between state. A rule language is a framework for describing sets of rules. Rule Engines A rules engine is an application that takes as input a set of rules, creates a framework for executing those rules, and acts as a monitor to a system that must behave in conjunction with those rules. Rules engine work together with a rules languages. Bina Nusantara University 10 What is a Business Rule System? (cont…)

There are many sources for rules, such as conversation with people, design documents, laws, regulations, and program codes, to name a few. Each of these source may be rich in business rules, but because of the peculiarities of each source, the extraction of rules from each requires different skills. People Conversation with SMEs are likely to yield a treasure trove of business rules, especially when these conversations are prompted as a result of previous iterations of analysis. Documentation Documentation is a rich source of business rules, because documentation frequently does not remain synchronized with what is being documented. Descriptive text is rich with rules. Regulations Organizations that are bound by a governing a board’s set of regulations may find that regulations are an excellent source of business rules. Laws and regulations, Bina Nusantara University 11 Source of Business Rules

directives, and even suggestions by governing organizations or industry consortia are good sources for business rules. Program Code One stickier problem in rule discovery is extracting business rules from existing application programs. Alternatively there have been some suggested tools to perform what could be called “code mining”. Turning Language into Rules A major benefit of the business rules approach is that analyzing a business process, provides a mechanism for extracting BI from program logic and allowing it to be treated as content. The rule analysis process leads toward the ability not just to isolate intelligence rules, but also to identify terms, facts, and assertions about the business entities that typically modeled in a database. The Value of Subject Matter Experts Having business-savvy staff or SMEs on the team will ease that process. Bina Nusantara University 12 Source of Business Rules (cont…)

Management Issue When deciding to develop a system using the business rules approach, consider what the system should look like after it is built, and enumerate all the rules that specify our expectations about how that system works. These expectations are the seeds of our business rules. Political Issues Similar to other components of a BI program, a big roadblock to a successful business rule implementation is a social issue, not technical one, for a number of reasons.  Risk Assessment  Turf Concern  High Expectations Limitations of The Approach There are of course limitations to the use of business rules.  Detail Management  Inflated Expectations  Programmers are not eliminated Bina Nusantara University 13

End of Slide Bina Nusantara University 14