Writing effective business rules a practical method
Writing Effective Business Rules moves beyond the fundamental dilemma of system design: defining business rules either in natural language, intelligible but often ambiguous, or program code (or rule engine instructions), unambiguous but unintelligible to stakeholders. Designed to meet the needs of b...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Boston :
Morgan Kaufmann
2012.
|
| Edición: | 1st edition |
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627797106719 |
Tabla de Contenidos:
- Front Cover; Writing Effective Business Rules: A Practical Method; Copyright; Dedication; Contents; Acknowledgments; Introduction; Is this book for you?; What this book is about; How this book is organized; How to use this book; Some typographical conventions; Chapter 1: The world of rules; 1.1. What is a business rule?; 1.1.1. Laws of physics; 1.1.2. Legislation, regulations, external standards, and best practices; 1.1.3. Rule or business rule?; 1.1.4. System rule or business rule?; 1.2. Why rules are important; 1.3. Best practice rule management; 1.4. The nature of the problem
- 1.5. The solutions1.5.1. Constrained natural language; 1.5.1.1. The benefits of expressing rules in natural language; 1.5.1.2. The benefits of standardized vocabulary; 1.5.1.3. The benefits of standardized syntax; 1.5.2. The benefits of a rule repository; 1.5.3. The benefits of rule metadata; 1.6. Summary; Chapter 2: How rules work; 2.1. Operative rules; 2.2. Definitional (structural) rules; 2.3. Normative, prescriptive, and descriptive rules; 2.4. Business processes; 2.4.1. Characteristics of a business process; 2.4.2. How rules govern business processes; 2.5. Rules in user interfaces
- 2.6. Rules governing electronic messages2.7. Rules ensuring database integrity; 2.8. Human activities other than business processes; 2.9. Summary; Chapter 3: A brief history of rules; 3.1. Implementing rules; 3.1.1. Rules in program code; 3.1.2. Decision tables; 3.1.3. Rule sets in data; 3.1.4. Database constraints; 3.1.5. Graphical user interface building tools; 3.1.6. Constraints in XML schemas; 3.1.7. Rules engines; 3.2. Documenting rules; 3.2.1. Rules in data models; 3.2.1.1. Entity-relationship models; 3.2.1.2. Object-role modeling; 3.2.1.3. UML; 3.2.2. Rules in business process models
- 3.3. Recent developments3.3.1. Ross's rule taxonomy and diagramming notation; 3.3.2. Expressing rules in natural language; 3.3.2.1. Verbalization of ORM models; 3.3.2.2. My 1999 paper; 3.3.2.3. RuleSpeak; 3.3.2.4. Morgan's rule patterns; 3.3.2.5. Assertions; 3.3.3. The Business Rules Approach; 3.3.4. The Business Rules Manifesto; 3.3.5. The SBVR; 3.3.6. Rules and rule statements; 3.3.7. Rule statements and advice statements; 3.3.8. Types of rule statements; 3.3.8.1. Procedural and declarative rule statements; 3.3.8.2. Structural assertions, action assertions, and derivations
- 3.3.8.3. Operative rule statements3.3.8.4. Definitional (structural) rule statements; 3.3.9. Types of advice statements; 3.3.9.1. Statements of advice of permission; 3.3.9.2. Statements of advice of possibility; 3.4. Summary; Chapter 4: Types of rules; 4.1. Rules governing the physical world; 4.1.1. Mandatory and optional attributes and relationships; 4.1.2. Single-valued and multi-valued attributes and relationships; 4.1.3. Variant and invariant attributes and relationships; 4.1.4. Constraints between attributes; 4.1.5. The impact of the physical world on an organization's rule book
- 4.2. Legislation and regulations
