Business and Functional Requirements for Counterparty Risk
Detailed definition of business and functional requirements are critical to the success of all technology re-engineering projects. These form a core building block to identifying the right technology solution to meet business needs, whether this ultimate solution might be a bespoke build, vendor package or mixture of the two. For a complex technology implementation such as that required to support counterparty risk management infrastructure and processes, clearly documented business and functional requirements are of particular importance.
Within the InteDelta Delivery Lifecycle for Counterparty Risk, the scope of the requirements gathering and documentation typically incorporates definition of:
- Risk exposure methodologies (Potential Future Exposure, Expected Exposure, stress testing, issuer risk, settlement risk etc)
- Limit categories and hierarchies
- Limit control, maintenance and management requirements
- Customer data maintenance and management requirements
- Legal agreement maintenance and management requirements
- Interface and integration requirements (e.g. for trade feeds, pre-deal checks etc)
- Requirements for data management, validation and sourcing
- User interface and overall usability requirements
- Reporting
- Performance and timeliness of processing
For more details on our wider approach to business and functional requirements definition, see our overall business and functional requirements page.
