Page Comparison

II. Use Case Summary

Goal

Describe briefly the goal the use case is intended to satisfy

Requirements

State any requirement(s)specific to this use case, including any capabilities from a business architecture or process model that the use case supports, any metrics or other reporting requirements, etc., including any reference identifier for the requirement(s), as applicableCounterparty exposure is one aspect of managing risk related to derivatives reporting, as one of many requirements related to regulatory reporting on risk.  It involves knowing who your counterparties are and rolling up the risk across legal entities under various scenarios - based on parameters required for stress testing.  Clearly organizations need to understand their counterparty exposure regardless of the reporting requirement.  Companies have many subsidiaries and complex relationships, and understanding total exposure across legal entities can be difficult at best.  The goal is to show how to use FIBO to demonstrate total exposure to a given counterparty.

Requirements

Exposure as a majority stakeholder, as a minority stakeholder, ... this involves percent ownership, what the risk in a given subsidiary might be, what happens if the subsidiary goes under but the parent does not, backing / recourse behind such situations ...

Scope

Identify any known boundaries and the intended scope of the use case

Priority

Identify the priority of the use case (with respect to other use cases for the project)

Stakeholders

Identify all known stakeholders for the use caseOf the three use cases we have to date, this is the top priority and required in order to implement the others.

Stakeholders

Executives within financial control / risk, anyone within the risk organization responsible for identifying counterparty risk, chief risk officer and other C-level executives, board of directors, regulators ...

Description

Summarize the use case, capturing the essential objectives (no longer than a page), including a quick overview, restated goals, and principal actor(s).

User stories, if applicable, and any narrative mapped from those user stories to usage scenarios should be included in the Usage Scenarios section, below.

Actors / Interfaces

List actors: people, systems, knowledge bases, repositories, and other data resources, services, sensors, or other “things” outside the system that either act on the system (primary actors) or are acted on by the system (secondary actors). Primary actors are those that invoke the use case and benefit from the result. Identify the primary actor and briefly describe role. 

Any actor that is external to or outside the control of the use case owner should be further described under Resources, below.

Pre-conditions

Identify any assumptions about the state of the system that must be met for the trigger (below) to initiate the use case.  Any assumptions about the state of other related systems can also be stated here.  List all preconditions.

Post-conditions

Provide any conditions that will be true of the state of the system after the use case has been completed.

Triggers

Describe in detail the event or events that initiate the execution of this use case.  Triggers can be external, temporal, or internal.  They can be single events or a complex event that indicates that some set of conditions has been met.

Performance Requirements

List any known performance-specific requirements – timing and sizing (volume, frequency, etc.), maintainability, reusability, other “-ilities”, etc.

Assumptions

Open Issues