Home Page Icon
Home Page
Table of Contents for
D. The Business Rules Group and David C. Hay Modified Motivation Model
Close
D. The Business Rules Group and David C. Hay Modified Motivation Model
by David C. Hay
Requirements Analysis: From Business Views to Architecture
Copyright
Dedication
Foreword
Preface
The Inspiration for This Book: Object-Oriented Analysis
About the Book
The Important Stuff
Acknowledgments
Introduction
About Requirements Analysis
History
Structured Techniques
Information Engineering
Object orientation
From Analysis to Design
About This Book
System Development Life Cycle
Architecture Framework
The Framework and Requirements Analysis
1. A Framework for Architecture
The Zachman Framework
The Rows
The Columns
The Architecture Framework
The Analysis Process
Data
Activities
Locations
People and Organizations
Timing
Motivation
Implications
2. Managing Projects
Introduction
Summary of Development Phases
About Strategy
Articulation
Definition
About Requirements Analysis
Process One: Define Scope
Process Two: Plan the Process
Process Three: Gather Information
Step 1: Conduct Briefing
Step 2A: Conduct Interviews
Step 2B: Joint Application Development (JAD) and Feedback Sessions
Step 3: Obtain Industry Information and Patterns
Step 4: Examine Current Systems
Step 5: The Deliverable
Process Four: Describe the Enterprise
Step 1: Define Data Models (See Chapter 3)
Task 1: Create Business Data Model
Task 2: Create Conceptual Data Model
Step 2: Define Activity Models (See Chapter 4)
Task 1: Identify Current Business Processes
Task 2: If Appropriate, Create Essential Data Flow Diagrams
Task 3: If Appropriate, Create IDEF0 Diagram
Task 4: If Appropriate, Create Function Hierarchy
Task 5: Create Function/Data Map
Step 3: Define Location Models (See Chapter 6)
Task 1: Describe Location Network
Task 2: Define Roles, Data-Distribution Requirements
Step 4: Define People and Organization Models (See Chapter 5)
Task 1: Articulate Organizational Philosophy
Task 2: Create Organization Chart, Including Descriptions of Lateral Communications and Roles
Task 3: Map Organization to Viable Systems 1–5
Task 4: Define Information Requirements, by Role
Step 5: Define Event and Timing Models (See Chapter 7)
Task 1: If Appropriate, Create Essential Data Flow Diagram
Task 2: If Appropriate, Create State/Transition Diagrams
Task 3: If Appropriate, Create Entity Life Histories
Step 6: Define Motivation Models (See Chapter 8)
Task 1: Describe Background
Task 2: Define Ends and Means
Task 3: Articulate Business Policies
Task 4: Define Business Expression of Business Rules
Task 5: Map Business Rules to Data Model
Task 6: Map business rules to function model
Step 7: Present Models
Step 8: Deliverables: Model Descriptions
Process Five: Define What Is Required of a New System
Step 1: Restate Project Purpose
Step 2: Identify Key Players
Step 3: Identify Required Capabilities
Task 1: Identify Missing Data
Task 2: Identify Missing Functions
Task 3: Propose Systems and Define Use Cases for Them
Step 4: Identify Requirement Constraints
Step 5: Identify Non-functional Requirements
Task 1: Identify Quality Requirements
Task 2: Define Response-Time Requirements
Task 3: Define Look and Feel Requirements
Task 4: Define Security Requirements
Task 5: Define Cultural and Political Requirements
Task 6: Define Legal Requirements
Step 6: Determine Level of Technology
Step 7: Identify Capacity Requirements
Step 8: Decide Whether to Make or Buy
Step 9: Deliverable: Requirements Statement
Process Six: Determine the Existing Systems Environment
Step 1: Define Operating Environment
Step 2: Identify Software Environment
Task 1: Identify Development Tools
Step 3: Define Technological Architecture
Step 4: Define Operational Procedures
Step 5: Identify Existing Capacity
Step 6: Deliverable: System Inventory
Process Seven: Plan for Transition
Step 1: Begin Reorganization
Step 2: Begin Education
Step 3: Prepare for Training
Step 4: Prepare for Data Conversion
Step 5: Prepare for Implementation of Hardware and Software
Step 6: Deliverable: Transition Plan
Summary
3. Column One: Data
Views of Data
A Brief History of Data Architecture
The “Application Approach” to Systems . . .
What Went Wrong?
1. Input's Connections to Output
2. Overlapping Applications
3. Encoding Business in the Programs
The Solution—Version 1
Data Management
The Solution—Version 2
Advanced Data Management—Meta-data
Graphics—Data Modeling
A Short History
Entity/Relational Modeling
Object Modeling
Object-Role Modeling (ORM)
How to Draw a Data Model
Entity Types
Sub-types and Super-types
Relationships
Attributes
Unique Identifiers
Using Entity/Relationship and Object Models
Business Owners' Views (Row Two)
Architect's View (Row Three)
Designer's View (Row Four)
Normalization
Before Normal Forms
First Normal Form
Second Normal Form
Third Normal Form
Boyce/Codd Normal Form
Fourth Normal Form
Fifth Normal Form
Data Modeling and Normalization
Object-Oriented Design
Referential Integrity
Data Modeling Conventions
Syntactic—Symbols
Positional—The Crow's Foot Rule
Semantic—Data Model Patterns
People and Organizations
Geography
Products
Activity Type/Activity
Contract
Hierarchy/Network
Type
Entity/Relationship Model Validation
The Requirements Analysis Deliverable—Column One
Entity Types and Relationships, with Narrative
Attributes
Domains
Unique Identifiers
Referential Integrity
Data and the Other Columns
Data and Activities
Data and Locations
Data, People, and Organizations
Data and Timing
Data and Business Rules
Conclusion
4. Column Two: Activities
From the Business Owners' View to the Architect's View
Approach
Function Hierarchies
Dependency Diagrams
Data Flow Diagrams
“Exploding” Processes
Context Diagram
Physical Data Flow Diagrams
Logical (“Essential”) Data Flow Diagrams
IDEF0
Syntax
Rules
Box Rules
Arrow Rules
Diagram Rules
Model Rules
The UML Activity Diagram
Interaction Diagrams
Use Cases
A Word About Business Process Re-engineering
Business Process Diagrams
Detailed Function and Process Documentation
Structured Natural Language
Format
Key Words
Action Diagrams
Decision Trees and Decision Tables
Other Hierarchical Techniques
Implications of Analyzing Activities
Implications for Relational Design
Implications for Object-Oriented Design
The Requirements Analysis Deliverable—Column Two
A Comparison of the Techniques
Activities and the Other Columns
Activities and Data
Activities and Locations
Activities and People
Activities and Timing (Events)
Activities and Motivation
5. Column Four: People and Organizations
How to Organize the Enterprise (Row One)
Row Two: The Business Owner's View
Times Change...
A Very Short History of the World
Human Capital
Structural Capital
Customer Capital
Requirements for Knowledge Management
The New Workplace and Knowledge Management
Row Three: The Nature of a (Human) System
A System
Management
A Model of the Viable System—System One
Freedom
System Two: Dampen Waves
System Three: Achieve Synergy
System Four: Opportunities
System Five: System Identity
Extra Communication Channels
Implications of This Model
Information Overload
Jobs
Our Personal Lives
System Use
Requirements Analysis Deliverable—Column Four
People, Organizations, and the Other Columns
People and Data
People and Activities
People and Locations
People and Timing
People and Motivation
6. Column Three: Locations
Row Two—Geography
Headquarters and Field Offices
Production Network
Distribution Network
Research Network
Customer Locations
The Set of Sites
Row Three—Network (and the Other Columns)
Column One: Where Are Data Created? Where Are They Used?
Column Two: Which Functions Are Where?
Column Four: Which Roles Are Where?
Column Five: What Events Are Where?
Column Six: Which Business Rules Are Where?
The Requirements Analysis Deliverable—Column Three
7. Column Five: Timing
Introduction
Row One: Scope
Row Two: The Business Owner's View
Schedules
Events and States
State/Transition Diagram
Row Three: The Architect's View
Events and States
Essential Data Flow Diagrams
Entity Life Histories
A Data Model
Events
Event/Entity Type Matrix
Asset Type
Physical Asset
Site
Contract
Line Item
Movement
Activity Fragments
The Requirements Analysis Deliverable—Column Five
Timing and the Other Columns
Timing and Data
Timing and Activities
Timing and Locations
Timing, People, and Organizations
Timing and Motivation
Conclusion
8. Column Six: Motivation
Introduction
Row One: Scope
Row Two: Business Owners' Views
End
Goal
Objective
Means
Course of Action
Element of Guidance
Assessment
Discovering Rules
Row Three: Architect's View
Classes of Rules
Terms and Definitions
Facts
Rules
Derivations
Constraints
Action Enabler Rules
Quality Criteria
Rule Descriptions
Natural Language
Object Constraint Language
Ronald Ross Notation
Instance Verifiers
Type Verifiers
Position Verifiers
Functional Verifiers
Comparative Evaluators
Mathematical Evaluators
Projection Controllers
Object-Role Modeling (ORM)
Entity Types, Attributes, and Relationships
About Constraints
Mandatory Roles
Uniqueness
Objectified Relationships
Occurrence Frequency
Derivations
Value Constraints
Set Constraints—Subsets
Set Constraints—Join Subset Constraint
Set Constraints—Equality
Set Constraints—Exclusion
Ring Constraints
Other Constraints
Rule Patterns
Business Rule Patterns—CASEtech, Inc.
Requirements Analysis Deliverable—Column Six
Motivation and the Other Columns
Motivation and Data
Motivation and Activities
Motivation and Locations
Motivation, People, and Organizations
Motivation and Timing
Conclusion
A. The Zachman Framework
B. A Comparison of Data Modeling Techniques(Syntactic Conventions)
Peter Chen
Entity Types and Attributes
Relationships
Cardinality/Optionality
Names
Unique Identifiers
Sub-types
Constraints between Relationships
Comments
Information Engineering
Entity Types and Attributes
Relationships
Names
Cardinality/Optionality
Unique Identifiers
Sub-types
Constraints between Relationships
Comments
Richard Barker's Notation (as Used by Oracle Corporation)
Entity Types and Attributes
Relationships
Cardinality/Optionality
Names
Unique Identifiers
Sub-types
Constraints between Relationships
Comments
IDEF1X
Entity Types and Attributes
Relationships
Cardinality/Optionality
Names
Unique Identifiers
Sub-type
Constraints between Relationships
Comments
Object-Role Modeling (ORM)
Entity Types and Attributes
Relationships
Cardinality/Optionality
Names
Unique Identifiers
Sub-types
Constraints between Relationships
Comments
The Unified Modeling Language (UML)
Entity Types (Object Classes) and Attributes
Relationships (Associations)
Cardinality/Optionality
Names
“Part of/composed of”
Unique Identifiers
Sub-types
Constraints between Relationships
Comments
Extensible Markup Language (XML)
What Is It?
Entity Types and Attributes
Cardinality/Optionality
Names
Unique Identifiers
Sub-types
Constraints between Relationships
Comments
Recommendations
For Analysis—Richard Barker's Notation
Aesthetic simplicity
Completeness
Language
For Object-Oriented Design—The UML
For Relational Design—IDEF1X
Summary
C. The Business Rules Group Motivation Model
D. The Business Rules Group and David C. Hay Modified Motivation Model
Glossary
Bibliography
Search in book...
Toggle Font Controls
Playlists
Add To
Create new playlist
Name your new playlist
Playlist description (optional)
Cancel
Create playlist
Sign In
Email address
Password
Forgot Password?
Create account
Login
or
Continue with Facebook
Continue with Google
Sign Up
Full Name
Email address
Confirm Email Address
Password
Login
Create account
or
Continue with Facebook
Continue with Google
Prev
Previous Chapter
C. The Business Rules Group Motivation Model
Next
Next Chapter
Glossary
Appendix D. The Business Rules Group and David C. Hay Modified Motivation Model
Copyright © The Business Rules Group (Used with permission)
Add Highlight
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click
here
login for view all page.
Day Mode
Cloud Mode
Night Mode
Reset