I. Use Case Description | |
Use Case Name | Index analysis for ETF development |
Use Case Identifier | IND-EFT-DEV |
Source | IND Content Team |
Point of Contact | |
Creation / Revision Date | 7/19/2019 |
Associated Documents | Requirements documentation, traceability matrix if applicable |
...
There are a number of usage scenarios that this use case represents. Common scenarios that institutions perform on a daily basis include:
- Get the value of an Index at any point in time. Optionally the user can seek details of the constituents' contribution to the movement of index value from a particular point in time (e.g. previous day's close) - JIRA Issue IND-86
- As a user of the Index service, I need to be able to get all the details of the constituents of the Index including the weighting of constituents and other details - JIRA Issue IND-85, IND-81
- Index constituents are changed as conditions require. Whenever this is done there may be a need to "rebalance" the index so that the change in the fundamentals of the constituents does not cause an abrupt discontinuity in the index - JIRA Issue IND-83
- There are certain corporate actions of the Index constituents (like stock splits and stock dividends) that require changes to be done to the Index data maintained. Other examples are share issuance and these require adjustments to prevent the value of index from changing. - JIRA Issue IND-84
IV. Competency Questions
...
- What is the value (price) of this index on a certain date? What are the prices for the constituents of this index as of this date and how are they weighted?
- What are the constituents of this index as of a given date?
- What indices have a given equity as a constituent as of a given date?
Describe at least one way you expect to use the semantics and/or provenance to propose an answer to the questions. Include an initial description of why the semantics and/or provenance representation and reasoning provides an advantage over other obvious approaches to the problem. (optional – depending on the use case and need for supporting business case).
V. Resources
...
Knowledge Bases, Repositories, or other Data Sources
Data | Type | Characteristics | Description | Owner | Source | Access Policies & Usage |
(dataset or repository name) | (remote, local/in situ, etc.) | e.g. – no cloud cover | Short description of the dataset, possibly including rationale of the usage characteristics |
| Source (possibly a system, or remote site) for discovery and access |
|
|
|
|
|
|
|
|
VI. References and Bibliography
...