Skip to content
This repository has been archived by the owner on Sep 19, 2022. It is now read-only.

Home

Jump to bottom
Shawn Zhang edited this page Oct 9, 2019 · 11 revisions

Rationale of Clojucture

In very high level , clojucture intends to provide building blocks utilities for structured products. Use case would be various depends on the users:

  • Issuer/Originator

They would interest in pool selection and waterfall design, bond sizing (aka structuring ) ~ to build a MBS/ABS deal

  • Investor

They would interest in bond cashflow as they are holding the bond. The bond cashflow depends on the waterfall design and pool performance , investor would use assumptions to project cashflow of pools ,and analysis the bond cashflows. ~ to invest a MBS/ABS bonds

  • Operation

They would focus on regulatory reporting, asset surveillance, ongoing deal monitoring. ~ to automate reporting/accounting process

While there are different trading/structuring/regulatory rules in each market, it is very hard to build an universal solution pertains to all the structured products. clojucture would use namespace local to accommodate country specific/market specific/product specific rules .

all the namespaces except clojucture.local are collections of abstraction of foundation pieces fit into a real Deal while clojucture.local has a real classes(records actually) ready to be initialized for analysis.

Clone this wiki locally