Financial Domain Modeling Principles Framework
5 patterns · 119 sections · 0.1 MB
Table of contents
- Financial Domain Modeling Principles Framework
- Table of Contents
- Financial Domain Modeling Readme
- Practical entries
- FDM-E1 — A score is presented as a financial benefit
- FDM-E2 — A group’s cash is used to justify one entity’s payment
- Preface
- FDM.Preface:1 - The working problem
- FDM.Preface:2 - How the methods connect
- FDM.Preface:3 - Connect models by the financial question
- FDM.Preface:4 - Parties, resources and several useful structures
- FDM.Preface:5 - Practical gain, cost and evidence
- FDM.Preface:6 - Source choices and alternatives
- FDM.Preface:7 - Using the connected account correctly
- FDM.Preface:End
- FDM.1FDM.1 - Recover the Financial Position Behind a Record
- FDM.1:0 - Use this when
- FDM.1:1 - Problem frame
- FDM.1:2 - Problem
- FDM.1:3 - Forces
- FDM.1:4 - Solution
- FDM.1:4.1 - State the financial question and relevant party
- FDM.1:4.2 - Recover the position from its applicable basis
- FDM.1:4.3 - Relate descriptions and resources to the position
- FDM.1:4.4 - Return what is warranted for this use
- FDM.1:5 - Archetypal Grounding
- FDM.1:6 - Bias-Annotation
- FDM.1:7 - Conformance Checklist
- FDM.1:8 - Common Anti-Patterns and How to Avoid Them
- FDM.1:9 - Consequences
- FDM.1:10 - Architectural Rationale
- FDM.1:11 - SoTA-Echoing
- FDM.1:12 - Relations
- FDM.1:End
- FDM.2FDM.2 - Choose Party and Group Boundaries for Financial Modeling
- FDM.2:0 - Use this when
- FDM.2:1 - Problem frame
- FDM.2:2 - Problem
- FDM.2:3 - Forces
- FDM.2:4 - Solution
- FDM.2:4.1 - Start with the financial consequence being examined
- FDM.2:4.2 - State why these members belong together
- FDM.2:4.3 - Recover what connects the positions
- FDM.2:4.4 - Build the warranted aggregate
- FDM.2:4.5 - Return the boundary and its financial meaning
- FDM.2:5 - Archetypal Grounding
- FDM.2:6 - Bias-Annotation
- FDM.2:7 - Conformance Checklist
- FDM.2:8 - Common Anti-Patterns and How to Avoid Them
- FDM.2:9 - Consequences
- FDM.2:10 - Architectural Rationale
- FDM.2:11 - SoTA-Echoing
- FDM.2:12 - Relations
- FDM.2:End
- FDM.3FDM.3 - Derive Events and Conditional Flows from Financial Contract Terms
- FDM.3:0 - Use this when
- FDM.3:1 - Problem frame
- FDM.3:2 - Problem
- FDM.3:3 - Forces
- FDM.3:4 - Solution
- FDM.3:4.1 - Recover the arrangement and intended question
- FDM.3:4.2 - Extract the terms that determine the events
- FDM.3:4.3 - Derive and inspect contractual behavior
- FDM.3:4.4 - Add scenarios and performance without replacing the contract
- FDM.3:4.5 - Return the usable event model and its limits
- FDM.3:5 - Archetypal Grounding
- FDM.3:6 - Bias-Annotation
- FDM.3:7 - Conformance Checklist
- FDM.3:8 - Common Anti-Patterns and How to Avoid Them
- FDM.3:9 - Consequences
- FDM.3:10 - Architectural Rationale
- FDM.3:11 - SoTA-Echoing
- FDM.3:12 - Relations
- FDM.3:End
- FDM.4FDM.4 - Establish What a Financial Action Changed
- FDM.4:0 - Use this when
- FDM.4:1 - Problem frame
- FDM.4:2 - Problem
- FDM.4:3 - Forces
- FDM.4:4 - Solution
- FDM.4:4.1 - Name the claimed change and prior position
- FDM.4:4.2 - Recover the rule that gives the event its effect
- FDM.4:4.3 - Establish what actually occurred
- FDM.4:4.4 - Derive the effect and remaining position
- FDM.4:4.5 - Return the result needed by the next user
- FDM.4:5 - Archetypal Grounding
- FDM.4:5.1 - A payment, an instruction and a modification
- FDM.4:5.2 - Deriving the position through an interpreted calculation
- FDM.4:6 - Bias-Annotation
- FDM.4:7 - Conformance Checklist
- FDM.4:8 - Common Anti-Patterns and How to Avoid Them
- FDM.4:9 - Consequences
- FDM.4:10 - Architectural Rationale
- FDM.4:11 - SoTA-Echoing
- FDM.4:12 - Relations
- FDM.4:End
- FDM.5FDM.5 - Trace a Financial Service to a Participant’s Result
- FDM.5:0 - Use this when
- FDM.5:1 - Problem frame
- FDM.5:2 - Problem
Showing 1–100 of 119 entries. Source edition 1f16950577d0.