More Related Content Similar to 20140408 knowledge partners international iiba (20) 20140408 knowledge partners international iiba13. © 2014 Knowledge Partners International LLC – www.kpiusa.com – www.thedecisionmodel.com
Align the Vision of Stakeholders (Scope): Row 1
• Represents the view of the “Executive”, i.e. the
Business Context Planner
• Each Column consists of “Scope Contexts”, i.e.
Scope Identification Lists
List of Inventory
Types
Concepts in the
Glossary within
Scope, e.g.:
Customer,
Vendor,
Inventory Item;
Loan
Property
Repayment Term
List of Process
Types
Specific high level
processes in the
scope, e. g.:
Assign Taxpayer
ID Number,
Initiate Taxpayer
Account, Process
Taxpayer Annual
Return, etc.
List of Distribution
Types
Locations of
consequence, e.g.:
Warehouses,
Primary Customer
locations, Network
Centers, other
location specific
cases
List of Responsibility
Types
External and
internal
Organizations
and Roles of
importance to
the business.
List of Time
Types
Important
Events, dates,
timelines, and
schedules of
importance.
Sequencing
information that
impact
processes and
events
List of Motivation
Types
Business
Motivations and
objectives and the
decisions by which
the objectives are
implemented.
15. © 2014 Knowledge Partners International LLC – www.kpiusa.com – www.thedecisionmodel.com
Using the Zachman Framework to Select the Models: Row 2
• Represents the view of the “Executive” or “Business
Concept Owners”
• Each Column consists of “Business Concepts”, or
“Business Definition Models”
Inventory
Definition
Business Entity,
Business
Relationship e.g.:
Data Dictionary,
Glossary, Conceptual
Data Model
Process
Definition
Business Transform,
Business
Input/Output e.g.:
Silver Level 1
Business Processes;
User Stories;
Use Cases
Distribution
Definition
Business Location,
Business
Connections e.g.:
Logistic networks,
communication
networks, Geo‐
spatial relationships
Responsibility
Definition
Business Role,
Business Work
Product, e.g.:
Organization
Structures and
responsibilities,
Customer and Vendor
Networks, industry
organizations.
Timing
Definition
Business Interval,
Business moment
e.g. event models,
business schedules,
time lines
Motivation
Definition
Business End and
Business Means e.g.
Motivation Models,
Business Decision
Models, Quantitative
Business Models.
Strengths, Weaknesses,
Opportunities and
Limitations (SWOT)
Visualizations
20. © 2014 Knowledge Partners International LLC ●www.kpiusa.com ● www.thedecisionmodel.com 20
Rule ID Rule Object Focus Conclusion subject Conclusion
1.1
Fraud Dept Account Block
All non‐financial transactions must be declined across all bank channels Account Fraud status Closure eligibility OK / HR
1.5
Fraud Dept Account Block
All non‐financial transactions must be declined across all bank channels Account Fraud status Closure eligibility OK / HR
1.8
Fraud Dept Account Block
11. A message must be displayed at account level in all front end user systems ‘Fraudulent Account – Refer to
Special Investigations Dept’ for non‐financial transactions Account Fraud status Mediated message requirement OK / HR
1.10
Fraud Account Block
'The current account statement must not be printed Account Fraud status Account statement eligibility OK / HR
1.11
Fraud Account Block
'No correspondence can be mailed to the customer
Account Fraud status
Account mailed correspondence
eligibility OK / HR
2.1
Lost Card
'IF in Branch/Over the counter transaction AND Lost card is used (Swiped)
THEN the transaction must initially be declined with the message "Warning ‐ Lost card ‐ do you wish to
continue?"
Note. The bank user may choose to continue or abort the transaction Card Lost / stolen status Closure eligibility OK / SR
3.2
Stolen Card
IF in Branch/Over the counter transaction AND non financial transaction (excluding Enquiries)
AND Stolen card is used (Swiped)
THEN the transaction must initially be declined with the message "Warning ‐ Stolen card ‐ do you wish to
continue?"
Note. The bank user may choose to continue or abort the transaction Card Lost / stolen status Closure eligibility OK / SR
5.5
Criminal Financial Court Order
Account Closure is not permitted. Unless by an authorised SID user.
Note this will be achieved by the temporary removal of the inhibit by SID Account
Financial court
order status Closure eligibility OK / HR
6.8
Federal State Arrestment Order
'IF a Federal State Arrestment is in place
THEN an account must not be closed Account
Federal state
arrestment order
status Closure eligibility OK / HR
7.1
UN Sanction
Account Closure is not permitted. Unless by an authorised SID user.
Note this will be achieved by the temporary removal of the inhibit by SID Account UN sanctions status Closure eligibility OK / HR
8.2
Missing Address Flag
IF a customer's account is locked because of Missing Address
OR a customer's card is locked because of Missing Address
THEN a message must be displayed on mediated systems
Note: a mediated system is defined as one which is operated by an authorised bank user (e.g. a bank
employee or an agent acting on behalf of bank)This system may or may not be in the presence of an bank
Customer. Customer
Missing Address
status Mediated message requirement OK / HR
Copyright ©2014 SAP. Reprinted with permission.
The Legacy Method of Maintaining Business Rules
22. © 2014 Knowledge Partners International LLC ●www.kpiusa.com ● www.thedecisionmodel.com 22
Linked e‐Products Orphan Status in
Relation to Sole Account Closure
_________________
‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐
Additional Open Current Accounts held by
Account Holder Count
Linked e‐Products in Relation to Account
Closure Count
Linked e‐Products Orphan Status in
Relation to Joint Account Closure
_________________
‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐
Additional Open Joint Current Accounts
held by Account Holders Count
Additional Open Current Accounts held by
Account Holder 1 Count
Additional Open Current Accounts held by
Account Holder 2 Count
Linked e‐Products held jointly by both
members in Relation to Joint Account
Closure Count
Linked e‐Products not held jointly by both
members in Relation to Joint Account
Closure Count
Linked e‐Bonds Orphan Status in
Relation to Joint Account Closure
_________________
‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐
Additional Open Joint Accounts Held by
Same Account Holders Count
Linked e‐Bonds Held Jointly by Both
Members in Relation to Joint Account
Closure Count
Linked e‐Bonds Not Held Jointly by Both
Members in Relation to Joint Account
Closure Count
Linked e‐Bonds Orphan Status in
Relation to Sole Account Closure
_________________
‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐ ‐
Additional Open Sole Accounts held by
Account Holder Count
Linked e‐Bonds Count in Relation to
Account Closure Count
Overall decision
Locks Pending items
Linked e‐products /
e‐bonds
Customer
locks
Account
locks
Card locks
Orphaned e‐
bonds
Orphaned e‐
products
Sole account
Sole
accounts
Joint
accounts
Joint
accounts
Copyright ©2014 SAP. Reprinted with permission.
Simplifying Complexity
23. © 2014 Knowledge Partners International LLC ●www.kpiusa.com ● www.thedecisionmodel.com 23
Copyright ©2014 SAP. Reprinted with permission.
Account Closure Simulation Eligibility
Row
ID
Rule
Pattern
Message
Class 1
Message
1 1 is in
{Active, not yet used; Active,
used}
Is Eligible is eligible Is
Contract
Present Date
is in
{Close,
Close and log}
is Eligible
2 1 is in
{Active, not yet used; Active,
used}
Is Eligible is eligible Is
Contract
Present Date
is soft reject is Soft reject
3 2 is in
{Active, not yet used;
Active, used}
Is Not Eligible is Not Eligible
There is a lock on the account &1 which
prevents account closure
4 1 is in
{Active, not yet used;
Active, used}
Is Soft Reject is eligible Is
Contract
Present Date
is in
{close, Close and
log, Soft reject}
is Soft Reject There is a lock on the account &1
5 3 is in
{In Release, Process, Created;
Being Terminated; Terminated}
is Not Eligible Account &1 is already terminated
6 4 is in
{Active, not yet used;
Active, used}
is Not eligible is Not Eligible
Closure not possible ‐ Outstanding
Pending Items
7 5 is in
{Active, not yet used;
Active, used}
Is Not
Contract
Present Date
is Not Eligible
Specified Value Date &1 should be the
same as A/C Presence date &2
Conclusion Messages
Account Closure
Simulation
Pending Items
Account Closure
Simulation Account
Closure Date
Account Closure
Simulation linked e‐
product capability
Account Closure Simulation Account
Status
Account Closure
Simulation Lock
Eligibility
Conditions
Account Closure
Simulation Eligibility
Drilling Deeper…
26. © 2014 Knowledge Partners International LLC ●www.kpiusa.com ● www.thedecisionmodel.com 26
Copyright ©2014 SAP. Reprinted with permission.
Account Closure Simulation Eligibility
Row
ID
Rule
Pattern
Message
Class 1
Message
1 1 is in
{Active, not yet used; Active,
used}
Is Eligible is eligible Is
Contract
Present Date
is in
{Close,
Close and log}
is Eligible
2 1 is in
{Active, not yet used; Active,
used}
Is Eligible is eligible Is
Contract
Present Date
is soft reject is Soft reject
3 2 is in
{Active, not yet used;
Active, used}
Is Not Eligible is Not Eligible
There is a lock on the account &1 which
prevents account closure
4 1 is in
{Active, not yet used;
Active, used}
Is Soft Reject is eligible Is
Contract
Present Date
is in
{close, Close and
log, Soft reject}
is Soft Reject There is a lock on the account &1
5 3 is in
{In Release, Process, Created;
Being Terminated; Terminated}
is Not Eligible Account &1 is already terminated
6 4 is in
{Active, not yet used;
Active, used}
is Not eligible is Not Eligible
Closure not possible ‐ Outstanding
Pending Items
7 5 is in
{Active, not yet used;
Active, used}
Is Not
Contract
Present Date
is Not Eligible
Specified Value Date &1 should be the
same as A/C Presence date &2
Conclusion Messages
Account Closure
Simulation
Pending Items
Account Closure
Simulation Account
Closure Date
Account Closure
Simulation linked e‐
product capability
Account Closure Simulation Account
Status
Account Closure
Simulation Lock
Eligibility
Conditions
Account Closure
Simulation Eligibility
Account Closure Simulation Card Lock Status Eligibility
Row
ID
Rule
Pattern
Message
Class 1
Message Class 2
1 1
is
Not
in
{Lost Card,
Stolen Card}
is Eligible
2 2 Is in
{Lost Card,
Stolen Card}
Is Active Is Nucleus is Not Eligible Closure not possible ‐ Lock &1
3 2 Is in
{Lost Card,
Stolen Card}
Is Active Is BOSS is Soft Reject
Card Lock&1 on account &2 Do
you wish to proceed?
4 3 Is in
{Scheduled,
Inactive, Closed}
is Eligible
5 4
Is Not
in
{BOSS,
Nucleus}
is Not Eligible
You cannot close an account in
channel &1
Conditions Conclusion Messages
Card Lock Status
Type
Account Closure Lock
Status
Account Closure
Channel
Account
Closure
Simulation
Account Closure Simulation Lock Eligibility
Row
ID
Rule
Pattern
Message
Class 1
Message Class 2
1 1 is Eligible is Eligible is Eligible is eligible
2 1 is Soft Reject is not Not Eligible is not Not Eligible is Soft Reject Lock on customer &1 Do you wish to proceed?
3 1 is not Not Eligible is Soft Reject is not Not Eligible is Soft Reject Account lock &1 Do you wish to proceed?
4 1 is not Not Eligible is not Not Eligible is Soft Reject is Soft Reject Lock on Card &1 Do you wish to proceed?
5 2 is Not Eligible is Not Eligible Closure not possible due to customer lock &1
6 3 is Not Eligible is Not Eligible Closure not possible due to account lock &1
7 4 is Not Eligible is Not Eligible Closure not possible due to card lock &1
Account Closure
Simulation Lock
Eligibility
s Conclusion Messages
Account Closure
Simulation
Customer lock
Account Closure
Simulation
Account Lock
Account Closure
Simulation Card Lock
Status Eligibility
Seeing it in Context
35. © 2014 Knowledge Partners International LLC ●www.kpiusa.com ● www.thedecisionmodel.com 36
Iterative Development
Fix / Integrate $
$
Test
Code
Release 1
$Release 2
$
Release 3
Release 4 $
Design
Specifications
Use Cases /
Functional Specs
Requirements Gathering
Project Plan/Estimation
Level Stories
Vision & High-
Project Estimates:
• Agile gives more accurate estimates earlier in the
project
• Progress measured by tested software
Development Productivity:
• Agile teams work with their tools for
longer and become more proficient
• Seasoned Agile teams produce
software very rapidly
Architecture:
• Agile proves out architecture
sooner - significant reduction
of technical risk
End-User Feedback:
• Validates business benefits
• Makes execution more
successful
• Reduces “false features”
• Drives high IT value
Software in Production:
• Agile approach reduces time-to-
market
• Business decides when to go live
• Reduces risk of failure due to
early exit/reduction of project
scope
36. © 2014 Knowledge Partners International LLC ●www.kpiusa.com ● www.thedecisionmodel.com 37
Agile Value Proposition
Business Value
Deliver small
chunks
Deliver
frequently
Deliver what is
“done”
Focus team on
customer value
(stories)
Visibility
Iteration
demos/reviews
High customer
engagement
Continuous
feedback
Visual
information
radiators
Risk
Frequent visibility
into what is
“done”
Automate testing
Focus on quality
Inspect and
adapt the plan
Adaptability
Adapt to
customer’s
changing needs
Focus on
delivering highest
value
“Just‐in‐time”
details
Value drivers adapted from VersionOne.
40. © 2014 Knowledge Partners International LLC ●www.kpiusa.com ● www.thedecisionmodel.com 41
Iteration Zero Standard Iterations
Analysis
Design
Analysis
Design
Code
Test
TimeTime
Project Life Cycle (Development)
Iteration Zero Activities (back log)
1. Scope (Z. Row 1)
2. Select A Set Of Suitable Models and Techniques (Z. Row 2)
3. Build The First Iteration of the Models
4. Create High‐Level User Stories
5. Build High Level Visualizations (Analysis Level)
6. Document Non‐Functional Requirements
7. Size User Stories
8. Prioritize User Stories (functionality)
9. Assign User Stories To Releases
10. Establish Release Schedule
•High level processes in scope
•Concepts in the glossary in scope
•Locations of consequence
•External and internal organizations and roles
of importance
•Important events, dates, timelines and
schedules
•Business motivations and objectives and the
decisions by which the objectives are
implemented
41. © 2014 Knowledge Partners International LLC ●www.kpiusa.com ● www.thedecisionmodel.com 42
Iteration Zero Standard Iterations
Analysis
Design
Analysis
Design
Code
Test
TimeTime
Project Life Cycle (Development)
Iteration Zero Activities (back log)
1. Scope (Z. Row 1)
2. Select A Set Of Suitable Models and Techniques (Z. Row 2)
3. Build The First Iteration of the Models
4. Create High‐Level User Stories
5. Build High Level Visualizations (Analysis Level)
6. Document Non‐Functional Requirements
7. Size User Stories
8. Prioritize User Stories (functionality)
9. Assign User Stories To Releases
10. Establish Release Schedule
•Glossary
•ER Diagram
•Conceptual Data Model
•Data Flow Diagram
•Process Model (Silver Level 1)
•Use Cases
•Concept Diagrams
•Timing Diagram
•Decision Models
•Other Models As Needed
42. © 2014 Knowledge Partners International LLC ●www.kpiusa.com ● www.thedecisionmodel.com 43
Iteration Zero Standard Iterations
Analysis
Design
Analysis
Design
Code
Test
TimeTime
Project Life Cycle (Development)
Iteration Zero Activities (back log)
1. Scope (Z. Row 1)
2. Select A Set Of Suitable Models and Techniques (Z. Row 2)
3. Build The First Iteration of the Models
4. Create High‐Level User Stories
5. Build High Level Visualizations (Analysis Level)
6. Document Non‐Functional Requirements
7. Size User Stories
8. Prioritize User Stories (functionality)
9. Assign User Stories To Releases
10. Establish Release Schedule
Setting Priorities Blends:
•Business Priority and,
•Technology Priority
43. © 2014 Knowledge Partners International LLC ●www.kpiusa.com ● www.thedecisionmodel.com 44
Iteration Zero Standard Iterations
Analysis
Design
Analysis
Design
Code
Test
TimeTime
Project Life Cycle (Development)
Iteration Zero Activities (back log)
1. Scope (Z. Row 1)
2. Select A Set Of Suitable Models and Techniques (Z. Row 2)
3. Build The First Iteration of the Models
4. Create High‐Level User Stories
5. Build High Level Visualizations (Analysis Level)
6. Document Non‐Functional Requirements
7. Size User Stories
8. Prioritize User Stories (functionality)
9. Assign User Stories To Releases
10. Establish Release Schedule
Weekly Demonstrations. Attendees
Include; Executives, Stakeholders
and Extended Team
45. © 2014 Knowledge Partners International LLC ●www.kpiusa.com ● www.thedecisionmodel.com 46
Iteration Zero Standard Iterations
Analysis
Design
Analysis
Design
Code
Test
TimeTime
Project Life Cycle (Development)
Iteration Zero Activities (back log)
1. Scope (Z. Row 1)
2. Select A Set Of Suitable Models and Techniques (Z. Row 2)
3. Build The First Iteration of the Models
4. Create High‐Level User Stories
5. Build High Level Visualizations (Analysis Level)
6. Document Non‐Functional Requirements
7. Size User Stories
8. Prioritize User Stories (functionality)
9. Assign User Stories To Releases
10. Establish Release Schedule
Iteration Activities:
•Create:
•Detail User Stories
•High Fidelity Visualizations
•Completed Decision Models (includes testing and
approval)
•New Models as Needed
•Update:
•Glossary
•Data Models
•Process Models
•All Other Models As Needed
49. © 2014 Knowledge Partners International LLC ●www.kpiusa.com ● www.thedecisionmodel.com 50
Project Life Cycle (Off‐The‐Shelf)
Iteration Zero Standard Iterations
Analysis
Design Vendor Selection Activities
1. Prepare RFP (Using High Level User Stories)
2. Identify Potential Vendors and Send RFP
3. Prepare Scoring Matrix
4. Use Sores To Select Vendor Finalists
5. Prepare Scenarios (Epic User Stories)
6. Vendor Demonstrations and Interviews
7. Select Vendor/s
8. Prepare and execute a proof‐of‐concept
9. Create Gap analysis and prepare Development Plan
1. Size Gap User Stories
2. Prioritize Gap User Stories
10. Prepare Implementation Plan
1. Assign User Stories To Releases
2. Establish Release Schedule
3. Vendor Software Implementation Plan
Vendor Selection
Analysis
Design
Code
Test
Off-The-Shelf Solution
TimeTime
51. © 2014 Knowledge Partners International LLC ●www.kpiusa.com ● www.thedecisionmodel.com 52
Iteration Deliverables Cross Reference
Visualization Process Models
Glossary
Unknown Systems
(TBD)
Business Decision
Management System
BPMS (Deal and Non-Deal
workflow)
Decision
Mgmt Process
Contract Publishing
Service
Contract
Publishing
Process
TOB & nonTOB
Text & Data
Work Queue
Alerts / Requests
Enterprise
Data
Dictionary
Fact Type
Approval
Seller
Servicer
Guide
SSG Text
Process
Models
BPMN
Process
Models
Rule Requirements
(Rule Family Table
Views)
Performance
Metrics
Reporting
(Automated)
Performance
Metrics
Agreement
Data
Business
Intelligence &
Objectives
(Multiple
Sources TBD)
Business
Metrics
Guide
Bulletins
Business Decision Mgmt Future State
Rules Mgmt MISMO Release 2
Views into Negotiated Terms & Repository of Record
Deal & Non-Deal
Management
Workflow Process
Business
Decision
Views
Deal &
Non-Deal
Data
Repository
Customer
Data
Rules Mgmt
Pricing
Engine
(PMA)
Credit
Enhancements
Rule Requirements
(Rule Family Tables)
Fact Type
Request
Customer Eligibility
Criteria, TOB tie down &
Negotiated Terms
Deal
Data
Available
Negotiated
Terms
BRMS
Business
Rules Engine
(iLog)
V0.9
Pricing Workflow
Process
Business
Intent
Decision
Models
Std & Neg
Legal
Language
Components
Customer
Operational
Summery &
Views
Eligibility
Profile
Pricing
Decision
Model
Business Decision Repository
& Extensible Business Objects
Extensible
Business
Objects
Contracting
Decision Views
Contracting Views
Cust
Display
of
Pricing
Contract
Terms
Display
Cust
Decision
Views
Contract
Repository
Attribute
Definition System
(ADS)
Rule Family
Testing &
Deployment
Feedback
Test
Cases
Context Diagrams
State Diagrams
Master Committement Terms
Primary Key
"Agreement Id" [PK1] [FK]
"Master Committment Terms No" [PK2]
Non-Key Attributes
"TOB Id" [FK]
"Master Committment Terms Effective Date"
"Master Committment Terms Expiration Date"
Negotiated Terms of Business
Primary Key
"TOB Id" [PK1]
Non-Key Attributes
"TOB Assigned No"
"TOB Version No"
"TOB Description"
"TOB Effective Date"
"TOB Expiration Date"
Master Committment
Primary Key
"Agreement Id" [PK1] [FK]
Non-Key Attributes
"Master Committment Assigned N o"
"Master Committment Verions No"
Agreement
Primary Key
"Agreement Id" [PK1]
Non-Key Attributes
"Party Id" [FK]
"Agreement Effective Date"
"Agreement Expiration Date"
Master Agreement Terms
Primary Key
"Agreement Id" [PK1] [FK]
"Master Agreement Terms No" [PK2]
Loan Purchase Contract Terms
Primary Key
"Agreement Id" [PK1] [FK]
"Loan Purchase Contract Terms No" [PK2]
Loan Purchase Contract
Primary Key
"Agreement Id" [PK1] [FK]
Master Agreement
Primary Key
"Agreement Id" [PK1] [FK]
Agreement Seller/Servicer
Primary Key
"Agreement Id" [PK1] [FK]
"Party Id" [PK2] [FK]
Seller
Primary Key
"Party Id" [PK1] [FK]
Agreement (Entity Relation Subject Area)
System Architect
Tue Nov 17, 2009 15:15
Data Models
Data Flow Diagrams
Decision Models
User
Story
Epic User Story
54. © 2014 Knowledge Partners International LLC – www.kpiusa.com – www.thedecisionmodel.com
KPI’s Role and Responsibilities
Domain Responsibilities
Process Lead the engagement;
Design and execute training interventions during the course of the
assignment;
Facilitate all meetings which are part of the Agile Methodology (daily
stand‐ups, demonstrations, retrospectives);
Lead release planning, sprint planning, and sizing;
Mentor and coach team members on improving the adoption and
effectiveness of the process;
Provide knowledge transfer to enable self‐reliance.
Engineering Train and coach on the continuous integration framework and
structuring of automated builds;
Advocate simple design for reduced complexity and increased scalability;
Establish and enforce test‐driven development.
Quality Train and mentor on best practices for testing and testing automation;
Establish and enforce test rigor.
64. © 2014 Knowledge Partners International LLC – www.kpiusa.com – www.thedecisionmodel.com
Models
QuickSTEP 3 – Use a set of suitable models and techniques
Business Decision Models
Business Process Models
Visualization
Master Committement Terms
Primary Key
"Agreement Id" [PK1] [FK]
"Master Committment Terms No" [PK2]
Non-Key Attributes
"TOB Id" [FK]
"Master Committment Terms Effective Date"
"Master Committment Terms Expiration Date"
Negotiated Terms of Business
Primary Key
"TOB Id" [PK1]
Non-Key Attributes
"TOB Assigned No"
"TOB Version No"
"TOB Description"
"TOB Effective Date"
"TOB Expiration Date"
Master Committment
Primary Key
"Agreement Id" [PK1] [FK]
Non-Key Attributes
"Master Committment Assigned N o"
"Master Committment Verions No"
Agreement
Primary Key
"Agreement Id" [PK1]
Non-Key Attributes
"Party Id" [FK]
"Agreement Effective Date"
"Agreement Expiration Date"
Master Agreement Terms
Primary Key
"Agreement Id" [PK1] [FK]
"Master Agreement Terms No" [PK2]
Loan Purchase Contract Terms
Primary Key
"Agreement Id" [PK1] [FK]
"Loan Purchase Contract Terms No" [PK2]
Loan Purchase Contract
Primary Key
"Agreement Id" [PK1] [FK]
Master Agreement
Primary Key
"Agreement Id" [PK1] [FK]
Agreement Seller/Servicer
Primary Key
"Agreement Id" [PK1] [FK]
"Party Id" [PK2] [FK]
Seller
Primary Key
"Party Id" [PK1] [FK]
Agreement (Entity Relation Subject Area)
System Architect
Tue Nov 17, 2009 15:15
Conceptual Data Models
Unknown Systems
(TBD)
Business Decision
Management System
BPMS (Deal and Non-Deal
workflow)
Decision
Mgmt Process
Contract Publishing
Service
Contract
Publishing
Process
TOB & nonTOB
Text & Data
Work Queue
Alerts / Requests
Enterprise
Data
Dictionary
Fact Type
Approval
Seller
Servicer
Guide
SSG Text
Process
Models
BPMN
Process
Models
Rule Requirements
(Rule Family Table
Views)
Performance
Metrics
Reporting
(Automated)
Performance
Metrics
Agreement
Data
Business
Intelligence &
Objectives
(Multiple
Sources TBD)
Business
Metrics
Guide
Bulletins
Business Decision Mgmt Future State
Rules Mgmt MISMO Release 2
Views into Negotiated Terms & Repository of Record
Deal & Non-Deal
Management
Workflow Process
Business
Decision
Views
Deal &
Non-Deal
Data
Repository
Customer
Data
Rules Mgmt
Pricing
Engine
(PMA)
Credit
Enhancements
Rule Requirements
(Rule Family Tables)
Fact Type
Request
Customer Eligibility
Criteria, TOB tie down &
Negotiated Terms
Deal
Data
Available
Negotiated
Terms
BRMS
Business
Rules Engine
(iLog)
V0.9
Pricing Workflow
Process
Business
Intent
Decision
Models
Std & Neg
Legal
Language
Components
Customer
Operational
Summery &
Views
Eligibility
Profile
Pricing
Decision
Model
Business Decision Repository
& Extensible Business Objects
Extensible
Business
Objects
Contracting
Decision Views
Contracting Views
Cust
Display
of
Pricing
Contract
Terms
Display
Cust
Decision
Views
Contract
Repository
Attribute
Definition System
(ADS)
Rule Family
Testing &
Deployment
Feedback
Test
Cases
Context Diagrams